<ns0:Benchmark id="RHEL-7" resolved="1" style="SCAP_1.1" xml:lang="en-US" xmlns:ns0="http://checklists.nist.gov/xccdf/1.1">
  <ns0:status date="2016-11-28">draft</ns0:status>
  <ns0:title xml:lang="en-US">Guide to the Secure Configuration of Red Hat Enterprise Linux 7</ns0:title>
  <ns0:description xml:lang="en-US">This guide presents a catalog of security-relevant
configuration settings for Red Hat Enterprise Linux 7. It is a rendering of
content structured in the eXtensible Configuration Checklist Description Format (XCCDF)
in order to support security automation.  The SCAP content is
is available in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">scap-security-guide</html:code> package which is developed at
<html:a href="https://www.open-scap.org/security-policies/scap-security-guide" xmlns:html="http://www.w3.org/1999/xhtml">https://www.open-scap.org/security-policies/scap-security-guide</html:a>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Providing system administrators with such guidance informs them how to securely
configure systems under their control in a variety of network roles. Policy
makers and baseline creators can use this catalog of settings, with its
associated references to higher-level security control catalogs, in order to
assist them in security baseline creation. This guide is a <html:i xmlns:html="http://www.w3.org/1999/xhtml">catalog, not a
checklist,</html:i> and satisfaction of every item is not likely to be possible or
sensible in many operational scenarios. However, the XCCDF format enables
granular selection and adjustment of settings, and their association with OVAL
and OCIL content provides an automated checking capability. Transformations of
this document, and its associated automated checking content, are capable of
providing baselines that meet a diverse set of policy objectives. Some example
XCCDF <html:i xmlns:html="http://www.w3.org/1999/xhtml">Profiles</html:i>, which are selections of items that form checklists and
can be used as baselines, are available with this guide. They can be
processed, in an automated fashion, with tools that support the Security
Content Automation Protocol (SCAP). The DISA STIG for Red Hat Enterprise Linux 7,
which provides required settings for US Department of Defense systems, is
one example of a baseline created from this guidance.
</ns0:description>
  <ns0:notice id="centos_warning"><html:div xmlns:html="http://www.w3.org/1999/xhtml">
<html:p>This benchmark is a direct port of a <html:i>SCAP Security Guide </html:i> benchmark developed for <html:i>Red Hat Enterprise Linux</html:i>. It has been modified through an automated process to remove specific dependencies on <html:i>Red Hat Enterprise Linux</html:i> and to function with <html:i>CentOS</html:i>. The result is a generally useful <html:i>SCAP Security Guide</html:i> benchmark with the following caveats:</html:p>
<html:ul>
<html:li><html:i>CentOS</html:i> is not an exact copy of <html:i>Red Hat Enterprise Linux</html:i>. There may be configuration differences that produce false positives and/or false negatives. If this occurs please file a bug report.</html:li>

<html:li><html:i>CentOS</html:i> has its own build system, compiler options, patchsets, and is a community supported, non-commercial operating system. <html:i>CentOS</html:i> does not inherit certifications or evaluations from <html:i>Red Hat Enterprise Linux</html:i>. As such, some configuration rules (such as those requiring <html:i>FIPS 140-2</html:i> encryption) will continue to fail on <html:i>CentOS</html:i>.</html:li>
</html:ul>

<html:p>Members of the <html:i>CentOS</html:i> community are invited to participate in <html:a href="http://open-scap.org">OpenSCAP</html:a> and <html:a href="https://github.com/OpenSCAP/scap-security-guide">SCAP Security Guide</html:a> development. Bug reports and patches can be sent to GitHub: <html:a href="https://github.com/OpenSCAP/scap-security-guide">https://github.com/OpenSCAP/scap-security-guide</html:a>. The mailing list is at <html:a href="https://fedorahosted.org/mailman/listinfo/scap-security-guide">https://fedorahosted.org/mailman/listinfo/scap-security-guide</html:a>.</html:p></html:div></ns0:notice>
  <ns0:notice id="terms_of_use" xml:lang="en-US">Do not attempt to implement any of the settings in
this guide without first testing them in a non-operational environment. The
creators of this guidance assume no responsibility whatsoever for its use by
other parties, and makes no guarantees, expressed or implied, about its
quality, reliability, or any other characteristic.</ns0:notice>
  <ns0:front-matter xml:lang="en-US">
    <html:p xmlns:html="http://www.w3.org/1999/xhtml">
      <ns3:svg enable-background="new 30 100 330 150" height="140px" id="Layer_1" version="1.1" viewBox="30 100 330 150" width="350px" x="0px" y="0px" xml:space="preserve" xmlns:ns3="http://www.w3.org/2000/svg">
        <ns3:g fill="#3A3B3B">
          <ns3:path d="m197.1 150.3s-10.1-1.2-14.4-1.2c-7.2 0-11.0 2.6-11.0 8.3 0 6.6 3.5 7.7 12.3 9.6 10.1 2.3 14.5 4.7 14.5 13.6 0 11.2-6.1 15.6-16.1 15.6-6.0 0-16.0-1.6-16.0-1.6l0.6-4.7s9.9 1.3 15.1 1.3c7.2 0 10.8-3.1 10.8-10.2 0-5.7-3.0-7.3-11.2-8.9-10.4-2.3-15.7-4.7-15.7-14.4 0-9.8 6.4-13.6 16.3-13.6 6.0 0 15.3 1.5 15.3 1.5l-0.5 4.8z" />
          <ns3:path d="m238.7 194.6c-3.6 0.7-9.1 1.5-13.9 1.5-15.1 0-18.5-9.2-18.5-25.9 0-17.1 3.3-26.1 18.5-26.1 5.2 0 10.7 1.0 13.9 1.6l-0.2 4.7c-3.3-0.6-9.2-1.3-13.1-1.3-11.2 0-13.2 6.7-13.2 21.1 0 14.1 1.8 20.8 13.4 20.8 4.1 0 9.5-0.7 13.0-1.3l0.2 4.8z" />
          <ns3:path d="m257.5 144.9h12.3l13.9 50.5h-5.6l-3.7-13.0h-21.6l-3.7 13.0h-5.5l13.9-50.5zm-3.4 32.5h19.1l-7.7-27.7h-3.8l-7.7 27.7z" />
          <ns3:path d="m297.2 178.4v17.0h-5.6v-50.5h18.5c11.0 0 16.1 5.3 16.1 16.3 0 11.0-5.1 17.2-16.1 17.2h-12.9zm12.8-5.0c7.4 0 10.4-4.5 10.4-12.3 0-7.7-3.1-11.3-10.4-11.3h-12.8v23.6h12.8z" />
        </ns3:g>
        <ns3:g fill="#676767">
          <ns3:path d="m176.8 211.2s-2.8-0.3-4.0-0.3c-1.5 0-2.2 0.5-2.2 1.4 0 0.9 0.5 1.2 2.8 1.9 2.9 0.9 3.8 1.8 3.8 4.0 0 3.0-2.0 4.3-4.7 4.3-1.9 0-4.5-0.6-4.5-0.6l0.3-2.1s2.7 0.4 4.1 0.4c1.5 0 2.1-0.7 2.1-1.8 0-0.8-0.5-1.2-2.4-1.8-3.1-0.9-4.2-1.9-4.2-4.1 0-2.8 1.9-4.0 4.6-4.0 1.8 0 4.5 0.5 4.5 0.5l-0.2 2.2z" />
          <ns3:path d="m180.6 208.7h8.8v2.4h-6.0v3.2h4.8v2.4h-4.9v3.3h6.0v2.4h-8.8v-13.6z" />
          <ns3:path d="m201.2 222.1c-0.9 0.2-2.7 0.5-4.0 0.5-4.2 0-5.2-2.3-5.2-7.0 0-5.2 1.2-7.0 5.2-7.0 1.4 0 3.1 0.3 4.0 0.5l-0.1 2.2c-0.9-0.1-2.6-0.3-3.5-0.3-2.1 0-2.8 0.7-2.8 4.6 0 3.7 0.5 4.6 2.8 4.6 0.9 0 2.6-0.2 3.4-0.3l0.1 2.3z" />
          <ns3:path d="m209.5 220.2c1.6 0 2.4-0.8 2.4-2.4v-9.1h2.8v9.0c0 3.4-1.8 4.8-5.2 4.8-3.4 0-5.2-1.4-5.2-4.8v-9.0h2.8v9.1c0 1.6 0.8 2.4 2.4 2.4z" />
          <ns3:path d="m221.3 217.8v4.6h-2.8v-13.6h5.3c3.1 0 4.8 1.4 4.8 4.5 0 1.9-0.8 3.1-2.0 3.9l1.9 5.2h-3.0l-1.6-4.6h-2.7zm2.5-6.7h-2.5v4.3h2.6c1.4 0 1.9-1.0 1.9-2.2 0-1.3-0.7-2.2-2.0-2.2z" />
          <ns3:path d="m231.9 208.7h2.8v13.6h-2.8v-13.6z" />
          <ns3:path d="m237.4 208.7h10.0v2.4h-3.6v11.2h-2.8v-11.2h-3.6v-2.4z" />
          <ns3:path d="m255.7 222.3h-2.8v-5.5l-4.2-8.1h3.1l2.5 5.4 2.5-5.4h3.1l-4.2 8.1v5.5z" />
          <ns3:path d="m273.4 215.1h4.0v7.1s-2.9 0.5-4.6 0.5c-4.4 0-5.6-2.5-5.6-7.0 0-5.0 1.4-7.0 5.5-7.0 2.1 0 4.7 0.6 4.7 0.6l-0.1 2.1s-2.4-0.3-4.2-0.3c-2.4 0-3.1 0.8-3.1 4.6 0 3.6 0.5 4.6 3.0 4.6 0.8 0 1.7-0.1 1.7-0.1v-2.6h-1.2v-2.4z" />
          <ns3:path d="m286 220.2c1.6 0 2.4-0.8 2.4-2.4v-9.1h2.8v9.0c0 3.4-1.8 4.8-5.2 4.8s-5.2-1.4-5.2-4.8v-9.0h2.8v9.1c0 1.6 0.8 2.4 2.4 2.4z" />
          <ns3:path d="m295.0 208.7h2.8v13.6h-2.8v-13.6z" />
          <ns3:path d="m301.8 222.3v-13.6h4.6c4.7 0 5.8 2.0 5.6 6.5 0 4.6-0.9 7.1-5.8 7.1h-4.6zm4.6-11.2h-1.8v8.8h1.8c2.7 0 2.9-1.6 2.9-4.7 0-3.0-0.3-4.1-3.0-4.1z" />
          <ns3:path d="m315.5 208.7h8.8v2.4h-6.0v3.2h4.8v2.4h-4.8v3.3h6.0v2.4h-8.8v-13.6z" />
        </ns3:g>
        <ns3:path d="m116.0 204.9h-2.8c-1.5 0-2.8 1.2-2.8 2.7v19.2c0 1.5 1.3 2.7 2.8 2.7h27.9c1.5 0 2.8-1.2 2.8-2.7v-19.2c0-1.5-1.3-2.7-2.8-2.7h-2.8v-8.2c0-6.1-5.0-11.0-11.2-11.0-6.2 0-11.2 4.9-11.2 11.0v8.2zm5.6-8.2c0-3.0 2.5-5.5 5.6-5.4 3.1 0 5.6 2.4 5.6 5.5v8.2h-11.2v-8.2z" fill="#6D0B2B" />
        <ns3:g fill="#AD1D3F">
          <ns3:path d="m106.4 214.7c-16.4 11.4-37.5 7.8-50.0-3.4l11.9-11.7c2.3-1.9 3.4-5.4 1.2-8.8-0.1-0.1-6.7-11.0 2.3-19.8 7.3-7.2 17.8-5.8 23.3-0.3 3.2 3.1 4.9 7.1 4.9 11.4v0.1c0 4.3-1.8 8.5-5.1 11.7-4.0 3.9-9.6 5.4-15.4 4.1-2.1-0.5-4.3 0.8-4.8 2.9-0.5 2.1 0.8 4.2 2.9 4.7 8.4 2.0 16.9-0.3 22.8-6.1 4.9-4.8 7.5-10.9 7.4-17.4-0.0-6.3-2.6-12.3-7.3-16.8-8.2-8.1-23.8-10.3-34.5 0.3-10.7 10.5-6.6 23.8-3.7 28.8l-12.8 12.6c-2.9 2.9-2.3 6.6-0.2 8.7 15.4 15.2 38.7 17.9 56.9 8.2l-0.0-9.1z" />
          <ns3:path d="m43.9 188.4c-1.1-7.5-1.1-21.8 11.2-33.9 8.0-7.9 18.5-12.0 29.5-11.7 10.2 0.3 20.1 4.5 27.1 11.4 7.6 7.4 11.8 17.3 11.9 27.8v0.1c1.16-0.3 2.4-0.4 3.6-0.4 1.5 0 2.9 0.2 4.3 0.6 0-0.1 0.0-0.2 0.0-0.3-0.1-12.5-5.2-24.3-14.2-33.2-8.4-8.3-20.2-13.3-32.4-13.7-13.2-0.5-25.8 4.5-35.4 14.0-9.1 8.9-14.0 20.8-14.0 33.3 0 2.4 0.2 4.8 0.5 7.2 0.6 4.0 1.8 8.1 3.7 12.2 0.9 2.0 3.2 2.8 5.2 1.9 2.0-0.9 2.9-3.1 2.0-5.1-1.5-3.3-2.6-6.8-3.1-10.1z" />
        </ns3:g>
        <ns3:circle cx="127.26" cy="218.49" fill="#fff" r="3.233" />
      </ns3:svg>
    </html:p>
  </ns0:front-matter>
  <ns0:rear-matter xml:lang="en-US">Red Hat and Red Hat Enterprise Linux are either registered
trademarks or trademarks of Red Hat, Inc. in the United States and other
countries. All other names are registered trademarks or trademarks of their
respective companies.</ns0:rear-matter>
  <ns0:platform idref="cpe:/o:redhat:enterprise_linux:7" />
  <ns0:platform idref="cpe:/o:centos:centos:7" />
  <ns0:platform idref="cpe:/o:redhat:enterprise_linux:7::client" />
  <ns0:platform idref="cpe:/o:redhat:enterprise_linux:7::computenode" />
  <ns0:version update="https://github.com/OpenSCAP/scap-security-guide/releases/latest">0.1.31</ns0:version>
  <ns0:metadata>
    <ns2:publisher xmlns:ns2="http://purl.org/dc/elements/1.1/">SCAP Security Guide Project</ns2:publisher>
    <ns2:creator xmlns:ns2="http://purl.org/dc/elements/1.1/">SCAP Security Guide Project</ns2:creator>
    <ns2:source xmlns:ns2="http://purl.org/dc/elements/1.1/">https://github.com/OpenSCAP/scap-security-guide/releases/latest</ns2:source>
  </ns0:metadata>
  <ns0:model system="urn:xccdf:scoring:default" />
  <ns0:Profile id="standard">
    <ns0:title xml:lang="en-US">Standard System Security Profile</ns0:title>
    <ns0:description xml:lang="en-US">This profile contains rules to ensure standard security baseline of Red Hat Enterprise Linux 7 system.
Regardless of your system's workload all of these checks should pass.</ns0:description>
    <ns0:select idref="ensure_redhat_gpgkey_installed" selected="true" />
    <ns0:select idref="ensure_gpgcheck_globally_activated" selected="true" />
    <ns0:select idref="rpm_verify_permissions" selected="true" />
    <ns0:select idref="rpm_verify_hashes" selected="true" />
    <ns0:select idref="no_empty_passwords" selected="true" />
    <ns0:select idref="file_permissions_unauthorized_sgid" selected="true" />
    <ns0:select idref="file_permissions_unauthorized_suid" selected="true" />
    <ns0:select idref="file_permissions_unauthorized_world_writable" selected="true" />
    <ns0:select idref="accounts_root_path_dirs_no_write" selected="true" />
    <ns0:select idref="dir_perms_world_writable_sticky_bits" selected="true" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="disk_partitioning" selected="false" />
    <ns0:select idref="aide" selected="false" />
    <ns0:select idref="endpoint_security_software" selected="false" />
    <ns0:select idref="mcafee_security_software" selected="false" />
    <ns0:select idref="mcafee_hbss_software" selected="false" />
    <ns0:select idref="fips" selected="false" />
    <ns0:select idref="certified-vendor" selected="false" />
    <ns0:select idref="gnome" selected="false" />
    <ns0:select idref="gnome_login_screen" selected="false" />
    <ns0:select idref="gnome_screen_locking" selected="false" />
    <ns0:select idref="gnome_system_settings" selected="false" />
    <ns0:select idref="gnome_network_settings" selected="false" />
    <ns0:select idref="gnome_remote_access_settings" selected="false" />
    <ns0:select idref="gnome_media_settings" selected="false" />
    <ns0:select idref="sudo" selected="false" />
    <ns0:select idref="partitions" selected="false" />
    <ns0:select idref="mounting" selected="false" />
    <ns0:select idref="permissions_important_account_files" selected="false" />
    <ns0:select idref="permissions_within_important_dirs" selected="false" />
    <ns0:select idref="restrictions" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="coredumps" selected="false" />
    <ns0:select idref="enable_execshield_settings" selected="false" />
    <ns0:select idref="enable_nx" selected="false" />
    <ns0:select idref="selinux" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="root_logins" selected="false" />
    <ns0:select idref="password_expiration" selected="false" />
    <ns0:select idref="account_expiration" selected="false" />
    <ns0:select idref="accounts-pam" selected="false" />
    <ns0:select idref="password_quality" selected="false" />
    <ns0:select idref="password_quality_pwquality" selected="false" />
    <ns0:select idref="locking_out_password_attempts" selected="false" />
    <ns0:select idref="set_password_hashing_algorithm" selected="false" />
    <ns0:select idref="user_umask" selected="false" />
    <ns0:select idref="accounts-physical" selected="false" />
    <ns0:select idref="bootloader" selected="false" />
    <ns0:select idref="screen_locking" selected="false" />
    <ns0:select idref="console_screen_locking" selected="false" />
    <ns0:select idref="smart_card_login" selected="false" />
    <ns0:select idref="accounts-banners" selected="false" />
    <ns0:select idref="gui_login_banner" selected="false" />
    <ns0:select idref="network" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="network-kernel" selected="false" />
    <ns0:select idref="network_host_parameters" selected="false" />
    <ns0:select idref="network_host_and_router_parameters" selected="false" />
    <ns0:select idref="network-wireless" selected="false" />
    <ns0:select idref="wireless_software" selected="false" />
    <ns0:select idref="network-ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6" selected="false" />
    <ns0:select idref="configuring_ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6_autoconfig" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="network-firewalld" selected="false" />
    <ns0:select idref="firewalld_activation" selected="false" />
    <ns0:select idref="ruleset_modifications" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-uncommon" selected="false" />
    <ns0:select idref="network-ipsec" selected="false" />
    <ns0:select idref="logging" selected="false" />
    <ns0:select idref="ensure_rsyslog_log_file_configuration" selected="false" />
    <ns0:select idref="rsyslog_sending_messages" selected="false" />
    <ns0:select idref="rsyslog_accepting_remote_messages" selected="false" />
    <ns0:select idref="log_rotation" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="auditing" selected="false" />
    <ns0:select idref="configure_auditd_data_retention" selected="false" />
    <ns0:select idref="auditd_configure_rules" selected="false" />
    <ns0:select idref="audit_time_rules" selected="false" />
    <ns0:select idref="audit_dac_actions" selected="false" />
    <ns0:select idref="services" selected="false" />
    <ns0:select idref="obsolete" selected="false" />
    <ns0:select idref="inetd_and_xinetd" selected="false" />
    <ns0:select idref="telnet" selected="false" />
    <ns0:select idref="r_services" selected="false" />
    <ns0:select idref="nis" selected="false" />
    <ns0:select idref="tftp" selected="false" />
    <ns0:select idref="talk" selected="false" />
    <ns0:select idref="base" selected="false" />
    <ns0:select idref="cron_and_at" selected="false" />
    <ns0:select idref="restrict_at_cron_users" selected="false" />
    <ns0:select idref="docker" selected="false" />
    <ns0:select idref="ssh" selected="false" />
    <ns0:select idref="ssh_server" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="sssd" selected="false" />
    <ns0:select idref="xwindows" selected="false" />
    <ns0:select idref="disabling_xwindows" selected="false" />
    <ns0:select idref="avahi" selected="false" />
    <ns0:select idref="disable_avahi_group" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="printing" selected="false" />
    <ns0:select idref="configure_printing" selected="false" />
    <ns0:select idref="dhcp" selected="false" />
    <ns0:select idref="disabling_dhcp_server" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="disabling_dhcp_client" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="ntp" selected="false" />
    <ns0:select idref="mail" selected="false" />
    <ns0:select idref="postfix_client" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="ldap" selected="false" />
    <ns0:select idref="openldap_client" selected="false" />
    <ns0:select idref="openldap_server" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="nfs_and_rpc" selected="false" />
    <ns0:select idref="disabling_nfs" selected="false" />
    <ns0:select idref="disabling_nfs_services" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="nfs_configuring_clients" selected="false" />
    <ns0:select idref="disabling_nfsd" selected="false" />
    <ns0:select idref="mounting_remote_filesystems" selected="false" />
    <ns0:select idref="nfs_configuring_servers" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns" selected="false" />
    <ns0:select idref="disabling_dns_server" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp" selected="false" />
    <ns0:select idref="disabling_vsftpd" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_configure_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="http" selected="false" />
    <ns0:select idref="disabling_httpd" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="imap" selected="false" />
    <ns0:select idref="disabling_dovecot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="routing" selected="false" />
    <ns0:select idref="disabling_quagga" selected="false" />
    <ns0:select idref="smb" selected="false" />
    <ns0:select idref="disabling_samba" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="proxy" selected="false" />
    <ns0:select idref="disabling_squid" selected="false" />
    <ns0:select idref="snmp" selected="false" />
    <ns0:select idref="disabling_snmp_service" selected="false" />
    <ns0:select idref="snmp_configure_server" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
  </ns0:Profile>
  <ns0:Profile id="pci-dss">
    <ns0:title xml:lang="en-US">PCI-DSS v3 Control Baseline for Red Hat Enterprise Linux 7</ns0:title>
    <ns0:description xml:lang="en-US">This is a *draft* profile for PCI-DSS v3</ns0:description>
    <ns0:select idref="service_auditd_enabled" selected="true" />
    <ns0:select idref="bootloader_audit_argument" selected="true" />
    <ns0:select idref="auditd_data_retention_num_logs" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file_action" selected="true" />
    <ns0:select idref="auditd_data_retention_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_admin_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_action_mail_acct" selected="true" />
    <ns0:select idref="auditd_audispd_syslog_plugin_activated" selected="true" />
    <ns0:select idref="audit_rules_time_adjtimex" selected="true" />
    <ns0:select idref="audit_rules_time_settimeofday" selected="true" />
    <ns0:select idref="audit_rules_time_stime" selected="true" />
    <ns0:select idref="audit_rules_time_clock_settime" selected="true" />
    <ns0:select idref="audit_rules_time_watch_localtime" selected="true" />
    <ns0:select idref="audit_rules_usergroup_modification" selected="true" />
    <ns0:select idref="audit_rules_networkconfig_modification" selected="true" />
    <ns0:select idref="file_permissions_var_log_audit" selected="true" />
    <ns0:select idref="file_ownership_var_log_audit" selected="true" />
    <ns0:select idref="audit_rules_mac_modification" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmodat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchownat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_removexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_setxattr" selected="true" />
    <ns0:select idref="audit_rules_login_events" selected="true" />
    <ns0:select idref="audit_rules_session_events" selected="true" />
    <ns0:select idref="audit_rules_unsuccessful_file_modification" selected="true" />
    <ns0:select idref="audit_rules_privileged_commands" selected="true" />
    <ns0:select idref="audit_rules_media_export" selected="true" />
    <ns0:select idref="audit_rules_file_deletion_events" selected="true" />
    <ns0:select idref="audit_rules_sysadmin_actions" selected="true" />
    <ns0:select idref="audit_rules_kernel_module_loading" selected="true" />
    <ns0:select idref="audit_rules_immutable" selected="true" />
    <ns0:select idref="service_chronyd_or_ntpd_enabled" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_remote_server" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_multiple_servers" selected="true" />
    <ns0:select idref="rpm_verify_permissions" selected="true" />
    <ns0:select idref="rpm_verify_hashes" selected="true" />
    <ns0:select idref="install_hids" selected="true" />
    <ns0:select idref="rsyslog_files_permissions" selected="true" />
    <ns0:select idref="rsyslog_files_ownership" selected="true" />
    <ns0:select idref="rsyslog_files_groupownership" selected="true" />
    <ns0:select idref="ensure_logrotate_activated" selected="true" />
    <ns0:select idref="package_aide_installed" selected="true" />
    <ns0:select idref="disable_prelink" selected="true" />
    <ns0:select idref="aide_build_database" selected="true" />
    <ns0:select idref="aide_periodic_cron_checking" selected="true" />
    <ns0:select idref="account_unique_name" selected="true" />
    <ns0:select idref="gid_passwd_group_same" selected="true" />
    <ns0:select idref="accounts_password_all_shadowed" selected="true" />
    <ns0:select idref="no_empty_passwords" selected="true" />
    <ns0:select idref="display_login_attempts" selected="true" />
    <ns0:select idref="account_disable_post_pw_expiration" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_unlock_time" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_idle_delay" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_idle_activation_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_lock_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_mode_blank" selected="true" />
    <ns0:select idref="sshd_set_idle_timeout" selected="true" />
    <ns0:select idref="accounts_password_pam_minlen" selected="true" />
    <ns0:select idref="accounts_password_pam_dcredit" selected="true" />
    <ns0:select idref="accounts_password_pam_ucredit" selected="true" />
    <ns0:select idref="accounts_password_pam_lcredit" selected="true" />
    <ns0:select idref="accounts_password_pam_unix_remember" selected="true" />
    <ns0:select idref="accounts_maximum_age_login_defs" selected="true" />
    <ns0:select idref="ensure_redhat_gpgkey_installed" selected="true" />
    <ns0:select idref="ensure_gpgcheck_globally_activated" selected="true" />
    <ns0:select idref="ensure_gpgcheck_never_disabled" selected="true" />
    <ns0:select idref="security_patches_up_to_date" selected="true" />
    <ns0:select idref="smartcard_auth" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_systemauth" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_logindefs" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_libuserconf" selected="true" />
    <ns0:select idref="userowner_shadow_file" selected="true" />
    <ns0:select idref="groupowner_shadow_file" selected="true" />
    <ns0:select idref="file_permissions_etc_shadow" selected="true" />
    <ns0:select idref="file_owner_etc_group" selected="true" />
    <ns0:select idref="file_groupowner_etc_group" selected="true" />
    <ns0:select idref="file_permissions_etc_group" selected="true" />
    <ns0:select idref="file_owner_etc_passwd" selected="true" />
    <ns0:select idref="file_groupowner_etc_passwd" selected="true" />
    <ns0:select idref="file_permissions_etc_passwd" selected="true" />
    <ns0:select idref="file_user_owner_grub2_cfg" selected="true" />
    <ns0:select idref="file_group_owner_grub2_cfg" selected="true" />
    <ns0:select idref="package_libreswan_installed" selected="true" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="disk_partitioning" selected="false" />
    <ns0:select idref="mcafee_security_software" selected="false" />
    <ns0:select idref="mcafee_hbss_software" selected="false" />
    <ns0:select idref="fips" selected="false" />
    <ns0:select idref="certified-vendor" selected="false" />
    <ns0:select idref="gnome_login_screen" selected="false" />
    <ns0:select idref="gnome_system_settings" selected="false" />
    <ns0:select idref="gnome_network_settings" selected="false" />
    <ns0:select idref="gnome_remote_access_settings" selected="false" />
    <ns0:select idref="gnome_media_settings" selected="false" />
    <ns0:select idref="sudo" selected="false" />
    <ns0:select idref="partitions" selected="false" />
    <ns0:select idref="mounting" selected="false" />
    <ns0:select idref="permissions_within_important_dirs" selected="false" />
    <ns0:select idref="restrictions" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="coredumps" selected="false" />
    <ns0:select idref="enable_execshield_settings" selected="false" />
    <ns0:select idref="enable_nx" selected="false" />
    <ns0:select idref="selinux" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="root_logins" selected="false" />
    <ns0:select idref="accounts-session" selected="false" />
    <ns0:select idref="root_paths" selected="false" />
    <ns0:select idref="user_umask" selected="false" />
    <ns0:select idref="console_screen_locking" selected="false" />
    <ns0:select idref="accounts-banners" selected="false" />
    <ns0:select idref="gui_login_banner" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="network-kernel" selected="false" />
    <ns0:select idref="network_host_parameters" selected="false" />
    <ns0:select idref="network_host_and_router_parameters" selected="false" />
    <ns0:select idref="network-wireless" selected="false" />
    <ns0:select idref="wireless_software" selected="false" />
    <ns0:select idref="network-ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6" selected="false" />
    <ns0:select idref="configuring_ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6_autoconfig" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="network-firewalld" selected="false" />
    <ns0:select idref="firewalld_activation" selected="false" />
    <ns0:select idref="ruleset_modifications" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-uncommon" selected="false" />
    <ns0:select idref="rsyslog_sending_messages" selected="false" />
    <ns0:select idref="rsyslog_accepting_remote_messages" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="obsolete" selected="false" />
    <ns0:select idref="inetd_and_xinetd" selected="false" />
    <ns0:select idref="telnet" selected="false" />
    <ns0:select idref="r_services" selected="false" />
    <ns0:select idref="nis" selected="false" />
    <ns0:select idref="tftp" selected="false" />
    <ns0:select idref="talk" selected="false" />
    <ns0:select idref="base" selected="false" />
    <ns0:select idref="cron_and_at" selected="false" />
    <ns0:select idref="restrict_at_cron_users" selected="false" />
    <ns0:select idref="docker" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="sssd" selected="false" />
    <ns0:select idref="xwindows" selected="false" />
    <ns0:select idref="disabling_xwindows" selected="false" />
    <ns0:select idref="avahi" selected="false" />
    <ns0:select idref="disable_avahi_group" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="printing" selected="false" />
    <ns0:select idref="configure_printing" selected="false" />
    <ns0:select idref="dhcp" selected="false" />
    <ns0:select idref="disabling_dhcp_server" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="disabling_dhcp_client" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="mail" selected="false" />
    <ns0:select idref="postfix_client" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="ldap" selected="false" />
    <ns0:select idref="openldap_client" selected="false" />
    <ns0:select idref="openldap_server" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="nfs_and_rpc" selected="false" />
    <ns0:select idref="disabling_nfs" selected="false" />
    <ns0:select idref="disabling_nfs_services" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="nfs_configuring_clients" selected="false" />
    <ns0:select idref="disabling_nfsd" selected="false" />
    <ns0:select idref="mounting_remote_filesystems" selected="false" />
    <ns0:select idref="nfs_configuring_servers" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns" selected="false" />
    <ns0:select idref="disabling_dns_server" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp" selected="false" />
    <ns0:select idref="disabling_vsftpd" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_configure_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="http" selected="false" />
    <ns0:select idref="disabling_httpd" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="imap" selected="false" />
    <ns0:select idref="disabling_dovecot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="routing" selected="false" />
    <ns0:select idref="disabling_quagga" selected="false" />
    <ns0:select idref="smb" selected="false" />
    <ns0:select idref="disabling_samba" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="proxy" selected="false" />
    <ns0:select idref="disabling_squid" selected="false" />
    <ns0:select idref="snmp" selected="false" />
    <ns0:select idref="disabling_snmp_service" selected="false" />
    <ns0:select idref="snmp_configure_server" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
    <ns0:refine-value idref="var_password_pam_unix_remember" selector="4" />
    <ns0:refine-value idref="var_account_disable_post_pw_expiration" selector="90" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_deny" selector="6" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_unlock_time" selector="1800" />
    <ns0:refine-value idref="sshd_idle_timeout_value" selector="15_minutes" />
    <ns0:refine-value idref="var_password_pam_minlen" selector="7" />
    <ns0:refine-value idref="var_password_pam_minclass" selector="2" />
    <ns0:refine-value idref="var_accounts_maximum_age_login_defs" selector="90" />
    <ns0:refine-value idref="var_auditd_num_logs" selector="5" />
    <ns0:refine-value idref="var_multiple_time_servers" selector="rhel" />
  </ns0:Profile>
  <ns0:Profile id="C2S">
    <ns0:title xml:lang="en-US">C2S for Red Hat Enterprise Linux 7</ns0:title>
    <ns0:description xml:lang="en-US">This profile demonstrates compliance against the
U.S. Government Commercial Cloud Services (C2S) baseline.

This baseline was inspired by the Center for Internet Security
(CIS) Red Hat Enterprise Linux 7 Benchmark, v1.1.0 - 04-02-2015.
For the SCAP Security Guide project to remain in compliance with
CIS' terms and conditions, specifically Restrictions(8), note
there is no representation or claim that the C2S profile will
ensure a system is in compliance or consistency with the CIS
baseline.
</ns0:description>
    <ns0:select idref="partition_for_tmp" selected="true" />
    <ns0:select idref="mount_option_tmp_nodev" selected="true" />
    <ns0:select idref="mount_option_tmp_nosuid" selected="true" />
    <ns0:select idref="mount_option_tmp_noexec" selected="true" />
    <ns0:select idref="partition_for_var" selected="true" />
    <ns0:select idref="mount_option_var_tmp_bind" selected="true" />
    <ns0:select idref="partition_for_var_log" selected="true" />
    <ns0:select idref="partition_for_var_log_audit" selected="true" />
    <ns0:select idref="partition_for_home" selected="true" />
    <ns0:select idref="mount_option_nodev_nonroot_local_partitions" selected="true" />
    <ns0:select idref="mount_option_nodev_removable_partitions" selected="true" />
    <ns0:select idref="mount_option_noexec_removable_partitions" selected="true" />
    <ns0:select idref="mount_option_nosuid_removable_partitions" selected="true" />
    <ns0:select idref="mount_option_dev_shm_nodev" selected="true" />
    <ns0:select idref="mount_option_dev_shm_nosuid" selected="true" />
    <ns0:select idref="mount_option_dev_shm_noexec" selected="true" />
    <ns0:select idref="dir_perms_world_writable_sticky_bits" selected="true" />
    <ns0:select idref="kernel_module_cramfs_disabled" selected="true" />
    <ns0:select idref="kernel_module_freevxfs_disabled" selected="true" />
    <ns0:select idref="kernel_module_jffs2_disabled" selected="true" />
    <ns0:select idref="kernel_module_hfs_disabled" selected="true" />
    <ns0:select idref="kernel_module_hfsplus_disabled" selected="true" />
    <ns0:select idref="kernel_module_squashfs_disabled" selected="true" />
    <ns0:select idref="kernel_module_udf_disabled" selected="true" />
    <ns0:select idref="ensure_redhat_gpgkey_installed" selected="true" />
    <ns0:select idref="ensure_gpgcheck_globally_activated" selected="true" />
    <ns0:select idref="service_rhnsd_disabled" selected="true" />
    <ns0:select idref="rpm_verify_permissions" selected="true" />
    <ns0:select idref="rpm_verify_hashes" selected="true" />
    <ns0:select idref="package_aide_installed" selected="true" />
    <ns0:select idref="aide_periodic_cron_checking" selected="true" />
    <ns0:select idref="enable_selinux_bootloader" selected="true" />
    <ns0:select idref="selinux_state" selected="true" />
    <ns0:select idref="selinux_policytype" selected="true" />
    <ns0:select idref="package_setroubleshoot_removed" selected="true" />
    <ns0:select idref="package_mcstrans_removed" selected="true" />
    <ns0:select idref="selinux_confinement_of_daemons" selected="true" />
    <ns0:select idref="file_user_owner_grub2_cfg" selected="true" />
    <ns0:select idref="file_group_owner_grub2_cfg" selected="true" />
    <ns0:select idref="file_permissions_grub2_cfg" selected="true" />
    <ns0:select idref="bootloader_password" selected="true" />
    <ns0:select idref="disable_users_coredumps" selected="true" />
    <ns0:select idref="sysctl_fs_suid_dumpable" selected="true" />
    <ns0:select idref="sysctl_kernel_randomize_va_space" selected="true" />
    <ns0:select idref="security_patches_up_to_date" selected="true" />
    <ns0:select idref="package_telnet-server_removed" selected="true" />
    <ns0:select idref="package_telnet_removed" selected="true" />
    <ns0:select idref="package_rsh-server_removed" selected="true" />
    <ns0:select idref="package_rsh_removed" selected="true" />
    <ns0:select idref="package_ypbind_removed" selected="true" />
    <ns0:select idref="package_ypserv_removed" selected="true" />
    <ns0:select idref="package_tftp-server_removed" selected="true" />
    <ns0:select idref="package_tftp_removed" selected="true" />
    <ns0:select idref="package_talk_removed" selected="true" />
    <ns0:select idref="package_talk-server_removed" selected="true" />
    <ns0:select idref="package_xinetd_removed" selected="true" />
    <ns0:select idref="package_xorg-x11-server-common_removed" selected="true" />
    <ns0:select idref="service_avahi-daemon_disabled" selected="true" />
    <ns0:select idref="service_cups_disabled" selected="true" />
    <ns0:select idref="package_dhcp_removed" selected="true" />
    <ns0:select idref="service_chronyd_or_ntpd_enabled" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_remote_server" selected="true" />
    <ns0:select idref="package_openldap-servers_removed" selected="true" />
    <ns0:select idref="service_nfslock_disabled" selected="true" />
    <ns0:select idref="service_rpcgssd_disabled" selected="true" />
    <ns0:select idref="service_rpcbind_disabled" selected="true" />
    <ns0:select idref="service_rpcidmapd_disabled" selected="true" />
    <ns0:select idref="service_rpcsvcgssd_disabled" selected="true" />
    <ns0:select idref="package_bind_removed" selected="true" />
    <ns0:select idref="package_vsftpd_removed" selected="true" />
    <ns0:select idref="package_httpd_removed" selected="true" />
    <ns0:select idref="package_dovecot_removed" selected="true" />
    <ns0:select idref="package_samba_removed" selected="true" />
    <ns0:select idref="package_squid_removed" selected="true" />
    <ns0:select idref="package_net-snmp_removed" selected="true" />
    <ns0:select idref="postfix_network_listening_disabled" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_ip_forward" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_secure_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_secure_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_log_martians" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_log_martians" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_icmp_ignore_bogus_error_responses" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_rp_filter" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_rp_filter" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_tcp_syncookies" selected="true" />
    <ns0:select idref="wireless_disable_interfaces" selected="true" />
    <ns0:select idref="sysctl_net_ipv6_conf_all_accept_ra" selected="true" />
    <ns0:select idref="sysctl_net_ipv6_conf_default_accept_ra" selected="true" />
    <ns0:select idref="sysctl_net_ipv6_conf_all_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv6_conf_default_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_kernel_ipv6_disable" selected="true" />
    <ns0:select idref="kernel_module_dccp_disabled" selected="true" />
    <ns0:select idref="kernel_module_sctp_disabled" selected="true" />
    <ns0:select idref="service_firewalld_enabled" selected="true" />
    <ns0:select idref="package_rsyslog_installed" selected="true" />
    <ns0:select idref="service_rsyslog_enabled" selected="true" />
    <ns0:select idref="rsyslog_files_permissions" selected="true" />
    <ns0:select idref="rsyslog_remote_loghost" selected="true" />
    <ns0:select idref="rsyslog_accept_remote_messages_tcp" selected="true" />
    <ns0:select idref="rsyslog_accept_remote_messages_udp" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file" selected="true" />
    <ns0:select idref="auditd_data_retention_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_action_mail_acct" selected="true" />
    <ns0:select idref="auditd_data_retention_admin_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file_action" selected="true" />
    <ns0:select idref="service_auditd_enabled" selected="true" />
    <ns0:select idref="bootloader_audit_argument" selected="true" />
    <ns0:select idref="audit_rules_time_adjtimex" selected="true" />
    <ns0:select idref="audit_rules_time_settimeofday" selected="true" />
    <ns0:select idref="audit_rules_time_clock_settime" selected="true" />
    <ns0:select idref="audit_rules_time_watch_localtime" selected="true" />
    <ns0:select idref="audit_rules_usergroup_modification" selected="true" />
    <ns0:select idref="audit_rules_networkconfig_modification" selected="true" />
    <ns0:select idref="audit_rules_mac_modification" selected="true" />
    <ns0:select idref="audit_rules_login_events" selected="true" />
    <ns0:select idref="audit_rules_session_events" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmodat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchownat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_setxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_removexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fremovexattr" selected="true" />
    <ns0:select idref="audit_rules_unsuccessful_file_modification" selected="true" />
    <ns0:select idref="audit_rules_privileged_commands" selected="true" />
    <ns0:select idref="audit_rules_media_export" selected="true" />
    <ns0:select idref="audit_rules_file_deletion_events" selected="true" />
    <ns0:select idref="audit_rules_sysadmin_actions" selected="true" />
    <ns0:select idref="audit_rules_kernel_module_loading" selected="true" />
    <ns0:select idref="audit_rules_immutable" selected="true" />
    <ns0:select idref="service_crond_enabled" selected="true" />
    <ns0:select idref="restrict_at_cron_users" selected="false" />
    <ns0:select idref="sshd_allow_only_protocol2" selected="true" />
    <ns0:select idref="sshd_disable_rhosts" selected="true" />
    <ns0:select idref="disable_host_auth" selected="true" />
    <ns0:select idref="sshd_disable_root_login" selected="true" />
    <ns0:select idref="sshd_disable_empty_passwords" selected="true" />
    <ns0:select idref="sshd_do_not_permit_user_env" selected="true" />
    <ns0:select idref="sshd_use_approved_ciphers" selected="true" />
    <ns0:select idref="sshd_set_idle_timeout" selected="true" />
    <ns0:select idref="sshd_set_keepalive" selected="true" />
    <ns0:select idref="sshd_limit_user_access" selected="true" />
    <ns0:select idref="sshd_enable_warning_banner" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_systemauth" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_logindefs" selected="true" />
    <ns0:select idref="accounts_password_pam_retry" selected="true" />
    <ns0:select idref="accounts_password_pam_minlen" selected="true" />
    <ns0:select idref="accounts_password_pam_dcredit" selected="true" />
    <ns0:select idref="accounts_password_pam_ucredit" selected="true" />
    <ns0:select idref="accounts_password_pam_ocredit" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_unlock_time" selected="true" />
    <ns0:select idref="accounts_password_pam_unix_remember" selected="true" />
    <ns0:select idref="no_direct_root_logins" selected="true" />
    <ns0:select idref="accounts_maximum_age_login_defs" selected="true" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="endpoint_security_software" selected="false" />
    <ns0:select idref="mcafee_security_software" selected="false" />
    <ns0:select idref="mcafee_hbss_software" selected="false" />
    <ns0:select idref="fips" selected="false" />
    <ns0:select idref="certified-vendor" selected="false" />
    <ns0:select idref="gnome" selected="false" />
    <ns0:select idref="gnome_login_screen" selected="false" />
    <ns0:select idref="gnome_screen_locking" selected="false" />
    <ns0:select idref="gnome_system_settings" selected="false" />
    <ns0:select idref="gnome_network_settings" selected="false" />
    <ns0:select idref="gnome_remote_access_settings" selected="false" />
    <ns0:select idref="gnome_media_settings" selected="false" />
    <ns0:select idref="sudo" selected="false" />
    <ns0:select idref="permissions_important_account_files" selected="false" />
    <ns0:select idref="permissions_within_important_dirs" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="enable_nx" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="password_storage" selected="false" />
    <ns0:select idref="account_expiration" selected="false" />
    <ns0:select idref="accounts-session" selected="false" />
    <ns0:select idref="root_paths" selected="false" />
    <ns0:select idref="user_umask" selected="false" />
    <ns0:select idref="screen_locking" selected="false" />
    <ns0:select idref="console_screen_locking" selected="false" />
    <ns0:select idref="smart_card_login" selected="false" />
    <ns0:select idref="accounts-banners" selected="false" />
    <ns0:select idref="gui_login_banner" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="ruleset_modifications" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-ipsec" selected="false" />
    <ns0:select idref="log_rotation" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="docker" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="sssd" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="configure_printing" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="disabling_dhcp_client" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="openldap_client" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="mounting_remote_filesystems" selected="false" />
    <ns0:select idref="nfs_configuring_servers" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_configure_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="routing" selected="false" />
    <ns0:select idref="disabling_quagga" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="snmp_configure_server" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
    <ns0:refine-value idref="var_selinux_state" selector="enforcing" />
    <ns0:refine-value idref="var_selinux_policy_name" selector="targeted" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_accept_source_route_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_accept_source_route_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_secure_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_secure_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_log_martians_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_log_martians_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_icmp_ignore_bogus_error_responses_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_rp_filter_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_rp_filter_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_tcp_syncookies_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv6_conf_all_accept_ra_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv6_conf_default_accept_ra_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv6_conf_all_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv6_conf_default_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="var_auditd_max_log_file" selector="20" />
    <ns0:refine-value idref="var_auditd_space_left_action" selector="email" />
    <ns0:refine-value idref="var_auditd_action_mail_acct" selector="root" />
    <ns0:refine-value idref="var_auditd_admin_space_left_action" selector="halt" />
    <ns0:refine-value idref="var_auditd_max_log_file_action" selector="keep_logs" />
    <ns0:refine-value idref="sshd_idle_timeout_value" selector="5_minutes" />
    <ns0:refine-value idref="var_password_pam_retry" selector="3" />
    <ns0:refine-value idref="var_password_pam_minlen" selector="14" />
    <ns0:refine-value idref="var_password_pam_dcredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_ucredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_ocredit" selector="1" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_deny" selector="5" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_unlock_time" selector="900" />
    <ns0:refine-value idref="var_password_pam_unix_remember" selector="5" />
    <ns0:refine-value idref="var_accounts_maximum_age_login_defs" selector="90" />
  </ns0:Profile>
  <ns0:Profile id="rht-ccp">
    <ns0:title xml:lang="en-US">Red Hat Corporate Profile for Certified Cloud Providers (RH CCP)</ns0:title>
    <ns0:description xml:lang="en-US">This is a *draft* SCAP profile for Red Hat Certified Cloud Providers</ns0:description>
    <ns0:select idref="partition_for_tmp" selected="true" />
    <ns0:select idref="partition_for_var" selected="true" />
    <ns0:select idref="partition_for_var_log" selected="true" />
    <ns0:select idref="partition_for_var_log_audit" selected="true" />
    <ns0:select idref="selinux_state" selected="true" />
    <ns0:select idref="selinux_policytype" selected="true" />
    <ns0:select idref="ensure_redhat_gpgkey_installed" selected="true" />
    <ns0:select idref="security_patches_up_to_date" selected="true" />
    <ns0:select idref="ensure_gpgcheck_globally_activated" selected="true" />
    <ns0:select idref="ensure_gpgcheck_never_disabled" selected="true" />
    <ns0:select idref="package_aide_installed" selected="true" />
    <ns0:select idref="accounts_password_pam_unix_remember" selected="true" />
    <ns0:select idref="no_shelllogin_for_systemaccounts" selected="true" />
    <ns0:select idref="no_empty_passwords" selected="true" />
    <ns0:select idref="accounts_password_all_shadowed" selected="true" />
    <ns0:select idref="accounts_no_uid_except_zero" selected="true" />
    <ns0:select idref="accounts_password_minlen_login_defs" selected="true" />
    <ns0:select idref="accounts_minimum_age_login_defs" selected="true" />
    <ns0:select idref="accounts_password_warn_age_login_defs" selected="true" />
    <ns0:select idref="accounts_password_pam_retry" selected="true" />
    <ns0:select idref="accounts_password_pam_dcredit" selected="true" />
    <ns0:select idref="accounts_password_pam_ucredit" selected="true" />
    <ns0:select idref="accounts_password_pam_ocredit" selected="true" />
    <ns0:select idref="accounts_password_pam_lcredit" selected="true" />
    <ns0:select idref="accounts_password_pam_difok" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_systemauth" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_logindefs" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_libuserconf" selected="true" />
    <ns0:select idref="require_singleuser_auth" selected="true" />
    <ns0:select idref="userowner_shadow_file" selected="true" />
    <ns0:select idref="groupowner_shadow_file" selected="true" />
    <ns0:select idref="file_permissions_etc_shadow" selected="true" />
    <ns0:select idref="file_owner_etc_gshadow" selected="true" />
    <ns0:select idref="file_groupowner_etc_gshadow" selected="true" />
    <ns0:select idref="file_permissions_etc_gshadow" selected="true" />
    <ns0:select idref="file_owner_etc_passwd" selected="true" />
    <ns0:select idref="file_groupowner_etc_passwd" selected="true" />
    <ns0:select idref="file_permissions_etc_passwd" selected="true" />
    <ns0:select idref="file_owner_etc_group" selected="true" />
    <ns0:select idref="file_groupowner_etc_group" selected="true" />
    <ns0:select idref="file_permissions_etc_group" selected="true" />
    <ns0:select idref="file_permissions_library_dirs" selected="true" />
    <ns0:select idref="file_ownership_library_dirs" selected="true" />
    <ns0:select idref="file_permissions_binary_dirs" selected="true" />
    <ns0:select idref="file_ownership_binary_dirs" selected="true" />
    <ns0:select idref="file_permissions_var_log_audit" selected="true" />
    <ns0:select idref="file_user_owner_grub2_cfg" selected="true" />
    <ns0:select idref="file_group_owner_grub2_cfg" selected="true" />
    <ns0:select idref="file_permissions_grub2_cfg" selected="true" />
    <ns0:select idref="bootloader_password" selected="true" />
    <ns0:select idref="kernel_module_dccp_disabled" selected="true" />
    <ns0:select idref="kernel_module_sctp_disabled" selected="true" />
    <ns0:select idref="service_firewalld_enabled" selected="true" />
    <ns0:select idref="set_firewalld_default_zone" selected="true" />
    <ns0:select idref="service_abrtd_disabled" selected="true" />
    <ns0:select idref="service_telnet_disabled" selected="true" />
    <ns0:select idref="package_telnet-server_removed" selected="true" />
    <ns0:select idref="package_telnet_removed" selected="true" />
    <ns0:select idref="sshd_allow_only_protocol2" selected="true" />
    <ns0:select idref="sshd_set_idle_timeout" selected="true" />
    <ns0:select idref="sshd_set_keepalive" selected="true" />
    <ns0:select idref="sshd_disable_rhosts" selected="true" />
    <ns0:select idref="disable_host_auth" selected="true" />
    <ns0:select idref="sshd_disable_root_login" selected="true" />
    <ns0:select idref="sshd_disable_empty_passwords" selected="true" />
    <ns0:select idref="sshd_enable_warning_banner" selected="true" />
    <ns0:select idref="sshd_do_not_permit_user_env" selected="true" />
    <ns0:select idref="sshd_use_approved_ciphers" selected="true" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="rpm_verification" selected="false" />
    <ns0:select idref="endpoint_security_software" selected="false" />
    <ns0:select idref="mcafee_security_software" selected="false" />
    <ns0:select idref="mcafee_hbss_software" selected="false" />
    <ns0:select idref="fips" selected="false" />
    <ns0:select idref="certified-vendor" selected="false" />
    <ns0:select idref="gnome" selected="false" />
    <ns0:select idref="gnome_login_screen" selected="false" />
    <ns0:select idref="gnome_screen_locking" selected="false" />
    <ns0:select idref="gnome_system_settings" selected="false" />
    <ns0:select idref="gnome_network_settings" selected="false" />
    <ns0:select idref="gnome_remote_access_settings" selected="false" />
    <ns0:select idref="gnome_media_settings" selected="false" />
    <ns0:select idref="sudo" selected="false" />
    <ns0:select idref="partitions" selected="false" />
    <ns0:select idref="mounting" selected="false" />
    <ns0:select idref="restrictions" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="coredumps" selected="false" />
    <ns0:select idref="enable_execshield_settings" selected="false" />
    <ns0:select idref="enable_nx" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="account_expiration" selected="false" />
    <ns0:select idref="accounts-session" selected="false" />
    <ns0:select idref="root_paths" selected="false" />
    <ns0:select idref="user_umask" selected="false" />
    <ns0:select idref="screen_locking" selected="false" />
    <ns0:select idref="console_screen_locking" selected="false" />
    <ns0:select idref="smart_card_login" selected="false" />
    <ns0:select idref="accounts-banners" selected="false" />
    <ns0:select idref="gui_login_banner" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="network-kernel" selected="false" />
    <ns0:select idref="network_host_parameters" selected="false" />
    <ns0:select idref="network_host_and_router_parameters" selected="false" />
    <ns0:select idref="network-wireless" selected="false" />
    <ns0:select idref="wireless_software" selected="false" />
    <ns0:select idref="network-ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6" selected="false" />
    <ns0:select idref="configuring_ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6_autoconfig" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-ipsec" selected="false" />
    <ns0:select idref="logging" selected="false" />
    <ns0:select idref="ensure_rsyslog_log_file_configuration" selected="false" />
    <ns0:select idref="rsyslog_sending_messages" selected="false" />
    <ns0:select idref="rsyslog_accepting_remote_messages" selected="false" />
    <ns0:select idref="log_rotation" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="configure_auditd_data_retention" selected="false" />
    <ns0:select idref="audit_time_rules" selected="false" />
    <ns0:select idref="audit_dac_actions" selected="false" />
    <ns0:select idref="inetd_and_xinetd" selected="false" />
    <ns0:select idref="r_services" selected="false" />
    <ns0:select idref="nis" selected="false" />
    <ns0:select idref="tftp" selected="false" />
    <ns0:select idref="talk" selected="false" />
    <ns0:select idref="cron_and_at" selected="false" />
    <ns0:select idref="restrict_at_cron_users" selected="false" />
    <ns0:select idref="docker" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="sssd" selected="false" />
    <ns0:select idref="xwindows" selected="false" />
    <ns0:select idref="disabling_xwindows" selected="false" />
    <ns0:select idref="avahi" selected="false" />
    <ns0:select idref="disable_avahi_group" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="printing" selected="false" />
    <ns0:select idref="configure_printing" selected="false" />
    <ns0:select idref="dhcp" selected="false" />
    <ns0:select idref="disabling_dhcp_server" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="disabling_dhcp_client" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="ntp" selected="false" />
    <ns0:select idref="mail" selected="false" />
    <ns0:select idref="postfix_client" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="ldap" selected="false" />
    <ns0:select idref="openldap_client" selected="false" />
    <ns0:select idref="openldap_server" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="nfs_and_rpc" selected="false" />
    <ns0:select idref="disabling_nfs" selected="false" />
    <ns0:select idref="disabling_nfs_services" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="nfs_configuring_clients" selected="false" />
    <ns0:select idref="disabling_nfsd" selected="false" />
    <ns0:select idref="mounting_remote_filesystems" selected="false" />
    <ns0:select idref="nfs_configuring_servers" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns" selected="false" />
    <ns0:select idref="disabling_dns_server" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp" selected="false" />
    <ns0:select idref="disabling_vsftpd" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_configure_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="http" selected="false" />
    <ns0:select idref="disabling_httpd" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="imap" selected="false" />
    <ns0:select idref="disabling_dovecot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="routing" selected="false" />
    <ns0:select idref="disabling_quagga" selected="false" />
    <ns0:select idref="smb" selected="false" />
    <ns0:select idref="disabling_samba" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="proxy" selected="false" />
    <ns0:select idref="disabling_squid" selected="false" />
    <ns0:select idref="snmp" selected="false" />
    <ns0:select idref="disabling_snmp_service" selected="false" />
    <ns0:select idref="snmp_configure_server" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
    <ns0:refine-value idref="var_selinux_state" selector="enforcing" />
    <ns0:refine-value idref="var_selinux_policy_name" selector="targeted" />
    <ns0:refine-value idref="file_owner_logfiles_value" selector="root" />
    <ns0:refine-value idref="file_groupowner_logfiles_value" selector="root" />
    <ns0:refine-value idref="sshd_idle_timeout_value" selector="5_minutes" />
    <ns0:refine-value idref="var_accounts_password_minlen_login_defs" selector="6" />
    <ns0:refine-value idref="var_accounts_minimum_age_login_defs" selector="7" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_deny" selector="5" />
    <ns0:refine-value idref="var_accounts_password_warn_age_login_defs" selector="7" />
    <ns0:refine-value idref="var_password_pam_retry" selector="3" />
    <ns0:refine-value idref="var_password_pam_dcredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_ucredit" selector="2" />
    <ns0:refine-value idref="var_password_pam_ocredit" selector="2" />
    <ns0:refine-value idref="var_password_pam_lcredit" selector="2" />
    <ns0:refine-value idref="var_password_pam_difok" selector="3" />
    <ns0:refine-value idref="var_password_pam_unix_remember" selector="5" />
    <ns0:refine-value idref="var_accounts_user_umask" selector="077" />
    <ns0:refine-value idref="login_banner_text" selector="usgcb_default" />
  </ns0:Profile>
  <ns0:Profile id="common">
    <ns0:title xml:lang="en-US">Common Profile for General-Purpose Systems</ns0:title>
    <ns0:description xml:lang="en-US">This profile contains items common to general-purpose desktop and server installations.</ns0:description>
    <ns0:select idref="partition_for_var_log" selected="true" />
    <ns0:select idref="partition_for_var_log_audit" selected="true" />
    <ns0:select idref="package_rsyslog_installed" selected="true" />
    <ns0:select idref="service_rsyslog_enabled" selected="true" />
    <ns0:select idref="audit_rules_time_adjtimex" selected="true" />
    <ns0:select idref="audit_rules_time_settimeofday" selected="true" />
    <ns0:select idref="audit_rules_time_stime" selected="true" />
    <ns0:select idref="audit_rules_time_clock_settime" selected="true" />
    <ns0:select idref="audit_rules_time_watch_localtime" selected="true" />
    <ns0:select idref="audit_rules_usergroup_modification" selected="true" />
    <ns0:select idref="audit_rules_networkconfig_modification" selected="true" />
    <ns0:select idref="audit_rules_mac_modification" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmodat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchownat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_removexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_setxattr" selected="true" />
    <ns0:select idref="audit_rules_unsuccessful_file_modification" selected="true" />
    <ns0:select idref="audit_rules_privileged_commands" selected="true" />
    <ns0:select idref="audit_rules_media_export" selected="true" />
    <ns0:select idref="audit_rules_file_deletion_events" selected="true" />
    <ns0:select idref="audit_rules_sysadmin_actions" selected="true" />
    <ns0:select idref="audit_rules_kernel_module_loading" selected="true" />
    <ns0:select idref="service_abrtd_disabled" selected="true" />
    <ns0:select idref="service_atd_disabled" selected="true" />
    <ns0:select idref="service_autofs_disabled" selected="true" />
    <ns0:select idref="service_ntpdate_disabled" selected="true" />
    <ns0:select idref="service_oddjobd_disabled" selected="true" />
    <ns0:select idref="service_qpidd_disabled" selected="true" />
    <ns0:select idref="service_rdisc_disabled" selected="true" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="updating" selected="false" />
    <ns0:select idref="integrity" selected="false" />
    <ns0:select idref="software-integrity" selected="false" />
    <ns0:select idref="aide" selected="false" />
    <ns0:select idref="rpm_verification" selected="false" />
    <ns0:select idref="endpoint_security_software" selected="false" />
    <ns0:select idref="mcafee_security_software" selected="false" />
    <ns0:select idref="mcafee_hbss_software" selected="false" />
    <ns0:select idref="fips" selected="false" />
    <ns0:select idref="certified-vendor" selected="false" />
    <ns0:select idref="gnome" selected="false" />
    <ns0:select idref="gnome_login_screen" selected="false" />
    <ns0:select idref="gnome_screen_locking" selected="false" />
    <ns0:select idref="gnome_system_settings" selected="false" />
    <ns0:select idref="gnome_network_settings" selected="false" />
    <ns0:select idref="gnome_remote_access_settings" selected="false" />
    <ns0:select idref="gnome_media_settings" selected="false" />
    <ns0:select idref="sudo" selected="false" />
    <ns0:select idref="partitions" selected="false" />
    <ns0:select idref="files" selected="false" />
    <ns0:select idref="permissions_important_account_files" selected="false" />
    <ns0:select idref="permissions_within_important_dirs" selected="false" />
    <ns0:select idref="restrictions" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="coredumps" selected="false" />
    <ns0:select idref="enable_execshield_settings" selected="false" />
    <ns0:select idref="enable_nx" selected="false" />
    <ns0:select idref="selinux" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="accounts" selected="false" />
    <ns0:select idref="accounts-restrictions" selected="false" />
    <ns0:select idref="root_logins" selected="false" />
    <ns0:select idref="password_storage" selected="false" />
    <ns0:select idref="password_expiration" selected="false" />
    <ns0:select idref="account_expiration" selected="false" />
    <ns0:select idref="accounts-pam" selected="false" />
    <ns0:select idref="password_quality" selected="false" />
    <ns0:select idref="password_quality_pwquality" selected="false" />
    <ns0:select idref="locking_out_password_attempts" selected="false" />
    <ns0:select idref="set_password_hashing_algorithm" selected="false" />
    <ns0:select idref="accounts-session" selected="false" />
    <ns0:select idref="root_paths" selected="false" />
    <ns0:select idref="user_umask" selected="false" />
    <ns0:select idref="accounts-physical" selected="false" />
    <ns0:select idref="bootloader" selected="false" />
    <ns0:select idref="screen_locking" selected="false" />
    <ns0:select idref="console_screen_locking" selected="false" />
    <ns0:select idref="smart_card_login" selected="false" />
    <ns0:select idref="accounts-banners" selected="false" />
    <ns0:select idref="gui_login_banner" selected="false" />
    <ns0:select idref="network" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="network-kernel" selected="false" />
    <ns0:select idref="network_host_parameters" selected="false" />
    <ns0:select idref="network_host_and_router_parameters" selected="false" />
    <ns0:select idref="network-wireless" selected="false" />
    <ns0:select idref="wireless_software" selected="false" />
    <ns0:select idref="network-ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6" selected="false" />
    <ns0:select idref="configuring_ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6_autoconfig" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="network-firewalld" selected="false" />
    <ns0:select idref="firewalld_activation" selected="false" />
    <ns0:select idref="ruleset_modifications" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-uncommon" selected="false" />
    <ns0:select idref="network-ipsec" selected="false" />
    <ns0:select idref="ensure_rsyslog_log_file_configuration" selected="false" />
    <ns0:select idref="rsyslog_sending_messages" selected="false" />
    <ns0:select idref="rsyslog_accepting_remote_messages" selected="false" />
    <ns0:select idref="log_rotation" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="configure_auditd_data_retention" selected="false" />
    <ns0:select idref="obsolete" selected="false" />
    <ns0:select idref="inetd_and_xinetd" selected="false" />
    <ns0:select idref="telnet" selected="false" />
    <ns0:select idref="r_services" selected="false" />
    <ns0:select idref="nis" selected="false" />
    <ns0:select idref="tftp" selected="false" />
    <ns0:select idref="talk" selected="false" />
    <ns0:select idref="restrict_at_cron_users" selected="false" />
    <ns0:select idref="docker" selected="false" />
    <ns0:select idref="ssh" selected="false" />
    <ns0:select idref="ssh_server" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="sssd" selected="false" />
    <ns0:select idref="xwindows" selected="false" />
    <ns0:select idref="disabling_xwindows" selected="false" />
    <ns0:select idref="avahi" selected="false" />
    <ns0:select idref="disable_avahi_group" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="printing" selected="false" />
    <ns0:select idref="configure_printing" selected="false" />
    <ns0:select idref="dhcp" selected="false" />
    <ns0:select idref="disabling_dhcp_server" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="disabling_dhcp_client" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="ntp" selected="false" />
    <ns0:select idref="mail" selected="false" />
    <ns0:select idref="postfix_client" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="ldap" selected="false" />
    <ns0:select idref="openldap_client" selected="false" />
    <ns0:select idref="openldap_server" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="nfs_and_rpc" selected="false" />
    <ns0:select idref="disabling_nfs" selected="false" />
    <ns0:select idref="disabling_nfs_services" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="nfs_configuring_clients" selected="false" />
    <ns0:select idref="disabling_nfsd" selected="false" />
    <ns0:select idref="mounting_remote_filesystems" selected="false" />
    <ns0:select idref="nfs_configuring_servers" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns" selected="false" />
    <ns0:select idref="disabling_dns_server" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp" selected="false" />
    <ns0:select idref="disabling_vsftpd" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_configure_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="http" selected="false" />
    <ns0:select idref="disabling_httpd" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="imap" selected="false" />
    <ns0:select idref="disabling_dovecot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="routing" selected="false" />
    <ns0:select idref="disabling_quagga" selected="false" />
    <ns0:select idref="smb" selected="false" />
    <ns0:select idref="disabling_samba" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="proxy" selected="false" />
    <ns0:select idref="disabling_squid" selected="false" />
    <ns0:select idref="snmp" selected="false" />
    <ns0:select idref="disabling_snmp_service" selected="false" />
    <ns0:select idref="snmp_configure_server" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
  </ns0:Profile>
  <ns0:Profile id="stig-rhel7-workstation-upstream">
    <ns0:title override="true" xml:lang="en-US">STIG for Red Hat Enterprise Linux 7 Workstation</ns0:title>
    <ns0:description override="true" xml:lang="en-US">This is a *draft* profile for STIG. This profile is being developed under the DoD consensus model to become a STIG in coordination with DISA FSO.<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />

<html:p xmlns:html="http://www.w3.org/1999/xhtml"><html:strong>Where is the RHEL7 STIG?</html:strong><html:ul><html:li>Question: May I deploy a product if no STIG exists?<html:br />
            Answer: Yes, based on mission need and with DAA approval.
        </html:li><html:li>Question: What do I use if there is no STIG?<html:br />
            Answer: DISA FSO developed Security Requirement Guides (SRGs) to address technology areas. In the absence of a STIG, an SRG can be used to determine compliance with DoD policies. If there is no applicable SRG or STIG, industry or vendor recommended practices may be used. Examples include Center for Internet Security Benchmarks, Payment Card Industry requirements or the vendor's own security documentation.
        </html:li></html:ul><ns0:small>Source: http://iase.disa.mil/stigs/Pages/faqs.aspx#STIG</ns0:small></html:p>
</ns0:description>
    <ns0:select idref="installed_OS_is_certified" selected="true" />
    <ns0:select idref="accounts_password_pam_minlen" selected="true" />
    <ns0:select idref="accounts_password_pam_ocredit" selected="true" />
    <ns0:select idref="accounts_password_pam_dcredit" selected="true" />
    <ns0:select idref="accounts_password_pam_ucredit" selected="true" />
    <ns0:select idref="accounts_password_pam_lcredit" selected="true" />
    <ns0:select idref="package_screen_installed" selected="true" />
    <ns0:select idref="sshd_set_idle_timeout" selected="true" />
    <ns0:select idref="accounts_password_all_shadowed" selected="true" />
    <ns0:select idref="no_empty_passwords" selected="true" />
    <ns0:select idref="bootloader_password" selected="true" />
    <ns0:select idref="bootloader_uefi_password" selected="true" />
    <ns0:select idref="require_singleuser_auth" selected="true" />
    <ns0:select idref="disable_interactive_boot" selected="true" />
    <ns0:select idref="service_debug-shell_disabled" selected="true" />
    <ns0:select idref="no_direct_root_logins" selected="true" />
    <ns0:select idref="securetty_root_login_console_only" selected="true" />
    <ns0:select idref="restrict_serial_port_logins" selected="true" />
    <ns0:select idref="sshd_disable_root_login" selected="true" />
    <ns0:select idref="sshd_disable_empty_passwords" selected="true" />
    <ns0:select idref="bios_assign_password" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny_root" selected="true" />
    <ns0:select idref="accounts_password_pam_retry" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_unlock_time" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_interval" selected="true" />
    <ns0:select idref="service_firewalld_enabled" selected="true" />
    <ns0:select idref="set_firewalld_default_zone" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_tcp_syncookies" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_ip_forward" selected="true" />
    <ns0:select idref="sysctl_net_ipv6_conf_all_accept_source_route" selected="true" />
    <ns0:select idref="auditd_audispd_syslog_plugin_activated" selected="true" />
    <ns0:select idref="auditd_data_retention_num_logs" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file_action" selected="true" />
    <ns0:select idref="auditd_data_retention_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_admin_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_action_mail_acct" selected="true" />
    <ns0:select idref="file_permissions_var_log_audit" selected="true" />
    <ns0:select idref="service_auditd_enabled" selected="true" />
    <ns0:select idref="bootloader_audit_argument" selected="true" />
    <ns0:select idref="auditd_data_retention_flush" selected="true" />
    <ns0:select idref="audit_rules_time_adjtimex" selected="true" />
    <ns0:select idref="audit_rules_time_settimeofday" selected="true" />
    <ns0:select idref="audit_rules_time_stime" selected="true" />
    <ns0:select idref="audit_rules_time_clock_settime" selected="true" />
    <ns0:select idref="audit_rules_time_watch_localtime" selected="true" />
    <ns0:select idref="audit_rules_usergroup_modification" selected="true" />
    <ns0:select idref="audit_rules_networkconfig_modification" selected="true" />
    <ns0:select idref="audit_rules_mac_modification" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmodat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchownat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_removexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_setxattr" selected="true" />
    <ns0:select idref="audit_rules_login_events" selected="true" />
    <ns0:select idref="audit_rules_session_events" selected="true" />
    <ns0:select idref="audit_rules_unsuccessful_file_modification" selected="true" />
    <ns0:select idref="audit_rules_privileged_commands" selected="true" />
    <ns0:select idref="audit_rules_media_export" selected="true" />
    <ns0:select idref="audit_rules_file_deletion_events" selected="true" />
    <ns0:select idref="audit_rules_sysadmin_actions" selected="true" />
    <ns0:select idref="audit_rules_kernel_module_loading" selected="true" />
    <ns0:select idref="audit_rules_immutable" selected="true" />
    <ns0:select idref="service_chronyd_or_ntpd_enabled" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_remote_server" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_multiple_servers" selected="true" />
    <ns0:select idref="wireless_disable_in_bios" selected="true" />
    <ns0:select idref="wireless_disable_interfaces" selected="true" />
    <ns0:select idref="kernel_module_bluetooth_disabled" selected="true" />
    <ns0:select idref="service_bluetooth_disabled" selected="true" />
    <ns0:select idref="kernel_module_usb-storage_disabled" selected="true" />
    <ns0:select idref="bootloader_nousb_argument" selected="true" />
    <ns0:select idref="bios_disable_usb_boot" selected="true" />
    <ns0:select idref="service_autofs_disabled" selected="true" />
    <ns0:select idref="service_xinetd_disabled" selected="true" />
    <ns0:select idref="package_xinetd_removed" selected="true" />
    <ns0:select idref="service_telnet_disabled" selected="true" />
    <ns0:select idref="package_telnet-server_removed" selected="true" />
    <ns0:select idref="package_telnet_removed" selected="true" />
    <ns0:select idref="package_rsh-server_removed" selected="true" />
    <ns0:select idref="service_rexec_disabled" selected="true" />
    <ns0:select idref="service_rsh_disabled" selected="true" />
    <ns0:select idref="package_rsh_removed" selected="true" />
    <ns0:select idref="service_rlogin_disabled" selected="true" />
    <ns0:select idref="no_rsh_trust_files" selected="true" />
    <ns0:select idref="package_ypserv_removed" selected="true" />
    <ns0:select idref="service_ypbind_disabled" selected="true" />
    <ns0:select idref="package_ypbind_removed" selected="true" />
    <ns0:select idref="package_talk-server_removed" selected="true" />
    <ns0:select idref="package_talk_removed" selected="true" />
    <ns0:select idref="service_crond_enabled" selected="true" />
    <ns0:select idref="sshd_allow_only_protocol2" selected="true" />
    <ns0:select idref="sshd_set_keepalive" selected="true" />
    <ns0:select idref="sshd_disable_rhosts" selected="true" />
    <ns0:select idref="disable_host_auth" selected="true" />
    <ns0:select idref="sshd_do_not_permit_user_env" selected="true" />
    <ns0:select idref="sshd_use_approved_ciphers" selected="true" />
    <ns0:select idref="sshd_use_approved_macs" selected="true" />
    <ns0:select idref="enable_selinux_bootloader" selected="true" />
    <ns0:select idref="selinux_state" selected="true" />
    <ns0:select idref="selinux_policytype" selected="true" />
    <ns0:select idref="selinux_confinement_of_daemons" selected="true" />
    <ns0:select idref="selinux_all_devicefiles_labeled" selected="true" />
    <ns0:select idref="accounts_no_uid_except_zero" selected="true" />
    <ns0:select idref="gid_passwd_group_same" selected="true" />
    <ns0:select idref="rpm_verify_permissions" selected="true" />
    <ns0:select idref="file_permissions_sshd_pub_key" selected="true" />
    <ns0:select idref="file_permissions_sshd_private_key" selected="true" />
    <ns0:select idref="file_permissions_ungroupowned" selected="true" />
    <ns0:select idref="no_files_unowned_by_user" selected="true" />
    <ns0:select idref="package_aide_installed" selected="true" />
    <ns0:select idref="disable_prelink" selected="true" />
    <ns0:select idref="aide_build_database" selected="true" />
    <ns0:select idref="aide_periodic_cron_checking" selected="true" />
    <ns0:select idref="rpm_verify_hashes" selected="true" />
    <ns0:select idref="install_hids" selected="true" />
    <ns0:select idref="sysctl_fs_suid_dumpable" selected="true" />
    <ns0:select idref="sysctl_kernel_exec_shield" selected="true" />
    <ns0:select idref="sysctl_kernel_randomize_va_space" selected="true" />
    <ns0:select idref="install_PAE_kernel_on_x86-32" selected="true" />
    <ns0:select idref="bios_enable_execution_restrictions" selected="true" />
    <ns0:select idref="sysctl_kernel_dmesg_restrict" selected="true" />
    <ns0:select idref="accounts_max_concurrent_login_sessions" selected="true" />
    <ns0:select idref="accounts_maximum_age_login_defs" selected="true" />
    <ns0:select idref="accounts_minimum_age_login_defs" selected="true" />
    <ns0:select idref="accounts_tmout" selected="true" />
    <ns0:select idref="display_login_attempts" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_libuserconf" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_systemauth" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_logindefs" selected="true" />
    <ns0:select idref="encrypt_partitions" selected="true" />
    <ns0:select idref="ensure_gpgcheck_globally_activated" selected="true" />
    <ns0:select idref="ensure_gpgcheck_repo_metadata" selected="true" />
    <ns0:select idref="ensure_gpgcheck_local_packages" selected="true" />
    <ns0:select idref="network_sniffer_disabled" selected="true" />
    <ns0:select idref="partition_for_tmp" selected="true" />
    <ns0:select idref="partition_for_var_log_audit" selected="true" />
    <ns0:select idref="partition_for_var" selected="true" />
    <ns0:select idref="partition_for_home" selected="true" />
    <ns0:select idref="mount_option_nosuid_remote_filesystems" selected="true" />
    <ns0:select idref="mount_option_nodev_remote_filesystems" selected="true" />
    <ns0:select idref="mount_option_nosuid_removable_partitions" selected="true" />
    <ns0:select idref="mount_option_nodev_removable_partitions" selected="true" />
    <ns0:select idref="mount_option_noexec_removable_partitions" selected="true" />
    <ns0:select idref="accounts_password_pam_minclass" selected="true" />
    <ns0:select idref="accounts_password_pam_unix_remember" selected="true" />
    <ns0:select idref="accounts_password_pam_difok" selected="true" />
    <ns0:select idref="accounts_password_pam_maxrepeat" selected="true" />
    <ns0:select idref="accounts_password_pam_maxclassrepeat" selected="true" />
    <ns0:select idref="account_disable_post_pw_expiration" selected="true" />
    <ns0:select idref="account_temp_expire_date" selected="true" />
    <ns0:select idref="accounts_logon_fail_delay" selected="true" />
    <ns0:select idref="sudo_remove_no_authenticate" selected="true" />
    <ns0:select idref="sudo_remove_nopasswd" selected="true" />
    <ns0:select idref="smartcard_auth" selected="true" />
    <ns0:select idref="banner_etc_issue" selected="true" />
    <ns0:select idref="sshd_enable_warning_banner" selected="true" />
    <ns0:select idref="ftp_present_banner" selected="true" />
    <ns0:select idref="accounts_umask_etc_login_defs" selected="true" />
    <ns0:select idref="ensure_redhat_gpgkey_installed" selected="true" />
    <ns0:select idref="ensure_gpgcheck_never_disabled" selected="true" />
    <ns0:select idref="security_patches_up_to_date" selected="true" />
    <ns0:select idref="clean_components_post_updating" selected="true" />
    <ns0:select idref="network_disable_ddns_interfaces" selected="true" />
    <ns0:select idref="libreswan_approved_tunnels" selected="true" />
    <ns0:select idref="package_libreswan_installed" selected="true" />
    <ns0:select idref="package_dracut-fips_installed" selected="true" />
    <ns0:select idref="grub2_enable_fips_mode" selected="true" />
    <ns0:select idref="rsyslog_remote_loghost" selected="true" />
    <ns0:select idref="rsyslog_nolisten" selected="true" />
    <ns0:select idref="rsyslog_cron_logging" selected="true" />
    <ns0:select idref="package_openssh-server_installed" selected="true" />
    <ns0:select idref="firewalld_sshd_port_enabled" selected="true" />
    <ns0:select idref="service_sshd_enabled" selected="true" />
    <ns0:select idref="sshd_disable_compression" selected="true" />
    <ns0:select idref="sshd_disable_gssapi_auth" selected="true" />
    <ns0:select idref="sshd_disable_kerb_auth" selected="true" />
    <ns0:select idref="sshd_enable_strictmodes" selected="true" />
    <ns0:select idref="sshd_use_priv_separation" selected="true" />
    <ns0:select idref="sshd_limit_user_access" selected="true" />
    <ns0:select idref="sshd_print_last_log" selected="true" />
    <ns0:select idref="sshd_disable_user_known_hosts" selected="true" />
    <ns0:select idref="sshd_disable_rhosts_rsa" selected="true" />
    <ns0:select idref="sssd_memcache_timeout" selected="true" />
    <ns0:select idref="sssd_offline_cred_expiration" selected="true" />
    <ns0:select idref="sssd_ssh_known_hosts_timeout" selected="true" />
    <ns0:select idref="install_mcafee_hbss_accm" selected="true" />
    <ns0:select idref="install_mcafee_hbss_pa" selected="true" />
    <ns0:select idref="install_mcafee_antivirus" selected="true" />
    <ns0:select idref="service_nails_enabled" selected="true" />
    <ns0:select idref="mcafee_antivirus_definitions_updated" selected="true" />
    <ns0:select idref="install_antivirus" selected="false" />
    <ns0:select idref="aide_scan_notification" selected="true" />
    <ns0:select idref="aide_verify_acls" selected="true" />
    <ns0:select idref="aide_verify_ext_attributes" selected="true" />
    <ns0:select idref="aide_use_fips_hashes" selected="true" />
    <ns0:select idref="enable_x11_forwarding" selected="true" />
    <ns0:select idref="mount_option_krb_sec_remote_filesystems" selected="true" />
    <ns0:select idref="use_kerberos_security_all_exports" selected="true" />
    <ns0:select idref="package_tftp-server_removed" selected="true" />
    <ns0:select idref="tftpd_uses_secure_mode" selected="true" />
    <ns0:select idref="service_zebra_disabled" selected="true" />
    <ns0:select idref="snmpd_not_default_password" selected="true" />
    <ns0:select idref="service_kdump_disabled" selected="true" />
    <ns0:select idref="package_vsftpd_removed" selected="true" />
    <ns0:select idref="ldap_client_start_tls" selected="true" />
    <ns0:select idref="disable_ctrlaltdel_reboot" selected="true" />
    <ns0:select idref="dir_perms_world_writable_system_owned" selected="true" />
    <ns0:select idref="file_owner_cron_allow" selected="true" />
    <ns0:select idref="file_groupowner_cron_allow" selected="true" />
    <ns0:select idref="dconf_gnome_banner_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_login_banner_text" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_lock_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_lock_delay" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_idle_activation_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_idle_delay" selected="true" />
    <ns0:select idref="dconf_gnome_session_user_locks" selected="true" />
    <ns0:select idref="dconf_gnome_disable_ctrlaltdel_reboot" selected="true" />
    <ns0:select idref="gnome_gdm_disable_automatic_login" selected="true" />
    <ns0:select idref="enable_dconf_user_profile" selected="true" />
    <ns0:select idref="gnome_gdm_disable_guest_login" selected="true" />
    <ns0:select idref="dconf_gnome_disable_user_list" selected="true" />
    <ns0:select idref="dconf_gnome_disable_restart_shutdown" selected="true" />
    <ns0:select idref="dconf_gnome_enable_smartcard_auth" selected="true" />
    <ns0:select idref="dconf_gnome_login_retries" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_mode_blank" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_user_info" selected="true" />
    <ns0:select idref="dconf_gnome_disable_user_admin" selected="true" />
    <ns0:select idref="dconf_gnome_disable_power_settings" selected="true" />
    <ns0:select idref="dconf_gnome_disable_geolocation" selected="true" />
    <ns0:select idref="dconf_gnome_disable_wifi_create" selected="true" />
    <ns0:select idref="dconf_gnome_disable_wifi_notification" selected="true" />
    <ns0:select idref="dconf_gnome_remote_access_credential_prompt" selected="true" />
    <ns0:select idref="dconf_gnome_remote_access_encryption" selected="true" />
    <ns0:select idref="dconf_gnome_disable_automount" selected="true" />
    <ns0:select idref="dconf_gnome_disable_thumbnailers" selected="true" />
    <ns0:select idref="xwindows_runlevel_setting" selected="false" />
    <ns0:select idref="package_xorg-x11-server-common_removed" selected="false" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="permissions_important_account_files" selected="false" />
    <ns0:select idref="permissions_within_important_dirs" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="root_paths" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="disabling_ipv6" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-uncommon" selected="false" />
    <ns0:select idref="log_rotation" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="docker" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="xwindows" selected="false" />
    <ns0:select idref="disabling_xwindows" selected="false" />
    <ns0:select idref="avahi" selected="false" />
    <ns0:select idref="disable_avahi_group" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="printing" selected="false" />
    <ns0:select idref="configure_printing" selected="false" />
    <ns0:select idref="dhcp" selected="false" />
    <ns0:select idref="disabling_dhcp_server" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="disabling_dhcp_client" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="mail" selected="false" />
    <ns0:select idref="postfix_client" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="openldap_server" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="disabling_nfs" selected="false" />
    <ns0:select idref="disabling_nfs_services" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="disabling_nfsd" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns" selected="false" />
    <ns0:select idref="disabling_dns_server" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="http" selected="false" />
    <ns0:select idref="disabling_httpd" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="imap" selected="false" />
    <ns0:select idref="disabling_dovecot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="smb" selected="false" />
    <ns0:select idref="disabling_samba" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="proxy" selected="false" />
    <ns0:select idref="disabling_squid" selected="false" />
    <ns0:select idref="disabling_snmp_service" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
    <ns0:refine-value idref="var_password_pam_minlen" selector="15" />
    <ns0:refine-value idref="var_password_pam_ocredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_dcredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_ucredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_lcredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_retry" selector="3" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_deny" selector="3" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_unlock_time" selector="604800" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_fail_interval" selector="900" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_accept_source_route_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_tcp_syncookies_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value" selector="enabled" />
    <ns0:refine-value idref="var_auditd_num_logs" selector="5" />
    <ns0:refine-value idref="var_auditd_max_log_file" selector="6" />
    <ns0:refine-value idref="var_auditd_max_log_file_action" selector="rotate" />
    <ns0:refine-value idref="var_auditd_space_left_action" selector="email" />
    <ns0:refine-value idref="var_auditd_admin_space_left_action" selector="single" />
    <ns0:refine-value idref="var_auditd_action_mail_acct" selector="root" />
    <ns0:refine-value idref="var_multiple_time_servers" selector="rhel" />
    <ns0:refine-value idref="var_selinux_state" selector="enforcing" />
    <ns0:refine-value idref="var_selinux_policy_name" selector="targeted" />
    <ns0:refine-value idref="var_accounts_max_concurrent_login_sessions" selector="10" />
    <ns0:refine-value idref="var_accounts_maximum_age_login_defs" selector="60" />
    <ns0:refine-value idref="var_accounts_minimum_age_login_defs" selector="1" />
    <ns0:refine-value idref="var_accounts_tmout" selector="10_min" />
    <ns0:refine-value idref="sshd_idle_timeout_value" selector="10_minutes" />
    <ns0:refine-value idref="var_password_pam_unix_remember" selector="5" />
    <ns0:refine-value idref="var_password_pam_difok" selector="8" />
    <ns0:refine-value idref="var_password_pam_minclass" selector="4" />
    <ns0:refine-value idref="var_password_pam_maxrepeat" selector="2" />
    <ns0:refine-value idref="var_password_pam_maxclassrepeat" selector="4" />
    <ns0:refine-value idref="inactivity_timeout_value" selector="15_minutes" />
    <ns0:refine-value idref="var_account_disable_post_pw_expiration" selector="0" />
    <ns0:refine-value idref="var_accounts_fail_delay" selector="4" />
    <ns0:refine-value idref="sshd_listening_port" selector="default" />
    <ns0:refine-value idref="var_accounts_user_umask" selector="077" />
    <ns0:refine-value idref="login_banner_text" selector="dod_default" />
  </ns0:Profile>
  <ns0:Profile id="stig-rhel7-server-gui-upstream">
    <ns0:title override="true" xml:lang="en-US">STIG for Red Hat Enterprise Linux 7 Server Running GUIs</ns0:title>
    <ns0:description override="true" xml:lang="en-US">This is a *draft* profile for STIG. This profile is being developed under the DoD consensus model to become a STIG in coordination with DISA FSO.<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />

<html:p xmlns:html="http://www.w3.org/1999/xhtml"><html:strong>Where is the RHEL7 STIG?</html:strong><html:ul><html:li>Question: May I deploy a product if no STIG exists?<html:br />
            Answer: Yes, based on mission need and with DAA approval.
        </html:li><html:li>Question: What do I use if there is no STIG?<html:br />
            Answer: DISA FSO developed Security Requirement Guides (SRGs) to address technology areas. In the absence of a STIG, an SRG can be used to determine compliance with DoD policies. If there is no applicable SRG or STIG, industry or vendor recommended practices may be used. Examples include Center for Internet Security Benchmarks, Payment Card Industry requirements or the vendor's own security documentation.
        </html:li></html:ul><ns0:small>Source: http://iase.disa.mil/stigs/Pages/faqs.aspx#STIG</ns0:small></html:p>
</ns0:description>
    <ns0:select idref="installed_OS_is_certified" selected="true" />
    <ns0:select idref="accounts_password_pam_minlen" selected="true" />
    <ns0:select idref="accounts_password_pam_ocredit" selected="true" />
    <ns0:select idref="accounts_password_pam_dcredit" selected="true" />
    <ns0:select idref="accounts_password_pam_ucredit" selected="true" />
    <ns0:select idref="accounts_password_pam_lcredit" selected="true" />
    <ns0:select idref="package_screen_installed" selected="true" />
    <ns0:select idref="sshd_set_idle_timeout" selected="true" />
    <ns0:select idref="accounts_password_all_shadowed" selected="true" />
    <ns0:select idref="no_empty_passwords" selected="true" />
    <ns0:select idref="bootloader_password" selected="true" />
    <ns0:select idref="bootloader_uefi_password" selected="true" />
    <ns0:select idref="require_singleuser_auth" selected="true" />
    <ns0:select idref="disable_interactive_boot" selected="true" />
    <ns0:select idref="service_debug-shell_disabled" selected="true" />
    <ns0:select idref="no_direct_root_logins" selected="true" />
    <ns0:select idref="securetty_root_login_console_only" selected="true" />
    <ns0:select idref="restrict_serial_port_logins" selected="true" />
    <ns0:select idref="sshd_disable_root_login" selected="true" />
    <ns0:select idref="sshd_disable_empty_passwords" selected="true" />
    <ns0:select idref="bios_assign_password" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny_root" selected="true" />
    <ns0:select idref="accounts_password_pam_retry" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_unlock_time" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_interval" selected="true" />
    <ns0:select idref="service_firewalld_enabled" selected="true" />
    <ns0:select idref="set_firewalld_default_zone" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_tcp_syncookies" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_ip_forward" selected="true" />
    <ns0:select idref="sysctl_net_ipv6_conf_all_accept_source_route" selected="true" />
    <ns0:select idref="auditd_audispd_syslog_plugin_activated" selected="true" />
    <ns0:select idref="auditd_data_retention_num_logs" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file_action" selected="true" />
    <ns0:select idref="auditd_data_retention_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_admin_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_action_mail_acct" selected="true" />
    <ns0:select idref="file_permissions_var_log_audit" selected="true" />
    <ns0:select idref="service_auditd_enabled" selected="true" />
    <ns0:select idref="bootloader_audit_argument" selected="true" />
    <ns0:select idref="auditd_data_retention_flush" selected="true" />
    <ns0:select idref="audit_rules_time_adjtimex" selected="true" />
    <ns0:select idref="audit_rules_time_settimeofday" selected="true" />
    <ns0:select idref="audit_rules_time_stime" selected="true" />
    <ns0:select idref="audit_rules_time_clock_settime" selected="true" />
    <ns0:select idref="audit_rules_time_watch_localtime" selected="true" />
    <ns0:select idref="audit_rules_usergroup_modification" selected="true" />
    <ns0:select idref="audit_rules_networkconfig_modification" selected="true" />
    <ns0:select idref="audit_rules_mac_modification" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmodat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchownat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_removexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_setxattr" selected="true" />
    <ns0:select idref="audit_rules_login_events" selected="true" />
    <ns0:select idref="audit_rules_session_events" selected="true" />
    <ns0:select idref="audit_rules_unsuccessful_file_modification" selected="true" />
    <ns0:select idref="audit_rules_privileged_commands" selected="true" />
    <ns0:select idref="audit_rules_media_export" selected="true" />
    <ns0:select idref="audit_rules_file_deletion_events" selected="true" />
    <ns0:select idref="audit_rules_sysadmin_actions" selected="true" />
    <ns0:select idref="audit_rules_kernel_module_loading" selected="true" />
    <ns0:select idref="audit_rules_immutable" selected="true" />
    <ns0:select idref="service_chronyd_or_ntpd_enabled" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_remote_server" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_multiple_servers" selected="true" />
    <ns0:select idref="wireless_disable_in_bios" selected="true" />
    <ns0:select idref="wireless_disable_interfaces" selected="true" />
    <ns0:select idref="kernel_module_bluetooth_disabled" selected="true" />
    <ns0:select idref="service_bluetooth_disabled" selected="true" />
    <ns0:select idref="kernel_module_usb-storage_disabled" selected="true" />
    <ns0:select idref="bootloader_nousb_argument" selected="true" />
    <ns0:select idref="bios_disable_usb_boot" selected="true" />
    <ns0:select idref="service_autofs_disabled" selected="true" />
    <ns0:select idref="service_xinetd_disabled" selected="true" />
    <ns0:select idref="package_xinetd_removed" selected="true" />
    <ns0:select idref="service_telnet_disabled" selected="true" />
    <ns0:select idref="package_telnet-server_removed" selected="true" />
    <ns0:select idref="package_telnet_removed" selected="true" />
    <ns0:select idref="package_rsh-server_removed" selected="true" />
    <ns0:select idref="service_rexec_disabled" selected="true" />
    <ns0:select idref="service_rsh_disabled" selected="true" />
    <ns0:select idref="package_rsh_removed" selected="true" />
    <ns0:select idref="service_rlogin_disabled" selected="true" />
    <ns0:select idref="no_rsh_trust_files" selected="true" />
    <ns0:select idref="package_ypserv_removed" selected="true" />
    <ns0:select idref="service_ypbind_disabled" selected="true" />
    <ns0:select idref="package_ypbind_removed" selected="true" />
    <ns0:select idref="package_talk-server_removed" selected="true" />
    <ns0:select idref="package_talk_removed" selected="true" />
    <ns0:select idref="service_crond_enabled" selected="true" />
    <ns0:select idref="sshd_allow_only_protocol2" selected="true" />
    <ns0:select idref="sshd_set_keepalive" selected="true" />
    <ns0:select idref="sshd_disable_rhosts" selected="true" />
    <ns0:select idref="disable_host_auth" selected="true" />
    <ns0:select idref="sshd_do_not_permit_user_env" selected="true" />
    <ns0:select idref="sshd_use_approved_ciphers" selected="true" />
    <ns0:select idref="sshd_use_approved_macs" selected="true" />
    <ns0:select idref="enable_selinux_bootloader" selected="true" />
    <ns0:select idref="selinux_state" selected="true" />
    <ns0:select idref="selinux_policytype" selected="true" />
    <ns0:select idref="selinux_confinement_of_daemons" selected="true" />
    <ns0:select idref="selinux_all_devicefiles_labeled" selected="true" />
    <ns0:select idref="accounts_no_uid_except_zero" selected="true" />
    <ns0:select idref="gid_passwd_group_same" selected="true" />
    <ns0:select idref="rpm_verify_permissions" selected="true" />
    <ns0:select idref="file_permissions_sshd_pub_key" selected="true" />
    <ns0:select idref="file_permissions_sshd_private_key" selected="true" />
    <ns0:select idref="file_permissions_ungroupowned" selected="true" />
    <ns0:select idref="no_files_unowned_by_user" selected="true" />
    <ns0:select idref="package_aide_installed" selected="true" />
    <ns0:select idref="disable_prelink" selected="true" />
    <ns0:select idref="aide_build_database" selected="true" />
    <ns0:select idref="aide_periodic_cron_checking" selected="true" />
    <ns0:select idref="rpm_verify_hashes" selected="true" />
    <ns0:select idref="install_hids" selected="true" />
    <ns0:select idref="sysctl_fs_suid_dumpable" selected="true" />
    <ns0:select idref="sysctl_kernel_exec_shield" selected="true" />
    <ns0:select idref="sysctl_kernel_randomize_va_space" selected="true" />
    <ns0:select idref="install_PAE_kernel_on_x86-32" selected="true" />
    <ns0:select idref="bios_enable_execution_restrictions" selected="true" />
    <ns0:select idref="sysctl_kernel_dmesg_restrict" selected="true" />
    <ns0:select idref="accounts_max_concurrent_login_sessions" selected="true" />
    <ns0:select idref="accounts_maximum_age_login_defs" selected="true" />
    <ns0:select idref="accounts_minimum_age_login_defs" selected="true" />
    <ns0:select idref="accounts_tmout" selected="true" />
    <ns0:select idref="display_login_attempts" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_libuserconf" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_systemauth" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_logindefs" selected="true" />
    <ns0:select idref="encrypt_partitions" selected="true" />
    <ns0:select idref="ensure_gpgcheck_globally_activated" selected="true" />
    <ns0:select idref="ensure_gpgcheck_repo_metadata" selected="true" />
    <ns0:select idref="ensure_gpgcheck_local_packages" selected="true" />
    <ns0:select idref="network_sniffer_disabled" selected="true" />
    <ns0:select idref="partition_for_tmp" selected="true" />
    <ns0:select idref="partition_for_var_log_audit" selected="true" />
    <ns0:select idref="partition_for_var" selected="true" />
    <ns0:select idref="partition_for_home" selected="true" />
    <ns0:select idref="mount_option_nosuid_remote_filesystems" selected="true" />
    <ns0:select idref="mount_option_nodev_remote_filesystems" selected="true" />
    <ns0:select idref="mount_option_nosuid_removable_partitions" selected="true" />
    <ns0:select idref="mount_option_nodev_removable_partitions" selected="true" />
    <ns0:select idref="mount_option_noexec_removable_partitions" selected="true" />
    <ns0:select idref="accounts_password_pam_minclass" selected="true" />
    <ns0:select idref="accounts_password_pam_unix_remember" selected="true" />
    <ns0:select idref="accounts_password_pam_difok" selected="true" />
    <ns0:select idref="accounts_password_pam_maxrepeat" selected="true" />
    <ns0:select idref="accounts_password_pam_maxclassrepeat" selected="true" />
    <ns0:select idref="account_disable_post_pw_expiration" selected="true" />
    <ns0:select idref="account_temp_expire_date" selected="true" />
    <ns0:select idref="accounts_logon_fail_delay" selected="true" />
    <ns0:select idref="sudo_remove_no_authenticate" selected="true" />
    <ns0:select idref="sudo_remove_nopasswd" selected="true" />
    <ns0:select idref="smartcard_auth" selected="true" />
    <ns0:select idref="banner_etc_issue" selected="true" />
    <ns0:select idref="sshd_enable_warning_banner" selected="true" />
    <ns0:select idref="ftp_present_banner" selected="true" />
    <ns0:select idref="accounts_umask_etc_login_defs" selected="true" />
    <ns0:select idref="ensure_redhat_gpgkey_installed" selected="true" />
    <ns0:select idref="ensure_gpgcheck_never_disabled" selected="true" />
    <ns0:select idref="security_patches_up_to_date" selected="true" />
    <ns0:select idref="clean_components_post_updating" selected="true" />
    <ns0:select idref="network_disable_ddns_interfaces" selected="true" />
    <ns0:select idref="libreswan_approved_tunnels" selected="true" />
    <ns0:select idref="package_libreswan_installed" selected="true" />
    <ns0:select idref="package_dracut-fips_installed" selected="true" />
    <ns0:select idref="grub2_enable_fips_mode" selected="true" />
    <ns0:select idref="rsyslog_remote_loghost" selected="true" />
    <ns0:select idref="rsyslog_nolisten" selected="true" />
    <ns0:select idref="rsyslog_cron_logging" selected="true" />
    <ns0:select idref="package_openssh-server_installed" selected="true" />
    <ns0:select idref="firewalld_sshd_port_enabled" selected="true" />
    <ns0:select idref="service_sshd_enabled" selected="true" />
    <ns0:select idref="sshd_disable_compression" selected="true" />
    <ns0:select idref="sshd_disable_gssapi_auth" selected="true" />
    <ns0:select idref="sshd_disable_kerb_auth" selected="true" />
    <ns0:select idref="sshd_enable_strictmodes" selected="true" />
    <ns0:select idref="sshd_use_priv_separation" selected="true" />
    <ns0:select idref="sshd_limit_user_access" selected="true" />
    <ns0:select idref="sshd_print_last_log" selected="true" />
    <ns0:select idref="sshd_disable_user_known_hosts" selected="true" />
    <ns0:select idref="sshd_disable_rhosts_rsa" selected="true" />
    <ns0:select idref="sssd_memcache_timeout" selected="true" />
    <ns0:select idref="sssd_offline_cred_expiration" selected="true" />
    <ns0:select idref="sssd_ssh_known_hosts_timeout" selected="true" />
    <ns0:select idref="install_mcafee_hbss_accm" selected="true" />
    <ns0:select idref="install_mcafee_hbss_pa" selected="true" />
    <ns0:select idref="install_mcafee_antivirus" selected="true" />
    <ns0:select idref="service_nails_enabled" selected="true" />
    <ns0:select idref="mcafee_antivirus_definitions_updated" selected="true" />
    <ns0:select idref="install_antivirus" selected="false" />
    <ns0:select idref="aide_scan_notification" selected="true" />
    <ns0:select idref="aide_verify_acls" selected="true" />
    <ns0:select idref="aide_verify_ext_attributes" selected="true" />
    <ns0:select idref="aide_use_fips_hashes" selected="true" />
    <ns0:select idref="enable_x11_forwarding" selected="true" />
    <ns0:select idref="mount_option_krb_sec_remote_filesystems" selected="true" />
    <ns0:select idref="use_kerberos_security_all_exports" selected="true" />
    <ns0:select idref="package_tftp-server_removed" selected="true" />
    <ns0:select idref="tftpd_uses_secure_mode" selected="true" />
    <ns0:select idref="service_zebra_disabled" selected="true" />
    <ns0:select idref="snmpd_not_default_password" selected="true" />
    <ns0:select idref="service_kdump_disabled" selected="true" />
    <ns0:select idref="package_vsftpd_removed" selected="true" />
    <ns0:select idref="ldap_client_start_tls" selected="true" />
    <ns0:select idref="disable_ctrlaltdel_reboot" selected="true" />
    <ns0:select idref="dir_perms_world_writable_system_owned" selected="true" />
    <ns0:select idref="file_owner_cron_allow" selected="true" />
    <ns0:select idref="file_groupowner_cron_allow" selected="true" />
    <ns0:select idref="dconf_gnome_banner_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_login_banner_text" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_lock_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_lock_delay" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_idle_activation_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_idle_delay" selected="true" />
    <ns0:select idref="dconf_gnome_session_user_locks" selected="true" />
    <ns0:select idref="dconf_gnome_disable_ctrlaltdel_reboot" selected="true" />
    <ns0:select idref="gnome_gdm_disable_automatic_login" selected="true" />
    <ns0:select idref="enable_dconf_user_profile" selected="true" />
    <ns0:select idref="gnome_gdm_disable_guest_login" selected="true" />
    <ns0:select idref="dconf_gnome_disable_user_list" selected="true" />
    <ns0:select idref="dconf_gnome_disable_restart_shutdown" selected="true" />
    <ns0:select idref="dconf_gnome_enable_smartcard_auth" selected="true" />
    <ns0:select idref="dconf_gnome_login_retries" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_mode_blank" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_user_info" selected="true" />
    <ns0:select idref="dconf_gnome_disable_user_admin" selected="true" />
    <ns0:select idref="dconf_gnome_disable_power_settings" selected="true" />
    <ns0:select idref="dconf_gnome_disable_geolocation" selected="true" />
    <ns0:select idref="dconf_gnome_disable_wifi_create" selected="true" />
    <ns0:select idref="dconf_gnome_disable_wifi_notification" selected="true" />
    <ns0:select idref="dconf_gnome_remote_access_credential_prompt" selected="true" />
    <ns0:select idref="dconf_gnome_remote_access_encryption" selected="true" />
    <ns0:select idref="dconf_gnome_disable_automount" selected="true" />
    <ns0:select idref="dconf_gnome_disable_thumbnailers" selected="true" />
    <ns0:select idref="xwindows_runlevel_setting" selected="false" />
    <ns0:select idref="package_xorg-x11-server-common_removed" selected="false" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="permissions_important_account_files" selected="false" />
    <ns0:select idref="permissions_within_important_dirs" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="root_paths" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="disabling_ipv6" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-uncommon" selected="false" />
    <ns0:select idref="log_rotation" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="docker" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="xwindows" selected="false" />
    <ns0:select idref="disabling_xwindows" selected="false" />
    <ns0:select idref="avahi" selected="false" />
    <ns0:select idref="disable_avahi_group" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="printing" selected="false" />
    <ns0:select idref="configure_printing" selected="false" />
    <ns0:select idref="dhcp" selected="false" />
    <ns0:select idref="disabling_dhcp_server" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="disabling_dhcp_client" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="mail" selected="false" />
    <ns0:select idref="postfix_client" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="openldap_server" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="disabling_nfs" selected="false" />
    <ns0:select idref="disabling_nfs_services" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="disabling_nfsd" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns" selected="false" />
    <ns0:select idref="disabling_dns_server" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="http" selected="false" />
    <ns0:select idref="disabling_httpd" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="imap" selected="false" />
    <ns0:select idref="disabling_dovecot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="smb" selected="false" />
    <ns0:select idref="disabling_samba" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="proxy" selected="false" />
    <ns0:select idref="disabling_squid" selected="false" />
    <ns0:select idref="disabling_snmp_service" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
    <ns0:refine-value idref="var_password_pam_minlen" selector="15" />
    <ns0:refine-value idref="var_password_pam_ocredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_dcredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_ucredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_lcredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_retry" selector="3" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_deny" selector="3" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_unlock_time" selector="604800" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_fail_interval" selector="900" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_accept_source_route_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_tcp_syncookies_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value" selector="enabled" />
    <ns0:refine-value idref="var_auditd_num_logs" selector="5" />
    <ns0:refine-value idref="var_auditd_max_log_file" selector="6" />
    <ns0:refine-value idref="var_auditd_max_log_file_action" selector="rotate" />
    <ns0:refine-value idref="var_auditd_space_left_action" selector="email" />
    <ns0:refine-value idref="var_auditd_admin_space_left_action" selector="single" />
    <ns0:refine-value idref="var_auditd_action_mail_acct" selector="root" />
    <ns0:refine-value idref="var_multiple_time_servers" selector="rhel" />
    <ns0:refine-value idref="var_selinux_state" selector="enforcing" />
    <ns0:refine-value idref="var_selinux_policy_name" selector="targeted" />
    <ns0:refine-value idref="var_accounts_max_concurrent_login_sessions" selector="10" />
    <ns0:refine-value idref="var_accounts_maximum_age_login_defs" selector="60" />
    <ns0:refine-value idref="var_accounts_minimum_age_login_defs" selector="1" />
    <ns0:refine-value idref="var_accounts_tmout" selector="10_min" />
    <ns0:refine-value idref="sshd_idle_timeout_value" selector="10_minutes" />
    <ns0:refine-value idref="var_password_pam_unix_remember" selector="5" />
    <ns0:refine-value idref="var_password_pam_difok" selector="8" />
    <ns0:refine-value idref="var_password_pam_minclass" selector="4" />
    <ns0:refine-value idref="var_password_pam_maxrepeat" selector="2" />
    <ns0:refine-value idref="var_password_pam_maxclassrepeat" selector="4" />
    <ns0:refine-value idref="inactivity_timeout_value" selector="15_minutes" />
    <ns0:refine-value idref="var_account_disable_post_pw_expiration" selector="0" />
    <ns0:refine-value idref="var_accounts_fail_delay" selector="4" />
    <ns0:refine-value idref="sshd_listening_port" selector="default" />
    <ns0:refine-value idref="var_accounts_user_umask" selector="077" />
    <ns0:refine-value idref="login_banner_text" selector="dod_default" />
  </ns0:Profile>
  <ns0:Profile id="stig-rhel7-server-upstream">
    <ns0:title override="true" xml:lang="en-US">STIG for Red Hat Enterprise Linux 7 Server</ns0:title>
    <ns0:description override="true" xml:lang="en-US">This is a *draft* profile for STIG. This profile is being developed under the DoD consensus model to become a STIG in coordination with DISA FSO.<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />

<html:p xmlns:html="http://www.w3.org/1999/xhtml"><html:strong>Where is the RHEL7 STIG?</html:strong><html:ul><html:li>Question: May I deploy a product if no STIG exists?<html:br />
            Answer: Yes, based on mission need and with DAA approval.
        </html:li><html:li>Question: What do I use if there is no STIG?<html:br />
            Answer: DISA FSO developed Security Requirement Guides (SRGs) to address technology areas. In the absence of a STIG, an SRG can be used to determine compliance with DoD policies. If there is no applicable SRG or STIG, industry or vendor recommended practices may be used. Examples include Center for Internet Security Benchmarks, Payment Card Industry requirements or the vendor's own security documentation.
        </html:li></html:ul><ns0:small>Source: http://iase.disa.mil/stigs/Pages/faqs.aspx#STIG</ns0:small></html:p>
</ns0:description>
    <ns0:select idref="installed_OS_is_certified" selected="true" />
    <ns0:select idref="accounts_password_pam_minlen" selected="true" />
    <ns0:select idref="accounts_password_pam_ocredit" selected="true" />
    <ns0:select idref="accounts_password_pam_dcredit" selected="true" />
    <ns0:select idref="accounts_password_pam_ucredit" selected="true" />
    <ns0:select idref="accounts_password_pam_lcredit" selected="true" />
    <ns0:select idref="package_screen_installed" selected="true" />
    <ns0:select idref="sshd_set_idle_timeout" selected="true" />
    <ns0:select idref="accounts_password_all_shadowed" selected="true" />
    <ns0:select idref="no_empty_passwords" selected="true" />
    <ns0:select idref="bootloader_password" selected="true" />
    <ns0:select idref="bootloader_uefi_password" selected="true" />
    <ns0:select idref="require_singleuser_auth" selected="true" />
    <ns0:select idref="disable_interactive_boot" selected="true" />
    <ns0:select idref="service_debug-shell_disabled" selected="true" />
    <ns0:select idref="no_direct_root_logins" selected="true" />
    <ns0:select idref="securetty_root_login_console_only" selected="true" />
    <ns0:select idref="restrict_serial_port_logins" selected="true" />
    <ns0:select idref="sshd_disable_root_login" selected="true" />
    <ns0:select idref="sshd_disable_empty_passwords" selected="true" />
    <ns0:select idref="bios_assign_password" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny_root" selected="true" />
    <ns0:select idref="accounts_password_pam_retry" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_unlock_time" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_interval" selected="true" />
    <ns0:select idref="service_firewalld_enabled" selected="true" />
    <ns0:select idref="set_firewalld_default_zone" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_tcp_syncookies" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_ip_forward" selected="true" />
    <ns0:select idref="sysctl_net_ipv6_conf_all_accept_source_route" selected="true" />
    <ns0:select idref="auditd_audispd_syslog_plugin_activated" selected="true" />
    <ns0:select idref="auditd_data_retention_num_logs" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file_action" selected="true" />
    <ns0:select idref="auditd_data_retention_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_admin_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_action_mail_acct" selected="true" />
    <ns0:select idref="file_permissions_var_log_audit" selected="true" />
    <ns0:select idref="service_auditd_enabled" selected="true" />
    <ns0:select idref="bootloader_audit_argument" selected="true" />
    <ns0:select idref="auditd_data_retention_flush" selected="true" />
    <ns0:select idref="audit_rules_time_adjtimex" selected="true" />
    <ns0:select idref="audit_rules_time_settimeofday" selected="true" />
    <ns0:select idref="audit_rules_time_stime" selected="true" />
    <ns0:select idref="audit_rules_time_clock_settime" selected="true" />
    <ns0:select idref="audit_rules_time_watch_localtime" selected="true" />
    <ns0:select idref="audit_rules_usergroup_modification" selected="true" />
    <ns0:select idref="audit_rules_networkconfig_modification" selected="true" />
    <ns0:select idref="audit_rules_mac_modification" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmodat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchownat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_removexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_setxattr" selected="true" />
    <ns0:select idref="audit_rules_login_events" selected="true" />
    <ns0:select idref="audit_rules_session_events" selected="true" />
    <ns0:select idref="audit_rules_unsuccessful_file_modification" selected="true" />
    <ns0:select idref="audit_rules_privileged_commands" selected="true" />
    <ns0:select idref="audit_rules_media_export" selected="true" />
    <ns0:select idref="audit_rules_file_deletion_events" selected="true" />
    <ns0:select idref="audit_rules_sysadmin_actions" selected="true" />
    <ns0:select idref="audit_rules_kernel_module_loading" selected="true" />
    <ns0:select idref="audit_rules_immutable" selected="true" />
    <ns0:select idref="service_chronyd_or_ntpd_enabled" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_remote_server" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_multiple_servers" selected="true" />
    <ns0:select idref="wireless_disable_in_bios" selected="true" />
    <ns0:select idref="wireless_disable_interfaces" selected="true" />
    <ns0:select idref="kernel_module_bluetooth_disabled" selected="true" />
    <ns0:select idref="service_bluetooth_disabled" selected="true" />
    <ns0:select idref="kernel_module_usb-storage_disabled" selected="true" />
    <ns0:select idref="bootloader_nousb_argument" selected="true" />
    <ns0:select idref="bios_disable_usb_boot" selected="true" />
    <ns0:select idref="service_autofs_disabled" selected="true" />
    <ns0:select idref="service_xinetd_disabled" selected="true" />
    <ns0:select idref="package_xinetd_removed" selected="true" />
    <ns0:select idref="service_telnet_disabled" selected="true" />
    <ns0:select idref="package_telnet-server_removed" selected="true" />
    <ns0:select idref="package_telnet_removed" selected="true" />
    <ns0:select idref="package_rsh-server_removed" selected="true" />
    <ns0:select idref="service_rexec_disabled" selected="true" />
    <ns0:select idref="service_rsh_disabled" selected="true" />
    <ns0:select idref="package_rsh_removed" selected="true" />
    <ns0:select idref="service_rlogin_disabled" selected="true" />
    <ns0:select idref="no_rsh_trust_files" selected="true" />
    <ns0:select idref="package_ypserv_removed" selected="true" />
    <ns0:select idref="service_ypbind_disabled" selected="true" />
    <ns0:select idref="package_ypbind_removed" selected="true" />
    <ns0:select idref="package_talk-server_removed" selected="true" />
    <ns0:select idref="package_talk_removed" selected="true" />
    <ns0:select idref="service_crond_enabled" selected="true" />
    <ns0:select idref="sshd_allow_only_protocol2" selected="true" />
    <ns0:select idref="sshd_set_keepalive" selected="true" />
    <ns0:select idref="sshd_disable_rhosts" selected="true" />
    <ns0:select idref="disable_host_auth" selected="true" />
    <ns0:select idref="sshd_do_not_permit_user_env" selected="true" />
    <ns0:select idref="sshd_use_approved_ciphers" selected="true" />
    <ns0:select idref="sshd_use_approved_macs" selected="true" />
    <ns0:select idref="enable_selinux_bootloader" selected="true" />
    <ns0:select idref="selinux_state" selected="true" />
    <ns0:select idref="selinux_policytype" selected="true" />
    <ns0:select idref="selinux_confinement_of_daemons" selected="true" />
    <ns0:select idref="selinux_all_devicefiles_labeled" selected="true" />
    <ns0:select idref="accounts_no_uid_except_zero" selected="true" />
    <ns0:select idref="gid_passwd_group_same" selected="true" />
    <ns0:select idref="rpm_verify_permissions" selected="true" />
    <ns0:select idref="file_permissions_sshd_pub_key" selected="true" />
    <ns0:select idref="file_permissions_sshd_private_key" selected="true" />
    <ns0:select idref="file_permissions_ungroupowned" selected="true" />
    <ns0:select idref="no_files_unowned_by_user" selected="true" />
    <ns0:select idref="package_aide_installed" selected="true" />
    <ns0:select idref="disable_prelink" selected="true" />
    <ns0:select idref="aide_build_database" selected="true" />
    <ns0:select idref="aide_periodic_cron_checking" selected="true" />
    <ns0:select idref="rpm_verify_hashes" selected="true" />
    <ns0:select idref="install_hids" selected="true" />
    <ns0:select idref="sysctl_fs_suid_dumpable" selected="true" />
    <ns0:select idref="sysctl_kernel_exec_shield" selected="true" />
    <ns0:select idref="sysctl_kernel_randomize_va_space" selected="true" />
    <ns0:select idref="install_PAE_kernel_on_x86-32" selected="true" />
    <ns0:select idref="bios_enable_execution_restrictions" selected="true" />
    <ns0:select idref="sysctl_kernel_dmesg_restrict" selected="true" />
    <ns0:select idref="accounts_max_concurrent_login_sessions" selected="true" />
    <ns0:select idref="accounts_maximum_age_login_defs" selected="true" />
    <ns0:select idref="accounts_minimum_age_login_defs" selected="true" />
    <ns0:select idref="accounts_tmout" selected="true" />
    <ns0:select idref="display_login_attempts" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_libuserconf" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_systemauth" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_logindefs" selected="true" />
    <ns0:select idref="encrypt_partitions" selected="true" />
    <ns0:select idref="ensure_gpgcheck_globally_activated" selected="true" />
    <ns0:select idref="ensure_gpgcheck_repo_metadata" selected="true" />
    <ns0:select idref="ensure_gpgcheck_local_packages" selected="true" />
    <ns0:select idref="network_sniffer_disabled" selected="true" />
    <ns0:select idref="partition_for_tmp" selected="true" />
    <ns0:select idref="partition_for_var_log_audit" selected="true" />
    <ns0:select idref="partition_for_var" selected="true" />
    <ns0:select idref="partition_for_home" selected="true" />
    <ns0:select idref="mount_option_nosuid_remote_filesystems" selected="true" />
    <ns0:select idref="mount_option_nodev_remote_filesystems" selected="true" />
    <ns0:select idref="mount_option_nosuid_removable_partitions" selected="true" />
    <ns0:select idref="mount_option_nodev_removable_partitions" selected="true" />
    <ns0:select idref="mount_option_noexec_removable_partitions" selected="true" />
    <ns0:select idref="accounts_password_pam_minclass" selected="true" />
    <ns0:select idref="accounts_password_pam_unix_remember" selected="true" />
    <ns0:select idref="accounts_password_pam_difok" selected="true" />
    <ns0:select idref="accounts_password_pam_maxrepeat" selected="true" />
    <ns0:select idref="accounts_password_pam_maxclassrepeat" selected="true" />
    <ns0:select idref="account_disable_post_pw_expiration" selected="true" />
    <ns0:select idref="account_temp_expire_date" selected="true" />
    <ns0:select idref="accounts_logon_fail_delay" selected="true" />
    <ns0:select idref="sudo_remove_no_authenticate" selected="true" />
    <ns0:select idref="sudo_remove_nopasswd" selected="true" />
    <ns0:select idref="smartcard_auth" selected="true" />
    <ns0:select idref="banner_etc_issue" selected="true" />
    <ns0:select idref="sshd_enable_warning_banner" selected="true" />
    <ns0:select idref="ftp_present_banner" selected="true" />
    <ns0:select idref="accounts_umask_etc_login_defs" selected="true" />
    <ns0:select idref="ensure_redhat_gpgkey_installed" selected="true" />
    <ns0:select idref="ensure_gpgcheck_never_disabled" selected="true" />
    <ns0:select idref="security_patches_up_to_date" selected="true" />
    <ns0:select idref="clean_components_post_updating" selected="true" />
    <ns0:select idref="network_disable_ddns_interfaces" selected="true" />
    <ns0:select idref="libreswan_approved_tunnels" selected="true" />
    <ns0:select idref="package_libreswan_installed" selected="true" />
    <ns0:select idref="package_dracut-fips_installed" selected="true" />
    <ns0:select idref="grub2_enable_fips_mode" selected="true" />
    <ns0:select idref="rsyslog_remote_loghost" selected="true" />
    <ns0:select idref="rsyslog_nolisten" selected="true" />
    <ns0:select idref="rsyslog_cron_logging" selected="true" />
    <ns0:select idref="package_openssh-server_installed" selected="true" />
    <ns0:select idref="firewalld_sshd_port_enabled" selected="true" />
    <ns0:select idref="service_sshd_enabled" selected="true" />
    <ns0:select idref="sshd_disable_compression" selected="true" />
    <ns0:select idref="sshd_disable_gssapi_auth" selected="true" />
    <ns0:select idref="sshd_disable_kerb_auth" selected="true" />
    <ns0:select idref="sshd_enable_strictmodes" selected="true" />
    <ns0:select idref="sshd_use_priv_separation" selected="true" />
    <ns0:select idref="sshd_limit_user_access" selected="true" />
    <ns0:select idref="sshd_print_last_log" selected="true" />
    <ns0:select idref="sshd_disable_user_known_hosts" selected="true" />
    <ns0:select idref="sshd_disable_rhosts_rsa" selected="true" />
    <ns0:select idref="sssd_memcache_timeout" selected="true" />
    <ns0:select idref="sssd_offline_cred_expiration" selected="true" />
    <ns0:select idref="sssd_ssh_known_hosts_timeout" selected="true" />
    <ns0:select idref="install_mcafee_hbss_accm" selected="true" />
    <ns0:select idref="install_mcafee_hbss_pa" selected="true" />
    <ns0:select idref="install_mcafee_antivirus" selected="true" />
    <ns0:select idref="service_nails_enabled" selected="true" />
    <ns0:select idref="mcafee_antivirus_definitions_updated" selected="true" />
    <ns0:select idref="install_antivirus" selected="false" />
    <ns0:select idref="aide_scan_notification" selected="true" />
    <ns0:select idref="aide_verify_acls" selected="true" />
    <ns0:select idref="aide_verify_ext_attributes" selected="true" />
    <ns0:select idref="aide_use_fips_hashes" selected="true" />
    <ns0:select idref="xwindows_runlevel_setting" selected="true" />
    <ns0:select idref="package_xorg-x11-server-common_removed" selected="true" />
    <ns0:select idref="enable_x11_forwarding" selected="true" />
    <ns0:select idref="mount_option_krb_sec_remote_filesystems" selected="true" />
    <ns0:select idref="use_kerberos_security_all_exports" selected="true" />
    <ns0:select idref="package_tftp-server_removed" selected="true" />
    <ns0:select idref="tftpd_uses_secure_mode" selected="true" />
    <ns0:select idref="service_zebra_disabled" selected="true" />
    <ns0:select idref="snmpd_not_default_password" selected="true" />
    <ns0:select idref="service_kdump_disabled" selected="true" />
    <ns0:select idref="package_vsftpd_removed" selected="true" />
    <ns0:select idref="ldap_client_start_tls" selected="true" />
    <ns0:select idref="disable_ctrlaltdel_reboot" selected="true" />
    <ns0:select idref="dir_perms_world_writable_system_owned" selected="true" />
    <ns0:select idref="file_owner_cron_allow" selected="true" />
    <ns0:select idref="file_groupowner_cron_allow" selected="true" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="gnome" selected="false" />
    <ns0:select idref="gnome_login_screen" selected="false" />
    <ns0:select idref="gnome_screen_locking" selected="false" />
    <ns0:select idref="gnome_system_settings" selected="false" />
    <ns0:select idref="gnome_network_settings" selected="false" />
    <ns0:select idref="gnome_remote_access_settings" selected="false" />
    <ns0:select idref="gnome_media_settings" selected="false" />
    <ns0:select idref="permissions_important_account_files" selected="false" />
    <ns0:select idref="permissions_within_important_dirs" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="root_paths" selected="false" />
    <ns0:select idref="gui_login_banner" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="disabling_ipv6" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-uncommon" selected="false" />
    <ns0:select idref="log_rotation" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="docker" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="avahi" selected="false" />
    <ns0:select idref="disable_avahi_group" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="printing" selected="false" />
    <ns0:select idref="configure_printing" selected="false" />
    <ns0:select idref="dhcp" selected="false" />
    <ns0:select idref="disabling_dhcp_server" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="disabling_dhcp_client" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="mail" selected="false" />
    <ns0:select idref="postfix_client" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="openldap_server" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="disabling_nfs" selected="false" />
    <ns0:select idref="disabling_nfs_services" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="disabling_nfsd" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns" selected="false" />
    <ns0:select idref="disabling_dns_server" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="http" selected="false" />
    <ns0:select idref="disabling_httpd" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="imap" selected="false" />
    <ns0:select idref="disabling_dovecot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="smb" selected="false" />
    <ns0:select idref="disabling_samba" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="proxy" selected="false" />
    <ns0:select idref="disabling_squid" selected="false" />
    <ns0:select idref="disabling_snmp_service" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
    <ns0:refine-value idref="var_password_pam_minlen" selector="15" />
    <ns0:refine-value idref="var_password_pam_ocredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_dcredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_ucredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_lcredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_retry" selector="3" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_deny" selector="3" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_unlock_time" selector="604800" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_fail_interval" selector="900" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_accept_source_route_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_tcp_syncookies_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value" selector="enabled" />
    <ns0:refine-value idref="var_auditd_num_logs" selector="5" />
    <ns0:refine-value idref="var_auditd_max_log_file" selector="6" />
    <ns0:refine-value idref="var_auditd_max_log_file_action" selector="rotate" />
    <ns0:refine-value idref="var_auditd_space_left_action" selector="email" />
    <ns0:refine-value idref="var_auditd_admin_space_left_action" selector="single" />
    <ns0:refine-value idref="var_auditd_action_mail_acct" selector="root" />
    <ns0:refine-value idref="var_multiple_time_servers" selector="rhel" />
    <ns0:refine-value idref="var_selinux_state" selector="enforcing" />
    <ns0:refine-value idref="var_selinux_policy_name" selector="targeted" />
    <ns0:refine-value idref="var_accounts_max_concurrent_login_sessions" selector="10" />
    <ns0:refine-value idref="var_accounts_maximum_age_login_defs" selector="60" />
    <ns0:refine-value idref="var_accounts_minimum_age_login_defs" selector="1" />
    <ns0:refine-value idref="var_accounts_tmout" selector="10_min" />
    <ns0:refine-value idref="sshd_idle_timeout_value" selector="10_minutes" />
    <ns0:refine-value idref="var_password_pam_unix_remember" selector="5" />
    <ns0:refine-value idref="var_password_pam_difok" selector="8" />
    <ns0:refine-value idref="login_banner_text" selector="dod_default" />
    <ns0:refine-value idref="var_password_pam_minclass" selector="4" />
    <ns0:refine-value idref="var_password_pam_maxrepeat" selector="2" />
    <ns0:refine-value idref="var_password_pam_maxclassrepeat" selector="4" />
    <ns0:refine-value idref="inactivity_timeout_value" selector="15_minutes" />
    <ns0:refine-value idref="var_account_disable_post_pw_expiration" selector="0" />
    <ns0:refine-value idref="var_accounts_fail_delay" selector="4" />
    <ns0:refine-value idref="sshd_listening_port" selector="default" />
    <ns0:refine-value idref="var_accounts_user_umask" selector="077" />
  </ns0:Profile>
  <ns0:Profile id="ospp-rhel7-server">
    <ns0:title xml:lang="en-US">United States Government Configuration Baseline (USGCB / STIG)</ns0:title>
    <ns0:description override="true" xml:lang="en-US">This is a *draft* profile for NIAP OSPP v4.0. This profile is being developed under the National Information Assurance Partnership. The scope of this profile is to configure Red Hat Enteprise Linux 7 against the NIAP Protection Profile for General Purpose Operating Systems v4.0. The NIAP OSPP profile also serves as a working draft for USGCB submission against RHEL7 Server.</ns0:description>
    <ns0:select idref="installed_OS_is_certified" selected="true" />
    <ns0:select idref="accounts_password_pam_minlen" selected="true" />
    <ns0:select idref="accounts_password_pam_ocredit" selected="true" />
    <ns0:select idref="accounts_password_pam_dcredit" selected="true" />
    <ns0:select idref="accounts_password_pam_ucredit" selected="true" />
    <ns0:select idref="accounts_password_pam_lcredit" selected="true" />
    <ns0:select idref="package_screen_installed" selected="true" />
    <ns0:select idref="sshd_set_idle_timeout" selected="true" />
    <ns0:select idref="accounts_password_all_shadowed" selected="true" />
    <ns0:select idref="no_empty_passwords" selected="true" />
    <ns0:select idref="bootloader_password" selected="true" />
    <ns0:select idref="bootloader_uefi_password" selected="true" />
    <ns0:select idref="require_singleuser_auth" selected="true" />
    <ns0:select idref="disable_interactive_boot" selected="true" />
    <ns0:select idref="service_debug-shell_disabled" selected="true" />
    <ns0:select idref="no_direct_root_logins" selected="true" />
    <ns0:select idref="securetty_root_login_console_only" selected="true" />
    <ns0:select idref="restrict_serial_port_logins" selected="true" />
    <ns0:select idref="sshd_disable_root_login" selected="true" />
    <ns0:select idref="sshd_disable_empty_passwords" selected="true" />
    <ns0:select idref="bios_assign_password" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny_root" selected="true" />
    <ns0:select idref="accounts_password_pam_retry" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_unlock_time" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_interval" selected="true" />
    <ns0:select idref="service_firewalld_enabled" selected="true" />
    <ns0:select idref="set_firewalld_default_zone" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_tcp_syncookies" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_ip_forward" selected="true" />
    <ns0:select idref="sysctl_net_ipv6_conf_all_accept_source_route" selected="true" />
    <ns0:select idref="rsyslog_remote_loghost" selected="true" />
    <ns0:select idref="auditd_audispd_syslog_plugin_activated" selected="true" />
    <ns0:select idref="auditd_data_retention_num_logs" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file_action" selected="true" />
    <ns0:select idref="auditd_data_retention_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_admin_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_action_mail_acct" selected="true" />
    <ns0:select idref="file_permissions_var_log_audit" selected="true" />
    <ns0:select idref="service_auditd_enabled" selected="true" />
    <ns0:select idref="bootloader_audit_argument" selected="true" />
    <ns0:select idref="auditd_data_retention_flush" selected="true" />
    <ns0:select idref="audit_rules_time_adjtimex" selected="true" />
    <ns0:select idref="audit_rules_time_settimeofday" selected="true" />
    <ns0:select idref="audit_rules_time_stime" selected="true" />
    <ns0:select idref="audit_rules_time_clock_settime" selected="true" />
    <ns0:select idref="audit_rules_time_watch_localtime" selected="true" />
    <ns0:select idref="audit_rules_usergroup_modification" selected="true" />
    <ns0:select idref="audit_rules_networkconfig_modification" selected="true" />
    <ns0:select idref="audit_rules_mac_modification" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmodat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchownat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_removexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_setxattr" selected="true" />
    <ns0:select idref="audit_rules_login_events" selected="true" />
    <ns0:select idref="audit_rules_session_events" selected="true" />
    <ns0:select idref="audit_rules_unsuccessful_file_modification" selected="true" />
    <ns0:select idref="audit_rules_privileged_commands" selected="true" />
    <ns0:select idref="audit_rules_media_export" selected="true" />
    <ns0:select idref="audit_rules_file_deletion_events" selected="true" />
    <ns0:select idref="audit_rules_sysadmin_actions" selected="true" />
    <ns0:select idref="audit_rules_kernel_module_loading" selected="true" />
    <ns0:select idref="audit_rules_immutable" selected="true" />
    <ns0:select idref="service_chronyd_or_ntpd_enabled" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_remote_server" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_multiple_servers" selected="true" />
    <ns0:select idref="security_patches_up_to_date" selected="true" />
    <ns0:select idref="wireless_disable_in_bios" selected="true" />
    <ns0:select idref="wireless_disable_interfaces" selected="true" />
    <ns0:select idref="kernel_module_bluetooth_disabled" selected="true" />
    <ns0:select idref="service_bluetooth_disabled" selected="true" />
    <ns0:select idref="kernel_module_usb-storage_disabled" selected="true" />
    <ns0:select idref="bootloader_nousb_argument" selected="true" />
    <ns0:select idref="bios_disable_usb_boot" selected="true" />
    <ns0:select idref="service_autofs_disabled" selected="true" />
    <ns0:select idref="service_xinetd_disabled" selected="true" />
    <ns0:select idref="package_xinetd_removed" selected="true" />
    <ns0:select idref="service_telnet_disabled" selected="true" />
    <ns0:select idref="package_telnet-server_removed" selected="true" />
    <ns0:select idref="package_telnet_removed" selected="true" />
    <ns0:select idref="package_rsh-server_removed" selected="true" />
    <ns0:select idref="service_rexec_disabled" selected="true" />
    <ns0:select idref="service_rsh_disabled" selected="true" />
    <ns0:select idref="package_rsh_removed" selected="true" />
    <ns0:select idref="service_rlogin_disabled" selected="true" />
    <ns0:select idref="no_rsh_trust_files" selected="true" />
    <ns0:select idref="package_ypserv_removed" selected="true" />
    <ns0:select idref="service_ypbind_disabled" selected="true" />
    <ns0:select idref="package_ypbind_removed" selected="true" />
    <ns0:select idref="package_talk-server_removed" selected="true" />
    <ns0:select idref="package_talk_removed" selected="true" />
    <ns0:select idref="service_crond_enabled" selected="true" />
    <ns0:select idref="sshd_allow_only_protocol2" selected="true" />
    <ns0:select idref="sshd_set_keepalive" selected="true" />
    <ns0:select idref="sshd_disable_rhosts" selected="true" />
    <ns0:select idref="disable_host_auth" selected="true" />
    <ns0:select idref="sshd_do_not_permit_user_env" selected="true" />
    <ns0:select idref="sshd_use_approved_ciphers" selected="true" />
    <ns0:select idref="sshd_use_approved_macs" selected="true" />
    <ns0:select idref="enable_selinux_bootloader" selected="true" />
    <ns0:select idref="selinux_state" selected="true" />
    <ns0:select idref="selinux_policytype" selected="true" />
    <ns0:select idref="selinux_confinement_of_daemons" selected="true" />
    <ns0:select idref="selinux_all_devicefiles_labeled" selected="true" />
    <ns0:select idref="accounts_no_uid_except_zero" selected="true" />
    <ns0:select idref="gid_passwd_group_same" selected="true" />
    <ns0:select idref="rpm_verify_permissions" selected="true" />
    <ns0:select idref="file_permissions_sshd_pub_key" selected="true" />
    <ns0:select idref="file_permissions_sshd_private_key" selected="true" />
    <ns0:select idref="file_permissions_ungroupowned" selected="true" />
    <ns0:select idref="no_files_unowned_by_user" selected="true" />
    <ns0:select idref="package_aide_installed" selected="true" />
    <ns0:select idref="disable_prelink" selected="true" />
    <ns0:select idref="aide_build_database" selected="true" />
    <ns0:select idref="aide_periodic_cron_checking" selected="true" />
    <ns0:select idref="rpm_verify_hashes" selected="true" />
    <ns0:select idref="install_hids" selected="true" />
    <ns0:select idref="install_antivirus" selected="true" />
    <ns0:select idref="sysctl_fs_suid_dumpable" selected="true" />
    <ns0:select idref="sysctl_kernel_exec_shield" selected="true" />
    <ns0:select idref="sysctl_kernel_randomize_va_space" selected="true" />
    <ns0:select idref="install_PAE_kernel_on_x86-32" selected="true" />
    <ns0:select idref="bios_enable_execution_restrictions" selected="true" />
    <ns0:select idref="sysctl_kernel_dmesg_restrict" selected="true" />
    <ns0:select idref="accounts_max_concurrent_login_sessions" selected="true" />
    <ns0:select idref="accounts_maximum_age_login_defs" selected="true" />
    <ns0:select idref="accounts_minimum_age_login_defs" selected="true" />
    <ns0:select idref="accounts_tmout" selected="true" />
    <ns0:select idref="display_login_attempts" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_libuserconf" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_systemauth" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_logindefs" selected="true" />
    <ns0:select idref="encrypt_partitions" selected="true" />
    <ns0:select idref="ensure_redhat_gpgkey_installed" selected="true" />
    <ns0:select idref="ensure_gpgcheck_globally_activated" selected="true" />
    <ns0:select idref="ensure_gpgcheck_never_disabled" selected="true" />
    <ns0:select idref="ensure_gpgcheck_repo_metadata" selected="true" />
    <ns0:select idref="ensure_gpgcheck_local_packages" selected="true" />
    <ns0:select idref="network_sniffer_disabled" selected="true" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="mcafee_security_software" selected="false" />
    <ns0:select idref="mcafee_hbss_software" selected="false" />
    <ns0:select idref="fips" selected="false" />
    <ns0:select idref="gnome" selected="false" />
    <ns0:select idref="gnome_login_screen" selected="false" />
    <ns0:select idref="gnome_screen_locking" selected="false" />
    <ns0:select idref="gnome_system_settings" selected="false" />
    <ns0:select idref="gnome_network_settings" selected="false" />
    <ns0:select idref="gnome_remote_access_settings" selected="false" />
    <ns0:select idref="gnome_media_settings" selected="false" />
    <ns0:select idref="sudo" selected="false" />
    <ns0:select idref="partitions" selected="false" />
    <ns0:select idref="permissions_important_account_files" selected="false" />
    <ns0:select idref="permissions_within_important_dirs" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="account_expiration" selected="false" />
    <ns0:select idref="root_paths" selected="false" />
    <ns0:select idref="user_umask" selected="false" />
    <ns0:select idref="smart_card_login" selected="false" />
    <ns0:select idref="accounts-banners" selected="false" />
    <ns0:select idref="gui_login_banner" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="disabling_ipv6" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-uncommon" selected="false" />
    <ns0:select idref="network-ipsec" selected="false" />
    <ns0:select idref="ensure_rsyslog_log_file_configuration" selected="false" />
    <ns0:select idref="rsyslog_accepting_remote_messages" selected="false" />
    <ns0:select idref="log_rotation" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="tftp" selected="false" />
    <ns0:select idref="base" selected="false" />
    <ns0:select idref="restrict_at_cron_users" selected="false" />
    <ns0:select idref="docker" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="sssd" selected="false" />
    <ns0:select idref="xwindows" selected="false" />
    <ns0:select idref="disabling_xwindows" selected="false" />
    <ns0:select idref="avahi" selected="false" />
    <ns0:select idref="disable_avahi_group" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="printing" selected="false" />
    <ns0:select idref="configure_printing" selected="false" />
    <ns0:select idref="dhcp" selected="false" />
    <ns0:select idref="disabling_dhcp_server" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="disabling_dhcp_client" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="mail" selected="false" />
    <ns0:select idref="postfix_client" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="ldap" selected="false" />
    <ns0:select idref="openldap_client" selected="false" />
    <ns0:select idref="openldap_server" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="nfs_and_rpc" selected="false" />
    <ns0:select idref="disabling_nfs" selected="false" />
    <ns0:select idref="disabling_nfs_services" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="nfs_configuring_clients" selected="false" />
    <ns0:select idref="disabling_nfsd" selected="false" />
    <ns0:select idref="mounting_remote_filesystems" selected="false" />
    <ns0:select idref="nfs_configuring_servers" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns" selected="false" />
    <ns0:select idref="disabling_dns_server" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp" selected="false" />
    <ns0:select idref="disabling_vsftpd" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_configure_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="http" selected="false" />
    <ns0:select idref="disabling_httpd" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="imap" selected="false" />
    <ns0:select idref="disabling_dovecot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="routing" selected="false" />
    <ns0:select idref="disabling_quagga" selected="false" />
    <ns0:select idref="smb" selected="false" />
    <ns0:select idref="disabling_samba" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="proxy" selected="false" />
    <ns0:select idref="disabling_squid" selected="false" />
    <ns0:select idref="snmp" selected="false" />
    <ns0:select idref="disabling_snmp_service" selected="false" />
    <ns0:select idref="snmp_configure_server" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
    <ns0:refine-value idref="var_password_pam_minlen" selector="15" />
    <ns0:refine-value idref="var_password_pam_ocredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_dcredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_ucredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_lcredit" selector="1" />
    <ns0:refine-value idref="sshd_idle_timeout_value" selector="5_minutes" />
    <ns0:refine-value idref="var_password_pam_retry" selector="3" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_deny" selector="3" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_unlock_time" selector="604800" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_fail_interval" selector="900" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_accept_source_route_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_tcp_syncookies_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value" selector="enabled" />
    <ns0:refine-value idref="var_auditd_num_logs" selector="5" />
    <ns0:refine-value idref="var_auditd_max_log_file" selector="6" />
    <ns0:refine-value idref="var_auditd_max_log_file_action" selector="rotate" />
    <ns0:refine-value idref="var_auditd_space_left_action" selector="email" />
    <ns0:refine-value idref="var_auditd_admin_space_left_action" selector="single" />
    <ns0:refine-value idref="var_auditd_action_mail_acct" selector="root" />
    <ns0:refine-value idref="var_multiple_time_servers" selector="rhel" />
    <ns0:refine-value idref="var_selinux_state" selector="enforcing" />
    <ns0:refine-value idref="var_selinux_policy_name" selector="targeted" />
    <ns0:refine-value idref="var_accounts_max_concurrent_login_sessions" selector="10" />
    <ns0:refine-value idref="var_accounts_maximum_age_login_defs" selector="60" />
    <ns0:refine-value idref="var_accounts_minimum_age_login_defs" selector="1" />
    <ns0:refine-value idref="var_accounts_tmout" selector="10_min" />
  </ns0:Profile>
  <ns0:Profile id="nist-cl-il-al">
    <ns0:title override="true" xml:lang="en-US">CNSSI 1253 Low/Low/Low Control Baseline for Red Hat Enterprise Linux 7</ns0:title>
    <ns0:description override="true" xml:lang="en-US">This profile follows the Committee on National Security Systems Instruction
(CNSSI) No. 1253, "Security Categorization and Control Selection for National Security
Systems" on security controls to meet low confidentiality, low integrity, and low
assurance."</ns0:description>
    <ns0:select idref="partition_for_var_log" selected="true" />
    <ns0:select idref="partition_for_var_log_audit" selected="true" />
    <ns0:select idref="package_rsyslog_installed" selected="true" />
    <ns0:select idref="service_rsyslog_enabled" selected="true" />
    <ns0:select idref="account_temp_expire_date" selected="true" />
    <ns0:select idref="account_disable_post_pw_expiration" selected="true" />
    <ns0:select idref="audit_rules_usergroup_modification" selected="true" />
    <ns0:select idref="audit_rules_sysadmin_actions" selected="true" />
    <ns0:select idref="sshd_use_approved_ciphers" selected="true" />
    <ns0:select idref="enable_selinux_bootloader" selected="true" />
    <ns0:select idref="selinux_state" selected="true" />
    <ns0:select idref="selinux_policytype" selected="true" />
    <ns0:select idref="service_rdisc_disabled" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_secure_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_secure_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_rp_filter" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_rp_filter" selected="true" />
    <ns0:select idref="service_firewalld_enabled" selected="true" />
    <ns0:select idref="audit_rules_immutable" selected="true" />
    <ns0:select idref="service_oddjobd_disabled" selected="true" />
    <ns0:select idref="rpm_verify_permissions" selected="true" />
    <ns0:select idref="file_permissions_var_log_audit" selected="true" />
    <ns0:select idref="file_ownership_var_log_audit" selected="true" />
    <ns0:select idref="userowner_shadow_file" selected="true" />
    <ns0:select idref="groupowner_shadow_file" selected="true" />
    <ns0:select idref="file_permissions_etc_shadow" selected="true" />
    <ns0:select idref="file_owner_etc_group" selected="true" />
    <ns0:select idref="file_groupowner_etc_group" selected="true" />
    <ns0:select idref="file_permissions_etc_group" selected="true" />
    <ns0:select idref="file_owner_etc_gshadow" selected="true" />
    <ns0:select idref="file_groupowner_etc_gshadow" selected="true" />
    <ns0:select idref="file_permissions_etc_gshadow" selected="true" />
    <ns0:select idref="file_owner_etc_passwd" selected="true" />
    <ns0:select idref="file_groupowner_etc_passwd" selected="true" />
    <ns0:select idref="file_permissions_etc_passwd" selected="true" />
    <ns0:select idref="selinux_confinement_of_daemons" selected="true" />
    <ns0:select idref="file_ownership_library_dirs" selected="true" />
    <ns0:select idref="file_permissions_binary_dirs" selected="true" />
    <ns0:select idref="file_ownership_binary_dirs" selected="true" />
    <ns0:select idref="dir_perms_world_writable_sticky_bits" selected="true" />
    <ns0:select idref="file_permissions_unauthorized_world_writable" selected="true" />
    <ns0:select idref="no_files_unowned_by_user" selected="true" />
    <ns0:select idref="file_permissions_ungroupowned" selected="true" />
    <ns0:select idref="dir_perms_world_writable_system_owned" selected="true" />
    <ns0:select idref="accounts_no_uid_except_zero" selected="true" />
    <ns0:select idref="rsyslog_files_ownership" selected="true" />
    <ns0:select idref="rsyslog_files_groupownership" selected="true" />
    <ns0:select idref="securetty_root_login_console_only" selected="true" />
    <ns0:select idref="restrict_serial_port_logins" selected="true" />
    <ns0:select idref="sshd_disable_root_login" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_deny" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_interval" selected="true" />
    <ns0:select idref="accounts_passwords_pam_faillock_unlock_time" selected="true" />
    <ns0:select idref="banner_etc_issue" selected="true" />
    <ns0:select idref="dconf_gnome_banner_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_login_banner_text" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_idle_delay" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_idle_activation_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_lock_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_mode_blank" selected="true" />
    <ns0:select idref="service_auditd_enabled" selected="true" />
    <ns0:select idref="bootloader_audit_argument" selected="true" />
    <ns0:select idref="audit_rules_time_adjtimex" selected="true" />
    <ns0:select idref="audit_rules_time_settimeofday" selected="true" />
    <ns0:select idref="audit_rules_time_stime" selected="true" />
    <ns0:select idref="audit_rules_time_clock_settime" selected="true" />
    <ns0:select idref="audit_rules_time_watch_localtime" selected="true" />
    <ns0:select idref="audit_rules_networkconfig_modification" selected="true" />
    <ns0:select idref="audit_rules_mac_modification" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmodat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchownat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_removexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_setxattr" selected="true" />
    <ns0:select idref="audit_rules_login_events" selected="true" />
    <ns0:select idref="audit_rules_session_events" selected="true" />
    <ns0:select idref="audit_rules_unsuccessful_file_modification" selected="true" />
    <ns0:select idref="audit_rules_privileged_commands" selected="true" />
    <ns0:select idref="audit_rules_media_export" selected="true" />
    <ns0:select idref="audit_rules_file_deletion_events" selected="true" />
    <ns0:select idref="audit_rules_kernel_module_loading" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_log_martians" selected="true" />
    <ns0:select idref="service_xinetd_disabled" selected="true" />
    <ns0:select idref="package_xinetd_removed" selected="true" />
    <ns0:select idref="service_telnet_disabled" selected="true" />
    <ns0:select idref="package_telnet-server_removed" selected="true" />
    <ns0:select idref="package_rsh_removed" selected="true" />
    <ns0:select idref="service_rexec_disabled" selected="true" />
    <ns0:select idref="service_rsh_disabled" selected="true" />
    <ns0:select idref="service_rlogin_disabled" selected="true" />
    <ns0:select idref="no_rsh_trust_files" selected="true" />
    <ns0:select idref="package_ypserv_removed" selected="true" />
    <ns0:select idref="service_ypbind_disabled" selected="true" />
    <ns0:select idref="service_tftp_disabled" selected="true" />
    <ns0:select idref="package_tftp_removed" selected="true" />
    <ns0:select idref="tftpd_uses_secure_mode" selected="true" />
    <ns0:select idref="service_abrtd_disabled" selected="true" />
    <ns0:select idref="service_kdump_disabled" selected="true" />
    <ns0:select idref="service_netconsole_disabled" selected="true" />
    <ns0:select idref="service_ntpdate_disabled" selected="true" />
    <ns0:select idref="service_portreserve_disabled" selected="true" />
    <ns0:select idref="service_qpidd_disabled" selected="true" />
    <ns0:select idref="service_rhnsd_disabled" selected="true" />
    <ns0:select idref="service_saslauthd_disabled" selected="true" />
    <ns0:select idref="sshd_allow_only_protocol2" selected="true" />
    <ns0:select idref="wireless_disable_in_bios" selected="true" />
    <ns0:select idref="wireless_disable_interfaces" selected="true" />
    <ns0:select idref="service_bluetooth_disabled" selected="true" />
    <ns0:select idref="kernel_module_bluetooth_disabled" selected="true" />
    <ns0:select idref="mount_option_nodev_removable_partitions" selected="true" />
    <ns0:select idref="mount_option_noexec_removable_partitions" selected="true" />
    <ns0:select idref="mount_option_nosuid_removable_partitions" selected="true" />
    <ns0:select idref="kernel_module_usb-storage_disabled" selected="true" />
    <ns0:select idref="bootloader_nousb_argument" selected="true" />
    <ns0:select idref="bios_disable_usb_boot" selected="true" />
    <ns0:select idref="service_autofs_disabled" selected="true" />
    <ns0:select idref="dconf_gnome_disable_automount" selected="true" />
    <ns0:select idref="auditd_data_retention_num_logs" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file_action" selected="true" />
    <ns0:select idref="auditd_data_retention_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_admin_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_action_mail_acct" selected="true" />
    <ns0:select idref="auditd_audispd_syslog_plugin_activated" selected="true" />
    <ns0:select idref="rsyslog_remote_loghost" selected="true" />
    <ns0:select idref="service_chronyd_or_ntpd_enabled" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_remote_server" selected="true" />
    <ns0:select idref="chronyd_or_ntpd_specify_multiple_servers" selected="true" />
    <ns0:select idref="service_psacct_enabled" selected="true" />
    <ns0:select idref="package_aide_installed" selected="true" />
    <ns0:select idref="disable_prelink" selected="true" />
    <ns0:select idref="aide_build_database" selected="true" />
    <ns0:select idref="aide_periodic_cron_checking" selected="true" />
    <ns0:select idref="rpm_verify_hashes" selected="true" />
    <ns0:select idref="sysctl_kernel_ipv6_disable" selected="true" />
    <ns0:select idref="network_ipv6_disable_rpc" selected="true" />
    <ns0:select idref="sysctl_net_ipv6_conf_default_accept_ra" selected="true" />
    <ns0:select idref="sysctl_net_ipv6_conf_default_accept_redirects" selected="true" />
    <ns0:select idref="network_disable_zeroconf" selected="true" />
    <ns0:select idref="network_sniffer_disabled" selected="true" />
    <ns0:select idref="kernel_module_dccp_disabled" selected="true" />
    <ns0:select idref="kernel_module_sctp_disabled" selected="true" />
    <ns0:select idref="set_firewalld_default_zone" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_ip_forward" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_icmp_ignore_bogus_error_responses" selected="true" />
    <ns0:select idref="kernel_module_cramfs_disabled" selected="true" />
    <ns0:select idref="kernel_module_freevxfs_disabled" selected="true" />
    <ns0:select idref="kernel_module_jffs2_disabled" selected="true" />
    <ns0:select idref="kernel_module_hfs_disabled" selected="true" />
    <ns0:select idref="kernel_module_hfsplus_disabled" selected="true" />
    <ns0:select idref="kernel_module_squashfs_disabled" selected="true" />
    <ns0:select idref="kernel_module_udf_disabled" selected="true" />
    <ns0:select idref="dconf_gnome_disable_thumbnailers" selected="true" />
    <ns0:select idref="mount_option_nodev_nonroot_local_partitions" selected="true" />
    <ns0:select idref="mount_option_tmp_nodev" selected="true" />
    <ns0:select idref="mount_option_tmp_noexec" selected="true" />
    <ns0:select idref="mount_option_tmp_nosuid" selected="true" />
    <ns0:select idref="mount_option_dev_shm_nodev" selected="true" />
    <ns0:select idref="mount_option_dev_shm_noexec" selected="true" />
    <ns0:select idref="mount_option_dev_shm_nosuid" selected="true" />
    <ns0:select idref="mount_option_var_tmp_bind" selected="true" />
    <ns0:select idref="service_cups_disabled" selected="true" />
    <ns0:select idref="cups_disable_browsing" selected="true" />
    <ns0:select idref="cups_disable_printserver" selected="true" />
    <ns0:select idref="service_dhcpd_disabled" selected="true" />
    <ns0:select idref="package_dhcp_removed" selected="true" />
    <ns0:select idref="sysconfig_networking_bootproto_ifcfg" selected="true" />
    <ns0:select idref="service_avahi-daemon_disabled" selected="true" />
    <ns0:select idref="service_crond_enabled" selected="true" />
    <ns0:select idref="service_named_disabled" selected="true" />
    <ns0:select idref="package_bind_removed" selected="true" />
    <ns0:select idref="package_openldap-servers_removed" selected="true" />
    <ns0:select idref="package_sendmail_removed" selected="true" />
    <ns0:select idref="service_acpid_disabled" selected="true" />
    <ns0:select idref="service_atd_disabled" selected="true" />
    <ns0:select idref="service_certmonger_disabled" selected="true" />
    <ns0:select idref="service_cgconfig_disabled" selected="true" />
    <ns0:select idref="service_cgred_disabled" selected="true" />
    <ns0:select idref="service_cpupower_disabled" selected="true" />
    <ns0:select idref="service_irqbalance_enabled" selected="true" />
    <ns0:select idref="service_mdmonitor_disabled" selected="true" />
    <ns0:select idref="service_messagebus_disabled" selected="true" />
    <ns0:select idref="service_quota_nld_disabled" selected="true" />
    <ns0:select idref="service_rhsmcertd_disabled" selected="true" />
    <ns0:select idref="service_smartd_disabled" selected="true" />
    <ns0:select idref="service_sysstat_disabled" selected="true" />
    <ns0:select idref="service_httpd_disabled" selected="true" />
    <ns0:select idref="package_httpd_removed" selected="true" />
    <ns0:select idref="service_vsftpd_disabled" selected="true" />
    <ns0:select idref="package_vsftpd_removed" selected="true" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="updating" selected="false" />
    <ns0:select idref="endpoint_security_software" selected="false" />
    <ns0:select idref="mcafee_security_software" selected="false" />
    <ns0:select idref="mcafee_hbss_software" selected="false" />
    <ns0:select idref="fips" selected="false" />
    <ns0:select idref="certified-vendor" selected="false" />
    <ns0:select idref="gnome_login_screen" selected="false" />
    <ns0:select idref="gnome_system_settings" selected="false" />
    <ns0:select idref="gnome_network_settings" selected="false" />
    <ns0:select idref="gnome_remote_access_settings" selected="false" />
    <ns0:select idref="sudo" selected="false" />
    <ns0:select idref="restrictions" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="coredumps" selected="false" />
    <ns0:select idref="enable_execshield_settings" selected="false" />
    <ns0:select idref="enable_nx" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="password_storage" selected="false" />
    <ns0:select idref="password_expiration" selected="false" />
    <ns0:select idref="password_quality" selected="false" />
    <ns0:select idref="password_quality_pwquality" selected="false" />
    <ns0:select idref="set_password_hashing_algorithm" selected="false" />
    <ns0:select idref="accounts-session" selected="false" />
    <ns0:select idref="root_paths" selected="false" />
    <ns0:select idref="user_umask" selected="false" />
    <ns0:select idref="accounts-physical" selected="false" />
    <ns0:select idref="bootloader" selected="false" />
    <ns0:select idref="screen_locking" selected="false" />
    <ns0:select idref="console_screen_locking" selected="false" />
    <ns0:select idref="smart_card_login" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-ipsec" selected="false" />
    <ns0:select idref="rsyslog_accepting_remote_messages" selected="false" />
    <ns0:select idref="log_rotation" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="talk" selected="false" />
    <ns0:select idref="restrict_at_cron_users" selected="false" />
    <ns0:select idref="docker" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="sssd" selected="false" />
    <ns0:select idref="xwindows" selected="false" />
    <ns0:select idref="disabling_xwindows" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="postfix_client" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="openldap_client" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="nfs_and_rpc" selected="false" />
    <ns0:select idref="disabling_nfs" selected="false" />
    <ns0:select idref="disabling_nfs_services" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="nfs_configuring_clients" selected="false" />
    <ns0:select idref="disabling_nfsd" selected="false" />
    <ns0:select idref="mounting_remote_filesystems" selected="false" />
    <ns0:select idref="nfs_configuring_servers" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_configure_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="imap" selected="false" />
    <ns0:select idref="disabling_dovecot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="routing" selected="false" />
    <ns0:select idref="disabling_quagga" selected="false" />
    <ns0:select idref="smb" selected="false" />
    <ns0:select idref="disabling_samba" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="proxy" selected="false" />
    <ns0:select idref="disabling_squid" selected="false" />
    <ns0:select idref="snmp" selected="false" />
    <ns0:select idref="disabling_snmp_service" selected="false" />
    <ns0:select idref="snmp_configure_server" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
    <ns0:refine-value idref="var_account_disable_post_pw_expiration" selector="40" />
    <ns0:refine-value idref="var_selinux_state" selector="enforcing" />
    <ns0:refine-value idref="var_selinux_policy_name" selector="targeted" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_secure_redirects_value" selector="enabled" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_deny" selector="3" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_fail_interval" selector="900" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_unlock_time" selector="900" />
    <ns0:refine-value idref="inactivity_timeout_value" selector="15_minutes" />
    <ns0:refine-value idref="login_banner_text" selector="usgcb_default" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_accept_source_route_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_accept_redirects_value" selector="disabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_all_log_martians_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_conf_default_secure_redirects_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value" selector="enabled" />
    <ns0:refine-value idref="sysctl_net_ipv4_icmp_ignore_bogus_error_responses_value" selector="enabled" />
  </ns0:Profile>
  <ns0:Profile id="cjis-rhel7-server">
    <ns0:title xml:lang="en-US">Criminal Justice Information Services (CJIS) Security Policy</ns0:title>
    <ns0:description override="true" xml:lang="en-US">This is a *draft* profile for CJIS v5.4. The scope of this profile is to configure Red Hat Enteprise Linux 7 against the U. S. Department of Justice, FBI CJIS Security Policy.
</ns0:description>
    <ns0:select idref="service_auditd_enabled" selected="true" />
    <ns0:select idref="bootloader_audit_argument" selected="true" />
    <ns0:select idref="auditd_data_retention_num_logs" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file" selected="true" />
    <ns0:select idref="auditd_data_retention_max_log_file_action" selected="true" />
    <ns0:select idref="auditd_data_retention_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_admin_space_left_action" selected="true" />
    <ns0:select idref="auditd_data_retention_action_mail_acct" selected="true" />
    <ns0:select idref="auditd_audispd_syslog_plugin_activated" selected="true" />
    <ns0:select idref="audit_rules_time_adjtimex" selected="true" />
    <ns0:select idref="audit_rules_time_settimeofday" selected="true" />
    <ns0:select idref="audit_rules_time_stime" selected="true" />
    <ns0:select idref="audit_rules_time_clock_settime" selected="true" />
    <ns0:select idref="audit_rules_time_watch_localtime" selected="true" />
    <ns0:select idref="audit_rules_usergroup_modification" selected="true" />
    <ns0:select idref="audit_rules_networkconfig_modification" selected="true" />
    <ns0:select idref="file_permissions_var_log_audit" selected="true" />
    <ns0:select idref="file_ownership_var_log_audit" selected="true" />
    <ns0:select idref="audit_rules_mac_modification" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_chown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmod" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchmodat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fchownat" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_fsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lchown" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lremovexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_lsetxattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_removexattr" selected="true" />
    <ns0:select idref="audit_rules_dac_modification_setxattr" selected="true" />
    <ns0:select idref="audit_rules_login_events" selected="true" />
    <ns0:select idref="audit_rules_session_events" selected="true" />
    <ns0:select idref="audit_rules_unsuccessful_file_modification" selected="true" />
    <ns0:select idref="audit_rules_privileged_commands" selected="true" />
    <ns0:select idref="audit_rules_media_export" selected="true" />
    <ns0:select idref="audit_rules_file_deletion_events" selected="true" />
    <ns0:select idref="audit_rules_sysadmin_actions" selected="true" />
    <ns0:select idref="audit_rules_kernel_module_loading" selected="true" />
    <ns0:select idref="audit_rules_immutable" selected="true" />
    <ns0:select idref="account_unique_name" selected="true" />
    <ns0:select idref="gid_passwd_group_same" selected="true" />
    <ns0:select idref="accounts_password_all_shadowed" selected="true" />
    <ns0:select idref="no_empty_passwords" selected="true" />
    <ns0:select idref="display_login_attempts" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_systemauth" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_logindefs" selected="true" />
    <ns0:select idref="set_password_hashing_algorithm_libuserconf" selected="true" />
    <ns0:select idref="userowner_shadow_file" selected="true" />
    <ns0:select idref="groupowner_shadow_file" selected="true" />
    <ns0:select idref="file_permissions_etc_shadow" selected="true" />
    <ns0:select idref="file_owner_etc_group" selected="true" />
    <ns0:select idref="file_groupowner_etc_group" selected="true" />
    <ns0:select idref="file_permissions_etc_group" selected="true" />
    <ns0:select idref="file_owner_etc_passwd" selected="true" />
    <ns0:select idref="file_groupowner_etc_passwd" selected="true" />
    <ns0:select idref="file_permissions_etc_passwd" selected="true" />
    <ns0:select idref="file_user_owner_grub2_cfg" selected="true" />
    <ns0:select idref="file_group_owner_grub2_cfg" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_idle_delay" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_idle_activation_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_lock_enabled" selected="true" />
    <ns0:select idref="dconf_gnome_screensaver_mode_blank" selected="true" />
    <ns0:select idref="sshd_allow_only_protocol2" selected="true" />
    <ns0:select idref="sshd_set_idle_timeout" selected="true" />
    <ns0:select idref="sshd_set_keepalive" selected="true" />
    <ns0:select idref="sshd_disable_rhosts" selected="true" />
    <ns0:select idref="disable_host_auth" selected="true" />
    <ns0:select idref="sshd_disable_root_login" selected="true" />
    <ns0:select idref="sshd_disable_empty_passwords" selected="true" />
    <ns0:select idref="sshd_enable_warning_banner" selected="true" />
    <ns0:select idref="sshd_do_not_permit_user_env" selected="true" />
    <ns0:select idref="sshd_use_approved_ciphers" selected="true" />
    <ns0:select idref="kernel_module_dccp_disabled" selected="true" />
    <ns0:select idref="kernel_module_sctp_disabled" selected="true" />
    <ns0:select idref="service_firewalld_enabled" selected="true" />
    <ns0:select idref="set_firewalld_default_zone" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_source_route" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_tcp_syncookies" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_send_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_all_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_conf_default_accept_redirects" selected="true" />
    <ns0:select idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts" selected="true" />
    <ns0:select idref="package_aide_installed" selected="true" />
    <ns0:select idref="disable_prelink" selected="true" />
    <ns0:select idref="aide_build_database" selected="true" />
    <ns0:select idref="aide_periodic_cron_checking" selected="true" />
    <ns0:select idref="rpm_verify_permissions" selected="true" />
    <ns0:select idref="rpm_verify_hashes" selected="true" />
    <ns0:select idref="ensure_redhat_gpgkey_installed" selected="true" />
    <ns0:select idref="ensure_gpgcheck_globally_activated" selected="true" />
    <ns0:select idref="ensure_gpgcheck_never_disabled" selected="true" />
    <ns0:select idref="security_patches_up_to_date" selected="true" />
    <ns0:select idref="kernel_module_bluetooth_disabled" selected="true" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="disk_partitioning" selected="false" />
    <ns0:select idref="endpoint_security_software" selected="false" />
    <ns0:select idref="mcafee_security_software" selected="false" />
    <ns0:select idref="mcafee_hbss_software" selected="false" />
    <ns0:select idref="fips" selected="false" />
    <ns0:select idref="certified-vendor" selected="false" />
    <ns0:select idref="gnome_login_screen" selected="false" />
    <ns0:select idref="gnome_system_settings" selected="false" />
    <ns0:select idref="gnome_network_settings" selected="false" />
    <ns0:select idref="gnome_remote_access_settings" selected="false" />
    <ns0:select idref="gnome_media_settings" selected="false" />
    <ns0:select idref="sudo" selected="false" />
    <ns0:select idref="partitions" selected="false" />
    <ns0:select idref="mounting" selected="false" />
    <ns0:select idref="permissions_within_important_dirs" selected="false" />
    <ns0:select idref="restrictions" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="coredumps" selected="false" />
    <ns0:select idref="enable_execshield_settings" selected="false" />
    <ns0:select idref="enable_nx" selected="false" />
    <ns0:select idref="selinux" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="root_logins" selected="false" />
    <ns0:select idref="password_expiration" selected="false" />
    <ns0:select idref="password_quality" selected="false" />
    <ns0:select idref="password_quality_pwquality" selected="false" />
    <ns0:select idref="locking_out_password_attempts" selected="false" />
    <ns0:select idref="accounts-session" selected="false" />
    <ns0:select idref="root_paths" selected="false" />
    <ns0:select idref="user_umask" selected="false" />
    <ns0:select idref="screen_locking" selected="false" />
    <ns0:select idref="console_screen_locking" selected="false" />
    <ns0:select idref="smart_card_login" selected="false" />
    <ns0:select idref="accounts-banners" selected="false" />
    <ns0:select idref="gui_login_banner" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="network-ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6" selected="false" />
    <ns0:select idref="configuring_ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6_autoconfig" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-ipsec" selected="false" />
    <ns0:select idref="logging" selected="false" />
    <ns0:select idref="ensure_rsyslog_log_file_configuration" selected="false" />
    <ns0:select idref="rsyslog_sending_messages" selected="false" />
    <ns0:select idref="rsyslog_accepting_remote_messages" selected="false" />
    <ns0:select idref="log_rotation" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="obsolete" selected="false" />
    <ns0:select idref="inetd_and_xinetd" selected="false" />
    <ns0:select idref="telnet" selected="false" />
    <ns0:select idref="r_services" selected="false" />
    <ns0:select idref="nis" selected="false" />
    <ns0:select idref="tftp" selected="false" />
    <ns0:select idref="talk" selected="false" />
    <ns0:select idref="base" selected="false" />
    <ns0:select idref="cron_and_at" selected="false" />
    <ns0:select idref="restrict_at_cron_users" selected="false" />
    <ns0:select idref="docker" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="sssd" selected="false" />
    <ns0:select idref="xwindows" selected="false" />
    <ns0:select idref="disabling_xwindows" selected="false" />
    <ns0:select idref="avahi" selected="false" />
    <ns0:select idref="disable_avahi_group" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="printing" selected="false" />
    <ns0:select idref="configure_printing" selected="false" />
    <ns0:select idref="dhcp" selected="false" />
    <ns0:select idref="disabling_dhcp_server" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="disabling_dhcp_client" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="ntp" selected="false" />
    <ns0:select idref="mail" selected="false" />
    <ns0:select idref="postfix_client" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="ldap" selected="false" />
    <ns0:select idref="openldap_client" selected="false" />
    <ns0:select idref="openldap_server" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="nfs_and_rpc" selected="false" />
    <ns0:select idref="disabling_nfs" selected="false" />
    <ns0:select idref="disabling_nfs_services" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="nfs_configuring_clients" selected="false" />
    <ns0:select idref="disabling_nfsd" selected="false" />
    <ns0:select idref="mounting_remote_filesystems" selected="false" />
    <ns0:select idref="nfs_configuring_servers" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns" selected="false" />
    <ns0:select idref="disabling_dns_server" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp" selected="false" />
    <ns0:select idref="disabling_vsftpd" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_configure_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="http" selected="false" />
    <ns0:select idref="disabling_httpd" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="imap" selected="false" />
    <ns0:select idref="disabling_dovecot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="routing" selected="false" />
    <ns0:select idref="disabling_quagga" selected="false" />
    <ns0:select idref="smb" selected="false" />
    <ns0:select idref="disabling_samba" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="proxy" selected="false" />
    <ns0:select idref="disabling_squid" selected="false" />
    <ns0:select idref="snmp" selected="false" />
    <ns0:select idref="disabling_snmp_service" selected="false" />
    <ns0:select idref="snmp_configure_server" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
    <ns0:refine-value idref="var_accounts_password_minlen_login_defs" selector="8" />
    <ns0:refine-value idref="var_accounts_maximum_age_login_defs" selector="90" />
    <ns0:refine-value idref="var_password_pam_unix_remember" selector="10" />
    <ns0:refine-value idref="var_password_pam_retry" selector="5" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_deny" selector="5" />
    <ns0:refine-value idref="var_accounts_passwords_pam_faillock_unlock_time" selector="600" />
    <ns0:refine-value idref="sshd_idle_timeout_value" selector="5_minutes" />
    <ns0:refine-value idref="var_password_pam_ocredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_dcredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_ucredit" selector="1" />
    <ns0:refine-value idref="var_password_pam_lcredit" selector="1" />
  </ns0:Profile>
  <ns0:Profile id="docker-host">
    <ns0:title xml:lang="en-US">Standard Docker Host Security Profile</ns0:title>
    <ns0:description xml:lang="en-US">This profile contains rules to ensure standard security baseline of Red Hat Enterprise Linux 7 system
  running the docker daemon. This discussion is currently being held on open-scap-list@redhat.com 
  and scap-security-guide@lists.fedorahosted.org.
</ns0:description>
    <ns0:select idref="service_docker_enabled" selected="true" />
    <ns0:select idref="enable_selinux_bootloader" selected="true" />
    <ns0:select idref="selinux_state" selected="true" />
    <ns0:select idref="selinux_policytype" selected="true" />
    <ns0:select idref="docker_selinux_enabled" selected="true" />
    <ns0:select idref="docker_storage_configured" selected="true" />
    <ns0:select idref="remediation_functions" selected="false" />
    <ns0:select idref="intro" selected="false" />
    <ns0:select idref="general-principles" selected="false" />
    <ns0:select idref="principle-encrypt-transmitted-data" selected="false" />
    <ns0:select idref="principle-minimize-software" selected="false" />
    <ns0:select idref="principle-separate-servers" selected="false" />
    <ns0:select idref="principle-use-security-tools" selected="false" />
    <ns0:select idref="principle-least-privilege" selected="false" />
    <ns0:select idref="how-to-use" selected="false" />
    <ns0:select idref="intro-read-sections-completely" selected="false" />
    <ns0:select idref="intro-test-non-production" selected="false" />
    <ns0:select idref="intro-root-shell-assumed" selected="false" />
    <ns0:select idref="intro-formatting-conventions" selected="false" />
    <ns0:select idref="intro-reboot-required" selected="false" />
    <ns0:select idref="software" selected="false" />
    <ns0:select idref="disk_partitioning" selected="false" />
    <ns0:select idref="updating" selected="false" />
    <ns0:select idref="integrity" selected="false" />
    <ns0:select idref="software-integrity" selected="false" />
    <ns0:select idref="aide" selected="false" />
    <ns0:select idref="rpm_verification" selected="false" />
    <ns0:select idref="endpoint_security_software" selected="false" />
    <ns0:select idref="mcafee_security_software" selected="false" />
    <ns0:select idref="mcafee_hbss_software" selected="false" />
    <ns0:select idref="fips" selected="false" />
    <ns0:select idref="certified-vendor" selected="false" />
    <ns0:select idref="gnome" selected="false" />
    <ns0:select idref="gnome_login_screen" selected="false" />
    <ns0:select idref="gnome_screen_locking" selected="false" />
    <ns0:select idref="gnome_system_settings" selected="false" />
    <ns0:select idref="gnome_network_settings" selected="false" />
    <ns0:select idref="gnome_remote_access_settings" selected="false" />
    <ns0:select idref="gnome_media_settings" selected="false" />
    <ns0:select idref="sudo" selected="false" />
    <ns0:select idref="permissions" selected="false" />
    <ns0:select idref="partitions" selected="false" />
    <ns0:select idref="mounting" selected="false" />
    <ns0:select idref="files" selected="false" />
    <ns0:select idref="permissions_important_account_files" selected="false" />
    <ns0:select idref="permissions_within_important_dirs" selected="false" />
    <ns0:select idref="restrictions" selected="false" />
    <ns0:select idref="daemon_umask" selected="false" />
    <ns0:select idref="coredumps" selected="false" />
    <ns0:select idref="enable_execshield_settings" selected="false" />
    <ns0:select idref="enable_nx" selected="false" />
    <ns0:select idref="selinux-booleans" selected="false" />
    <ns0:select idref="accounts" selected="false" />
    <ns0:select idref="accounts-restrictions" selected="false" />
    <ns0:select idref="root_logins" selected="false" />
    <ns0:select idref="password_storage" selected="false" />
    <ns0:select idref="password_expiration" selected="false" />
    <ns0:select idref="account_expiration" selected="false" />
    <ns0:select idref="accounts-pam" selected="false" />
    <ns0:select idref="password_quality" selected="false" />
    <ns0:select idref="password_quality_pwquality" selected="false" />
    <ns0:select idref="locking_out_password_attempts" selected="false" />
    <ns0:select idref="set_password_hashing_algorithm" selected="false" />
    <ns0:select idref="accounts-session" selected="false" />
    <ns0:select idref="root_paths" selected="false" />
    <ns0:select idref="user_umask" selected="false" />
    <ns0:select idref="accounts-physical" selected="false" />
    <ns0:select idref="bootloader" selected="false" />
    <ns0:select idref="screen_locking" selected="false" />
    <ns0:select idref="console_screen_locking" selected="false" />
    <ns0:select idref="smart_card_login" selected="false" />
    <ns0:select idref="accounts-banners" selected="false" />
    <ns0:select idref="gui_login_banner" selected="false" />
    <ns0:select idref="network" selected="false" />
    <ns0:select idref="network_disable_unused_interfaces" selected="false" />
    <ns0:select idref="network-kernel" selected="false" />
    <ns0:select idref="network_host_parameters" selected="false" />
    <ns0:select idref="network_host_and_router_parameters" selected="false" />
    <ns0:select idref="network-wireless" selected="false" />
    <ns0:select idref="wireless_software" selected="false" />
    <ns0:select idref="network-ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6" selected="false" />
    <ns0:select idref="configuring_ipv6" selected="false" />
    <ns0:select idref="disabling_ipv6_autoconfig" selected="false" />
    <ns0:select idref="network_ipv6_limit_requests" selected="false" />
    <ns0:select idref="network-firewalld" selected="false" />
    <ns0:select idref="firewalld_activation" selected="false" />
    <ns0:select idref="ruleset_modifications" selected="false" />
    <ns0:select idref="network_ssl" selected="false" />
    <ns0:select idref="network-uncommon" selected="false" />
    <ns0:select idref="network-ipsec" selected="false" />
    <ns0:select idref="logging" selected="false" />
    <ns0:select idref="ensure_rsyslog_log_file_configuration" selected="false" />
    <ns0:select idref="rsyslog_sending_messages" selected="false" />
    <ns0:select idref="rsyslog_accepting_remote_messages" selected="false" />
    <ns0:select idref="log_rotation" selected="false" />
    <ns0:select idref="configure_logwatch_on_logserver" selected="false" />
    <ns0:select idref="auditing" selected="false" />
    <ns0:select idref="configure_auditd_data_retention" selected="false" />
    <ns0:select idref="auditd_configure_rules" selected="false" />
    <ns0:select idref="audit_time_rules" selected="false" />
    <ns0:select idref="audit_dac_actions" selected="false" />
    <ns0:select idref="obsolete" selected="false" />
    <ns0:select idref="inetd_and_xinetd" selected="false" />
    <ns0:select idref="telnet" selected="false" />
    <ns0:select idref="r_services" selected="false" />
    <ns0:select idref="nis" selected="false" />
    <ns0:select idref="tftp" selected="false" />
    <ns0:select idref="talk" selected="false" />
    <ns0:select idref="base" selected="false" />
    <ns0:select idref="cron_and_at" selected="false" />
    <ns0:select idref="restrict_at_cron_users" selected="false" />
    <ns0:select idref="ssh" selected="false" />
    <ns0:select idref="ssh_server" selected="false" />
    <ns0:select idref="sshd_strengthen_firewall" selected="false" />
    <ns0:select idref="sssd" selected="false" />
    <ns0:select idref="xwindows" selected="false" />
    <ns0:select idref="disabling_xwindows" selected="false" />
    <ns0:select idref="avahi" selected="false" />
    <ns0:select idref="disable_avahi_group" selected="false" />
    <ns0:select idref="avahi_configuration" selected="false" />
    <ns0:select idref="printing" selected="false" />
    <ns0:select idref="configure_printing" selected="false" />
    <ns0:select idref="dhcp" selected="false" />
    <ns0:select idref="disabling_dhcp_server" selected="false" />
    <ns0:select idref="dhcp_server_configuration" selected="false" />
    <ns0:select idref="dhcp_server_minimize_served_info" selected="false" />
    <ns0:select idref="disabling_dhcp_client" selected="false" />
    <ns0:select idref="dhcp_client_configuration" selected="false" />
    <ns0:select idref="dhcp_client_restrict_options" selected="false" />
    <ns0:select idref="ntp" selected="false" />
    <ns0:select idref="mail" selected="false" />
    <ns0:select idref="postfix_client" selected="false" />
    <ns0:select idref="postfix_harden_os" selected="false" />
    <ns0:select idref="postfix_configure_ssl_certs" selected="false" />
    <ns0:select idref="postfix_install_ssl_cert" selected="false" />
    <ns0:select idref="postfix_server_configuration" selected="false" />
    <ns0:select idref="postfix_server_denial_of_service" selected="false" />
    <ns0:select idref="postfix_server_mail_relay" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_set_trusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_relay_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_smtpd_recipient_restrictions" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_smtp_auth_for_untrusted_networks" selected="false" />
    <ns0:select idref="postfix_server_mail_relay_require_tls_for_smtp_auth" selected="false" />
    <ns0:select idref="ldap" selected="false" />
    <ns0:select idref="openldap_client" selected="false" />
    <ns0:select idref="openldap_server" selected="false" />
    <ns0:select idref="ldap_server_config_certificate_files" selected="false" />
    <ns0:select idref="nfs_and_rpc" selected="false" />
    <ns0:select idref="disabling_nfs" selected="false" />
    <ns0:select idref="disabling_nfs_services" selected="false" />
    <ns0:select idref="nfs_configuring_all_machines" selected="false" />
    <ns0:select idref="nfs_client_or_server_not_both" selected="false" />
    <ns0:select idref="nfs_configure_fixed_ports" selected="false" />
    <ns0:select idref="nfs_configuring_clients" selected="false" />
    <ns0:select idref="disabling_nfsd" selected="false" />
    <ns0:select idref="mounting_remote_filesystems" selected="false" />
    <ns0:select idref="nfs_configuring_servers" selected="false" />
    <ns0:select idref="configure_exports_restrictively" selected="false" />
    <ns0:select idref="use_acl_enforce_auth_restrictions" selected="false" />
    <ns0:select idref="export_filesystems_read_only" selected="false" />
    <ns0:select idref="dns" selected="false" />
    <ns0:select idref="disabling_dns_server" selected="false" />
    <ns0:select idref="dns_server_isolation" selected="false" />
    <ns0:select idref="dns_server_dedicated" selected="false" />
    <ns0:select idref="dns_server_chroot" selected="false" />
    <ns0:select idref="dns_server_protection" selected="false" />
    <ns0:select idref="dns_server_separate_internal_external" selected="false" />
    <ns0:select idref="dns_server_partition_with_views" selected="false" />
    <ns0:select idref="ftp" selected="false" />
    <ns0:select idref="disabling_vsftpd" selected="false" />
    <ns0:select idref="ftp_use_vsftpd" selected="false" />
    <ns0:select idref="ftp_configure_vsftpd" selected="false" />
    <ns0:select idref="ftp_restrict_users" selected="false" />
    <ns0:select idref="ftp_limit_users" selected="false" />
    <ns0:select idref="ftp_configure_firewall" selected="false" />
    <ns0:select idref="http" selected="false" />
    <ns0:select idref="disabling_httpd" selected="false" />
    <ns0:select idref="installing_httpd" selected="false" />
    <ns0:select idref="httpd_minimal_modules_installed" selected="false" />
    <ns0:select idref="securing_httpd" selected="false" />
    <ns0:select idref="httpd_restrict_info_leakage" selected="false" />
    <ns0:select idref="httpd_minimize_loadable_modules" selected="false" />
    <ns0:select idref="httpd_core_modules" selected="false" />
    <ns0:select idref="httpd_basic_authentication" selected="false" />
    <ns0:select idref="httpd_optional_components" selected="false" />
    <ns0:select idref="httpd_minimize_config_files_included" selected="false" />
    <ns0:select idref="httpd_directory_restrictions" selected="false" />
    <ns0:select idref="httpd_modules_improve_security" selected="false" />
    <ns0:select idref="httpd_deploy_mod_ssl" selected="false" />
    <ns0:select idref="httpd_deploy_mod_security" selected="false" />
    <ns0:select idref="httpd_use_dos_protection_modules" selected="false" />
    <ns0:select idref="httpd_configure_php_securely" selected="false" />
    <ns0:select idref="httpd_configure_os_protect_web_server" selected="false" />
    <ns0:select idref="httpd_restrict_file_dir_access" selected="false" />
    <ns0:select idref="httpd_configure_firewalld" selected="false" />
    <ns0:select idref="httpd_chroot" selected="false" />
    <ns0:select idref="imap" selected="false" />
    <ns0:select idref="disabling_dovecot" selected="false" />
    <ns0:select idref="configure_dovecot" selected="false" />
    <ns0:select idref="dovecot_support_necessary_protocols" selected="false" />
    <ns0:select idref="dovecot_enabling_ssl" selected="false" />
    <ns0:select idref="dovecot_allow_imap_access" selected="false" />
    <ns0:select idref="routing" selected="false" />
    <ns0:select idref="disabling_quagga" selected="false" />
    <ns0:select idref="smb" selected="false" />
    <ns0:select idref="disabling_samba" selected="false" />
    <ns0:select idref="configuring_samba" selected="false" />
    <ns0:select idref="smb_restrict_file_sharing" selected="false" />
    <ns0:select idref="smb_disable_printing" selected="false" />
    <ns0:select idref="proxy" selected="false" />
    <ns0:select idref="disabling_squid" selected="false" />
    <ns0:select idref="snmp" selected="false" />
    <ns0:select idref="disabling_snmp_service" selected="false" />
    <ns0:select idref="snmp_configure_server" selected="false" />
    <ns0:select idref="srg_support" selected="false" />
    <ns0:select idref="c2s_support" selected="false" />
    <ns0:refine-value idref="var_selinux_policy_name" selector="targeted" />
    <ns0:refine-value idref="var_selinux_state" selector="enforcing" />
  </ns0:Profile>
  <ns0:Group id="remediation_functions">
    <ns0:title xml:lang="en-US">Remediation functions used by the SCAP Security Guide Project</ns0:title>
    <ns0:description xml:lang="en-US">XCCDF form of the various remediation functions as used by
remediation scripts from the SCAP Security Guide Project</ns0:description>
    <ns0:Value hidden="true" id="function_fix_audit_syscall_rule" operator="equals" prohibitChanges="true" type="string">
      <ns0:title xml:lang="en-US">Remediation function to fix syscall audit rule for given system call</ns0:title>
      <ns0:description xml:lang="en-US">Function to fix syscall audit rule for given system call. It is
based on example audit syscall rule definitions as outlined in
/usr/share/doc/audit-2.3.7/stig.rules file provided with the audit package. It
will combine multiple system calls belonging to the same syscall group into one
audit rule (rather than to create audit rule per different system call) to
avoid audit infrastructure performance penalty in the case of
'one-audit-rule-definition-per-one-system-call'. See:

	https://www.redhat.com/archives/linux-audit/2014-November/msg00009.html

for further details.

Expects five arguments (each of them is required) in the form of:
  * audit tool                          tool used to load audit rules,
                                        either 'auditctl', or 'augenrules
  * audit rules' pattern                audit rule skeleton for same syscall
  * syscall group                       greatest common string this rule shares
                                        with other rules from the same group
  * architecture                        architecture this rule is intended for
  * full form of new rule to add        expected full form of audit rule as to
                                        be added into audit.rules file

Note: The 2-th up to 4-th arguments are used to determine how many existing
audit rules will be inspected for resemblance with the new audit rule
(5-th argument) the function is going to add. The rule's similarity check
is performed to optimize audit.rules definition (merge syscalls of the same
group into one rule) to avoid the "single-syscall-per-audit-rule" performance
penalty.

Example call:

  PATTERN="-a always,exit -F arch=$ARCH -S .* -F auid&gt;=500 -F auid!=4294967295 -k delete"
  # Use escaped BRE regex to specify rule group
  GROUP="\(rmdir\|unlink\|rename\)"
  FULL_RULE="-a always,exit -F arch=$ARCH -S rmdir -S unlink -S unlinkat -S rename -S renameat -F auid&gt;=500 -F auid!=4294967295 -k delete"
  fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
</ns0:description>
      <ns0:value>
function fix_audit_syscall_rule {

# Load function arguments into local variables
local tool="$1"
local pattern="$2"
local group="$3"
local arch="$4"
local full_rule="$5"

# Check sanity of the input
if [ $# -ne "5" ]
then
        echo "Usage: fix_audit_syscall_rule 'tool' 'pattern' 'group' 'arch' 'full rule'"
        echo "Aborting."
        exit 1
fi

# Create a list of audit *.rules files that should be inspected for presence and correctness
# of a particular audit rule. The scheme is as follows:
#
# -----------------------------------------------------------------------------------------
#  Tool used to load audit rules | Rule already defined  |  Audit rules file to inspect    |
# -----------------------------------------------------------------------------------------
#        auditctl                |     Doesn't matter    |  /etc/audit/audit.rules         |
# -----------------------------------------------------------------------------------------
#        augenrules              |          Yes          |  /etc/audit/rules.d/*.rules     |
#        augenrules              |          No           |  /etc/audit/rules.d/$key.rules  |
# -----------------------------------------------------------------------------------------
#
declare -a files_to_inspect

# First check sanity of the specified audit tool
if [ "$tool" != 'auditctl' ] &amp;&amp; [ "$tool" != 'augenrules' ]
then
        echo "Unknown audit rules loading tool: $1. Aborting."
        echo "Use either 'auditctl' or 'augenrules'!"
        exit 1
# If audit tool is 'auditctl', then add '/etc/audit/audit.rules'
# file to the list of files to be inspected
elif [ "$tool" == 'auditctl' ]
then
        files_to_inspect=("${files_to_inspect[@]}" '/etc/audit/audit.rules' )
# If audit tool is 'augenrules', then check if the audit rule is defined
# If rule is defined, add '/etc/audit/rules.d/*.rules' to the list for inspection
# If rule isn't defined yet, add '/etc/audit/rules.d/$key.rules' to the list for inspection
elif [ "$tool" == 'augenrules' ]
then
        # Extract audit $key from audit rule so we can use it later
        key=$(expr "$full_rule" : '.*-k[[:space:]]\([^[:space:]]\+\)')
        # Check if particular audit rule is already defined
        IFS=$'\n' matches=($(sed -s -n -e "/${pattern}/!d" -e "/${arch}/!d" -e "/${group}/!d;F" /etc/audit/rules.d/*.rules))
        # Reset IFS back to default
        unset $IFS
        for match in "${matches[@]}"
        do
                files_to_inspect=("${files_to_inspect[@]}" "${match}")
        done
        # Case when particular rule isn't defined in /etc/audit/rules.d/*.rules yet
        if [ ${#files_to_inspect[@]} -eq "0" ]
        then
                files_to_inspect="/etc/audit/rules.d/$key.rules"
                if [ ! -e "$files_to_inspect" ]
                then
                        touch "$files_to_inspect"
                        chmod 0640 "$files_to_inspect"
                fi
        fi
fi

#
# Indicator that we want to append $full_rule into $audit_file by default
local append_expected_rule=0

for audit_file in "${files_to_inspect[@]}"
do

        # Filter existing $audit_file rules' definitions to select those that:
        # * follow the rule pattern, and
        # * meet the hardware architecture requirement, and
        # * are current syscall group specific
        IFS=$'\n' existing_rules=($(sed -e "/${pattern}/!d" -e "/${arch}/!d" -e "/${group}/!d"  "$audit_file"))
        # Reset IFS back to default
        unset $IFS

        # Process rules found case-by-case
        for rule in "${existing_rules[@]}"
        do
                # Found rule is for same arch &amp; key, but differs (e.g. in count of -S arguments)
                if [ "${rule}" != "${full_rule}" ]
                then
                        # If so, isolate just '(-S \w)+' substring of that rule
                        rule_syscalls=$(echo $rule | grep -o -P '(-S \w+ )+')
                        # Check if list of '-S syscall' arguments of that rule is subset
                        # of '-S syscall' list of expected $full_rule
                        if grep -q -- "$rule_syscalls" &lt;&lt;&lt; "$full_rule"
                        then
                                # Rule is covered (i.e. the list of -S syscalls for this rule is
                                # subset of -S syscalls of $full_rule =&gt; existing rule can be deleted
                                # Thus delete the rule from audit.rules &amp; our array
                                sed -i -e "/$rule/d" "$audit_file"
                                existing_rules=("${existing_rules[@]//$rule/}")
                        else
                                # Rule isn't covered by $full_rule - it besides -S syscall arguments
                                # for this group contains also -S syscall arguments for other syscall
                                # group. Example: '-S lchown -S fchmod -S fchownat' =&gt; group='chown'
                                # since 'lchown' &amp; 'fchownat' share 'chown' substring
                                # Therefore:
                                # * 1) delete the original rule from audit.rules
                                # (original '-S lchown -S fchmod -S fchownat' rule would be deleted)
                                # * 2) delete the -S syscall arguments for this syscall group, but
                                # keep those not belonging to this syscall group
                                # (original '-S lchown -S fchmod -S fchownat' would become '-S fchmod'
                                # * 3) append the modified (filtered) rule again into audit.rules
                                # if the same rule not already present
                                #
                                # 1) Delete the original rule
                                sed -i -e "/$rule/d" "$audit_file"
                                # 2) Delete syscalls for this group, but keep those from other groups
                                # Convert current rule syscall's string into array splitting by '-S' delimiter
                                IFS=$'-S' read -a rule_syscalls_as_array &lt;&lt;&lt; "$rule_syscalls"
                                # Reset IFS back to default
                                unset $IFS
                                # Declare new empty string to hold '-S syscall' arguments from other groups
                                new_syscalls_for_rule=''
                                # Walk through existing '-S syscall' arguments
                                for syscall_arg in "${rule_syscalls_as_array[@]}"
                                do
                                        # Skip empty $syscall_arg values
                                        if [ "$syscall_arg" == '' ]
                                        then
                                                continue
                                        fi
                                        # If the '-S syscall' doesn't belong to current group add it to the new list
                                        # (together with adding '-S' delimiter back for each of such item found)
                                        if grep -q -v -- "$group" &lt;&lt;&lt; "$syscall_arg"
                                        then
                                                new_syscalls_for_rule="$new_syscalls_for_rule -S $syscall_arg"
                                        fi
                                done
                                # Replace original '-S syscall' list with the new one for this rule
                                updated_rule=${rule//$rule_syscalls/$new_syscalls_for_rule}
                                # Squeeze repeated whitespace characters in rule definition (if any) into one
                                updated_rule=$(echo "$updated_rule" | tr -s '[:space:]')
                                # 3) Append the modified / filtered rule again into audit.rules
                                #    (but only in case it's not present yet to prevent duplicate definitions)
                                if ! grep -q -- "$updated_rule" "$audit_file"
                                then
                                        echo "$updated_rule" &gt;&gt; "$audit_file"
                                fi
                        fi
                else
                        # $audit_file already contains the expected rule form for this
                        # architecture &amp; key =&gt; don't insert it second time
                        append_expected_rule=1
                fi
        done

        # We deleted all rules that were subset of the expected one for this arch &amp; key.
        # Also isolated rules containing system calls not from this system calls group.
        # Now append the expected rule if it's not present in $audit_file yet
        if [[ ${append_expected_rule} -eq "0" ]]
        then
                echo "$full_rule" &gt;&gt; "$audit_file"
        fi
done

}
</ns0:value>
    </ns0:Value>
    <ns0:Value hidden="true" id="function_fix_audit_watch_rule" operator="equals" prohibitChanges="true" type="string">
      <ns0:title xml:lang="en-US">Remediation function to fix audit file system object watch rule for given path</ns0:title>
      <ns0:description xml:lang="en-US">Function to fix audit file system object watch rule for given path:
  * if rule exists, also verifies the -w bits match the requirements
  * if rule doesn't exist yet, appends expected rule form to $files_to_inspect
    audit rules file, depending on the tool which was used to load audit rules

Expects four arguments (each of them is required) in the form of:
  * audit tool                          tool used to load audit rules,
                                        either 'auditctl', or 'augenrules'
  * path                                value of -w audit rule's argument
  * required access bits                value of -p audit rule's argument
  * key                                 value of -k audit rule's argument

Example call:

  fix_audit_watch_rule "auditctl" "/etc/localtime" "wa" "audit_time_rules"
</ns0:description>
      <ns0:value>
function fix_audit_watch_rule {

# Load function arguments into local variables
local tool="$1"
local path="$2"
local required_access_bits="$3"
local key="$4"

# Check sanity of the input
if [ $# -ne "4" ]
then
        echo "Usage: fix_audit_watch_rule 'tool' 'path' 'bits' 'key'"
        echo "Aborting."
        exit 1
fi

# Create a list of audit *.rules files that should be inspected for presence and correctness
# of a particular audit rule. The scheme is as follows:
#
# -----------------------------------------------------------------------------------------
# Tool used to load audit rules | Rule already defined  |  Audit rules file to inspect    |
# -----------------------------------------------------------------------------------------
#       auditctl                |     Doesn't matter    |  /etc/audit/audit.rules         |
# -----------------------------------------------------------------------------------------
#       augenrules              |          Yes          |  /etc/audit/rules.d/*.rules     |
#       augenrules              |          No           |  /etc/audit/rules.d/$key.rules  |
# -----------------------------------------------------------------------------------------
declare -a files_to_inspect

# Check sanity of the specified audit tool
if [ "$tool" != 'auditctl' ] &amp;&amp; [ "$tool" != 'augenrules' ]
then
        echo "Unknown audit rules loading tool: $1. Aborting."
        echo "Use either 'auditctl' or 'augenrules'!"
        exit 1
# If the audit tool is 'auditctl', then add '/etc/audit/audit.rules'
# into the list of files to be inspected
elif [ "$tool" == 'auditctl' ]
then
        files_to_inspect=("${files_to_inspect[@]}" '/etc/audit/audit.rules')
# If the audit is 'augenrules', then check if rule is already defined
# If rule is defined, add '/etc/audit/rules.d/*.rules' to list of files for inspection.
# If rule isn't defined, add '/etc/audit/rules.d/$key.rules' to list of files for inspection.
elif [ "$tool" == 'augenrules' ]
then
        # Case when particular audit rule is already defined in some of /etc/audit/rules.d/*.rules file
        # Get pair -- filepath : matching_row into @matches array
        IFS=$'\n' matches=($(grep -P "[\s]*-w[\s]+$path" /etc/audit/rules.d/*.rules))
        # Reset IFS back to default
        unset $IFS
        # For each of the matched entries
        for match in "${matches[@]}"
        do
                # Extract filepath from the match
                rulesd_audit_file=$(echo $match | cut -f1 -d ':')
                # Append that path into list of files for inspection
                files_to_inspect=("${files_to_inspect[@]}" "$rulesd_audit_file")
        done
        # Case when particular audit rule isn't defined yet
        if [ ${#files_to_inspect[@]} -eq "0" ]
        then
                # Append '/etc/audit/rules.d/$key.rules' into list of files for inspection
                files_to_inspect="/etc/audit/rules.d/$key.rules"
                # If the $key.rules file doesn't exist yet, create it with correct permissions
                if [ ! -e "$files_to_inspect" ]
                then
                        touch "$files_to_inspect"
                        chmod 0640 "$files_to_inspect"
                fi
        fi
fi

# Finally perform the inspection and possible subsequent audit rule
# correction for each of the files previously identified for inspection
for audit_rules_file in "${files_to_inspect[@]}"
do

        # Check if audit watch file system object rule for given path already present
        if grep -q -P -- "[\s]*-w[\s]+$path" "$audit_rules_file"
        then
                # Rule is found =&gt; verify yet if existing rule definition contains
                # all of the required access type bits

                # Escape slashes in path for use in sed pattern below
                local esc_path=${path//$'/'/$'\/'}
                # Define BRE whitespace class shortcut
                local sp="[[:space:]]"
                # Extract current permission access types (e.g. -p [r|w|x|a] values) from audit rule
                current_access_bits=$(sed -ne "s/$sp*-w$sp\+$esc_path$sp\+-p$sp\+\([rxwa]\{1,4\}\).*/\1/p" "$audit_rules_file")
                # Split required access bits string into characters array
                # (to check bit's presence for one bit at a time)
                for access_bit in $(echo "$required_access_bits" | grep -o .)
                do
                        # For each from the required access bits (e.g. 'w', 'a') check
                        # if they are already present in current access bits for rule.
                        # If not, append that bit at the end
                        if ! grep -q "$access_bit" &lt;&lt;&lt; "$current_access_bits"
                        then
                                # Concatenate the existing mask with the missing bit
                                current_access_bits="$current_access_bits$access_bit"
                        fi
                done
                # Propagate the updated rule's access bits (original + the required
                # ones) back into the /etc/audit/audit.rules file for that rule
                sed -i "s/\($sp*-w$sp\+$esc_path$sp\+-p$sp\+\)\([rxwa]\{1,4\}\)\(.*\)/\1$current_access_bits\3/" "$audit_rules_file"
        else
                # Rule isn't present yet. Append it at the end of $audit_rules_file file
                # with proper key

                echo "-w $path -p $required_access_bits -k $key" &gt;&gt; "$audit_rules_file"
        fi
done
}
</ns0:value>
    </ns0:Value>
    <ns0:Value hidden="true" id="function_package_command" operator="equals" prohibitChanges="true" type="string">
      <ns0:title xml:lang="en-US">Remediation function to to install or uninstall packages on RHEL and Fedora systems</ns0:title>
      <ns0:description xml:lang="en-US">Function to install or uninstall packages on RHEL and Fedora systems.

Example Call(s):

  package_command install aide
  package_command remove telnet-server
</ns0:description>
      <ns0:value>
function package_command {

# Load function arguments into local variables
local package_operation=$1
local package=$2

# Check sanity of the input
if [ $# -ne "2" ]
then
  echo "Usage: package_command 'install/uninstall' 'rpm_package_name"
  echo "Aborting."
  exit 1
fi

# If dnf is installed, use dnf; otherwise, use yum
if [ -f "/usr/bin/dnf" ] ; then
  install_util="/usr/bin/dnf"
else
  install_util="/usr/bin/yum"
fi

if [ "$package_operation" != 'remove' ] ; then
  # If the rpm is not installed, install the rpm
  if ! /bin/rpm -q --quiet $package; then
    $install_util -y $package_operation $package
  fi
else
  # If the rpm is installed, uninstall the rpm
  if /bin/rpm -q --quiet $package; then
    $install_util -y $package_operation $package
  fi
fi

}
</ns0:value>
    </ns0:Value>
    <ns0:Value hidden="true" id="function_service_command" operator="equals" prohibitChanges="true" type="string">
      <ns0:title xml:lang="en-US">Remediation function to enable/disable and start/stop services on RHEL
and Fedora systems</ns0:title>
      <ns0:description xml:lang="en-US">Function to enable/disable and start/stop services on RHEL and
Fedora systems.

Example Call(s):

  service_command enable bluetooth
  service_command disable bluetooth.service

  Using xinetd:
  service_command disable rsh.socket xinetd=rsh
</ns0:description>
      <ns0:value>
function service_command {

# Load function arguments into local variables
local service_state=$1
local service=$2
local xinetd=$(echo $3 | cut -d'=' -f2)

# Check sanity of the input
if [ $# -lt "2" ]
then
  echo "Usage: service_command 'enable/disable' 'service_name.service'"
  echo
  echo "To enable or disable xinetd services add \'xinetd=service_name\'"
  echo "as the last argument"
  echo "Aborting."
  exit 1
fi

# If systemctl is installed, use systemctl command; otherwise, use the service/chkconfig commands
if [ -f "/usr/bin/systemctl" ] ; then
  service_util="/usr/bin/systemctl"
else
  service_util="/sbin/service"
  chkconfig_util="/sbin/chkconfig"
fi

# If disable is not specified in arg1, set variables to enable services.
# Otherwise, variables are to be set to disable services.
if [ "$service_state" != 'disable' ] ; then
  service_state="enable"
  service_operation="start"
  chkconfig_state="on"
else
  service_state="disable"
  service_operation="stop"
  chkconfig_state="off"
fi

# If chkconfig_util is not empty, use chkconfig/service commands.
if ! [ "x$chkconfig_util" = x ] ; then
  $service_util $service $service_operation
  $chkconfig_util --level 0123456 $service $chkconfig_state
else
  $service_util $service_operation $service
  $service_util $service_state $service
fi

# Test if local variable xinetd is empty using non-bashism.
# If empty, then xinetd is not being used.
if ! [ "x$xinetd" = x ] ; then
  grep -qi disable /etc/xinetd.d/$xinetd &amp;&amp; \

  if ! [ "$service_operation" != 'disable' ] ; then
    sed -i "s/disable.*/disable         = no/gI" /etc/xinetd.d/$xinetd
  else
    sed -i "s/disable.*/disable         = yes/gI" /etc/xinetd.d/$xinetd
  fi
fi

}
</ns0:value>
    </ns0:Value>
    <ns0:Value hidden="true" id="function_perform_audit_rules_privileged_commands_remediation" operator="equals" prohibitChanges="true" type="string">
      <ns0:title xml:lang="en-US">Remediation function to perform remediation for 'audit_rules_privileged_commands' rule</ns0:title>
      <ns0:description xml:lang="en-US">Function to perform remediation for 'audit_rules_privileged_commands' rule

Expects two arguments:

  audit_tool            tool used to load audit rules
                        One of 'auditctl' or 'augenrules'

  min_auid              Minimum original ID the user logged in with
                        '500' for RHEL-6 and before, '1000' for RHEL-7 and after.

Example Call(s):

  perform_audit_rules_privileged_commands_remediation "auditctl" "500"
  perform_audit_rules_privileged_commands_remediation "augenrules" "1000"
</ns0:description>
      <ns0:value>
function perform_audit_rules_privileged_commands_remediation {
#
# Load function arguments into local variables
local tool="$1"
local min_auid="$2"

# Check sanity of the input
if [ $# -ne "2" ]
then
        echo "Usage: perform_audit_rules_privileged_commands_remediation 'auditctl | augenrules' '500 | 1000'"
        echo "Aborting."
        exit 1
fi

declare -a files_to_inspect=()

# Check sanity of the specified audit tool
if [ "$tool" != 'auditctl' ] &amp;&amp; [ "$tool" != 'augenrules' ]
then
        echo "Unknown audit rules loading tool: $1. Aborting."
        echo "Use either 'auditctl' or 'augenrules'!"
        exit 1
# If the audit tool is 'auditctl', then:
# * add '/etc/audit/audit.rules'to the list of files to be inspected,
# * specify '/etc/audit/audit.rules' as the output audit file, where
#   missing rules should be inserted
elif [ "$tool" == 'auditctl' ]
then
        files_to_inspect=("/etc/audit/audit.rules")
        output_audit_file="/etc/audit/audit.rules"
#
# If the audit tool is 'augenrules', then:
# * add '/etc/audit/rules.d/*.rules' to the list of files to be inspected
#   (split by newline),
# * specify /etc/audit/rules.d/privileged.rules' as the output file, where
#   missing rules should be inserted
elif [ "$tool" == 'augenrules' ]
then
        IFS=$'\n' files_to_inspect=($(find /etc/audit/rules.d -maxdepth 1 -type f -name *.rules -print))
        output_audit_file="/etc/audit/rules.d/privileged.rules"
fi

# Obtain the list of SUID/SGID binaries on the particular system (split by newline)
# into privileged_binaries array
IFS=$'\n' privileged_binaries=($(find / -xdev -type f -perm -4000 -o -type f -perm -2000 2&gt;/dev/null))

# Keep list of SUID/SGID binaries that have been already handled within some previous iteration
declare -a sbinaries_to_skip=()

# For each found sbinary in privileged_binaries list
for sbinary in "${privileged_binaries[@]}"
do

        # Replace possible slash '/' character in sbinary definition so we could use it in sed expressions below
        sbinary_esc=${sbinary//$'/'/$'\/'}
        # Check if this sbinary wasn't already handled in some of the previous iterations
        # Return match only if whole sbinary definition matched (not in the case just prefix matched!!!)
        if [[ $(sed -ne "/${sbinary_esc}$/p" &lt;&lt;&lt; ${sbinaries_to_skip[@]}) ]]
        then
                # If so, don't process it second time &amp; go to process next sbinary
                continue
        fi

        # Reset the counter of inspected files when starting to check
        # presence of existing audit rule for new sbinary
        local count_of_inspected_files=0

        # For each audit rules file from the list of files to be inspected
        for afile in "${files_to_inspect[@]}"
        do

                # Search current audit rules file's content for match. Match criteria:
                # * existing rule is for the same SUID/SGID binary we are currently processing (but
                #   can contain multiple -F path= elements covering multiple SUID/SGID binaries)
                # * existing rule contains all arguments from expected rule form (though can contain
                #   them in arbitrary order)

                base_search=$(sed -e "/-a always,exit/!d" -e "/-F path=${sbinary_esc}$/!d"   \
                                  -e "/-F path=[^[:space:]]\+/!d" -e "/-F perm=.*/!d"       \
                                  -e "/-F auid&gt;=${min_auid}/!d" -e "/-F auid!=4294967295/!d"  \
                                  -e "/-k privileged/!d" $afile)

                # Increase the count of inspected files for this sbinary
                count_of_inspected_files=$((count_of_inspected_files + 1))

                # Define expected rule form for this binary
                expected_rule="-a always,exit -F path=${sbinary} -F perm=x -F auid&gt;=${min_auid} -F auid!=4294967295 -k privileged"

                # Require execute access type to be set for existing audit rule
                exec_access='x'

                # Search current audit rules file's content for presence of rule pattern for this sbinary
                if [[ $base_search ]]
                then

                        # Current audit rules file already contains rule for this binary =&gt;
                        # Store the exact form of found rule for this binary for further processing
                        concrete_rule=$base_search

                        # Select all other SUID/SGID binaries possibly also present in the found rule
                        IFS=$'\n' handled_sbinaries=($(grep -o -e "-F path=[^[:space:]]\+" &lt;&lt;&lt; $concrete_rule))
                        IFS=$' ' handled_sbinaries=(${handled_sbinaries[@]//-F path=/})

                        # Merge the list of such SUID/SGID binaries found in this iteration with global list ignoring duplicates
                        sbinaries_to_skip=($(for i in "${sbinaries_to_skip[@]}" "${handled_sbinaries[@]}"; do echo $i; done | sort -du))

                        # Separate concrete_rule into three sections using hash '#'
                        # sign as a delimiter around rule's permission section borders
                        concrete_rule=$(echo $concrete_rule | sed -n "s/\(.*\)\+\(-F perm=[rwax]\+\)\+/\1#\2#/p")

                        # Split concrete_rule into head, perm, and tail sections using hash '#' delimiter
                        IFS=$'#' read rule_head rule_perm rule_tail &lt;&lt;&lt;  "$concrete_rule"

                        # Extract already present exact access type [r|w|x|a] from rule's permission section
                        access_type=${rule_perm//-F perm=/}

                        # Verify current permission access type(s) for rule contain 'x' (execute) permission
                        if ! grep -q "$exec_access" &lt;&lt;&lt; "$access_type"
                        then

                                # If not, append the 'x' (execute) permission to the existing access type bits
                                access_type="$access_type$exec_access"
                                # Reconstruct the permissions section for the rule
                                new_rule_perm="-F perm=$access_type"
                                # Update existing rule in current audit rules file with the new permission section
                                sed -i "s#${rule_head}\(.*\)${rule_tail}#${rule_head}${new_rule_perm}${rule_tail}#" $afile

                        fi

                # If the required audit rule for particular sbinary wasn't found yet, insert it under following conditions:
                #
                # * in the "auditctl" mode of operation insert particular rule each time
                #   (because in this mode there's only one file -- /etc/audit/audit.rules to be inspected for presence of this rule),
                #
                # * in the "augenrules" mode of operation insert particular rule only once and only in case we have already
                #   searched all of the files from /etc/audit/rules.d/*.rules location (since that audit rule can be defined
                #   in any of those files and if not, we want it to be inserted only once into /etc/audit/rules.d/privileged.rules file)
                #
                elif [ "$tool" == "auditctl" ] || [[ "$tool" == "augenrules" &amp;&amp; $count_of_inspected_files -eq "${#files_to_inspect[@]}" ]]
                then

                        # Current audit rules file's content doesn't contain expected rule for this
                        # SUID/SGID binary yet =&gt; append it
                        echo $expected_rule &gt;&gt; $output_audit_file
                fi

        done

done

}
</ns0:value>
    </ns0:Value>
    <ns0:Value hidden="true" id="function_populate" operator="equals" prohibitChanges="true" type="string">
      <ns0:title xml:lang="en-US">Remediation function to populate environment variables needed for unit testing</ns0:title>
      <ns0:description xml:lang="en-US">The populate function isn't directly used by SSG at the moment but it can
ba used for testing purposes (to verify proper work of the remediation script directly
from the shell).</ns0:description>
      <ns0:value>
function populate {
# Code to populate environment variables needed (for unit testing)
if [ -z "${!1}" ]; then
	echo "$1 is not defined. Exiting."
	exit
fi
}
</ns0:value>
    </ns0:Value>
    <ns0:Value hidden="true" id="function_rhel6_perform_audit_adjtimex_settimeofday_stime_remediation" operator="equals" prohibitChanges="true" type="string">
      <ns0:title xml:lang="en-US">Remediation function for the 'adjtimex', 'settimeofday', and 'stime'
audit system calls on Red Hat Enterprise Linux 6</ns0:title>
      <ns0:description xml:lang="en-US">Perform the remediation for the 'adjtimex', 'settimeofday', and 'stime' audit
# system calls on Red Hat Enterprise Linux 6 OS</ns0:description>
      <ns0:value>
function fix_audit_syscall_rule {

# Load function arguments into local variables
local tool="$1"
local pattern="$2"
local group="$3"
local arch="$4"
local full_rule="$5"

# Check sanity of the input
if [ $# -ne "5" ]
then
        echo "Usage: fix_audit_syscall_rule 'tool' 'pattern' 'group' 'arch' 'full rule'"
        echo "Aborting."
        exit 1
fi

# Create a list of audit *.rules files that should be inspected for presence and correctness
# of a particular audit rule. The scheme is as follows:
# 
# -----------------------------------------------------------------------------------------
#  Tool used to load audit rules | Rule already defined  |  Audit rules file to inspect    |
# -----------------------------------------------------------------------------------------
#        auditctl                |     Doesn't matter    |  /etc/audit/audit.rules         |
# -----------------------------------------------------------------------------------------
#        augenrules              |          Yes          |  /etc/audit/rules.d/*.rules     |
#        augenrules              |          No           |  /etc/audit/rules.d/$key.rules  |
# -----------------------------------------------------------------------------------------
#
declare -a files_to_inspect

# First check sanity of the specified audit tool
if [ "$tool" != 'auditctl' ] &amp;&amp; [ "$tool" != 'augenrules' ]
then
        echo "Unknown audit rules loading tool: $1. Aborting."
        echo "Use either 'auditctl' or 'augenrules'!"
        exit 1
# If audit tool is 'auditctl', then add '/etc/audit/audit.rules'
# file to the list of files to be inspected
elif [ "$tool" == 'auditctl' ]
then
        files_to_inspect=("${files_to_inspect[@]}" '/etc/audit/audit.rules' )
# If audit tool is 'augenrules', then check if the audit rule is defined
# If rule is defined, add '/etc/audit/rules.d/*.rules' to the list for inspection
# If rule isn't defined yet, add '/etc/audit/rules.d/$key.rules' to the list for inspection
elif [ "$tool" == 'augenrules' ]
then
        # Extract audit $key from audit rule so we can use it later
        key=$(expr "$full_rule" : '.*-k[[:space:]]\([^[:space:]]\+\)')
        # Check if particular audit rule is already defined
        IFS=$'\n' matches=($(sed -s -n -e "/${pattern}/!d" -e "/${arch}/!d" -e "/${group}/!d;F" /etc/audit/rules.d/*.rules))
        # Reset IFS back to default
        unset $IFS
        for match in "${matches[@]}"
        do
                files_to_inspect=("${files_to_inspect[@]}" "${match}")
        done
        # Case when particular rule isn't defined in /etc/audit/rules.d/*.rules yet
        if [ ${#files_to_inspect[@]} -eq "0" ]
        then
                files_to_inspect="/etc/audit/rules.d/$key.rules"
                if [ ! -e "$files_to_inspect" ]
                then
                        touch "$files_to_inspect"
                        chmod 0640 "$files_to_inspect"
                fi
        fi
fi

#
# Indicator that we want to append $full_rule into $audit_file by default
local append_expected_rule=0

for audit_file in "${files_to_inspect[@]}"
do

        # Filter existing $audit_file rules' definitions to select those that:
        # * follow the rule pattern, and
        # * meet the hardware architecture requirement, and
        # * are current syscall group specific
        IFS=$'\n' existing_rules=($(sed -e "/${pattern}/!d" -e "/${arch}/!d" -e "/${group}/!d"  "$audit_file"))
        # Reset IFS back to default
        unset $IFS

        # Process rules found case-by-case
        for rule in "${existing_rules[@]}"
        do
                # Found rule is for same arch &amp; key, but differs (e.g. in count of -S arguments)
                if [ "${rule}" != "${full_rule}" ]
                then
                        # If so, isolate just '(-S \w)+' substring of that rule
                        rule_syscalls=$(echo $rule | grep -o -P '(-S \w+ )+')
                        # Check if list of '-S syscall' arguments of that rule is subset
                        # of '-S syscall' list of expected $full_rule
                        if grep -q -- "$rule_syscalls" &lt;&lt;&lt; "$full_rule"
                        then
                                # Rule is covered (i.e. the list of -S syscalls for this rule is
                                # subset of -S syscalls of $full_rule =&gt; existing rule can be deleted
                                # Thus delete the rule from audit.rules &amp; our array
                                sed -i -e "/$rule/d" "$audit_file"
                                existing_rules=("${existing_rules[@]//$rule/}")
                        else
                                # Rule isn't covered by $full_rule - it besides -S syscall arguments
                                # for this group contains also -S syscall arguments for other syscall
                                # group. Example: '-S lchown -S fchmod -S fchownat' =&gt; group='chown'
                                # since 'lchown' &amp; 'fchownat' share 'chown' substring
                                # Therefore:
                                # * 1) delete the original rule from audit.rules
                                # (original '-S lchown -S fchmod -S fchownat' rule would be deleted)
                                # * 2) delete the -S syscall arguments for this syscall group, but
                                # keep those not belonging to this syscall group
                                # (original '-S lchown -S fchmod -S fchownat' would become '-S fchmod'
                                # * 3) append the modified (filtered) rule again into audit.rules
                                # if the same rule not already present
                                #
                                # 1) Delete the original rule
                                sed -i -e "/$rule/d" "$audit_file"
                                # 2) Delete syscalls for this group, but keep those from other groups
                                # Convert current rule syscall's string into array splitting by '-S' delimiter
                                IFS=$'-S' read -a rule_syscalls_as_array &lt;&lt;&lt; "$rule_syscalls"
                                # Reset IFS back to default
                                unset $IFS
                                # Declare new empty string to hold '-S syscall' arguments from other groups
                                new_syscalls_for_rule=''
                                # Walk through existing '-S syscall' arguments
                                for syscall_arg in "${rule_syscalls_as_array[@]}"
                                do
                                        # Skip empty $syscall_arg values
                                        if [ "$syscall_arg" == '' ]
                                        then
                                                continue
                                        fi
                                        # If the '-S syscall' doesn't belong to current group add it to the new list
                                        # (together with adding '-S' delimiter back for each of such item found)
                                        if grep -q -v -- "$group" &lt;&lt;&lt; "$syscall_arg"
                                        then
                                                new_syscalls_for_rule="$new_syscalls_for_rule -S $syscall_arg"
                                        fi
                                done
                                # Replace original '-S syscall' list with the new one for this rule
                                updated_rule=${rule//$rule_syscalls/$new_syscalls_for_rule}
                                # Squeeze repeated whitespace characters in rule definition (if any) into one
                                updated_rule=$(echo "$updated_rule" | tr -s '[:space:]')
                                # 3) Append the modified / filtered rule again into audit.rules
                                #    (but only in case it's not present yet to prevent duplicate definitions)
                                if ! grep -q -- "$updated_rule" "$audit_file"
                                then
                                        echo "$updated_rule" &gt;&gt; "$audit_file"
                                fi
                        fi
                else
                        # $audit_file already contains the expected rule form for this
                        # architecture &amp; key =&gt; don't insert it second time
                        append_expected_rule=1
                fi
        done

        # We deleted all rules that were subset of the expected one for this arch &amp; key.
        # Also isolated rules containing system calls not from this system calls group.
        # Now append the expected rule if it's not present in $audit_file yet
        if [[ ${append_expected_rule} -eq "0" ]]
        then
                echo "$full_rule" &gt;&gt; "$audit_file"
        fi
done

}

function rhel6_perform_audit_adjtimex_settimeofday_stime_remediation {

# Perform the remediation for the 'adjtimex', 'settimeofday', and 'stime' audit
# system calls on Red Hat Enterprise Linux 6 OS
#
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
        PATTERN="-a always,exit -F arch=${ARCH} -S .* -k *"
        # Create expected audit group and audit rule form for particular system call &amp; architecture
        if [ ${ARCH} = "b32" ]
        then
                # stime system call is known at 32-bit arch (see e.g "$ ausyscall i386 stime" 's output)
                # so append it to the list of time group system calls to be audited
                GROUP="\(adjtimex\|settimeofday\|stime\)"
                FULL_RULE="-a always,exit -F arch=${ARCH} -S adjtimex -S settimeofday -S stime -k audit_time_rules"
        elif [ ${ARCH} = "b64" ]
        then
                # stime system call isn't known at 64-bit arch (see "$ ausyscall x86_64 stime" 's output)
                # therefore don't add it to the list of time group system calls to be audited
                GROUP="\(adjtimex\|settimeofday\)"
                FULL_RULE="-a always,exit -F arch=${ARCH} -S adjtimex -S settimeofday -k audit_time_rules"
        fi
        # Perform the remediation itself
        fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done

}
</ns0:value>
    </ns0:Value>
    <ns0:Value hidden="true" id="function_rhel7_fedora_perform_audit_adjtimex_settimeofday_stime_remediation" operator="equals" prohibitChanges="true" type="string">
      <ns0:title xml:lang="en-US">Remediation function for the 'adjtimex', 'settimeofday', and 'stime'
audit system calls on Red Hat Enterprise Linux 7 or Fedora</ns0:title>
      <ns0:description xml:lang="en-US">Perform the remediation for the 'adjtimex', 'settimeofday', and
'stime' audit system calls on Red Hat Enterprise Linux 7 or Fedora OSes</ns0:description>
      <ns0:value>
function fix_audit_syscall_rule {

# Load function arguments into local variables
local tool="$1"
local pattern="$2"
local group="$3"
local arch="$4"
local full_rule="$5"

# Check sanity of the input
if [ $# -ne "5" ]
then
        echo "Usage: fix_audit_syscall_rule 'tool' 'pattern' 'group' 'arch' 'full rule'"
        echo "Aborting."
        exit 1
fi

# Create a list of audit *.rules files that should be inspected for presence and correctness
# of a particular audit rule. The scheme is as follows:
# 
# -----------------------------------------------------------------------------------------
#  Tool used to load audit rules | Rule already defined  |  Audit rules file to inspect    |
# -----------------------------------------------------------------------------------------
#        auditctl                |     Doesn't matter    |  /etc/audit/audit.rules         |
# -----------------------------------------------------------------------------------------
#        augenrules              |          Yes          |  /etc/audit/rules.d/*.rules     |
#        augenrules              |          No           |  /etc/audit/rules.d/$key.rules  |
# -----------------------------------------------------------------------------------------
#
declare -a files_to_inspect

# First check sanity of the specified audit tool
if [ "$tool" != 'auditctl' ] &amp;&amp; [ "$tool" != 'augenrules' ]
then
        echo "Unknown audit rules loading tool: $1. Aborting."
        echo "Use either 'auditctl' or 'augenrules'!"
        exit 1
# If audit tool is 'auditctl', then add '/etc/audit/audit.rules'
# file to the list of files to be inspected
elif [ "$tool" == 'auditctl' ]
then
        files_to_inspect=("${files_to_inspect[@]}" '/etc/audit/audit.rules' )
# If audit tool is 'augenrules', then check if the audit rule is defined
# If rule is defined, add '/etc/audit/rules.d/*.rules' to the list for inspection
# If rule isn't defined yet, add '/etc/audit/rules.d/$key.rules' to the list for inspection
elif [ "$tool" == 'augenrules' ]
then
        # Extract audit $key from audit rule so we can use it later
        key=$(expr "$full_rule" : '.*-k[[:space:]]\([^[:space:]]\+\)')
        # Check if particular audit rule is already defined
        IFS=$'\n' matches=($(sed -s -n -e "/${pattern}/!d" -e "/${arch}/!d" -e "/${group}/!d;F" /etc/audit/rules.d/*.rules))
        # Reset IFS back to default
        unset $IFS
        for match in "${matches[@]}"
        do
                files_to_inspect=("${files_to_inspect[@]}" "${match}")
        done
        # Case when particular rule isn't defined in /etc/audit/rules.d/*.rules yet
        if [ ${#files_to_inspect[@]} -eq "0" ]
        then
                files_to_inspect="/etc/audit/rules.d/$key.rules"
                if [ ! -e "$files_to_inspect" ]
                then
                        touch "$files_to_inspect"
                        chmod 0640 "$files_to_inspect"
                fi
        fi
fi

#
# Indicator that we want to append $full_rule into $audit_file by default
local append_expected_rule=0

for audit_file in "${files_to_inspect[@]}"
do

        # Filter existing $audit_file rules' definitions to select those that:
        # * follow the rule pattern, and
        # * meet the hardware architecture requirement, and
        # * are current syscall group specific
        IFS=$'\n' existing_rules=($(sed -e "/${pattern}/!d" -e "/${arch}/!d" -e "/${group}/!d"  "$audit_file"))
        # Reset IFS back to default
        unset $IFS

        # Process rules found case-by-case
        for rule in "${existing_rules[@]}"
        do
                # Found rule is for same arch &amp; key, but differs (e.g. in count of -S arguments)
                if [ "${rule}" != "${full_rule}" ]
                then
                        # If so, isolate just '(-S \w)+' substring of that rule
                        rule_syscalls=$(echo $rule | grep -o -P '(-S \w+ )+')
                        # Check if list of '-S syscall' arguments of that rule is subset
                        # of '-S syscall' list of expected $full_rule
                        if grep -q -- "$rule_syscalls" &lt;&lt;&lt; "$full_rule"
                        then
                                # Rule is covered (i.e. the list of -S syscalls for this rule is
                                # subset of -S syscalls of $full_rule =&gt; existing rule can be deleted
                                # Thus delete the rule from audit.rules &amp; our array
                                sed -i -e "/$rule/d" "$audit_file"
                                existing_rules=("${existing_rules[@]//$rule/}")
                        else
                                # Rule isn't covered by $full_rule - it besides -S syscall arguments
                                # for this group contains also -S syscall arguments for other syscall
                                # group. Example: '-S lchown -S fchmod -S fchownat' =&gt; group='chown'
                                # since 'lchown' &amp; 'fchownat' share 'chown' substring
                                # Therefore:
                                # * 1) delete the original rule from audit.rules
                                # (original '-S lchown -S fchmod -S fchownat' rule would be deleted)
                                # * 2) delete the -S syscall arguments for this syscall group, but
                                # keep those not belonging to this syscall group
                                # (original '-S lchown -S fchmod -S fchownat' would become '-S fchmod'
                                # * 3) append the modified (filtered) rule again into audit.rules
                                # if the same rule not already present
                                #
                                # 1) Delete the original rule
                                sed -i -e "/$rule/d" "$audit_file"
                                # 2) Delete syscalls for this group, but keep those from other groups
                                # Convert current rule syscall's string into array splitting by '-S' delimiter
                                IFS=$'-S' read -a rule_syscalls_as_array &lt;&lt;&lt; "$rule_syscalls"
                                # Reset IFS back to default
                                unset $IFS
                                # Declare new empty string to hold '-S syscall' arguments from other groups
                                new_syscalls_for_rule=''
                                # Walk through existing '-S syscall' arguments
                                for syscall_arg in "${rule_syscalls_as_array[@]}"
                                do
                                        # Skip empty $syscall_arg values
                                        if [ "$syscall_arg" == '' ]
                                        then
                                                continue
                                        fi
                                        # If the '-S syscall' doesn't belong to current group add it to the new list
                                        # (together with adding '-S' delimiter back for each of such item found)
                                        if grep -q -v -- "$group" &lt;&lt;&lt; "$syscall_arg"
                                        then
                                                new_syscalls_for_rule="$new_syscalls_for_rule -S $syscall_arg"
                                        fi
                                done
                                # Replace original '-S syscall' list with the new one for this rule
                                updated_rule=${rule//$rule_syscalls/$new_syscalls_for_rule}
                                # Squeeze repeated whitespace characters in rule definition (if any) into one
                                updated_rule=$(echo "$updated_rule" | tr -s '[:space:]')
                                # 3) Append the modified / filtered rule again into audit.rules
                                #    (but only in case it's not present yet to prevent duplicate definitions)
                                if ! grep -q -- "$updated_rule" "$audit_file"
                                then
                                        echo "$updated_rule" &gt;&gt; "$audit_file"
                                fi
                        fi
                else
                        # $audit_file already contains the expected rule form for this
                        # architecture &amp; key =&gt; don't insert it second time
                        append_expected_rule=1
                fi
        done

        # We deleted all rules that were subset of the expected one for this arch &amp; key.
        # Also isolated rules containing system calls not from this system calls group.
        # Now append the expected rule if it's not present in $audit_file yet
        if [[ ${append_expected_rule} -eq "0" ]]
        then
                echo "$full_rule" &gt;&gt; "$audit_file"
        fi
done

}

function rhel7_fedora_perform_audit_adjtimex_settimeofday_stime_remediation {

# Perform the remediation for the 'adjtimex', 'settimeofday', and 'stime' audit
# system calls on Red Hat Enterprise Linux 7 or Fedora OSes
#
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do

        PATTERN="-a always,exit -F arch=${ARCH} -S .* -k *"
        # Create expected audit group and audit rule form for particular system call &amp; architecture
        if [ ${ARCH} = "b32" ]
        then
                # stime system call is known at 32-bit arch (see e.g "$ ausyscall i386 stime" 's output)
                # so append it to the list of time group system calls to be audited
                GROUP="\(adjtimex\|settimeofday\|stime\)"
                FULL_RULE="-a always,exit -F arch=${ARCH} -S adjtimex -S settimeofday -S stime -k audit_time_rules"
        elif [ ${ARCH} = "b64" ]
        then
                # stime system call isn't known at 64-bit arch (see "$ ausyscall x86_64 stime" 's output)
                # therefore don't add it to the list of time group system calls to be audited
                GROUP="\(adjtimex\|settimeofday\)"
                FULL_RULE="-a always,exit -F arch=${ARCH} -S adjtimex -S settimeofday -k audit_time_rules"
        fi
        # Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
        fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
        fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done

}
</ns0:value>
    </ns0:Value>
    <ns0:Value hidden="true" id="function_replace_or_append" operator="equals" prohibitChanges="true" type="string">
      <ns0:title xml:lang="en-US">Remediation function to replace configuration setting in config file or
add the configuration setting if it does not exist yet</ns0:title>
      <ns0:description xml:lang="en-US">Function to replace configuration setting in config file or add
the configuration setting if it does not exist.

Expects four arguments:

  config_file:		Configuration file that will be modified
  key:			Configuration option to change
  value:		Value of the configuration option to change
  cce:			The CCE identifier or '$CCENUM' if no CCE identifier exists

Optional arguments:

  format:		Optional argument to specify the format of how key/value should be
			modified/appended in the configuration file. The default is key = value.

Example Call(s):

  With default format of 'key = value':
  replace_or_append '/etc/sysctl.conf' '^kernel.randomize_va_space' '2' '$CCENUM'

  With custom key/value format:
  replace_or_append '/etc/sysconfig/selinux' '^SELINUX=' 'disabled' '$CCENUM' '%s=%s'

  With a variable:
  replace_or_append '/etc/sysconfig/selinux' '^SELINUX=' $var_selinux_state '$CCENUM' '%s=%s'
</ns0:description>
      <ns0:value>
function replace_or_append {
  local config_file=$1
  local key=$2
  local value=$3
  local cce=$4
  local format=$5

  # Check sanity of the input
  if [ $# -lt "3" ]
  then
        echo "Usage: replace_or_append 'config_file_location' 'key_to_search' 'new_value'"
        echo
        echo "If symlinks need to be taken into account, add yes/no to the last argument"
        echo "to allow to 'follow_symlinks'."
        echo "Aborting."
        exit 1
  fi

  # Test if the config_file is a symbolic link. If so, use --follow-symlinks with sed.
  # Otherwise, regular sed command will do.
  if test -L $config_file; then
    sed_command="sed -i --follow-symlinks"
  else
    sed_command="sed -i"
  fi

  # Test that the cce arg is not empty or does not equal $CCENUM.
  # If $CCENUM exists, it means that there is no CCE assigned.
  if ! [ "x$cce" = x ] &amp;&amp; [ "$cce" != '$CCENUM' ]; then
    cce="CCE-${cce}"
  else
    cce="CCE"
  fi

  # Strip any search characters in the key arg so that the key can be replaced without
  # adding any search characters to the config file.
  stripped_key=$(sed "s/[\^=\$,;+]*//g" &lt;&lt;&lt; $key)

  # If there is no print format specified in the last arg, use the default format.
  if ! [ "x$format" = x ] ; then
    printf -v formatted_output "$format" $stripped_key $value
  else
    formatted_output="$stripped_key = $value"
  fi

  # If the key exists, change it. Otherwise, add it to the config_file.
  if `grep -qi $key $config_file` ; then
    $sed_command "s/$key.*/$formatted_output/g" $config_file
  else
    echo -ne "\n# Per $cce: Set $formatted_output in $config_file" &gt;&gt; $config_file
    echo -ne "\n$formatted_output" &gt;&gt; $config_file
  fi

}
</ns0:value>
    </ns0:Value>
    <ns0:Value hidden="true" id="function_firefox_js_setting" operator="equals" prohibitChanges="true" type="string">
      <ns0:title xml:lang="en-US">Remediation function to replace configuration setting(s) in the Firefox
preferences JavaScript file or add the preference if it does not exist yet</ns0:title>
      <ns0:description xml:lang="en-US">Function to replace configuration setting(s) in the Firefox
preferences JavaScript file or add the preference if it does not exist.

Expects three arguments:

  config_file:          Configuration file that will be modified
  key:                  Configuration option to change
  value:                Value of the configuration option to change


Example Call(s):

  Without string or variable:
  firefox_js_setting "stig_settings.js" "general.config.obscure_value" "0"

  With string:
  firefox_js_setting "stig_settings.js" "general.config.filename" "\"stig.cfg\""

  With a string variable:
  firefox_js_setting "stig_settings.js" "general.config.filename" "\"$var_config_file_name\""
</ns0:description>
      <ns0:value>
function firefox_js_setting {
  local firefox_js=$1
  local key=$2
  local value=$3
  local firefox_dirs="/usr/lib/firefox /usr/lib64/firefox /usr/local/lib/firefox /usr/local/lib64/firefox"
  local firefox_pref="/defaults/pref"
  local firefox_preferences="/defaults/preferences"

  # Check sanity of input
  if [ $# -lt "3" ]
  then
        echo "Usage: firefox_js_setting 'config_javascript_file' 'key_to_search' 'new_value'"
        echo
        echo "Aborting."
        exit 1
  fi

  # Check the possible Firefox install directories
  for firefox_dir in ${firefox_dirs}; do
    # If the Firefox directory exists, then Firefox is installed
    if [ -d "${firefox_dir}" ]; then
      # Different versions of Firefox have different preferences directories, check for them and set the right one
      if [ -d "${firefox_dir}/${firefox_pref}" ] ; then
        local firefox_pref_dir="${firefox_dir}/${firefox_pref}"
      elif [ -d "${firefox_dir}/${firefox_preferences}" ] ; then
        local firefox_pref_dir="${firefox_dir}/${firefox_preferences}"
      else
        mkdir -m 755 -p "${firefox_dir}/${firefox_preferences}"
        local firefox_pref_dir="${firefox_dir}/${firefox_preferences}"
      fi

      # Make sure the Firefox .js file exists and has the appropriate permissions
      if ! [ -f "${firefox_pref_dir}/${firefox_js}" ] ; then
        touch "${firefox_pref_dir}/${firefox_js}"
        chmod 644 "${firefox_pref_dir}/${firefox_js}"
      fi

      # If the key exists, change it. Otherwise, add it to the config_file.
      if `grep -q "^pref(\"${key}\", " "${firefox_pref_dir}/${firefox_js}"` ; then
        sed -i "s/pref(\"${key}\".*/pref(\"${key}\", ${value});/g" "${firefox_pref_dir}/${firefox_js}"
      else
        echo "pref(\"${key}\", ${value});" &gt;&gt; "${firefox_pref_dir}/${firefox_js}"
      fi
    fi
  done

}
</ns0:value>
    </ns0:Value>
    <ns0:Value hidden="true" id="function_firefox_cfg_setting" operator="equals" prohibitChanges="true" type="string">
      <ns0:title xml:lang="en-US">Remediation function to replace configuration setting(s) in the Firefox
preferences configuration (.cfg) file or add the preference if it does not exist yet</ns0:title>
      <ns0:description xml:lang="en-US">Function to replace configuration setting(s) in the Firefox
preferences configuration (.cfg) file or add the preference if it does not exist.

Expects three arguments:

  config_file:          Configuration file that will be modified
  key:                  Configuration option to change
  value:                Value of the configuration option to change


Example Call(s):

  Without string or variable:
  firefox_cfg_setting "stig.cfg" "extensions.update.enabled" "false"

  With string:
  firefox_cfg_setting "stig.cfg" "security.default_personal_cert" "\"Ask Every Time\""

  With a string variable:
  firefox_cfg_setting "stig.cfg" "browser.startup.homepage\" "\"${var_default_home_page}\""
</ns0:description>
      <ns0:value>
function firefox_cfg_setting {
  local firefox_cfg=$1
  local key=$2
  local value=$3
  local firefox_dirs="/usr/lib/firefox /usr/lib64/firefox /usr/local/lib/firefox /usr/local/lib64/firefox"

  # Check sanity of input
  if [ $# -lt "3" ]
  then
        echo "Usage: firefox_cfg_setting 'config_cfg_file' 'key_to_search' 'new_value'"
        echo
        echo "Aborting."
        exit 1
  fi

  # Check the possible Firefox install directories
  for firefox_dir in ${firefox_dirs}; do
    # If the Firefox directory exists, then Firefox is installed
    if [ -d "${firefox_dir}" ]; then
      # Make sure the Firefox .cfg file exists and has the appropriate permissions
      if ! [ -f "${firefox_dir}/${firefox_cfg}" ] ; then
        touch "${firefox_dir}/${firefox_cfg}"
        chmod 644 "${firefox_dir}/${firefox_cfg}"
      fi

      # If the key exists, change it. Otherwise, add it to the config_file.
      if `grep -q "^lockPref(\"${key}\", " "${firefox_dir}/${firefox_cfg}"` ; then
        sed -i "s/lockPref(\"${key}\".*/lockPref(\"${key}\", ${value});/g" "${firefox_dir}/${firefox_cfg}"
      else
        echo "lockPref(\"${key}\", ${value});" &gt;&gt; "${firefox_dir}/${firefox_cfg}"
      fi
    fi
  done
}
</ns0:value>
    </ns0:Value>
  </ns0:Group>
  <ns0:Group id="intro">
    <ns0:title xml:lang="en-US">Introduction</ns0:title>
    <ns0:description xml:lang="en-US">
The purpose of this guidance is to provide security configuration
recommendations and baselines for the Red Hat Enterprise Linux 7 operating
system. Recommended settings for the basic operating system are provided,
as well as for many network services that the system can provide to other systems.
The guide is intended for system administrators. Readers are assumed to
possess basic system administration skills for Unix-like systems, as well
as some familiarity with the product's documentation and administration
conventions. Some instructions within this guide are complex.
All directions should be followed completely and with understanding of
their effects in order to avoid serious adverse effects on the system
and its security.
</ns0:description>
    <ns0:Group id="general-principles">
      <ns0:title xml:lang="en-US">General Principles</ns0:title>
      <ns0:description xml:lang="en-US">
The following general principles motivate much of the advice in this
guide and should also influence any configuration decisions that are
not explicitly covered.
</ns0:description>
      <ns0:Group id="principle-encrypt-transmitted-data">
        <ns0:title xml:lang="en-US">Encrypt Transmitted Data Whenever Possible</ns0:title>
        <ns0:description xml:lang="en-US">
Data transmitted over a network, whether wired or wireless, is susceptible
to passive monitoring. Whenever practical solutions for encrypting
such data exist, they should be applied. Even if data is expected to
be transmitted only over a local network, it should still be encrypted.
Encrypting authentication data, such as passwords, is particularly
important. Networks of Red Hat Enterprise Linux 7 machines can and should be configured
so that no unencrypted authentication data is ever transmitted between
machines.
</ns0:description>
      </ns0:Group>
      <ns0:Group id="principle-minimize-software">
        <ns0:title xml:lang="en-US">Minimize Software to Minimize Vulnerability</ns0:title>
        <ns0:description xml:lang="en-US">
The simplest way to avoid vulnerabilities in software is to avoid
installing that software. On Red Hat Enterprise Linux 7,
the RPM Package Manager (originally Red Hat
Package Manager, abbreviated RPM)
allows for careful management of
the set of software packages installed on a system. Installed software
contributes to system vulnerability in several ways. Packages that
include setuid programs may provide local attackers a potential path to
privilege escalation. Packages that include network services may give
this opportunity to network-based attackers. Packages that include
programs which are predictably executed by local users (e.g. after
graphical login) may provide opportunities for trojan horses or other
attack code to be run undetected. The number of software packages
installed on a system can almost always be significantly pruned to include
only the software for which there is an environmental or operational need.
</ns0:description>
      </ns0:Group>
      <ns0:Group id="principle-separate-servers">
        <ns0:title xml:lang="en-US">Run Different Network Services on Separate Systems</ns0:title>
        <ns0:description xml:lang="en-US">
Whenever possible, a server should be dedicated to serving exactly one
network service. This limits the number of other services that can
be compromised in the event that an attacker is able to successfully
exploit a software flaw in one network service.
</ns0:description>
      </ns0:Group>
      <ns0:Group id="principle-use-security-tools">
        <ns0:title xml:lang="en-US">Configure Security Tools to Improve System Robustness</ns0:title>
        <ns0:description xml:lang="en-US">
Several tools exist which can be effectively used to improve a system's
resistance to and detection of unknown attacks. These tools can improve
robustness against attack at the cost of relatively little configuration
effort. In particular, this guide recommends and discusses the use of
host-based firewalling, SELinux for protection against
vulnerable services, and a logging and auditing infrastructure for
detection of problems.
</ns0:description>
      </ns0:Group>
      <ns0:Group id="principle-least-privilege">
        <ns0:title xml:lang="en-US">Least Privilege</ns0:title>
        <ns0:description xml:lang="en-US">
Grant the least privilege necessary for user accounts and software to perform tasks.
For example, <html:code xmlns:html="http://www.w3.org/1999/xhtml">sudo</html:code> can be implemented to limit authorization to super user
accounts on the system only to designated personnel. Another example is to limit
logins on server systems to only those administrators who need to log into them in
order to perform administration tasks. Using SELinux also follows the principle of
least privilege: SELinux policy can confine software to perform only actions on the
system that are specifically allowed. This can be far more restrictive than the
actions permissible by the traditional Unix permissions model.
</ns0:description>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="how-to-use">
      <ns0:title xml:lang="en-US">How to Use This Guide</ns0:title>
      <ns0:description xml:lang="en-US">
Readers should heed the following points when using the guide.
</ns0:description>
      <ns0:Group id="intro-read-sections-completely">
        <ns0:title xml:lang="en-US">Read Sections Completely and in Order</ns0:title>
        <ns0:description xml:lang="en-US">
Each section may build on information and recommendations discussed in
prior sections. Each section should be read and understood completely;
instructions should never be blindly applied. Relevant discussion may
occur after instructions for an action. 
</ns0:description>
      </ns0:Group>
      <ns0:Group id="intro-test-non-production">
        <ns0:title xml:lang="en-US">Test in Non-Production Environment</ns0:title>
        <ns0:description xml:lang="en-US">
This guidance should always be tested in a non-production environment
before deployment. This test environment should simulate the setup in
which the system will be deployed as closely as possible.
</ns0:description>
      </ns0:Group>
      <ns0:Group id="intro-root-shell-assumed">
        <ns0:title xml:lang="en-US">Root Shell Environment Assumed</ns0:title>
        <ns0:description xml:lang="en-US">
Most of the actions listed in this document are written with the
assumption that they will be executed by the root user running the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/bin/bash</html:code> shell. Commands preceded with a hash mark (#)
assume that the administrator will execute the commands as root, i.e.
apply the command via <html:code xmlns:html="http://www.w3.org/1999/xhtml">sudo</html:code> whenever possible, or use
<html:code xmlns:html="http://www.w3.org/1999/xhtml">su</html:code> to gain root privileges if <html:code xmlns:html="http://www.w3.org/1999/xhtml">sudo</html:code> cannot be
used. Commands which can be executed as a non-root user are are preceded
by a dollar sign ($) prompt.
</ns0:description>
      </ns0:Group>
      <ns0:Group id="intro-formatting-conventions">
        <ns0:title xml:lang="en-US">Formatting Conventions</ns0:title>
        <ns0:description xml:lang="en-US">
Commands intended for shell execution, as well as configuration file text,
are featured in a <html:code xmlns:html="http://www.w3.org/1999/xhtml">monospace font</html:code>. <html:i xmlns:html="http://www.w3.org/1999/xhtml">Italics</html:i> are used
to indicate instances where the system administrator must substitute
the appropriate information into a command or configuration file.
</ns0:description>
      </ns0:Group>
      <ns0:Group id="intro-reboot-required">
        <ns0:title xml:lang="en-US">Reboot Required</ns0:title>
        <ns0:description xml:lang="en-US">
A system reboot is implicitly required after some actions in order to
complete the reconfiguration of the system. In many cases, the changes
will not take effect until a reboot is performed. In order to ensure
that changes are applied properly and to test functionality, always
reboot the system after applying a set of recommendations from this guide.
</ns0:description>
      </ns0:Group>
    </ns0:Group>
  </ns0:Group>
  <ns0:Group id="system">
    <ns0:title xml:lang="en-US">System Settings</ns0:title>
    <ns0:description xml:lang="en-US">Contains rules that check correct system settings.</ns0:description>
    <ns0:Group id="software">
      <ns0:title xml:lang="en-US">Installing and Maintaining Software</ns0:title>
      <ns0:description xml:lang="en-US">The following sections contain information on
security-relevant choices during the initial operating system
installation process and the setup of software
updates.</ns0:description>
      <ns0:Group id="disk_partitioning">
        <ns0:title xml:lang="en-US">Disk Partitioning</ns0:title>
        <ns0:description xml:lang="en-US">To ensure separation and protection of data, there
are top-level system directories which should be placed on their
own physical partition or logical volume. The installer's default
partitioning scheme creates separate logical volumes for 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">/boot</html:code>, and <html:code xmlns:html="http://www.w3.org/1999/xhtml">swap</html:code>.
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>If starting with any of the default layouts, check the box to
"Review and modify partitioning." This allows for the easy creation
of additional logical volumes inside the volume group already
created, though it may require making <html:code>/</html:code>'s logical volume smaller to
create space. In general, using logical volumes is preferable to
using partitions because they can be more easily adjusted
later.</html:li><html:li>If creating a custom layout, create the partitions mentioned in
the previous paragraph (which the installer will require anyway),
as well as separate ones described in the following sections.</html:li></html:ul>
If a system has already been installed, and the default
partitioning scheme was used, it is possible but nontrivial to
modify it to create separate logical volumes for the directories
listed above. The Logical Volume Manager (LVM) makes this possible.
See the LVM HOWTO at <html:a href="http://tldp.org/HOWTO/LVM-HOWTO/" xmlns:html="http://www.w3.org/1999/xhtml">http://tldp.org/HOWTO/LVM-HOWTO/</html:a>
for more detailed information on LVM.</ns0:description>
        <ns0:Rule id="partition_for_tmp" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure /tmp Located On Separate Partition</ns0:title>
          <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code> directory is a world-writable directory used
for temporary file storage. Ensure it has its own partition or
logical volume at installation time, or migrate it using LVM.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-32(1)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.1</ns0:reference>
          <ns0:rationale xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code> partition is used as temporary storage by many programs.
Placing <html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code> in its own partition enables the setting of more
restrictive mount options, which can help protect programs which use it.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-partition_for_tmp:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-partition_for_tmp_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="partition_for_var" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure /var Located On Separate Partition</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var</html:code> directory is used by daemons and other system
services to store frequently-changing data. Ensure that <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var</html:code> has its own partition
or logical volume at installation time, or migrate it using LVM.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-32(1)</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Ensuring that <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var</html:code> is mounted on its own partition enables the
setting of more restrictive mount options. This helps protect
system services such as daemons or other programs which use it.
It is not uncommon for the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var</html:code> directory to contain
world-writable directories installed by other software packages.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-partition_for_var:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-partition_for_var_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="partition_for_var_log" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure /var/log Located On Separate Partition</ns0:title>
          <ns0:description xml:lang="en-US">
System logs are stored in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log</html:code> directory.
Ensure that it has its own partition or logical
volume at installation time, or migrate it using LVM.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-32</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.7</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Placing <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log</html:code> in its own partition
enables better separation between log files
and other files in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/</html:code>.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-partition_for_var_log:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-partition_for_var_log_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="partition_for_var_log_audit" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure /var/log/audit Located On Separate Partition</ns0:title>
          <ns0:description xml:lang="en-US">
Audit logs are stored in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log/audit</html:code> directory.  Ensure that it
has its own partition or logical volume at installation time, or migrate it
later using LVM. Make absolutely certain that it is large enough to store all
audit logs that will be created by the auditing daemon.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-4</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-32(1)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.8</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Placing <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log/audit</html:code> in its own partition
enables better separation between audit files
and other files, and helps ensure that
auditing cannot be halted due to the partition running out
of space.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-partition_for_var_log_audit:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-partition_for_var_log_audit_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="partition_for_home" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure /home Located On Separate Partition</ns0:title>
          <ns0:description xml:lang="en-US">
If user home directories will be stored locally, create a separate partition
for <html:code xmlns:html="http://www.w3.org/1999/xhtml">/home</html:code> at installation time (or migrate it later using LVM). If
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/home</html:code> will be mounted from another system such as an NFS server, then
creating a separate partition is not necessary at installation time, and the
mountpoint can instead be configured later.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-32(1)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1208</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.9</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Ensuring that <html:code xmlns:html="http://www.w3.org/1999/xhtml">/home</html:code> is mounted on its own partition enables the
setting of more restrictive mount options, and also helps ensure that
users cannot trivially fill partitions used for log or audit data storage.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-partition_for_home:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-partition_for_home_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="encrypt_partitions" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Encrypt Partitions</ns0:title>
          <ns0:description xml:lang="en-US">
Red Hat Enterprise Linux 7 natively supports partition encryption through the
Linux Unified Key Setup-on-disk-format (LUKS) technology. The easiest way to 
encrypt a partition is during installation time.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For manual installations, select the <html:code xmlns:html="http://www.w3.org/1999/xhtml">Encrypt</html:code> checkbox during
partition creation to encrypt the partition. When this
option is selected the system will prompt for a passphrase to use in
decrypting the partition. The passphrase will subsequently need to be entered manually
every time the system boots.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For automated/unattended installations, it is possible to use Kickstart by adding
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">--encrypted</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">--passphrase=</html:code> options to the definition of each partition to be
encrypted. For example, the following line would encrypt the root partition:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">part / --fstype=ext4 --size=100 --onpart=hda1 --encrypted --passphrase=<html:i>PASSPHRASE</html:i></html:pre>
Any <html:i xmlns:html="http://www.w3.org/1999/xhtml">PASSPHRASE</html:i> is stored in the Kickstart in plaintext, and the Kickstart must then be protected accordingly.
Omitting the <html:code xmlns:html="http://www.w3.org/1999/xhtml">--passphrase=</html:code> option from the partition definition will cause the
installer to pause and interactively ask for the passphrase during installation.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Detailed information on encrypting partitions using LUKS can be found on
the Red Hat Documentation web site:<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:a href="https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/sec-Encryption.html" xmlns:html="http://www.w3.org/1999/xhtml">https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/sec-Encryption.html</html:a>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-13</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-28(1)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1199</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2476</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000405-GPOS-00184</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000185-GPOS-00079</ns0:reference>
          <ns0:rationale xml:lang="en-US">
The risk of a system's physical compromise, particularly mobile systems such as
laptops, places its data at risk of compromise.  Encrypting this data mitigates
the risk of its loss if the system is lost.
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-encrypt_partitions_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="updating">
        <ns0:title xml:lang="en-US">Updating Software</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">yum</html:code> command line tool is used to install and
update software packages. The system also provides a graphical
software update tool in the <html:b xmlns:html="http://www.w3.org/1999/xhtml">System</html:b> menu, in the <html:b xmlns:html="http://www.w3.org/1999/xhtml">Administration</html:b> submenu,
called <html:b xmlns:html="http://www.w3.org/1999/xhtml">Software Update</html:b>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Red Hat Enterprise Linux systems contain an installed software catalog called
the RPM database, which records metadata of installed packages. Consistently using
<html:code xmlns:html="http://www.w3.org/1999/xhtml">yum</html:code> or the graphical <html:b xmlns:html="http://www.w3.org/1999/xhtml">Software Update</html:b> for all software installation
allows for insight into the current inventory of installed software on the system.
</ns0:description>
        <ns0:Rule id="ensure_redhat_gpgkey_installed" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Ensure Red Hat GPG Key Installed</ns0:title>
          <ns0:description xml:lang="en-US">
To ensure the system can cryptographically verify base software
packages come from Red Hat (and to connect to the Red Hat Network to
receive them), the Red Hat GPG key must properly be installed.  
To install the Red Hat GPG key, run:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo rhn_register</html:pre>
If the system is not connected to the Internet or an RHN Satellite,
then install the Red Hat GPG key from trusted media such as
the Red Hat installation CD-ROM or DVD. Assuming the disc is mounted
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/media/cdrom</html:code>, use the following command as the root user to import
it into the keyring:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo rpm --import /media/cdrom/RPM-GPG-KEY</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-5(3)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MA-1(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1749</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-6.2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.2.2</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Changes to software components can have significant effects on the
overall security of the operating system. This requirement ensures
the software has not been tampered with and that it has been provided 
by a trusted vendor. The Red Hat GPG key is necessary to 
cryptographically verify packages are from Red Hat.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="ensure_redhat_gpgkey_installed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"># The two fingerprints below are retrieved from https://access.redhat.com/security/team/key
readonly REDHAT_RELEASE_2_FINGERPRINT="567E 347A D004 4ADE 55BA 8A5F 199E 2F91 FD43 1D51"
readonly REDHAT_AUXILIARY_FINGERPRINT="43A6 E49C 4A38 F4BE 9ABF 2A53 4568 9C88 2FA6 58E0"
# Location of the key we would like to import (once it's integrity verified)
readonly REDHAT_RELEASE_KEY="/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release"

RPM_GPG_DIR_PERMS=$(stat -c %a "$(dirname "$REDHAT_RELEASE_KEY")")

# Verify /etc/pki/rpm-gpg directory permissions are safe
if [ "${RPM_GPG_DIR_PERMS}" -le "755" ]
then
  # If they are safe, try to obtain fingerprints from the key file
  # (to ensure there won't be e.g. CRC error)
  IFS=$'\n' GPG_OUT=($(gpg --with-fingerprint "${REDHAT_RELEASE_KEY}"))
  GPG_RESULT=$?
  # No CRC error, safe to proceed
  if [ "${GPG_RESULT}" -eq "0" ]
  then
    for ITEM in "${GPG_OUT[@]}"
    do
      # Filter just hexadecimal fingerprints from gpg's output from
      # processing of a key file
      RESULT=$(echo ${ITEM} | sed -n "s/[[:space:]]*Key fingerprint = \(.*\)/\1/p" | tr -s '[:space:]')
      # If fingerprint matches Red Hat's release 2 or auxiliary key import the key
      if [[ ${RESULT} ]] &amp;&amp; ([[ ${RESULT} = "${REDHAT_RELEASE_2_FINGERPRINT}" ]] || \
                             [[ ${RESULT} = "${REDHAT_AUXILIARY_FINGERPRINT}" ]])
      then
        rpm --import "${REDHAT_RELEASE_KEY}"
      fi
    done
  fi
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-ensure_redhat_gpgkey_installed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-ensure_redhat_gpgkey_installed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="ensure_gpgcheck_globally_activated" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Ensure gpgcheck Enabled In Main Yum Configuration</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">gpgcheck</html:code> option controls whether
RPM packages' signatures are always checked prior to installation.
To configure yum to check package signatures before installing
them, ensure the following line appears in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/yum.conf</html:code> in
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[main]</html:code> section:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">gpgcheck=1</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-5(3)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MA-1(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1749</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000366-GPOS-00153</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-6.2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.2.3</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Changes to any software components can have significant effects on the overall security 
of the operating system. This requirement ensures the software has not been tampered with
and that it has been provided by a trusted vendor.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Accordingly, patches, service packs, device drivers, or operating system components must
be signed with a certificate recognized and approved by the organization.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Verifying the authenticity of the software prior to installation
validates the integrity of the patch or upgrade received from
a vendor. This ensures the software has not been tampered with and
that it has been provided by a trusted vendor. Self-signed
certificates are disallowed by this requirement. Certificates
used to verify the software must be from an approved Certificate
Authority (CA).
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="ensure_gpgcheck_globally_activated" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">sed -i 's/gpgcheck=.*/gpgcheck=1/g' /etc/yum.conf
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-ensure_gpgcheck_globally_activated:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-ensure_gpgcheck_globally_activated_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="ensure_gpgcheck_never_disabled" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Ensure gpgcheck Enabled For All Yum Package Repositories</ns0:title>
          <ns0:description xml:lang="en-US">To ensure signature checking is not disabled for
any repos, remove any lines from files in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/yum.repos.d</html:code> of the form:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">gpgcheck=0</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-5(3)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MA-1(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1749</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-6.2</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Verifying the authenticity of the software prior to installation
validates the integrity of the patch or upgrade received from
a vendor. This ensures the software has not been tampered with and
that it has been provided by a trusted vendor. Self-signed 
certificates are disallowed by this requirement. Certificates
used to verify the software must be from an approved Certificate
Authority (CA).
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="ensure_gpgcheck_never_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">sed -i 's/gpgcheck=.*/gpgcheck=1/g' /etc/yum.repos.d/*
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-ensure_gpgcheck_never_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-ensure_gpgcheck_never_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="security_patches_up_to_date" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Ensure Software Patches Installed</ns0:title>
          <ns0:description xml:lang="en-US">If the system is joined to the Red Hat Network, a Red Hat Satellite Server,
or a yum server, run the following command to install updates:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum update</html:pre>
If the system is not configured to use one of these sources, updates (in the form of RPM packages)
can be manually downloaded from the Red Hat Network and installed using <html:code xmlns:html="http://www.w3.org/1999/xhtml">rpm</html:code>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
NOTE: U.S. Defense systems are required to be patched within 30 days or sooner as local policy
dictates.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-2</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MA-1(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-6.2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Installing software updates is a fundamental mitigation against
the exploitation of publicly-known vulnerabilities. If the most
recent security patches and updates are not installed, unauthorized
users may take advantage of weaknesses in the unpatched software. The
lack of prompt attention to patching could result in a system compromise.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="security_patches_up_to_date" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">yum -y update
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="http://www.redhat.com/security/data/oval/com.redhat.rhsa-RHEL7.xml.bz2" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-security_patches_up_to_date_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="clean_components_post_updating" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure YUM Removes Previous Package Versions</ns0:title>
          <ns0:description xml:lang="en-US"><html:code xmlns:html="http://www.w3.org/1999/xhtml">Yum</html:code> should be configured to remove previous software components after
previous versions have been installed. To configure <html:code xmlns:html="http://www.w3.org/1999/xhtml">yum</html:code> to remove the
previous software components after updating, set the <html:code xmlns:html="http://www.w3.org/1999/xhtml">clean_requirements_on_remove</html:code>
to <html:code xmlns:html="http://www.w3.org/1999/xhtml">1</html:code> in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/yum.conf</html:code>.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-2(6)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2617</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000437-GPOS-00194</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Previous versions of software components that are not removed from the information
system after updates have been installed may be exploited by some adversaries.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="clean_components_post_updating" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
if grep --silent ^clean_requirements_on_remove /etc/yum.conf ; then
        sed -i "s/^clean_requirements_on_remove.*/clean_requirements_on_remove=1/g" /etc/yum.conf
else
        echo -e "\n# Set clean_requirements_on_remove to 1 per security requirements" &gt;&gt; /etc/yum.conf
        echo "clean_requirements_on_remove=1" &gt;&gt; /etc/yum.conf
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-clean_components_post_updating:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-clean_components_post_updating_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="ensure_gpgcheck_local_packages" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Ensure gpgcheck Enabled for Local Packages</ns0:title>
          <ns0:description xml:lang="en-US"><html:code xmlns:html="http://www.w3.org/1999/xhtml">Yum</html:code> should be configured to verify the signature(s) of local packages
prior to installation. To configure <html:code xmlns:html="http://www.w3.org/1999/xhtml">yum</html:code> to verify signatures of local
packages, set the <html:code xmlns:html="http://www.w3.org/1999/xhtml">localpkg_gpgcheck</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">1</html:code> in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/yum.conf</html:code>.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-5(3)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1749</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000366-GPOS-00153</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Changes to any software components can have significant effects to the overall security
of the operating system. This requirement ensures the software has not been tampered and
has been provided by a trusted vendor.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Accordingly, patches, service packs, device drivers, or operating system components must
be signed with a certificate recognized and approved by the organization.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="ensure_gpgcheck_local_packages" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
if grep --silent ^localpkg_gpgcheck /etc/yum.conf ; then
        sed -i "s/^localpkg_gpgcheck.*/localpkg_gpgcheck=1/g" /etc/yum.conf
else
        echo -e "\n# Set localpkg_gpgcheck to 1 per security requirements" &gt;&gt; /etc/yum.conf
        echo "localpkg_gpgcheck=1" &gt;&gt; /etc/yum.conf
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-ensure_gpgcheck_local_packages:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-ensure_gpgcheck_local_packages_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="ensure_gpgcheck_repo_metadata" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Ensure gpgcheck Enabled for Repository Metadata</ns0:title>
          <ns0:description xml:lang="en-US">
Verify the operating system prevents the installation of patches, service packs, device
drivers, or operating system components of local packages without verification of the 
repository metadata.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Check that <html:code xmlns:html="http://www.w3.org/1999/xhtml">yum</html:code> verifies the repository metadata prior to install with the
following command. This should be configured by setting <html:code xmlns:html="http://www.w3.org/1999/xhtml">repo_gpgcheck</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">1</html:code>
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/yum.conf</html:code>.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-5(3)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1749</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000366-GPOS-00153</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Changes to any software components can have significant effects to the overall security
of the operating system. This requirement ensures the software has not been tampered and
has been provided by a trusted vendor.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Accordingly, patches, service packs, device drivers, or operating system components must
be signed with a certificate recognized and approved by the organization.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Verifying the authenticity of the software prior to installation validates the integrity
of the patch or upgrade received from a vendor. This ensures the software has not been
tampered with and that it has been provided by a trusted vendor. Self-signed certificates
are disallowed by this requirement. The operating system should not have to verify the software
again.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
NOTE: For U.S. Military systems, this requirement does not mandate DoD certificates for
this purpose; however, the certificate used to verify the software must be from an 
approved Certificate Authority.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="ensure_gpgcheck_repo_metadata" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
if grep --silent ^repo_gpgcheck /etc/yum.conf ; then
        sed -i "s/^repo_gpgcheck.*/repo_gpgcheck=1/g" /etc/yum.conf
else
        echo -e "\n# Set repo_gpgcheck to 1 per security requirements" &gt;&gt; /etc/yum.conf
        echo "repo_gpgcheck=1" &gt;&gt; /etc/yum.conf
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-ensure_gpgcheck_repo_metadata:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-ensure_gpgcheck_repo_metadata_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="integrity">
        <ns0:title xml:lang="en-US">System and Software Integrity</ns0:title>
        <ns0:description xml:lang="en-US">
System and software integrity can be gained by installing antivirus, increasing
system encryption strength with FIPS, verifying installed software, enabling SELinux,
installing an Intrusion Prevention System, etc. However, installing or enabling integrity
checking tools cannot <html:i xmlns:html="http://www.w3.org/1999/xhtml">prevent</html:i> intrusions, but they can detect that an intrusion
may have occurred. Requirements for integrity checking may be highly dependent on
the environment in which the system will be used. Snapshot-based approaches such
as AIDE may induce considerable overhead in the presence of frequent software updates.
</ns0:description>
        <ns0:Rule id="disable_prelink" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Prelinking</ns0:title>
          <ns0:description xml:lang="en-US">
The prelinking feature changes binaries in an attempt to decrease their startup
time. In order to disable it, change or add the following line inside the file
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/prelink</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">PRELINKING=no</html:pre>
Next, run the following command to return binaries to a normal, non-prelinked state:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo /usr/sbin/prelink -ua</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(3)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-28</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-7</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-11.5</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Because the prelinking feature changes binaries, it can interfere with the
operation of certain software and/or modes such as AIDE, FIPS, etc.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="disable_prelink" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">#
# Disable prelinking altogether
#
if grep -q ^PRELINKING /etc/sysconfig/prelink
then
  sed -i 's/PRELINKING.*/PRELINKING=no/g' /etc/sysconfig/prelink
else
  echo -e "\n# Set PRELINKING=no per security requirements" &gt;&gt; /etc/sysconfig/prelink
  echo "PRELINKING=no" &gt;&gt; /etc/sysconfig/prelink
fi

#
# Undo previous prelink changes to binaries
#
/usr/sbin/prelink -ua
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-disable_prelink:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="software-integrity">
          <ns0:title xml:lang="en-US">Software Integrity Checking</ns0:title>
          <ns0:description xml:lang="en-US">
Both the AIDE (Advanced Intrusion Detection Environment)
software and the RPM package management system provide
mechanisms for verifying the integrity of installed software.
AIDE uses snapshots of file metadata (such as hashes) and compares these
to current system files in order to detect changes.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The RPM package management system can conduct integrity
checks by comparing information in its metadata database with
files installed on the system.
</ns0:description>
          <ns0:Group id="aide">
            <ns0:title xml:lang="en-US">Verify Integrity with AIDE</ns0:title>
            <ns0:description xml:lang="en-US">AIDE conducts integrity checks by comparing information about
files with previously-gathered information. Ideally, the AIDE database is
created immediately after initial system configuration, and then again after any
software update.  AIDE is highly configurable, with further configuration
information located in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/usr/share/doc/aide-<html:i>VERSION</html:i></html:code>.
</ns0:description>
            <ns0:Rule id="package_aide_installed" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Install AIDE</ns0:title>
              <ns0:description xml:lang="en-US">
Install the AIDE package with the command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install aide</html:pre>
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-3(d)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-3(e)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(d)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(3)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-28</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-7</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
              <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-11.5</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.3.1</ns0:reference>
              <ns0:rationale xml:lang="en-US">
The AIDE package must be installed if it is to be available for integrity checking.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="package_aide_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command install aide
</ns0:fix>
              <ns0:fix complexity="low" disruption="low" id="package_aide_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Ensure aide is installed
  package:
    name="{{item}}"
    state=present
  with_items:
    - aide
</ns0:fix>
              <ns0:fix complexity="low" disruption="low" id="package_aide_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:puppet">include install_aide

class install_aide {
  package { 'aide':
    ensure =&gt; 'installed',
  }
}
</ns0:fix>
              <ns0:fix complexity="low" disruption="low" id="package_aide_installed" reboot="false" strategy="enable" system="urn:redhat:anaconda:pre">
package --add=aide
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_aide_installed:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_aide_installed_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="aide_build_database" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Build and Test AIDE Database</ns0:title>
              <ns0:description xml:lang="en-US">Run the following command to generate a new database:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo /usr/sbin/aide --init</html:pre>
By default, the database will be written to the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/lib/aide/aide.db.new.gz</html:code>.
Storing the database, the configuration file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/aide.conf</html:code>, and the binary
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/usr/sbin/aide</html:code> (or hashes of these files), in a secure location (such as on read-only media) provides additional assurance about their integrity.
The newly-generated database can be installed as follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo cp /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz</html:pre>
To initiate a manual check, run the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo /usr/sbin/aide --check</html:pre>
If this check produces any unexpected output, investigate.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-3(d)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-3(e)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(d)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(3)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-28</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-7</ns0:reference>
              <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-11.5</ns0:reference>
              <ns0:rationale xml:lang="en-US">
For AIDE to be effective, an initial database of "known-good" information about files
must be captured and it should be able to be verified against the installed files.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="aide_build_database" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">/usr/sbin/aide --init
/bin/cp -p /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-aide_build_database:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-aide_build_database_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="aide_periodic_cron_checking" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Configure Periodic Execution of AIDE</ns0:title>
              <ns0:description xml:lang="en-US">
At a minimum, AIDE should be configured to run a weekly scan. At most, AIDE should be run daily.
To implement a daily execution of AIDE at 4:05am using cron, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/crontab</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">05 4 * * * root /usr/sbin/aide --check</html:pre>
To implement a weekly execution of AIDE at 4:05am using cron, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/crontab</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">05 4 * * 0 root /usr/sbin/aide --check</html:pre>
AIDE can be executed periodically through other means; this is merely one example.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-3(d)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-3(e)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-3(5)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(d)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(3)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-28</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-7</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1744</ns0:reference>
              <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-11.5</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.3.1</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000363-GPOS-00150</ns0:reference>
              <ns0:reference href="">020130</ns0:reference>
              <ns0:rationale xml:lang="en-US">
By default, AIDE does not install itself for periodic execution. Periodically
running AIDE is necessary to reveal unexpected changes in installed files.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Unauthorized changes to the baseline configuration could make the system vulnerable
to various attacks or allow unauthorized access to the operating system. Changes to
operating system configurations can have unintended side effects, some of which may
be relevant to security.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Detecting such changes and providing an automated response can help avoid unintended,
negative consequences that could ultimately affect the security state of the operating
system. The operating system's Information Management Officer (IMO)/Information System
Security Officer (ISSO) and System Administrators (SAs) must be notified via email and/or
monitoring system trap when there is an unauthorized modification of a configuration item.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="aide_periodic_cron_checking" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">echo "05 4 * * * root /usr/sbin/aide --check" &gt;&gt; /etc/crontab
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-aide_periodic_cron_checking:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-aide_periodic_cron_checking_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="aide_scan_notification" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Configure Notification of Post-AIDE Scan Details</ns0:title>
              <ns0:description xml:lang="en-US">
AIDE should notify appropriate personnel of the details of a scan after the scan has been run.
If AIDE has already been configured for periodic execution in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/crontab</html:code>, append the
following line to the existing AIDE line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"> | /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhost</html:pre>
Otherwise, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/crontab</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">05 4 * * * root /usr/sbin/aide --check | /bin/mail -s "$(hostname) - AIDE Integrity Check" root@localhost</html:pre>
AIDE can be executed periodically through other means; this is merely one example.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-3(5)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1744</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000363-GPOS-00150</ns0:reference>
              <ns0:reference href="">020140</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Unauthorized changes to the baseline configuration could make the system vulnerable
to various attacks or allow unauthorized access to the operating system. Changes to
operating system configurations can have unintended side effects, some of which may
be relevant to security.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Detecting such changes and providing an automated response can help avoid unintended,
negative consequences that could ultimately affect the security state of the operating
system. The operating system's Information Management Officer (IMO)/Information System
Security Officer (ISSO) and System Administrators (SAs) must be notified via email and/or
monitoring system trap when there is an unauthorized modification of a configuration item.
</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-aide_scan_notification:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-aide_scan_notification_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="aide_verify_acls" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Configure AIDE to Verify Access Control Lists (ACLs)</ns0:title>
              <ns0:description xml:lang="en-US">
By default, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">acl</html:code> option is added to the <html:code xmlns:html="http://www.w3.org/1999/xhtml">FIPSR</html:code> ruleset in AIDE.
If using a custom ruleset or the <html:code xmlns:html="http://www.w3.org/1999/xhtml">acl</html:code> option is missing, add <html:code xmlns:html="http://www.w3.org/1999/xhtml">acl</html:code>
to the appropriate ruleset.
For example, add <html:code xmlns:html="http://www.w3.org/1999/xhtml">acl</html:code> to the following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/aide.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">FIPSR = p+i+n+u+g+s+m+c+acl+selinux+xattrs+sha256</html:pre>
AIDE rules can be configured in multiple ways; this is merely one example that is already
configured by default.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-7.1</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
              <ns0:reference href="">021600</ns0:reference>
              <ns0:rationale xml:lang="en-US">
ACLs can provide permissions beyond those permitted through the file mode and must be
verified by the file integrity tools.
</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-aide_verify_acls:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-aide_verify_acls_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="aide_verify_ext_attributes" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Configure AIDE to Verify Extended Attributes</ns0:title>
              <ns0:description xml:lang="en-US">
By default, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xattrs</html:code> option is added to the <html:code xmlns:html="http://www.w3.org/1999/xhtml">FIPSR</html:code> ruleset in AIDE.
If using a custom ruleset or the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xattrs</html:code> option is missing, add <html:code xmlns:html="http://www.w3.org/1999/xhtml">xattrs</html:code>
to the appropriate ruleset.
For example, add <html:code xmlns:html="http://www.w3.org/1999/xhtml">xattrs</html:code> to the following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/aide.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">FIPSR = p+i+n+u+g+s+m+c+acl+selinux+xattrs+sha256</html:pre>
AIDE rules can be configured in multiple ways; this is merely one example that is already
configured by default.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-7.1</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
              <ns0:reference href="">021610</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Extended attributes in file systems are used to contain arbitrary data and file metadata
with security implications.
</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-aide_verify_ext_attributes:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-aide_verify_ext_attributes_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="aide_use_fips_hashes" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Configure AIDE to Use FIPS 140-2 for Validating Hashes</ns0:title>
              <ns0:description xml:lang="en-US">
By default, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sha512</html:code> option is added to the <html:code xmlns:html="http://www.w3.org/1999/xhtml">NORMAL</html:code> ruleset in AIDE.
If using a custom ruleset or the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sha512</html:code> option is missing, add <html:code xmlns:html="http://www.w3.org/1999/xhtml">sha512</html:code>
to the appropriate ruleset.
For example, add <html:code xmlns:html="http://www.w3.org/1999/xhtml">sha512</html:code> to the following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/aide.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">NORMAL = FIPSR+sha512</html:pre>
AIDE rules can be configured in multiple ways; this is merely one example that is already
configured by default.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-7.1</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
              <ns0:reference href="">021620</ns0:reference>
              <ns0:rationale xml:lang="en-US">
File integrity tools use cryptographic hashes for verifying file contents and directories
have not been altered. These hashes must be FIPS 140-2 approved cryptographic hashes.
</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-aide_use_fips_hashes:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-aide_use_fips_hashes_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
          </ns0:Group>
          <ns0:Group id="rpm_verification">
            <ns0:title xml:lang="en-US">Verify Integrity with RPM</ns0:title>
            <ns0:description xml:lang="en-US">The RPM package management system includes the ability
to verify the integrity of installed packages by comparing the
installed files with information about the files taken from the
package metadata stored in the RPM database. Although an attacker
could corrupt the RPM database (analogous to attacking the AIDE
database as described above), this check can still reveal
modification of important files. To list which files on the system differ from what is expected by the RPM database:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ rpm -qVa</html:pre>
See the man page for <html:code xmlns:html="http://www.w3.org/1999/xhtml">rpm</html:code> to see a complete explanation of each column.
</ns0:description>
            <ns0:Rule id="rpm_verify_permissions" selected="false" severity="high">
              <ns0:title xml:lang="en-US">Verify and Correct File Permissions with RPM</ns0:title>
              <ns0:description xml:lang="en-US">
Discretionary access control is weakened if a user or group has access
permissions to system files and directories greater than the default.

The RPM package management system can check file access permissions
of installed software packages, including many that are important
to system security.

Verify that the file permissions, ownership, and gruop membership of system files
and commands match vendor values. Check the file permissions, ownership, and group
membership with the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo rpm -Va | grep '^.M'</html:pre>

Output indicates files that do not match vendor defaults. After locating a file with incorrect permissions, run the following command to determine which package owns it:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ rpm -qf <html:i>FILENAME</html:i></html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Next, run the following command to reset its permissions to
the correct values:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo rpm --setperms <html:i>PACKAGENAME</html:i></html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
</ns0:description>
              <ns0:warning category="general" xml:lang="en-US">Note: Due to a bug in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">gdm</html:code> package, the
RPM verify command may continue to fail even after file permissions have been
correctly set on <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log/gdm</html:code>. This is being tracked in Red Hat
Bugzilla #1275532.
</ns0:warning>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9(1)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9(3)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(d)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(3)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1494</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1496</ns0:reference>
              <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-11.5</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.2.6</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.1.3</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.1.4</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.1.5</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.1.6</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.1.7</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.1.8</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.1.9</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.2.3</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000257-GPOS-00098</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000278-GPOS-00108</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Permissions on system binaries and configuration files that are too generous
could allow an unauthorized user to gain privileges that they should not have.
The permissions set by the vendor should be maintained. Any deviations from
this baseline should be investigated.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="rpm_verify_permissions" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
# Declare array to hold list of RPM packages we need to correct permissions for
declare -a SETPERMS_RPM_LIST

# Create a list of files on the system having permissions different from what
# is expected by the RPM database
FILES_WITH_INCORRECT_PERMS=($(rpm -Va --nofiledigest | grep '^.M'))

# For each file path from that list:
# * Determine the RPM package the file path is shipped by,
# * Include it into SETPERMS_RPM_LIST array

for FILE_PATH in "${FILES_WITH_INCORRECT_PERMS[@]}"
do
	RPM_PACKAGE=$(rpm -qf "$FILE_PATH")
	SETPERMS_RPM_LIST=("${SETPERMS_RPM_LIST[@]}" "$RPM_PACKAGE")
done

# Remove duplicate mention of same RPM in $SETPERMS_RPM_LIST (if any)
SETPERMS_RPM_LIST=( $(echo "${SETPERMS_RPM_LIST[@]}" | sort -n | uniq) )

# For each of the RPM packages left in the list -- reset its permissions to the
# correct values
for RPM_PACKAGE in "${SETPERMS_RPM_LIST[@]}"
do
	rpm --setperms "${RPM_PACKAGE}"
done
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-rpm_verify_permissions:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-rpm_verify_permissions_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="rpm_verify_hashes" selected="false" severity="high">
              <ns0:title xml:lang="en-US">Verify File Hashes with RPM</ns0:title>
              <ns0:description xml:lang="en-US">Without cryptographic integrity protections, system
executables and files can be altered by unauthorized users without
detection.

The RPM package management system can check the hashes of
installed software packages, including many that are important to system
security.

To verify that the cryptographic hash of system files and commands match vendor
values, run the following command to list which files on the system
have hashes that differ from what is expected by the RPM database:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ rpm -Va | grep '^..5'</html:pre>

A "c" in the second column indicates that a file is a configuration file, which
may appropriately be expected to change.  If the file was not expected to
change, investigate the cause of the change using audit logs or other means.
The package can then be reinstalled to restore the file.

Run the following command to determine which package owns the file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ rpm -qf <html:i>FILENAME</html:i></html:pre>

The package can be reinstalled from a yum repository using the command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum reinstall <html:i>PACKAGENAME</html:i></html:pre>

Alternatively, the package can be reinstalled from trusted media using the command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo rpm -Uvh <html:i>PACKAGENAME</html:i></html:pre>
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(d)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(3)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-7(1)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">663</ns0:reference>
              <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-11.5</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.2.6</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
              <ns0:rationale xml:lang="en-US">
The hashes of important files like system executables should match the
information given by the RPM database. Executables with erroneous hashes could
be a sign of nefarious activity on the system.</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-rpm_verify_hashes:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-rpm_verify_hashes_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
          </ns0:Group>
        </ns0:Group>
        <ns0:Group id="endpoint_security_software">
          <ns0:title xml:lang="en-US">Endpoint Protection Software</ns0:title>
          <ns0:description xml:lang="en-US">
Endpoint protection security software that is not provided or supported
by Red Hat can be installed to provide complementary or duplicative
security capabilities to those provided by the base platform.  Add-on
software may not be appropriate for some specialized systems.
</ns0:description>
          <ns0:Rule id="install_hids" selected="false" severity="high">
            <ns0:title xml:lang="en-US">Install Intrusion Detection Software</ns0:title>
            <ns0:description xml:lang="en-US">
The base Red Hat platform already includes a sophisticated auditing system that
can detect intruder activity, as well as SELinux, which provides host-based
intrusion prevention capabilities by confining privileged programs and user
sessions which may become compromised.
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note in DoD environments, supplemental intrusion
detection tools, such as the McAfee Host-based Security System, are available
to integrate with existing infrastructure. When these supplemental tools
interfere with proper functioning of SELinux, SELinux takes precedence.</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1263</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-11.4</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Host-based intrusion detection tools provide a system-level defense when an
intruder gains access to a system or network.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-install_hids:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-install_hids_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="install_antivirus" selected="false" severity="high">
            <ns0:title xml:lang="en-US">Install Virus Scanning Software</ns0:title>
            <ns0:description xml:lang="en-US">
Install virus scanning software, which uses signatures to search for the
presence of viruses on the filesystem.
Ensure virus definition files are no older than 7 days, or their last release.

Configure the virus scanning software to perform scans dynamically on all
accessed files.  If this is not possible, configure the
system to scan all altered files on the system on a daily
basis. If the system processes inbound SMTP mail, configure the virus scanner
to scan all received mail.

</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-28</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-3</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1239</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1668</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Virus scanning software can be used to detect if a system has been compromised by
computer viruses, as well as to limit their spread to other systems.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-install_antivirus:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-install_antivirus_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Group id="mcafee_security_software">
            <ns0:title xml:lang="en-US">McAfee Endpoint Security Software</ns0:title>
            <ns0:description xml:lang="en-US">
In DoD environments, McAfee Host-based Security System (HBSS) and
VirusScan Enterprise for Linux (VSEL) is required to be installed on all systems.
</ns0:description>
            <ns0:Rule id="install_mcafee_cma_rt" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Install the McAfee Runtime Libraries and Linux Agent</ns0:title>
              <ns0:description xml:lang="en-US">
Install the McAfee Runtime Libraries (MFErt) and Linux Agent (MFEcma).
</ns0:description>
              <ns0:rationale xml:lang="en-US">
The McAfee Runtime Libraries (MFErt) and Linux Agent (MFEcma) are dependencies
for VirusScan Enterprise for Linux (VSEL) and Host-based Security System (HBSS)
to run.
</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-install_mcafee_cma_rt:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-install_mcafee_cma_rt_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Group id="mcafee_hbss_software">
              <ns0:title xml:lang="en-US">McAfee Host-Based Intrusion Detection Software (HBSS)</ns0:title>
              <ns0:description xml:lang="en-US">
McAfee Host-based Security System (HBSS) is a suite of software applications
used to monitor, detect, and defend computer networks and systems.
</ns0:description>
              <ns0:Rule id="install_mcafee_hbss_hips" selected="false" severity="medium">
                <ns0:title xml:lang="en-US">Install the Host Intrusion Prevention System (HIPS) Module</ns0:title>
                <ns0:description xml:lang="en-US">
Install the McAfee Host Intrusion Prevention System (HIPS) Module if it is absolutely
necessary. If SELinux is enabled, do not install or enable this module.
</ns0:description>
                <ns0:warning category="general" xml:lang="en-US">Installing and enabling this module conflicts with SELinux.
SELinux takes precedence over this module.</ns0:warning>
                <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-7</ns0:reference>
                <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-4(1).1</ns0:reference>
                <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
                <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1263</ns0:reference>
                <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-11.4</ns0:reference>
                <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">STG-OS-000480-GPOS-00227</ns0:reference>
                <ns0:rationale xml:lang="en-US">
Without a host-based intrusion detection tool, there is no system-level defense
when an intruder gains access to a system or network. Additionally, a host-based
intrusion prevention tool can provide methods to immediately lock out detected
intrusion attempts.
</ns0:rationale>
                <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                  <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-install_mcafee_hbss_hips:def:1" />
                </ns0:check>
                <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                  <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-install_mcafee_hbss_hips_ocil:questionnaire:1" />
                </ns0:check>
              </ns0:Rule>
              <ns0:Rule id="install_mcafee_hbss_accm" selected="false" severity="medium">
                <ns0:title xml:lang="en-US">Install the Asset Configuration Compliance Module (ACCM)</ns0:title>
                <ns0:description xml:lang="en-US">
Install the Asset Configuration Compliance Module (ACCM).
</ns0:description>
                <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-7</ns0:reference>
                <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-4(1).1</ns0:reference>
                <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
                <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1263</ns0:reference>
                <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-11.4</ns0:reference>
                <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">STG-OS-000480-GPOS-00227</ns0:reference>
                <ns0:rationale xml:lang="en-US">
Without a host-based intrusion detection tool, there is no system-level defense
when an intruder gains access to a system or network. Additionally, a host-based
intrusion prevention tool can provide methods to immediately lock out detected
intrusion attempts.
</ns0:rationale>
                <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                  <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-install_mcafee_hbss_accm:def:1" />
                </ns0:check>
                <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                  <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-install_mcafee_hbss_accm_ocil:questionnaire:1" />
                </ns0:check>
              </ns0:Rule>
              <ns0:Rule id="install_mcafee_hbss_pa" selected="false" severity="medium">
                <ns0:title xml:lang="en-US">Install the Policy Auditor (PA) Module</ns0:title>
                <ns0:description xml:lang="en-US">
Install the Policy Auditor (PA) Module.
</ns0:description>
                <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-7</ns0:reference>
                <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-4(1).1</ns0:reference>
                <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
                <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1263</ns0:reference>
                <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-11.4</ns0:reference>
                <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">STG-OS-000480-GPOS-00227</ns0:reference>
                <ns0:rationale xml:lang="en-US">
Without a host-based intrusion detection tool, there is no system-level defense
when an intruder gains access to a system or network. Additionally, a host-based
intrusion prevention tool can provide methods to immediately lock out detected
intrusion attempts.
</ns0:rationale>
                <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                  <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-install_mcafee_hbss_pa:def:1" />
                </ns0:check>
                <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                  <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-install_mcafee_hbss_pa_ocil:questionnaire:1" />
                </ns0:check>
              </ns0:Rule>
            </ns0:Group>
            <ns0:Rule id="install_mcafee_antivirus" selected="false" severity="high">
              <ns0:title xml:lang="en-US">Install McAfee Virus Scanning Software</ns0:title>
              <ns0:description xml:lang="en-US">
Install McAfee VirusScan Enterprise for Linux antivirus software
which is provided for DoD systems and uses signatures to search for the
presence of viruses on the filesystem.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-28</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-3</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-3(1)(ii)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1239</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1668</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Virus scanning software can be used to detect if a system has been compromised by
computer viruses, as well as to limit their spread to other systems.
</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-install_mcafee_antivirus:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-install_mcafee_antivirus_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="service_nails_enabled" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Enable nails Service</ns0:title>
              <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nails</html:code> service is used to run McAfee VirusScan Enterprise
for Linux and McAfee Host-based Security System (HBSS) services.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nails</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable nails.service</html:pre>
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-28</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-3</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-3(1)(ii)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1239</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1668</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Virus scanning software can be used to detect if a system has been compromised by
computer viruses, as well as to limit their spread to other systems.
</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_nails_enabled:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_nails_enabled_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="mcafee_antivirus_definitions_updated" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Virus Scanning Software Definitions Are Updated</ns0:title>
              <ns0:description xml:lang="en-US">
Ensure virus definition files are no older than 7 days or their last release.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-28</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-3</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-3(1)(ii)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1239</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1668</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Virus scanning software can be used to detect if a system has been compromised by
computer viruses, as well as to limit their spread to other systems.
</ns0:rationale>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-mcafee_antivirus_definitions_updated_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
          </ns0:Group>
        </ns0:Group>
        <ns0:Group id="fips">
          <ns0:title xml:lang="en-US">Federal Information Processing Standard (FIPS)</ns0:title>
          <ns0:description xml:lang="en-US">
The Federal Information Processing Standard (FIPS) is a computer security standard which
is developed by the U.S. Government and industry working groups to validate the quality
of cryptographic modules. The FIPS standard provides four security levels to ensure
adequate coverage of different industries, implementation of cryptographic modules, and
organizational sizes and requirements.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules
utilize authentication that meets industry and government requirements. For government systems, this allows
Security Levels 1, 2, 3, or 4 for use on Red Hat Enterprise Linux.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
See <html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="http://csrc.nist.gov/publications/PubsFIPS.html">http://csrc.nist.gov/publications/PubsFIPS.html</html:a></html:b> for more information.
</ns0:description>
          <ns0:Rule id="package_dracut-fips_installed" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Install the dracut-fips Package</ns0:title>
            <ns0:description xml:lang="en-US">
To enable FIPS, the system requires that the <html:code xmlns:html="http://www.w3.org/1999/xhtml">dracut-fips</html:code>
package be installed.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">dracut-fips</html:code> package can be installed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install dracut-fips</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(2)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">68</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2450</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000033-GPOS-00014</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000396-GPOS-00176</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000478-GPOS-00223</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to
protect data. The operating system must implement cryptographic modules adhering to the higher
standards approved by the federal government since this provides assurance they have been tested
and validated.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_dracut-fips_installed:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_dracut-fips_installed_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="grub2_enable_fips_mode" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Enable FIPS Mode in GRUB2</ns0:title>
            <ns0:description xml:lang="en-US">
To ensure FIPS mode is enabled, rebuild <html:code xmlns:html="http://www.w3.org/1999/xhtml">initramfs</html:code> by running the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">dracut -f</html:pre>
After the <html:code xmlns:html="http://www.w3.org/1999/xhtml">dracut</html:code> command has been run, add the argument <html:code xmlns:html="http://www.w3.org/1999/xhtml">fips=1</html:code> to the default
GRUB 2 command line for the Linux operating system in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/default/grub</html:code>, in the manner below:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=VolGroup/LogVol06 rd.lvm.lv=VolGroup/lv_swap rhgb quiet rd.shell=0 fips=1"</html:pre>
Finally, rebuild the <html:code xmlns:html="http://www.w3.org/1999/xhtml">grub.cfg</html:code> file by using the
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">grub2-mkconfig -o</html:pre> command as follows:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>On BIOS-based machines, issue the following command as <html:code>root</html:code>:
<html:pre>~]# grub2-mkconfig -o /boot/grub2/grub.cfg</html:pre></html:li><html:li>On UEFI-based machines, issue the following command as <html:code>root</html:code>:
<html:pre>~]# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</html:pre></html:li></html:ul>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Running <html:pre xmlns:html="http://www.w3.org/1999/xhtml">dracut -f</html:pre> will overwrite the existing initramfs file.</ns0:warning>
            <ns0:warning category="general" xml:lang="en-US">The system needs to be rebooted for these changes to take effect.</ns0:warning>
            <ns0:warning category="general" xml:lang="en-US">The ability to enable FIPS does not denote FIPS compliancy or certification.
Red Hat, Inc. and Red Hat Enterprise Linux are respectively FIPS certified and compliant. Community
projects such as CentOS, Scientific Linux, etc. do not necessarily meet FIPS certification and compliancy.
Therefore, non-certified vendors and/or projects do not meet this requirement even if technically feasible.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
See <html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401vend.htm">http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401vend.htm</html:a></html:b> for a list of FIPS certified
vendors.</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(2)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">68</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2450</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000033-GPOS-00014</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000396-GPOS-00176</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000478-GPOS-00223</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to
protect data. The operating system must implement cryptographic modules adhering to the higher
standards approved by the federal government since this provides assurance they have been tested
and validated.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="grub2_enable_fips_mode" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
if grep --silent ^PRELINKING /etc/sysconfig/prelink ; then
        sed -i "s/^PRELINKING.*/PRELINKING=yes/g" /etc/sysconfig/prelink
else
        echo -e "\n# Set PRELINKING to 'yes' per security requirements" &gt;&gt; /etc/sysconfig/prelink
        echo "PRELINKING=yes" &gt;&gt; /etc/sysconfig/prelink
fi

prelink -u -a

dracut -f

if [ -e /sys/firmware/efi ]; then
	BOOT=`df /boot/efi | tail -1 | awk '{print $1 }'`
else
	BOOT=`df /boot | tail -1 | awk '{ print $1 }'`
fi

/sbin/grubby --update-kernel=ALL --args="boot=${BOOT} fips=1"
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-grub2_enable_fips_mode:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-grub2_enable_fips_mode_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="certified-vendor">
          <ns0:title xml:lang="en-US">Operating System Vendor Support and Certification</ns0:title>
          <ns0:description xml:lang="en-US">
The assurance of a vendor to provide operating system support and maintenance
for their product is an important criterion to ensure product stability and
security over the life of the product. A certified product that follows the
necessary standards and government certification requirements guarantees that
known software vulnerabilities will be remediated, and proper guidance for
protecting and securing the operating system will be given.
</ns0:description>
          <ns0:Rule id="installed_OS_is_certified" selected="false" severity="high">
            <ns0:title xml:lang="en-US">The Installed Operating System Is Vendor Supported and Certified</ns0:title>
            <ns0:description xml:lang="en-US">
The installed operating system must be maintained and certified by a vendor.
Red Hat Enterprise Linux is supported by Red Hat, Inc. As the Red Hat Enterprise
Linux vendor, Red Hat, Inc. is responsible for providing security patches as well
as meeting and maintaining goverment certifications and standards.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-2(c)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">
An operating system is considered "supported" if the vendor continues to provide
security patches for the product as well as maintain government certification requirements.
With an unsupported release, it will not be possible to resolve security issue discovered in
the system software as well as meet government certifications.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-installed_OS_is_certified:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-installed_OS_is_certified_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="gnome">
        <ns0:title xml:lang="en-US">GNOME Desktop Environment</ns0:title>
        <ns0:description xml:lang="en-US">
GNOME is a graphical desktop environment bundled with many Linux distributions that
allow users to easily interact with the operating system graphically rather than
textually. The GNOME Graphical Display Manager (GDM) provides login, logout, and user
switching contexts as well as display server management.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
GNOME is developed by the GNOME Project and is considered the default
Red Hat Graphical environment.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For more information on GNOME and the GNOME Project, see <html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="https://www.gnome.org">https://www.gnome.org</html:a></html:b>
</ns0:description>
        <ns0:Rule id="enable_dconf_user_profile" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Configure GNOME3 DConf User Profile</ns0:title>
          <ns0:description xml:lang="en-US">
By default, DConf provides a standard user profile. This profile contains a list
of DConf configuration databases. The user profile and database always take the
highest priority. As such the DConf User profile should always exist and be
configured correctly. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To make sure that the user profile is configured correctly, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/profile/user</html:code> should be set as follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">user-db:user
system-db:local
system-db:site
system-db:distro
</html:pre>
</ns0:description>
          <ns0:rationale xml:lang="en-US">
Failure to have a functional DConf profile prevents GNOME3 configuration settings
from being enforced for all users and allows various security risks.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-enable_dconf_user_profile:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-enable_dconf_user_profile_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="gnome_login_screen">
          <ns0:title xml:lang="en-US">Configure GNOME Login Screen</ns0:title>
          <ns0:description xml:lang="en-US">In the default GNOME3 desktop, the login is displayed after system boot
and can display user accounts, allow users to reboot the system, and allow users to
login automatically and/or with a guest account. The login screen should be configured
to prevent such behavior.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For more information about enforcing preferences in the GNOME3 environment using the DConf
configuration system, see <html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Desktop_Migration_and_Administration_Guide/index.html">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Desktop_Migration_and_Administration_Guide/index.html</html:a></html:b> and the man page <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf(1)</html:code>.
</ns0:description>
          <ns0:Rule id="gnome_gdm_disable_automatic_login" selected="false" severity="high">
            <ns0:title xml:lang="en-US">Disable GDM Automatic Login</ns0:title>
            <ns0:description xml:lang="en-US">The GNOME Display Manager (GDM) can allow users to automatically login without
user interaction or credentials. User should always be required to authenticate themselves
to the system that they are authorized to use. To disable user ability to automatically
login to the system, set the <html:code xmlns:html="http://www.w3.org/1999/xhtml">AutomaticLoginEnable</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">false</html:code> in the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">[daemon]</html:code> section in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/gdm/custom.conf</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[daemon]
AutomaticLoginEnable=false</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00229</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Failure to restrict system access to authenticated users negatively impacts operating
system security.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-gnome_gdm_disable_automatic_login:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-gnome_gdm_disable_automatic_login_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="gnome_gdm_disable_guest_login" selected="false" severity="high">
            <ns0:title xml:lang="en-US">Disable GDM Guest Login</ns0:title>
            <ns0:description xml:lang="en-US">The GNOME Display Manager (GDM) can allow users to login without credentials
which can be useful for public kiosk scenarios. Allowing users to login without credentials
or "guest" account access has inherent security risks and should be disabled. To do disable
timed logins or guest account access, set the <html:code xmlns:html="http://www.w3.org/1999/xhtml">TimedLoginEnable</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">false</html:code> in
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[daemon]</html:code> section in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/gdm/custom.conf</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[daemon]
TimedLoginEnable=false</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00229</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Failure to restrict system access to authenticated users negatively impacts operating
system security.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-gnome_gdm_disable_guest_login:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-gnome_gdm_disable_guest_login_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_disable_user_list" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Disable the GNOME3 Login User List</ns0:title>
            <ns0:description xml:lang="en-US">In the default graphical environment, users logging
directly into the system are greeted with a login screen that displays
all known users. This functionality should be disabled by setting
<html:code xmlns:html="http://www.w3.org/1999/xhtml">disable-user-list</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To disable, add or edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">disable-user-list</html:code> to 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/login-screen]
disable-user-list=true</html:pre>
Once the setting has been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/login-screen/disable-user-list</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-23</ns0:reference>
            <ns0:rationale xml:lang="en-US">Leaving the user list enabled is a security risk since it allows anyone
with physical access to the system to quickly enumerate known user accounts
without logging in.</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_disable_user_list:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_disable_user_list_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_disable_restart_shutdown" selected="false" severity="high">
            <ns0:title xml:lang="en-US">Disable the GNOME3 Login Restart and Shutdown Buttons</ns0:title>
            <ns0:description xml:lang="en-US">In the default graphical environment, users logging
directly into the system are greeted with a login screen that allows
any user, known or unknown, the ability the ability to shutdown or restart
the system. This functionality should be disabled by setting 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">disable-restart-buttons</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To disable, add or edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">disable-restart-buttons</html:code> to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/login-screen]
disable-restart-buttons=true</html:pre>
Once the setting has been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/login-screen/disable-restart-buttons</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">
A user who is at the console can reboot the system at the login screen. If restart or shutdown buttons
are pressed at the login screen, this can create the risk of short-term loss of availability of systems
due to reboot.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_disable_restart_shutdown:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_disable_restart_shutdown_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_enable_smartcard_auth" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Enable the GNOME3 Login Smartcard Authentication</ns0:title>
            <ns0:description xml:lang="en-US">In the default graphical environment, smart card authentication
can be enabled on the login screen by setting <html:code xmlns:html="http://www.w3.org/1999/xhtml">enable-smartcard-authentication</html:code>
to <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To enable, add or edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">enable-smartcard-authentication</html:code> to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/login-screen]
enable-smartcard-authentication=true</html:pre>
Once the setting has been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/login-screen/enable-smartcard-authentication</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">765</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">766</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">767</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">768</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">771</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">772</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">884</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.3</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Smart card login provides two-factor authentication stronger than
that provided by a username and password combination. Smart cards leverage PKI
(public key infrastructure) in order to provide and verify credentials.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_enable_smartcard_auth:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_enable_smartcard_auth_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_login_retries" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set the GNOME3 Login Number of Failures</ns0:title>
            <ns0:description xml:lang="en-US">In the default graphical environment, the GNOME3 login 
screen and be configured to restart the authentication process after 
a configured number of attempts. This can be configured by setting
<html:code xmlns:html="http://www.w3.org/1999/xhtml">allowed-failures</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">3</html:code> or less.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To enable, add or edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">allowed-failures</html:code> to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/login-screen]
allowed-failures=3</html:pre>
Once the setting has been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/login-screen/allowed-failures</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Setting the password retry prompts that are permitted on a per-session basis to a low value
requires some software, such as SSH, to re-connect. This can slow down and
draw additional attention to some types of password-guessing attacks.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_login_retries:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_login_retries_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="gnome_screen_locking">
          <ns0:title xml:lang="en-US">Configure GNOME Screen Locking</ns0:title>
          <ns0:description xml:lang="en-US">In the default GNOME3 desktop, the screen can be locked
by selecting the user name in the far right corner of the main panel and
selecting <html:b xmlns:html="http://www.w3.org/1999/xhtml">Lock</html:b>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The following sections detail commands to enforce idle activation of the screensaver,
screen locking, a blank-screen screensaver, and an idle activation time.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Because users should be trained to lock the screen when they
step away from the computer, the automatic locking feature is only
meant as a backup.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The root account can be screen-locked; however, the root account should
<html:i xmlns:html="http://www.w3.org/1999/xhtml">never</html:i> be used to log into an X Windows environment and should only
be used to for direct login via console in emergency circumstances.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For more information about enforcing preferences in the GNOME3 environment using the DConf
configuration system, see <html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="http://wiki.gnome.org/dconf">http://wiki.gnome.org/dconf</html:a></html:b> and
the man page <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf(1)</html:code>. For Red Hat specific information on configuring DConf
settings, see <html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Desktop_Migration_and_Administration_Guide/part-Configuration_and_Administration.html">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Desktop_Migration_and_Administration_Guide/part-Configuration_and_Administration.html</html:a></html:b>
</ns0:description>
          <ns0:Value id="inactivity_timeout_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">Inactivity timeout</ns0:title>
            <ns0:description xml:lang="en-US">Choose allowed duration of inactive SSH connections, shells, and X sessions</ns0:description>
            <ns0:value>900</ns0:value>
            <ns0:value selector="5_minutes">300</ns0:value>
            <ns0:value selector="10_minutes">600</ns0:value>
            <ns0:value selector="15_minutes">900</ns0:value>
          </ns0:Value>
          <ns0:Rule id="dconf_gnome_screensaver_idle_delay" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set GNOME3 Screensaver Inactivity Timeout</ns0:title>
            <ns0:description xml:lang="en-US">
The idle time-out value for inactivity in the GNOME3 desktop is configured via the <html:code xmlns:html="http://www.w3.org/1999/xhtml">idle-delay</html:code>
setting must be set under an appropriate configuration file(s) in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d</html:code> directory
and locked in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks</html:code> directory to prevent user modification.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For example, to configure the system for a 15 minute delay, add the following to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/desktop/session]
idle-delay=900</html:pre>
Once the setting has been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/session/idle-delay</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-11(a)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">57</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.1.8</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000029-GPOS-00010</ns0:reference>
            <ns0:rationale xml:lang="en-US">
A session time-out lock is a temporary action taken when a user stops work and moves away from
the immediate physical vicinity of the information system but does not logout because of the
temporary nature of the absence. Rather than relying on the user to manually lock their operating
system session prior to vacating the vicinity, GNOME3 can be configured to identify when
a user's session has idled and take action to initiate a session lock.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="dconf_gnome_screensaver_idle_delay" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
inactivity_timeout_value="<ns0:sub idref="inactivity_timeout_value" />"

# Define constants to be reused below
ORG_GNOME_DESKTOP_SESSION="org/gnome/desktop/session"
SSG_DCONF_IDLE_DELAY_FILE="/etc/dconf/db/local.d/10-scap-security-guide"
SESSION_LOCKS_FILE="/etc/dconf/db/local.d/locks/session"
IDLE_DELAY_DEFINED="FALSE"

# First update '[org/gnome/desktop/session] idle-delay' settings in
# /etc/dconf/db/local.d/* if already defined
for FILE in /etc/dconf/db/local.d/*
do
	if grep -q -d skip "$ORG_GNOME_DESKTOP_SESSION" "$FILE"
	then
		if grep 'idle-delay' "$FILE"
		then
			sed -i "s/idle-delay=.*/idle-delay=uint32 ${inactivity_timeout_value}/g" "$FILE"
			IDLE_DELAY_DEFINED="TRUE"
		fi
	fi
done

# Then define '[org/gnome/desktop/session] idle-delay' setting
# if still not defined yet
if [ "$IDLE_DELAY_DEFINED" != "TRUE" ]
then
	echo "" &gt;&gt; $SSG_DCONF_IDLE_DELAY_FILE
	echo "[org/gnome/desktop/session]" &gt;&gt;  $SSG_DCONF_IDLE_DELAY_FILE
	echo "idle-delay=uint32 ${inactivity_timeout_value}" &gt;&gt; $SSG_DCONF_IDLE_DELAY_FILE
fi

# Verify if 'idle-delay' modification is locked. If not, lock it
if ! grep -q "^/${ORG_GNOME_DESKTOP_SESSION}/idle-delay$" /etc/dconf/db/local.d/locks/*
then
	# Check if "$SESSION_LOCK_FILE" exists. If not, create it.
	if [ ! -f "$SESSION_LOCKS_FILE" ]
	then
		touch "$SESSION_LOCKS_FILE"
	fi
	echo "/${ORG_GNOME_DESKTOP_SESSION}/idle-delay" &gt;&gt; "$SESSION_LOCKS_FILE"
fi

</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-inactivity_timeout_value:var:1" value-id="inactivity_timeout_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_screensaver_idle_delay:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_screensaver_idle_delay_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_screensaver_idle_activation_enabled" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Enable GNOME3 Screensaver Idle Activation</ns0:title>
            <ns0:description xml:lang="en-US">
To activate the screensaver in the GNOME3 desktop after a period of inactivity,
add or set <html:code xmlns:html="http://www.w3.org/1999/xhtml">idle-activation-enabled</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code> in 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/desktop/screensaver]
idle_activation_enabled=true</html:pre>
Once the setting has been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/screensaver/idle-activation-enabled</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-11(a)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">57</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000029-GPOS-00010</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.1.8</ns0:reference>
            <ns0:rationale xml:lang="en-US">
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate
physical vicinity of the information system but does not logout because of the temporary nature of the absence.
Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity,
GNOME desktops can be configured to identify when a user's session has idled and take action to initiate the
session lock.

Enabling idle activation of the screensaver ensures the screensaver will
be activated after the idle delay.  Applications requiring continuous,
real-time screen display (such as network management products) require the
login session does not have administrator rights and the display station is located in a
controlled-access area.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="dconf_gnome_screensaver_idle_activation_enabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
# Define constants to be reused below
ORG_GNOME_DESKTOP_SCREENSAVER="org/gnome/desktop/screensaver"
SSG_DCONF_IDLE_ACTIVATION_FILE="/etc/dconf/db/local.d/10-scap-security-guide"
SCREENSAVER_LOCKS_FILE="/etc/dconf/db/local.d/locks/screensaver"
IDLE_ACTIVATION_DEFINED="FALSE"

# First update '[org/gnome/desktop/screensaver] idle-activation-enabled' settings in
# /etc/dconf/db/local.d/* if already defined
for FILE in /etc/dconf/db/local.d/*
do
	if grep -q -d skip "$ORG_GNOME_DESKTOP_SCREENSAVER" "$FILE"
	then
		if grep 'idle-activation-enabled' "$FILE"
		then
			sed -i "s/idle-activation-enabled=.*/idle-activation-enabled=true/g" "$FILE"
			IDLE_ACTIVATION_DEFINED="TRUE"
		fi
	fi
done

# Then define '[org/gnome/desktop/screensaver] idle-activation-enabled' setting
# if still not defined yet
if [ "$IDLE_ACTIVATION_DEFINED" != "TRUE" ]
then
	echo "" &gt;&gt; $SSG_DCONF_IDLE_ACTIVATION_FILE
	echo "[org/gnome/desktop/screensaver]" &gt;&gt;  $SSG_DCONF_IDLE_ACTIVATION_FILE
	echo "idle-activation-enabled=true" &gt;&gt; $SSG_DCONF_IDLE_ACTIVATION_FILE
fi

# Verify if 'idle-activation-enabled' modification is locked. If not, lock it
if ! grep -q "^/${ORG_GNOME_DESKTOP_SCREENSAVER}/idle-activation-enabled$" /etc/dconf/db/local.d/locks/*
then
	# Check if "$SCREENSAVER_LOCK_FILE" exists. If not, create it.
	if [ ! -f "$SCREENSAVER_LOCKS_FILE" ]
	then
		touch "$SCREENSAVER_LOCKS_FILE"
	fi
	echo "/${ORG_GNOME_DESKTOP_SCREENSAVER}/idle-activation-enabled" &gt;&gt; "$SCREENSAVER_LOCKS_FILE"
fi

</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_screensaver_idle_activation_enabled:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_screensaver_idle_activation_enabled_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_screensaver_lock_enabled" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Enable GNOME3 Screensaver Lock After Idle Period</ns0:title>
            <ns0:description xml:lang="en-US">
To activate locking of the screensaver in the GNOME3 desktop when it is activated,
add or set <html:code xmlns:html="http://www.w3.org/1999/xhtml">lock-enabled</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/desktop/screensaver]
lock-enabled=true
</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/screensaver/lock-enabled</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-11(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">56</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.1.8</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000028-GPOS-00009</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">OS-SRG-000030-GPOS-00011</ns0:reference>
            <ns0:rationale xml:lang="en-US">
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity
of the information system but does not want to logout because of the temporary nature of the absense.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="dconf_gnome_screensaver_lock_enabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
# Define constants to be reused below
ORG_GNOME_DESKTOP_SCREENSAVER="org/gnome/desktop/screensaver"
SSG_DCONF_LOCK_ENABLED_FILE="/etc/dconf/db/local.d/10-scap-security-guide"
SCREENSAVER_LOCKS_FILE="/etc/dconf/db/local.d/locks/screensaver"
LOCK_ENABLED_DEFINED="FALSE"
LOCK_DELAY_DEFINED="FALSE"

# First update '[org/gnome/desktop/screensaver] lock-enabled' and
# '[org/gnome/desktop/screensaver] lock-delay' settings in
# /etc/dconf/db/local.d/* if already defined
for FILE in /etc/dconf/db/local.d/*
do
	if grep -q -d skip "$ORG_GNOME_DESKTOP_SCREENSAVER" "$FILE"
	then
		if grep 'lock-enabled' "$FILE"
		then
			sed -i "s/lock-enabled=.*/lock-enabled=true/g" "$FILE"
			LOCK_ENABLED_DEFINED="TRUE"
		fi
		if grep 'lock-delay' "$FILE"
		then
			sed -i "s/lock-delay=.*/lock-delay=uint32 0/g" "$FILE"
			LOCK_DELAY_DEFINED="TRUE"
		fi
	fi
done

# Then define '[org/gnome/desktop/screensaver] lock-enabled' setting
# if still not defined yet
if [ "$LOCK_ENABLED_DEFINED" != "TRUE" ] || [ "$LOCK_DELAY_DEFINED" != "TRUE" ]
then
	echo "" &gt;&gt; $SSG_DCONF_LOCK_ENABLED_FILE
	echo "[org/gnome/desktop/screensaver]" &gt;&gt;  $SSG_DCONF_LOCK_ENABLED_FILE
	echo "lock-enabled=true" &gt;&gt; $SSG_DCONF_LOCK_ENABLED_FILE
	echo "lock-delay=uint32 0" &gt;&gt; $SSG_DCONF_LOCK_ENABLED_FILE
fi

# Verify if 'lock-enabled' modification is locked. If not, lock it
if ! grep -q "^/${ORG_GNOME_DESKTOP_SCREENSAVER}/lock-enabled$" /etc/dconf/db/local.d/locks/*
then
	# Check if "$SCREENSAVER_LOCK_FILE" exists. If not, create it.
	if [ ! -f "$SCREENSAVER_LOCKS_FILE" ]
	then
		touch "$SCREENSAVER_LOCKS_FILE"
	fi
	echo "/${ORG_GNOME_DESKTOP_SCREENSAVER}/lock-enabled" &gt;&gt; "$SCREENSAVER_LOCKS_FILE"
fi


# Verify if 'lock-delay' modification is locked. If not, lock it
if ! grep -q "^/${ORG_GNOME_DESKTOP_SCREENSAVER}/lock-delay$" /etc/dconf/db/local.d/locks/*
then
        # Check if "$SCREENSAVER_LOCK_FILE" exists. If not, create it.
        if [ ! -f "$SCREENSAVER_LOCKS_FILE" ]
        then
                touch "$SCREENSAVER_LOCKS_FILE"
        fi
        echo "/${ORG_GNOME_DESKTOP_SCREENSAVER}/lock-delay" &gt;&gt; "$SCREENSAVER_LOCKS_FILE"
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_screensaver_lock_enabled:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_screensaver_lock_enabled_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_screensaver_lock_delay" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set GNOME3 Screensaver Lock Delay After Activation Period</ns0:title>
            <ns0:description xml:lang="en-US">
To activate the locking delay of the screensaver in the GNOME3 desktop when 
the screensaver is activated, add or set <html:code xmlns:html="http://www.w3.org/1999/xhtml">lock-delay</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">uint32 0</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/desktop/screensaver]
lock-delay=uint32 0
</html:pre>
Once the setting has been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/screensaver/lock-delay</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-11(a)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">56</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.1.8</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">OS-SRG-000029-GPOS-00010</ns0:reference>
            <ns0:rationale xml:lang="en-US">
A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity
of the information system but does not want to logout because of the temporary nature of the absense.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_screensaver_lock_delay:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_screensaver_lock_delay_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_screensaver_mode_blank" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Implement Blank Screensaver</ns0:title>
            <ns0:description xml:lang="en-US">
To set the screensaver mode in the GNOME3 desktop to a blank screen,
add or set <html:code xmlns:html="http://www.w3.org/1999/xhtml">picture-uri</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">''</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/desktop/screensaver]
picture-uri=''
</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/screensaver/picture-uri</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-11(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">60</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.1.8</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Setting the screensaver mode to blank-only conceals the
contents of the display from passersby.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="dconf_gnome_screensaver_mode_blank" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
# Define constants to be reused below
ORG_GNOME_DESKTOP_SCREENSAVER="org/gnome/desktop/screensaver"
SSG_DCONF_MODE_BLANK_FILE="/etc/dconf/db/local.d/10-scap-security-guide"
SCREENSAVER_LOCKS_FILE="/etc/dconf/db/local.d/locks/screensaver"
MODE_BLANK_DEFINED="FALSE"

# First update '[org/gnome/desktop/screensaver] picture-uri' settings in
# /etc/dconf/db/local.d/* if already defined
for FILE in /etc/dconf/db/local.d/*
do
	if grep -q -d skip "$ORG_GNOME_DESKTOP_SCREENSAVER" "$FILE"
	then
		if grep 'picture-uri' "$FILE"
		then
			sed -i "s/picture-uri=.*/picture-uri=string ''/g" "$FILE"
			MODE_BLANK_DEFINED="TRUE"
		fi
	fi
done

# Then define '[org/gnome/desktop/screensaver] picture-uri' setting
# if still not defined yet
if [ "$MODE_BLANK_DEFINED" != "TRUE" ]
then
	echo "" &gt;&gt; $SSG_DCONF_MODE_BLANK_FILE
	echo "[org/gnome/desktop/screensaver]" &gt;&gt;  $SSG_DCONF_MODE_BLANK_FILE
	echo "picture-uri=string ''" &gt;&gt; $SSG_DCONF_MODE_BLANK_FILE
fi

# Verify if 'picture-uri' modification is locked. If not, lock it
if ! grep -q "^/${ORG_GNOME_DESKTOP_SCREENSAVER}/picture-uri$" /etc/dconf/db/local.d/locks/*
then
	# Check if "$SCREENSAVER_LOCK_FILE" exists. If not, create it.
	if [ ! -f "$SCREENSAVER_LOCKS_FILE" ]
	then
		touch "$SCREENSAVER_LOCKS_FILE"
	fi
	echo "/${ORG_GNOME_DESKTOP_SCREENSAVER}/picture-uri" &gt;&gt; "$SCREENSAVER_LOCKS_FILE"
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_screensaver_mode_blank:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_screensaver_mode_blank_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_screensaver_user_info" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable Full User Name on Splash Shield</ns0:title>
            <ns0:description xml:lang="en-US">
By default when the screen is locked, the splash shield will show the user's
full name. This should be disabled to prevent casual observers from seeing
who has access to the system. This can be disabled by adding or setting
<html:code xmlns:html="http://www.w3.org/1999/xhtml">show-full-name-in-top-bar</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">false</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/desktop/screensaver]
show-full-name-in-top-bar=false
</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/screensaver/show-full-name-in-top-bar</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Setting the splash screen to not reveal the logged in user's name
conceals who has access to the system from passersby.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_screensaver_user_info:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_screensaver_user_info_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_session_user_locks" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Ensure Users Cannot Change GNOME3 Session Settings</ns0:title>
            <ns0:description xml:lang="en-US">
If not already configured, ensure that users cannot change GNOME3 session idle and lock settings
by adding <html:code xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/screensaver/lock-delay</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/session/idle-delay</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/screensaver/lock-delay
/org/gnome/desktop/session/idle-delay</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-11(a)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">57</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-00029-GPOS-0010</ns0:reference>
            <ns0:rationale xml:lang="en-US">
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate
physical vicinity of the information system but does not logout because of the temporary nature of the absence.
Rather than relying on the user to manually lock their operating system session prior to vacating the vicinity,
GNOME desktops can be configured to identify when a user's session has idled and take action to initiate the
session lock. As such, users should not be allowed to change session settings.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_session_user_locks:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_session_user_locks_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="gnome_system_settings">
          <ns0:title xml:lang="en-US">GNOME System Settings</ns0:title>
          <ns0:description xml:lang="en-US">
GNOME provides configuration and functionality to a graphical desktop environment
that changes grahical configurations or allow a user to perform
actions that users normally would not be able to do in non-graphical mode such as
remote access configuration, power policies, Geo-location, etc.
Configuring such settings in GNOME will prevent accidential graphical configuration
changes by users from taking place.
</ns0:description>
          <ns0:Rule id="dconf_gnome_disable_ctrlaltdel_reboot" selected="false" severity="high">
            <ns0:title xml:lang="en-US">Disable Ctrl-Alt-Del Reboot Key Sequence in GNOME3</ns0:title>
            <ns0:description xml:lang="en-US">
By default, <html:code xmlns:html="http://www.w3.org/1999/xhtml">GNOME</html:code> will reboot the system if the <html:code xmlns:html="http://www.w3.org/1999/xhtml">Ctrl-Alt-Del</html:code>
key sequence is pressed.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To configure the system to ignore the <html:code xmlns:html="http://www.w3.org/1999/xhtml">Ctrl-Alt-Del</html:code> key sequence from the
Graphical User Interface (GUI) instead of rebooting the system, add or set 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">logout</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">''</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/settings-daemon/plugins/media-keys]
logout=''
</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/settings-daemon/plugins/media-keys/logout</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">
A locally logged-in user who presses Ctrl-Alt-Del, when at the console,
can reboot the system. If accidentally pressed, as could happen in
the case of mixed OS environment, this can create the risk of short-term
loss of availability of systems due to unintentional reboot.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_disable_ctrlaltdel_reboot:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_disable_ctrlaltdel_reboot_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_disable_user_admin" selected="false" severity="high">
            <ns0:title xml:lang="en-US">Disable User Administration in GNOME3</ns0:title>
            <ns0:description xml:lang="en-US">
By default, <html:code xmlns:html="http://www.w3.org/1999/xhtml">GNOME</html:code> will allow all users to have some administratrion
capability. This should be disabled so that non-administrative users are not making
configuration changes. To configure the system to disable user administration
capability in the Graphical User Interface (GUI), add or set
<html:code xmlns:html="http://www.w3.org/1999/xhtml">user-administration-disabled</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/desktop/lockdown]
user-administration-disabled=true
</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/lockdown/user-administration-disabled</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Allowing all users to have some administratrive capabilities to the system through
the Graphical User Interface (GUI) when they would not have them otherwise could allow
unintended configuration changes as well as a nefarious user the capability to make system
changes such as adding new accounts, etc.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_disable_user_admin:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_disable_user_admin_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_disable_power_settings" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Disable Power Settings in GNOME3</ns0:title>
            <ns0:description xml:lang="en-US">
By default, <html:code xmlns:html="http://www.w3.org/1999/xhtml">GNOME</html:code> enables a power profile designed for mobile devices
with battery usage. While useful for mobile devices, this setting should be disabled
for all other systems. To configure the system to disable the power setting, add or set
<html:code xmlns:html="http://www.w3.org/1999/xhtml">active</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">false</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/settings-daemon/plugins/power]
active=false
</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/settings-daemon/plugins/power</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Power settings should not be enabled on systems that are not mobile devices.
Enabling power settings on non-mobile devices could have unintended processing
consequences on standard systems.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_disable_power_settings:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_disable_power_settings_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_disable_geolocation" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Disable Geolocation in GNOME3</ns0:title>
            <ns0:description xml:lang="en-US"><html:code xmlns:html="http://www.w3.org/1999/xhtml">GNOME</html:code> allows the clock and applications to track and access location 
information. This setting should be disabled as applications should not track
system location. To configure the system to disable location tracking, add or set
<html:code xmlns:html="http://www.w3.org/1999/xhtml">enabled</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">false</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/system/location]
enabled=false
</html:pre>
To configure the clock to disable location tracking, add or set
<html:code xmlns:html="http://www.w3.org/1999/xhtml">geolocation</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">false</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/clocks]
geolocation=false
</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/system/location/enabled
/org/gnome/clocks/geolocation</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Power settings should not be enabled on systems that are not mobile devices.
Enabling power settings on non-mobile devices could have unintended processing
consequences on standard systems.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_disable_geolocation:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_disable_geolocation_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="gnome_network_settings">
          <ns0:title xml:lang="en-US">GNOME Network Settings</ns0:title>
          <ns0:description xml:lang="en-US">
GNOME network settings that apply to the graphical interface.
</ns0:description>
          <ns0:Rule id="dconf_gnome_disable_wifi_create" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Disable WIFI Network Connection Creation in GNOME3</ns0:title>
            <ns0:description xml:lang="en-US"><html:code xmlns:html="http://www.w3.org/1999/xhtml">GNOME</html:code> allows users to create ad-hoc wireless connections through the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">NetworkManager</html:code> applet. Wireless connections should be disabled by
adding or setting <html:code xmlns:html="http://www.w3.org/1999/xhtml">disable-wifi-create</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/nm-applet]
disable-wifi-create=true
</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/nm-applet/disable-wifi-create</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Wireless network connections should not be allowed to be configured by general
users on a given system as it could open the system to backdoor attacks.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_disable_wifi_create:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_disable_wifi_create_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_disable_wifi_notification" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Disable WIFI Network Notification in GNOME3</ns0:title>
            <ns0:description xml:lang="en-US">
By default, <html:code xmlns:html="http://www.w3.org/1999/xhtml">GNOME</html:code> disables WIFI notification. This should be permanently set
so that users do not connect to a wireless network when the system finds one.
While useful for mobile devices, this setting should be disabled for all other systems.
To configure the system to disable the WIFI notication, add or set
<html:code xmlns:html="http://www.w3.org/1999/xhtml">suppress-wireless-networks-available</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/nm-applet]
suppress-wireless-networks-available=true
</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/nm-applet/suppress-wireless-networks-available</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Wireless network connections should not be allowed to be configured by general
users on a given system as it could open the system to backdoor attacks.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_disable_wifi_notification:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_disable_wifi_notification_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="gnome_remote_access_settings">
          <ns0:title xml:lang="en-US">GNOME Remote Access Settings</ns0:title>
          <ns0:description xml:lang="en-US">
GNOME remote access settings that apply to the graphical interface.
</ns0:description>
          <ns0:Rule id="dconf_gnome_remote_access_credential_prompt" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Require Credential Prompting for Remote Access in GNOME3</ns0:title>
            <ns0:description xml:lang="en-US">
By default, <html:code xmlns:html="http://www.w3.org/1999/xhtml">GNOME</html:code> does not require credentials when using <html:code xmlns:html="http://www.w3.org/1999/xhtml">Vino</html:code> for
remote access. To configure the system to require remote credentials, add or set
<html:code xmlns:html="http://www.w3.org/1999/xhtml">authentication-methods</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">['vnc']</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/Vino]
authentication-methods=['vnc']
</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/Vino/authentication-methods</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Username and password prompting is required for remote access. Otherwise, non-authorized
and nefarious users can access the system freely.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_remote_access_credential_prompt:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_remote_access_credential_prompt_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_remote_access_encryption" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Require Encryption for Remote Access in GNOME3</ns0:title>
            <ns0:description xml:lang="en-US">
By default, <html:code xmlns:html="http://www.w3.org/1999/xhtml">GNOME</html:code> requires encryption when using <html:code xmlns:html="http://www.w3.org/1999/xhtml">Vino</html:code> for remote access.
To prevent remote access encryption from being disabled, add or set
<html:code xmlns:html="http://www.w3.org/1999/xhtml">require-encryption</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code> in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/Vino]
require-encryption=true
</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/Vino/require-encryption</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-2(1)(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Open X displays allow an attacker to capture keystrokes and to execute commands
remotely.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_remote_access_encryption:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_remote_access_encryption_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="gnome_media_settings">
          <ns0:title xml:lang="en-US">GNOME Media Settings</ns0:title>
          <ns0:description xml:lang="en-US">
GNOME media settings that apply to the graphical interface.
</ns0:description>
          <ns0:Rule id="dconf_gnome_disable_automount" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable GNOME3 Automounting</ns0:title>
            <ns0:description xml:lang="en-US">The system's default desktop environment, GNOME3, will mount
devices and removable media (such as DVDs, CDs and USB flash drives) whenever
they are inserted into the system. To disable automount and autorun within GNOME3, add or set
<html:code xmlns:html="http://www.w3.org/1999/xhtml">automount</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">false</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">automount-open</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">false</html:code>, and
<html:code xmlns:html="http://www.w3.org/1999/xhtml">autorun-never</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code> in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/desktop/media-handling]
automount=false
automount-open=false
autorun-never=true</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/media-handling/automount
/org/gnome/desktop/media-handling/auto-open
/org/gnome/desktop/media-handling/autorun-never</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(e)</ns0:reference>
            <ns0:rationale xml:lang="en-US">Disabling automatic mounting in GNOME3 can prevent
the introduction of malware via removable media.
It will, however, also prevent desktop users from legitimate use
of removable media.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_disable_automount:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_disable_automount_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_disable_thumbnailers" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable All GNOME3 Thumbnailers</ns0:title>
            <ns0:description xml:lang="en-US">The system's default desktop environment, GNOME3, uses
a number of different thumbnailer programs to generate thumbnails
for any new or modified content in an opened folder. To disable the
execution of these thumbnail applications, add or set <html:code xmlns:html="http://www.w3.org/1999/xhtml">disable-all</html:code>
to <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code> in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/00-security-settings</html:code>.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[org/gnome/desktop/thumbnailers]
disable-all=true</html:pre>
Once the settings have been added, add a lock to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/local.d/locks/00-security-settings-lock</html:code> to prevent user modification.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/org/gnome/desktop/thumbnailers/disable-all</html:pre>
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
This effectively prevents an attacker from gaining access to a
system through a flaw in GNOME3's Nautilus thumbnail creators.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:rationale xml:lang="en-US">An attacker with knowledge of a flaw in a GNOME3 thumbnailer application could craft a malicious
file to exploit this flaw. Assuming the attacker could place the malicious file on the local filesystem
(via a web upload for example) and assuming a user browses the same location using Nautilus, the
malicious file would exploit the thumbnailer with the potential for malicious code execution. It
is best to disable these thumbnailer applications unless they are explicitly required.</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_disable_thumbnailers:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_disable_thumbnailers_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="sudo">
        <ns0:title xml:lang="en-US">Sudo</ns0:title>
        <ns0:description xml:lang="en-US"><html:code xmlns:html="http://www.w3.org/1999/xhtml">Sudo</html:code>, which stands for "su 'do'", provides the ability to delegate authority
to certain users, groups of users, or system administrators. When configured for system 
users and/or groups, <html:code xmlns:html="http://www.w3.org/1999/xhtml">Sudo</html:code> can allow a user or group to execute privileged commands
that normally only <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code> is allowed to execute.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For more information on <html:code xmlns:html="http://www.w3.org/1999/xhtml">Sudo</html:code> and addition <html:code xmlns:html="http://www.w3.org/1999/xhtml">Sudo</html:code> configuration options, see
<html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="https://www.sudo.ws">https://www.sudo.ws</html:a></html:b>
</ns0:description>
        <ns0:Rule id="sudo_remove_nopasswd" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure Users Re-Authenticate for Privilege Escalation - sudo NOPASSWD</ns0:title>
          <ns0:description xml:lang="en-US">
The sudo <html:code xmlns:html="http://www.w3.org/1999/xhtml">NOPASSWD</html:code> tag, when specified, allows a user to execute commands using
sudo without having to authenticate. This should be disabled by making sure that the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">NOPASSWD</html:code> tag does not exist in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sudoers</html:code> configuration file or 
any sudo configuration snippets in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sudoers.d/</html:code>.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-11</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2038</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000373-GPOS-00156</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000373-GPOS-00157</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000373-GPOS-00158</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Without re-authentication, users may access resources or perform tasks for which they
do not have authorization.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
When operating systems provide the capability to escalate a functional capability, it
is critical that the user re-authenticate.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sudo_remove_nopasswd:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sudo_remove_nopasswd_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sudo_remove_no_authenticate" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure Users Re-Authenticate for Privilege Escalation - sudo !authenticate</ns0:title>
          <ns0:description xml:lang="en-US">
The sudo <html:code xmlns:html="http://www.w3.org/1999/xhtml">!authenticate</html:code> option, when specified, allows a user to execute commands using
sudo without having to authenticate. This should be disabled by making sure that the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">!authenticate</html:code> option does not exist in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sudoers</html:code> configuration file or
any sudo configuration snippets in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sudoers.d/</html:code>.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-11</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2038</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000373-GPOS-00156</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000373-GPOS-00157</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000373-GPOS-00158</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Without re-authentication, users may access resources or perform tasks for which they
do not have authorization.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
When operating systems provide the capability to escalate a functional capability, it
is critical that the user re-authenticate.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sudo_remove_no_authenticate:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sudo_remove_no_authenticate_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="permissions">
      <ns0:title xml:lang="en-US">File Permissions and Masks</ns0:title>
      <ns0:description xml:lang="en-US">Traditional Unix security relies heavily on file and
directory permissions to prevent unauthorized users from reading or
modifying files to which they should not have access. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Several of the commands in this section search filesystems
for files or directories with certain characteristics, and are
intended to be run on every local partition on a given system.
When the variable <html:i xmlns:html="http://www.w3.org/1999/xhtml">PART</html:i> appears in one of the commands below,
it means that the command is intended to be run repeatedly, with the
name of each local partition substituted for <html:i xmlns:html="http://www.w3.org/1999/xhtml">PART</html:i> in turn.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The following command prints a list of all xfs partitions on the local
system, which is the default filesystem for Red Hat Enterprise Linux
7 installations:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ mount -t xfs | awk '{print $3}'</html:pre>
For any systems that use a different
local filesystem type, modify this command as appropriate.
</ns0:description>
      <ns0:Group id="partitions">
        <ns0:title xml:lang="en-US">Restrict Partition Mount Options</ns0:title>
        <ns0:description xml:lang="en-US">System partitions can be mounted with certain options
that limit what files on those partitions can do. These options
are set in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> configuration file, and can be
used to make certain types of malicious behavior more difficult.</ns0:description>
        <ns0:Value id="var_removable_partition" operator="equals" type="string">
          <ns0:title xml:lang="en-US">Removable Partition</ns0:title>
          <ns0:description xml:lang="en-US">This value is used by the checks mount_option_nodev_removable_partitions, mount_option_nodev_removable_partitions,
and mount_option_nodev_removable_partitions to ensure that the correct mount options are set on partitions mounted from
removable media such as CD-ROMs, USB keys, and floppy drives. This value should be modified to reflect any removable
partitions that are required on the local system.</ns0:description>
          <ns0:value selector="dev_cdrom">/dev/cdrom</ns0:value>
        </ns0:Value>
        <ns0:Rule id="mount_option_nodev_nonroot_local_partitions" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Add nodev Option to Non-Root Local Partitions</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> mount option prevents files from being
interpreted as character or block devices. 
Legitimate character and block devices should exist only in
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev</html:code> directory on the root partition or within chroot
jails built for system services.

	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	any non-root local partitions.
	
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.11</ns0:reference>
          <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> mount option prevents files from being
interpreted as character or block devices. The only legitimate location
for device files is the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev</html:code> directory located on the root partition.
The only exception to this is chroot jails, for which it is not advised
to set <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> on these filesystems.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_nodev_nonroot_local_partitions:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="mount_option_nodev_removable_partitions" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Add nodev Option to Removable Media Partitions</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> mount option prevents files from being
interpreted as character or block devices.
Legitimate character and block devices should exist only in
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev</html:code> directory on the root partition or within chroot
jails built for system services.

	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	any removable media partitions.
	
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(e)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MP-2</ns0:reference>
          <ns0:rationale xml:lang="en-US">The only legitimate location for device files is the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev</html:code> directory
located on the root partition. An exception to this is chroot jails, and it is
not advised to set <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> on partitions which contain their root
filesystems.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_removable_partition:var:1" value-id="var_removable_partition" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_nodev_removable_partitions:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="mount_option_noexec_removable_partitions" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Add noexec Option to Removable Media Partitions</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">noexec</html:code> mount option prevents the direct
execution of binaries on the mounted filesystem. 
Preventing the direct execution of binaries from removable media (such as a USB
key) provides a defense against malicious software that may be present on such
untrusted media.

	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">noexec</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	any removable media partitions.
	
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(e)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MP-2</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">87</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.12</ns0:reference>
          <ns0:rationale xml:lang="en-US">Allowing users to execute binaries from removable media such as USB keys exposes
the system to potential compromise.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_removable_partition:var:1" value-id="var_removable_partition" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_noexec_removable_partitions:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-mount_option_noexec_removable_partitions_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="mount_option_nosuid_removable_partitions" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Add nosuid Option to Removable Media Partitions</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nosuid</html:code> mount option prevents set-user-identifier (SUID)
and set-group-identifier (SGID) permissions from taking effect. These permissions
allow users to execute binaries with the same permissions as the owner and group
of the file respectively. Users should not be allowed to introduce SUID and SGID
files into the system via partitions mounted from removeable media.

	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nosuid</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	any removable media partitions.
	
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(e)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MP-2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.13</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">The presence of SUID and SGID executables should be tightly controlled. Allowing
users to introduce SUID or SGID binaries from partitions mounted off of
removable media would allow them to introduce their own highly-privileged programs.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_removable_partition:var:1" value-id="var_removable_partition" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_nosuid_removable_partitions:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="mount_option_tmp_nodev" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Add nodev Option to /tmp</ns0:title>
          <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> mount option can be used to prevent device files from
being created in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code>.
Legitimate character and block devices should not exist
within temporary directories like <html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code>. 

	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code>.
	
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MP-2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.2</ns0:reference>
          <ns0:rationale xml:lang="en-US">The only legitimate location for device files is the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev</html:code> directory
located on the root partition. The only exception to this is chroot jails.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="mount_option_tmp_nodev" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">NEW_OPT=nodev

if [ $(grep " \/tmp " /etc/fstab | grep -c "$NEW_OPT" ) -eq 0 ]; then
        MNT_OPTS=$(grep " \/tmp " /etc/fstab | awk '{print $4}')
        sed -i "s/\( \/tmp.*${MNT_OPTS}\)/\1,${NEW_OPT}/" /etc/fstab
        
        if [ $MNT_OPTS = "defaults" ]
        then
                sed -i "s/defaults,//" /etc/fstab
        fi
fi
</ns0:fix>
          <ns0:fix complexity="low" disruption="high" id="mount_option_tmp_nodev" reboot="false" strategy="enable" system="urn:redhat:anaconda:pre">
part /tmp -mountoptions="nodev"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_tmp_nodev:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="mount_option_tmp_noexec" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Add noexec Option to /tmp</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">noexec</html:code> mount option can be used to prevent binaries
from being executed out of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code>.

	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">noexec</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code>.
	
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MP-2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.4</ns0:reference>
          <ns0:rationale xml:lang="en-US">Allowing users to execute binaries from world-writable directories
such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code> should never be necessary in normal operation and
can expose the system to potential compromise.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="mount_option_tmp_noexec" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">NEW_OPT=noexec

if [ $(grep " \/tmp " /etc/fstab | grep -c "$NEW_OPT" ) -eq 0 ]; then
        MNT_OPTS=$(grep " \/tmp " /etc/fstab | awk '{print $4}')
        sed -i "s/\( \/tmp.*${MNT_OPTS}\)/\1,${NEW_OPT}/" /etc/fstab
        
        if [ $MNT_OPTS = "defaults" ]
        then
                sed -i "s/defaults,//" /etc/fstab
        fi
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_tmp_noexec:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="mount_option_tmp_nosuid" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Add nosuid Option to /tmp</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nosuid</html:code> mount option can be used to prevent
execution of setuid programs in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code>. The SUID and SGID permissions
should not be required in these world-writable directories.

	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nosuid</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code>.
	
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MP-2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.3</ns0:reference>
          <ns0:rationale xml:lang="en-US">The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from temporary storage partitions.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="mount_option_tmp_nosuid" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">NEW_OPT="nosuid"

if [ $(grep " \/tmp " /etc/fstab | grep -c "$NEW_OPT" ) -eq 0 ]; then
        MNT_OPTS=$(grep " \/tmp " /etc/fstab | awk '{print $4}')
        sed -i "s/\( \/tmp.*${MNT_OPTS}\)/\1,${NEW_OPT}/" /etc/fstab
        
        if [ $MNT_OPTS = "defaults" ]
        then
        	sed -i "s/defaults,//" /etc/fstab
        fi
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_tmp_nosuid:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="mount_option_dev_shm_nodev" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Add nodev Option to /dev/shm</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> mount option can be used to prevent creation
of device files in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/shm</html:code>.
Legitimate character and block devices should not exist
within temporary directories like <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/shm</html:code>. 

	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/shm</html:code>.
	
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MP-2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.14</ns0:reference>
          <ns0:rationale xml:lang="en-US">The only legitimate location for device files is the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev</html:code> directory
located on the root partition. The only exception to this is chroot jails.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_dev_shm_nodev:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="mount_option_dev_shm_noexec" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Add noexec Option to /dev/shm</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">noexec</html:code> mount option can be used to prevent binaries
from being executed out of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/shm</html:code>.
It can be dangerous to allow the execution of binaries
from world-writable temporary storage directories such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/shm</html:code>.

	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">noexec</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/shm</html:code>.
	
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MP-2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.16</ns0:reference>
          <ns0:rationale xml:lang="en-US">Allowing users to execute binaries from world-writable directories
such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/shm</html:code> can expose the system to potential compromise.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_dev_shm_noexec:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="mount_option_dev_shm_nosuid" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Add nosuid Option to /dev/shm</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nosuid</html:code> mount option can be used to prevent execution
of setuid programs in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/shm</html:code>.  The SUID and SGID permissions should not
be required in these world-writable directories.

	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nosuid</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/shm</html:code>.
	
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MP-2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.14</ns0:reference>
          <ns0:rationale xml:lang="en-US">The presence of SUID and SGID executables should be tightly controlled. Users
should not be able to execute SUID or SGID binaries from temporary storage partitions.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_dev_shm_nosuid:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="mount_option_var_tmp_bind" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Bind Mount /var/tmp To /tmp</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/tmp</html:code> directory is a world-writable directory.  
Bind-mount it to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code> in order to consolidate temporary storage into
one location protected by the same techniques as <html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code>.  To do so, edit
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> and add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/tmp     /var/tmp     none     rw,nodev,noexec,nosuid,bind     0 0</html:pre>
See the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mount(8)</html:code> man page for further explanation of bind mounting.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.6</ns0:reference>
          <ns0:rationale xml:lang="en-US">Having multiple locations for temporary storage is not required. Unless absolutely
necessary to meet requirements, the storage location <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/tmp</html:code> should be bind mounted to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code> and thus share the same protections.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="mount_option_var_tmp_bind" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"># Delete particular /etc/fstab's row if /var/tmp is already configured to
# represent a mount point (for some device or filesystem other than /tmp)
if grep -q -P '.*\/var\/tmp.*' /etc/fstab
then
  sed -i '/.*\/var\/tmp.*/d' /etc/fstab
fi

# Bind-mount /var/tmp to /tmp via /etc/fstab (preserving the /etc/fstab form)
printf "%-24s%-24s%-8s%-32s%-3s\n" "/tmp" "/var/tmp" "none" "rw,nodev,noexec,nosuid,bind" "0 0" &gt;&gt; /etc/fstab
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_var_tmp_bind:def:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="mounting">
        <ns0:title xml:lang="en-US">Restrict Dynamic Mounting and Unmounting of
Filesystems</ns0:title>
        <ns0:description xml:lang="en-US">Linux includes a number of facilities for the automated addition
and removal of filesystems on a running system.  These facilities may be
necessary in many environments, but this capability also carries some risk -- whether direct
risk from allowing users to introduce arbitrary filesystems,
or risk that software flaws in the automated mount facility itself could
allow an attacker to compromise the system.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
This command can be used to list the types of filesystems that are
available to the currently executing kernel:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ find /lib/modules/`uname -r`/kernel/fs -type f -name '*.ko'</html:pre>
If these filesystems are not required then they can be explicitly disabled
in a configuratio file in  <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>.
</ns0:description>
        <ns0:Rule id="kernel_module_usb-storage_disabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable Modprobe Loading of USB Storage Driver</ns0:title>
          <ns0:description xml:lang="en-US">
To prevent USB storage devices from being used, configure the kernel module loading system
to prevent automatic loading of the USB storage driver. 

To configure the system to prevent the <html:code xmlns:html="http://www.w3.org/1999/xhtml">usb-storage</html:code>
kernel module from being loaded, add the following line to a file in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>:
<html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">install usb-storage /bin/true</html:pre>
This will prevent the <html:code xmlns:html="http://www.w3.org/1999/xhtml">modprobe</html:code> program from loading the <html:code xmlns:html="http://www.w3.org/1999/xhtml">usb-storage</html:code>
module, but will not prevent an administrator (or another program) from using the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">insmod</html:code> program to load the module manually.</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(e)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-3</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">778</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1958</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000114-GPOS-00059</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000378-GPOS-0016</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">USB storage devices such as thumb drives can be used to introduce
malicious software.</ns0:rationale>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_usb-storage_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">if grep --silent "^install usb-storage" /etc/modprobe.d/usb-storage.conf ; then
        sed -i 's/^install usb-storage.*/install usb-storage /bin/true/g' /etc/modprobe.d/usb-storage.conf
else
        echo -e "\n# Disable per security requirements" &gt;&gt; /etc/modprobe.d/usb-storage.conf
        echo "install usb-storage /bin/true" &gt;&gt; /etc/modprobe.d/usb-storage.conf
fi
</ns0:fix>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_usb-storage_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure kernel module 'usb-storage' is disabled
  lineinfile:
    create=yes
    dest="/etc/modprobe.d/{{item}}.conf"
    regexp="{{item}}"
    line="install {{item}} /bin/true"
  with_items:
    - usb-storage
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-kernel_module_usb-storage_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-kernel_module_usb-storage_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="bootloader_nousb_argument" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Kernel Support for USB via Bootloader Configuration</ns0:title>
          <ns0:description xml:lang="en-US">
All USB support can be disabled by adding the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nousb</html:code>
argument to the kernel's boot loader configuration. To do so, 
append "nousb" to the kernel line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/default/grub</html:code> as shown:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">kernel /vmlinuz-<html:i>VERSION</html:i> ro vga=ext root=/dev/VolGroup00/LogVol00 rhgb quiet nousb</html:pre>
<html:i xmlns:html="http://www.w3.org/1999/xhtml"><html:b>WARNING:</html:b> Disabling all kernel support for USB will cause problems for
systems with USB-based keyboards, mice, or printers. This configuration is
infeasible for systems which require USB devices, which is common.</html:i></ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(e)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1250</ns0:reference>
          <ns0:rationale xml:lang="en-US">Disabling the USB subsystem within the Linux kernel at system boot will
protect against potentially malicious USB devices, although it is only practical
in specialized systems.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="bootloader_nousb_argument" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
# Correct the form of default kernel command line in /etc/default/grub
if ! grep -q ^GRUB_CMDLINE_LINUX=\".*nousb.*\" /etc/default/grub;
then
  # Edit configuration setting
  # Append 'nousb' argument to /etc/default/grub (if not present yet)
  sed -i "s/\(GRUB_CMDLINE_LINUX=\)\"\(.*\)\"/\1\"\2 nousb\"/" /etc/default/grub
  # Edit runtime setting
  # Correct the form of kernel command line for each installed kernel in the bootloader
  /sbin/grubby --update-kernel=ALL --args="nousb"
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-bootloader_nousb_argument:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="bios_disable_usb_boot" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Booting from USB Devices in Boot Firmware</ns0:title>
          <ns0:description xml:lang="en-US">Configure the system boot firmware (historically called BIOS on PC
systems) to disallow booting from USB drives. 
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(e)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1250</ns0:reference>
          <ns0:rationale xml:lang="en-US">Booting a system from a USB device would allow an attacker to
circumvent any security measures provided by the operating system. Attackers
could mount partitions and modify the configuration of the OS.</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="bios_assign_password" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Assign Password to Prevent Changes to Boot Firmware Configuration</ns0:title>
          <ns0:description xml:lang="en-US">Assign a password to the system boot firmware (historically called BIOS on PC 
systems) to require a password for any configuration changes.  
</ns0:description>
          <ns0:rationale xml:lang="en-US">Assigning a password to the system boot firmware prevents anyone
with physical access from configuring the system to boot
from local media and circumvent the operating system's access controls.
For systems in physically secure locations, such as
a data center or Sensitive Compartmented Information Facility (SCIF), this risk must be weighed
against the risk of administrative personnel being unable to conduct recovery operations in
a timely fashion.
</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="service_autofs_disabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the Automounter</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">autofs</html:code> daemon mounts and unmounts filesystems, such as user
home directories shared via NFS, on demand. In addition, autofs can be used to handle
removable media, and the default configuration provides the cdrom device as <html:code xmlns:html="http://www.w3.org/1999/xhtml">/misc/cd</html:code>.
However, this method of providing access to removable media is not common, so autofs
can almost always be disabled if NFS is not in use. Even if NFS is required, it may be
possible to configure filesystem mounts statically by editing <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code>
rather than relying on the automounter.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">autofs</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable autofs.service</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-19(e)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-3</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">778</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1958</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000114-GPOS-00059</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000378-GPOS-00163</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">Disabling the automounter permits the administrator to 
statically control filesystem mounting through <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code>. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Additionally, automatically mounting filesystems permits easy introduction of
unknown devices, thereby facilitating malicious activity.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_autofs_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable autofs
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_autofs_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service autofs
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - autofs

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_autofs_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_autofs_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="kernel_module_cramfs_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Mounting of cramfs</ns0:title>
          <ns0:description xml:lang="en-US">
To configure the system to prevent the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cramfs</html:code>
kernel module from being loaded, add the following line to a file in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>:
<html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">install cramfs /bin/true</html:pre>
This effectively prevents usage of this uncommon filesystem.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.18</ns0:reference>
          <ns0:rationale xml:lang="en-US">Linux kernel modules which implement filesystems that are not needed by the
local system should be disabled.</ns0:rationale>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_cramfs_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">echo "install cramfs /bin/true" &gt; /etc/modprobe.d/cramfs.conf
</ns0:fix>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_cramfs_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure kernel module 'cramfs' is disabled
  lineinfile:
    create=yes
    dest="/etc/modprobe.d/{{item}}.conf"
    regexp="{{item}}"
    line="install {{item}} /bin/true"
  with_items:
    - cramfs
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-kernel_module_cramfs_disabled:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="kernel_module_freevxfs_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Mounting of freevxfs</ns0:title>
          <ns0:description xml:lang="en-US">
To configure the system to prevent the <html:code xmlns:html="http://www.w3.org/1999/xhtml">freevxfs</html:code>
kernel module from being loaded, add the following line to a file in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>:
<html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">install freevxfs /bin/true</html:pre>
This effectively prevents usage of this uncommon filesystem.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.19</ns0:reference>
          <ns0:rationale xml:lang="en-US">Linux kernel modules which implement filesystems that are not needed by the
local system should be disabled.</ns0:rationale>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_freevxfs_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">echo "install freevxfs /bin/true" &gt; /etc/modprobe.d/freevxfs.conf
</ns0:fix>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_freevxfs_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure kernel module 'freevxfs' is disabled
  lineinfile:
    create=yes
    dest="/etc/modprobe.d/{{item}}.conf"
    regexp="{{item}}"
    line="install {{item}} /bin/true"
  with_items:
    - freevxfs
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-kernel_module_freevxfs_disabled:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="kernel_module_jffs2_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Mounting of jffs2</ns0:title>
          <ns0:description xml:lang="en-US">
To configure the system to prevent the <html:code xmlns:html="http://www.w3.org/1999/xhtml">jffs2</html:code>
kernel module from being loaded, add the following line to a file in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>:
<html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">install jffs2 /bin/true</html:pre>
This effectively prevents usage of this uncommon filesystem.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.20</ns0:reference>
          <ns0:rationale xml:lang="en-US">Linux kernel modules which implement filesystems that are not needed by the
local system should be disabled.</ns0:rationale>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_jffs2_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">echo "install jffs2 /bin/true" &gt; /etc/modprobe.d/jffs2.conf
</ns0:fix>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_jffs2_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure kernel module 'jffs2' is disabled
  lineinfile:
    create=yes
    dest="/etc/modprobe.d/{{item}}.conf"
    regexp="{{item}}"
    line="install {{item}} /bin/true"
  with_items:
    - jffs2
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-kernel_module_jffs2_disabled:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="kernel_module_hfs_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Mounting of hfs</ns0:title>
          <ns0:description xml:lang="en-US">
To configure the system to prevent the <html:code xmlns:html="http://www.w3.org/1999/xhtml">hfs</html:code>
kernel module from being loaded, add the following line to a file in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>:
<html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">install hfs /bin/true</html:pre>
This effectively prevents usage of this uncommon filesystem.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.21</ns0:reference>
          <ns0:rationale xml:lang="en-US">Linux kernel modules which implement filesystems that are not needed by the
local system should be disabled.</ns0:rationale>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_hfs_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">echo "install hfs /bin/true" &gt; /etc/modprobe.d/hfs.conf
</ns0:fix>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_hfs_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure kernel module 'hfs' is disabled
  lineinfile:
    create=yes
    dest="/etc/modprobe.d/{{item}}.conf"
    regexp="{{item}}"
    line="install {{item}} /bin/true"
  with_items:
    - hfs
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-kernel_module_hfs_disabled:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="kernel_module_hfsplus_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Mounting of hfsplus</ns0:title>
          <ns0:description xml:lang="en-US">
To configure the system to prevent the <html:code xmlns:html="http://www.w3.org/1999/xhtml">hfsplus</html:code>
kernel module from being loaded, add the following line to a file in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>:
<html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">install hfsplus /bin/true</html:pre>
This effectively prevents usage of this uncommon filesystem.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.22</ns0:reference>
          <ns0:rationale xml:lang="en-US">Linux kernel modules which implement filesystems that are not needed by the
local system should be disabled.</ns0:rationale>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_hfsplus_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">echo "install hfsplus /bin/true" &gt; /etc/modprobe.d/hfsplus.conf
</ns0:fix>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_hfsplus_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure kernel module 'hfsplus' is disabled
  lineinfile:
    create=yes
    dest="/etc/modprobe.d/{{item}}.conf"
    regexp="{{item}}"
    line="install {{item}} /bin/true"
  with_items:
    - hfsplus
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-kernel_module_hfsplus_disabled:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="kernel_module_squashfs_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Mounting of squashfs</ns0:title>
          <ns0:description xml:lang="en-US">
To configure the system to prevent the <html:code xmlns:html="http://www.w3.org/1999/xhtml">squashfs</html:code>
kernel module from being loaded, add the following line to a file in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>:
<html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">install squashfs /bin/true</html:pre>
This effectively prevents usage of this uncommon filesystem.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.23</ns0:reference>
          <ns0:rationale xml:lang="en-US">Linux kernel modules which implement filesystems that are not needed by the
local system should be disabled.</ns0:rationale>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_squashfs_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">echo "install squashfs /bin/true" &gt; /etc/modprobe.d/squashfs.conf
</ns0:fix>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_squashfs_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure kernel module 'squashfs' is disabled
  lineinfile:
    create=yes
    dest="/etc/modprobe.d/{{item}}.conf"
    regexp="{{item}}"
    line="install {{item}} /bin/true"
  with_items:
    - squashfs
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-kernel_module_squashfs_disabled:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="kernel_module_udf_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Mounting of udf</ns0:title>
          <ns0:description xml:lang="en-US">
To configure the system to prevent the <html:code xmlns:html="http://www.w3.org/1999/xhtml">udf</html:code>
kernel module from being loaded, add the following line to a file in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>:
<html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">install udf /bin/true</html:pre>
This effectively prevents usage of this uncommon filesystem.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.24</ns0:reference>
          <ns0:rationale xml:lang="en-US">Linux kernel modules which implement filesystems that are not needed by the
local system should be disabled.</ns0:rationale>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_udf_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">echo "install udf /bin/true" &gt; /etc/modprobe.d/udf.conf
</ns0:fix>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_udf_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure kernel module 'udf' is disabled
  lineinfile:
    create=yes
    dest="/etc/modprobe.d/{{item}}.conf"
    regexp="{{item}}"
    line="install {{item}} /bin/true"
  with_items:
    - udf
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-kernel_module_udf_disabled:def:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="files">
        <ns0:title xml:lang="en-US">Verify Permissions on Important Files and
Directories</ns0:title>
        <ns0:description xml:lang="en-US">Permissions for many files on a system must be set
restrictively to ensure sensitive information is properly protected.
This section discusses important
permission restrictions which can be verified
to ensure that no harmful discrepancies have
arisen.</ns0:description>
        <ns0:Group id="permissions_important_account_files">
          <ns0:title xml:lang="en-US">Verify Permissions on Files with Local Account Information and Credentials</ns0:title>
          <ns0:description xml:lang="en-US">The default restrictive permissions for files which act as
important security databases such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">passwd</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">shadow</html:code>,
<html:code xmlns:html="http://www.w3.org/1999/xhtml">group</html:code>, and <html:code xmlns:html="http://www.w3.org/1999/xhtml">gshadow</html:code> files must be maintained.  Many utilities
need read access to the <html:code xmlns:html="http://www.w3.org/1999/xhtml">passwd</html:code> file in order to function properly, but
read access to the <html:code xmlns:html="http://www.w3.org/1999/xhtml">shadow</html:code> file allows malicious attacks against system
passwords, and should never be enabled.</ns0:description>
          <ns0:Rule id="userowner_shadow_file" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify User Who Owns shadow File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/shadow</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root /etc/shadow </html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.7.c</ns0:reference>
            <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/shadow</html:code> file contains the list of local
system accounts and stores password hashes. Protection of this file is
critical for system security. Failure to give ownership of this file
to root provides the designated owner with access to sensitive information
which could weaken the system security posture.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="userowner_shadow_file" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">chown root /etc/shadow
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-userowner_shadow_file:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-userowner_shadow_file_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="groupowner_shadow_file" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify Group Who Owns shadow File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the group owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/shadow</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chgrp root /etc/shadow </html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.7.c</ns0:reference>
            <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/shadow</html:code> file stores password hashes. Protection of this file is
critical for system security.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="groupowner_shadow_file" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">chgrp root /etc/shadow
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-groupowner_shadow_file:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-groupowner_shadow_file_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_permissions_etc_shadow" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify Permissions on shadow File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the permissions of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/shadow</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 0000 /etc/shadow</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.7.c</ns0:reference>
            <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/shadow</html:code> file contains the list of local
system accounts and stores password hashes. Protection of this file is
critical for system security. Failure to give ownership of this file
to root provides the designated owner with access to sensitive information
which could weaken the system security posture.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_permissions_etc_shadow" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">chmod 0000 /etc/shadow
</ns0:fix>
            <ns0:fix complexity="low" disruption="low" id="file_permissions_etc_shadow" reboot="false" strategy="configure" system="urn:xccdf:fix:script:ansible">- name: Ensure permission 0000 on /etc/shadow
  file:
    path="{{item}}"
    mode=0000
  with_items:
    - /etc/shadow
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_etc_shadow:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_etc_shadow_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_owner_etc_group" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify User Who Owns group File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/group</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root /etc/group </html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.7.c</ns0:reference>
            <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/group</html:code> file contains information regarding groups that are configured
on the system. Protection of this file is important for system security.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_owner_etc_group" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">chown root /etc/group
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_owner_etc_group:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_owner_etc_group_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_groupowner_etc_group" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify Group Who Owns group File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the group owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/group</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chgrp root /etc/group </html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.7.c</ns0:reference>
            <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/group</html:code> file contains information regarding groups that are configured
on the system. Protection of this file is important for system security.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_groupowner_etc_group" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">chgrp root /etc/group
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_groupowner_etc_group:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_groupowner_etc_group_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_permissions_etc_group" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify Permissions on group File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the permissions of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/group</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 644 /etc/group</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.7.c</ns0:reference>
            <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/group</html:code> file contains information regarding groups that are configured
on the system. Protection of this file is important for system security.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_permissions_etc_group" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">chmod 644 /etc/group
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_etc_group:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_etc_group_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_owner_etc_gshadow" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify User Who Owns gshadow File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/gshadow</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root /etc/gshadow </html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/gshadow</html:code> file contains group password hashes. Protection of this file
is critical for system security.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_owner_etc_gshadow" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">chown root /etc/gshadow
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_owner_etc_gshadow:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_owner_etc_gshadow_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_groupowner_etc_gshadow" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify Group Who Owns gshadow File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the group owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/gshadow</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chgrp root /etc/gshadow </html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/gshadow</html:code> file contains group password hashes. Protection of this file
is critical for system security.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_groupowner_etc_gshadow" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">chgrp root /etc/gshadow
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_groupowner_etc_gshadow:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_groupowner_etc_gshadow_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_permissions_etc_gshadow" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify Permissions on gshadow File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the permissions of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/gshadow</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 0000 /etc/gshadow</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/gshadow</html:code> file contains group password hashes. Protection of this file
is critical for system security.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_permissions_etc_gshadow" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">chmod 0000 /etc/gshadow
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_etc_gshadow:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_etc_gshadow_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_owner_etc_passwd" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify User Who Owns passwd File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/passwd</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root /etc/passwd </html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.7.c</ns0:reference>
            <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/passwd</html:code> file contains information about the users that are configured on
the system. Protection of this file is critical for system security.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_owner_etc_passwd" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">chown root /etc/passwd
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_owner_etc_passwd:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_owner_etc_passwd_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_groupowner_etc_passwd" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify Group Who Owns passwd File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the group owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/passwd</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chgrp root /etc/passwd </html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.7.c</ns0:reference>
            <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/passwd</html:code> file contains information about the users that are configured on
the system. Protection of this file is critical for system security.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_groupowner_etc_passwd" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">chgrp root /etc/passwd
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_groupowner_etc_passwd:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_groupowner_etc_passwd_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_permissions_etc_passwd" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify Permissions on passwd File</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To properly set the permissions of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/passwd</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 0644 /etc/passwd</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.7.c</ns0:reference>
            <ns0:rationale xml:lang="en-US">If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/passwd</html:code> file is writable by a group-owner or the
world the risk of its compromise is increased. The file contains the list of
accounts on the system and associated information, and protection of this file
is critical for system security.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_permissions_etc_passwd" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">chmod 0644 /etc/passwd
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_etc_passwd:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_etc_passwd_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="permissions_within_important_dirs">
          <ns0:title xml:lang="en-US">Verify File Permissions Within Some Important Directories</ns0:title>
          <ns0:description xml:lang="en-US">Some directories contain files whose confidentiality or integrity
is notably important and may also be susceptible to misconfiguration over time, particularly if
unpackaged software is installed. As such,
an argument exists to verify that files' permissions within these directories remain
configured correctly and restrictively.   
</ns0:description>
          <ns0:Rule id="file_permissions_library_dirs" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify that Shared Library Files Have Restrictive Permissions</ns0:title>
            <ns0:description xml:lang="en-US">System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/lib
/lib64
/usr/lib
/usr/lib64
</html:pre>
Kernel modules, which can be added to the kernel during runtime, are
stored in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/lib/modules</html:code>. All files in these directories
should not be group-writable or world-writable. If any file in these
directories is found to be group-writable or world-writable, correct
its permission with the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod go-w <html:i>FILE</html:i></html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:rationale xml:lang="en-US">Files from shared library directories are loaded into the address
space of processes (including privileged ones) or of the kernel itself at
runtime. Restrictive permissions are necessary to protect the integrity of the system.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_permissions_library_dirs" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">DIRS="/lib /lib64 /usr/lib /usr/lib64"
for dirPath in $DIRS; do
	find "$dirPath" -perm /022 -type f -exec chmod go-w '{}' \;
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_library_dirs:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_library_dirs_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_ownership_library_dirs" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify that Shared Library Files Have Root Ownership</ns0:title>
            <ns0:description xml:lang="en-US">System-wide shared library files, which are linked to executables
during process load time or run time, are stored in the following directories
by default:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/lib
/lib64
/usr/lib
/usr/lib64
</html:pre>
Kernel modules, which can be added to the kernel during runtime, are also
stored in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/lib/modules</html:code>. All files in these directories should be
owned by the <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code> user. If the directory, or any file in these
directories, is found to be owned by a user other than root correct its
ownership with the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root <html:i>FILE</html:i></html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:rationale xml:lang="en-US">Files from shared library directories are loaded into the address
space of processes (including privileged ones) or of the kernel itself at
runtime. Proper ownership is necessary to protect the integrity of the system.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_ownership_library_dirs" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">for LIBDIR in /usr/lib /usr/lib64 /lib /lib64
do
  if [ -d $LIBDIR ]
  then
    find -L $LIBDIR \! -user root -exec chown root {} \; 
  fi
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_ownership_library_dirs:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_ownership_library_dirs_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_permissions_binary_dirs" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify that System Executables Have Restrictive Permissions</ns0:title>
            <ns0:description xml:lang="en-US">
System executables are stored in the following directories by default:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/bin
/sbin
/usr/bin
/usr/libexec
/usr/local/bin
/usr/local/sbin
/usr/sbin</html:pre>
All files in these directories should not be group-writable or world-writable.
If any file <html:i xmlns:html="http://www.w3.org/1999/xhtml">FILE</html:i> in these directories is found
to be group-writable or world-writable, correct its permission with the
following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod go-w <html:i>FILE</html:i></html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:rationale xml:lang="en-US">System binaries are executed by privileged users, as well as system services,
and restrictive permissions are necessary to ensure execution of these programs
cannot be co-opted.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_permissions_binary_dirs" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">DIRS="/bin /usr/bin /usr/local/bin /sbin /usr/sbin /usr/local/sbin /usr/libexec"
for dirPath in $DIRS; do
	find "$dirPath" -perm /022 -exec chmod go-w '{}' \;
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_binary_dirs:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_binary_dirs_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_ownership_binary_dirs" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify that System Executables Have Root Ownership</ns0:title>
            <ns0:description xml:lang="en-US">
System executables are stored in the following directories by default:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/bin
/sbin
/usr/bin
/usr/libexec
/usr/local/bin
/usr/local/sbin
/usr/sbin</html:pre>
All files in these directories should be owned by the <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code> user.
If any file <html:i xmlns:html="http://www.w3.org/1999/xhtml">FILE</html:i> in these directories is found
to be owned by a user other than root, correct its ownership with the
following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root <html:i>FILE</html:i></html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:rationale xml:lang="en-US">System binaries are executed by privileged users as well as system services,
and restrictive permissions are necessary to ensure that their
execution of these programs cannot be co-opted.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_ownership_binary_dirs" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">find /bin/ \
/usr/bin/ \
/usr/local/bin/ \
/sbin/ \
/usr/sbin/ \
/usr/local/sbin/ \
/usr/libexec \
\! -user root -execdir chown root {} \;
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_ownership_binary_dirs:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_ownership_binary_dirs_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Rule id="dir_perms_world_writable_sticky_bits" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Verify that All World-Writable Directories Have Sticky Bits Set</ns0:title>
          <ns0:description xml:lang="en-US">When the so-called 'sticky bit' is set on a directory,
only the owner of a given file may remove that file from the
directory. Without the sticky bit, any user with write access to a
directory may remove any file in the directory. Setting the sticky
bit prevents users from removing each other's files. In cases where
there is no reason for a directory to be world-writable, a better
solution is to remove that permission rather than to set the sticky
bit. However, if a directory is used by a particular application,
consult that application's documentation instead of blindly
changing modes.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To set the sticky bit on a world-writable directory <html:i xmlns:html="http://www.w3.org/1999/xhtml">DIR</html:i>, run the
following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod +t <html:i>DIR</html:i></html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.1.17</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Failing to set the sticky bit on public directories allows unauthorized users to delete files in the directory structure.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The only authorized public directories are those temporary directories supplied with the system, 
or those designed to be temporary file repositories.  The setting is normally reserved for directories 
used by the system, by users for temporary file storage (such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">/tmp</html:code>), and for directories 
requiring global read/write access.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dir_perms_world_writable_sticky_bits:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dir_perms_world_writable_sticky_bits_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="file_permissions_unauthorized_world_writable" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure No World-Writable Files Exist</ns0:title>
          <ns0:description xml:lang="en-US">It is generally a good idea to remove global (other) write
access to a file when it is discovered. However, check with
documentation for specific applications before making changes.
Also, monitor for recurring world-writable files, as these may be
symptoms of a misconfigured application or user
account.</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Data in world-writable files can be modified by any
user on the system. In almost all circumstances, files can be
configured using a combination of user and group permissions to
support whatever legitimate access is needed without the risk
caused by world-writable files.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_unauthorized_world_writable:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_unauthorized_world_writable_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="file_permissions_unauthorized_sgid" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure All SGID Executables Are Authorized</ns0:title>
          <ns0:description xml:lang="en-US">The SGID (set group id) bit should be set only on files that were
installed via authorized means. A straightforward means of identifying
unauthorized SGID files is determine if any were not installed as part of an
RPM package, which is cryptographically verified. Investigate the origin
of any unpackaged SGID files. 
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6(1)</ns0:reference>
          <ns0:rationale xml:lang="en-US">Executable files with the SGID permission run with the privileges of
the owner of the file. SGID files of uncertain provenance could allow for
unprivileged users to elevate privileges. The presence of these files should be
strictly controlled on the system.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_unauthorized_sgid:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_unauthorized_sgid_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="file_permissions_unauthorized_suid" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure All SUID Executables Are Authorized</ns0:title>
          <ns0:description xml:lang="en-US">The SUID (set user id) bit should be set only on files that were
installed via authorized means. A straightforward means of identifying
unauthorized SGID files is determine if any were not installed as part of an
RPM package, which is cryptographically verified. Investigate the origin
of any unpackaged SUID files. 
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6(1)</ns0:reference>
          <ns0:rationale xml:lang="en-US">Executable files with the SUID permission run with the privileges of
the owner of the file. SUID files of uncertain provenance could allow for
unprivileged users to elevate privileges. The presence of these files should be
strictly controlled on the system.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_unauthorized_suid:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_unauthorized_suid_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="no_files_unowned_by_user" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure All Files Are Owned by a User</ns0:title>
          <ns0:description xml:lang="en-US">If any files are not owned by a user, then the
cause of their lack of ownership should be investigated.
Following this, the files should be deleted or assigned to an
appropriate user.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3(4)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">002165</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Unowned files do not directly imply a security problem, but they are generally
a sign that something is amiss. They may
be caused by an intruder, by incorrect software installation or
draft software removal, or by failure to remove all files belonging
to a deleted account. The files should be repaired so they
will not cause problems when accounts are created in the future,
and the cause should be discovered and addressed.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-no_files_unowned_by_user:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-no_files_unowned_by_user_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="file_permissions_ungroupowned" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure All Files Are Owned by a Group</ns0:title>
          <ns0:description xml:lang="en-US">If any files are not owned by a group, then the
cause of their lack of group-ownership should be investigated.
Following this, the files should be deleted or assigned to an
appropriate group.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3(4)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-2</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">02165</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Unowned files do not directly imply a security problem, but they are generally
a sign that something is amiss. They may
be caused by an intruder, by incorrect software installation or
draft software removal, or by failure to remove all files belonging
to a deleted account. The files should be repaired so they
will not cause problems when accounts are created in the future,
and the cause should be discovered and addressed.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_ungroupowned:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_ungroupowned_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="dir_perms_world_writable_system_owned" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure All World-Writable Directories Are Owned by a System Account</ns0:title>
          <ns0:description xml:lang="en-US">All directories in local partitions which are
world-writable should be owned by root or another
system account.  If any world-writable directories are not
owned by a system account, this should be investigated.
Following this, the files should be deleted or assigned to an
appropriate group.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Allowing a user account to own a world-writable directory is
undesirable because it allows the owner of that directory to remove
or replace any files that may be placed in the directory by other
users.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dir_perms_world_writable_system_owned:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dir_perms_world_writable_system_owned_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="restrictions">
        <ns0:title xml:lang="en-US">Restrict Programs from Dangerous Execution Patterns</ns0:title>
        <ns0:description xml:lang="en-US">The recommendations in this section are designed to
ensure that the system's features to protect against potentially
dangerous program execution are activated.
These protections are applied at the system initialization or
kernel level, and defend against certain types of badly-configured
or compromised programs.</ns0:description>
        <ns0:Group id="daemon_umask">
          <ns0:title xml:lang="en-US">Daemon Umask</ns0:title>
          <ns0:description xml:lang="en-US">The umask is a per-process setting which limits
the default permissions for creation of new files and directories.
The system includes initialization scripts which set the default umask
for system daemons.
</ns0:description>
          <ns0:Value id="var_umask_for_daemons" operator="equals" type="string">
            <ns0:title xml:lang="en-US">daemon umask</ns0:title>
            <ns0:description xml:lang="en-US">Enter umask for daemons</ns0:description>
            <ns0:value>022</ns0:value>
            <ns0:value selector="022">022</ns0:value>
            <ns0:value selector="027">027</ns0:value>
          </ns0:Value>
          <ns0:Rule id="umask_for_daemons" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Set Daemon Umask</ns0:title>
            <ns0:description xml:lang="en-US">The file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/init.d/functions</html:code> includes initialization
parameters for most or all daemons started at boot time.  The default umask of
022 prevents creation of group- or world-writable files.  To set the default
umask for daemons, edit the following line, inserting 022 or 027 for
<html:i xmlns:html="http://www.w3.org/1999/xhtml">UMASK</html:i> appropriately:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">umask <html:i><ns0:sub idref="var_umask_for_daemons" /></html:i></html:pre>
Setting the umask to too restrictive a setting can cause serious errors at
runtime.  Many daemons on the system already individually restrict themselves to
a umask of 077 in their own init scripts.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">The umask influences the permissions assigned to files created by a
process at run time.  An unnecessarily permissive umask could result in files
being created with insecure permissions.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="umask_for_daemons" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_umask_for_daemons="<ns0:sub idref="var_umask_for_daemons" />"

grep -q ^umask /etc/init.d/functions &amp;&amp; \
  sed -i "s/umask.*/umask $var_umask_for_daemons/g" /etc/init.d/functions
if ! [ $? -eq 0 ]; then
    echo "umask $var_umask_for_daemons" &gt;&gt; /etc/init.d/functions
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_umask_for_daemons:var:1" value-id="var_umask_for_daemons" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-umask_for_daemons:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-umask_for_daemons_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="coredumps">
          <ns0:title xml:lang="en-US">Disable Core Dumps</ns0:title>
          <ns0:description xml:lang="en-US">A core dump file is the memory image of an executable
program when it was terminated by the operating system due to
errant behavior. In most cases, only software developers
legitimately need to access these files. The core dump files may
also contain sensitive information, or unnecessarily occupy large
amounts of disk space.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Once a hard limit is set in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/limits.conf</html:code>, a
user cannot increase that limit within his or her own session. If access
to core dumps is required, consider restricting them to only
certain users or groups. See the <html:code xmlns:html="http://www.w3.org/1999/xhtml">limits.conf</html:code> man page for more
information.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The core dumps of setuid programs are further protected. The
<html:code xmlns:html="http://www.w3.org/1999/xhtml">sysctl</html:code> variable <html:code xmlns:html="http://www.w3.org/1999/xhtml">fs.suid_dumpable</html:code> controls whether
the kernel allows core dumps from these programs at all. The default
value of 0 is recommended.</ns0:description>
          <ns0:Rule id="disable_users_coredumps" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable Core Dumps for All Users</ns0:title>
            <ns0:description xml:lang="en-US">To disable core dumps for all users, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/limits.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">*     hard   core    0</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.6.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">A core dump includes a memory image taken at the time the operating system
terminates an application. The memory image could contain sensitive data and is generally useful
only for developers trying to debug problems.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="disable_users_coredumps" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">echo "*     hard   core    0" &gt;&gt; /etc/security/limits.conf
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-disable_users_coredumps:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-disable_users_coredumps_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_fs_suid_dumpable" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable Core Dumps for SUID programs</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">fs.suid_dumpable</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w fs.suid_dumpable=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">fs.suid_dumpable = 0</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-11</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.6.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">The core dump of a setuid program is more likely to contain
sensitive data, as the program itself runs with greater privileges than the
user who initiated execution of the program.  Disabling the ability for any
setuid program to write a core file decreases the risk of unauthorized access
of such data.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_fs_suid_dumpable" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">#
# Set runtime for fs.suid_dumpable
#
/sbin/sysctl -q -n -w fs.suid_dumpable=0

#
# If fs.suid_dumpable present in /etc/sysctl.conf, change value to "0"
#	else, add "fs.suid_dumpable = 0" to /etc/sysctl.conf
#
if grep --silent ^fs.suid_dumpable /etc/sysctl.conf ; then
	sed -i 's/^fs.suid_dumpable.*/fs.suid_dumpable = 0/g' /etc/sysctl.conf
else
	echo -e "\n# Set fs.suid_dumpable to 0 per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "fs.suid_dumpable = 0" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_fs_suid_dumpable:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_fs_suid_dumpable_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="enable_execshield_settings">
          <ns0:title xml:lang="en-US">Enable ExecShield</ns0:title>
          <ns0:description xml:lang="en-US">ExecShield describes kernel features that provide
protection against exploitation of memory corruption errors such as buffer
overflows. These features include random placement of the stack and other
memory regions, prevention of execution in memory that should only hold data,
and special handling of text buffers. These protections are enabled by default
on 32-bit systems and controlled through <html:code xmlns:html="http://www.w3.org/1999/xhtml">sysctl</html:code> variables 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">kernel.exec-shield</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">kernel.randomize_va_space</html:code>. On the latest
64-bit systems, <html:code xmlns:html="http://www.w3.org/1999/xhtml">kernel.exec-shield</html:code> cannot be enabled or disabled with 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">sysctl</html:code>.
</ns0:description>
          <ns0:Rule id="sysctl_kernel_exec_shield" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Enable ExecShield</ns0:title>
            <ns0:description xml:lang="en-US">By default on Red Hat Enterprise Linux 7 64-bit systems, ExecShield
is enabled and can only be disabled if the hardware does not support ExecShield
or is disabled in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/default/grub</html:code>. For Red Hat Enterprise Linux 7 
32-bit systems, <html:code xmlns:html="http://www.w3.org/1999/xhtml">sysctl</html:code> can be used to enable ExecShield.</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-39</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2530</ns0:reference>
            <ns0:rationale xml:lang="en-US">ExecShield uses the segmentation feature on all x86 systems
to prevent execution in memory higher than a certain address. It
writes an address as a limit in the code segment descriptor, to
control where code can be executed, on a per-process basis. When
the kernel places a process's memory regions such as the stack and
heap higher than this address, the hardware prevents execution in that
address range. This is enabled by default on the latest Red Hat and Fedora 
systems if supported by the hardware.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="sysctl_kernel_exec_shield" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">if [ $(getconf LONG_BIT) = "32" ] ; then
  #
  # Set runtime for kernel.exec-shield
  #
  sysctl -q -n -w kernel.exec-shield=1

  #
  # If kernel.exec-shield present in /etc/sysctl.conf, change value to "1"
  #	else, add "kernel.exec-shield = 1" to /etc/sysctl.conf
  #
  if grep --silent ^kernel.exec-shield /etc/sysctl.conf ; then
	sed -i 's/^kernel.exec-shield.*/kernel.exec-shield = 1/g' /etc/sysctl.conf
  else
	echo -e "\n# Set kernel.exec-shield to 1 per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "kernel.exec-shield = 1" &gt;&gt; /etc/sysctl.d/sysctl.conf
  fi
fi

if [ $(getconf LONG_BIT) = "64" ] ; then
  if grep --silent noexec /boot/grub2/grub*.cfg ; then 
        sed -i "s/noexec.*//g" /etc/default/grub
        sed -i "s/noexec.*//g" /etc/grub.d/*
        GRUBCFG=`ls | grep '.cfg$'`
        grub2-mkconfig -o /boot/grub2/$GRUBCFG
  fi
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_kernel_exec_shield:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_kernel_exec_shield_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_kernel_randomize_va_space" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Enable Randomized Layout of Virtual Address Space</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">kernel.randomize_va_space</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w kernel.randomize_va_space=2</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">kernel.randomize_va_space = 2</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-30(2)</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.6.1</ns0:reference>
            <ns0:rationale xml:lang="en-US"> Address space layout randomization (ASLR) makes it more difficult
for an attacker to predict the location of attack code they have introduced
into a process's address space during an attempt at exploitation.  Additionally, ASLR 
makes it more difficult for an attacker to know the location of existing code
in order to re-purpose it using return oriented programming (ROP) techniques.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_kernel_randomize_va_space" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/sysctl.conf' '^kernel.randomize_va_space' '2' 'CCE-27127-0'
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_kernel_randomize_va_space:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_kernel_randomize_va_space_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="enable_nx">
          <ns0:title xml:lang="en-US">Enable Execute Disable (XD) or No Execute (NX) Support on
x86 Systems</ns0:title>
          <ns0:description xml:lang="en-US">Recent processors in the x86 family support the
ability to prevent code execution on a per memory page basis.
Generically and on AMD processors, this ability is called No
Execute (NX), while on Intel processors it is called Execute
Disable (XD). This ability can help prevent exploitation of buffer
overflow vulnerabilities and should be activated whenever possible.
Extra steps must be taken to ensure that this protection is
enabled, particularly on 32-bit x86 systems. Other processors, such
as Itanium and POWER, have included such support since inception
and the standard kernel for those platforms supports the
feature. This is enabled by default on the latest Red Hat and 
Fedora systems if supported by the hardware.</ns0:description>
          <ns0:Rule id="install_PAE_kernel_on_x86-32" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Install PAE Kernel on Supported 32-bit x86 Systems</ns0:title>
            <ns0:description xml:lang="en-US">Systems that are using the 64-bit x86 kernel package
do not need to install the kernel-PAE package because the 64-bit
x86 kernel already includes this support. However, if the system is
32-bit and also supports the PAE and NX features as
determined in the previous section, the kernel-PAE package should
be installed to enable XD or NX support:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install kernel-PAE</html:pre>
The installation process should also have configured the
bootloader to load the new kernel at boot. Verify this at reboot
and modify <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/default/grub</html:code> if necessary.</ns0:description>
            <ns0:warning category="hardware" xml:lang="en-US">The kernel-PAE package should not be
installed on older systems that do not support the XD or NX bit, as
this may prevent them from booting.</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
            <ns0:rationale xml:lang="en-US">On 32-bit systems that support the XD or NX bit, the vendor-supplied
PAE kernel is required to enable either Execute Disable (XD) or No Execute (NX) support.</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-install_PAE_kernel_on_x86-32:def:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="bios_enable_execution_restrictions" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Enable NX or XD Support in the BIOS</ns0:title>
            <ns0:description xml:lang="en-US">Reboot the system and enter the BIOS or Setup configuration menu.
Navigate the BIOS configuration menu and make sure that the option is enabled. The setting may be located
under a Security section. Look for Execute Disable (XD) on Intel-based systems and No Execute (NX)
on AMD-based systems.</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
            <ns0:rationale xml:lang="en-US">Computers with the ability to prevent this type of code execution frequently put an option in the BIOS that will
allow users to turn the feature on or off at will.</ns0:rationale>
            </ns0:Rule>
        </ns0:Group>
        <ns0:Rule id="sysctl_kernel_dmesg_restrict" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Restrict Access to Kernel Message Buffer</ns0:title>
          <ns0:description xml:lang="en-US">
            
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">kernel.dmesg_restrict</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w kernel.dmesg_restrict=1</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">kernel.dmesg_restrict = 1</html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-11</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1314</ns0:reference>
          <ns0:rationale xml:lang="en-US">Unprivileged access to the kernel syslog can expose sensitive kernel 
address information.</ns0:rationale>
          <ns0:fix complexity="low" disruption="medium" id="sysctl_kernel_dmesg_restrict" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">#
# Set runtime for kernel.dmesg_restrict
#
/sbin/sysctl -q -n -w kernel.dmesg_restrict=1

#
# If kernel.dmesg_restrict present in /etc/sysctl.conf, change value to "1"
#	else, add "kernel.dmesg_restrict = 1" to /etc/sysctl.conf
#
if grep --silent ^kernel.dmesg_restrict /etc/sysctl.conf ; then
	sed -i 's/^kernel.dmesg_restrict.*/kernel.dmesg_restrict = 1/g' /etc/sysctl.conf
else
	echo -e "\n# Set kernel.dmesg_restrict to 1 per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "kernel.dmesg_restrict = 1" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_kernel_dmesg_restrict:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_kernel_dmesg_restrict_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="selinux">
      <ns0:title xml:lang="en-US">SELinux</ns0:title>
      <ns0:description xml:lang="en-US">SELinux is a feature of the Linux kernel which can be
used to guard against misconfigured or compromised programs.
SELinux enforces the idea that programs should be limited in what
files they can access and what actions they can take.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The default SELinux policy, as configured on Red Hat Enterprise Linux 7, has been
sufficiently developed and debugged that it should be usable on
almost any Red Hat machine with minimal configuration and a small
amount of system administrator training. This policy prevents
system services - including most of the common network-visible
services such as mail servers, FTP servers, and DNS servers - from
accessing files which those services have no valid reason to
access. This action alone prevents a huge amount of possible damage
from network attacks against services, from trojaned software, and
so forth.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
This guide recommends that SELinux be enabled using the
default (targeted) policy on every Red Hat system, unless that
system has unusual requirements which make a stronger policy
appropriate.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For more information on SELinux, see <html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide</html:a></html:b>
</ns0:description>
      <ns0:Value id="var_selinux_state" operator="equals" type="string">
        <ns0:title xml:lang="en-US">SELinux state</ns0:title>
        <ns0:description xml:lang="en-US">enforcing - SELinux security policy is enforced.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />permissive - SELinux prints warnings instead of enforcing.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />disabled - SELinux is fully disabled.</ns0:description>
        <ns0:value>enforcing</ns0:value>
        <ns0:value selector="enforcing">enforcing</ns0:value>
        <ns0:value selector="permissive">permissive</ns0:value>
        <ns0:value selector="disabled">disabled</ns0:value>
      </ns0:Value>
      <ns0:Value id="var_selinux_policy_name" operator="equals" type="string">
        <ns0:title xml:lang="en-US">SELinux policy</ns0:title>
        <ns0:description xml:lang="en-US">Type of policy in use. Possible values are:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />targeted - Only targeted network daemons are protected.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />strict - Full SELinux protection.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />mls - Multiple levels of security</ns0:description>
        <ns0:value>targeted</ns0:value>
        <ns0:value selector="targeted">targeted</ns0:value>
        <ns0:value selector="mls">mls</ns0:value>
      </ns0:Value>
      <ns0:Rule id="enable_selinux_bootloader" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Ensure SELinux Not Disabled in /etc/default/grub</ns0:title>
        <ns0:description xml:lang="en-US">SELinux can be disabled at boot time by an argument in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/default/grub</html:code>.
Remove any instances of <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinux=0</html:code> from the kernel arguments in that
file to prevent SELinux from being disabled at boot.
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3(3)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3(4)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-6(a)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">22</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">32</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.4.1</ns0:reference>
        <ns0:rationale xml:lang="en-US">
Disabling a major host protection feature, such as SELinux, at boot time prevents
it from confining system services at boot time.  Further, it increases
the chances that it will remain off during system operation.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="enable_selinux_bootloader" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">sed -i --follow-symlinks "s/selinux=0//gI" /etc/default/grub /etc/grub2.cfg /etc/grub.d/*
sed -i --follow-symlinks "s/enforcing=0//gI" /etc/default/grub /etc/grub2.cfg /etc/grub.d/*
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-enable_selinux_bootloader:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-enable_selinux_bootloader_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="selinux_state" selected="false" severity="high">
        <ns0:title xml:lang="en-US">Ensure SELinux State is Enforcing</ns0:title>
        <ns0:description xml:lang="en-US">The SELinux state should be set to <html:code xmlns:html="http://www.w3.org/1999/xhtml"><ns0:sub idref="var_selinux_state" /></html:code> at
system boot time.  In the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/selinux/config</html:code>, add or correct the
following line to configure the system to boot into enforcing mode:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">SELINUX=<ns0:sub idref="var_selinux_state" /></html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3(3)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3(4)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-6(a)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2165</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2696</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.4.2</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000445-GPOS-00199</ns0:reference>
        <ns0:rationale xml:lang="en-US">
Setting the SELinux state to enforcing ensures SELinux is able to confine
potentially compromised processes to the security policy, which is designed to
prevent them from causing damage to the system or further elevating their
privileges.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="selinux_state" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_selinux_state="<ns0:sub idref="var_selinux_state" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/sysconfig/selinux' '^SELINUX=' $var_selinux_state 'CCE-27334-2' '%s=%s'
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-export export-name="oval:ssg-var_selinux_state:var:1" value-id="var_selinux_state" />
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-selinux_state:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-selinux_state_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="selinux_policytype" selected="false" severity="high">
        <ns0:title xml:lang="en-US">Configure SELinux Policy</ns0:title>
        <ns0:description xml:lang="en-US">The SELinux <html:code xmlns:html="http://www.w3.org/1999/xhtml">targeted</html:code> policy is appropriate for
general-purpose desktops and servers, as well as systems in many other roles.
To configure the system to use this policy, add or correct the following line
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/selinux/config</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">SELINUXTYPE=<ns0:sub idref="var_selinux_policy_name" /></html:pre>
Other policies, such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">mls</html:code>, provide additional security labeling
and greater confinement but are not compatible with many general-purpose
use cases.
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3(3)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3(4)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-6(a)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2696</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.4.3</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000445-GPOS-00199</ns0:reference>
        <ns0:rationale xml:lang="en-US">
Setting the SELinux policy to <html:code xmlns:html="http://www.w3.org/1999/xhtml">targeted</html:code> or a more specialized policy
ensures the system will confine processes that are likely to be
targeted for exploitation, such as network or system services.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Note: During the development or debugging of SELinux modules, it is common to
temporarily place non-production systems in <html:code xmlns:html="http://www.w3.org/1999/xhtml">permissive</html:code> mode. In such
temporary cases, SELinux policies should be developed, and once work
is completed, the system should be reconfigured to
<html:code xmlns:html="http://www.w3.org/1999/xhtml"><ns0:sub idref="var_selinux_policy_name" /></html:code>.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="selinux_policytype" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_selinux_policy_name="<ns0:sub idref="var_selinux_policy_name" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/sysconfig/selinux' '^SELINUXTYPE=' $var_selinux_policy_name 'CCE-27279-9' '%s=%s'
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-export export-name="oval:ssg-var_selinux_policy_name:var:1" value-id="var_selinux_policy_name" />
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-selinux_policytype:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-selinux_policytype_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="package_setroubleshoot_removed" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Uninstall setroubleshoot Package</ns0:title>
        <ns0:description xml:lang="en-US">The SETroubleshoot service notifies desktop users of SELinux
denials. The service provides information around configuration errors,
unauthorized intrusions, and other potential errors.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">setroubleshoot</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase setroubleshoot</html:pre>
</ns0:description>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.4.4</ns0:reference>
        <ns0:rationale xml:lang="en-US">The SETroubleshoot service is an unnecessary daemon to
have running on a server</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_setroubleshoot_removed:def:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="package_mcstrans_removed" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Uninstall mcstrans Package</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">mcstransd</html:code> daemon provides category label information
to client processes requesting information. The label translations are defined
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/selinux/targeted/setrans.conf</html:code>.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">mcstrans</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase mcstrans</html:pre>
</ns0:description>
        <ns0:rationale xml:lang="en-US">Since this service is not used very often, disable it to reduce the
amount of potentially vulnerable code running on the system.

NOTE: This rule was added in support of the CIS RHEL6 v1.2.0 benchmark. Please
note that Red Hat does not feel this rule is security relevant.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_mcstrans_removed:def:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="selinux_confinement_of_daemons" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Ensure No Daemons are Unconfined by SELinux</ns0:title>
        <ns0:description xml:lang="en-US">
Daemons for which the SELinux policy does not contain rules will inherit the
context of the parent process. Because daemons are launched during
startup and descend from the <html:code xmlns:html="http://www.w3.org/1999/xhtml">init</html:code> process, they inherit the <html:code xmlns:html="http://www.w3.org/1999/xhtml">initrc_t</html:code> context.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To check for unconfined daemons, run the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo ps -eZ | egrep "initrc" | egrep -vw "tr|ps|egrep|bash|awk" | tr ':' ' ' | awk '{ print $NF }'</html:pre>
It should produce no output in a well-configured system.
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.4.6</ns0:reference>
        <ns0:rationale xml:lang="en-US">
Daemons which run with the <html:code xmlns:html="http://www.w3.org/1999/xhtml">initrc_t</html:code> context may cause AVC denials,
or allow privileges that the daemon does not require.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-selinux_confinement_of_daemons:def:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="selinux_all_devicefiles_labeled" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Ensure No Device Files are Unlabeled by SELinux</ns0:title>
        <ns0:description xml:lang="en-US">Device files, which are used for communication with important
system resources, should be labeled with proper SELinux types. If any device
files do not carry the SELinux type <html:code xmlns:html="http://www.w3.org/1999/xhtml">device_t</html:code>, report the bug so 
that policy can be corrected. Supply information about what the device is
and what programs use it.
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-3(f)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">22</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">32</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">368</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">318</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1812</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1813</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1814</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
        <ns0:rationale xml:lang="en-US">
If a device file carries the SELinux type <html:code xmlns:html="http://www.w3.org/1999/xhtml">device_t</html:code>, then SELinux
cannot properly restrict access to the device file.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-selinux_all_devicefiles_labeled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-selinux_all_devicefiles_labeled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="docker_selinux_enabled" selected="false" severity="high">
        <ns0:title xml:lang="en-US">Ensure SELinux support is enabled in Docker</ns0:title>
        <ns0:description xml:lang="en-US">
To enable the SELinux for the Docker service, the Docker service must be
configured to run the Docker daemon with <html:code xmlns:html="http://www.w3.org/1999/xhtml">--selinux-enabled</html:code> option.
In <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/docker</html:code> configuration file, add or correct
the following line to enable SELinux support in the Docker daemon:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">OPTIONS='--selinux-enabled'</html:pre>
</ns0:description>
        <ns0:rationale xml:lang="en-US">
If SELinux is not explicitely enabled in the Docker daemon configuration,
Docker does not use SELinux which means Docker runs unconfined,
and SELinux will not provide security separation for Docker container
processes. However enabling SELinux for the Docker service prevents
an attacker or rogue container from attacking other container processes
and content as well as prevents taking over the host operating system.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-docker_selinux_enabled:def:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Group id="selinux-booleans">
        <ns0:title xml:lang="en-US">SELinux - Booleans</ns0:title>
        <ns0:description xml:lang="en-US">
Enable or Disable runtime customization of SELinux system policies
without having to reload or recompile the SELinux policy.
</ns0:description>
        <ns0:Rule id="sebool_abrt_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the abrt_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">abrt_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">abrt_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P abrt_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_abrt_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_abrt_handle_event" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the abrt_handle_event SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">abrt_handle_event</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">abrt_handle_event</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P abrt_handle_event off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_abrt_handle_event_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_abrt_upload_watch_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the abrt_upload_watch_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">abrt_upload_watch_anon_write</html:code> is enabled.
This setting should be disabled as it allows the Automatic Bug Report Tool (ABRT)
to modify public files used for public file transfer services.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">abrt_upload_watch_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P abrt_upload_watch_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_abrt_upload_watch_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_antivirus_can_scan_system" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the antivirus_can_scan_system SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">antivirus_can_scan_system</html:code> is disabled.
This setting should be enabled as it allows antivirus programs to read non-security
files on a system.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">antivirus_can_scan_system</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P antivirus_can_scan_system on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_antivirus_can_scan_system_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_antivirus_use_jit" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the antivirus_use_jit SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">antivirus_use_jit</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">antivirus_use_jit</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P antivirus_use_jit off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_antivirus_use_jit_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_auditadm_exec_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the auditadm_exec_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditadm_exec_content</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditadm_exec_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P auditadm_exec_content on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_auditadm_exec_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_authlogin_nsswitch_use_ldap" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the authlogin_nsswitch_use_ldap SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">authlogin_nsswitch_use_ldap</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">authlogin_nsswitch_use_ldap</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P authlogin_nsswitch_use_ldap off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_authlogin_nsswitch_use_ldap_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_authlogin_radius" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the authlogin_radius SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">authlogin_radius</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">authlogin_radius</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P authlogin_radius off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_authlogin_radius_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_authlogin_yubikey" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the authlogin_yubikey SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">authlogin_yubikey</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">authlogin_yubikey</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P authlogin_yubikey off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_authlogin_yubikey_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_awstats_purge_apache_log_files" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the awstats_purge_apache_log_files SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">awstats_purge_apache_log_files</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">awstats_purge_apache_log_files</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P awstats_purge_apache_log_files off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_awstats_purge_apache_log_files_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_boinc_execmem" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the boinc_execmem SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">boinc_execmem</html:code> is enabled.
This setting should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">boinc_execmem</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P boinc_execmem off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_boinc_execmem_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cdrecord_read_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cdrecord_read_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cdrecord_read_content</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cdrecord_read_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cdrecord_read_content off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cdrecord_read_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cluster_can_network_connect" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cluster_can_network_connect SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cluster_can_network_connect</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cluster_can_network_connect</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cluster_can_network_connect off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cluster_can_network_connect_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cluster_manage_all_files" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cluster_manage_all_files SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cluster_manage_all_files</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cluster_manage_all_files</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cluster_manage_all_files off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cluster_manage_all_files_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cluster_use_execmem" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cluster_use_execmem SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cluster_use_execmem</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cluster_use_execmem</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cluster_use_execmem off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cluster_use_execmem_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cobbler_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cobbler_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cobbler_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cobbler_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cobbler_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cobbler_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cobbler_can_network_connect" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cobbler_can_network_connect SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cobbler_can_network_connect</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cobbler_can_network_connect</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cobbler_can_network_connect off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cobbler_can_network_connect_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cobbler_use_cifs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cobbler_use_cifs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cobbler_use_cifs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cobbler_use_cifs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cobbler_use_cifs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cobbler_use_cifs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cobbler_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cobbler_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cobbler_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cobbler_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cobbler_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cobbler_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_collectd_tcp_network_connect" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the collectd_tcp_network_connect SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">collectd_tcp_network_connect</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">collectd_tcp_network_connect</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P collectd_tcp_network_connect off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_collectd_tcp_network_connect_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_condor_tcp_network_connect" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the condor_tcp_network_connect SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">condor_tcp_network_connect</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">condor_tcp_network_connect</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P condor_tcp_network_connect off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_condor_tcp_network_connect_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_conman_can_network" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the conman_can_network SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">conman_can_network</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">conman_can_network</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P conman_can_network off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_conman_can_network_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cron_can_relabel" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cron_can_relabel SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron_can_relabel</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron_can_relabel</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cron_can_relabel off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cron_can_relabel_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cron_system_cronjob_use_shares" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cron_system_cronjob_use_shares SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron_system_cronjob_use_shares</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron_system_cronjob_use_shares</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cron_system_cronjob_use_shares off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cron_system_cronjob_use_shares_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cron_userdomain_transition" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the cron_userdomain_transition SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron_userdomain_transition</html:code> is enabled.
This setting should be enabled as end user cron jobs run in their default
associated user domain(s) instead of the general cronjob domain.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron_userdomain_transition</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cron_userdomain_transition on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cron_userdomain_transition_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cups_execmem" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cups_execmem SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cups_execmem</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cups_execmem</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cups_execmem off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cups_execmem_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_cvs_read_shadow" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the cvs_read_shadow SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">cvs_read_shadow</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">cvs_read_shadow</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P cvs_read_shadow off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_cvs_read_shadow_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_daemons_dump_core" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the daemons_dump_core SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">daemons_dump_core</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">daemons_dump_core</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P daemons_dump_core off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_daemons_dump_core_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_daemons_enable_cluster_mode" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the daemons_enable_cluster_mode SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">daemons_enable_cluster_mode</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">daemons_enable_cluster_mode</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P daemons_enable_cluster_mode off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_daemons_enable_cluster_mode_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_daemons_use_tcp_wrapper" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the daemons_use_tcp_wrapper SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">daemons_use_tcp_wrapper</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">daemons_use_tcp_wrapper</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P daemons_use_tcp_wrapper off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_daemons_use_tcp_wrapper_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_daemons_use_tty" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the daemons_use_tty SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">daemons_use_tty</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">daemons_use_tty</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P daemons_use_tty off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_daemons_use_tty_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_dbadm_exec_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the dbadm_exec_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">dbadm_exec_content</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">dbadm_exec_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P dbadm_exec_content on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_dbadm_exec_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_dbadm_manage_user_files" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the dbadm_manage_user_files SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">dbadm_manage_user_files</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">dbadm_manage_user_files</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P dbadm_manage_user_files off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_dbadm_manage_user_files_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_dbadm_read_user_files" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the dbadm_read_user_files SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">dbadm_read_user_files</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">dbadm_read_user_files</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P dbadm_read_user_files off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_dbadm_read_user_files_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_deny_execmem" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the deny_execmem SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">deny_execmem</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">deny_execmem</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P deny_execmem off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_deny_execmem_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_deny_ptrace" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the deny_ptrace SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">deny_ptrace</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">deny_ptrace</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P deny_ptrace off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_deny_ptrace_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_dhcpc_exec_iptables" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the dhcpc_exec_iptables SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">dhcpc_exec_iptables</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">dhcpc_exec_iptables</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P dhcpc_exec_iptables off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_dhcpc_exec_iptables_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_dhcpd_use_ldap" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the dhcpd_use_ldap SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">dhcpd_use_ldap</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">dhcpd_use_ldap</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P dhcpd_use_ldap off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_dhcpd_use_ldap_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_docker_connect_any" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the docker_connect_any SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">docker_connect_any</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">docker_connect_any</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P docker_connect_any off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_docker_connect_any_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_docker_transition_unconfined" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the docker_transition_unconfined SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">docker_transition_unconfined</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">docker_transition_unconfined</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P docker_transition_unconfined on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_docker_transition_unconfined_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_domain_fd_use" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the domain_fd_use SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">domain_fd_use</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">domain_fd_use</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P domain_fd_use on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_domain_fd_use_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_domain_kernel_load_modules" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the domain_kernel_load_modules SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">domain_kernel_load_modules</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">domain_kernel_load_modules</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P domain_kernel_load_modules off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_domain_kernel_load_modules_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_entropyd_use_audio" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the entropyd_use_audio SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">entropyd_use_audio</html:code> is enabled.
This setting should be disabled as it uses audit input to generate entropy.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">entropyd_use_audio</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P entropyd_use_audio off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_entropyd_use_audio_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_exim_can_connect_db" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the exim_can_connect_db SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">exim_can_connect_db</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">exim_can_connect_db</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P exim_can_connect_db off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_exim_can_connect_db_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_exim_manage_user_files" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the exim_manage_user_files SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">exim_manage_user_files</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">exim_manage_user_files</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P exim_manage_user_files off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_exim_manage_user_files_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_exim_read_user_files" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the exim_read_user_files SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">exim_read_user_files</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">exim_read_user_files</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P exim_read_user_files off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_exim_read_user_files_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_fcron_crond" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the fcron_crond SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">fcron_crond</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">fcron_crond</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P fcron_crond off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_fcron_crond_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_fenced_can_network_connect" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the fenced_can_network_connect SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">fenced_can_network_connect</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">fenced_can_network_connect</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P fenced_can_network_connect off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_fenced_can_network_connect_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_fenced_can_ssh" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the fenced_can_ssh SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">fenced_can_ssh</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">fenced_can_ssh</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P fenced_can_ssh off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_fenced_can_ssh_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_fips_mode" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the fips_mode SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">fips_mode</html:code> is enabled.
This allows all SELinux domains to execute in <html:code xmlns:html="http://www.w3.org/1999/xhtml">fips_mode</html:code>.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">fips_mode</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P fips_mode on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_fips_mode_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ftpd_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ftpd_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ftpd_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ftpd_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ftpd_connect_all_unreserved" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ftpd_connect_all_unreserved SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_connect_all_unreserved</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_connect_all_unreserved</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ftpd_connect_all_unreserved off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ftpd_connect_all_unreserved_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ftpd_connect_db" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ftpd_connect_db SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_connect_db</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_connect_db</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ftpd_connect_db off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ftpd_connect_db_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ftpd_full_access" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ftpd_full_access SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_full_access</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_full_access</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ftpd_full_access off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ftpd_full_access_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ftpd_use_cifs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ftpd_use_cifs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_use_cifs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_use_cifs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ftpd_use_cifs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ftpd_use_cifs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ftpd_use_fusefs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ftpd_use_fusefs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_use_fusefs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_use_fusefs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ftpd_use_fusefs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ftpd_use_fusefs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ftpd_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ftpd_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ftpd_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ftpd_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ftpd_use_passive_mode" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ftpd_use_passive_mode SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_use_passive_mode</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftpd_use_passive_mode</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ftpd_use_passive_mode off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ftpd_use_passive_mode_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ftp_home_dir" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ftp_home_dir SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftp_home_dir</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ftp_home_dir</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ftp_home_dir off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ftp_home_dir_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_git_cgi_enable_homedirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the git_cgi_enable_homedirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_cgi_enable_homedirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_cgi_enable_homedirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P git_cgi_enable_homedirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_git_cgi_enable_homedirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_git_cgi_use_cifs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the git_cgi_use_cifs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_cgi_use_cifs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_cgi_use_cifs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P git_cgi_use_cifs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_git_cgi_use_cifs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_git_cgi_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the git_cgi_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_cgi_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_cgi_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P git_cgi_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_git_cgi_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_gitosis_can_sendmail" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the gitosis_can_sendmail SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">gitosis_can_sendmail</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">gitosis_can_sendmail</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P gitosis_can_sendmail off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_gitosis_can_sendmail_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_git_session_bind_all_unreserved_ports" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the git_session_bind_all_unreserved_ports SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_session_bind_all_unreserved_ports</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_session_bind_all_unreserved_ports</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P git_session_bind_all_unreserved_ports off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_git_session_bind_all_unreserved_ports_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_git_session_users" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the git_session_users SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_session_users</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_session_users</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P git_session_users off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_git_session_users_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_git_system_enable_homedirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the git_system_enable_homedirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_system_enable_homedirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_system_enable_homedirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P git_system_enable_homedirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_git_system_enable_homedirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_git_system_use_cifs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the git_system_use_cifs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_system_use_cifs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_system_use_cifs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P git_system_use_cifs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_git_system_use_cifs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_git_system_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the git_system_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_system_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">git_system_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P git_system_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_git_system_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_glance_api_can_network" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the glance_api_can_network SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">glance_api_can_network</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">glance_api_can_network</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P glance_api_can_network off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_glance_api_can_network_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_glance_use_execmem" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the glance_use_execmem SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">glance_use_execmem</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">glance_use_execmem</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P glance_use_execmem off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_glance_use_execmem_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_glance_use_fusefs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the glance_use_fusefs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">glance_use_fusefs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">glance_use_fusefs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P glance_use_fusefs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_glance_use_fusefs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_global_ssp" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the global_ssp SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">global_ssp</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">global_ssp</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P global_ssp off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_global_ssp_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_gluster_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the gluster_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">gluster_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">gluster_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P gluster_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_gluster_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_gluster_export_all_ro" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the gluster_export_all_ro SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">gluster_export_all_ro</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">gluster_export_all_ro</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P gluster_export_all_ro off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_gluster_export_all_ro_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_gluster_export_all_rw" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure the gluster_export_all_rw SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">gluster_export_all_rw</html:code> is enabled.
If <html:code xmlns:html="http://www.w3.org/1999/xhtml">GlusterFS</html:code> is in use, this setting should be enabled. Otherwise,
disable it.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">gluster_export_all_rw</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P gluster_export_all_rw off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_gluster_export_all_rw_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_gpg_web_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the gpg_web_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">gpg_web_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">gpg_web_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P gpg_web_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_gpg_web_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_gssd_read_tmp" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the gssd_read_tmp SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">gssd_read_tmp</html:code> is enabled.
This setting allows <html:code xmlns:html="http://www.w3.org/1999/xhtml">gssd</html:code> processes to access Kerberos to read
TGTs in the temp directory. If this setting is disabled, it should
be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">gssd_read_tmp</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P gssd_read_tmp on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_gssd_read_tmp_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_guest_exec_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the guest_exec_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">guest_exec_content</html:code> is enabled.
This setting should be disabled as no guest accounts should be used.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">guest_exec_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P guest_exec_content on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_guest_exec_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_haproxy_connect_any" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the haproxy_connect_any SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">haproxy_connect_any</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">haproxy_connect_any</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P haproxy_connect_any off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_haproxy_connect_any_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_builtin_scripting" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure the httpd_builtin_scripting SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_builtin_scripting</html:code> is enabled.
This setting should be disabled if <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> is not running <html:code xmlns:html="http://www.w3.org/1999/xhtml">php</html:code>
or some similary scripting language.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_builtin_scripting</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_builtin_scripting off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_builtin_scripting_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_can_check_spam" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_can_check_spam SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_check_spam</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_check_spam</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_can_check_spam off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_can_check_spam_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_can_connect_ftp" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_can_connect_ftp SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_connect_ftp</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_connect_ftp</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_can_connect_ftp off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_can_connect_ftp_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_can_connect_ldap" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_can_connect_ldap SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_connect_ldap</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_connect_ldap</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_can_connect_ldap off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_can_connect_ldap_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_can_connect_mythtv" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_can_connect_mythtv SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_connect_mythtv</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_connect_mythtv</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_can_connect_mythtv off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_can_connect_mythtv_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_can_connect_zabbix" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_can_connect_zabbix SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_connect_zabbix</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_connect_zabbix</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_can_connect_zabbix off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_can_connect_zabbix_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_can_network_connect_cobbler" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_can_network_connect_cobbler SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_network_connect_cobbler</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_network_connect_cobbler</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_can_network_connect_cobbler off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_can_network_connect_cobbler_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_can_network_connect_db" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_can_network_connect_db SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_network_connect_db</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_network_connect_db</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_can_network_connect_db off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_can_network_connect_db_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_can_network_connect" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_can_network_connect SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_network_connect</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_network_connect</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_can_network_connect off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_can_network_connect_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_can_network_memcache" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_can_network_memcache SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_network_memcache</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_network_memcache</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_can_network_memcache off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_can_network_memcache_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_can_network_relay" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_can_network_relay SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_network_relay</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_network_relay</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_can_network_relay off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_can_network_relay_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_can_sendmail" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_can_sendmail SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_sendmail</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_can_sendmail</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_can_sendmail off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_can_sendmail_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_dbus_avahi" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_dbus_avahi SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_dbus_avahi</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_dbus_avahi</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_dbus_avahi off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_dbus_avahi_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_dbus_sssd" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_dbus_sssd SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_dbus_sssd</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_dbus_sssd</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_dbus_sssd off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_dbus_sssd_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_dontaudit_search_dirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_dontaudit_search_dirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_dontaudit_search_dirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_dontaudit_search_dirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_dontaudit_search_dirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_dontaudit_search_dirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_enable_cgi" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure the httpd_enable_cgi SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_enable_cgi</html:code> is enabled.
This setting should be disabled unless <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> is used with <html:code xmlns:html="http://www.w3.org/1999/xhtml">CGI</html:code>
scripting.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_enable_cgi</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_enable_cgi off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_enable_cgi_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_enable_ftp_server" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_enable_ftp_server SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_enable_ftp_server</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_enable_ftp_server</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_enable_ftp_server off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_enable_ftp_server_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_enable_homedirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_enable_homedirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_enable_homedirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_enable_homedirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_enable_homedirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_enable_homedirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_execmem" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_execmem SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_execmem</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_execmem</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_execmem off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_execmem_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_graceful_shutdown" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the httpd_graceful_shutdown SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_graceful_shutdown</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_graceful_shutdown</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_graceful_shutdown on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_graceful_shutdown_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_manage_ipa" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_manage_ipa SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_manage_ipa</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_manage_ipa</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_manage_ipa off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_manage_ipa_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_mod_auth_ntlm_winbind" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_mod_auth_ntlm_winbind SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_mod_auth_ntlm_winbind</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_mod_auth_ntlm_winbind</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_mod_auth_ntlm_winbind off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_mod_auth_ntlm_winbind_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_mod_auth_pam" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_mod_auth_pam SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_mod_auth_pam</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_mod_auth_pam</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_mod_auth_pam off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_mod_auth_pam_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_read_user_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_read_user_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_read_user_content</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_read_user_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_read_user_content off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_read_user_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_run_ipa" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_run_ipa SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_run_ipa</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_run_ipa</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_run_ipa off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_run_ipa_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_run_preupgrade" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_run_preupgrade SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_run_preupgrade</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_run_preupgrade</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_run_preupgrade off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_run_preupgrade_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_run_stickshift" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_run_stickshift SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_run_stickshift</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_run_stickshift</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_run_stickshift off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_run_stickshift_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_serve_cobbler_files" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_serve_cobbler_files SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_serve_cobbler_files</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_serve_cobbler_files</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_serve_cobbler_files off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_serve_cobbler_files_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_setrlimit" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_setrlimit SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_setrlimit</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_setrlimit</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_setrlimit off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_setrlimit_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_ssi_exec" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_ssi_exec SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_ssi_exec</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_ssi_exec</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_ssi_exec off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_ssi_exec_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_sys_script_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_sys_script_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_sys_script_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_sys_script_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_sys_script_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_sys_script_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_tmp_exec" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_tmp_exec SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_tmp_exec</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_tmp_exec</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_tmp_exec off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_tmp_exec_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_tty_comm" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_tty_comm SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_tty_comm</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_tty_comm</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_tty_comm off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_tty_comm_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_unified" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_unified SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_unified</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_unified</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_unified off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_unified_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_use_cifs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_use_cifs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_cifs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_cifs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_use_cifs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_use_cifs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_use_fusefs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_use_fusefs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_fusefs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_fusefs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_use_fusefs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_use_fusefs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_use_gpg" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_use_gpg SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_gpg</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_gpg</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_use_gpg off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_use_gpg_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_use_openstack" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_use_openstack SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_openstack</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_openstack</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_use_openstack off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_use_openstack_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_use_sasl" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_use_sasl SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_sasl</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_use_sasl</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_use_sasl off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_use_sasl_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_httpd_verify_dns" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the httpd_verify_dns SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_verify_dns</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd_verify_dns</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P httpd_verify_dns off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_httpd_verify_dns_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_icecast_use_any_tcp_ports" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the icecast_use_any_tcp_ports SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">icecast_use_any_tcp_ports</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">icecast_use_any_tcp_ports</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P icecast_use_any_tcp_ports off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_icecast_use_any_tcp_ports_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_irc_use_any_tcp_ports" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the irc_use_any_tcp_ports SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">irc_use_any_tcp_ports</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">irc_use_any_tcp_ports</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P irc_use_any_tcp_ports off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_irc_use_any_tcp_ports_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_irssi_use_full_network" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the irssi_use_full_network SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">irssi_use_full_network</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">irssi_use_full_network</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P irssi_use_full_network off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_irssi_use_full_network_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_kdumpgui_run_bootloader" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the kdumpgui_run_bootloader SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">kdumpgui_run_bootloader</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">kdumpgui_run_bootloader</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P kdumpgui_run_bootloader off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_kdumpgui_run_bootloader_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_kerberos_enabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the kerberos_enabled SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">kerberos_enabled</html:code> is enabled.
If this setting is disabled, it should be enabled to allow confined
applications to run with Kerberos.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">kerberos_enabled</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P kerberos_enabled on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_kerberos_enabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ksmtuned_use_cifs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ksmtuned_use_cifs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ksmtuned_use_cifs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ksmtuned_use_cifs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ksmtuned_use_cifs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ksmtuned_use_cifs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ksmtuned_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ksmtuned_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ksmtuned_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ksmtuned_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ksmtuned_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ksmtuned_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_logadm_exec_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the logadm_exec_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">logadm_exec_content</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">logadm_exec_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P logadm_exec_content on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_logadm_exec_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_logging_syslogd_can_sendmail" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the logging_syslogd_can_sendmail SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">logging_syslogd_can_sendmail</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">logging_syslogd_can_sendmail</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P logging_syslogd_can_sendmail off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_logging_syslogd_can_sendmail_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_logging_syslogd_run_nagios_plugins" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the logging_syslogd_run_nagios_plugins SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">logging_syslogd_run_nagios_plugins</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">logging_syslogd_run_nagios_plugins</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P logging_syslogd_run_nagios_plugins off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_logging_syslogd_run_nagios_plugins_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_logging_syslogd_use_tty" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the logging_syslogd_use_tty SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">logging_syslogd_use_tty</html:code> is enabled.
If this setting is disabled, it should be enabled as it allows <html:code xmlns:html="http://www.w3.org/1999/xhtml">syslog</html:code>
the ability to read/write to terminal.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">logging_syslogd_use_tty</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P logging_syslogd_use_tty on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_logging_syslogd_use_tty_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_login_console_enabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the login_console_enabled SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">login_console_enabled</html:code> is enabled.
If this setting is disabled, it should be enabled as it allows login from
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/console</html:code> to a console session.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">login_console_enabled</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P login_console_enabled on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_login_console_enabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_logrotate_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the logrotate_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">logrotate_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">logrotate_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P logrotate_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_logrotate_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_logwatch_can_network_connect_mail" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the logwatch_can_network_connect_mail SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">logwatch_can_network_connect_mail</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">logwatch_can_network_connect_mail</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P logwatch_can_network_connect_mail off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_logwatch_can_network_connect_mail_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_lsmd_plugin_connect_any" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the lsmd_plugin_connect_any SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">lsmd_plugin_connect_any</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">lsmd_plugin_connect_any</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P lsmd_plugin_connect_any off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_lsmd_plugin_connect_any_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mailman_use_fusefs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mailman_use_fusefs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mailman_use_fusefs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mailman_use_fusefs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mailman_use_fusefs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mailman_use_fusefs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mcelog_client" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mcelog_client SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mcelog_client</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mcelog_client</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mcelog_client off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mcelog_client_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mcelog_exec_scripts" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the mcelog_exec_scripts SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mcelog_exec_scripts</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mcelog_exec_scripts</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mcelog_exec_scripts on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mcelog_exec_scripts_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mcelog_foreground" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mcelog_foreground SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mcelog_foreground</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mcelog_foreground</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mcelog_foreground off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mcelog_foreground_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mcelog_server" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mcelog_server SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mcelog_server</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mcelog_server</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mcelog_server off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mcelog_server_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_minidlna_read_generic_user_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the minidlna_read_generic_user_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">minidlna_read_generic_user_content</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">minidlna_read_generic_user_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P minidlna_read_generic_user_content off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_minidlna_read_generic_user_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mmap_low_allowed" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mmap_low_allowed SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mmap_low_allowed</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mmap_low_allowed</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mmap_low_allowed off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mmap_low_allowed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mock_enable_homedirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mock_enable_homedirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mock_enable_homedirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mock_enable_homedirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mock_enable_homedirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mock_enable_homedirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mount_anyfile" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the mount_anyfile SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mount_anyfile</html:code> is enabled.
If this setting is disabled, it should be enabled to allow any file
or directory to be mounted.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mount_anyfile</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mount_anyfile on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mount_anyfile_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mozilla_plugin_bind_unreserved_ports" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mozilla_plugin_bind_unreserved_ports SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_plugin_bind_unreserved_ports</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_plugin_bind_unreserved_ports</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mozilla_plugin_bind_unreserved_ports off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mozilla_plugin_bind_unreserved_ports_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mozilla_plugin_can_network_connect" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mozilla_plugin_can_network_connect SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_plugin_can_network_connect</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_plugin_can_network_connect</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mozilla_plugin_can_network_connect off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mozilla_plugin_can_network_connect_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mozilla_plugin_use_bluejeans" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mozilla_plugin_use_bluejeans SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_plugin_use_bluejeans</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_plugin_use_bluejeans</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mozilla_plugin_use_bluejeans off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mozilla_plugin_use_bluejeans_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mozilla_plugin_use_gps" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mozilla_plugin_use_gps SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_plugin_use_gps</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_plugin_use_gps</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mozilla_plugin_use_gps off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mozilla_plugin_use_gps_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mozilla_plugin_use_spice" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mozilla_plugin_use_spice SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_plugin_use_spice</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_plugin_use_spice</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mozilla_plugin_use_spice off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mozilla_plugin_use_spice_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mozilla_read_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mozilla_read_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_read_content</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mozilla_read_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mozilla_read_content off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mozilla_read_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mpd_enable_homedirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mpd_enable_homedirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mpd_enable_homedirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mpd_enable_homedirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mpd_enable_homedirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mpd_enable_homedirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mpd_use_cifs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mpd_use_cifs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mpd_use_cifs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mpd_use_cifs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mpd_use_cifs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mpd_use_cifs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mpd_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mpd_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mpd_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mpd_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mpd_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mpd_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mplayer_execstack" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mplayer_execstack SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mplayer_execstack</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mplayer_execstack</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mplayer_execstack off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mplayer_execstack_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_mysql_connect_any" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the mysql_connect_any SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">mysql_connect_any</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mysql_connect_any</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P mysql_connect_any off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_mysql_connect_any_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_nagios_run_pnp4nagios" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the nagios_run_pnp4nagios SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">nagios_run_pnp4nagios</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nagios_run_pnp4nagios</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P nagios_run_pnp4nagios off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_nagios_run_pnp4nagios_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_nagios_run_sudo" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the nagios_run_sudo SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">nagios_run_sudo</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nagios_run_sudo</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P nagios_run_sudo off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_nagios_run_sudo_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_named_tcp_bind_http_port" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the named_tcp_bind_http_port SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">named_tcp_bind_http_port</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">named_tcp_bind_http_port</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P named_tcp_bind_http_port off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_named_tcp_bind_http_port_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_named_write_master_zones" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the named_write_master_zones SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">named_write_master_zones</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">named_write_master_zones</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P named_write_master_zones off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_named_write_master_zones_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_neutron_can_network" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the neutron_can_network SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">neutron_can_network</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">neutron_can_network</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P neutron_can_network off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_neutron_can_network_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_nfsd_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the nfsd_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">nfsd_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nfsd_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P nfsd_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_nfsd_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_nfs_export_all_ro" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the nfs_export_all_ro SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">nfs_export_all_ro</html:code> is enabled.
If this setting is disabled, it should be enabled as it allows NFS to
export read-only mounts.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nfs_export_all_ro</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P nfs_export_all_ro on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_nfs_export_all_ro_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_nfs_export_all_rw" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the nfs_export_all_rw SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">nfs_export_all_rw</html:code> is enabled.
If this setting is disabled, it should be enabled as it allows NFS to
export read/write mounts.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nfs_export_all_rw</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P nfs_export_all_rw on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_nfs_export_all_rw_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_nis_enabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the nis_enabled SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">nis_enabled</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nis_enabled</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P nis_enabled off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_nis_enabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_nscd_use_shm" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the nscd_use_shm SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">nscd_use_shm</html:code> is enabled.
If this setting is disabled, it should be enabled to allow <html:code xmlns:html="http://www.w3.org/1999/xhtml">nscd</html:code>
to use shared memory.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nscd_use_shm</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P nscd_use_shm on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_nscd_use_shm_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_openshift_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the openshift_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">openshift_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">openshift_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P openshift_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_openshift_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_openvpn_can_network_connect" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the openvpn_can_network_connect SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">openvpn_can_network_connect</html:code> is enabled.
This setting should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">openvpn_can_network_connect</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P openvpn_can_network_connect off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_openvpn_can_network_connect_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_openvpn_enable_homedirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the openvpn_enable_homedirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">openvpn_enable_homedirs</html:code> is enabled.
This setting should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">openvpn_enable_homedirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P openvpn_enable_homedirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_openvpn_enable_homedirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_openvpn_run_unconfined" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the openvpn_run_unconfined SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">openvpn_run_unconfined</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">openvpn_run_unconfined</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P openvpn_run_unconfined off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_openvpn_run_unconfined_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_pcp_bind_all_unreserved_ports" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the pcp_bind_all_unreserved_ports SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">pcp_bind_all_unreserved_ports</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">pcp_bind_all_unreserved_ports</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P pcp_bind_all_unreserved_ports off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_pcp_bind_all_unreserved_ports_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_pcp_read_generic_logs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the pcp_read_generic_logs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">pcp_read_generic_logs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">pcp_read_generic_logs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P pcp_read_generic_logs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_pcp_read_generic_logs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_piranha_lvs_can_network_connect" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the piranha_lvs_can_network_connect SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">piranha_lvs_can_network_connect</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">piranha_lvs_can_network_connect</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P piranha_lvs_can_network_connect off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_piranha_lvs_can_network_connect_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_polipo_connect_all_unreserved" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the polipo_connect_all_unreserved SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">polipo_connect_all_unreserved</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">polipo_connect_all_unreserved</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P polipo_connect_all_unreserved off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_polipo_connect_all_unreserved_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_polipo_session_bind_all_unreserved_ports" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the polipo_session_bind_all_unreserved_ports SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">polipo_session_bind_all_unreserved_ports</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">polipo_session_bind_all_unreserved_ports</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P polipo_session_bind_all_unreserved_ports off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_polipo_session_bind_all_unreserved_ports_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_polipo_session_users" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the polipo_session_users SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">polipo_session_users</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">polipo_session_users</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P polipo_session_users off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_polipo_session_users_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_polipo_use_cifs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the polipo_use_cifs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">polipo_use_cifs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">polipo_use_cifs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P polipo_use_cifs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_polipo_use_cifs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_polipo_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the polipo_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">polipo_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">polipo_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P polipo_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_polipo_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_polyinstantiation_enabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the polyinstantiation_enabled SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">polyinstantiation_enabled</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">polyinstantiation_enabled</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P polyinstantiation_enabled off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_polyinstantiation_enabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_postfix_local_write_mail_spool" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the postfix_local_write_mail_spool SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">postfix_local_write_mail_spool</html:code> is enabled.
If this setting is disabled, it should be enabled as it allows Postfix to write
to the mail spool directories.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">postfix_local_write_mail_spool</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P postfix_local_write_mail_spool on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_postfix_local_write_mail_spool_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_postgresql_can_rsync" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the postgresql_can_rsync SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">postgresql_can_rsync</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">postgresql_can_rsync</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P postgresql_can_rsync off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_postgresql_can_rsync_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_postgresql_selinux_transmit_client_label" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the postgresql_selinux_transmit_client_label SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">postgresql_selinux_transmit_client_label</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">postgresql_selinux_transmit_client_label</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P postgresql_selinux_transmit_client_label off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_postgresql_selinux_transmit_client_label_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_postgresql_selinux_unconfined_dbadm" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the postgresql_selinux_unconfined_dbadm SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">postgresql_selinux_unconfined_dbadm</html:code> is enabled.
If this setting is disabled, it should be enabled as it allows Database Administrators to
execute Data Manipulation Language (DML) statements.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">postgresql_selinux_unconfined_dbadm</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P postgresql_selinux_unconfined_dbadm on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_postgresql_selinux_unconfined_dbadm_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_postgresql_selinux_users_ddl" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the postgresql_selinux_users_ddl SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">postgresql_selinux_users_ddl</html:code> is enabled.
If this setting is disabled, it should be enabled as it allows Database Administrators to
execute Data Definition Language (DDL) statements.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">postgresql_selinux_users_ddl</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P postgresql_selinux_users_ddl on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_postgresql_selinux_users_ddl_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_pppd_can_insmod" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the pppd_can_insmod SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">pppd_can_insmod</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">pppd_can_insmod</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P pppd_can_insmod off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_pppd_can_insmod_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_pppd_for_user" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the pppd_for_user SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">pppd_for_user</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">pppd_for_user</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P pppd_for_user off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_pppd_for_user_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_privoxy_connect_any" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the privoxy_connect_any SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">privoxy_connect_any</html:code> is enabled.
This setting should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">privoxy_connect_any</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P privoxy_connect_any off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_privoxy_connect_any_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_prosody_bind_http_port" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the prosody_bind_http_port SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">prosody_bind_http_port</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">prosody_bind_http_port</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P prosody_bind_http_port off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_prosody_bind_http_port_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_puppetagent_manage_all_files" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the puppetagent_manage_all_files SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">puppetagent_manage_all_files</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">puppetagent_manage_all_files</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P puppetagent_manage_all_files off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_puppetagent_manage_all_files_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_puppetmaster_use_db" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the puppetmaster_use_db SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">puppetmaster_use_db</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">puppetmaster_use_db</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P puppetmaster_use_db off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_puppetmaster_use_db_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_racoon_read_shadow" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the racoon_read_shadow SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">racoon_read_shadow</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">racoon_read_shadow</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P racoon_read_shadow off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_racoon_read_shadow_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_rsync_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the rsync_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsync_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsync_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P rsync_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_rsync_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_rsync_client" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the rsync_client SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsync_client</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsync_client</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P rsync_client off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_rsync_client_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_rsync_export_all_ro" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the rsync_export_all_ro SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsync_export_all_ro</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsync_export_all_ro</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P rsync_export_all_ro off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_rsync_export_all_ro_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_rsync_full_access" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the rsync_full_access SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsync_full_access</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsync_full_access</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P rsync_full_access off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_rsync_full_access_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_samba_create_home_dirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the samba_create_home_dirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_create_home_dirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_create_home_dirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P samba_create_home_dirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_samba_create_home_dirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_samba_domain_controller" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the samba_domain_controller SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_domain_controller</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_domain_controller</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P samba_domain_controller off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_samba_domain_controller_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_samba_enable_home_dirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the samba_enable_home_dirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_enable_home_dirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_enable_home_dirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P samba_enable_home_dirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_samba_enable_home_dirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_samba_export_all_ro" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the samba_export_all_ro SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_export_all_ro</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_export_all_ro</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P samba_export_all_ro off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_samba_export_all_ro_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_samba_export_all_rw" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the samba_export_all_rw SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_export_all_rw</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_export_all_rw</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P samba_export_all_rw off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_samba_export_all_rw_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_samba_load_libgfapi" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the samba_load_libgfapi SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_load_libgfapi</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_load_libgfapi</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P samba_load_libgfapi off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_samba_load_libgfapi_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_samba_portmapper" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the samba_portmapper SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_portmapper</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_portmapper</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P samba_portmapper off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_samba_portmapper_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_samba_run_unconfined" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the samba_run_unconfined SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_run_unconfined</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_run_unconfined</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P samba_run_unconfined off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_samba_run_unconfined_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_samba_share_fusefs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the samba_share_fusefs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_share_fusefs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_share_fusefs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P samba_share_fusefs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_samba_share_fusefs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_samba_share_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the samba_share_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_share_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_share_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P samba_share_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_samba_share_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_sanlock_use_fusefs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the sanlock_use_fusefs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">sanlock_use_fusefs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sanlock_use_fusefs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P sanlock_use_fusefs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_sanlock_use_fusefs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_sanlock_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the sanlock_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">sanlock_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sanlock_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P sanlock_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_sanlock_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_sanlock_use_samba" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the sanlock_use_samba SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">sanlock_use_samba</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sanlock_use_samba</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P sanlock_use_samba off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_sanlock_use_samba_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_saslauthd_read_shadow" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the saslauthd_read_shadow SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">saslauthd_read_shadow</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">saslauthd_read_shadow</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P saslauthd_read_shadow off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_saslauthd_read_shadow_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_secadm_exec_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the secadm_exec_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">secadm_exec_content</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">secadm_exec_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P secadm_exec_content on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_secadm_exec_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_secure_mode_insmod" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the secure_mode_insmod SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">secure_mode_insmod</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">secure_mode_insmod</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P secure_mode_insmod off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_secure_mode_insmod_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_secure_mode" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the secure_mode SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">secure_mode</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">secure_mode</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P secure_mode off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_secure_mode_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_secure_mode_policyload" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the secure_mode_policyload SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">secure_mode_policyload</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">secure_mode_policyload</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P secure_mode_policyload off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_secure_mode_policyload_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_direct_dri_enabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure the selinuxuser_direct_dri_enabled SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_direct_dri_enabled</html:code> is enabled.
If XWindows is not installed or used on the system, this setting should be disabled.
Otherwise, enable it.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_direct_dri_enabled</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_direct_dri_enabled off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_direct_dri_enabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_execheap" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the selinuxuser_execheap SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_execheap</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_execheap</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_execheap off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_execheap_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_execmod" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the selinuxuser_execmod SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_execmod</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_execmod</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_execmod on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_execmod_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_execstack" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">disable the selinuxuser_execstack SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_execstack</html:code> is enabled.
This setting should be disabled as unconfined executables should not be able
to make their stack executable.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_execstack</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_execstack off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_execstack_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_mysql_connect_enabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the selinuxuser_mysql_connect_enabled SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_mysql_connect_enabled</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_mysql_connect_enabled</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_mysql_connect_enabled off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_mysql_connect_enabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_ping" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the selinuxuser_ping SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_ping</html:code> is enabled.
If this setting is disabled, it should be enabled as it allows confined users
to use ping and traceroute which is helpful for network troubleshooting.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_ping</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_ping on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_ping_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_postgresql_connect_enabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the selinuxuser_postgresql_connect_enabled SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_postgresql_connect_enabled</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_postgresql_connect_enabled</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_postgresql_connect_enabled off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_postgresql_connect_enabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_rw_noexattrfile" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the selinuxuser_rw_noexattrfile SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_rw_noexattrfile</html:code> is enabled.
This setting should be disabled as users should not be able to read/write files
on filesystems that do not have extended attributes e.g. FAT, CDROM, FLOPPY, etc.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_rw_noexattrfile</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_rw_noexattrfile off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_rw_noexattrfile_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_share_music" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the selinuxuser_share_music SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_share_music</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_share_music</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_share_music off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_share_music_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_tcp_server" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the selinuxuser_tcp_server SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_tcp_server</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_tcp_server</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_tcp_server off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_tcp_server_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_udp_server" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the selinuxuser_udp_server SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_udp_server</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_udp_server</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_udp_server off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_udp_server_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_selinuxuser_use_ssh_chroot" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the selinuxuser_use_ssh_chroot SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_use_ssh_chroot</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">selinuxuser_use_ssh_chroot</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P selinuxuser_use_ssh_chroot off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_selinuxuser_use_ssh_chroot_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_sftpd_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the sftpd_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">sftpd_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sftpd_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P sftpd_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_sftpd_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_sftpd_enable_homedirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the sftpd_enable_homedirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">sftpd_enable_homedirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sftpd_enable_homedirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P sftpd_enable_homedirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_sftpd_enable_homedirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_sftpd_full_access" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the sftpd_full_access SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">sftpd_full_access</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sftpd_full_access</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P sftpd_full_access off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_sftpd_full_access_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_sftpd_write_ssh_home" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the sftpd_write_ssh_home SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">sftpd_write_ssh_home</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sftpd_write_ssh_home</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P sftpd_write_ssh_home off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_sftpd_write_ssh_home_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_sge_domain_can_network_connect" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the sge_domain_can_network_connect SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">sge_domain_can_network_connect</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sge_domain_can_network_connect</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P sge_domain_can_network_connect off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_sge_domain_can_network_connect_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_sge_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the sge_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">sge_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sge_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P sge_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_sge_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_smartmon_3ware" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the smartmon_3ware SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">smartmon_3ware</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">smartmon_3ware</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P smartmon_3ware off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_smartmon_3ware_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_smbd_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the smbd_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">smbd_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">smbd_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P smbd_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_smbd_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_spamassassin_can_network" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the spamassassin_can_network SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">spamassassin_can_network</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">spamassassin_can_network</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P spamassassin_can_network off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_spamassassin_can_network_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_spamd_enable_home_dirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the spamd_enable_home_dirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">spamd_enable_home_dirs</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">spamd_enable_home_dirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P spamd_enable_home_dirs on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_spamd_enable_home_dirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_squid_connect_any" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the squid_connect_any SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">squid_connect_any</html:code> is enabled.
This setting should be disabled as squid should only connect on specified
ports.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">squid_connect_any</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P squid_connect_any off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_squid_connect_any_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_squid_use_tproxy" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the squid_use_tproxy SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">squid_use_tproxy</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">squid_use_tproxy</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P squid_use_tproxy off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_squid_use_tproxy_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ssh_chroot_rw_homedirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ssh_chroot_rw_homedirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ssh_chroot_rw_homedirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ssh_chroot_rw_homedirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ssh_chroot_rw_homedirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ssh_chroot_rw_homedirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ssh_keysign" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ssh_keysign SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ssh_keysign</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ssh_keysign</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ssh_keysign off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ssh_keysign_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_ssh_sysadm_login" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the ssh_sysadm_login SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">ssh_sysadm_login</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ssh_sysadm_login</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P ssh_sysadm_login off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_ssh_sysadm_login_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_staff_exec_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the staff_exec_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">staff_exec_content</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">staff_exec_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P staff_exec_content on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_staff_exec_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_staff_use_svirt" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the staff_use_svirt SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">staff_use_svirt</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">staff_use_svirt</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P staff_use_svirt off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_staff_use_svirt_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_swift_can_network" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the swift_can_network SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">swift_can_network</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">swift_can_network</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P swift_can_network off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_swift_can_network_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_sysadm_exec_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the sysadm_exec_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">sysadm_exec_content</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sysadm_exec_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P sysadm_exec_content on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_sysadm_exec_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_telepathy_connect_all_ports" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the telepathy_connect_all_ports SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">telepathy_connect_all_ports</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">telepathy_connect_all_ports</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P telepathy_connect_all_ports off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_telepathy_connect_all_ports_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_telepathy_tcp_connect_generic_network_ports" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the telepathy_tcp_connect_generic_network_ports SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">telepathy_tcp_connect_generic_network_ports</html:code> is enabled.
This setting should be disabled as <html:code xmlns:html="http://www.w3.org/1999/xhtml">telepathy</html:code> should not connect to any generic network
ports.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">telepathy_tcp_connect_generic_network_ports</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P telepathy_tcp_connect_generic_network_ports off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_telepathy_tcp_connect_generic_network_ports_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_tftp_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the tftp_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P tftp_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_tftp_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_tftp_home_dir" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the tftp_home_dir SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp_home_dir</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp_home_dir</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P tftp_home_dir off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_tftp_home_dir_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_tmpreaper_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the tmpreaper_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">tmpreaper_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">tmpreaper_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P tmpreaper_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_tmpreaper_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_tmpreaper_use_samba" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the tmpreaper_use_samba SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">tmpreaper_use_samba</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">tmpreaper_use_samba</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P tmpreaper_use_samba off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_tmpreaper_use_samba_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_tor_bind_all_unreserved_ports" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the tor_bind_all_unreserved_ports SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">tor_bind_all_unreserved_ports</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">tor_bind_all_unreserved_ports</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P tor_bind_all_unreserved_ports off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_tor_bind_all_unreserved_ports_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_tor_can_network_relay" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the tor_can_network_relay SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">tor_can_network_relay</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">tor_can_network_relay</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P tor_can_network_relay off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_tor_can_network_relay_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_unconfined_chrome_sandbox_transition" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the unconfined_chrome_sandbox_transition SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">unconfined_chrome_sandbox_transition</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">unconfined_chrome_sandbox_transition</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P unconfined_chrome_sandbox_transition on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_unconfined_chrome_sandbox_transition_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_unconfined_login" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the unconfined_login SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">unconfined_login</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">unconfined_login</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P unconfined_login on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_unconfined_login_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_unconfined_mozilla_plugin_transition" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the unconfined_mozilla_plugin_transition SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">unconfined_mozilla_plugin_transition</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">unconfined_mozilla_plugin_transition</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P unconfined_mozilla_plugin_transition on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_unconfined_mozilla_plugin_transition_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_unprivuser_use_svirt" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the unprivuser_use_svirt SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">unprivuser_use_svirt</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">unprivuser_use_svirt</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P unprivuser_use_svirt off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_unprivuser_use_svirt_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_use_ecryptfs_home_dirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the use_ecryptfs_home_dirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">use_ecryptfs_home_dirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">use_ecryptfs_home_dirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P use_ecryptfs_home_dirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_use_ecryptfs_home_dirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_use_fusefs_home_dirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the use_fusefs_home_dirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">use_fusefs_home_dirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">use_fusefs_home_dirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P use_fusefs_home_dirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_use_fusefs_home_dirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_use_lpd_server" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the use_lpd_server SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">use_lpd_server</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">use_lpd_server</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P use_lpd_server off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_use_lpd_server_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_use_nfs_home_dirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the use_nfs_home_dirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">use_nfs_home_dirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">use_nfs_home_dirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P use_nfs_home_dirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_use_nfs_home_dirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_user_exec_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the user_exec_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">user_exec_content</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">user_exec_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P user_exec_content on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_user_exec_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_use_samba_home_dirs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the use_samba_home_dirs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">use_samba_home_dirs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">use_samba_home_dirs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P use_samba_home_dirs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_use_samba_home_dirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_varnishd_connect_any" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the varnishd_connect_any SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">varnishd_connect_any</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">varnishd_connect_any</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P varnishd_connect_any off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_varnishd_connect_any_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_read_qemu_ga_data" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_read_qemu_ga_data SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_read_qemu_ga_data</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_read_qemu_ga_data</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_read_qemu_ga_data off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_read_qemu_ga_data_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_rw_qemu_ga_data" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_rw_qemu_ga_data SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_rw_qemu_ga_data</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_rw_qemu_ga_data</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_rw_qemu_ga_data off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_rw_qemu_ga_data_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_sandbox_use_all_caps" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_sandbox_use_all_caps SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_all_caps</html:code> is enabled.
This setting is disabled as containers should not run with privileges.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_all_caps</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_sandbox_use_all_caps off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_sandbox_use_all_caps_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_sandbox_use_audit" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the virt_sandbox_use_audit SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_audit</html:code> is enabled.
If this setting is disabled, it should be enabled to allow sandboxed containers
to send audit messages.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_audit</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_sandbox_use_audit on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_sandbox_use_audit_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_sandbox_use_mknod" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_sandbox_use_mknod SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_mknod</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_mknod</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_sandbox_use_mknod off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_sandbox_use_mknod_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_sandbox_use_netlink" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_sandbox_use_netlink SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_netlink</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_netlink</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_sandbox_use_netlink off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_sandbox_use_netlink_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_sandbox_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_sandbox_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_sandbox_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_sandbox_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_sandbox_use_samba" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_sandbox_use_samba SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_samba</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_samba</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_sandbox_use_samba off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_sandbox_use_samba_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_sandbox_use_sys_admin" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_sandbox_use_sys_admin SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_sys_admin</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_sandbox_use_sys_admin</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_sandbox_use_sys_admin off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_sandbox_use_sys_admin_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_transition_userdomain" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_transition_userdomain SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_transition_userdomain</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_transition_userdomain</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_transition_userdomain off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_transition_userdomain_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_use_comm" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_use_comm SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_comm</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_comm</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_use_comm off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_use_comm_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_use_execmem" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_use_execmem SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_execmem</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_execmem</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_use_execmem off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_use_execmem_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_use_fusefs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_use_fusefs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_fusefs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_fusefs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_use_fusefs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_use_fusefs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_use_rawip" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_use_rawip SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_rawip</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_rawip</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_use_rawip off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_use_rawip_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_use_samba" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_use_samba SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_samba</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_samba</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_use_samba off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_use_samba_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_use_sanlock" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_use_sanlock SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_sanlock</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_sanlock</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_use_sanlock off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_use_sanlock_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_use_usb" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_use_usb SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_usb</html:code> is enabled.
This setting should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_usb</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_use_usb off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_use_usb_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_virt_use_xserver" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the virt_use_xserver SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_xserver</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">virt_use_xserver</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P virt_use_xserver off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_virt_use_xserver_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_webadm_manage_user_files" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the webadm_manage_user_files SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">webadm_manage_user_files</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">webadm_manage_user_files</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P webadm_manage_user_files off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_webadm_manage_user_files_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_webadm_read_user_files" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the webadm_read_user_files SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">webadm_read_user_files</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">webadm_read_user_files</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P webadm_read_user_files off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_webadm_read_user_files_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_wine_mmap_zero_ignore" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the wine_mmap_zero_ignore SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">wine_mmap_zero_ignore</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">wine_mmap_zero_ignore</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P wine_mmap_zero_ignore off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_wine_mmap_zero_ignore_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xdm_bind_vnc_tcp_port" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xdm_bind_vnc_tcp_port SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xdm_bind_vnc_tcp_port</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xdm_bind_vnc_tcp_port</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xdm_bind_vnc_tcp_port off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xdm_bind_vnc_tcp_port_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xdm_exec_bootloader" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xdm_exec_bootloader SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xdm_exec_bootloader</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xdm_exec_bootloader</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xdm_exec_bootloader off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xdm_exec_bootloader_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xdm_sysadm_login" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xdm_sysadm_login SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xdm_sysadm_login</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xdm_sysadm_login</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xdm_sysadm_login off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xdm_sysadm_login_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xdm_write_home" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xdm_write_home SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xdm_write_home</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xdm_write_home</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xdm_write_home off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xdm_write_home_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xend_run_blktap" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the xend_run_blktap SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xend_run_blktap</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xend_run_blktap</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xend_run_blktap on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xend_run_blktap_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xend_run_qemu" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable the xend_run_qemu SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xend_run_qemu</html:code> is enabled.
If this setting is disabled, it should be enabled.

        To enable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xend_run_qemu</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xend_run_qemu on</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xend_run_qemu_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xen_use_nfs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xen_use_nfs SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xen_use_nfs</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xen_use_nfs</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xen_use_nfs off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xen_use_nfs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xguest_connect_network" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xguest_connect_network SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xguest_connect_network</html:code> is enabled.
This setting should be disabled as guest users should not be able to configure
<html:code xmlns:html="http://www.w3.org/1999/xhtml">NetworkManager</html:code>.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xguest_connect_network</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xguest_connect_network off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xguest_connect_network_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xguest_exec_content" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xguest_exec_content SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xguest_exec_content</html:code> is enabled.
This setting should be disabled as guest users should not be able to run
executables.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xguest_exec_content</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xguest_exec_content off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xguest_exec_content_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xguest_mount_media" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xguest_mount_media SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xguest_mount_media</html:code> is enabled.
This setting should be disabled as guest users should not be able to mount
any media.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xguest_mount_media</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xguest_mount_media off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xguest_mount_media_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xguest_use_bluetooth" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xguest_use_bluetooth SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xguest_use_bluetooth</html:code> is enabled.
This setting should be disabled as guests users should not be able to access
or use bluetooth.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xguest_use_bluetooth</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xguest_use_bluetooth off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xguest_use_bluetooth_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xserver_clients_write_xshm" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xserver_clients_write_xshm SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xserver_clients_write_xshm</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xserver_clients_write_xshm</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xserver_clients_write_xshm off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xserver_clients_write_xshm_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xserver_execmem" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xserver_execmem SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xserver_execmem</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xserver_execmem</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xserver_execmem off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xserver_execmem_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_xserver_object_manager" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the xserver_object_manager SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">xserver_object_manager</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xserver_object_manager</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P xserver_object_manager off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_xserver_object_manager_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_zabbix_can_network" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the zabbix_can_network SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">zabbix_can_network</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">zabbix_can_network</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P zabbix_can_network off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_zabbix_can_network_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_zarafa_setrlimit" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the zarafa_setrlimit SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">zarafa_setrlimit</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">zarafa_setrlimit</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P zarafa_setrlimit off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_zarafa_setrlimit_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_zebra_write_config" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the zebra_write_config SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">zebra_write_config</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">zebra_write_config</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P zebra_write_config off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_zebra_write_config_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_zoneminder_anon_write" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the zoneminder_anon_write SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">zoneminder_anon_write</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">zoneminder_anon_write</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P zoneminder_anon_write off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_zoneminder_anon_write_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sebool_zoneminder_run_sudo" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable the zoneminder_run_sudo SELinux Boolean</ns0:title>
          <ns0:description xml:lang="en-US">
By default, the SELinux boolean <html:code xmlns:html="http://www.w3.org/1999/xhtml">zoneminder_run_sudo</html:code> is disabled.
If this setting is enabled, it should be disabled.

        To disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">zoneminder_run_sudo</html:code> SELinux boolean, run the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo setsebool -P zoneminder_run_sudo off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
          <ns0:rationale xml:lang="en-US">
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sebool_zoneminder_run_sudo_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="accounts">
      <ns0:title xml:lang="en-US">Account and Access Control</ns0:title>
      <ns0:description xml:lang="en-US">In traditional Unix security, if an attacker gains
shell access to a certain login account, they can perform any action
or access any file to which that account has access. Therefore,
making it more difficult for unauthorized people to gain shell
access to accounts, particularly to privileged accounts, is a
necessary part of securing a system. This section introduces
mechanisms for restricting access to accounts under
Red Hat Enterprise Linux 7.</ns0:description>
      <ns0:Group id="accounts-restrictions">
        <ns0:title xml:lang="en-US">Protect Accounts by Restricting Password-Based Login</ns0:title>
        <ns0:description xml:lang="en-US">Conventionally, Unix shell accounts are accessed by
providing a username and password to a login program, which tests
these values for correctness using the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/passwd</html:code> and
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/shadow</html:code> files. Password-based login is vulnerable to
guessing of weak passwords, and to sniffing and man-in-the-middle
attacks against passwords entered over a network or at an insecure
console. Therefore, mechanisms for accessing accounts by entering
usernames and passwords should be restricted to those which are
operationally necessary.</ns0:description>
        <ns0:Group id="root_logins">
          <ns0:title xml:lang="en-US">Restrict Root Logins</ns0:title>
          <ns0:description xml:lang="en-US">
Direct root logins should be allowed only for emergency use.
In normal situations, the administrator should access the system
via a unique unprivileged account, and then use <html:code xmlns:html="http://www.w3.org/1999/xhtml">su</html:code> or <html:code xmlns:html="http://www.w3.org/1999/xhtml">sudo</html:code> to execute
privileged commands. Discouraging administrators from accessing the
root account directly ensures an audit trail in organizations with
multiple administrators. Locking down the channels through which
root can connect directly also reduces opportunities for
password-guessing against the root account. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">login</html:code> program
uses the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/securetty</html:code> to determine which interfaces
should allow root logins.

The virtual devices <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/console</html:code>
and <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/tty*</html:code> represent the system consoles (accessible via
the Ctrl-Alt-F1 through Ctrl-Alt-F6 keyboard sequences on a default
installation). The default securetty file also contains <html:code xmlns:html="http://www.w3.org/1999/xhtml">/dev/vc/*</html:code>.
These are likely to be deprecated in most environments, but may be retained
for compatibility. Root should also be prohibited from connecting
via network protocols. Other sections of this document
include guidance describing how to prevent root from logging in via SSH.
</ns0:description>
          <ns0:Rule id="no_direct_root_logins" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Direct root Logins Not Allowed</ns0:title>
            <ns0:description xml:lang="en-US">To further limit access to the <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code> account, administrators
can disable root logins at the console by editing the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/securetty</html:code> file.
This file lists all devices the root user is allowed to login to. If the file does
not exist at all, the root user can login through any communication device on the
system, whether via the console or via a raw network interface. This is dangerous
as user can login to his machine as root via Telnet, which sends the password in
plain text over the network. By default, Red Hat Enteprise Linux's
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/securetty</html:code> file only allows the root user to login at the console
physically attached to the machine. To prevent root from logging in, remove the
contents of this file. To prevent direct root logins, remove the contents of this
file by typing the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">
$ sudo echo &gt; /etc/securetty
</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-2(1)</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.4</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Disabling direct root logins ensures proper accountability and multifactor
authentication to privileged accounts. Users will first login, then escalate
to privileged (root) access via su / sudo. This is required for FISMA Low
and FISMA Moderate systems.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="no_direct_root_logins" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">echo &gt; /etc/securetty
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-no_direct_root_logins:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-no_direct_root_logins_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="securetty_root_login_console_only" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Restrict Virtual Console Root Logins</ns0:title>
            <ns0:description xml:lang="en-US">
To restrict root logins through the (deprecated) virtual console devices,
ensure lines of this form do not appear in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/securetty</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">vc/1
vc/2
vc/3
vc/4</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6(2)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">770</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Preventing direct root login to virtual console devices
helps ensure accountability for actions taken on the system
using the root account.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="securetty_root_login_console_only" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">sed -i '/^vc\//d' /etc/securetty
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-securetty_root_login_console_only:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-securetty_root_login_console_only_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="restrict_serial_port_logins" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Restrict Serial Port Root Logins</ns0:title>
            <ns0:description xml:lang="en-US">To restrict root logins on serial ports,
ensure lines of this form do not appear in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/securetty</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ttyS0
ttyS1</html:pre>

</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6(2)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">770</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Preventing direct root login to serial port interfaces
helps ensure accountability for actions taken on the systems
using the root account.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="restrict_serial_port_logins" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">sed -i '/ttyS/d' /etc/securetty
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-restrict_serial_port_logins:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-restrict_serial_port_logins_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="no_root_webbrowsing" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Restrict Web Browser Use for Administrative Accounts</ns0:title>
            <ns0:description xml:lang="en-US">
Enforce policy requiring administrative accounts use web browsers only for
local service administration.
</ns0:description>
            <ns0:rationale xml:lang="en-US">
If a browser vulnerability is exploited while running with administrative privileges,
the entire system could be compromised. Specific exceptions for local service
administration should be documented in site-defined policy.
</ns0:rationale>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-no_root_webbrowsing_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="no_shelllogin_for_systemaccounts" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Ensure that System Accounts Do Not Run a Shell Upon Login</ns0:title>
            <ns0:description xml:lang="en-US">
Some accounts are not associated with a human user of the system, and exist to
perform some administrative function. Should an attacker be able to log into
these accounts, they should not be granted access to a shell.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The login shell for each local account is stored in the last field of each line
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/passwd</html:code>. System accounts are those user accounts with a user ID
less than UID_MIN, where value of UID_MIN directive is set in
/etc/login.defs configuration file. In the default configuration UID_MIN is set
to 1000, thus system accounts are those user accounts with a user ID less than
1000. The user ID is stored in the third field. If any system account
<html:i xmlns:html="http://www.w3.org/1999/xhtml">SYSACCT</html:i> (other than root) has a login shell, disable it with the
command: <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo usermod -s /sbin/nologin <html:i>SYSACCT</html:i></html:pre>
</ns0:description>
            <ns0:warning category="functionality" xml:lang="en-US">
Do not perform the steps in this section on the root account. Doing so might
cause the system to become inaccessible.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-2</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:rationale xml:lang="en-US">
Ensuring shells are not given to system accounts upon login makes it more
difficult for attackers to make use of system accounts.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-no_shelllogin_for_systemaccounts:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-no_shelllogin_for_systemaccounts_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_no_uid_except_zero" selected="false" severity="high">
            <ns0:title xml:lang="en-US">Verify Only Root Has UID 0</ns0:title>
            <ns0:description xml:lang="en-US">
If any account other than root has a UID of 0, this misconfiguration should 
be investigated and the accounts other than root should be removed or 
have their UID changed.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the account is associated with system commands or applications the UID should be changed
to one greater than "0" but less than "1000." Otherwise assign a UID greater than "1000" that
has not already been assigned.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-2(1)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-4</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">
An account has root authority if it has a UID of 0. Multiple accounts
with a UID of 0 afford more opportunity for potential intruders to
guess a password for a privileged account. Proper configuration of
sudo is recommended to afford multiple system administrators
access to root privileges in an accountable manner.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_no_uid_except_zero" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">awk -F: '$3 == 0 &amp;&amp; $1 != "root" { print $1 }' /etc/passwd | xargs passwd -l
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_no_uid_except_zero:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_no_uid_except_zero_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="root_path_default" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Root Path Must Be Vendor Default</ns0:title>
            <ns0:description xml:lang="en-US">
Assuming root shell is bash, edit the following files:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">~/.profile</html:pre>
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">~/.bashrc</html:pre>
Change any <html:code xmlns:html="http://www.w3.org/1999/xhtml">PATH</html:code> variables to the vendor default for root and remove any
empty <html:code xmlns:html="http://www.w3.org/1999/xhtml">PATH</html:code> entries or references to relative paths.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SA-8</ns0:reference>
            <ns0:rationale xml:lang="en-US">
The root account's executable search path must be the vendor default, and must
contain only absolute paths.
</ns0:rationale>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-root_path_default_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="password_storage">
          <ns0:title xml:lang="en-US">Verify Proper Storage and Existence of Password
Hashes</ns0:title>
          <ns0:description xml:lang="en-US">
By default, password hashes for local accounts are stored
in the second field (colon-separated) in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/shadow</html:code>. This file should be readable only by
processes running with root credentials, preventing users from
casually accessing others' password hashes and attempting
to crack them.
However, it remains possible to misconfigure the system
and store password hashes
in world-readable files such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/passwd</html:code>, or
to even store passwords themselves in plaintext on the system.
Using system-provided tools for password change/creation
should allow administrators to avoid such misconfiguration.
</ns0:description>
          <ns0:Rule id="no_empty_passwords" selected="false" severity="high">
            <ns0:title xml:lang="en-US">Prevent Log In to Accounts With Empty Password</ns0:title>
            <ns0:description xml:lang="en-US">If an account is configured for password authentication
but does not have an assigned password, it may be possible to log
into the account without authentication. Remove any instances of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nullok</html:code>
option in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/system-auth</html:code> to
prevent logins with empty passwords.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(a)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.2.3</ns0:reference>
            <ns0:rationale xml:lang="en-US">
If an account has an empty password, anyone could log in and
run commands with the privileges of that account. Accounts with
empty passwords should never be used in operational environments.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="no_empty_passwords" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">sed --follow-symlinks -i 's/\&lt;nullok\&gt;//g' /etc/pam.d/system-auth
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-no_empty_passwords:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-no_empty_passwords_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_password_all_shadowed" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify All Account Password Hashes are Shadowed</ns0:title>
            <ns0:description xml:lang="en-US">
If any password hashes are stored in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/passwd</html:code> (in the second field,
instead of an <html:code xmlns:html="http://www.w3.org/1999/xhtml">x</html:code>), the cause of this misconfiguration should be
investigated.  The account should have its password reset and the hash should be
properly stored, or the account should be deleted entirely.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(h)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.2.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">
The hashes for all user account passwords should be stored in
the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/shadow</html:code> and never in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/passwd</html:code>,
which is readable by all users.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_all_shadowed:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_all_shadowed_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="gid_passwd_group_same" selected="false" severity="low">
            <ns0:title xml:lang="en-US">All GIDs referenced in /etc/passwd must be defined in /etc/group</ns0:title>
            <ns0:description xml:lang="en-US">
Add a group to the system for each GID referenced without a corresponding group.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-2</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">764</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000104-GPOS-00051</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.5.a</ns0:reference>
            <ns0:rationale xml:lang="en-US">
If a user is assigned the Group Identifier (GID) of a group not existing on the system, and a group
with the Gruop Identifier (GID) is subsequently created, the user may have unintended rights to
any files associated with the group.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-gid_passwd_group_same:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-gid_passwd_group_same_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="no_netrc_files" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify No netrc Files Exist</ns0:title>
            <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">.netrc</html:code> files contain login information
used to auto-login into FTP servers and reside in the user's home
directory. These files may contain unencrypted passwords to
remote FTP servers making them susceptible to access by unauthorized
users and should not be used.  Any <html:code xmlns:html="http://www.w3.org/1999/xhtml">.netrc</html:code> files should be removed.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(h)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">196</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Unencrypted passwords for remote FTP servers may be stored in <html:code xmlns:html="http://www.w3.org/1999/xhtml">.netrc</html:code>
files. DoD policy requires passwords be encrypted in storage and not used
in access scripts.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-no_netrc_files:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-no_netrc_files_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="password_expiration">
          <ns0:title xml:lang="en-US">Set Password Expiration Parameters</ns0:title>
          <ns0:description xml:lang="en-US">The file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code> controls several
password-related settings. Programs such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">passwd</html:code>,
<html:code xmlns:html="http://www.w3.org/1999/xhtml">su</html:code>, and
<html:code xmlns:html="http://www.w3.org/1999/xhtml">login</html:code> consult <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code> to determine
behavior with regard to password aging, expiration warnings,
and length. See the man page <html:code xmlns:html="http://www.w3.org/1999/xhtml">login.defs(5)</html:code> for more information.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Users should be forced to change their passwords, in order to
decrease the utility of compromised passwords. However, the need to
change passwords often should be balanced against the risk that
users will reuse or write down passwords if forced to change them
too often. Forcing password changes every 90-360 days, depending on
the environment, is recommended. Set the appropriate value as
<html:code xmlns:html="http://www.w3.org/1999/xhtml">PASS_MAX_DAYS</html:code> and apply it to existing accounts with the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">-M</html:code> flag.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">PASS_MIN_DAYS</html:code> (<html:code xmlns:html="http://www.w3.org/1999/xhtml">-m</html:code>) setting prevents password
changes for 7 days after the first change, to discourage password
cycling. If you use this setting, train users to contact an administrator
for an emergency password change in case a new password becomes
compromised. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">PASS_WARN_AGE</html:code> (<html:code xmlns:html="http://www.w3.org/1999/xhtml">-W</html:code>) setting gives
users 7 days of warnings at login time that their passwords are about to expire.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For example, for each existing human user <html:i xmlns:html="http://www.w3.org/1999/xhtml">USER</html:i>, expiration parameters
could be adjusted to a 180 day maximum password age, 7 day minimum password
age, and 7 day warning period with the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chage -M 180 -m 7 -W 7 USER</html:pre>
</ns0:description>
          <ns0:Value id="var_accounts_password_minlen_login_defs" type="number">
            <ns0:title xml:lang="en-US">minimum password length</ns0:title>
            <ns0:description xml:lang="en-US">Minimum number of characters in password</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">This will only check new passwords</ns0:warning>
            <ns0:value>15</ns0:value>
            <ns0:value selector="6">6</ns0:value>
            <ns0:value selector="8">8</ns0:value>
            <ns0:value selector="10">10</ns0:value>
            <ns0:value selector="12">12</ns0:value>
            <ns0:value selector="14">14</ns0:value>
            <ns0:value selector="15">15</ns0:value>
          </ns0:Value>
          <ns0:Value id="var_accounts_maximum_age_login_defs" type="number">
            <ns0:title xml:lang="en-US">maximum password age</ns0:title>
            <ns0:description xml:lang="en-US">Maximum age of password in days</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">This will only apply to newly created accounts</ns0:warning>
            <ns0:value>60</ns0:value>
            <ns0:value selector="60">60</ns0:value>
            <ns0:value selector="90">90</ns0:value>
            <ns0:value selector="120">120</ns0:value>
            <ns0:value selector="180">180</ns0:value>
          </ns0:Value>
          <ns0:Value id="var_accounts_minimum_age_login_defs" type="number">
            <ns0:title xml:lang="en-US">minimum password age</ns0:title>
            <ns0:description xml:lang="en-US">Minimum age of password in days</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">This will only apply to newly created accounts</ns0:warning>
            <ns0:value>7</ns0:value>
            <ns0:value selector="7">7</ns0:value>
            <ns0:value selector="5">5</ns0:value>
            <ns0:value selector="2">2</ns0:value>
            <ns0:value selector="1">1</ns0:value>
            <ns0:value selector="0">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="var_accounts_password_warn_age_login_defs" type="number">
            <ns0:title xml:lang="en-US">warning days before password expires</ns0:title>
            <ns0:description xml:lang="en-US">The number of days' warning given before a password expires.</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">This will only apply to newly created accounts</ns0:warning>
            <ns0:value>7</ns0:value>
            <ns0:value selector="0">0</ns0:value>
            <ns0:value selector="7">7</ns0:value>
            <ns0:value selector="14">14</ns0:value>
          </ns0:Value>
          <ns0:Rule id="accounts_password_minlen_login_defs" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set Password Minimum Length in login.defs</ns0:title>
            <ns0:description xml:lang="en-US">To specify password length requirements for new accounts,
edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code> and add or correct the following
lines:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">PASS_MIN_LEN 14</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The DoD requirement is <html:code xmlns:html="http://www.w3.org/1999/xhtml">15</html:code>. 
The FISMA requirement is <html:code xmlns:html="http://www.w3.org/1999/xhtml">12</html:code>.
If a program consults <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code> and also another PAM module
(such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_pwquality</html:code>) during a password change operation,
then the most restrictive must be satisfied. See PAM section
for more information about enforcing password quality requirements.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(f)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(a)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
            <ns0:rationale xml:lang="en-US">
Requiring a minimum password length makes password
cracking attacks more difficult by ensuring a larger
search space. However, any security benefit from an onerous requirement
must be carefully weighed against usability problems, support costs, or counterproductive
behavior that may result.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_password_minlen_login_defs" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_accounts_password_minlen_login_defs="<ns0:sub idref="var_accounts_password_minlen_login_defs" />"

grep -q ^PASS_MIN_LEN /etc/login.defs &amp;&amp; \
  sed -i "s/PASS_MIN_LEN.*/PASS_MIN_LEN     $var_accounts_password_minlen_login_defs/g" /etc/login.defs
if ! [ $? -eq 0 ]; then
    echo "PASS_MIN_LEN      $var_accounts_password_minlen_login_defs" &gt;&gt; /etc/login.defs
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_accounts_password_minlen_login_defs:var:1" value-id="var_accounts_password_minlen_login_defs" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_minlen_login_defs:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_minlen_login_defs_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_minimum_age_login_defs" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set Password Minimum Age</ns0:title>
            <ns0:description xml:lang="en-US">To specify password minimum age for new accounts,
edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code>
and add or correct the following line, replacing <html:i xmlns:html="http://www.w3.org/1999/xhtml">DAYS</html:i> appropriately:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">PASS_MIN_DAYS <html:i>DAYS</html:i></html:pre>
A value of 1 day is considered for sufficient for many
environments. The DoD requirement is 1. 
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(f)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(d)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">198</ns0:reference>
            <ns0:reference href="">SRG-OS-000075-GPOS-00043</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat
the password reuse or history enforcement requirement. If users are allowed to immediately
and continually change their password, then the password could be repeatedly changed in a 
short period of time to defeat the organization's policy regarding password reuse.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Setting the minimum password age protects against users cycling back to a favorite password
after satisfying the password reuse requirement.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_minimum_age_login_defs" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_accounts_minimum_age_login_defs="<ns0:sub idref="var_accounts_minimum_age_login_defs" />"

grep -q ^PASS_MIN_DAYS /etc/login.defs &amp;&amp; \
  sed -i "s/PASS_MIN_DAYS.*/PASS_MIN_DAYS     $var_accounts_minimum_age_login_defs/g" /etc/login.defs
if ! [ $? -eq 0 ]; then
    echo "PASS_MIN_DAYS      $var_accounts_minimum_age_login_defs" &gt;&gt; /etc/login.defs
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_accounts_minimum_age_login_defs:var:1" value-id="var_accounts_minimum_age_login_defs" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_minimum_age_login_defs:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_minimum_age_login_defs_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_maximum_age_login_defs" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set Password Maximum Age</ns0:title>
            <ns0:description xml:lang="en-US">To specify password maximum age for new accounts,
edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code>
and add or correct the following line, replacing <html:i xmlns:html="http://www.w3.org/1999/xhtml">DAYS</html:i> appropriately:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">PASS_MAX_DAYS <html:i>DAYS</html:i></html:pre>
A value of 180 days is sufficient for many environments. 
The DoD requirement is 60.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(f)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(g)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(d)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">199</ns0:reference>
            <ns0:reference href="">SRG-OS-000076-GPOS-00044</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.2.4</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">7.1.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Any password, no matter how complex, can eventually be cracked. Therefore, passwords
need to be changed periodically. If the operating system does not limit the lifetime
of passwords and force users to change their passwords, there is the risk that the
operating system passwords could be compromised. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Setting the password maximum age ensures users are required to
periodically change their passwords. Requiring shorter password lifetimes
increases the risk of users writing down the password in a convenient
location subject to physical compromise.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_maximum_age_login_defs" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_accounts_maximum_age_login_defs="<ns0:sub idref="var_accounts_maximum_age_login_defs" />"

grep -q ^PASS_MAX_DAYS /etc/login.defs &amp;&amp; \
  sed -i "s/PASS_MAX_DAYS.*/PASS_MAX_DAYS     $var_accounts_maximum_age_login_defs/g" /etc/login.defs
if ! [ $? -eq 0 ]; then
    echo "PASS_MAX_DAYS      $var_accounts_maximum_age_login_defs" &gt;&gt; /etc/login.defs
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_accounts_maximum_age_login_defs:var:1" value-id="var_accounts_maximum_age_login_defs" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_maximum_age_login_defs:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_maximum_age_login_defs_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_password_warn_age_login_defs" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Set Password Warning Age</ns0:title>
            <ns0:description xml:lang="en-US">To specify how many days prior to password
expiration that a warning will be issued to users,
edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code> and add or correct
 the following line, replacing <html:i xmlns:html="http://www.w3.org/1999/xhtml">DAYS</html:i> appropriately:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">PASS_WARN_AGE <html:i>DAYS</html:i></html:pre>
The DoD requirement is 7.

</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-2(2)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(f)</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Setting the password warning age enables users to
make the change at a practical time.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_password_warn_age_login_defs" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_accounts_password_warn_age_login_defs="<ns0:sub idref="var_accounts_password_warn_age_login_defs" />"

grep -q ^PASS_WARN_AGE /etc/login.defs &amp;&amp; \
  sed -i "s/PASS_WARN_AGE.*/PASS_WARN_AGE     $var_accounts_password_warn_age_login_defs/g" /etc/login.defs
if ! [ $? -eq 0 ]; then
    echo "PASS_WARN_AGE      $var_accounts_password_warn_age_login_defs" &gt;&gt; /etc/login.defs
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_accounts_password_warn_age_login_defs:var:1" value-id="var_accounts_password_warn_age_login_defs" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_warn_age_login_defs:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_warn_age_login_defs_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="account_expiration">
          <ns0:title xml:lang="en-US">Set Account Expiration Parameters</ns0:title>
          <ns0:description xml:lang="en-US">Accounts can be configured to be automatically disabled
after a certain time period,
meaning that they will require administrator interaction to become usable again.
Expiration of accounts after inactivity can be set for all accounts by default
and also on a per-account basis, such as for accounts that are known to be temporary.
To configure automatic expiration of an account following
the expiration of its password (that is, after the password has expired and not been changed),
run the following command, substituting <html:code xmlns:html="http://www.w3.org/1999/xhtml"><html:i>NUM_DAYS</html:i></html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml"><html:i>USER</html:i></html:code> appropriately:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chage -I <html:i>NUM_DAYS USER</html:i></html:pre>
Accounts, such as temporary accounts, can also be configured to expire on an explicitly-set date with the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">-E</html:code> option.
The file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/default/useradd</html:code> controls
default settings for all newly-created accounts created with the system's
normal command line utilities.
</ns0:description>
          <ns0:Value id="var_account_disable_post_pw_expiration" type="number">
            <ns0:title xml:lang="en-US">number of days after a password expires until the account is permanently disabled</ns0:title>
            <ns0:description xml:lang="en-US">The number of days to wait after a password expires, until the account will be permanently disabled.</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">This will only apply to newly created accounts</ns0:warning>
            <ns0:value>35</ns0:value>
            <ns0:value selector="0">0</ns0:value>
            <ns0:value selector="30">30</ns0:value>
            <ns0:value selector="35">35</ns0:value>
            <ns0:value selector="40">40</ns0:value>
            <ns0:value selector="60">60</ns0:value>
            <ns0:value selector="90">90</ns0:value>
            <ns0:value selector="180">180</ns0:value>
          </ns0:Value>
          <ns0:Rule id="account_disable_post_pw_expiration" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set Account Expiration Following Inactivity</ns0:title>
            <ns0:description xml:lang="en-US">To specify the number of days after a password expires (which
signifies inactivity) until an account is permanently disabled, add or correct
the following lines in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/default/useradd</html:code>, substituting
<html:code xmlns:html="http://www.w3.org/1999/xhtml"><html:i>NUM_DAYS</html:i></html:code> appropriately:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">INACTIVE=<html:i><ns0:sub idref="account_disable_post_pw_expiration" /></html:i></html:pre>
A value of 35 is recommended.  
If a password is currently on the
verge of expiration, then 35 days remain until the account is automatically
disabled. However, if the password will not expire for another 60 days, then 95
days could elapse until the account would be automatically disabled. See the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">useradd</html:code> man page for more information.  Determining the inactivity
timeout must be done with careful consideration of the length of a "normal"
period of inactivity for users in the particular environment. Setting
the timeout too low incurs support costs and also has the potential to impact
availability of the system to legitimate users.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-2(2)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-2(3)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-4(e)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">795</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000118-GPOS-00060</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.1.4</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Disabling inactive accounts ensures that accounts which may not
have been responsibly removed are not available to attackers
who may have compromised their credentials.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="account_disable_post_pw_expiration" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_account_disable_post_pw_expiration="<ns0:sub idref="var_account_disable_post_pw_expiration" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append /etc/default/useradd INACTIVE "$var_account_disable_post_pw_expiration" '' '%s=%s'
</ns0:fix>
            <ns0:fix complexity="low" disruption="low" id="account_disable_post_pw_expiration" reboot="false" strategy="configure" system="urn:xccdf:fix:script:ansible">- name: "Disable POST password expiration"
  lineinfile:
    create=yes
    dest="/etc/default/useradd"
    regexp="^INACTIVE"
    line="INACTIVE=-1"
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_account_disable_post_pw_expiration:var:1" value-id="var_account_disable_post_pw_expiration" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-account_disable_post_pw_expiration:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-account_disable_post_pw_expiration_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="account_unique_name" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Ensure All Accounts on the System Have Unique Names</ns0:title>
            <ns0:description xml:lang="en-US">
Change usernames, or delete accounts, so each has a unique name.
</ns0:description>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">770</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">804</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.1.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Unique usernames allow for accountability on the system.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-account_unique_name:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-account_unique_name_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="account_temp_expire_date" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Assign Expiration Date to Temporary Accounts</ns0:title>
            <ns0:description xml:lang="en-US">
Temporary accounts are established as part of normal account activation procedures
when there is a need for short-term accounts. In the event temporary 
or emergency accounts are required, configure the system to terminate 
them after a documented time period. For every temporary and
emergency account, run the following command to set an expiration date on it,
substituting <html:code xmlns:html="http://www.w3.org/1999/xhtml"><html:i>USER</html:i></html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml"><html:i>YYYY-MM-DD</html:i></html:code> appropriately:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chage -E <html:i>YYYY-MM-DD USER</html:i></html:pre>
<html:code xmlns:html="http://www.w3.org/1999/xhtml"><html:i>YYYY-MM-DD</html:i></html:code> indicates the documented expiration date for the account.
For U.S. Government systems, the operating system must be configured to automatically terminate
these types of accounts after a period of 72 hours.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-2(2)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-2(3)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">16</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1682</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">2</ns0:reference>
            <ns0:rationale xml:lang="en-US">
If temporary user accounts remain active when no longer needed or for
an excessive period, these accounts may be used to gain unauthorized access.
To mitigate this risk, automated termination of all temporary accounts
must be set upon account creation.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
</ns0:rationale>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-account_temp_expire_date_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="accounts-pam">
        <ns0:title xml:lang="en-US">Protect Accounts by Configuring PAM</ns0:title>
        <ns0:description xml:lang="en-US">PAM, or Pluggable Authentication Modules, is a system
which implements modular authentication for Linux programs. PAM provides
a flexible and configurable architecture for authentication, and it should be configured
to minimize exposure to unnecessary risk. This section contains
guidance on how to accomplish that.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
PAM is implemented as a set of shared objects which are
loaded and invoked whenever an application wishes to authenticate a
user. Typically, the application must be running as root in order
to take advantage of PAM, because PAM's modules often need to be able
to access sensitive stores of account information, such as /etc/shadow.
Traditional privileged network listeners
(e.g. sshd) or SUID programs (e.g. sudo) already meet this
requirement. An SUID root application, userhelper, is provided so
that programs which are not SUID or privileged themselves can still
take advantage of PAM.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
PAM looks in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d</html:code> for
application-specific configuration information. For instance, if
the program login attempts to authenticate a user, then PAM's
libraries follow the instructions in the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/login</html:code>
to determine what actions should be taken.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
One very important file in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d</html:code> is
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/system-auth</html:code>. This file, which is included by
many other PAM configuration files, defines 'default' system authentication
measures. Modifying this file is a good way to make far-reaching
authentication changes, for instance when implementing a
centralized authentication service.</ns0:description>
        <ns0:warning category="general" xml:lang="en-US">Be careful when making changes to PAM's
configuration files. The syntax for these files is complex, and
modifications can have unexpected consequences. The default
configurations shipped with applications should be sufficient for
most users.</ns0:warning>
        <ns0:warning category="general" xml:lang="en-US">Running <html:code xmlns:html="http://www.w3.org/1999/xhtml">authconfig</html:code> or
<html:code xmlns:html="http://www.w3.org/1999/xhtml">system-config-authentication</html:code> will re-write the PAM configuration
files, destroying any manually made changes and replacing them with
a series of system defaults. One reference to the configuration
file syntax can be found at
<html:a href="http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/sag-configuration-file.html" xmlns:html="http://www.w3.org/1999/xhtml">http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/sag-configuration-file.html</html:a>
.</ns0:warning>
        <ns0:Value id="var_password_pam_unix_remember" operator="equals" type="number">
          <ns0:title xml:lang="en-US">remember</ns0:title>
          <ns0:description xml:lang="en-US">The last n passwords for each user are saved in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/opasswd</html:code> in order to force password change history and
keep the user from alternating between the same password too
frequently.</ns0:description>
          <ns0:value>5</ns0:value>
          <ns0:value selector="0">0</ns0:value>
          <ns0:value selector="4">4</ns0:value>
          <ns0:value selector="5">5</ns0:value>
          <ns0:value selector="10">10</ns0:value>
          <ns0:value selector="24">24</ns0:value>
        </ns0:Value>
        <ns0:Rule id="display_login_attempts" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Set Last Logon/Access Notification</ns0:title>
          <ns0:description xml:lang="en-US">To configure the system to notify users of last logon/access
using <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_lastlog</html:code>, add or correct the <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_lastlog</html:code> settings in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/postlogin</html:code> to read as follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">session     [success=1 default=ignore] pam_succeed_if.so service !~ gdm* service !~ su* quiet
session     [default=1]   pam_lastlog.so nowtmp showfailed
session     optional      pam_lastlog.so silent noupdate showfailed</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-9</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.4</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Users need to be aware of activity that occurs regarding
their account. Providing users with information regarding the number
of unsuccessful attempts that were made to login to their account
allows the user to determine if any unauthorized activity has occurred
and gives them an opportunity to notify administrators.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="display_login_attempts" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
if ! `grep -q ^[^#].*pam_succeed_if.*showfailed /etc/pam.d/postlogin` ; then
  if ! grep `^session.*pam_succeed_if.so /etc/pam.d/postlogin` ; then
    echo "session     [default=1]   pam_lastlog.so nowtmp showfailed" &gt;&gt; /etc/pam.d/postlogin
    echo "session     optional      pam_lastlog.so silent noupdate showfailed" &gt;&gt; /etc/pam.d/postlogin
  else
    sed -i '/^session.*pam_succeed_if.so/a session\t    optional\t  pam_lastlog.so silent noupdate showfailed' /etc/pam.d/postlogin
    sed -i '/^session.*pam_succeed_if.so/a session\t    [default=1]\t  pam_lastlog.so nowtmp showfailed' /etc/pam.d/postlogin
  fi
else
  sed -i "s/session[ ]*\[default=1][ ]*pam_lastlog.so.*/session     [default=1]   pam_lastlog.so nowtmp showfailed/g" /etc/pam.d/postlogin
  sed -i "s/session[ ]*optional[ ]*pam_lastlog.so.*/session     optional      pam_lastlog.so silent noupdate showfailed/g" /etc/pam.d/postlogin
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-display_login_attempts:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-display_login_attempts_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="password_quality">
          <ns0:title xml:lang="en-US">Set Password Quality Requirements</ns0:title>
          <ns0:description xml:lang="en-US">The default <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_pwquality</html:code> PAM module provides strength
checking for passwords. It performs a number of checks, such as
making sure passwords are not similar to dictionary words, are of
at least a certain length, are not the previous password reversed,
and are not simply a change of case from the previous password. It
can also require passwords to be in certain character classes. The
<html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_pwquality</html:code> module is the preferred way of configuring
password requirements.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_cracklib</html:code> PAM module can also provide strength
checking for passwords as the <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_pwquality</html:code> module.
It performs a number of checks, such as making sure passwords are
not similar to dictionary words, are of at least a certain length,
are not the previous password reversed, and are not simply a change
of case from the previous password. It can also require passwords to
be in certain character classes.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The man pages <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_pwquality(8)</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_cracklib(8)</html:code>
provide information on the capabilities and configuration of
each.</ns0:description>
          <ns0:Group id="password_quality_pwquality">
            <ns0:title xml:lang="en-US">Set Password Quality Requirements with pam_pwquality</ns0:title>
            <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_pwquality</html:code> PAM module can be configured to meet
requirements for a variety of policies.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For example, to configure <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_pwquality</html:code> to require at least one uppercase
character, lowercase character, digit, and other (special)
character, make sure that <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_pwquality</html:code> exists in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/system-auth</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">password    requisite     pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=</html:pre>
If no such line exists, add one as the first line of the password section in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/system-auth</html:code>.
Next, modify the settings in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/pwquality.conf</html:code> to match the following:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">difok = 4
minlen = 14
dcredit = -1
ucredit = -1
lcredit = -1
ocredit = -1
maxrepeat = 3</html:pre>
The arguments can be modified to ensure compliance with
your organization's security policy. Discussion of each parameter follows.
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that the password quality
requirements are not enforced for the root account for some
reason.</ns0:warning>
            <ns0:Value id="var_password_pam_retry" operator="equals" type="number">
              <ns0:title xml:lang="en-US">retry</ns0:title>
              <ns0:description xml:lang="en-US">Number of retry attempts before erroring out</ns0:description>
              <ns0:value>3</ns0:value>
              <ns0:value selector="1">1</ns0:value>
              <ns0:value selector="2">2</ns0:value>
              <ns0:value selector="3">3</ns0:value>
              <ns0:value selector="4">4</ns0:value>
              <ns0:value selector="5">5</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_password_pam_maxrepeat" operator="equals" type="number">
              <ns0:title xml:lang="en-US">maxrepeat</ns0:title>
              <ns0:description xml:lang="en-US">Maximum Number of Consecutive Repeating Characters in a Password</ns0:description>
              <ns0:value>3</ns0:value>
              <ns0:value selector="1">1</ns0:value>
              <ns0:value selector="2">2</ns0:value>
              <ns0:value selector="3">3</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_password_pam_maxclassrepeat" operator="equals" type="number">
              <ns0:title xml:lang="en-US">maxclassrepeat</ns0:title>
              <ns0:description xml:lang="en-US">Maximum Number of Consecutive Repeating Characters in a Password From the Same Character Class</ns0:description>
              <ns0:value>4</ns0:value>
              <ns0:value selector="1">1</ns0:value>
              <ns0:value selector="2">2</ns0:value>
              <ns0:value selector="3">3</ns0:value>
              <ns0:value selector="4">4</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_password_pam_minlen" operator="equals" type="number">
              <ns0:title xml:lang="en-US">minlen</ns0:title>
              <ns0:description xml:lang="en-US">Minimum number of characters in password</ns0:description>
              <ns0:value>15</ns0:value>
              <ns0:value selector="6">6</ns0:value>
              <ns0:value selector="7">7</ns0:value>
              <ns0:value selector="8">8</ns0:value>
              <ns0:value selector="10">10</ns0:value>
              <ns0:value selector="12">12</ns0:value>
              <ns0:value selector="14">14</ns0:value>
              <ns0:value selector="15">15</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_password_pam_dcredit" operator="equals" type="number">
              <ns0:title xml:lang="en-US">dcredit</ns0:title>
              <ns0:description xml:lang="en-US">Minimum number of digits in password</ns0:description>
              <ns0:value>-1</ns0:value>
              <ns0:value selector="2">-2</ns0:value>
              <ns0:value selector="1">-1</ns0:value>
              <ns0:value selector="0">0</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_password_pam_ocredit" operator="equals" type="number">
              <ns0:title xml:lang="en-US">ocredit</ns0:title>
              <ns0:description xml:lang="en-US">Minimum number of other (special characters) in
password</ns0:description>
              <ns0:value>-1</ns0:value>
              <ns0:value selector="2">-2</ns0:value>
              <ns0:value selector="1">-1</ns0:value>
              <ns0:value selector="0">0</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_password_pam_lcredit" operator="equals" type="number">
              <ns0:title xml:lang="en-US">lcredit</ns0:title>
              <ns0:description xml:lang="en-US">Minimum number of lower case in password</ns0:description>
              <ns0:value>-1</ns0:value>
              <ns0:value selector="2">-2</ns0:value>
              <ns0:value selector="1">-1</ns0:value>
              <ns0:value selector="0">0</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_password_pam_ucredit" operator="equals" type="number">
              <ns0:title xml:lang="en-US">ucredit</ns0:title>
              <ns0:description xml:lang="en-US">Minimum number of upper case in password</ns0:description>
              <ns0:value>-1</ns0:value>
              <ns0:value selector="2">-2</ns0:value>
              <ns0:value selector="1">-1</ns0:value>
              <ns0:value selector="0">0</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_password_pam_difok" operator="equals" type="number">
              <ns0:title xml:lang="en-US">difok</ns0:title>
              <ns0:description xml:lang="en-US">Minimum number of characters not present in old
password</ns0:description>
              <ns0:warning category="general" xml:lang="en-US">Keep this high for short passwords</ns0:warning>
              <ns0:value>8</ns0:value>
              <ns0:value selector="2">2</ns0:value>
              <ns0:value selector="3">3</ns0:value>
              <ns0:value selector="4">4</ns0:value>
              <ns0:value selector="5">5</ns0:value>
              <ns0:value selector="6">6</ns0:value>
              <ns0:value selector="7">7</ns0:value>
              <ns0:value selector="8">8</ns0:value>
              <ns0:value selector="15">15</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_password_pam_minclass" operator="equals" type="number">
              <ns0:title xml:lang="en-US">minclass</ns0:title>
              <ns0:description xml:lang="en-US">Minimum number of categories of characters that must exist in a password</ns0:description>
              <ns0:value>3</ns0:value>
              <ns0:value selector="1">1</ns0:value>
              <ns0:value selector="2">2</ns0:value>
              <ns0:value selector="3">3</ns0:value>
              <ns0:value selector="4">4</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_accounts_passwords_pam_faillock_deny" operator="equals" type="number">
              <ns0:title xml:lang="en-US">fail_deny</ns0:title>
              <ns0:description xml:lang="en-US">Number of failed login attempts before account lockout</ns0:description>
              <ns0:value>3</ns0:value>
              <ns0:value selector="3">3</ns0:value>
              <ns0:value selector="5">5</ns0:value>
              <ns0:value selector="6">6</ns0:value>
              <ns0:value selector="10">10</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_accounts_passwords_pam_faillock_unlock_time" operator="equals" type="number">
              <ns0:title xml:lang="en-US">fail_unlock_time</ns0:title>
              <ns0:description xml:lang="en-US">Seconds before automatic unlocking after excessive failed logins</ns0:description>
              <ns0:value>604800</ns0:value>
              <ns0:value selector="600">600</ns0:value>
              <ns0:value selector="900">900</ns0:value>
              <ns0:value selector="1800">1800</ns0:value>
              <ns0:value selector="3600">3600</ns0:value>
              <ns0:value selector="86400">86400</ns0:value>
              <ns0:value selector="604800">604800</ns0:value>
            </ns0:Value>
            <ns0:Value id="var_accounts_passwords_pam_faillock_fail_interval" operator="equals" type="number">
              <ns0:title xml:lang="en-US">fail_interval</ns0:title>
              <ns0:description xml:lang="en-US">Interval for counting failed login attempts before account lockout</ns0:description>
              <ns0:value>900</ns0:value>
              <ns0:value selector="900">900</ns0:value>
              <ns0:value selector="1800">1800</ns0:value>
              <ns0:value selector="3600">3600</ns0:value>
              <ns0:value selector="86400">86400</ns0:value>
              <ns0:value selector="100000000">100000000</ns0:value>
            </ns0:Value>
            <ns0:Rule id="accounts_password_pam_retry" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Set Password Retry Prompts Permitted Per-Session</ns0:title>
              <ns0:description xml:lang="en-US">To configure the number of retry prompts that are permitted per-session:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Edit the <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_pwquality.so</html:code> statement in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/system-auth</html:code> to 
show <html:code xmlns:html="http://www.w3.org/1999/xhtml">retry=<ns0:sub idref="var_password_pam_retry" /></html:code>, or a lower value if site policy is more restrictive.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The DoD requirement is a maximum of 3 prompts per session.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.3.2</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00225</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Setting the password retry prompts that are permitted on a per-session basis to a low value
requires some software, such as SSH, to re-connect. This can slow down and
draw additional attention to some types of password-guessing attacks. Note that this
is different from account lockout, which is provided by the pam_faillock module.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="accounts_password_pam_retry" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_password_pam_retry="<ns0:sub idref="var_password_pam_retry" />"

if grep -q "retry=" /etc/pam.d/system-auth; then   
	sed -i --follow-symlinks "s/\(retry *= *\).*/\1$var_password_pam_retry/" /etc/pam.d/system-auth
else
	sed -i --follow-symlinks "/pam_pwquality.so/ s/$/ retry=$var_password_pam_retry/" /etc/pam.d/system-auth
fi
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-var_password_pam_retry:var:1" value-id="var_password_pam_retry" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_pam_retry:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_pam_retry_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="accounts_password_pam_maxrepeat" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Set Password Maximum Consecutive Repeating Characters</ns0:title>
              <ns0:description xml:lang="en-US">The pam_pwquality module's <html:code xmlns:html="http://www.w3.org/1999/xhtml">maxrepeat</html:code> parameter controls requirements for
consecutive repeating characters. When set to a positive number, it will reject passwords
which contain more than that number of consecutive characters. Modify the <html:code xmlns:html="http://www.w3.org/1999/xhtml">maxrepeat</html:code> setting
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/pwquality.conf</html:code> to equal <ns0:sub idref="var_password_pam_maxrepeat" /> to prevent a 
run of (<ns0:sub idref="var_password_pam_maxrepeat" /> + 1) or more identical characters.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">195</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000072-GPOS-00040</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Use of a complex password helps to increase the time and resources required to compromise the password. 
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at 
guessing and brute-force attacks.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Password complexity is one factor of several that determines how long it takes to crack a password. The more
complex the password, the greater the number of possible combinations that need to be tested before the
password is compromised.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Passwords with excessive repeating characters may be more vulnerable to password-guessing attacks.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="accounts_password_pam_maxrepeat" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_password_pam_maxrepeat="<ns0:sub idref="var_password_pam_maxrepeat" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/security/pwquality.conf' '^maxrepeat' $var_password_pam_maxrepeat 'CCE-27333-4' '%s = %s'
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-var_password_pam_maxrepeat:var:1" value-id="var_password_pam_maxrepeat" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_pam_maxrepeat:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_pam_maxrepeat_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="accounts_password_pam_maxclassrepeat" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Set Password to Maximum of Consecutive Repeating Characters from Same Character Class</ns0:title>
              <ns0:description xml:lang="en-US">The pam_pwquality module's <html:code xmlns:html="http://www.w3.org/1999/xhtml">maxclassrepeat</html:code> parameter controls requirements for
consecutive repeating characters from the same character class. When set to a positive number, it will reject passwords
which contain more than that number of consecutive characters from the same character class. Modify the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">maxclassrepeat</html:code> setting in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/pwquality.conf</html:code> to equal <ns0:sub idref="var_password_pam_maxclassrepeat" />
to prevent a run of (<ns0:sub idref="var_password_pam_maxclassrepeat" /> + 1) or more identical characters.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">195</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000072-GPOS-00040</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Use of a complex password helps to increase the time and resources required to comrpomise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting
attempts at guessing and brute-force attacks.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Password complexity is one factor of several that determines how long it takes to crack a password. The
more complex a password, the greater the number of possible combinations that need to be tested before the
password is compromised.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="accounts_password_pam_maxclassrepeat" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_password_pam_maxclassrepeat="<ns0:sub idref="var_password_pam_maxclassrepeat" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/security/pwquality.conf' '^maxclassrepeat' $var_password_pam_maxclassrepeat 'CCE-27512-3' '%s = %s'
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-var_password_pam_maxclassrepeat:var:1" value-id="var_password_pam_maxclassrepeat" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_pam_maxclassrepeat:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_pam_maxclassrepeat_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="accounts_password_pam_dcredit" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Set Password Strength Minimum Digit Characters</ns0:title>
              <ns0:description xml:lang="en-US">The pam_pwquality module's <html:code xmlns:html="http://www.w3.org/1999/xhtml">dcredit</html:code> parameter controls requirements for
usage of digits in a password. When set to a negative number, any password will be required to
contain that many digits. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each digit. Modify the <html:code xmlns:html="http://www.w3.org/1999/xhtml">dcredit</html:code> setting in 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/pwquality.conf</html:code> to require the use of a digit in passwords.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(a)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(b)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">194</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">194</ns0:reference>
              <ns0:reference href="">SRG-OS-000071-GPOS-00039</ns0:reference>
              <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.2.3</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.3.2</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Use of a complex password helps to increase the time and resources required
to compromise the password. Password complexity, or strength, is a measure of
the effectiveness of a password in resisting attempts at guessing and brute-force
attacks. 

Password complexity is one factor of several that determines how long it takes
to crack a password. The more complex the password, the greater the number of 
possble combinations that need to be tested before the password is compromised.
Requiring digits makes password guessing attacks more difficult by ensuring a larger
search space.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="accounts_password_pam_dcredit" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_password_pam_dcredit="<ns0:sub idref="var_password_pam_dcredit" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/security/pwquality.conf' '^dcredit' $var_password_pam_dcredit 'CCE-27214-6' '%s = %s'
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-var_password_pam_dcredit:var:1" value-id="var_password_pam_dcredit" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_pam_dcredit:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_pam_dcredit_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="accounts_password_pam_minlen" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Set Password Minimum Length</ns0:title>
              <ns0:description xml:lang="en-US">The pam_pwquality module's <html:code xmlns:html="http://www.w3.org/1999/xhtml">minlen</html:code> parameter controls requirements for
minimum characters required in a password. Add <html:code xmlns:html="http://www.w3.org/1999/xhtml">minlen=<ns0:sub idref="var_password_pam_minlen" /></html:code>
after pam_pwquality to set minimum password length requirements.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(a)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">205</ns0:reference>
              <ns0:reference href="">SRG-OS-000078-GPOS-00046</ns0:reference>
              <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.2.3</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.3.2</ns0:reference>
              <ns0:rationale xml:lang="en-US">
The shorter the password, the lower the number of possible combinations
that need to be tested before the password is compromised.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Password complexity, or strength, is a measure of the effectiveness of a 
password in resisting attempts at guessing and brute-force attacks. 
Password length is one factor of several that helps to determine strength
and how long it takes to crack a password. Use of more characters in a password
helps to exponentially increase the time and/or resources required to 
compromose the password.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="accounts_password_pam_minlen" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_password_pam_minlen="<ns0:sub idref="var_password_pam_minlen" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/security/pwquality.conf' '^minlen' $var_password_pam_minlen 'CCE-27293-0' '%s = %s'
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-var_password_pam_minlen:var:1" value-id="var_password_pam_minlen" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_pam_minlen:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_pam_minlen_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="accounts_password_pam_ucredit" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Set Password Strength Minimum Uppercase Characters</ns0:title>
              <ns0:description xml:lang="en-US">The pam_pwquality module's <html:code xmlns:html="http://www.w3.org/1999/xhtml">ucredit=</html:code> parameter controls requirements for
usage of uppercase letters in a password. When set to a negative number, any password will be required to
contain that many uppercase characters. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each uppercase character. Modify the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ucredit</html:code> setting in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/pwquality.conf</html:code> to require the use of an uppercase character in passwords.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(b)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(a)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">192</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000069-GPOS-00037</ns0:reference>
              <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.2.3</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.3.2</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Use of a complex password helps to increase the time and resources reuiqred to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts
at guessing and brute-force attacks.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Password complexity is one factor of several that determines how long it takes to crack a password. The more
complex the password, the greater the number of possible combinations that need to be tested before
the password is compromised.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="accounts_password_pam_ucredit" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_password_pam_ucredit="<ns0:sub idref="var_password_pam_ucredit" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/security/pwquality.conf' '^ucredit' $var_password_pam_ucredit 'CCE-27200-5' '%s = %s'
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-var_password_pam_ucredit:var:1" value-id="var_password_pam_ucredit" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_pam_ucredit:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_pam_ucredit_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="accounts_password_pam_ocredit" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Set Password Strength Minimum Special Characters</ns0:title>
              <ns0:description xml:lang="en-US">The pam_pwquality module's <html:code xmlns:html="http://www.w3.org/1999/xhtml">ocredit=</html:code> parameter controls requirements for
usage of special (or "other") characters in a password. When set to a negative number, any password will be
required to contain that many special characters. When set to a positive number, pam_pwquality will grant +1 
additional length credit for each special character. Modify the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ocredit</html:code> setting in 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/pwquality.conf</html:code> to equal <ns0:sub idref="var_password_pam_ocredit" /> to require use of a special character in passwords.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(b)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(a)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1619</ns0:reference>
              <ns0:reference href="">SRG-OS-000266-GPOS-00101</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Use of a complex password helps to increase the time and resources required
to compromise the password. Password complexity, or strength, is a measure of
the effectiveness of a password in resisting attempts at guessing and brute-force
attacks. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Password complexity is one factor of several that determines how long it takes
to crack a password. The more complex the password, the greater the number of 
possble combinations that need to be tested before the password is compromised.
Requiring a minimum number of special characters makes password guessing attacks
more difficult by ensuring a larger search space.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="accounts_password_pam_ocredit" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_password_pam_ocredit="<ns0:sub idref="var_password_pam_ocredit" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/security/pwquality.conf' '^ocredit' $var_password_pam_ocredit 'CCE-27360-7' '%s = %s'
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-var_password_pam_ocredit:var:1" value-id="var_password_pam_ocredit" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_pam_ocredit:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_pam_ocredit_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="accounts_password_pam_lcredit" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Set Password Strength Minimum Lowercase Characters</ns0:title>
              <ns0:description xml:lang="en-US">The pam_pwquality module's <html:code xmlns:html="http://www.w3.org/1999/xhtml">lcredit</html:code> parameter controls requirements for
usage of lowercase letters in a password. When set to a negative number, any password will be required to
contain that many lowercase characters. When set to a positive number, pam_pwquality will grant +1 additional
length credit for each lowercase character. Modify the <html:code xmlns:html="http://www.w3.org/1999/xhtml">lcredit</html:code> setting in 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/pwquality.conf</html:code> to require the use of a lowercase character in passwords.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(b)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(a)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">193</ns0:reference>
              <ns0:reference href="">SRG-OS-000070-GPOS-00038</ns0:reference>
              <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.2.3</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Use of a complex password helps to increase the time and resources required
to compromise the password. Password complexity, or strength, is a measure of
the effectiveness of a password in resisting attempts at guessing and brute-force
attacks. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Password complexity is one factor of several that determines how long it takes
to crack a password. The more complex the password, the greater the number of 
possble combinations that need to be tested before the password is compromised.
Requiring a minimum number of lowercase characters makes password guessing attacks
more difficult by ensuring a larger search space.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="accounts_password_pam_lcredit" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_password_pam_lcredit="<ns0:sub idref="var_password_pam_lcredit" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/security/pwquality.conf' '^lcredit' $var_password_pam_lcredit 'CCE-27345-8' '%s = %s'
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-var_password_pam_lcredit:var:1" value-id="var_password_pam_lcredit" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_pam_lcredit:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_pam_lcredit_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="accounts_password_pam_difok" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Set Password Strength Minimum Different Characters</ns0:title>
              <ns0:description xml:lang="en-US">The pam_pwquality module's <html:code xmlns:html="http://www.w3.org/1999/xhtml">difok</html:code> parameter sets the number of characters
in a password that must not be present in and old password during a password change. 

Modify the <html:code xmlns:html="http://www.w3.org/1999/xhtml">difok</html:code> setting in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/pwquality.conf</html:code>
to equal <ns0:sub idref="var_password_pam_difok" /> to require differing characters 
when changing passwords.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(b)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(b)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">195</ns0:reference>
              <ns0:reference href="">SRG-OS-000072-GPOS-00040</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Use of a complex password helps to increase the time and resources 
required to compromise the password. Password complexity, or strength, 
is a measure of the effectiveness of a password in resisting attempts 
at guessing and brute&#8211;force attacks.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Password complexity is one factor of several that determines how long 
it takes to crack a password. The more complex the password, the 
greater the number of possible combinations that need to be tested 
before the password is compromised.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Requiring a minimum number of different characters during password changes ensures that
newly changed passwords should not resemble previously compromised ones.
Note that passwords which are changed on compromised systems will still be compromised, however.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="accounts_password_pam_difok" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_password_pam_difok="<ns0:sub idref="var_password_pam_difok" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/security/pwquality.conf' '^difok' $var_password_pam_difok 'CCE-26631-2' '%s = %s'
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-var_password_pam_difok:var:1" value-id="var_password_pam_difok" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_pam_difok:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_pam_difok_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="accounts_password_pam_minclass" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Set Password Strength Minimum Different Categories</ns0:title>
              <ns0:description xml:lang="en-US">The pam_pwquality module's <html:code xmlns:html="http://www.w3.org/1999/xhtml">minclass</html:code> parameter controls
requirements for usage of different character classes, or types, of character
that must exist in a password before it is considered valid. For example,
setting this value to three (3) requires that any password must have characters
from at least three different categories in order to be approved. The default
value is zero (0), meaning there are no required classes. There are four
categories available:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">
* Upper-case characters
* Lower-case characters
* Digits
* Special characters (for example, punctuation)
</html:pre>
Modify the <html:code xmlns:html="http://www.w3.org/1999/xhtml">minclass</html:code> setting in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/pwquality.conf</html:code> entry to require <ns0:sub idref="var_password_pam_minclass" /> 
differing categories of characters when changing passwords. 
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">195</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000072-GPOS-00040</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Use of a complex password helps to increase the time and resources required to compromise the password.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts 
at guessing and brute-force attacks.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Password complexity is one factor of several that determines how long it takes to crack a password. The
more complex the password, the greater the number of possible combinations that need to be tested before
the password is compromised.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Requiring a minimum number of character categories makes password guessing attacks more difficult 
by ensuring a larger search space.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="accounts_password_pam_minclass" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_password_pam_minclass="<ns0:sub idref="var_password_pam_minclass" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/security/pwquality.conf' '^minclass' $var_password_pam_minclass 'CCE-27115-5' '%s = %s'
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-var_password_pam_minclass:var:1" value-id="var_password_pam_minclass" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_pam_minclass:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_pam_minclass_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
          </ns0:Group>
        </ns0:Group>
        <ns0:Group id="locking_out_password_attempts">
          <ns0:title xml:lang="en-US">Set Lockouts for Failed Password Attempts</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_faillock</html:code> PAM module provides the capability to
lock out user accounts after a number of failed login attempts. Its
documentation is available in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/usr/share/doc/pam-VERSION/txts/README.pam_faillock</html:code>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">Locking out user accounts presents the
risk of a denial-of-service attack. The lockout policy
must weigh whether the risk of such a
denial-of-service attack outweighs the benefits of thwarting
password guessing attacks.</ns0:warning>
          <ns0:Rule id="accounts_passwords_pam_faillock_deny" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set Deny For Failed Password Attempts</ns0:title>
            <ns0:description xml:lang="en-US">
To configure the system to lock out accounts after a number of incorrect login
attempts using <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_faillock.so</html:code>, modify the content of both
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/system-auth</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/password-auth</html:code> as follows:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li> add the following line immediately <html:code>before</html:code> the <html:code>pam_unix.so</html:code> statement in the <html:code>AUTH</html:code> section:
<html:pre>auth required pam_faillock.so preauth silent deny=<ns0:sub idref="var_accounts_passwords_pam_faillock_deny" /> unlock_time=<ns0:sub idref="var_accounts_passwords_pam_faillock_unlock_time" /> fail_interval=<ns0:sub idref="var_accounts_passwords_pam_faillock_fail_interval" /></html:pre></html:li><html:li> add the following line immediately <html:code>after</html:code> the <html:code>pam_unix.so</html:code> statement in the <html:code>AUTH</html:code> section:
<html:pre>auth [default=die] pam_faillock.so authfail deny=<ns0:sub idref="var_accounts_passwords_pam_faillock_deny" /> unlock_time=<ns0:sub idref="var_accounts_passwords_pam_faillock_unlock_time" /> fail_interval=<ns0:sub idref="var_accounts_passwords_pam_faillock_fail_interval" /></html:pre></html:li><html:li> add the following line immediately <html:code>before</html:code> the <html:code>pam_unix.so</html:code> statement in the <html:code>ACCOUNT</html:code> section:
<html:pre>account required pam_faillock.so</html:pre></html:li></html:ul>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-7(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2238</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000329-GPOS-00128</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000021-GPOS-00005</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.1.6</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.3.3</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Locking out user accounts after a number of incorrect attempts
prevents direct password guessing attacks.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_passwords_pam_faillock_deny" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_accounts_passwords_pam_faillock_deny="<ns0:sub idref="var_accounts_passwords_pam_faillock_deny" />"

AUTH_FILES[0]="/etc/pam.d/system-auth"
AUTH_FILES[1]="/etc/pam.d/password-auth"

for pamFile in "${AUTH_FILES[@]}"
do
	
	# pam_faillock.so already present?
	if grep -q "^auth.*pam_faillock.so.*" $pamFile; then

		# pam_faillock.so present, deny directive present?
		if grep -q "^auth.*[default=die].*pam_faillock.so.*authfail.*deny=" $pamFile; then

			# both pam_faillock.so &amp; deny present, just correct deny directive value
			sed -i --follow-symlinks "s/\(^auth.*required.*pam_faillock.so.*preauth.*silent.*\)\(deny *= *\).*/\1\2$var_accounts_passwords_pam_faillock_deny/" $pamFile
			sed -i --follow-symlinks "s/\(^auth.*[default=die].*pam_faillock.so.*authfail.*\)\(deny *= *\).*/\1\2$var_accounts_passwords_pam_faillock_deny/" $pamFile

		# pam_faillock.so present, but deny directive not yet
		else

			# append correct deny value to appropriate places
			sed -i --follow-symlinks "/^auth.*required.*pam_faillock.so.*preauth.*silent.*/ s/$/ deny=$var_accounts_passwords_pam_faillock_deny/" $pamFile
			sed -i --follow-symlinks "/^auth.*[default=die].*pam_faillock.so.*authfail.*/ s/$/ deny=$var_accounts_passwords_pam_faillock_deny/" $pamFile
		fi

	# pam_faillock.so not present yet
	else

		# insert pam_faillock.so preauth &amp; authfail rows with proper value of the 'deny' option
		sed -i --follow-symlinks "/^auth.*sufficient.*pam_unix.so.*/i auth        required      pam_faillock.so preauth silent deny=$var_accounts_passwords_pam_faillock_deny" $pamFile
		sed -i --follow-symlinks "/^auth.*sufficient.*pam_unix.so.*/a auth        [default=die] pam_faillock.so authfail deny=$var_accounts_passwords_pam_faillock_deny" $pamFile
		sed -i --follow-symlinks "/^account.*required.*pam_unix.so/i account     required      pam_faillock.so" $pamFile
	fi
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_accounts_passwords_pam_faillock_deny:var:1" value-id="var_accounts_passwords_pam_faillock_deny" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_passwords_pam_faillock_deny:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_passwords_pam_faillock_deny_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_passwords_pam_faillock_unlock_time" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set Lockout Time For Failed Password Attempts</ns0:title>
            <ns0:description xml:lang="en-US">
To configure the system to lock out accounts after a number of incorrect login
attempts and require an administrator to unlock the account using <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_faillock.so</html:code>,
modify the content of both <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/system-auth</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/password-auth</html:code> as follows:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li> add the following line immediately <html:code>before</html:code> the <html:code>pam_unix.so</html:code> statement in the <html:code>AUTH</html:code> section:
<html:pre>auth required pam_faillock.so preauth silent deny=<ns0:sub idref="var_accounts_passwords_pam_faillock_deny" /> unlock_time=<ns0:sub idref="var_accounts_passwords_pam_faillock_unlock_time" /> fail_interval=<ns0:sub idref="var_accounts_passwords_pam_faillock_fail_interval" /></html:pre></html:li><html:li> add the following line immediately <html:code>after</html:code> the <html:code>pam_unix.so</html:code> statement in the <html:code>AUTH</html:code> section:
<html:pre>auth [default=die] pam_faillock.so authfail deny=<ns0:sub idref="var_accounts_passwords_pam_faillock_deny" /> unlock_time=<ns0:sub idref="var_accounts_passwords_pam_faillock_unlock_time" /> fail_interval=<ns0:sub idref="var_accounts_passwords_pam_faillock_fail_interval" /></html:pre></html:li><html:li> add the following line immediately <html:code>before</html:code> the <html:code>pam_unix.so</html:code> statement in the <html:code>ACCOUNT</html:code> section:
<html:pre>account required pam_faillock.so</html:pre></html:li></html:ul>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-7(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">002238</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000329-GPOS-00128</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000021-GPOS-00005</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.1.7</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.3.3</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Locking out user accounts after a number of incorrect attempts
prevents direct password guessing attacks.  Ensuring that an administrator is
involved in unlocking locked accounts draws appropriate attention to such
situations.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_passwords_pam_faillock_unlock_time" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_accounts_passwords_pam_faillock_unlock_time="<ns0:sub idref="var_accounts_passwords_pam_faillock_unlock_time" />"

AUTH_FILES[0]="/etc/pam.d/system-auth"
AUTH_FILES[1]="/etc/pam.d/password-auth"

for pamFile in "${AUTH_FILES[@]}"
do
	
	# pam_faillock.so already present?
	if grep -q "^auth.*pam_faillock.so.*" $pamFile; then

		# pam_faillock.so present, unlock_time directive present?
		if grep -q "^auth.*[default=die].*pam_faillock.so.*authfail.*unlock_time=" $pamFile; then

			# both pam_faillock.so &amp; unlock_time present, just correct unlock_time directive value
			sed -i --follow-symlinks "s/\(^auth.*required.*pam_faillock.so.*preauth.*silent.*\)\(unlock_time *= *\).*/\1\2$var_accounts_passwords_pam_faillock_unlock_time/" $pamFile
			sed -i --follow-symlinks "s/\(^auth.*[default=die].*pam_faillock.so.*authfail.*\)\(unlock_time *= *\).*/\1\2$var_accounts_passwords_pam_faillock_unlock_time/" $pamFile

		# pam_faillock.so present, but unlock_time directive not yet
		else

			# append correct unlock_time value to appropriate places
			sed -i --follow-symlinks "/^auth.*required.*pam_faillock.so.*preauth.*silent.*/ s/$/ unlock_time=$var_accounts_passwords_pam_faillock_unlock_time/" $pamFile
			sed -i --follow-symlinks "/^auth.*[default=die].*pam_faillock.so.*authfail.*/ s/$/ unlock_time=$var_accounts_passwords_pam_faillock_unlock_time/" $pamFile
		fi

	# pam_faillock.so not present yet
	else

		# insert pam_faillock.so preauth &amp; authfail rows with proper value of the 'unlock_time' option
		sed -i --follow-symlinks "/^auth.*sufficient.*pam_unix.so.*/i auth        required      pam_faillock.so preauth silent unlock_time=$var_accounts_passwords_pam_faillock_unlock_time" $pamFile
		sed -i --follow-symlinks "/^auth.*sufficient.*pam_unix.so.*/a auth        [default=die] pam_faillock.so authfail unlock_time=$var_accounts_passwords_pam_faillock_unlock_time" $pamFile
		sed -i --follow-symlinks "/^account.*required.*pam_unix.so/i account     required      pam_faillock.so" $pamFile
	fi
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_accounts_passwords_pam_faillock_unlock_time:var:1" value-id="var_accounts_passwords_pam_faillock_unlock_time" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_passwords_pam_faillock_unlock_time:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_passwords_pam_faillock_unlock_time_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_passwords_pam_faillock_deny_root" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure the root Account for Failed Password Attempts</ns0:title>
            <ns0:description xml:lang="en-US">
To configure the system to lock out the <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code> account after a number of incorrect login
attempts using <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_faillock.so</html:code>, modify the content of both
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/system-auth</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/password-auth</html:code> as follows:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>Modify the following line in the <html:code>AUTH</html:code> section to add <html:code>even_deny_root</html:code>:
<html:pre>auth required pam_faillock.so preauth silent <html:b>even_deny_root</html:b> deny=<ns0:sub idref="var_accounts_passwords_pam_faillock_deny" /> unlock_time=<ns0:sub idref="var_accounts_passwords_pam_faillock_unlock_time" /> fail_interval=<ns0:sub idref="var_accounts_passwords_pam_faillock_fail_interval" /></html:pre></html:li><html:li>Modify the following line in the <html:code>AUTH</html:code> section to add <html:code>even_deny_root</html:code>:
<html:pre>auth [default=die] pam_faillock.so authfail <html:b>even_deny_root</html:b> deny=<ns0:sub idref="var_accounts_passwords_pam_faillock_deny" /> unlock_time=<ns0:sub idref="var_accounts_passwords_pam_faillock_unlock_time" /> fail_interval=<ns0:sub idref="var_accounts_passwords_pam_faillock_fail_interval" /></html:pre></html:li></html:ul>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-7(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2238</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000329-GPOS-00128</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000021-GPOS-00005</ns0:reference>
            <ns0:rationale xml:lang="en-US">
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password
guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_passwords_pam_faillock_deny_root" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
if [ $( grep -c "auth.*required.*pam_faillock.so.*even_deny_root" /etc/pam.d/system-auth ) -eq 0 ]; then
        BEGINNING_TXT=$( cat /etc/pam.d/system-auth | grep "auth.*required.*pam_faillock.so" | sed -e 's/[]\/$*.^|[]/\\&amp;/g' )
	sed -i --follow-symlinks "s/$BEGINNING_TXT/$BEGINNING_TXT even_deny_root/" /etc/pam.d/system-auth
fi

if [ $( grep -c "auth.*default.*die.*pam_faillock.so.*even_deny_root" /etc/pam.d/system-auth ) -eq 0 ]; then
        BEGINNING_TXT=$( cat /etc/pam.d/system-auth | grep "auth.*default.*die.*pam_faillock.so"  | sed -e 's/[]\/$*.^|[]/\\&amp;/g' )
	sed -i --follow-symlinks "s/$BEGINNING_TXT/$BEGINNING_TXT even_deny_root/" /etc/pam.d/system-auth
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_passwords_pam_faillock_deny_root:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_passwords_pam_faillock_deny_root_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_passwords_pam_faillock_interval" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set Interval For Counting Failed Password Attempts</ns0:title>
            <ns0:description xml:lang="en-US">
Utilizing <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_faillock.so</html:code>, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">fail_interval</html:code> directive 
configures the system to lock out an accounts after a number of incorrect login
attempts within a specified time period.. Modify the content of both 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/system-auth</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/password-auth</html:code> as follows:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>Add the following line immediately <html:code>before</html:code> the <html:code>pam_unix.so</html:code> statement in the <html:code>AUTH</html:code> section:
<html:pre>auth required pam_faillock.so preauth silent deny=<ns0:sub idref="var_accounts_passwords_pam_faillock_deny" /> unlock_time=<ns0:sub idref="var_accounts_passwords_pam_faillock_unlock_time" /> fail_interval=<ns0:sub idref="var_accounts_passwords_pam_faillock_fail_interval" /></html:pre></html:li><html:li>Add the following line immediately <html:code>after</html:code> the <html:code>pam_unix.so</html:code> statement in the <html:code>AUTH</html:code> section:
<html:pre>auth [default=die] pam_faillock.so authfail deny=<ns0:sub idref="var_accounts_passwords_pam_faillock_deny" /> unlock_time=<ns0:sub idref="var_accounts_passwords_pam_faillock_unlock_time" /> fail_interval=<ns0:sub idref="var_accounts_passwords_pam_faillock_fail_interval" /></html:pre></html:li><html:li>Add the following line immediately <html:code>before</html:code> the <html:code>pam_unix.so</html:code> statement in the <html:code>ACCOUNT</html:code> section:
<html:pre>account required pam_faillock.so</html:pre></html:li></html:ul>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-7(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2238</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000329-GPOS-00128</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000021-GPOS-00005</ns0:reference>
            <ns0:rationale xml:lang="en-US">
By limiting the number of failed logon attempts the risk of unauthorized system
access via user password guessing, otherwise known as brute-forcing, is reduced.
Limits are imposed by locking the account.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_passwords_pam_faillock_interval" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_accounts_passwords_pam_faillock_fail_interval="<ns0:sub idref="var_accounts_passwords_pam_faillock_fail_interval" />"

AUTH_FILES[0]="/etc/pam.d/system-auth"
AUTH_FILES[1]="/etc/pam.d/password-auth"

for pamFile in "${AUTH_FILES[@]}"
do
	
	# pam_faillock.so already present?
	if grep -q "^auth.*pam_faillock.so.*" $pamFile; then

		# pam_faillock.so present, 'fail_interval' directive present?
		if grep -q "^auth.*[default=die].*pam_faillock.so.*authfail.*fail_interval=" $pamFile; then

			# both pam_faillock.so &amp; 'fail_interval' present, just correct 'fail_interval' directive value
			sed -i --follow-symlinks "s/\(^auth.*required.*pam_faillock.so.*preauth.*silent.*\)\(fail_interval *= *\).*/\1\2$var_accounts_passwords_pam_faillock_fail_interval/" $pamFile
			sed -i --follow-symlinks "s/\(^auth.*[default=die].*pam_faillock.so.*authfail.*\)\(fail_interval *= *\).*/\1\2$var_accounts_passwords_pam_faillock_fail_interval/" $pamFile

		# pam_faillock.so present, but 'fail_interval' directive not yet
		else

			# append correct 'fail_interval' value to appropriate places
			sed -i --follow-symlinks "/^auth.*required.*pam_faillock.so.*preauth.*silent.*/ s/$/ fail_interval=$var_accounts_passwords_pam_faillock_fail_interval/" $pamFile
			sed -i --follow-symlinks "/^auth.*[default=die].*pam_faillock.so.*authfail.*/ s/$/ fail_interval=$var_accounts_passwords_pam_faillock_fail_interval/" $pamFile
		fi

	# pam_faillock.so not present yet
	else

		# insert pam_faillock.so preauth &amp; authfail rows with proper value of the 'fail_interval' option
		sed -i --follow-symlinks "/^auth.*sufficient.*pam_unix.so.*/i auth        required      pam_faillock.so preauth silent fail_interval=$var_accounts_passwords_pam_faillock_fail_interval" $pamFile
		sed -i --follow-symlinks "/^auth.*sufficient.*pam_unix.so.*/a auth        [default=die] pam_faillock.so authfail fail_interval=$var_accounts_passwords_pam_faillock_fail_interval" $pamFile
		sed -i --follow-symlinks "/^account.*required.*pam_unix.so/i account     required      pam_faillock.so" $pamFile
	fi
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_accounts_passwords_pam_faillock_fail_interval:var:1" value-id="var_accounts_passwords_pam_faillock_fail_interval" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_passwords_pam_faillock_interval:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_passwords_pam_faillock_interval_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_password_pam_unix_remember" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Limit Password Reuse</ns0:title>
            <ns0:description xml:lang="en-US">Do not allow users to reuse recent passwords. This can be
accomplished by using the <html:code xmlns:html="http://www.w3.org/1999/xhtml">remember</html:code> option for the <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_unix</html:code>
or <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_pwhistory</html:code> PAM modules. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
In the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/system-auth</html:code>, append <html:code xmlns:html="http://www.w3.org/1999/xhtml">remember=<ns0:sub idref="var_password_pam_unix_remember" /></html:code>
to the line which refers to the <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_unix.so</html:code> or <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_pwhistory.so</html:code>module, as shown below:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>for the <html:code>pam_unix.so</html:code> case:
<html:pre>password sufficient pam_unix.so <html:i>...existing_options...</html:i> remember=<ns0:sub idref="var_password_pam_unix_remember" /></html:pre>
</html:li><html:li>for the <html:code>pam_pwhistory.so</html:code> case:
<html:pre>password requisite pam_pwhistory.so <html:i>...existing_options...</html:i> remember=<ns0:sub idref="var_password_pam_unix_remember" /></html:pre>
</html:li></html:ul>
The DoD STIG requirement is 5 passwords.</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(f)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(e)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">200</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000077-GPOS-00045</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.2.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.3.4</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Preventing re-use of previous passwords helps ensure that a compromised password is not re-used by a user.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_password_pam_unix_remember" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_password_pam_unix_remember="<ns0:sub idref="var_password_pam_unix_remember" />"

if grep -q "remember=" /etc/pam.d/system-auth; then   
	sed -i --follow-symlinks "s/\(^password.*sufficient.*pam_unix.so.*\)\(\(remember *= *\)[^ $]*\)/\1remember=$var_password_pam_unix_remember/" /etc/pam.d/system-auth
else
	sed -i --follow-symlinks "/^password[[:space:]]\+sufficient[[:space:]]\+pam_unix.so/ s/$/ remember=$var_password_pam_unix_remember/" /etc/pam.d/system-auth
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_password_pam_unix_remember:var:1" value-id="var_password_pam_unix_remember" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_password_pam_unix_remember:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_password_pam_unix_remember_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="set_password_hashing_algorithm">
          <ns0:title xml:lang="en-US">Set Password Hashing Algorithm</ns0:title>
          <ns0:description xml:lang="en-US">The system's default algorithm for storing password hashes in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/shadow</html:code> is SHA-512. This can be configured in several
locations.</ns0:description>
          <ns0:Rule id="set_password_hashing_algorithm_systemauth" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set PAM's Password Hashing Algorithm</ns0:title>
            <ns0:description xml:lang="en-US">
The PAM system service can be configured to only store encrypted representations of passwords.
In <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pam.d/system-auth</html:code>, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">password</html:code> section of the file controls 
which PAM modules execute during a password change. Set the <html:code xmlns:html="http://www.w3.org/1999/xhtml">pam_unix.so</html:code> 
module in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">password</html:code> section to include the argument <html:code xmlns:html="http://www.w3.org/1999/xhtml">sha512</html:code>, as shown below:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">password    sufficient    pam_unix.so sha512 <html:i>other arguments...</html:i></html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
This will help ensure when local users change their passwords, hashes for the new
passwords will be generated using the SHA-512 algorithm. This is the default.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">196</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000073-GPOS-00041</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.2.1</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.3.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Passwords need to be protected at all times, and encryption is the standard method for protecting
passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily
compromised. Passwords that are encrypted with a weak algorithm are no more protected than if they 
are kepy in plain text.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
This setting ensures user and group account administration utilities are configured to store only
encrypted representations of passwords. Additionally, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">crypt_style</html:code> configuration option
ensures the use of a strong hashing algorithm that makes password cracking attacks more difficult. 
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="set_password_hashing_algorithm_systemauth" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">if ! grep -q "^password.*sufficient.*pam_unix.so.*sha512" /etc/pam.d/system-auth; then   
	sed -i --follow-symlinks "/^password.*sufficient.*pam_unix.so/ s/$/ sha512/" /etc/pam.d/system-auth
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-set_password_hashing_algorithm_systemauth:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-set_password_hashing_algorithm_systemauth_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="set_password_hashing_algorithm_logindefs" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set Password Hashing Algorithm in /etc/login.defs</ns0:title>
            <ns0:description xml:lang="en-US">
In <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code>, add or correct the following line to ensure
the system will use SHA-512 as the hashing algorithm:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ENCRYPT_METHOD SHA512</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">196</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000073-GPOS-00041</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.2.1</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.3.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords.
If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Passwords
that are encrypted with a weak algorithm are no more protected than if they are kept in plain text.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Using a stronger hashing algorithm makes password cracking attacks more difficult.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="set_password_hashing_algorithm_logindefs" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">if grep --silent ^ENCRYPT_METHOD /etc/login.defs ; then
	sed -i 's/^ENCRYPT_METHOD.*/ENCRYPT_METHOD SHA512/g' /etc/login.defs
else
	echo "" &gt;&gt; /etc/login.defs
	echo "ENCRYPT_METHOD SHA512" &gt;&gt; /etc/login.defs
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-set_password_hashing_algorithm_logindefs:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-set_password_hashing_algorithm_logindefs_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="set_password_hashing_algorithm_libuserconf" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set Password Hashing Algorithm in /etc/libuser.conf</ns0:title>
            <ns0:description xml:lang="en-US">
In <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/libuser.conf</html:code>, add or correct the following line in its
<html:code xmlns:html="http://www.w3.org/1999/xhtml">[defaults]</html:code> section to ensure the system will use the SHA-512
algorithm for password hashing:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">crypt_style = sha512</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">196</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000073-GPOS-00041</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.2.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Passwords need to be protected at all times, and encryption is the standard method for protecting
passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily
compromised. Passwords that are encrypted with a weak algorithm are no more protected than if they 
are kepy in plain text.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
This setting ensures user and group account administration utilities are configured to store only
encrypted representations of passwords. Additionally, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">crypt_style</html:code> configuration option
ensures the use of a strong hashing algorithm that makes password cracking attacks more difficult. 
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-set_password_hashing_algorithm_libuserconf:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-set_password_hashing_algorithm_libuserconf_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="accounts-session">
        <ns0:title xml:lang="en-US">Secure Session Configuration Files for Login Accounts</ns0:title>
        <ns0:description xml:lang="en-US">When a user logs into a Unix account, the system
configures the user's session by reading a number of files. Many of
these files are located in the user's home directory, and may have
weak permissions as a result of user error or misconfiguration. If
an attacker can modify or even read certain types of account
configuration information, they can often gain full access to the
affected user's account. Therefore, it is important to test and
correct configuration file permissions for interactive accounts,
particularly those of privileged users such as root or system
administrators.</ns0:description>
        <ns0:Value id="var_accounts_max_concurrent_login_sessions" operator="equals" type="number">
          <ns0:title xml:lang="en-US">Maximum concurrent login sessions</ns0:title>
          <ns0:description xml:lang="en-US">Maximum number of concurrent sessions by a user</ns0:description>
          <ns0:value>1</ns0:value>
          <ns0:value selector="1">1</ns0:value>
          <ns0:value selector="3">3</ns0:value>
          <ns0:value selector="5">5</ns0:value>
          <ns0:value selector="10">10</ns0:value>
          <ns0:value selector="15">15</ns0:value>
          <ns0:value selector="20">20</ns0:value>
        </ns0:Value>
        <ns0:Value id="var_accounts_fail_delay" operator="equals" type="number">
          <ns0:title xml:lang="en-US">Maximum login attempts delay</ns0:title>
          <ns0:description xml:lang="en-US">Maximum time in seconds between fail login attempts before re-prompting.</ns0:description>
          <ns0:value>4</ns0:value>
          <ns0:value selector="1">1</ns0:value>
          <ns0:value selector="2">2</ns0:value>
          <ns0:value selector="3">3</ns0:value>
          <ns0:value selector="4">4</ns0:value>
          <ns0:value selector="5">5</ns0:value>
        </ns0:Value>
        <ns0:Value id="var_accounts_tmout" operator="equals" type="number">
          <ns0:title xml:lang="en-US">Account Inactivity Timeout (minutes)</ns0:title>
          <ns0:description xml:lang="en-US">In an interactive shell, the value is interpreted as the
number of seconds to wait for input after issueing the primary prompt.
Bash terminates after waiting for that number of seconds if input does
not arrive.</ns0:description>
          <ns0:value>600</ns0:value>
          <ns0:value selector="5_min">300</ns0:value>
          <ns0:value selector="10_min">600</ns0:value>
          <ns0:value selector="15_min">900</ns0:value>
        </ns0:Value>
        <ns0:Rule id="accounts_tmout" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Set Interactive Session Timeout</ns0:title>
          <ns0:description xml:lang="en-US">
Setting the <html:code xmlns:html="http://www.w3.org/1999/xhtml">TMOUT</html:code> option in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/profile</html:code> ensures that
RHEL7 will terminate all user sessions based on inactivity.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-12</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-10</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1133</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">0361</ns0:reference>
          <ns0:reference href="">SRG-OS-000163-GPOS-00072</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Terminating an idle session within a short time period reduces
the window of opportunity for unauthorized personnel to take control of a
management session enabled on the console or console port that has been
left unattended.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="accounts_tmout" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_accounts_tmout="<ns0:sub idref="var_accounts_tmout" />"

if grep --silent ^TMOUT /etc/profile ; then
        sed -i "s/^TMOUT.*/TMOUT = $var_accounts_tmout/g" /etc/profile
else
        echo -e "\n# Set TMOUT to $var_accounts_tmout per security requirements" &gt;&gt; /etc/profile
        echo "TMOUT = $var_accounts_tmout" &gt;&gt; /etc/profile
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_accounts_tmout:var:1" value-id="var_accounts_tmout" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_tmout:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_tmout_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="accounts_max_concurrent_login_sessions" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Limit the Number of Concurrent Login Sessions Allowed Per User</ns0:title>
          <ns0:description xml:lang="en-US">
Limiting the number of allowed users and sessions per user can limit risks related to Denial of
Service attacks. This addresses concurrent sessions for a single account and does not address
concurrent sessions by a single user via multiple accounts. To set the number of concurrent
sessions per user add the following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/security/limits.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">* hard maxlogins <ns0:sub idref="var_accounts_max_concurrent_login_sessions" /></html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-10</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">54</ns0:reference>
          <ns0:reference href="">SRG-OS-000027-GPOS-00008</ns0:reference>
          <ns0:rationale xml:lang="en-US">Limiting simultaneous user logins can insulate the system from denial of service
problems caused by excessive logins. Automated login processes operating improperly or
maliciously may result in an exceptional number of simultaneous login sessions.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="accounts_max_concurrent_login_sessions" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_accounts_max_concurrent_login_sessions="<ns0:sub idref="var_accounts_max_concurrent_login_sessions" />"

if grep -q '^[^#]*\&lt;maxlogins\&gt;' /etc/security/limits.d/*.conf; then
	sed -i "/^[^#]*\&lt;maxlogins\&gt;/ s/maxlogins.*/maxlogins $var_accounts_max_concurrent_login_sessions/" /etc/security/limits.d/*.conf
elif grep -q '^[^#]*\&lt;maxlogins\&gt;' /etc/security/limits.conf; then
	sed -i "/^[^#]*\&lt;maxlogins\&gt;/ s/maxlogins.*/maxlogins $var_accounts_max_concurrent_login_sessions/" /etc/security/limits.conf
else
	echo "*	hard	maxlogins	$var_accounts_max_concurrent_login_sessions" &gt;&gt; /etc/security/limits.conf
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_accounts_max_concurrent_login_sessions:var:1" value-id="var_accounts_max_concurrent_login_sessions" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_max_concurrent_login_sessions:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_max_concurrent_login_sessions_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="accounts_logon_fail_delay" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure the Logon Failure Delay is Set Correctly in login.defs</ns0:title>
          <ns0:description xml:lang="en-US">
To ensure the logon failure delay controlled by <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code> is set properly,
add or correct the <html:code xmlns:html="http://www.w3.org/1999/xhtml">FAIL_DELAY</html:code> setting in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code> to read as follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">FAIL_DELAY <ns0:sub idref="var_accounts_fail_delay" /></html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00226</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Increasing the time between a failed authentication attempt and re-prompting to
enter credentials helps to slow a single-threaded brute force attack.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_accounts_fail_delay:var:1" value-id="var_accounts_fail_delay" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_logon_fail_delay:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_logon_fail_delay_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="root_paths">
          <ns0:title xml:lang="en-US">Ensure that No Dangerous Directories Exist in Root's Path</ns0:title>
          <ns0:description xml:lang="en-US">The active path of the root account can be obtained by
starting a new root shell and running:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"># echo $PATH</html:pre>
This will produce a colon-separated list of
directories in the path.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Certain path elements could be considered dangerous, as they could lead
to root executing unknown or
untrusted programs, which could contain malicious
code.
Since root may sometimes work inside
untrusted directories, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">.</html:code> character, which represents the
current directory, should never be in the root path, nor should any
directory which can be written to by an unprivileged or
semi-privileged (system) user.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
It is a good practice for administrators to always execute
privileged commands by typing the full path to the
command.</ns0:description>
          <ns0:Rule id="root_path_no_dot" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Ensure that Root's Path Does Not Include Relative Paths or Null Directories</ns0:title>
            <ns0:description xml:lang="en-US">
Ensure that none of the directories in root's path is equal to a single
<html:code xmlns:html="http://www.w3.org/1999/xhtml">.</html:code> character, or
that it contains any instances that lead to relative path traversal, such as
<html:code xmlns:html="http://www.w3.org/1999/xhtml">..</html:code> or beginning a path without the slash (<html:code xmlns:html="http://www.w3.org/1999/xhtml">/</html:code>) character.
Also ensure that there are no "empty" elements in the path, such as in these examples:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">PATH=:/bin
PATH=/bin:
PATH=/bin::/sbin</html:pre>
These empty elements have the same effect as a single <html:code xmlns:html="http://www.w3.org/1999/xhtml">.</html:code> character.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Including these entries increases the risk that root could
execute code from an untrusted location.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-root_path_no_dot:def:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_root_path_dirs_no_write" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Ensure that Root's Path Does Not Include World or Group-Writable Directories</ns0:title>
            <ns0:description xml:lang="en-US">
For each element in root's path, run:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"># ls -ld <html:i>DIR</html:i></html:pre>
and ensure that write permissions are disabled for group and
other.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Such entries increase the risk that root could
execute code provided by unprivileged users,
and potentially malicious code.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_root_path_dirs_no_write:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_root_path_dirs_no_write_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Rule id="file_permissions_home_dirs" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure that User Home Directories are not Group-Writable or World-Readable</ns0:title>
          <ns0:description xml:lang="en-US">For each human user of the system, view the
permissions of the user's home directory:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"># ls -ld /home/<html:i>USER</html:i></html:pre>
Ensure that the directory is not group-writable and that it
is not world-readable. If necessary, repair the permissions:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"># chmod g-w /home/<html:i>USER</html:i>
# chmod o-rwx /home/<html:i>USER</html:i></html:pre>
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">This action may involve
modifying user home directories. Notify your user community, and
solicit input if appropriate, before making this type of
change.</ns0:warning>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6(7)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">225</ns0:reference>
          <ns0:rationale xml:lang="en-US">
User home directories contain many configuration files which
affect the behavior of a user's account. No user should ever have
write permission to another user's home directory. Group shared
directories can be configured in sub-directories or elsewhere in the
filesystem if they are needed. Typically, user home directories
should not be world-readable, as it would disclose file names
to other users. If a subset of users need read access
to one another's home directories, this can be provided using
groups or ACLs.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_home_dirs:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_home_dirs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="user_umask">
          <ns0:title xml:lang="en-US">Ensure that Users Have Sensible Umask Values</ns0:title>
          <ns0:description xml:lang="en-US">
The umask setting controls the default permissions
for the creation of new files.
With a default <html:code xmlns:html="http://www.w3.org/1999/xhtml">umask</html:code> setting of 077, files and directories
created by users will not be readable by any other user on the
system. Users who wish to make specific files group- or
world-readable can accomplish this by using the chmod command.
Additionally, users can make all their files readable to their
group by default by setting a <html:code xmlns:html="http://www.w3.org/1999/xhtml">umask</html:code> of 027 in their shell
configuration files. If default per-user groups exist (that is, if
every user has a default group whose name is the same as that
user's username and whose only member is the user), then it may
even be safe for users to select a <html:code xmlns:html="http://www.w3.org/1999/xhtml">umask</html:code> of 007, making it very
easy to intentionally share files with groups of which the user is
a member.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />

</ns0:description>
          <ns0:Value id="var_accounts_user_umask" operator="equals" type="string">
            <ns0:title xml:lang="en-US">Sensible umask</ns0:title>
            <ns0:description xml:lang="en-US">Enter default user umask</ns0:description>
            <ns0:value>027</ns0:value>
            <ns0:value selector="007">007</ns0:value>
            <ns0:value selector="022">022</ns0:value>
            <ns0:value selector="027">027</ns0:value>
            <ns0:value selector="077">077</ns0:value>
          </ns0:Value>
          <ns0:Rule id="accounts_umask_etc_bashrc" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Ensure the Default Bash Umask is Set Correctly</ns0:title>
            <ns0:description xml:lang="en-US">
To ensure the default umask for users of the Bash shell is set properly,
add or correct the <html:code xmlns:html="http://www.w3.org/1999/xhtml">umask</html:code> setting in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/bashrc</html:code> to read
as follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">umask <ns0:sub idref="var_accounts_user_umask" /></html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SA-8</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:rationale xml:lang="en-US">The umask value influences the permissions assigned to files when they are created.
A misconfigured umask value could result in files with excessive permissions that can be read or
written to by unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_umask_etc_bashrc" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_accounts_user_umask="<ns0:sub idref="var_accounts_user_umask" />"

grep -q umask /etc/bashrc &amp;&amp; \
  sed -i "s/umask.*/umask $var_accounts_user_umask/g" /etc/bashrc
if ! [ $? -eq 0 ]; then
    echo "umask $var_accounts_user_umask" &gt;&gt; /etc/bashrc
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_accounts_user_umask:var:1" value-id="var_accounts_user_umask" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_umask_etc_bashrc:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_umask_etc_bashrc_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_umask_etc_csh_cshrc" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Ensure the Default C Shell Umask is Set Correctly</ns0:title>
            <ns0:description xml:lang="en-US">
To ensure the default umask for users of the C shell is set properly,
add or correct the <html:code xmlns:html="http://www.w3.org/1999/xhtml">umask</html:code> setting in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/csh.cshrc</html:code> to read as follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">umask <ns0:sub idref="var_accounts_user_umask" /></html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SA-8</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:rationale xml:lang="en-US">The umask value influences the permissions assigned to files when they are created.
A misconfigured umask value could result in files with excessive permissions that can be read or
written to by unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_umask_etc_csh_cshrc" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_accounts_user_umask="<ns0:sub idref="var_accounts_user_umask" />"

grep -q umask /etc/csh.cshrc &amp;&amp; \
  sed -i "s/umask.*/umask $var_accounts_user_umask/g" /etc/csh.cshrc
if ! [ $? -eq 0 ]; then
    echo "umask $var_accounts_user_umask" &gt;&gt; /etc/csh.cshrc
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_accounts_user_umask:var:1" value-id="var_accounts_user_umask" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_umask_etc_csh_cshrc:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_umask_etc_csh_cshrc_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_umask_etc_profile" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Ensure the Default Umask is Set Correctly in /etc/profile</ns0:title>
            <ns0:description xml:lang="en-US">
To ensure the default umask controlled by <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/profile</html:code> is set properly,
add or correct the <html:code xmlns:html="http://www.w3.org/1999/xhtml">umask</html:code> setting in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/profile</html:code> to read as follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">umask <ns0:sub idref="var_accounts_user_umask" /></html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SA-8</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:rationale xml:lang="en-US">The umask value influences the permissions assigned to files when they are created.
A misconfigured umask value could result in files with excessive permissions that can be read or
written to by unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_umask_etc_profile" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_accounts_user_umask="<ns0:sub idref="var_accounts_user_umask" />"

grep -q umask /etc/profile &amp;&amp; \
  sed -i "s/umask.*/umask $var_accounts_user_umask/g" /etc/profile
if ! [ $? -eq 0 ]; then
    echo "umask $var_accounts_user_umask" &gt;&gt; /etc/profile
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_accounts_user_umask:var:1" value-id="var_accounts_user_umask" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_umask_etc_profile:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_umask_etc_profile_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="accounts_umask_etc_login_defs" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Ensure the Default Umask is Set Correctly in login.defs</ns0:title>
            <ns0:description xml:lang="en-US">
To ensure the default umask controlled by <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code> is set properly,
add or correct the <html:code xmlns:html="http://www.w3.org/1999/xhtml">UMASK</html:code> setting in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/login.defs</html:code> to read as follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">UMASK <ns0:sub idref="var_accounts_user_umask" /></html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SA-8</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00228</ns0:reference>
            <ns0:rationale xml:lang="en-US">The umask value influences the permissions assigned to files when they are created.
A misconfigured umask value could result in files with excessive permissions that can be read and
written to by unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="accounts_umask_etc_login_defs" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_accounts_user_umask="<ns0:sub idref="var_accounts_user_umask" />"

grep -q UMASK /etc/login.defs &amp;&amp; \
  sed -i "s/UMASK.*/UMASK $var_accounts_user_umask/g" /etc/login.defs
if ! [ $? -eq 0 ]; then
    echo "UMASK $var_accounts_user_umask" &gt;&gt; /etc/login.defs
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-var_accounts_user_umask:var:1" value-id="var_accounts_user_umask" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-accounts_umask_etc_login_defs:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-accounts_umask_etc_login_defs_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="accounts-physical">
        <ns0:title xml:lang="en-US">Protect Physical Console Access</ns0:title>
        <ns0:description xml:lang="en-US">It is impossible to fully protect a system from an
attacker with physical access, so securing the space in which the
system is located should be considered a necessary step. However,
there are some steps which, if taken, make it more difficult for an
attacker to quickly or undetectably modify a system from its
console.</ns0:description>
        <ns0:Group id="bootloader">
          <ns0:title xml:lang="en-US">Set Boot Loader Password</ns0:title>
          <ns0:description xml:lang="en-US">During the boot process, the boot loader is
responsible for starting the execution of the kernel and passing
options to it. The boot loader allows for the selection of
different kernels - possibly on different partitions or media.
The default Red Hat Enterprise Linux boot loader for x86 systems is called GRUB2.
Options it can pass to the kernel include <html:i xmlns:html="http://www.w3.org/1999/xhtml">single-user mode</html:i>, which
provides root access without any authentication, and the ability to
disable SELinux. To prevent local users from modifying the boot
parameters and endangering security, protect the boot loader configuration
with a password and ensure its configuration file's permissions
are set properly.
</ns0:description>
          <ns0:Rule id="file_user_owner_grub2_cfg" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify /boot/grub2/grub.cfg User Ownership</ns0:title>
            <ns0:description xml:lang="en-US">The file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/boot/grub2/grub.cfg</html:code> should 
be owned by the <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code> user to prevent destruction 
or modification of the file.

    To properly set the owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/boot/grub2/grub.cfg</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root /boot/grub2/grub.cfg </html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6(7)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">225</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-7.1</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.5.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Only root should be able to modify important boot parameters.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_user_owner_grub2_cfg" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">chown root /boot/grub2/grub.cfg
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_user_owner_grub2_cfg:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_user_owner_grub2_cfg_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_group_owner_grub2_cfg" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify /boot/grub2/grub.cfg Group Ownership</ns0:title>
            <ns0:description xml:lang="en-US">The file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/boot/grub2/grub.cfg</html:code> should 
be group-owned by the <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code> group to prevent 
destruction or modification of the file.

    To properly set the group owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/boot/grub2/grub.cfg</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chgrp root /boot/grub2/grub.cfg </html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6(7)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">225</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-7.1</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.5.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code> group is a highly-privileged group. Furthermore, the group-owner of this
file should not have any access privileges anyway.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_group_owner_grub2_cfg" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">chgrp root /boot/grub2/grub.cfg
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_group_owner_grub2_cfg:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_group_owner_grub2_cfg_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="file_permissions_grub2_cfg" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify /boot/grub2/grub.cfg Permissions</ns0:title>
            <ns0:description xml:lang="en-US">File permissions for <html:code xmlns:html="http://www.w3.org/1999/xhtml">/boot/grub2/grub.cfg</html:code> should be set to 600.

    To properly set the permissions of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/boot/grub2/grub.cfg</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 600 /boot/grub2/grub.cfg</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6(7)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">225</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.5.2</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Proper permissions ensure that only the root user can modify important boot
parameters.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="file_permissions_grub2_cfg" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">chmod 600 /boot/grub2/grub.cfg
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_grub2_cfg:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_grub2_cfg_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="bootloader_password" selected="false" severity="high">
            <ns0:title xml:lang="en-US">Set Boot Loader Password</ns0:title>
            <ns0:description xml:lang="en-US">The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To do so, select a superuser account and password and add them into the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/grub.d/01_users</html:code> configuration file.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Since plaintext passwords are a security risk, generate a hash for the pasword
by running the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ grub2-mkpasswd-pbkdf2</html:pre>
When prompted, enter the password that was selected and insert the returned 
password hash into the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/grub.d/01_users</html:code> configuration file
immediately after the superuser account.
(Use the output from <html:code xmlns:html="http://www.w3.org/1999/xhtml">grub2-mkpasswd-pbkdf2</html:code> as the value of 
<html:b xmlns:html="http://www.w3.org/1999/xhtml">password-hash</html:b>):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">password_pbkdf2 <html:b>superusers-account</html:b> <html:b>password-hash</html:b></html:pre>
NOTE: It is recommended not to use common administrator account names like root,
admin, or administrator for the grub2 superuser account. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To meet FISMA Moderate, the bootloader superuser account and password MUST 
differ from the root account and password.
Once the superuser account and password have been added, update the 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">grub.cfg</html:code> file by running:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">grub2-mkconfig -o /boot/grub2/grub.cfg</html:pre>
NOTE: Do NOT manually add the superuser account and password to the 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">grub.cfg</html:code> file as the grub2-mkconfig command overwrites this file.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-2(1)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(e)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">213</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000080-GPOS-00048</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.5.3</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Password protection on the boot loader configuration ensures
users with physical access cannot trivially alter
important bootloader settings. These include which kernel to use,
and whether to enter single-user mode. For more information on how to configure 
the grub2 superuser account and password, please refer to 
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li><html:a href="https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html">https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html</html:a></html:li>.
</html:ul>
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-bootloader_password:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-bootloader_password_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="bootloader_uefi_password" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set the UEFI Boot Loader Password</ns0:title>
            <ns0:description xml:lang="en-US">The UEFI grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To do so, select a superuser account and password and add them into the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/grub.d/01_users</html:code> configuration file.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Since plaintext passwords are a security risk, generate a hash for the pasword
by running the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ grub2-mkpasswd-pbkdf2</html:pre>
When prompted, enter the password that was selected and insert the returned
password hash into the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/grub.d/01_users</html:code> configuration file immediately
after the superuser account.
(Use the output from <html:code xmlns:html="http://www.w3.org/1999/xhtml">grub2-mkpasswd-pbkdf2</html:code> as the value of
<html:b xmlns:html="http://www.w3.org/1999/xhtml">password-hash</html:b>):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">password_pbkdf2 <html:b>superusers-account</html:b> <html:b>password-hash</html:b></html:pre>
NOTE: It is recommended not to use common administrator account names like root,
admin, or administrator for the grub2 superuser account.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To meet FISMA Moderate, the bootloader superuser account and password MUST
differ from the root account and password.
Once the superuser account and password have been added, update the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">grub.cfg</html:code> file by running:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</html:pre>
NOTE: Do NOT manually add the superuser account and password to the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">grub.cfg</html:code> file as the grub2-mkconfig command overwrites this file.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">213</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000080-GPOS-00048</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Password protection on the boot loader configuration ensures
users with physical access cannot trivially alter
important bootloader settings. These include which kernel to use,
and whether to enter single-user mode. For more information on how to configure
the grub2 superuser account and password, please refer to
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li><html:a href="https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html">https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html</html:a></html:li>.
</html:ul>
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-bootloader_uefi_password:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-bootloader_uefi_password_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Rule id="require_singleuser_auth" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Require Authentication for Single User Mode</ns0:title>
          <ns0:description xml:lang="en-US">Single-user mode is intended as a system recovery
method, providing a single user root access to the system by
providing a boot option at startup. By default, no authentication
is performed if single-user mode is selected.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
By default, single-user mode is protected by requiring a password and is set
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/usr/lib/systemd/system/rescue.service</html:code>.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-2(1)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">213</ns0:reference>
          <ns0:rationale xml:lang="en-US">
This prevents attackers with physical access from trivially bypassing security
on the machine and gaining root access. Such accesses are further prevented
by configuring the bootloader password.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="require_singleuser_auth" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">grep -q sulogin /usr/lib/systemd/system/rescue.service 
if ! [ $? -eq 0 ]; then
    sed -i "s/-c \"/-c \"\/sbin\/sulogin; /g" /usr/lib/systemd/system/rescue.service
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-require_singleuser_auth:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-require_singleuser_auth_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="service_debug-shell_disabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable debug-shell SystemD Service</ns0:title>
          <ns0:description xml:lang="en-US">SystemD's <html:code xmlns:html="http://www.w3.org/1999/xhtml">debug-shell</html:code> service is intended to
diagnose SystemD related boot issues with various <html:code xmlns:html="http://www.w3.org/1999/xhtml">systemctl</html:code>
commands. Once enabled and following a system reboot, the root shell
will be available on <html:code xmlns:html="http://www.w3.org/1999/xhtml">tty9</html:code> which is access by pressing
<html:code xmlns:html="http://www.w3.org/1999/xhtml">CTRL-ALT-F9</html:code>. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">debug-shell</html:code> service should only be used
for SystemD related issues and should otherwise be disabled.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
By default, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">debug-shell</html:code> SystemD service is disabled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">debug-shell</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable debug-shell.service</html:pre>
</ns0:description>
          <ns0:rationale xml:lang="en-US">
This prevents attackers with physical access from trivially bypassing security
on the machine through valid troubleshooting configurations and gaining root
access when the system is rebooted.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_debug-shell_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable debug-shell
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_debug-shell_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service debug-shell
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - debug-shell

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_debug-shell_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_debug-shell_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="disable_ctrlaltdel_reboot" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Disable Ctrl-Alt-Del Reboot Activation</ns0:title>
          <ns0:description xml:lang="en-US">
By default, <html:code xmlns:html="http://www.w3.org/1999/xhtml">SystemD</html:code> will reboot the system if the <html:code xmlns:html="http://www.w3.org/1999/xhtml">Ctrl-Alt-Del</html:code>
key sequence is pressed.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To configure the system to ignore the <html:code xmlns:html="http://www.w3.org/1999/xhtml">Ctrl-Alt-Del</html:code> key sequence from the
command line instead of rebooting the system, do either of the following:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ln -sf /dev/null /etc/systemd/system/ctrl-alt-del.target</html:pre>
or
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">systemctl mask ctrl-alt-del.target</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Do not simply delete the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/usr/lib/systemd/system/ctrl-alt-del.service</html:code> file,
as this file may be restored during future system updates.
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">Disabling the <html:code xmlns:html="http://www.w3.org/1999/xhtml">Ctrl-Alt-Del</html:code> key sequence
with <html:code xmlns:html="http://www.w3.org/1999/xhtml">SystemD</html:code> DOES NOT disable the <html:code xmlns:html="http://www.w3.org/1999/xhtml">Ctrl-Alt-Del</html:code> key sequence
if running in <html:code xmlns:html="http://www.w3.org/1999/xhtml">graphical.target</html:code> mode (e.g. in GNOME, KDE, etc.)! The
<html:code xmlns:html="http://www.w3.org/1999/xhtml">Ctrl-Alt-Del</html:code> key sequence will only be disabled if running in
the non-graphical <html:code xmlns:html="http://www.w3.org/1999/xhtml">multi-user.target</html:code> mode.
</ns0:warning>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
A locally logged-in user who presses Ctrl-Alt-Del, when at the console,
can reboot the system. If accidentally pressed, as could happen in
the case of mixed OS environment, this can create the risk of short-term
loss of availability of systems due to unintentional reboot.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="disable_ctrlaltdel_reboot" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"># The process to disable ctrl+alt+del has changed in RHEL7. 
# Reference: https://access.redhat.com/solutions/1123873
ln -sf /dev/null /etc/systemd/system/ctrl-alt-del.target
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-disable_ctrlaltdel_reboot:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-disable_ctrlaltdel_reboot_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="disable_interactive_boot" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Verify that Interactive Boot is Disabled</ns0:title>
          <ns0:description xml:lang="en-US">
Red Hat Enterprise Linux systems support an "interactive boot" option that can
be used to prevent services from being started. On a Red Hat Enterprise Linux 7
system, interactive boot can be enabled by providing a <html:code xmlns:html="http://www.w3.org/1999/xhtml">1</html:code>,
<html:code xmlns:html="http://www.w3.org/1999/xhtml">yes</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">true</html:code>, or <html:code xmlns:html="http://www.w3.org/1999/xhtml">on</html:code> value to the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">systemd.confirm_spawn</html:code> kernel argument in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/default/grub</html:code>.
Remove any instance of <html:pre xmlns:html="http://www.w3.org/1999/xhtml">systemd.confirm_spawn=(1|yes|true|on)</html:pre> from
the kernel arguments in that file to disable interactive boot.
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">The GRUB 2 configuration file, <html:code xmlns:html="http://www.w3.org/1999/xhtml">grub.cfg</html:code>,
is automatically updated each time a new kernel is installed. Note that any
changes to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/default/grub</html:code> require rebuilding the <html:code xmlns:html="http://www.w3.org/1999/xhtml">grub.cfg</html:code>
file. To update the GRUB 2 configuration file manually, use the
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">grub2-mkconfig -o</html:pre> command as follows:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>On BIOS-based machines, issue the following command as <html:code>root</html:code>:
<html:pre>~]# grub2-mkconfig -o /boot/grub2/grub.cfg</html:pre></html:li><html:li>On UEFI-based machines, issue the following command as <html:code>root</html:code>:
<html:pre>~]# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</html:pre></html:li></html:ul>
</ns0:warning>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-2</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">213</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Using interactive boot, the console user could disable auditing, firewalls,
or other services, weakening system security.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="disable_interactive_boot" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
# Systemd confirm_spawn regex to search for and delete if found
CONFIRM_SPAWN_REGEX="systemd.confirm_spawn=\(1\|yes\|true\|on\)"

# Modify both the GRUB_CMDLINE_LINUX and GRUB_CMDLINE_LINUX_DEFAULT directives
for grubcmdline in "GRUB_CMDLINE_LINUX" "GRUB_CMDLINE_LINUX_DEFAULT"
do
  # Remove 'systemd.confirm_spawn' argument from /etc/default/grub if found
  if grep -q "^${grubcmdline}=\".*${CONFIRM_SPAWN_REGEX}.*\"" /etc/default/grub
  then
    # Remove all three possible occurrences of CONFIRM_SPAWN_REGEX:
    # At the start
    sed -i "s/\"${CONFIRM_SPAWN_REGEX} /\"/" /etc/default/grub
    # At the end
    sed -i "s/ ${CONFIRM_SPAWN_REGEX}\"$/\"/" /etc/default/grub
    # In the middle
    sed -i "s/ ${CONFIRM_SPAWN_REGEX}//" /etc/default/grub
  fi
done
# Remove 'systemd.confirm_spawn' kernel argument also from runtime settings
/sbin/grubby --update-kernel=ALL --remove-args="systemd.confirm_spawn"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-disable_interactive_boot:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-disable_interactive_boot_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="screen_locking">
          <ns0:title xml:lang="en-US">Configure Screen Locking</ns0:title>
          <ns0:description xml:lang="en-US">When a user must temporarily leave an account
logged-in, screen locking should be employed to prevent passersby
from abusing the account. User education and training is
particularly important for screen locking to be effective, and policies
can be implemented to reinforce this.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Automatic screen locking is only meant as a safeguard for
those cases where a user forgot to lock the screen.</ns0:description>
          <ns0:Group id="console_screen_locking">
            <ns0:title xml:lang="en-US">Configure Console Screen Locking</ns0:title>
            <ns0:description xml:lang="en-US">
A console screen locking mechanism is provided in the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">screen</html:code> package, which is not installed by default.
</ns0:description>
            <ns0:Rule id="package_screen_installed" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Install the screen Package</ns0:title>
              <ns0:description xml:lang="en-US">
To enable console screen locking, install the <html:code xmlns:html="http://www.w3.org/1999/xhtml">screen</html:code> package:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install screen</html:pre>
Instruct users to begin new terminal sessions with the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ screen</html:pre>
The console can now be locked with the following key combination:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ctrl+a x</html:pre>
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-11(a)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">57</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000029-GPOS-00010</ns0:reference>
              <ns0:rationale xml:lang="en-US">
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate
physical vicinity of the information system but des not logout because of the temporary nature of the absence.
Rather than relying on the user to manually lock their operation system session prior to vacating the vicinity,
operating systems need to be able to identify when a user's session has idled and take action to initiate the
session lock. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">screen</html:code> package allows for a session lock to be implemented and configured.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="package_screen_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command install screen
</ns0:fix>
              <ns0:fix complexity="low" disruption="low" id="package_screen_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Ensure screen is installed
  package:
    name="{{item}}"
    state=present
  with_items:
    - screen
</ns0:fix>
              <ns0:fix complexity="low" disruption="low" id="package_screen_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:puppet">include install_screen

class install_screen {
  package { 'screen':
    ensure =&gt; 'installed',
  }
}
</ns0:fix>
              <ns0:fix complexity="low" disruption="low" id="package_screen_installed" reboot="false" strategy="enable" system="urn:redhat:anaconda:pre">
package --add=screen
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_screen_installed:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_screen_installed_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
          </ns0:Group>
          <ns0:Group id="smart_card_login">
            <ns0:title xml:lang="en-US">Hardware Tokens for Authentication</ns0:title>
            <ns0:description xml:lang="en-US">
The use of hardware tokens such as smart cards for system login
provides stronger, two-factor authentication than using a username and password.
In Red Hat Enterprise Linux servers and workstations, hardware token login
is not enabled by default and must be enabled in the system settings.
</ns0:description>
            <ns0:Rule id="smartcard_auth" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Enable Smart Card Login</ns0:title>
              <ns0:description xml:lang="en-US">
To enable smart card authentication, consult the documentation at:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li><html:b><html:a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System-Level_Authentication_Guide/smartcards.html#authconfig-smartcards">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System-Level_Authentication_Guide/smartcards.html#authconfig-smartcards</html:a></html:b></html:li></html:ul>
For guidance on enabling SSH to authenticate against a Common Access Card (CAC), consult documentation at:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li><html:b><html:a href="https://access.redhat.com/solutions/82273">https://access.redhat.com/solutions/82273</html:a></html:b></html:li></html:ul>
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-2(2)</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">765</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">766</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">767</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">768</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">771</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">772</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">884</ns0:reference>
              <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.3</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000104-GPOS-00051</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000106-GPOS-00053</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000107-GPOS-00054</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000109-GPOS-00056</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000108-GPOS-00055</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000108-GPOS-00057</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000108-GPOS-00058</ns0:reference>
              <ns0:rationale xml:lang="en-US">Smart card login provides two-factor authentication stronger than
that provided by a username and password combination. Smart cards leverage PKI
(public key infrastructure) in order to provide and verify credentials.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="smartcard_auth" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Install required packages
<ns0:sub idref="function_package_command" />
package_command install esc
package_command install pam_pkcs11

# Enable pcscd.socket systemd activation socket
<ns0:sub idref="function_service_command" />
service_command enable pcscd.socket

# Configure the expected /etc/pam.d/system-auth{,-ac} settings directly
#
# The code below will configure system authentication in the way smart card
# logins will be enabled, but also user login(s) via other method to be allowed
#
# NOTE: It is not possible to use the 'authconfig' command to perform the
#       remediation for us, because call of 'authconfig' would discard changes
#       for other remediations (see RH BZ#1357019 for details)
#
#	Therefore we need to configure the necessary settings directly.
#

# Define system-auth config location
SYSTEM_AUTH_CONF="/etc/pam.d/system-auth"
# Define expected 'pam_env.so' row in $SYSTEM_AUTH_CONF
PAM_ENV_SO="auth.*required.*pam_env.so"

# Define 'pam_succeed_if.so' row to be appended past $PAM_ENV_SO row into $SYSTEM_AUTH_CONF
SYSTEM_AUTH_PAM_SUCCEED="\
auth        \[success=1 default=ignore\] pam_succeed_if.so service notin \
login:gdm:xdm:kdm:xscreensaver:gnome-screensaver:kscreensaver quiet use_uid"
# Define 'pam_pkcs11.so' row to be appended past $SYSTEM_AUTH_PAM_SUCCEED
# row into SYSTEM_AUTH_CONF file
SYSTEM_AUTH_PAM_PKCS11="\
auth        \[success=done authinfo_unavail=ignore ignore=ignore default=die\] \
pam_pkcs11.so nodebug"

# Define smartcard-auth config location
SMARTCARD_AUTH_CONF="/etc/pam.d/smartcard-auth"
# Define 'pam_pkcs11.so' auth section to be appended past $PAM_ENV_SO into $SMARTCARD_AUTH_CONF
SMARTCARD_AUTH_SECTION="\
auth        [success=done ignore=ignore default=die] pam_pkcs11.so wait_for_card card_only"
# Define expected 'pam_permit.so' row in $SMARTCARD_AUTH_CONF
PAM_PERMIT_SO="account.*required.*pam_permit.so"
# Define 'pam_pkcs11.so' password section
SMARTCARD_PASSWORD_SECTION="\
password    required      pam_pkcs11.so"

# First Correct the SYSTEM_AUTH_CONF configuration
if ! grep -q 'pam_pkcs11.so' "$SYSTEM_AUTH_CONF"
then
	# Append (expected) pam_succeed_if.so row past the pam_env.so into SYSTEM_AUTH_CONF file
	sed -i --follow-symlinks -e '/^'"$PAM_ENV_SO"'/a '"$SYSTEM_AUTH_PAM_SUCCEED" "$SYSTEM_AUTH_CONF"
	# Append (expected) pam_pkcs11.so row past the pam_succeed_if.so into SYSTEM_AUTH_CONF file
	sed -i --follow-symlinks -e '/^'"$SYSTEM_AUTH_PAM_SUCCEED"'/a '"$SYSTEM_AUTH_PAM_PKCS11" "$SYSTEM_AUTH_CONF"
fi

# Then also correct the SMARTCARD_AUTH_CONF
if ! grep -q 'pam_pkcs11.so' "$SMARTCARD_AUTH_CONF"
then
	# Append (expected) SMARTCARD_AUTH_SECTION row past the pam_env.so into SMARTCARD_AUTH_CONF file
	sed -i --follow-symlinks -e '/^'"$PAM_ENV_SO"'/a '"$SMARTCARD_AUTH_SECTION" "$SMARTCARD_AUTH_CONF"
	# Append (expected) SMARTCARD_PASSWORD_SECTION row past the pam_permit.so into SMARTCARD_AUTH_CONF file
	sed -i --follow-symlinks -e '/^'"$PAM_PERMIT_SO"'/a '"$SMARTCARD_PASSWORD_SECTION" "$SMARTCARD_AUTH_CONF"
fi

# Perform /etc/pam_pkcs11/pam_pkcs11.conf settings below
# Define selected constants for later reuse
SP="[:space:]"
PAM_PKCS11_CONF="/etc/pam_pkcs11/pam_pkcs11.conf"

# Ensure OCSP is turned on in $PAM_PKCS11_CONF
# 1) First replace any occurrence of 'none' value of 'cert_policy' key setting with the correct configuration
sed -i "s/^[$SP]*cert_policy[$SP]\+=[$SP]\+none;/\t\tcert_policy = ca, ocsp_on, signature;/g" "$PAM_PKCS11_CONF"
# 2) Then append 'ocsp_on' value setting to each 'cert_policy' key in $PAM_PKCS11_CONF configuration line,
# which does not contain it yet
sed -i "/ocsp_on/! s/^[$SP]*cert_policy[$SP]\+=[$SP]\+\(.*\);/\t\tcert_policy = \1, ocsp_on;/" "$PAM_PKCS11_CONF"
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-smartcard_auth:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-smartcard_auth_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
          </ns0:Group>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="accounts-banners">
        <ns0:title xml:lang="en-US">Warning Banners for System Accesses</ns0:title>
        <ns0:description xml:lang="en-US">Each system should expose as little information about
itself as possible.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
System banners, which are typically displayed just before a
login prompt, give out information about the service or the host's
operating system. This might include the distribution name and the
system kernel version, and the particular version of a network
service. This information can assist intruders in gaining access to
the system as it can reveal whether the system is running
vulnerable software. Most network services can be configured to
limit what information is displayed.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Many organizations implement security policies that require a
system banner provide notice of the system's ownership, provide
warning to unauthorized users, and remind authorized users of their
consent to monitoring.</ns0:description>
        <ns0:Value id="login_banner_text" operator="equals" type="string">
          <ns0:title xml:lang="en-US">Login Banner Verbiage</ns0:title>
          <ns0:description xml:lang="en-US">Enter an appropriate login banner for your organization. Please note that new lines must
be expressed by the '\n' character and special characters like parentheses and quotation marks must be escaped with '\'.</ns0:description>
          <ns0:value selector="usgcb_default">--[\s\n]+WARNING[\s\n]+--[\s\n]*This[\s\n]+system[\s\n]+is[\s\n]+for[\s\n]+the[\s\n]+use[\s\n]+of[\s\n]+authorized[\s\n]+users[\s\n]+only.[\s\n]+Individuals[\s\n]*using[\s\n]+this[\s\n]+computer[\s\n]+system[\s\n]+without[\s\n]+authority[\s\n]+or[\s\n]+in[\s\n]+excess[\s\n]+of[\s\n]+their[\s\n]*authority[\s\n]+are[\s\n]+subject[\s\n]+to[\s\n]+having[\s\n]+all[\s\n]+their[\s\n]+activities[\s\n]+on[\s\n]+this[\s\n]+system[\s\n]*monitored[\s\n]+and[\s\n]+recorded[\s\n]+by[\s\n]+system[\s\n]+personnel.[\s\n]+Anyone[\s\n]+using[\s\n]+this[\s\n]*system[\s\n]+expressly[\s\n]+consents[\s\n]+to[\s\n]+such[\s\n]+monitoring[\s\n]+and[\s\n]+is[\s\n]+advised[\s\n]+that[\s\n]*if[\s\n]+such[\s\n]+monitoring[\s\n]+reveals[\s\n]+possible[\s\n]+evidence[\s\n]+of[\s\n]+criminal[\s\n]+activity[\s\n]*system[\s\n]+personal[\s\n]+may[\s\n]+provide[\s\n]+the[\s\n]+evidence[\s\n]+of[\s\n]+such[\s\n]+monitoring[\s\n]+to[\s\n]+law[\s\n]*enforcement[\s\n]+officials.</ns0:value>
          <ns0:value selector="dod_default">You[\s\n]+are[\s\n]+accessing[\s\n]+a[\s\n]+U.S.[\s\n]+Government[\s\n]+\(USG\)[\s\n]+Information[\s\n]+System[\s\n]+\(IS\)[\s\n]+that[\s\n]+is[\s\n]+provided[\s\n]+for[\s\n]+USG-authorized[\s\n]+use[\s\n]+only.[\s\n]*By[\s\n]+using[\s\n]+this[\s\n]+IS[\s\n]+\(which[\s\n]+includes[\s\n]+any[\s\n]+device[\s\n]+attached[\s\n]+to[\s\n]+this[\s\n]+IS\),[\s\n]+you[\s\n]+consent[\s\n]+to[\s\n]+the[\s\n]+following[\s\n]+conditions\:[\s\n]*-[\s\n]*The[\s\n]+USG[\s\n]+routinely[\s\n]+intercepts[\s\n]+and[\s\n]+monitors[\s\n]+communications[\s\n]+on[\s\n]+this[\s\n]+IS[\s\n]+for[\s\n]+purposes[\s\n]+including,[\s\n]+but[\s\n]+not[\s\n]+limited[\s\n]+to,[\s\n]+penetration[\s\n]+testing,[\s\n]+COMSEC[\s\n]+monitoring,[\s\n]+network[\s\n]+operations[\s\n]+and[\s\n]+defense,[\s\n]+personnel[\s\n]+misconduct[\s\n]+\(PM\),[\s\n]+law[\s\n]+enforcement[\s\n]+\(LE\),[\s\n]+and[\s\n]+counterintelligence[\s\n]+\(CI\)[\s\n]+investigations.[\s\n]*-[\s\n]*At[\s\n]+any[\s\n]+time,[\s\n]+the[\s\n]+USG[\s\n]+may[\s\n]+inspect[\s\n]+and[\s\n]+seize[\s\n]+data[\s\n]+stored[\s\n]+on[\s\n]+this[\s\n]+IS.[\s\n]*-[\s\n]*Communications[\s\n]+using,[\s\n]+or[\s\n]+data[\s\n]+stored[\s\n]+on,[\s\n]+this[\s\n]+IS[\s\n]+are[\s\n]+not[\s\n]+private,[\s\n]+are[\s\n]+subject[\s\n]+to[\s\n]+routine[\s\n]+monitoring,[\s\n]+interception,[\s\n]+and[\s\n]+search,[\s\n]+and[\s\n]+may[\s\n]+be[\s\n]+disclosed[\s\n]+or[\s\n]+used[\s\n]+for[\s\n]+any[\s\n]+USG-authorized[\s\n]+purpose.[\s\n]*-[\s\n]*This[\s\n]+IS[\s\n]+includes[\s\n]+security[\s\n]+measures[\s\n]+\(e.g.,[\s\n]+authentication[\s\n]+and[\s\n]+access[\s\n]+controls\)[\s\n]+to[\s\n]+protect[\s\n]+USG[\s\n]+interests[\s\n]+--[\s\n]+not[\s\n]+for[\s\n]+your[\s\n]+personal[\s\n]+benefit[\s\n]+or[\s\n]+privacy.[\s\n]*-[\s\n]*Notwithstanding[\s\n]+the[\s\n]+above,[\s\n]+using[\s\n]+this[\s\n]+IS[\s\n]+does[\s\n]+not[\s\n]+constitute[\s\n]+consent[\s\n]+to[\s\n]+PM,[\s\n]+LE[\s\n]+or[\s\n]+CI[\s\n]+investigative[\s\n]+searching[\s\n]+or[\s\n]+monitoring[\s\n]+of[\s\n]+the[\s\n]+content[\s\n]+of[\s\n]+privileged[\s\n]+communications,[\s\n]+or[\s\n]+work[\s\n]+product,[\s\n]+related[\s\n]+to[\s\n]+personal[\s\n]+representation[\s\n]+or[\s\n]+services[\s\n]+by[\s\n]+attorneys,[\s\n]+psychotherapists,[\s\n]+or[\s\n]+clergy,[\s\n]+and[\s\n]+their[\s\n]+assistants.[\s\n]+Such[\s\n]+communications[\s\n]+and[\s\n]+work[\s\n]+product[\s\n]+are[\s\n]+private[\s\n]+and[\s\n]+confidential.[\s\n]+See[\s\n]+User[\s\n]+Agreement[\s\n]+for[\s\n]+details.</ns0:value>
          <ns0:value selector="dod_short">I\'ve[\s\n]+read[\s\n]+\&amp;[\s\n]+consent[\s\n]+to[\s\n]+terms[\s\n]+in[\s\n]+IS[\s\n]+user[\s\n]+agreem\'t.</ns0:value>
          <ns0:value selector="dss_odaa_default">[\s\n]+Use[\s\n]+of[\s\n]+this[\s\n]+or[\s\n]+any[\s\n]+other[\s\n]+DoD[\s\n]+interest[\s\n]+computer[\s\n]+system[\s\n]+constitutes[\s\n]+consent[\s\n]+to[\s\n]+monitoring[\s\n]+at[\s\n]+all[\s\n]+times.[\s\n]+This[\s\n]+is[\s\n]+a[\s\n]+DoD[\s\n]+interest[\s\n]+computer[\s\n]+system.[\s\n]+All[\s\n]+DoD[\s\n]+interest[\s\n]+computer[\s\n]+systems[\s\n]+and[\s\n]+related[\s\n]+equipment[\s\n]+are[\s\n]+intended[\s\n]+for[\s\n]+the[\s\n]+communication,[\s\n]+transmission,[\s\n]+processing,[\s\n]+and[\s\n]+storage[\s\n]+of[\s\n]+official[\s\n]+U.S.[\s\n]+Government[\s\n]+or[\s\n]+other[\s\n]+authorized[\s\n]+information[\s\n]+only.[\s\n]+All[\s\n]+DoD[\s\n]+interest[\s\n]+computer[\s\n]+systems[\s\n]+are[\s\n]+subject[\s\n]+to[\s\n]+monitoring[\s\n]+at[\s\n]+all[\s\n]+times[\s\n]+to[\s\n]+ensure[\s\n]+proper[\s\n]+functioning[\s\n]+of[\s\n]+equipment[\s\n]+and[\s\n]+systems[\s\n]+including[\s\n]+security[\s\n]+devices[\s\n]+and[\s\n]+systems,[\s\n]+to[\s\n]+prevent[\s\n]+unauthorized[\s\n]+use[\s\n]+and[\s\n]+violations[\s\n]+of[\s\n]+statutes[\s\n]+and[\s\n]+security[\s\n]+regulations,[\s\n]+to[\s\n]+deter[\s\n]+criminal[\s\n]+activity,[\s\n]+and[\s\n]+for[\s\n]+other[\s\n]+similar[\s\n]+purposes.[\s\n]+Any[\s\n]+user[\s\n]+of[\s\n]+a[\s\n]+DoD[\s\n]+interest[\s\n]+computer[\s\n]+system[\s\n]+should[\s\n]+be[\s\n]+aware[\s\n]+that[\s\n]+any[\s\n]+information[\s\n]+placed[\s\n]+in[\s\n]+the[\s\n]+system[\s\n]+is[\s\n]+subject[\s\n]+to[\s\n]+monitoring[\s\n]+and[\s\n]+is[\s\n]+not[\s\n]+subject[\s\n]+to[\s\n]+any[\s\n]+expectation[\s\n]+of[\s\n]+privacy.[\s\n]+If[\s\n]+monitoring[\s\n]+of[\s\n]+this[\s\n]+or[\s\n]+any[\s\n]+other[\s\n]+DoD[\s\n]+interest[\s\n]+computer[\s\n]+system[\s\n]+reveals[\s\n]+possible[\s\n]+evidence[\s\n]+of[\s\n]+violation[\s\n]+of[\s\n]+criminal[\s\n]+statutes,[\s\n]+this[\s\n]+evidence[\s\n]+and[\s\n]+any[\s\n]+other[\s\n]+related[\s\n]+information,[\s\n]+including[\s\n]+identification[\s\n]+information[\s\n]+about[\s\n]+the[\s\n]+user,[\s\n]+may[\s\n]+be[\s\n]+provided[\s\n]+to[\s\n]+law[\s\n]+enforcement[\s\n]+officials.[\s\n]+If[\s\n]+monitoring[\s\n]+of[\s\n]+this[\s\n]+or[\s\n]+any[\s\n]+other[\s\n]+DoD[\s\n]+interest[\s\n]+computer[\s\n]+systems[\s\n]+reveals[\s\n]+violations[\s\n]+of[\s\n]+security[\s\n]+regulations[\s\n]+or[\s\n]+unauthorized[\s\n]+use,[\s\n]+employees[\s\n]+who[\s\n]+violate[\s\n]+security[\s\n]+regulations[\s\n]+or[\s\n]+make[\s\n]+unauthorized[\s\n]+use[\s\n]+of[\s\n]+DoD[\s\n]+interest[\s\n]+computer[\s\n]+systems[\s\n]+are[\s\n]+subject[\s\n]+to[\s\n]+appropriate[\s\n]+disciplinary[\s\n]+action.[\s\n]+Use[\s\n]+of[\s\n]+this[\s\n]+or[\s\n]+any[\s\n]+other[\s\n]+DoD[\s\n]+interest[\s\n]+computer[\s\n]+system[\s\n]+constitutes[\s\n]+consent[\s\n]+to[\s\n]+monitoring[\s\n]+at[\s\n]+all[\s\n]+times.</ns0:value>
        </ns0:Value>
        <ns0:Rule id="banner_etc_issue" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Modify the System Login Banner</ns0:title>
          <ns0:description xml:lang="en-US">
To configure the system login banner edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/issue</html:code>. Replace 
the default text with a message compliant with the local site policy 
or a legal disclaimer.

The DoD required text is either:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:code xmlns:html="http://www.w3.org/1999/xhtml">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: 
<html:br />-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. 
<html:br />-At any time, the USG may inspect and seize data stored on this IS. 
<html:br />-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. 
<html:br />-This IS includes security measures (e.g., authentication and access controls) 
to protect USG interests -- not for your personal benefit or privacy. 
<html:br />-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.</html:code>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
OR:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:code xmlns:html="http://www.w3.org/1999/xhtml">I've read &amp; consent to terms in IS user agreem't.</html:code>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(c)(1)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(c)(2)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(c)(3)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">48</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000023-GPOS-00006</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000024-GPOS-00007</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Display of a standardized and approved use notification before granting access to the operating system
ensures privacy and security notification verbiage used is consistent with applicable federal laws,
Executive Orders, directives, policies, regulations, standards, and guidance. 

System use notifications are required only for access via login interfaces with human users and
are not required when such human interfaces do not exist.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="banner_etc_issue" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
login_banner_text="<ns0:sub idref="login_banner_text" />"

# There was a regular-expression matching various banners, needs to be expanded
expanded=$(echo "$login_banner_text" | sed 's/\[\\s\\n\][+*]/ /g;s/\\//g;s/[^-]- /\n\n-/g')
formatted=$(echo "$expanded" | fold -sw 80)

cat &lt;&lt;EOF &gt;/etc/issue
$formatted
EOF

printf "\n" &gt;&gt; /etc/issue
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-login_banner_text:var:1" value-id="login_banner_text" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-banner_etc_issue:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-banner_etc_issue_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="gui_login_banner">
          <ns0:title xml:lang="en-US">Implement a GUI Warning Banner</ns0:title>
          <ns0:description xml:lang="en-US">In the default graphical environment, users logging
directly into the system are greeted with a login screen provided
by the GNOME3 Display Manager (GDM). The warning banner should be
displayed in this graphical environment for these users.
The following sections describe how to configure the GDM login
banner.
</ns0:description>
          <ns0:Rule id="dconf_gnome_banner_enabled" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Enable GNOME3 Login Warning Banner</ns0:title>
            <ns0:description xml:lang="en-US">
To enable displaying a login warning banner in the GNOME
Display Manager's login screen, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">banner-message-enable</html:code> setting must be 
set under an appropriate configuration file(s) in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d</html:code> directory 
and locked in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks</html:code> directory to prevent user modification. 
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
To display a banner, this setting must be enabled, and the user must be prevented
from making changes. The banner text must also be set.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(c)(1)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(c)(2)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(c)(3)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">48</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">OS-SRG-000023-GPOS-00006</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000024-GPOS-00007</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000228-GPOS-00088</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Display of a standardized and approved use notification before granting access to the operating system
ensures privacy and security notification verbiage used is consistent with applicable federal laws,
Executive Orders, directives, policies, regulations, standards, and guidance.

For U.S. Government systems, system use notifications are required only for access via login interfaces
with human users and are not required when such human interfaces do not exist.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_banner_enabled:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_banner_enabled_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dconf_gnome_login_banner_text" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set the GNOME3 Login Warning Banner Text</ns0:title>
            <ns0:description xml:lang="en-US">
To set the text shown by the GNOME3 Display Manager
in the login screen, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">banner-message-text</html:code> setting must be set under an
appropriate configuration file(s) in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d</html:code> directory and locked 
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dconf/db/gdm.d/locks</html:code> directory to prevent user modification. 
After the settings have been set, run <html:code xmlns:html="http://www.w3.org/1999/xhtml">dconf update</html:code>.
When entering a warning banner that spans several lines, remember
to begin and end the string with <html:code xmlns:html="http://www.w3.org/1999/xhtml">'</html:code> and use <html:code xmlns:html="http://www.w3.org/1999/xhtml">\n</html:code> for new lines.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(c)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">48</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000023-GPOS-00006</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000024-GPOS-00007</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000228-GPOS-00088</ns0:reference>
            <ns0:rationale xml:lang="en-US">
An appropriate warning message reinforces policy awareness during the logon
process and facilitates possible legal action against attackers.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-login_banner_text:var:1" value-id="login_banner_text" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dconf_gnome_login_banner_text:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-dconf_gnome_login_banner_text_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="network">
      <ns0:title xml:lang="en-US">Network Configuration and Firewalls</ns0:title>
      <ns0:description xml:lang="en-US">Most machines must be connected to a network of some
sort, and this brings with it the substantial risk of network
attack. This section discusses the security impact of decisions
about networking which must be made when configuring a system.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
This section also discusses firewalls, network access
controls, and other network security frameworks, which allow
system-level rules to be written that can limit an attackers' ability
to connect to your system. These rules can specify that network
traffic should be allowed or denied from certain IP addresses,
hosts, and networks. The rules can also specify which of the
system's network services are available to particular hosts or
networks.</ns0:description>
      <ns0:Group id="network_disable_unused_interfaces">
        <ns0:title xml:lang="en-US">Disable Unused Interfaces</ns0:title>
        <ns0:description xml:lang="en-US">Network interfaces expand the attack surface of the 
system.  Unused interfaces are not monitored or controlled, and 
should be disabled.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the system does not require network communications but still
needs to use the loopback interface, remove all files of the form
<html:code xmlns:html="http://www.w3.org/1999/xhtml">ifcfg-<html:i>interface</html:i></html:code> except for <html:code xmlns:html="http://www.w3.org/1999/xhtml">ifcfg-lo</html:code> from
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/network-scripts</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo rm /etc/sysconfig/network-scripts/ifcfg-<html:i>interface</html:i></html:pre>
If the system is a standalone machine with no need for network access or even
communication over the loopback device, then disable this service.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">network</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable network.service</html:pre>
</ns0:description>
      </ns0:Group>
      <ns0:Rule id="network_disable_ddns_interfaces" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Disable Client Dynamic DNS Updates</ns0:title>
        <ns0:description xml:lang="en-US">
Dynamic DNS allows clients to dynamically update their own DNS records.
The updates are transmitted by unencrypted means which can reveal information
to a potential malicious user. If the system does not require Dynamic DNS,
remove all <html:code xmlns:html="http://www.w3.org/1999/xhtml">DHCP_HOSTNAME</html:code> references from the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/network-scripts/ifcfg-<html:i>interface</html:i></html:code> scripts. If
<html:code xmlns:html="http://www.w3.org/1999/xhtml">dhclient</html:code> is used, remove all <html:code xmlns:html="http://www.w3.org/1999/xhtml">send host-name <html:i>hostname</html:i></html:code>
references from the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dhclient.conf</html:code> configuration file and/or any
reference from the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dhcp</html:code> directory.
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
        <ns0:rationale xml:lang="en-US">
Dynamic DNS updates transmit unencrypted information about a system
including its name and address and should not be used unless needed.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-network_disable_ddns_interfaces:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-network_disable_ddns_interfaces_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="network_disable_zeroconf" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Zeroconf Networking</ns0:title>
        <ns0:description xml:lang="en-US">Zeroconf networking allows the system to assign itself an IP
address and engage in IP communication without a statically-assigned address or
even a DHCP server. Automatic address assignment via Zeroconf (or DHCP) is not
recommended. To disable Zeroconf automatic route assignment in the 169.254.0.0
subnet, add or correct the following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/network</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">NOZEROCONF=yes</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">Zeroconf addresses are in the network 169.254.0.0. The networking
scripts add entries to the system's routing table for these addresses. Zeroconf
address assignment commonly occurs when the system is configured to use DHCP
but fails to receive an address assignment from the DHCP server.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="network_disable_zeroconf" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">echo "NOZEROCONF=yes" &gt;&gt; /etc/sysconfig/network
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-network_disable_zeroconf:def:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="network_sniffer_disabled" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Ensure System is Not Acting as a Network Sniffer</ns0:title>
        <ns0:description xml:lang="en-US">The system should not be acting as a network sniffer, which can
capture all traffic on the network to which it is connected. Run the following
to determine if any interface is running in promiscuous mode:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ ip link | grep PROMISC</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7(2).1(i)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf" />
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MA-3</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
        <ns0:rationale xml:lang="en-US">
Network interfaces in promiscuous mode allow for the capture of all network traffic
visible to the system. If unauthorized individuals can access these applications, it
may allow them to collect information such as logon IDs, passwords, and key exchanges
between systems.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the system is being used to perform a network troubleshooting function, the use of these
tools must be documented with the Information Systems Security Manager (ISSM) and restricted
to only authorized personnel.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-network_sniffer_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-network_sniffer_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Group id="network-kernel">
        <ns0:title xml:lang="en-US">Kernel Parameters Which Affect Networking</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">sysctl</html:code> utility is used to set
parameters which affect the operation of the Linux kernel. Kernel parameters
which affect networking and have security implications are described here.
</ns0:description>
        <ns0:Group id="network_host_parameters">
          <ns0:title xml:lang="en-US">Network Parameters for Hosts Only</ns0:title>
          <ns0:description xml:lang="en-US">If the system is not going to be used as a router, then setting certain
kernel parameters ensure that the host will not perform routing
of network traffic.</ns0:description>
          <ns0:Rule id="sysctl_net_ipv4_conf_default_send_redirects" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Disable Kernel Parameter for Sending ICMP Redirects by Default</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.send_redirects</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.default.send_redirects=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.send_redirects = 0</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.1.2</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages contain information
from the system's route table possibly revealing portions of the network topology.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The ability to send ICMP redirects is only appropriate for systems acting as routers.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_default_send_redirects" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">#
# Set runtime for net.ipv4.conf.default.send_redirects
#
/sbin/sysctl -q -n -w net.ipv4.conf.default.send_redirects=0

#
# If net.ipv4.conf.default.send_redirects present in /etc/sysctl.conf, change value to "0"
#	else, add "net.ipv4.conf.default.send_redirects = 0" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.default.send_redirects /etc/sysctl.conf ; then
	sed -i 's/^net.ipv4.conf.default.send_redirects.*/net.ipv4.conf.default.send_redirects = 0/g' /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.default.send_redirects to 0 per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.default.send_redirects = 0" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_default_send_redirects:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_default_send_redirects_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_conf_all_send_redirects" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Disable Kernel Parameter for Sending ICMP Redirects for All Interfaces</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.send_redirects</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.all.send_redirects=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.send_redirects = 0</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5(1)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.1.2</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">ICMP redirect messages are used by routers to inform hosts that a more
direct route exists for a particular destination. These messages contain information
from the system's route table possibly revealing portions of the network topology.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The ability to send ICMP redirects is only appropriate for systems acting as routers.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_all_send_redirects" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">#
# Set runtime for net.ipv4.conf.all.send_redirects
#
/sbin/sysctl -q -n -w net.ipv4.conf.all.send_redirects=0

#
# If net.ipv4.conf.all.send_redirects present in /etc/sysctl.conf, change value to "0"
#	else, add "net.ipv4.conf.all.send_redirects = 0" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.all.send_redirects /etc/sysctl.conf ; then
	sed -i 's/^net.ipv4.conf.all.send_redirects.*/net.ipv4.conf.all.send_redirects = 0/g' /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.all.send_redirects to 0 per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.all.send_redirects = 0" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_all_send_redirects:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_all_send_redirects_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_ip_forward" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Disable Kernel Parameter for IP Forwarding</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.ip_forward</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.ip_forward=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.ip_forward = 0</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-32</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.1.1</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">Routing protocol daemons are typically used on routers to exchange
network topology information with other routers. If this capability is used when
not required, system network information may be unnecessarily transmitted across
the network.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_ip_forward" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">#
# Set runtime for net.ipv4.ip_forward
#
/sbin/sysctl -q -n -w net.ipv4.ip_forward=0

#
# If net.ipv4.ip_forward present in /etc/sysctl.conf, change value to "0"
#	else, add "net.ipv4.ip_forward = 0" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.ip_forward /etc/sysctl.conf ; then
	sed -i 's/^net.ipv4.ip_forward.*/net.ipv4.ip_forward = 0/g' /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.ip_forward to 0 per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.ip_forward = 0" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_ip_forward:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_ip_forward_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="network_host_and_router_parameters">
          <ns0:title xml:lang="en-US">Network Related Kernel Runtime Parameters for Hosts and Routers</ns0:title>
          <ns0:description xml:lang="en-US">Certain kernel parameters should be set for systems which are
acting as either hosts or routers to improve the system's ability defend
against certain types of IPv4 protocol attacks.</ns0:description>
          <ns0:Value id="sysctl_net_ipv4_conf_all_accept_source_route_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.conf.all.accept_source_route</ns0:title>
            <ns0:description xml:lang="en-US">Trackers could be using source-routed packets to
generate traffic that seems to be intra-net, but actually was
created outside and has been redirected.</ns0:description>
            <ns0:value>0</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_conf_all_accept_redirects_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.conf.all.accept_redirects</ns0:title>
            <ns0:description xml:lang="en-US">Disable ICMP Redirect Acceptance</ns0:description>
            <ns0:value>0</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_conf_all_secure_redirects_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.conf.all.secure_redirects</ns0:title>
            <ns0:description xml:lang="en-US">Enable to prevent hijacking of routing path by only
allowing redirects from gateways known in routing
table.</ns0:description>
            <ns0:value>1</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_conf_default_log_martians_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.conf.default.log_martians</ns0:title>
            <ns0:description xml:lang="en-US">Disable so you don't Log Spoofed Packets, Source
Routed Packets, Redirect Packets</ns0:description>
            <ns0:value>1</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_conf_all_log_martians_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.conf.all.log_martians</ns0:title>
            <ns0:description xml:lang="en-US">Disable so you don't Log Spoofed Packets, Source
Routed Packets, Redirect Packets</ns0:description>
            <ns0:value>1</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_conf_default_accept_source_route_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.conf.default.accept_source_route</ns0:title>
            <ns0:description xml:lang="en-US">Disable IP source routing?</ns0:description>
            <ns0:value>0</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_conf_default_accept_redirects_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.conf.default.accept_redirects</ns0:title>
            <ns0:description xml:lang="en-US">Disable ICMP Redirect Acceptance?</ns0:description>
            <ns0:value>0</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_conf_default_secure_redirects_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.conf.default.secure_redirects</ns0:title>
            <ns0:description xml:lang="en-US">Log packets with impossible addresses to kernel
log?</ns0:description>
            <ns0:value>1</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.icmp_echo_ignore_broadcasts</ns0:title>
            <ns0:description xml:lang="en-US">Ignore all ICMP ECHO and TIMESTAMP requests sent to it
via broadcast/multicast</ns0:description>
            <ns0:value>1</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_icmp_ignore_bogus_error_responses_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.icmp_ignore_bogus_error_responses</ns0:title>
            <ns0:description xml:lang="en-US">Enable to prevent unnecessary logging</ns0:description>
            <ns0:value>1</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_tcp_syncookies_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.tcp_syncookies</ns0:title>
            <ns0:description xml:lang="en-US">Enable to turn on TCP SYN Cookie
Protection</ns0:description>
            <ns0:value>1</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_conf_all_rp_filter_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.conf.all.rp_filter</ns0:title>
            <ns0:description xml:lang="en-US">Enable to enforce sanity checking, also called ingress
filtering or egress filtering. The point is to drop a packet if the
source and destination IP addresses in the IP header do not make
sense when considered in light of the physical interface on which
it arrived.</ns0:description>
            <ns0:value>1</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Value id="sysctl_net_ipv4_conf_default_rp_filter_value" operator="equals" type="number">
            <ns0:title xml:lang="en-US">net.ipv4.conf.default.rp_filter</ns0:title>
            <ns0:description xml:lang="en-US">Enables source route verification</ns0:description>
            <ns0:value>1</ns0:value>
            <ns0:value selector="enabled">1</ns0:value>
            <ns0:value selector="disabled">0</ns0:value>
          </ns0:Value>
          <ns0:Rule id="sysctl_net_ipv4_conf_all_accept_source_route" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter for Accepting Source-Routed Packets for All Interfaces</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.accept_source_route</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.all.accept_source_route=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.accept_source_route = 0</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router, which can
be used to bypass network security measures. This requirement applies only to the
forwarding of source-routerd traffic, such as when IPv4 forwarding is enabled and 
the system is functioning as a router.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Accepting source-routed packets in the IPv4 protocol has few legitimate
uses. It should be disabled unless it is absolutely required.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_all_accept_source_route" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_conf_all_accept_source_route_value="<ns0:sub idref="sysctl_net_ipv4_conf_all_accept_source_route_value" />"

#
# Set runtime for net.ipv4.conf.all.accept_source_route
#
/sbin/sysctl -q -n -w net.ipv4.conf.all.accept_source_route=$sysctl_net_ipv4_conf_all_accept_source_route_value

#
# If net.ipv4.conf.all.accept_source_route present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.conf.all.accept_source_route = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.all.accept_source_route /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.conf.all.accept_source_route.*/net.ipv4.conf.all.accept_source_route = $sysctl_net_ipv4_conf_all_accept_source_route_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.all.accept_source_route to $sysctl_net_ipv4_conf_all_accept_source_route_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.all.accept_source_route = $sysctl_net_ipv4_conf_all_accept_source_route_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_conf_all_accept_source_route_value:var:1" value-id="sysctl_net_ipv4_conf_all_accept_source_route_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_all_accept_source_route:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_all_accept_source_route_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_conf_all_accept_redirects" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter for Accepting ICMP Redirects for All Interfaces</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.accept_redirects</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.all.accept_redirects=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.accept_redirects = 0</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1503</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1551</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.2</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">ICMP redirect messages are used by routers to inform hosts that a more direct
route exists for a particular destination. These messages modify the host's route table 
and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle
attack.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
This feature of the IPv4 protocol has few legitimate uses. It should be disabled unless 
absolutely required.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_all_accept_redirects" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_conf_all_accept_redirects_value="<ns0:sub idref="sysctl_net_ipv4_conf_all_accept_redirects_value" />"

#
# Set runtime for net.ipv4.conf.all.accept_redirects
#
/sbin/sysctl -q -n -w net.ipv4.conf.all.accept_redirects=$sysctl_net_ipv4_conf_all_accept_redirects_value

#
# If net.ipv4.conf.all.accept_redirects present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.conf.all.accept_redirects = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.all.accept_redirects /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.conf.all.accept_redirects.*/net.ipv4.conf.all.accept_redirects = $sysctl_net_ipv4_conf_all_accept_redirects_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.all.accept_redirects to $sysctl_net_ipv4_conf_all_accept_redirects_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.all.accept_redirects = $sysctl_net_ipv4_conf_all_accept_redirects_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_conf_all_accept_redirects_value:var:1" value-id="sysctl_net_ipv4_conf_all_accept_redirects_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_all_accept_redirects:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_all_accept_redirects_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_conf_all_secure_redirects" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter for Accepting Secure Redirects for All Interfaces</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.secure_redirects</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.all.secure_redirects=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.secure_redirects = 0</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1503</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1551</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.3</ns0:reference>
            <ns0:rationale xml:lang="en-US">Accepting "secure" ICMP redirects (from those gateways listed as
default gateways) has few legitimate uses. It should be disabled unless it is
absolutely required.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_all_secure_redirects" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_conf_all_secure_redirects_value="<ns0:sub idref="sysctl_net_ipv4_conf_all_secure_redirects_value" />"

#
# Set runtime for net.ipv4.conf.all.secure_redirects
#
/sbin/sysctl -q -n -w net.ipv4.conf.all.secure_redirects=$sysctl_net_ipv4_conf_all_secure_redirects_value

#
# If net.ipv4.conf.all.secure_redirects present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.conf.all.secure_redirects = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.all.secure_redirects /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.conf.all.secure_redirects.*/net.ipv4.conf.all.secure_redirects = $sysctl_net_ipv4_conf_all_secure_redirects_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.all.secure_redirects to $sysctl_net_ipv4_conf_all_secure_redirects_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.all.secure_redirects = $sysctl_net_ipv4_conf_all_secure_redirects_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_conf_all_secure_redirects_value:var:1" value-id="sysctl_net_ipv4_conf_all_secure_redirects_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_all_secure_redirects:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_all_secure_redirects_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_conf_all_log_martians" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter to Log Martian Packets</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.log_martians</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.all.log_martians=1</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.log_martians = 1</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5(3)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.4</ns0:reference>
            <ns0:rationale xml:lang="en-US">The presence of "martian" packets (which have impossible addresses)
as well as spoofed packets, source-routed packets, and redirects could be a
sign of nefarious network activity. Logging these packets enables this activity
to be detected.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_all_log_martians" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_conf_all_log_martians_value="<ns0:sub idref="sysctl_net_ipv4_conf_all_log_martians_value" />"

#
# Set runtime for net.ipv4.conf.all.log_martians
#
/sbin/sysctl -q -n -w net.ipv4.conf.all.log_martians=$sysctl_net_ipv4_conf_all_log_martians_value

#
# If net.ipv4.conf.all.log_martians present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.conf.all.log_martians = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.all.log_martians /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.conf.all.log_martians.*/net.ipv4.conf.all.log_martians = $sysctl_net_ipv4_conf_all_log_martians_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.all.log_martians to $sysctl_net_ipv4_conf_all_log_martians_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.all.log_martians = $sysctl_net_ipv4_conf_all_log_martians_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_conf_all_log_martians_value:var:1" value-id="sysctl_net_ipv4_conf_all_log_martians_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_all_log_martians:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_all_log_martians_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_conf_default_log_martians" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter to Log Martian Packets By Default</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.log_martians</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.default.log_martians=1</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.log_martians = 1</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5(3)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.4</ns0:reference>
            <ns0:rationale xml:lang="en-US">The presence of "martian" packets (which have impossible addresses)
as well as spoofed packets, source-routed packets, and redirects could be a
sign of nefarious network activity. Logging these packets enables this activity
to be detected.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_default_log_martians" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_conf_default_log_martians_value="<ns0:sub idref="sysctl_net_ipv4_conf_default_log_martians_value" />"

#
# Set runtime for net.ipv4.conf.default.log_martians
#
/sbin/sysctl -q -n -w net.ipv4.conf.default.log_martians=$sysctl_net_ipv4_conf_default_log_martians_value

#
# If net.ipv4.conf.default.log_martians present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.conf.default.log_martians = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.default.log_martians /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.conf.default.log_martians.*/net.ipv4.conf.default.log_martians = $sysctl_net_ipv4_conf_default_log_martians_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.default.log_martians to $sysctl_net_ipv4_conf_default_log_martians_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.default.log_martians = $sysctl_net_ipv4_conf_default_log_martians_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_conf_default_log_martians_value:var:1" value-id="sysctl_net_ipv4_conf_default_log_martians_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_default_log_martians:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_default_log_martians_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_conf_default_accept_source_route" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter for Accepting Source-Routed Packets By Default</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.accept_source_route</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.default.accept_source_route=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.accept_source_route = 0</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1551</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">Source-routed packates allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router, which can 
be used to bypass network security measures.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Accepting source-routed packets in the IPv4 protocol has few legitimate
uses. It should be disabled unless it is absolutely required, such as when
IPv4 forwarding is enabled and the system is legitimately functioning as
a router.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_default_accept_source_route" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_conf_default_accept_source_route_value="<ns0:sub idref="sysctl_net_ipv4_conf_default_accept_source_route_value" />"

#
# Set runtime for net.ipv4.conf.default.accept_source_route
#
/sbin/sysctl -q -n -w net.ipv4.conf.default.accept_source_route=$sysctl_net_ipv4_conf_default_accept_source_route_value

#
# If net.ipv4.conf.default.accept_source_route present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.conf.default.accept_source_route = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.default.accept_source_route /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.conf.default.accept_source_route.*/net.ipv4.conf.default.accept_source_route = $sysctl_net_ipv4_conf_default_accept_source_route_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.default.accept_source_route to $sysctl_net_ipv4_conf_default_accept_source_route_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.default.accept_source_route = $sysctl_net_ipv4_conf_default_accept_source_route_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_conf_default_accept_source_route_value:var:1" value-id="sysctl_net_ipv4_conf_default_accept_source_route_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_default_accept_source_route:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_default_accept_source_route_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_conf_default_accept_redirects" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter for Accepting ICMP Redirects By Default</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.accept_redirects</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.default.accept_redirects=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.accept_redirects = 0</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1551</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.2</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">ICMP redirect messages are used by routers to inform hosts that a more direct
route exists for a particular destination. These messages modify the host's route table
and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle
attack.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
This feature of the IPv4 protocol has few legitimate uses. It should be disabled unless 
absolutely required.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_default_accept_redirects" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_conf_default_accept_redirects_value="<ns0:sub idref="sysctl_net_ipv4_conf_default_accept_redirects_value" />"

#
# Set runtime for net.ipv4.conf.default.accept_redirects
#
/sbin/sysctl -q -n -w net.ipv4.conf.default.accept_redirects=$sysctl_net_ipv4_conf_default_accept_redirects_value

#
# If net.ipv4.conf.default.accept_redirects present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.conf.default.accept_redirects = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.default.accept_redirects /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.conf.default.accept_redirects.*/net.ipv4.conf.default.accept_redirects = $sysctl_net_ipv4_conf_default_accept_redirects_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.default.accept_redirects to $sysctl_net_ipv4_conf_default_accept_redirects_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.default.accept_redirects = $sysctl_net_ipv4_conf_default_accept_redirects_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_conf_default_accept_redirects_value:var:1" value-id="sysctl_net_ipv4_conf_default_accept_redirects_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_default_accept_redirects:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_default_accept_redirects_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_conf_default_secure_redirects" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter for Accepting Secure Redirects By Default</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.secure_redirects</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.default.secure_redirects=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.secure_redirects = 0</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1551</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.3</ns0:reference>
            <ns0:rationale xml:lang="en-US">Accepting "secure" ICMP redirects (from those gateways listed as
default gateways) has few legitimate uses. It should be disabled unless it is
absolutely required.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_default_secure_redirects" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_conf_default_secure_redirects_value="<ns0:sub idref="sysctl_net_ipv4_conf_default_secure_redirects_value" />"

#
# Set runtime for net.ipv4.conf.default.secure_redirects
#
/sbin/sysctl -q -n -w net.ipv4.conf.default.secure_redirects=$sysctl_net_ipv4_conf_default_secure_redirects_value

#
# If net.ipv4.conf.default.secure_redirects present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.conf.default.secure_redirects = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.default.secure_redirects /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.conf.default.secure_redirects.*/net.ipv4.conf.default.secure_redirects = $sysctl_net_ipv4_conf_default_secure_redirects_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.default.secure_redirects to $sysctl_net_ipv4_conf_default_secure_redirects_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.default.secure_redirects = $sysctl_net_ipv4_conf_default_secure_redirects_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_conf_default_secure_redirects_value:var:1" value-id="sysctl_net_ipv4_conf_default_secure_redirects_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_default_secure_redirects:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_default_secure_redirects_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_icmp_echo_ignore_broadcasts" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter to Ignore ICMP Broadcast Echo Requests</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.icmp_echo_ignore_broadcasts</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.icmp_echo_ignore_broadcasts = 1</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.5</ns0:reference>
            <ns0:rationale xml:lang="en-US">Responding to broadcast (ICMP) echoes facilitates network mapping
and provides a vector for amplification attacks.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Ignoring ICMP echo requests (pings) sent to broadcast or multicast
addresses makes the system slightly more difficult to enumerate on the network.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_icmp_echo_ignore_broadcasts" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value="<ns0:sub idref="sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value" />"

#
# Set runtime for net.ipv4.icmp_echo_ignore_broadcasts
#
/sbin/sysctl -q -n -w net.ipv4.icmp_echo_ignore_broadcasts=$sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value

#
# If net.ipv4.icmp_echo_ignore_broadcasts present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.icmp_echo_ignore_broadcasts = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.icmp_echo_ignore_broadcasts /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.icmp_echo_ignore_broadcasts.*/net.ipv4.icmp_echo_ignore_broadcasts = $sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.icmp_echo_ignore_broadcasts to $sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.icmp_echo_ignore_broadcasts = $sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value:var:1" value-id="sysctl_net_ipv4_icmp_echo_ignore_broadcasts_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_icmp_echo_ignore_broadcasts:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_icmp_echo_ignore_broadcasts_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_icmp_ignore_bogus_error_responses" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter to Ignore Bogus ICMP Error Responses</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.icmp_ignore_bogus_error_responses</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.icmp_ignore_bogus_error_responses = 1</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.6</ns0:reference>
            <ns0:rationale xml:lang="en-US">Ignoring bogus ICMP error responses reduces
log size, although some activity would not be logged.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_icmp_ignore_bogus_error_responses" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_icmp_ignore_bogus_error_responses_value="<ns0:sub idref="sysctl_net_ipv4_icmp_ignore_bogus_error_responses_value" />"

#
# Set runtime for net.ipv4.icmp_ignore_bogus_error_responses
#
/sbin/sysctl -q -n -w net.ipv4.icmp_ignore_bogus_error_responses=$sysctl_net_ipv4_icmp_ignore_bogus_error_responses_value

#
# If net.ipv4.icmp_ignore_bogus_error_responses present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.icmp_ignore_bogus_error_responses = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.icmp_ignore_bogus_error_responses /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.icmp_ignore_bogus_error_responses.*/net.ipv4.icmp_ignore_bogus_error_responses = $sysctl_net_ipv4_icmp_ignore_bogus_error_responses_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.icmp_ignore_bogus_error_responses to $sysctl_net_ipv4_icmp_ignore_bogus_error_responses_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.icmp_ignore_bogus_error_responses = $sysctl_net_ipv4_icmp_ignore_bogus_error_responses_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_icmp_ignore_bogus_error_responses_value:var:1" value-id="sysctl_net_ipv4_icmp_ignore_bogus_error_responses_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_icmp_ignore_bogus_error_responses:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_icmp_ignore_bogus_error_responses_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_tcp_syncookies" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter to Use TCP Syncookies</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.tcp_syncookies</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.tcp_syncookies=1</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.tcp_syncookies = 1</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5(1)(2)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5(2)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5(3)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.8</ns0:reference>
            <ns0:rationale xml:lang="en-US"> A TCP SYN flood attack can cause a denial of service by filling a
system's TCP connection table with connections in the SYN_RCVD state.
Syncookies can be used to track a connection when a subsequent ACK is received,
verifying the initiator is attempting a valid connection and is not a flood
source. This feature is activated when a flood condition is detected, and
enables the system to continue servicing valid connection requests.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_tcp_syncookies" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_tcp_syncookies_value="<ns0:sub idref="sysctl_net_ipv4_tcp_syncookies_value" />"

#
# Set runtime for net.ipv4.tcp_syncookies
#
/sbin/sysctl -q -n -w net.ipv4.tcp_syncookies=$sysctl_net_ipv4_tcp_syncookies_value

#
# If net.ipv4.tcp_syncookies present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.tcp_syncookies = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.tcp_syncookies /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.tcp_syncookies.*/net.ipv4.tcp_syncookies = $sysctl_net_ipv4_tcp_syncookies_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.tcp_syncookies to $sysctl_net_ipv4_tcp_syncookies_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.tcp_syncookies = $sysctl_net_ipv4_tcp_syncookies_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_tcp_syncookies_value:var:1" value-id="sysctl_net_ipv4_tcp_syncookies_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_tcp_syncookies:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_tcp_syncookies_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_conf_all_rp_filter" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter to Use Reverse Path Filtering for All Interfaces</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.rp_filter</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.all.rp_filter=1</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.all.rp_filter = 1</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1551</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.7</ns0:reference>
            <ns0:rationale xml:lang="en-US">Enabling reverse path filtering drops packets with source addresses
that should not have been able to be received on the interface they were
received on. It should not be used on systems which are routers for
complicated networks, but is helpful for end hosts and routers serving small
networks.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_all_rp_filter" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_conf_all_rp_filter_value="<ns0:sub idref="sysctl_net_ipv4_conf_all_rp_filter_value" />"

#
# Set runtime for net.ipv4.conf.all.rp_filter
#
/sbin/sysctl -q -n -w net.ipv4.conf.all.rp_filter=$sysctl_net_ipv4_conf_all_rp_filter_value

#
# If net.ipv4.conf.all.rp_filter present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.conf.all.rp_filter = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.all.rp_filter /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.conf.all.rp_filter.*/net.ipv4.conf.all.rp_filter = $sysctl_net_ipv4_conf_all_rp_filter_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.all.rp_filter to $sysctl_net_ipv4_conf_all_rp_filter_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.all.rp_filter = $sysctl_net_ipv4_conf_all_rp_filter_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_conf_all_rp_filter_value:var:1" value-id="sysctl_net_ipv4_conf_all_rp_filter_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_all_rp_filter:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_all_rp_filter_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="sysctl_net_ipv4_conf_default_rp_filter" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure Kernel Parameter to Use Reverse Path Filtering by Default</ns0:title>
            <ns0:description xml:lang="en-US">
              
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.rp_filter</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv4.conf.default.rp_filter=1</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv4.conf.default.rp_filter = 1</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-7</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.2.7</ns0:reference>
            <ns0:rationale xml:lang="en-US">Enabling reverse path filtering drops packets with source addresses
that should not have been able to be received on the interface they were
received on. It should not be used on systems which are routers for
complicated networks, but is helpful for end hosts and routers serving small
networks.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv4_conf_default_rp_filter" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv4_conf_default_rp_filter_value="<ns0:sub idref="sysctl_net_ipv4_conf_default_rp_filter_value" />"

#
# Set runtime for net.ipv4.conf.default.rp_filter
#
/sbin/sysctl -q -n -w net.ipv4.conf.default.rp_filter=$sysctl_net_ipv4_conf_default_rp_filter_value

#
# If net.ipv4.conf.default.rp_filter present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv4.conf.default.rp_filter = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv4.conf.default.rp_filter /etc/sysctl.conf ; then
	sed -i "s/^net.ipv4.conf.default.rp_filter.*/net.ipv4.conf.default.rp_filter = $sysctl_net_ipv4_conf_default_rp_filter_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv4.conf.default.rp_filter to $sysctl_net_ipv4_conf_default_rp_filter_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv4.conf.default.rp_filter = $sysctl_net_ipv4_conf_default_rp_filter_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-export export-name="oval:ssg-sysctl_net_ipv4_conf_default_rp_filter_value:var:1" value-id="sysctl_net_ipv4_conf_default_rp_filter_value" />
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv4_conf_default_rp_filter:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv4_conf_default_rp_filter_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="network-wireless">
        <ns0:title xml:lang="en-US">Wireless Networking</ns0:title>
        <ns0:description xml:lang="en-US">Wireless networking, such as 802.11
(WiFi) and Bluetooth, can present a security risk to sensitive or
classified systems and networks. Wireless networking hardware is
much more likely to be included in laptop or portable systems than
in desktops or servers. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Removal of hardware provides the greatest assurance that the wireless
capability remains disabled. Acquisition policies often include provisions to
prevent the purchase of equipment that will be used in sensitive spaces and
includes wireless capabilities. If it is impractical to remove the wireless
hardware, and policy permits the device to enter sensitive spaces as long
as wireless is disabled, efforts should instead focus on disabling wireless capability
via software.</ns0:description>
        <ns0:Group id="wireless_software">
          <ns0:title xml:lang="en-US">Disable Wireless Through Software Configuration</ns0:title>
          <ns0:description xml:lang="en-US">If it is impossible to remove the wireless hardware
from the device in question, disable as much of it as possible
through software. The following methods can disable software
support for wireless networking, but note that these methods do not
prevent malicious software or careless users from re-activating the
devices.</ns0:description>
          <ns0:Rule id="wireless_disable_in_bios" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable WiFi or Bluetooth in BIOS</ns0:title>
            <ns0:description xml:lang="en-US">Some systems that include built-in wireless support offer the
ability to disable the device through the BIOS. This is system-specific;
consult your hardware manual or explore the BIOS setup during
boot.</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(3)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">85</ns0:reference>
            <ns0:rationale xml:lang="en-US">Disabling wireless support in the BIOS prevents easy
activation of the wireless interface, generally requiring administrators
to reboot the system first.
</ns0:rationale>
            </ns0:Rule>
          <ns0:Rule id="wireless_disable_interfaces" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Deactivate Wireless Network Interfaces</ns0:title>
            <ns0:description xml:lang="en-US">Deactivating wireless network interfaces should prevent
normal usage of the wireless capability.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
First, identify the interfaces available with the command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ ifconfig -a</html:pre>
Additionally, the following command may be used to
determine whether wireless support is included for a
particular interface, though this may not always be a clear
indicator:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ iwconfig</html:pre>
After identifying any wireless interfaces (which may have
names like <html:code xmlns:html="http://www.w3.org/1999/xhtml">wlan0</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">ath0</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">wifi0</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">em1</html:code> or
<html:code xmlns:html="http://www.w3.org/1999/xhtml">eth0</html:code>), deactivate the interface with the command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo ifdown <html:i>interface</html:i></html:pre>
These changes will only last until the next reboot. To
disable the interface for future boots, remove the appropriate
interface file from <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/network-scripts</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo rm /etc/sysconfig/network-scripts/ifcfg-<html:i>interface</html:i></html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(3)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">85</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.3.1</ns0:reference>
            <ns0:rationale xml:lang="en-US">Wireless networking allows attackers within physical proximity to
launch network-based attacks against systems, including those against local LAN
protocols which were not designed with security in mind.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-wireless_disable_interfaces:def:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="service_bluetooth_disabled" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Disable Bluetooth Service</ns0:title>
            <ns0:description xml:lang="en-US">
              
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">bluetooth</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable bluetooth.service</html:pre>
              <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo service bluetooth stop</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(3)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">85</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1551</ns0:reference>
            <ns0:rationale xml:lang="en-US">Disabling the <html:code xmlns:html="http://www.w3.org/1999/xhtml">bluetooth</html:code> service prevents the system from attempting
connections to Bluetooth devices, which entails some security risk.
Nevertheless, variation in this risk decision may be expected due to the
utility of Bluetooth connectivity and its limited range.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="service_bluetooth_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">grep -qi disable /etc/xinetd.d/bluetooth &amp;&amp; \
	sed -i 's/disable.*/disable	= yes/gI' /etc/xinetd.d/bluetooth
#
# Disable bluetooth.service for all systemd targets
#
systemctl disable bluetooth.service

#
# Stop bluetooth.service if currently running
#
systemctl stop bluetooth.service
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_bluetooth_disabled:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_bluetooth_disabled_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="kernel_module_bluetooth_disabled" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Disable Bluetooth Kernel Modules</ns0:title>
            <ns0:description xml:lang="en-US">The kernel's module loading system can be configured to prevent
loading of the Bluetooth module. Add the following to
the appropriate <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code> configuration file
to prevent the loading of the Bluetooth module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">install bluetooth /bin/true</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-18(3)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">85</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1551</ns0:reference>
            <ns0:rationale xml:lang="en-US">If Bluetooth functionality must be disabled, preventing the kernel
from loading the kernel module provides an additional safeguard against its
activation.</ns0:rationale>
            <ns0:fix complexity="low" disruption="medium" id="kernel_module_bluetooth_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">if grep --silent "^install bluetooth" /etc/modprobe.d/bluetooth.conf ; then
        sed -i 's/^install bluetooth.*/install bluetooth /bin/true/g' /etc/modprobe.d/bluetooth.conf
else
        echo -e "\n# Disable per security requirements" &gt;&gt; /etc/modprobe.d/bluetooth.conf
        echo "install bluetooth /bin/true" &gt;&gt; /etc/modprobe.d/bluetooth.conf
fi
</ns0:fix>
            <ns0:fix complexity="low" disruption="medium" id="kernel_module_bluetooth_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure kernel module 'bluetooth' is disabled
  lineinfile:
    create=yes
    dest="/etc/modprobe.d/{{item}}.conf"
    regexp="{{item}}"
    line="install {{item}} /bin/true"
  with_items:
    - bluetooth
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-kernel_module_bluetooth_disabled:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-kernel_module_bluetooth_disabled_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="network-ipv6">
        <ns0:title xml:lang="en-US">IPv6</ns0:title>
        <ns0:description xml:lang="en-US">The system includes support for Internet Protocol
version 6. A major and often-mentioned improvement over IPv4 is its
enormous increase in the number of available addresses. Another
important feature is its support for automatic configuration of
many network settings.</ns0:description>
        <ns0:Group id="disabling_ipv6">
          <ns0:title xml:lang="en-US">Disable Support for IPv6 Unless Needed</ns0:title>
          <ns0:description xml:lang="en-US">
Despite configuration that suggests support for IPv6 has
been disabled, link-local IPv6 address auto-configuration occurs
even when only an IPv4 address is assigned. The only way to
effectively prevent execution of the IPv6 networking stack is to
instruct the system not to activate the IPv6 kernel module.
</ns0:description>
          <ns0:Rule id="sysctl_kernel_ipv6_disable" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Disable IPv6 Networking Support Automatic Loading</ns0:title>
            <ns0:description xml:lang="en-US">To disable support for (<html:code xmlns:html="http://www.w3.org/1999/xhtml">ipv6</html:code>) add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.d/ipv6.conf</html:code> (or another file in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.d</html:code>):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.all.disable_ipv6 = 1</html:pre>
This disables IPv6 on all network interfaces as other services and system
functionality require the IPv6 stack loaded to work.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1551</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.4.2</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Any unnecessary network stacks - including IPv6 - should be disabled, to reduce
the vulnerability to exploitation.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_kernel_ipv6_disable:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_kernel_ipv6_disable_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="network_ipv6_disable_interfaces" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable Interface Usage of IPv6</ns0:title>
            <ns0:description xml:lang="en-US">To disable interface usage of IPv6, add or correct the following lines in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/network</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">NETWORKING_IPV6=no
IPV6INIT=no</html:pre>
</ns0:description>
            </ns0:Rule>
          <ns0:Rule id="network_ipv6_disable_rpc" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable Support for RPC IPv6</ns0:title>
            <ns0:description xml:lang="en-US">RPC services for NFSv4 try to load transport modules for
<html:code xmlns:html="http://www.w3.org/1999/xhtml">udp6</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">tcp6</html:code> by default, even if IPv6 has been disabled in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>. To prevent RPC services such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">rpc.mountd</html:code>
from attempting to start IPv6 network listeners, remove or comment out the
following two lines in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/netconfig</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-network_ipv6_disable_rpc:def:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="configuring_ipv6">
          <ns0:title xml:lang="en-US">Configure IPv6 Settings if Necessary</ns0:title>
          <ns0:description xml:lang="en-US">A major feature of IPv6 is the extent to which systems
implementing it can automatically configure their networking
devices using information from the network. From a security
perspective, manually configuring important configuration
information is preferable to accepting it from the network
in an unauthenticated fashion.</ns0:description>
          <ns0:Group id="disabling_ipv6_autoconfig">
            <ns0:title xml:lang="en-US">Disable Automatic Configuration</ns0:title>
            <ns0:description xml:lang="en-US">Disable the system's acceptance of router
advertisements and redirects by adding or correcting the following
line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/network</html:code> (note that this does not disable
sending router solicitations):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">IPV6_AUTOCONF=no</html:pre>
</ns0:description>
            <ns0:Value id="sysconfig_network_IPV6_AUTOCONF_value" operator="equals" type="string">
              <ns0:title xml:lang="en-US">IPV6_AUTOCONF</ns0:title>
              <ns0:description xml:lang="en-US">Toggle global IPv6 auto-configuration (only, if global
forwarding is disabled)</ns0:description>
              <ns0:value>no</ns0:value>
              <ns0:value selector="enabled">yes</ns0:value>
              <ns0:value selector="disabled">no</ns0:value>
            </ns0:Value>
            <ns0:Value id="sysctl_net_ipv6_conf_all_accept_source_route_value" operator="equals" type="number">
              <ns0:title xml:lang="en-US">net.ipv6.conf.all.accept_source_route</ns0:title>
              <ns0:description xml:lang="en-US">Trackers could be using source-routed packets to
generate traffic that seems to be intra-net, but actually was
created outside and has been redirected.</ns0:description>
              <ns0:value>0</ns0:value>
              <ns0:value selector="enabled">1</ns0:value>
              <ns0:value selector="disabled">0</ns0:value>
            </ns0:Value>
            <ns0:Value id="sysctl_net_ipv6_conf_default_accept_ra_value" operator="equals" type="number">
              <ns0:title xml:lang="en-US">net.ipv6.conf.default.accept_ra</ns0:title>
              <ns0:description xml:lang="en-US">Accept default router advertisements by default?</ns0:description>
              <ns0:value>0</ns0:value>
              <ns0:value selector="enabled">1</ns0:value>
              <ns0:value selector="disabled">0</ns0:value>
            </ns0:Value>
            <ns0:Value id="sysctl_net_ipv6_conf_all_accept_ra_value" operator="equals" type="number">
              <ns0:title xml:lang="en-US">net.ipv6.conf.all.accept_ra</ns0:title>
              <ns0:description xml:lang="en-US">Accept all router advertisements?</ns0:description>
              <ns0:value>0</ns0:value>
              <ns0:value selector="enabled">1</ns0:value>
              <ns0:value selector="disabled">0</ns0:value>
            </ns0:Value>
            <ns0:Value id="sysctl_net_ipv6_conf_default_accept_redirects_value" operator="equals" type="number">
              <ns0:title xml:lang="en-US">net.ipv6.conf.default.accept_redirects</ns0:title>
              <ns0:description xml:lang="en-US">Toggle ICMP Redirect Acceptance By Default</ns0:description>
              <ns0:value>0</ns0:value>
              <ns0:value selector="enabled">1</ns0:value>
              <ns0:value selector="disabled">0</ns0:value>
            </ns0:Value>
            <ns0:Value id="sysctl_net_ipv6_conf_all_accept_redirects_value" operator="equals" type="number">
              <ns0:title xml:lang="en-US">net.ipv6.conf.all.accept_redirects</ns0:title>
              <ns0:description xml:lang="en-US">Toggle ICMP Redirect Acceptance</ns0:description>
              <ns0:value>0</ns0:value>
              <ns0:value selector="enabled">1</ns0:value>
              <ns0:value selector="disabled">0</ns0:value>
            </ns0:Value>
            <ns0:Value id="sysctl_net_ipv6_conf_default_accept_source_route_value" operator="equals" type="number">
              <ns0:title xml:lang="en-US">net.ipv6.conf.default.accept_source_route</ns0:title>
              <ns0:description xml:lang="en-US">Trackers could be using source-routed packets to
generate traffic that seems to be intra-net, but actually was
created outside and has been redirected.</ns0:description>
              <ns0:value>0</ns0:value>
              <ns0:value selector="enabled">1</ns0:value>
              <ns0:value selector="disabled">0</ns0:value>
            </ns0:Value>
            <ns0:Value id="sysctl_net_ipv6_conf_all_forwarding_value" operator="equals" type="number">
              <ns0:title xml:lang="en-US">net.ipv6.conf.all.forwarding</ns0:title>
              <ns0:description xml:lang="en-US">Toggle IPv6 Forwarding</ns0:description>
              <ns0:value>0</ns0:value>
              <ns0:value selector="enabled">1</ns0:value>
              <ns0:value selector="disabled">0</ns0:value>
            </ns0:Value>
            <ns0:Rule id="sysctl_net_ipv6_conf_all_accept_source_route" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Configure Kernel Parameter for Accepting Source-Routed Packets for All Interfaces</ns0:title>
              <ns0:description xml:lang="en-US">
                
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.all.accept_source_route</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv6.conf.all.accept_source_route=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.all.accept_source_route = 0</html:pre>
              </ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
              <ns0:rationale xml:lang="en-US">Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router, which can
be used to bypass network security measures. This requirement applies only to the
forwarding of source-routerd traffic, such as when IPv6 forwarding is enabled and
the system is functioning as a router.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Accepting source-routed packets in the IPv6 protocol has few legitimate
uses. It should be disabled unless it is absolutely required.</ns0:rationale>
              <ns0:fix complexity="low" disruption="low" id="sysctl_net_ipv6_conf_all_accept_source_route" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">#
# Set runtime for SYSCTLVAR
#
/sbin/sysctl -q -n -w net.ipv6.conf.all.accept_source_route=0

#
# If SYSCTLVAR present in /etc/sysctl.conf, change value to "SYSCTLVAL"
#	else, add "SYSCTLVAR = SYSCTLVAL" to /etc/sysctl.conf
#
if grep --silent ^net.ipv6.conf.all.accept_source_route /etc/sysctl.conf ; then
	sed -i 's/^net.ipv6.conf.all.accept_source_route.*/net.ipv6.conf.all.accept_source_route = 0/g' /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv6.conf.all.accept_source_route to 0 per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv6.conf.all.accept_source_route = 0" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-sysctl_net_ipv6_conf_all_accept_source_route_value:var:1" value-id="sysctl_net_ipv6_conf_all_accept_source_route_value" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv6_conf_all_accept_source_route:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv6_conf_all_accept_source_route_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="sysctl_net_ipv6_conf_all_accept_ra" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Configure Accepting IPv6 Router Advertisements</ns0:title>
              <ns0:description xml:lang="en-US">
                
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.all.accept_ra</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv6.conf.all.accept_ra=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.all.accept_ra = 0</html:pre>
              </ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.4.1.1</ns0:reference>
              <ns0:rationale xml:lang="en-US">
An illicit router advertisement message could result in a man-in-the-middle attack.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv6_conf_all_accept_ra" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv6_conf_all_accept_ra_value="<ns0:sub idref="sysctl_net_ipv6_conf_all_accept_ra_value" />"

#
# Set runtime for net.ipv6.conf.all.accept_ra
#
/sbin/sysctl -q -n -w net.ipv6.conf.all.accept_ra=$sysctl_net_ipv6_conf_all_accept_ra_value

#
# If net.ipv6.conf.all.accept_ra present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv6.conf.all.accept_ra = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv6.conf.all.accept_ra /etc/sysctl.conf ; then
	sed -i "s/^net.ipv6.conf.all.accept_ra.*/net.ipv6.conf.all.accept_ra = $sysctl_net_ipv6_conf_all_accept_ra_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv6.conf.all.accept_ra to $sysctl_net_ipv6_conf_all_accept_ra_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv6.conf.all.accept_ra = $sysctl_net_ipv6_conf_all_accept_ra_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-sysctl_net_ipv6_conf_all_accept_ra_value:var:1" value-id="sysctl_net_ipv6_conf_all_accept_ra_value" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv6_conf_all_accept_ra:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv6_conf_all_accept_ra_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="sysctl_net_ipv6_conf_default_accept_ra" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Configure Accepting IPv6 Router Advertisements</ns0:title>
              <ns0:description xml:lang="en-US">
                
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.default.accept_ra</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv6.conf.default.accept_ra=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.default.accept_ra = 0</html:pre>
              </ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.4.1.1</ns0:reference>
              <ns0:rationale xml:lang="en-US">
An illicit router advertisement message could result in a man-in-the-middle attack.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv6_conf_default_accept_ra" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv6_conf_default_accept_ra_value="<ns0:sub idref="sysctl_net_ipv6_conf_default_accept_ra_value" />"

#
# Set runtime for net.ipv6.conf.default.accept_ra
#
/sbin/sysctl -q -n -w net.ipv6.conf.default.accept_ra=$sysctl_net_ipv6_conf_default_accept_ra_value

#
# If net.ipv6.conf.default.accept_ra present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv6.conf.default.accept_ra = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv6.conf.default.accept_ra /etc/sysctl.conf ; then
	sed -i "s/^net.ipv6.conf.default.accept_ra.*/net.ipv6.conf.default.accept_ra = $sysctl_net_ipv6_conf_default_accept_ra_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv6.conf.default.accept_ra to $sysctl_net_ipv6_conf_default_accept_ra_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv6.conf.default.accept_ra = $sysctl_net_ipv6_conf_default_accept_ra_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-sysctl_net_ipv6_conf_default_accept_ra_value:var:1" value-id="sysctl_net_ipv6_conf_default_accept_ra_value" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv6_conf_default_accept_ra:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv6_conf_default_accept_ra_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="sysctl_net_ipv6_conf_all_accept_redirects" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Configure Accepting IPv6 Redirects By Default</ns0:title>
              <ns0:description xml:lang="en-US">
                
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.all.accept_redirects</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv6.conf.all.accept_redirects=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.all.accept_redirects = 0</html:pre>
              </ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1551</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.4.1.2</ns0:reference>
              <ns0:rationale xml:lang="en-US">
An illicit ICMP redirect message could result in a man-in-the-middle attack.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv6_conf_all_accept_redirects" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv6_conf_all_accept_redirects_value="<ns0:sub idref="sysctl_net_ipv6_conf_all_accept_redirects_value" />"

#
# Set runtime for net.ipv6.conf.all.accept_redirects
#
/sbin/sysctl -q -n -w net.ipv6.conf.all.accept_redirects=$sysctl_net_ipv6_conf_all_accept_redirects_value

#
# If net.ipv6.conf.all.accept_redirects present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv6.conf.all.accept_redirects = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv6.conf.all.accept_redirects /etc/sysctl.conf ; then
	sed -i "s/^net.ipv6.conf.all.accept_redirects.*/net.ipv6.conf.all.accept_redirects = $sysctl_net_ipv6_conf_all_accept_redirects_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv6.conf.all.accept_redirects to $sysctl_net_ipv6_conf_all_accept_redirects_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv6.conf.all.accept_redirects = $sysctl_net_ipv6_conf_all_accept_redirects_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-sysctl_net_ipv6_conf_all_accept_redirects_value:var:1" value-id="sysctl_net_ipv6_conf_all_accept_redirects_value" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv6_conf_all_accept_redirects:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv6_conf_all_accept_redirects_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="sysctl_net_ipv6_conf_default_accept_redirects" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Configure Accepting IPv6 Redirects By Default</ns0:title>
              <ns0:description xml:lang="en-US">
                
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.default.accept_redirects</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv6.conf.default.accept_redirects=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.default.accept_redirects = 0</html:pre>
              </ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1551</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.4.1.2</ns0:reference>
              <ns0:rationale xml:lang="en-US">
An illicit ICMP redirect message could result in a man-in-the-middle attack.
</ns0:rationale>
              <ns0:fix complexity="low" disruption="medium" id="sysctl_net_ipv6_conf_default_accept_redirects" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">
sysctl_net_ipv6_conf_default_accept_redirects_value="<ns0:sub idref="sysctl_net_ipv6_conf_default_accept_redirects_value" />"

#
# Set runtime for net.ipv6.conf.default.accept_redirects
#
/sbin/sysctl -q -n -w net.ipv6.conf.default.accept_redirects=$sysctl_net_ipv6_conf_default_accept_redirects_value

#
# If net.ipv6.conf.default.accept_redirects present in /etc/sysctl.conf, change value to appropriate value
#	else, add "net.ipv6.conf.default.accept_redirects = value" to /etc/sysctl.conf
#
if grep --silent ^net.ipv6.conf.default.accept_redirects /etc/sysctl.conf ; then
	sed -i "s/^net.ipv6.conf.default.accept_redirects.*/net.ipv6.conf.default.accept_redirects = $sysctl_net_ipv6_conf_default_accept_redirects_value/g" /etc/sysctl.conf
else
	echo -e "\n# Set net.ipv6.conf.default.accept_redirects to $sysctl_net_ipv6_conf_default_accept_redirects_value per security requirements" &gt;&gt; /etc/sysctl.conf
	echo "net.ipv6.conf.default.accept_redirects = $sysctl_net_ipv6_conf_default_accept_redirects_value" &gt;&gt; /etc/sysctl.conf
fi
</ns0:fix>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-sysctl_net_ipv6_conf_default_accept_redirects_value:var:1" value-id="sysctl_net_ipv6_conf_default_accept_redirects_value" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv6_conf_default_accept_redirects:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv6_conf_default_accept_redirects_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="sysctl_net_ipv6_conf_default_accept_source_route" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Configure Kernel Parameter for Accepting Source-Routed Packets for Interfaces By Default</ns0:title>
              <ns0:description xml:lang="en-US">
                
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.default.accept_source_route</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv6.conf.default.accept_source_route=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.default.accept_source_route = 0</html:pre>
              </ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
              <ns0:rationale xml:lang="en-US">Source-routed packets allow the source of the packet to suggest routers
forward the packet along a different path than configured on the router, which can
be used to bypass network security measures. This requirement applies only to the
forwarding of source-routerd traffic, such as when IPv6 forwarding is enabled and
the system is functioning as a router.

Accepting source-routed packets in the IPv6 protocol has few legitimate
uses. It should be disabled unless it is absolutely required.</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-sysctl_net_ipv6_conf_default_accept_source_route_value:var:1" value-id="sysctl_net_ipv6_conf_default_accept_source_route_value" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv6_conf_default_accept_source_route:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv6_conf_default_accept_source_route_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="sysctl_net_ipv6_conf_all_forwarding" selected="false" severity="medium">
              <ns0:title xml:lang="en-US">Disable Kernel Parameter for IPv6 Forwarding</ns0:title>
              <ns0:description xml:lang="en-US">
                
    To set the runtime status of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.all.forwarding</html:code> kernel parameter,
    run the following command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo sysctl -w net.ipv6.conf.all.forwarding=0</html:pre>
    If this is not the system's default value, add the following line to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.all.forwarding = 0</html:pre>
              </ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-5</ns0:reference>
              <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
              <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.1.1</ns0:reference>
              <ns0:rationale xml:lang="en-US">IP forwarding permits the kernel to forward packets from one network
interface to another. The ability to forward packets between two networks is
only appropriate for systems acting as routers.</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-export export-name="oval:ssg-sysctl_net_ipv6_conf_all_forwarding_value:var:1" value-id="sysctl_net_ipv6_conf_all_forwarding_value" />
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysctl_net_ipv6_conf_all_forwarding:def:1" />
              </ns0:check>
              <ns0:check system="http://scap.nist.gov/schema/ocil/2">
                <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysctl_net_ipv6_conf_all_forwarding_ocil:questionnaire:1" />
              </ns0:check>
            </ns0:Rule>
          </ns0:Group>
          <ns0:Rule id="network_ipv6_static_address" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Manually Assign Global IPv6 Address</ns0:title>
            <ns0:description xml:lang="en-US">To manually assign an IP address for an interface, edit the
file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/network-scripts/ifcfg-<html:i>interface</html:i></html:code>. Add or correct the
following line (substituting the correct IPv6 address):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">IPV6ADDR=2001:0DB8::ABCD/64</html:pre>
Manually assigning an IP address is preferable to accepting one from routers or
from the network otherwise. The example address here is an IPv6 address
reserved for documentation purposes, as defined by RFC3849.
</ns0:description>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-network_ipv6_static_address:def:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="network_ipv6_privacy_extensions" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Use Privacy Extensions for Address</ns0:title>
            <ns0:description xml:lang="en-US">To introduce randomness into the automatic generation of IPv6
addresses, add or correct the following line in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/network-scripts/ifcfg-<html:i>interface</html:i></html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">IPV6_PRIVACY=rfc3041</html:pre>
Automatically-generated IPv6 addresses are based on the underlying hardware
(e.g. Ethernet) address, and so it becomes possible to track a piece of
hardware over its lifetime using its traffic. If it is important for a system's
IP address to not trivially reveal its hardware address, this setting should be
applied.
</ns0:description>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-network_ipv6_privacy_extensions:def:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="network_ipv6_default_gateway" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Manually Assign IPv6 Router Address</ns0:title>
            <ns0:description xml:lang="en-US">Edit the file
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/network-scripts/ifcfg-<html:i>interface</html:i></html:code>, and add or correct
the following line (substituting your gateway IP as appropriate):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">IPV6_DEFAULTGW=2001:0DB8::0001</html:pre>
Router addresses should be manually set and not accepted via any
auto-configuration or router advertisement.
</ns0:description>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-network_ipv6_default_gateway:def:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Group id="network_ipv6_limit_requests">
            <ns0:title xml:lang="en-US">Limit Network-Transmitted Configuration if Using Static IPv6 Addresses</ns0:title>
            <ns0:description xml:lang="en-US">To limit the configuration information requested from other
systems and accepted from the network on a system that uses
statically-configured IPv6 addresses, add the following lines to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysctl.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">net.ipv6.conf.default.router_solicitations = 0
net.ipv6.conf.default.accept_ra_rtr_pref = 0
net.ipv6.conf.default.accept_ra_pinfo = 0
net.ipv6.conf.default.accept_ra_defrtr = 0
net.ipv6.conf.default.autoconf = 0
net.ipv6.conf.default.dad_transmits = 0
net.ipv6.conf.default.max_addresses = 1</html:pre>
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">router_solicitations</html:code> setting determines how many router
solicitations are sent when bringing up the interface. If addresses are
statically assigned, there is no need to send any solicitations.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">accept_ra_pinfo</html:code> setting controls whether the system will accept
prefix info from the router.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">accept_ra_defrtr</html:code> setting controls whether the system will accept
Hop Limit settings from a router advertisement. Setting it to 0 prevents a
router from changing your default IPv6 Hop Limit for outgoing packets.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">autoconf</html:code> setting controls whether router advertisements can cause
the system to assign a global unicast address to an interface.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">dad_transmits</html:code> setting determines how many neighbor solicitations
to send out per address (global and link-local) when bringing up an interface
to ensure the desired address is unique on the network.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">max_addresses</html:code> setting determines how many global unicast IPv6
addresses can be assigned to each interface.  The default is 16, but it should
be set to exactly the number of statically configured global addresses
required.
</ns0:description>
          </ns0:Group>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="network-firewalld">
        <ns0:title xml:lang="en-US">firewalld</ns0:title>
        <ns0:description xml:lang="en-US">The dynamic firewall daemon <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> provides a
dynamically managed firewall with support for network &#8220;zones&#8221; to assign
a level of trust to a network and its associated connections and interfaces.
It has support for IPv4 and IPv6 firewall settings. It supports Ethernet
bridges and has a separation of runtime and permanent configuration options.
It also has an interface for services or applications to add firewall rules
directly.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
A graphical configuration tool, <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewall-config</html:code>, is used to configure
<html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code>, which in turn uses <html:code xmlns:html="http://www.w3.org/1999/xhtml">iptables</html:code> tool to communicate
with <html:code xmlns:html="http://www.w3.org/1999/xhtml">Netfilter</html:code> in the kernel which implements packet filtering.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The firewall service provided by <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> is dynamic rather than
static because changes to the configuration can be made at anytime and are
immediately implemented. There is no need to save or apply the changes. No
unintended disruption of existing network connections occurs as no part of
the firewall has to be reloaded.
</ns0:description>
        <ns0:Group id="firewalld_activation">
          <ns0:title xml:lang="en-US">Inspect and Activate Default firewalld Rules</ns0:title>
          <ns0:description xml:lang="en-US">Firewalls can be used to separate networks into different zones
based on the level of trust the user has decided to place on the devices and
traffic within that network. <html:code xmlns:html="http://www.w3.org/1999/xhtml">NetworkManager</html:code> informs firewalld to which
zone an interface belongs. An interface's assigned zone can be changed by
<html:code xmlns:html="http://www.w3.org/1999/xhtml">NetworkManager</html:code> or via the <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewall-config</html:code> tool.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The zone settings in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/firewalld/</html:code> are a range of preset settings
which can be quickly applied to a network interface. These are the zones
provided by firewalld sorted according to the default trust level of the
zones from untrusted to trusted:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li><html:code>drop</html:code><html:br /><html:p>Any incoming network packets are dropped, there is no
reply. Only outgoing network connections are possible.</html:p></html:li><html:li><html:code>block</html:code><html:br /><html:p>Any incoming network connections are rejected with an
<html:code>icmp-host-prohibited</html:code> message for IPv4 and <html:code>icmp6-adm-prohibited</html:code>
for IPv6. Only network connections initiated from within the system are
possible.</html:p></html:li><html:li><html:code>public</html:code><html:br /><html:p>For use in public areas. You do not trust the other
computers on the network to not harm your computer. Only selected incoming
connections are accepted.</html:p></html:li><html:li><html:code>external</html:code><html:br /><html:p>For use on external networks with masquerading enabled
especially for routers. You do not trust the other computers on the network to
not harm your computer. Only selected incoming connections are accepted.</html:p></html:li><html:li><html:code>dmz</html:code><html:br /><html:p>For computers in your demilitarized zone that are
publicly-accessible with limited access to your internal network. Only selected
incoming connections are accepted.</html:p></html:li><html:li><html:code>work</html:code><html:br /><html:p>For use in work areas. You mostly trust the other computers
on networks to not harm your computer. Only selected incoming connections are
accepted.</html:p></html:li><html:li><html:code>home</html:code><html:br /><html:p>For use in home areas. You mostly trust the other computers
on networks to not harm your computer. Only selected incoming connections are
accepted.</html:p></html:li><html:li><html:code>internal</html:code><html:br /><html:p>For use on internal networks. You mostly trust the
other computers on the networks to not harm your computer. Only selected
incoming connections are accepted.</html:p></html:li><html:li><html:code>trusted</html:code><html:br /><html:p>All network connections are accepted.</html:p></html:li></html:ul>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
It is possible to designate one of these zones to be the default zone. When
interface connections are added to <html:code xmlns:html="http://www.w3.org/1999/xhtml">NetworkManager</html:code>, they are assigned
to the default zone. On installation, the default zone in firewalld is set to
be the public zone.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To find out all the settings of a zone, for example the <html:code xmlns:html="http://www.w3.org/1999/xhtml">public zone,</html:code>
enter the following command as root:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"># firewall-cmd --zone=public --list-all</html:pre>
Example output of this command might look like the following:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">
# firewall-cmd --zone=public --list-all
public
  interfaces:
  services: mdns dhcpv6-client ssh
  ports:
  forward-ports:
  icmp-blocks: source-quench
</html:pre>
To view the network zones currently active, enter the following command as root:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"># firewall-cmd --get-service</html:pre>
The following listing displays the result of this command on common Red Hat
Enterprise Linux 7 Server system:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">
# firewall-cmd --get-service
amanda-client bacula bacula-client dhcp dhcpv6 dhcpv6-client dns ftp
high-availability http https imaps ipp ipp-client ipsec kerberos kpasswd
ldap ldaps libvirt libvirt-tls mdns mountd ms-wbt mysql nfs ntp openvpn
pmcd pmproxy pmwebapi pmwebapis pop3s postgresql proxy-dhcp radius rpc-bind
samba samba-client smtp ssh telnet tftp tftp-client transmission-client
vnc-server wbem-https
</html:pre>
Finally to view the network zones that will be active after the next firewalld
service reload, enter the following command as root:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"># firewall-cmd --get-service --permanent</html:pre>
</ns0:description>
          <ns0:Rule id="service_firewalld_enabled" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Verify firewalld Enabled</ns0:title>
            <ns0:description xml:lang="en-US">
              
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable firewalld.service</html:pre>
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Access control methods provide the ability to enhance system security posture
by restricting services and known good IP addresses and address ranges. This
prevents connections from unknown hosts and protocols.
</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="service_firewalld_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command enable firewalld
</ns0:fix>
            <ns0:fix complexity="low" disruption="low" id="service_firewalld_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Enable service firewalld
  service:
    name="{{item}}"
    enabled="yes"
    state="started"
  with_items:
    - firewalld

</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_firewalld_enabled:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_firewalld_enabled_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="ruleset_modifications">
          <ns0:title xml:lang="en-US">Strengthen the Default Ruleset</ns0:title>
          <ns0:description xml:lang="en-US">The default rules can be strengthened. The system
scripts that activate the firewall rules expect them to be defined
in configuration files under the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/firewalld/services</html:code>
and <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/firewalld/zones</html:code> directories.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The following recommendations describe how to strengthen the
default ruleset configuration file. An alternative to editing this
configuration file is to create a shell script that makes calls to
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewall-cmd</html:code> program to load in rules under the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/firewalld/services</html:code>
and <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/firewalld/zones</html:code> directories.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Instructions apply to both unless otherwise noted. Language and address
conventions for regular firewalld rules are used throughout this section.
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">The program <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewall-config</html:code>
allows additional services to penetrate the default firewall rules
and automatically adjusts the <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> ruleset(s).</ns0:warning>
          <ns0:Rule id="set_firewalld_default_zone" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Set Default firewalld Zone for Incoming Packets</ns0:title>
            <ns0:description xml:lang="en-US">To set the default zone to <html:code xmlns:html="http://www.w3.org/1999/xhtml">drop</html:code> for
the built-in default zone which processes incoming IPv4 and IPv6 packets,
modify the following line in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/firewalld/firewalld.conf</html:code> to be:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">DefaultZone=drop</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">In <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> the default zone is applied only after all
the applicable rules in the table are examined for a match. Setting the
default zone to <html:code xmlns:html="http://www.w3.org/1999/xhtml">drop</html:code> implements proper design for a firewall, i.e.
any packets which are not explicitly permitted should not be
accepted.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="set_firewalld_default_zone" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">grep -q ^DefaultZone= /etc/firewalld/firewalld.conf &amp;&amp; \
  sed -i "s/DefaultZone=.*/DefaultZone=drop/g" /etc/firewalld/firewalld.conf
if ! [ $? -eq 0 ]; then
    echo "DefaultZone=drop" &gt;&gt; /etc/firewalld/firewalld.conf
fi
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-set_firewalld_default_zone:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-set_firewalld_default_zone_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="network_ssl">
        <ns0:title xml:lang="en-US">Transport Layer Security Support</ns0:title>
        <ns0:description xml:lang="en-US">
Support for Transport Layer Security (TLS), and its predecessor, the Secure
Sockets Layer (SSL), is included in Red Hat Enterprise Linux in the OpenSSL software (RPM package
<html:code xmlns:html="http://www.w3.org/1999/xhtml">openssl</html:code>).  TLS provides encrypted and authenticated network
communications, and many network services include support for it.  TLS or SSL
can be leveraged to avoid any plaintext transmission of sensitive data.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For information on how to use OpenSSL, see
<html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="http://www.openssl.org/docs/HOWTO/">http://www.openssl.org/docs/HOWTO/</html:a></html:b>.  Information on FIPS validation
of OpenSSL is available at <html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="http://www.openssl.org/docs/fips/fipsvalidation.html">http://www.openssl.org/docs/fips/fipsvalidation.html</html:a></html:b>
and <html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm">http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm</html:a></html:b>.
For information on how to use and implement OpenSSL on Red Hat Enterprise Linux, see
<html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/sec-Using_OpenSSL.html">https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/sec-Using_OpenSSL.html</html:a></html:b>
</ns0:description>
      </ns0:Group>
      <ns0:Group id="network-uncommon">
        <ns0:title xml:lang="en-US">Uncommon Network Protocols</ns0:title>
        <ns0:description xml:lang="en-US">The system includes support for several network
protocols which are not commonly used. Although security vulnerabilities 
in kernel networking code are not frequently
discovered, the consequences can be dramatic. Ensuring uncommon
network protocols are disabled reduces the system's risk to attacks
targeted at its implementation of those protocols.</ns0:description>
        <ns0:warning xml:lang="en-US">
Although these protocols are not commonly used, avoid disruption
in your network environment by ensuring they are not needed
prior to disabling them.
</ns0:warning>
        <ns0:Rule id="kernel_module_dccp_disabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable DCCP Support</ns0:title>
          <ns0:description xml:lang="en-US">
The Datagram Congestion Control Protocol (DCCP) is a
relatively new transport layer protocol, designed to support
streaming media and telephony.

To configure the system to prevent the <html:code xmlns:html="http://www.w3.org/1999/xhtml">dccp</html:code>
kernel module from being loaded, add the following line to a file in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>:
<html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">install dccp /bin/true</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.6.1</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Disabling DCCP protects
the system against exploitation of any flaws in its implementation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_dccp_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">echo "install dccp /bin/true" &gt; /etc/modprobe.d/dccp.conf
</ns0:fix>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_dccp_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure kernel module 'dccp' is disabled
  lineinfile:
    create=yes
    dest="/etc/modprobe.d/{{item}}.conf"
    regexp="{{item}}"
    line="install {{item}} /bin/true"
  with_items:
    - dccp
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-kernel_module_dccp_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-kernel_module_dccp_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="kernel_module_sctp_disabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable SCTP Support</ns0:title>
          <ns0:description xml:lang="en-US">
The Stream Control Transmission Protocol (SCTP) is a
transport layer protocol, designed to support the idea of
message-oriented communication, with several streams of messages
within one connection.

To configure the system to prevent the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sctp</html:code>
kernel module from being loaded, add the following line to a file in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/modprobe.d</html:code>:
<html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">install sctp /bin/true</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">4.6.2</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Disabling SCTP protects
the system against exploitation of any flaws in its implementation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_sctp_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:sh">echo "install sctp /bin/true" &gt; /etc/modprobe.d/sctp.conf
</ns0:fix>
          <ns0:fix complexity="low" disruption="medium" id="kernel_module_sctp_disabled" reboot="true" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure kernel module 'sctp' is disabled
  lineinfile:
    create=yes
    dest="/etc/modprobe.d/{{item}}.conf"
    regexp="{{item}}"
    line="install {{item}} /bin/true"
  with_items:
    - sctp
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-kernel_module_sctp_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-kernel_module_sctp_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="network-ipsec">
        <ns0:title xml:lang="en-US">IPSec Support</ns0:title>
        <ns0:description xml:lang="en-US">Support for Internet Protocol Security (IPsec)
is provided in Red Hat Enterprise Linux 7 with Libreswan.
</ns0:description>
        <ns0:Rule id="package_libreswan_installed" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Install libreswan Package</ns0:title>
          <ns0:description xml:lang="en-US">The Libreswan package provides an implementation of IPsec
and IKE, which permits the creation of secure tunnels over
untrusted networks. 
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">libreswan</html:code> package can be installed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install libreswan</html:pre> 
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MA-4</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-9</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1130</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1131</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-4.1</ns0:reference>
          <ns0:rationale xml:lang="en-US">Providing the ability for remote users or systems
to initiate a secure VPN connection protects information when it is
transmitted over a wide area network.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_libreswan_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command install libreswan
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_libreswan_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Ensure libreswan is installed
  package:
    name="{{item}}"
    state=present
  with_items:
    - libreswan
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_libreswan_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:puppet">include install_libreswan

class install_libreswan {
  package { 'libreswan':
    ensure =&gt; 'installed',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_libreswan_installed" reboot="false" strategy="enable" system="urn:redhat:anaconda:pre">
package --add=libreswan
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_libreswan_installed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_libreswan_installed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="libreswan_approved_tunnels" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Verify Any Configured IPSec Tunnel Connections</ns0:title>
          <ns0:description xml:lang="en-US">Libreswan provides an implementation of IPsec
and IKE, which permits the creation of secure tunnels over
untrusted networks. As such, IPsec can be used to circumvent certain
network requirements such as filtering. Verify that if any IPsec connection
(<html:code xmlns:html="http://www.w3.org/1999/xhtml">conn</html:code>) configured in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ipsec.conf</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ipsec.d</html:code>
exists is an approved organizational connection.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">336</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
IP tunneling mechanisms can be used to bypass network filtering.
</ns0:rationale>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-libreswan_approved_tunnels_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="logging">
      <ns0:title xml:lang="en-US">Configure Syslog</ns0:title>
      <ns0:description xml:lang="en-US">The syslog service has been the default Unix logging mechanism for
many years. It has a number of downsides, including inconsistent log format,
lack of authentication for received messages, and lack of authentication,
encryption, or reliable transport for messages sent over a network. However,
due to its long history, syslog is a de facto standard which is supported by
almost all Unix applications.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
In Red Hat Enterprise Linux 7, rsyslog has replaced ksyslogd as the
syslog daemon of choice, and it includes some additional security features
such as reliable, connection-oriented (i.e. TCP) transmission of logs, the
option to log to database formats, and the encryption of log data en route to
a central logging server.
This section discusses how to configure rsyslog for
best effect, and how to use tools provided with the system to maintain and
monitor logs.</ns0:description>
      <ns0:Rule id="package_rsyslog_installed" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Ensure rsyslog is Installed</ns0:title>
        <ns0:description xml:lang="en-US">
Rsyslog is installed by default. 

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> package can be installed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install rsyslog</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9(2)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1311</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1312</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.1.1</ns0:reference>
        <ns0:rationale xml:lang="en-US">
The rsyslog package provides the rsyslog daemon, which provides
system logging services.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="package_rsyslog_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command install rsyslog
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="package_rsyslog_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Ensure rsyslog is installed
  package:
    name="{{item}}"
    state=present
  with_items:
    - rsyslog
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="package_rsyslog_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:puppet">include install_rsyslog

class install_rsyslog {
  package { 'rsyslog':
    ensure =&gt; 'installed',
  }
}
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="package_rsyslog_installed" reboot="false" strategy="enable" system="urn:redhat:anaconda:pre">
package --add=rsyslog
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_rsyslog_installed:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_rsyslog_installed_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_rsyslog_enabled" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Enable rsyslog Service</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> service provides syslog-style logging by default on Red Hat Enterprise Linux 7.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable rsyslog.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-4(1)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1311</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1312</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1557</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1851</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.1.2</ns0:reference>
        <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> service must be running in order to provide
logging services, which are essential to system administration.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_rsyslog_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command enable rsyslog
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_rsyslog_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Enable service rsyslog
  service:
    name="{{item}}"
    enabled="yes"
    state="started"
  with_items:
    - rsyslog

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_rsyslog_enabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_rsyslog_enabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Group id="ensure_rsyslog_log_file_configuration">
        <ns0:title xml:lang="en-US">Ensure Proper Configuration of Log Files</ns0:title>
        <ns0:description xml:lang="en-US">
The file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code> controls where log message are written.
These are controlled by lines called <html:i xmlns:html="http://www.w3.org/1999/xhtml">rules</html:i>, which consist of a
<html:i xmlns:html="http://www.w3.org/1999/xhtml">selector</html:i> and an <html:i xmlns:html="http://www.w3.org/1999/xhtml">action</html:i>.
These rules are often customized depending on the role of the system, the
requirements of the environment, and whatever may enable
the administrator to most effectively make use of log data.
The default rules in Red Hat Enterprise Linux 7 are:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">*.info;mail.none;authpriv.none;cron.none                /var/log/messages
authpriv.*                                              /var/log/secure
mail.*                                                  -/var/log/maillog
cron.*                                                  /var/log/cron
*.emerg                                                 *
uucp,news.crit                                          /var/log/spooler
local7.*                                                /var/log/boot.log</html:pre>
See the man page <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog.conf(5)</html:code> for more information.
<html:i xmlns:html="http://www.w3.org/1999/xhtml">Note that the <html:code>rsyslog</html:code> daemon can be configured to use a timestamp format that
some log processing programs may not understand. If this occurs, 
edit the file <html:code>/etc/rsyslog.conf</html:code> and add or edit the following line:</html:i>
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat</html:pre>
</ns0:description>
        <ns0:Value id="file_owner_logfiles_value" operator="equals" type="string">
          <ns0:title xml:lang="en-US">User who owns log files</ns0:title>
          <ns0:description xml:lang="en-US">Specify user owner of all logfiles specified in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code>.</ns0:description>
          <ns0:value selector="root">root</ns0:value>
        </ns0:Value>
        <ns0:Value id="file_groupowner_logfiles_value" operator="equals" type="string">
          <ns0:title xml:lang="en-US">group who owns log files</ns0:title>
          <ns0:description xml:lang="en-US">Specify group owner of all logfiles specified in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf.</html:code></ns0:description>
          <ns0:value selector="root">root</ns0:value>
        </ns0:Value>
        <ns0:Rule id="rsyslog_files_ownership" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure Log Files Are Owned By Appropriate User</ns0:title>
          <ns0:description xml:lang="en-US">The owner of all log files written by
<html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> should be root.
These log files are determined by the second part of each Rule line in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code> and typically all appear in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log</html:code>.
For each log file <html:i xmlns:html="http://www.w3.org/1999/xhtml">LOGFILE</html:i> referenced in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code>,
run the following command to inspect the file's owner:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ ls -l <html:i>LOGFILE</html:i></html:pre>
If the owner is not <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code>, run the following command to
correct this:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root <html:i>LOGFILE</html:i></html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-11</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1314</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.1</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.2</ns0:reference>
          <ns0:rationale xml:lang="en-US">The log files generated by rsyslog contain valuable information regarding system
configuration, user authentication, and other such information. Log files should be
protected from unauthorized access.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-rsyslog_files_ownership:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-rsyslog_files_ownership_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="rsyslog_files_groupownership" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure Log Files Are Owned By Appropriate Group</ns0:title>
          <ns0:description xml:lang="en-US">The group-owner of all log files written by
<html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> should be root.
These log files are determined by the second part of each Rule line in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code> and typically all appear in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log</html:code>.
For each log file <html:i xmlns:html="http://www.w3.org/1999/xhtml">LOGFILE</html:i> referenced in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code>,
run the following command to inspect the file's group owner:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ ls -l <html:i>LOGFILE</html:i></html:pre>
If the owner is not <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code>, run the following command to
correct this:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chgrp root <html:i>LOGFILE</html:i></html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-11</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1314</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.1</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.2</ns0:reference>
          <ns0:rationale xml:lang="en-US">The log files generated by rsyslog contain valuable information regarding system
configuration, user authentication, and other such information. Log files should be
protected from unauthorized access.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-rsyslog_files_groupownership:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-rsyslog_files_groupownership_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="rsyslog_files_permissions" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure System Log Files Have Correct Permissions</ns0:title>
          <ns0:description xml:lang="en-US">The file permissions for all log files written by
<html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> should be set to 600, or more restrictive.
These log files are determined by the second part of each Rule line in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code> and typically all appear in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log</html:code>. 
For each log file <html:i xmlns:html="http://www.w3.org/1999/xhtml">LOGFILE</html:i> referenced in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code>,
run the following command to inspect the file's permissions:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ ls -l <html:i>LOGFILE</html:i></html:pre>
If the permissions are not 600 or more restrictive,
run the following command to correct this:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 0600 <html:i>LOGFILE</html:i></html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SI-11</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1314</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.1</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.1.4</ns0:reference>
          <ns0:rationale xml:lang="en-US">Log files can contain valuable information regarding system
configuration. If the system log files are not protected unauthorized
users could change the logged data, eliminating their forensic value.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="rsyslog_files_permissions" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
# List of log file paths to be inspected for correct permissions
# * Primarily inspect log file paths listed in /etc/rsyslog.conf
RSYSLOG_ETC_CONFIG="/etc/rsyslog.conf"
# * And also the log file paths listed after rsyslog's $IncludeConfig directive
#   (store the result into array for the case there's shell glob used as value of IncludeConfig)
RSYSLOG_INCLUDE_CONFIG=($(grep -e "\$IncludeConfig[[:space:]]\+[^[:space:];]\+" /etc/rsyslog.conf | cut -d ' ' -f 2))
# Declare an array to hold the final list of different log file paths
declare -a LOG_FILE_PATHS

# Browse each file selected above as containing paths of log files
# ('/etc/rsyslog.conf' and '/etc/rsyslog.d/*.conf' in the default configuration)
for LOG_FILE in "${RSYSLOG_ETC_CONFIG}" "${RSYSLOG_INCLUDE_CONFIG[@]}"
do
	# From each of these files extract just particular log file path(s), thus:
	# * Ignore lines starting with space (' '), comment ('#"), or variable syntax ('$') characters,
	# * Ignore empty lines,
	# * From the remaining valid rows select only fields constituting a log file path
	# Text file column is understood to represent a log file path if and only if all of the following are met:
	# * it contains at least one slash '/' character,
	# * it doesn't contain space (' '), colon (':'), and semicolon (';') characters
	# Search log file for path(s) only in case it exists!
	if [[ -f "${LOG_FILE}" ]]
	then
		MATCHED_ITEMS=$(sed -e "/^[[:space:]|#|$]/d ; s/[^\/]*[[:space:]]*\([^:;[:space:]]*\)/\1/g ; /^$/d" "${LOG_FILE}")
		# Since above sed command might return more than one item (delimited by newline), split the particular
		# matches entries into new array specific for this log file
		readarray -t ARRAY_FOR_LOG_FILE &lt;&lt;&lt; "$MATCHED_ITEMS"
		# Concatenate the two arrays - previous content of $LOG_FILE_PATHS array with
		# items from newly created array for this log file
		LOG_FILE_PATHS=("${LOG_FILE_PATHS[@]}" "${ARRAY_FOR_LOG_FILE[@]}")
		# Delete the temporary array
		unset ARRAY_FOR_LOG_FILE
	fi
done

for PATH in "${LOG_FILE_PATHS[@]}"
do
	# Sanity check - if particular $PATH is empty string, skip it from further processing
	if [ -z "$PATH" ]
	then
		continue
	fi
	# Per https://access.redhat.com/solutions/66805 '/var/log/boot.log' log file needs special care =&gt; perform it
	if [ "$PATH" == "/var/log/boot.log" ]
	then
		# Ensure permissions of /var/log/boot.log are configured to be updated in /etc/rc.local
		if ! /bin/grep -q "boot.log" "/etc/rc.local"
		then
			echo "/bin/chmod 600 /var/log/boot.log" &gt;&gt; /etc/rc.local
		fi
		# Ensure /etc/rc.d/rc.local has user-executable permission
		# (in order to be actually executed during boot)
		if [ "$(/usr/bin/stat -c %a /etc/rc.d/rc.local)" -ne 744 ]
		then
			/bin/chmod u+x /etc/rc.d/rc.local
		fi
	fi
	# Also for each log file check if its permissions differ from 600. If so, correct them
	if [ "$(/usr/bin/stat -c %a "$PATH")" -ne 600 ]
	then
		/bin/chmod 600 "$PATH"
	fi
done
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-rsyslog_files_permissions:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-rsyslog_files_permissions_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="rsyslog_cron_logging" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure cron Is Logging To Rsyslog</ns0:title>
          <ns0:description xml:lang="en-US">Cron logging must be implemented to spot intrusions or trace
cron job status. If <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron</html:code> is not logging to <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code>, it
can be implemented by adding the following to the <html:i xmlns:html="http://www.w3.org/1999/xhtml">RULES</html:i> section of
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">cron.*                                                  /var/log/cron</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Cron logging can be used to trace the successful or unsuccessful execution
of cron jobs. It can also be used to spot intrusions into the use of the cron
facility by unauthorized and malicious users.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-rsyslog_cron_logging:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-rsyslog_cron_logging_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="rsyslog_sending_messages">
        <ns0:title xml:lang="en-US">Rsyslog Logs Sent To Remote Host</ns0:title>
        <ns0:description xml:lang="en-US">
If system logs are to be useful in detecting malicious
activities, it is necessary to send logs to a remote server. An
intruder who has compromised the root account on a machine may
delete the log entries which indicate that the system was attacked
before they are seen by an administrator.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
However, it is recommended that logs be stored on the local
host in addition to being sent to the loghost, especially if
<html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> has been configured to use the UDP protocol to send
messages over a network. UDP does not guarantee reliable delivery,
and moderately busy sites will lose log messages occasionally,
especially in periods of high traffic which may be the result of an
attack. In addition, remote <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> messages are not
authenticated in any way by default, so it is easy for an attacker to
introduce spurious messages to the central log server. Also, some
problems cause loss of network connectivity, which will prevent the
sending of messages to the central server. For all of these reasons, it is
better to store log messages both centrally and on each host, so
that they can be correlated if necessary.</ns0:description>
        <ns0:Rule id="rsyslog_remote_loghost" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure Logs Sent To Remote Host</ns0:title>
          <ns0:description xml:lang="en-US">
To configure rsyslog to send logs to a remote log server,
open <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code> and read and understand the last section of the file,
which describes the multiple directives necessary to activate remote
logging.
Along with these other directives, the system can be configured
to forward its logs to a particular log server by
adding or correcting one of the following lines,
substituting <html:code xmlns:html="http://www.w3.org/1999/xhtml"><html:i>loghost.example.com</html:i></html:code> appropriately.
The choice of protocol depends on the environment of the system; 
although TCP and RELP provide more reliable message delivery, 
they may not be supported in all environments.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To use UDP for log message delivery:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">*.* @<html:i>loghost.example.com</html:i></html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To use TCP for log message delivery:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">*.* @@<html:i>loghost.example.com</html:i></html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To use RELP for log message delivery:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">*.* :omrelp:<html:i>loghost.example.com</html:i></html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-3(2)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-4(1)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1348</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">136</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1851</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.1.5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">A log server (loghost) receives syslog messages from one or more
systems. This data can be used as an additional log source in the event a
system is compromised and its local logs are suspect. Forwarding log messages
to a remote loghost also provides system administrators with a centralized
place to view the status of multiple hosts within the enterprise.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-rsyslog_remote_loghost:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-rsyslog_remote_loghost_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="rsyslog_accepting_remote_messages">
        <ns0:title xml:lang="en-US">Configure rsyslogd to Accept Remote Messages If Acting as a Log Server</ns0:title>
        <ns0:description xml:lang="en-US">
By default, <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> does not listen over the network
for log messages. If needed, modules can be enabled to allow
the rsyslog daemon to receive messages from other systems and for the system
thus to act as a log server.
If the machine is not a log server, then lines concerning these modules
should remain commented out.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
</ns0:description>
        <ns0:Rule id="rsyslog_nolisten" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure rsyslog Does Not Accept Remote Messages Unless Acting As Log Server</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> daemon should not accept remote messages
unless the system acts as a log server.
To ensure that it is not listening on the network, ensure the following lines are
<html:i xmlns:html="http://www.w3.org/1999/xhtml">not</html:i> found in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ModLoad imtcp
$InputTCPServerRun <html:i>port</html:i>
$ModLoad imudp
$UDPServerRun <html:i>port</html:i>
$ModLoad imrelp
$InputRELPServerRun <html:i>port</html:i></html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9(2)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(c)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">318</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">368</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1812</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1813</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1814</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Any process which receives messages from the network incurs some risk
of receiving malicious messages. This risk can be eliminated for
rsyslog by configuring it not to listen on the network.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-rsyslog_nolisten:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="rsyslog_accept_remote_messages_tcp" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Enable rsyslog to Accept Messages via TCP, if Acting As Log Server</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> daemon should not accept remote messages
unless the system acts as a log server.
If the system needs to act as a central log server, add the following lines to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code> to enable reception of messages over TCP:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ModLoad imtcp
$InputTCPServerRun 514</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.1.6</ns0:reference>
          <ns0:rationale xml:lang="en-US">
If the system needs to act as a log server, this ensures that it can receive
messages over a reliable TCP connection.
</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="rsyslog_accept_remote_messages_udp" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Enable rsyslog to Accept Messages via UDP, if Acting As Log Server</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsyslog</html:code> daemon should not accept remote messages
unless the system acts as a log server.
If the system needs to act as a central log server, add the following lines to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code> to enable reception of messages over UDP:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ModLoad imudp
$UDPServerRun 514</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.1.6</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Many devices, such as switches, routers, and other Unix-like systems, may only support
the traditional syslog transmission over UDP. If the system must act as a log server,
this enables it to receive their messages as well.
</ns0:rationale>
          </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="log_rotation">
        <ns0:title xml:lang="en-US">Ensure All Logs are Rotated by logrotate</ns0:title>
        <ns0:description xml:lang="en-US">Edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/logrotate.d/syslog</html:code>. Find the first
line, which should look like this (wrapped for clarity):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/var/log/messages /var/log/secure /var/log/maillog /var/log/spooler \
  /var/log/boot.log /var/log/cron {</html:pre>
Edit this line so that it contains a one-space-separated
listing of each log file referenced in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
All logs in use on a system must be rotated regularly, or the
log files will consume disk space over time, eventually interfering
with system operation. The file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/logrotate.d/syslog</html:code> is the
configuration file used by the <html:code xmlns:html="http://www.w3.org/1999/xhtml">logrotate</html:code> program to maintain all
log files written by <html:code xmlns:html="http://www.w3.org/1999/xhtml">syslog</html:code>. By default, it rotates logs weekly and
stores four archival copies of each log. These settings can be
modified by editing <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/logrotate.conf</html:code>, but the defaults are
sufficient for purposes of this guide.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Note that <html:code xmlns:html="http://www.w3.org/1999/xhtml">logrotate</html:code> is run nightly by the cron job
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/cron.daily/logrotate</html:code>. If particularly active logs need to be
rotated more often than once a day, some other mechanism must be
used.</ns0:description>
        <ns0:Rule id="ensure_logrotate_activated" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure Logrotate Runs Periodically</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">logrotate</html:code> utility allows for the automatic rotation of 
log files.  The frequency of rotation is specified in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/logrotate.conf</html:code>, 
which triggers a cron task.  To configure logrotate to run daily, add or correct 
the following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/logrotate.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"># rotate log files <html:i>frequency</html:i>
daily</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.7</ns0:reference>
          <ns0:rationale xml:lang="en-US">Log files that are not properly rotated run the risk of growing so large
that they fill up the /var/log partition. Valuable logging information could be lost
if the /var/log partition becomes full.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-ensure_logrotate_activated:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-ensure_logrotate_activated_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="configure_logwatch_on_logserver">
        <ns0:title xml:lang="en-US"> Configure Logwatch on the Central Log Server</ns0:title>
        <ns0:description xml:lang="en-US"> 
Is this machine the central log server? If so, edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/logwatch/conf/logwatch.conf</html:code> as shown below.
</ns0:description>
        <ns0:Rule id="logwatch_configured_hostlimit" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Configure Logwatch HostLimit Line</ns0:title>
          <ns0:description xml:lang="en-US"> On a central logserver, you want Logwatch to summarize all syslog entries, including those which did not originate 
on the logserver itself. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">HostLimit</html:code> setting tells Logwatch to report on all hosts, not just the one on which it 
is running. 
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"> HostLimit = no </html:pre> </ns0:description>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-logwatch_configured_hostlimit:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="logwatch_configured_splithosts" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Configure Logwatch SplitHosts Line</ns0:title>
          <ns0:description xml:lang="en-US">
If <html:code xmlns:html="http://www.w3.org/1999/xhtml">SplitHosts</html:code> is set, Logwatch will separate entries by hostname. This makes the report longer but significantly 
more usable. If it is not set, then Logwatch will not report which host generated a given log entry, and that 
information is almost always necessary
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"> SplitHosts = yes </html:pre> </ns0:description>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-logwatch_configured_splithosts:def:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Rule id="disable_logwatch_for_logserver" selected="false" severity="low">
        <ns0:title xml:lang="en-US"> Disable Logwatch on Clients if a Logserver Exists</ns0:title>
        <ns0:description xml:lang="en-US"> 
Does your site have a central logserver which has been configured to report on logs received from all systems? 
If so:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"> 
$ sudo rm /etc/cron.daily/0logwatch 
</html:pre>
If no logserver exists, it will be necessary for each machine to run Logwatch individually. Using a central 
logserver provides the security and reliability benefits discussed earlier, and also makes monitoring logs easier 
and less time-intensive for administrators.</ns0:description>
        </ns0:Rule>
    </ns0:Group>
    <ns0:Group id="auditing">
      <ns0:title xml:lang="en-US">System Accounting with auditd</ns0:title>
      <ns0:description xml:lang="en-US">The audit service provides substantial capabilities
for recording system activities. By default, the service audits about
SELinux AVC denials and certain types of security-relevant events
such as system logins, account modifications, and authentication
events performed by programs such as sudo.
Under its default configuration, <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> has modest disk space
requirements, and should not noticeably impact system performance.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
NOTE: The Linux Audit daemon <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> can be configured to use
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules files (<html:code xmlns:html="http://www.w3.org/1999/xhtml">*.rules</html:code>)
located in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code> location and compile them to create
the resulting form of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> configuration file
during the daemon startup (default configuration). Alternatively, the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code>
daemon can use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code> utility to read audit rules from the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> configuration file during daemon startup,
and load them into the kernel. The expected behavior is configured via the
appropriate <html:code xmlns:html="http://www.w3.org/1999/xhtml">ExecStartPost</html:code> directive setting in the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/usr/lib/systemd/system/auditd.service</html:code> configuration file.
To instruct the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program
to read audit rules (default configuration), use the following setting:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /> <html:pre xmlns:html="http://www.w3.org/1999/xhtml">ExecStartPost=-/sbin/augenrules --load</html:pre>
in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/usr/lib/systemd/system/auditd.service</html:code> configuration file.
In order to instruct the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules, use the following setting:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /> <html:pre xmlns:html="http://www.w3.org/1999/xhtml">ExecStartPost=-/sbin/auditctl -R /etc/audit/audit.rules</html:pre>
in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/usr/lib/systemd/system/auditd.service</html:code> configuration file.
Refer to <html:code xmlns:html="http://www.w3.org/1999/xhtml">[Service]</html:code> section of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/usr/lib/systemd/system/auditd.service</html:code>
configuration file for further details.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Government networks often have substantial auditing
requirements and <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> can be configured to meet these
requirements.
Examining some example audit records demonstrates how the Linux audit system
satisfies common requirements.
The following example from Fedora Documentation available at
<html:code xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide/sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide/sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages</html:a></html:code>
shows the substantial amount of information captured in a
two typical "raw" audit messages, followed by a breakdown of the most important
fields. In this example the message is SELinux-related and reports an AVC
denial (and the associated system call) that occurred when the Apache HTTP
Server attempted to access the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/www/html/file1</html:code> file (labeled with
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba_share_t</html:code> type):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">type=AVC msg=audit(1226874073.147:96): avc:  denied  { getattr } for pid=2465 comm="httpd"
path="/var/www/html/file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0
tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file

type=SYSCALL msg=audit(1226874073.147:96): arch=40000003 syscall=196 success=no exit=-13
a0=b98df198 a1=bfec85dc a2=54dff4 a3=2008171 items=0 ppid=2463 pid=2465 auid=502 uid=48
gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=6 comm="httpd"
exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
</html:pre>
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li><html:code>msg=audit(1226874073.147:96)</html:code><html:ul><html:li>The number in parentheses is the unformatted time stamp (Epoch time)
for the event, which can be converted to standard time by using the
<html:code>date</html:code> command.
</html:li></html:ul></html:li><html:li><html:code>{ getattr }</html:code><html:ul><html:li>The item in braces indicates the permission that was denied. <html:code>getattr</html:code>
indicates the source process was trying to read the target file's status information.
This occurs before reading files. This action is denied due to the file being
accessed having the wrong label. Commonly seen permissions include <html:code>getattr</html:code>,
<html:code>read</html:code>, and <html:code>write</html:code>.</html:li></html:ul></html:li><html:li><html:code>comm="httpd"</html:code><html:ul><html:li>The executable that launched the process. The full path of the executable is
found in the <html:code>exe=</html:code> section of the system call (<html:code>SYSCALL</html:code>) message,
which in this case, is <html:code>exe="/usr/sbin/httpd"</html:code>.
</html:li></html:ul></html:li><html:li><html:code>path="/var/www/html/file1"</html:code><html:ul><html:li>The path to the object (target) the process attempted to access.
</html:li></html:ul></html:li><html:li><html:code>scontext="unconfined_u:system_r:httpd_t:s0"</html:code><html:ul><html:li>The SELinux context of the process that attempted the denied action. In
this case, it is the SELinux context of the Apache HTTP Server, which is running
in the <html:code>httpd_t</html:code> domain.
</html:li></html:ul></html:li><html:li><html:code>tcontext="unconfined_u:object_r:samba_share_t:s0"</html:code><html:ul><html:li>The SELinux context of the object (target) the process attempted to access.
In this case, it is the SELinux context of <html:code>file1</html:code>. Note: the <html:code>samba_share_t</html:code>
type is not accessible to processes running in the <html:code>httpd_t</html:code> domain.</html:li></html:ul></html:li><html:li> From the system call (<html:code>SYSCALL</html:code>) message, two items are of interest:
<html:ul><html:li><html:code>success=no</html:code>: indicates whether the denial (AVC) was enforced or not.
<html:code>success=no</html:code> indicates the system call was not successful (SELinux denied
access). <html:code>success=yes</html:code> indicates the system call was successful - this can
be seen for permissive domains or unconfined domains, such as <html:code>initrc_t</html:code>
and <html:code>kernel_t</html:code>.
</html:li><html:li><html:code>exe="/usr/sbin/httpd"</html:code>: the full path to the executable that launched
the process, which in this case, is <html:code>exe="/usr/sbin/httpd"</html:code>.
</html:li></html:ul>
</html:li></html:ul>
</ns0:description>
      <ns0:Rule id="service_auditd_enabled" selected="false" severity="high">
        <ns0:title xml:lang="en-US">Enable auditd Service</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> service is an essential userspace component of
the Linux Auditing System, as it is responsible for writing audit records to
disk.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable auditd.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-3</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(1)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-10</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-14(1)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">131</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000038-GPOS-00016</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000039-GPOS-00017</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000042-GPOS-00021</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000254-GPOS-00095</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000255-GPOS-00096</ns0:reference>
        <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.2</ns0:reference>
        <ns0:rationale xml:lang="en-US">Without establishing what type of events occurred, it would be difficult
to establish, correlate, and investigate the events leading up to an outage or attack.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Ensuring the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> service is active ensures audit records 
generated by the kernel are appropriately recorded.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_auditd_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command enable auditd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_auditd_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Enable service auditd
  service:
    name="{{item}}"
    enabled="yes"
    state="started"
  with_items:
    - auditd

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_auditd_enabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_auditd_enabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="bootloader_audit_argument" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Enable Auditing for Processes Which Start Prior to the Audit Daemon</ns0:title>
        <ns0:description xml:lang="en-US">To ensure all processes can be audited, even those which start
prior to the audit daemon, add the argument <html:code xmlns:html="http://www.w3.org/1999/xhtml">audit=1</html:code> to the default
GRUB 2 command line for the Linux operating system in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/default/grub</html:code>, in the manner below:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=VolGroup/LogVol06 rd.lvm.lv=VolGroup/lv_swap rhgb quiet rd.shell=0 audit=1"</html:pre>
</ns0:description>
        <ns0:warning category="general" xml:lang="en-US">The GRUB 2 configuration file, <html:code xmlns:html="http://www.w3.org/1999/xhtml">grub.cfg</html:code>,
is automatically updated each time a new kernel is installed. Note that any
changes to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/default/grub</html:code> require rebuilding the <html:code xmlns:html="http://www.w3.org/1999/xhtml">grub.cfg</html:code>
file. To update the GRUB 2 configuration file manually, use the
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">grub2-mkconfig -o</html:pre> command as follows:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>On BIOS-based machines, issue the following command as <html:code>root</html:code>:
<html:pre>~]# grub2-mkconfig -o /boot/grub2/grub.cfg</html:pre></html:li><html:li>On UEFI-based machines, issue the following command as <html:code>root</html:code>:
<html:pre>~]# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</html:pre></html:li></html:ul>
</ns0:warning>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(1)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-14(1)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-10</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1464</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">130</ns0:reference>
        <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.3</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.3</ns0:reference>
        <ns0:rationale xml:lang="en-US">
Each process on the system carries an "auditable" flag which indicates whether
its activities can be audited. Although <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> takes care of enabling
this for all processes which launch after it does, adding the kernel argument
ensures it is set for every process during boot.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="bootloader_audit_argument" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
# Correct the form of default kernel command line in /etc/default/grub
grep -q ^GRUB_CMDLINE_LINUX=\".*audit=0.*\" /etc/default/grub &amp;&amp; \
  sed -i "s/audit=[^[:space:]\+]/audit=1/g" /etc/default/grub
if ! [ $? -eq 0 ]; then
  sed -i "s/\(GRUB_CMDLINE_LINUX=\)\"\(.*\)\"/\1\"\2 audit=1\"/" /etc/default/grub
fi

# Correct the form of kernel command line for each installed kernel
# in the bootloader
/sbin/grubby --update-kernel=ALL --args="audit=1"
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-bootloader_audit_argument:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-bootloader_audit_argument_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Group id="configure_auditd_data_retention">
        <ns0:title xml:lang="en-US">Configure auditd Data Retention</ns0:title>
        <ns0:description xml:lang="en-US">
The audit system writes data to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log/audit/audit.log</html:code>. By default,
<html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> rotates 5 logs by size (6MB), retaining a maximum of 30MB of
data in total, and refuses to write entries when the disk is too
full. This minimizes the risk of audit data filling its partition
and impacting other services. This also minimizes the risk of the audit
daemon temporarily disabling the system if it cannot write audit log (which
it can be configured to do).

For a busy
system or a system which is thoroughly auditing system activity, the default settings
for data retention may be
 insufficient. The log file size needed will depend heavily on what types
of events are being audited. First configure auditing to log all the events of
interest. Then monitor the log size manually for awhile to determine what file
size will allow you to keep the required data for the correct time period.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Using a dedicated partition for <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log/audit</html:code> prevents the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> logs from disrupting system functionality if they fill, and,
more importantly, prevents other activity in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var</html:code> from filling the
partition and stopping the audit trail. (The audit logs are size-limited and
therefore unlikely to grow without bound unless configured to do so.) Some
machines may have requirements that no actions occur which cannot be audited.
If this is the case, then <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> can be configured to halt the machine
if it runs out of space. <html:b xmlns:html="http://www.w3.org/1999/xhtml">Note:</html:b> Since older logs are rotated,
configuring <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> this way does not prevent older logs from being
rotated away before they can be viewed.

<html:i xmlns:html="http://www.w3.org/1999/xhtml">If your system is configured to halt when logging cannot be performed, make
sure this can never happen under normal circumstances! Ensure that
<html:code>/var/log/audit</html:code> is on its own partition, and that this partition is
larger than the maximum amount of data <html:code>auditd</html:code> will retain
normally.</html:i>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-11</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">138</ns0:reference>
        <ns0:Value id="var_auditd_num_logs" type="number">
          <ns0:title xml:lang="en-US">Number of log files for auditd to retain</ns0:title>
          <ns0:description xml:lang="en-US">The setting for num_logs in /etc/audit/auditd.conf</ns0:description>
          <ns0:value>5</ns0:value>
          <ns0:value selector="5">5</ns0:value>
          <ns0:value selector="4">4</ns0:value>
          <ns0:value selector="3">3</ns0:value>
          <ns0:value selector="2">2</ns0:value>
          <ns0:value selector="1">1</ns0:value>
          <ns0:value selector="0">0</ns0:value>
        </ns0:Value>
        <ns0:Value id="var_auditd_max_log_file" type="number">
          <ns0:title xml:lang="en-US">Maximum audit log file size for auditd</ns0:title>
          <ns0:description xml:lang="en-US">The setting for max_log_size in /etc/audit/auditd.conf</ns0:description>
          <ns0:value>6</ns0:value>
          <ns0:value selector="20">20</ns0:value>
          <ns0:value selector="10">10</ns0:value>
          <ns0:value selector="6">6</ns0:value>
          <ns0:value selector="5">5</ns0:value>
          <ns0:value selector="1">1</ns0:value>
        </ns0:Value>
        <ns0:Value id="var_auditd_max_log_file_action" type="string">
          <ns0:title xml:lang="en-US">Action for auditd to take when log files reach their maximum size</ns0:title>
          <ns0:description xml:lang="en-US">The setting for max_log_file_action in /etc/audit/auditd.conf</ns0:description>
          <ns0:value>rotate</ns0:value>
          <ns0:value selector="ignore">ignore</ns0:value>
          <ns0:value selector="syslog">syslog</ns0:value>
          <ns0:value selector="suspend">suspend</ns0:value>
          <ns0:value selector="rotate">rotate</ns0:value>
          <ns0:value selector="keep_logs">keep_logs</ns0:value>
        </ns0:Value>
        <ns0:Value id="var_auditd_space_left_action" type="string">
          <ns0:title xml:lang="en-US">Action for auditd to take when disk space just starts to run low</ns0:title>
          <ns0:description xml:lang="en-US">The setting for space_left_action in /etc/audit/auditd.conf</ns0:description>
          <ns0:value>email</ns0:value>
          <ns0:value selector="ignore">ignore</ns0:value>
          <ns0:value selector="syslog">syslog</ns0:value>
          <ns0:value selector="email">email</ns0:value>
          <ns0:value selector="exec">exec</ns0:value>
          <ns0:value selector="suspend">suspend</ns0:value>
          <ns0:value selector="single">single</ns0:value>
          <ns0:value selector="halt">halt</ns0:value>
        </ns0:Value>
        <ns0:Value id="var_auditd_admin_space_left_action" type="string">
          <ns0:title xml:lang="en-US">Action for auditd to take when disk space just starts to run low</ns0:title>
          <ns0:description xml:lang="en-US">The setting for space_left_action in /etc/audit/auditd.conf</ns0:description>
          <ns0:value>single</ns0:value>
          <ns0:value selector="ignore">ignore</ns0:value>
          <ns0:value selector="syslog">syslog</ns0:value>
          <ns0:value selector="email">email</ns0:value>
          <ns0:value selector="exec">exec</ns0:value>
          <ns0:value selector="suspend">suspend</ns0:value>
          <ns0:value selector="single">single</ns0:value>
          <ns0:value selector="halt">halt</ns0:value>
        </ns0:Value>
        <ns0:Value id="var_auditd_action_mail_acct" type="string">
          <ns0:title xml:lang="en-US">Account for auditd to send email when actions occurs</ns0:title>
          <ns0:description xml:lang="en-US">The setting for action_mail_acct in /etc/audit/auditd.conf</ns0:description>
          <ns0:value>root</ns0:value>
          <ns0:value selector="root">root</ns0:value>
          <ns0:value selector="admin">admin</ns0:value>
        </ns0:Value>
        <ns0:Value id="var_auditd_flush" type="string">
          <ns0:title xml:lang="en-US">Auditd priority for flushing data to disk</ns0:title>
          <ns0:description xml:lang="en-US">The setting for flush in /etc/audit/auditd.conf</ns0:description>
          <ns0:value>data</ns0:value>
          <ns0:value selector="none">none</ns0:value>
          <ns0:value selector="incremental">incremental</ns0:value>
          <ns0:value selector="data">data</ns0:value>
          <ns0:value selector="sync">sync</ns0:value>
        </ns0:Value>
        <ns0:Rule id="auditd_data_retention_num_logs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure auditd Number of Logs Retained</ns0:title>
          <ns0:description xml:lang="en-US">Determine how many log files
<html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> should retain when it rotates logs.
Edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/auditd.conf</html:code>. Add or modify the following
line, substituting <html:i xmlns:html="http://www.w3.org/1999/xhtml">NUMLOGS</html:i> with the correct value of <ns0:sub idref="var_auditd_num_logs" />:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">num_logs = <html:i>NUMLOGS</html:i></html:pre>
Set the value to 5 for general-purpose systems. 
Note that values less than 2 result in no log rotation.</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-11</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.7</ns0:reference>
          <ns0:rationale xml:lang="en-US">The total storage for audit log files must be large enough to retain
log information over the period required. This is a function of the maximum log
file size and the number of logs retained.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="auditd_data_retention_num_logs" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_auditd_num_logs="<ns0:sub idref="var_auditd_num_logs" />"

AUDITCONFIG=/etc/audit/auditd.conf

grep -q ^num_logs $AUDITCONFIG &amp;&amp; \
  sed -i 's/^num_logs.*/num_logs = '"$var_auditd_num_logs"'/g' $AUDITCONFIG
if ! [ $? -eq 0 ]; then
  echo "num_logs = $var_auditd_num_logs" &gt;&gt; $AUDITCONFIG
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_auditd_num_logs:var:1" value-id="var_auditd_num_logs" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-auditd_data_retention_num_logs:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-auditd_data_retention_num_logs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="auditd_data_retention_max_log_file" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure auditd Max Log File Size</ns0:title>
          <ns0:description xml:lang="en-US">Determine the amount of audit data (in megabytes)
which should be retained in each log file. Edit the file
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/auditd.conf</html:code>. Add or modify the following line, substituting
the correct value of <ns0:sub idref="var_auditd_max_log_file" /> for <html:i xmlns:html="http://www.w3.org/1999/xhtml">STOREMB</html:i>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">max_log_file = <html:i>STOREMB</html:i></html:pre>
Set the value to <html:code xmlns:html="http://www.w3.org/1999/xhtml">6</html:code> (MB) or higher for general-purpose systems.
Larger values, of course,
support retention of even more audit data.</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-11</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.1.1</ns0:reference>
          <ns0:rationale xml:lang="en-US">The total storage for audit log files must be large enough to retain
log information over the period required. This is a function of the maximum
log file size and the number of logs retained.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="auditd_data_retention_max_log_file" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_auditd_max_log_file="<ns0:sub idref="var_auditd_max_log_file" />"

AUDITCONFIG=/etc/audit/auditd.conf

grep -q ^max_log_file $AUDITCONFIG &amp;&amp; \
  sed -i 's/^max_log_file.*/max_log_file = '"$var_auditd_max_log_file"'/g' $AUDITCONFIG
if ! [ $? -eq 0 ]; then
  echo "max_log_file = $var_auditd_max_log_file" &gt;&gt; $AUDITCONFIG
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_auditd_max_log_file:var:1" value-id="var_auditd_max_log_file" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-auditd_data_retention_max_log_file:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-auditd_data_retention_max_log_file_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="auditd_data_retention_max_log_file_action" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure auditd max_log_file_action Upon Reaching Maximum Log Size</ns0:title>
          <ns0:description xml:lang="en-US"> The default action to take when the logs reach their maximum size
is to rotate the log files, discarding the oldest one. To configure the action taken
by <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code>, add or correct the line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/auditd.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">max_log_file_action = <html:i>ACTION</html:i></html:pre>
Possible values for <html:i xmlns:html="http://www.w3.org/1999/xhtml">ACTION</html:i> are described in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd.conf</html:code> man
page. These include:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li><html:code>ignore</html:code></html:li><html:li><html:code>syslog</html:code></html:li><html:li><html:code>suspend</html:code></html:li><html:li><html:code>rotate</html:code></html:li><html:li><html:code>keep_logs</html:code></html:li></html:ul>
Set the <html:code xmlns:html="http://www.w3.org/1999/xhtml"><html:i>ACTION</html:i></html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">rotate</html:code> to ensure log rotation
occurs.  This is the default.  The setting is case-insensitive.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-4</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-11</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.1.3</ns0:reference>
          <ns0:rationale xml:lang="en-US">Automatically rotating logs (by setting this to <html:code xmlns:html="http://www.w3.org/1999/xhtml">rotate</html:code>)
minimizes the chances of the system unexpectedly running out of disk space by
being overwhelmed with log data. However, for systems that must never discard
log data, or which use external processes to transfer it and reclaim space,
<html:code xmlns:html="http://www.w3.org/1999/xhtml">keep_logs</html:code> can be employed.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="auditd_data_retention_max_log_file_action" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_auditd_max_log_file_action="<ns0:sub idref="var_auditd_max_log_file_action" />"

AUDITCONFIG=/etc/audit/auditd.conf

grep -q ^max_log_file_action $AUDITCONFIG &amp;&amp; \
  sed -i 's/^max_log_file_action.*/max_log_file_action = '"$var_auditd_max_log_file_action"'/g' $AUDITCONFIG
if ! [ $? -eq 0 ]; then
  echo "max_log_file_action = $var_auditd_max_log_file_action" &gt;&gt; $AUDITCONFIG
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_auditd_max_log_file_action:var:1" value-id="var_auditd_max_log_file_action" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-auditd_data_retention_max_log_file_action:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-auditd_data_retention_max_log_file_action_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="auditd_data_retention_space_left_action" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure auditd space_left Action on Low Disk Space</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> service can be configured to take an action
when disk space <html:i xmlns:html="http://www.w3.org/1999/xhtml">starts</html:i> to run low.
Edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/auditd.conf</html:code>. Modify the following line,
substituting <html:i xmlns:html="http://www.w3.org/1999/xhtml">ACTION</html:i> appropriately:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">space_left_action = <html:i>ACTION</html:i></html:pre>
Possible values for <html:i xmlns:html="http://www.w3.org/1999/xhtml">ACTION</html:i> are described in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd.conf</html:code> man page.
These include:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li><html:code>ignore</html:code></html:li><html:li><html:code>syslog</html:code></html:li><html:li><html:code>email</html:code></html:li><html:li><html:code>exec</html:code></html:li><html:li><html:code>suspend</html:code></html:li><html:li><html:code>single</html:code></html:li><html:li><html:code>halt</html:code></html:li></html:ul>
Set this to <html:code xmlns:html="http://www.w3.org/1999/xhtml">email</html:code> (instead of the default,
which is <html:code xmlns:html="http://www.w3.org/1999/xhtml">suspend</html:code>) as it is more likely to get prompt attention. Acceptable values
also include <html:code xmlns:html="http://www.w3.org/1999/xhtml">suspend</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">single</html:code>, and <html:code xmlns:html="http://www.w3.org/1999/xhtml">halt</html:code>.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-4</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-5(1)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-5(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1855</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.1.2</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000343-GPOS-00134</ns0:reference>
          <ns0:rationale xml:lang="en-US">Notifying administrators of an impending disk space problem may
allow them to take corrective action prior to any disruption.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="auditd_data_retention_space_left_action" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_auditd_space_left_action="<ns0:sub idref="var_auditd_space_left_action" />"

grep -q ^space_left_action /etc/audit/auditd.conf &amp;&amp; \
  sed -i "s/space_left_action.*/space_left_action = $var_auditd_space_left_action/g" /etc/audit/auditd.conf
if ! [ $? -eq 0 ]; then
    echo "space_left_action = $var_auditd_space_left_action" &gt;&gt; /etc/audit/auditd.conf
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_auditd_space_left_action:var:1" value-id="var_auditd_space_left_action" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-auditd_data_retention_space_left_action:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-auditd_data_retention_space_left_action_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="auditd_data_retention_admin_space_left_action" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure auditd admin_space_left Action on Low Disk Space</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> service can be configured to take an action
when disk space is running low but prior to running out of space completely. 
Edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/auditd.conf</html:code>. Add or modify the following line,
substituting <html:i xmlns:html="http://www.w3.org/1999/xhtml">ACTION</html:i> appropriately:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">admin_space_left_action = <html:i>ACTION</html:i></html:pre>
Set this value to <html:code xmlns:html="http://www.w3.org/1999/xhtml">single</html:code> to cause the system to switch to single user
mode for corrective action. Acceptable values also include <html:code xmlns:html="http://www.w3.org/1999/xhtml">suspend</html:code> and
<html:code xmlns:html="http://www.w3.org/1999/xhtml">halt</html:code>. For certain systems, the need for availability
outweighs the need to log all actions, and a different setting should be
determined. Details regarding all possible values for <html:i xmlns:html="http://www.w3.org/1999/xhtml">ACTION</html:i> are described in the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd.conf</html:code> man page.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-4</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-5(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">140</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1343</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.1.2</ns0:reference>
          <ns0:rationale xml:lang="en-US">Administrators should be made aware of an inability to record
audit records. If a separate partition or logical volume of adequate size
is used, running low on space for audit records should never occur.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="auditd_data_retention_admin_space_left_action" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_auditd_admin_space_left_action="<ns0:sub idref="var_auditd_admin_space_left_action" />"

grep -q ^admin_space_left_action /etc/audit/auditd.conf &amp;&amp; \
  sed -i "s/admin_space_left_action.*/admin_space_left_action = $var_auditd_admin_space_left_action/g" /etc/audit/auditd.conf
if ! [ $? -eq 0 ]; then
    echo "admin_space_left_action = $var_auditd_admin_space_left_action" &gt;&gt; /etc/audit/auditd.conf
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_auditd_admin_space_left_action:var:1" value-id="var_auditd_admin_space_left_action" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-auditd_data_retention_admin_space_left_action:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-auditd_data_retention_admin_space_left_action_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="auditd_data_retention_action_mail_acct" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure auditd mail_acct Action on Low Disk Space</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> service can be configured to send email to
a designated account in certain situations. Add or correct the following line
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/auditd.conf</html:code> to ensure that administrators are notified
via email for those situations:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">action_mail_acct = <ns0:sub idref="var_auditd_action_mail_acct" /></html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-4</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-5(1)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-5(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1855</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.7.a</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.1.2</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000343-GPOS-00134</ns0:reference>
          <ns0:rationale xml:lang="en-US">Email sent to the root account is typically aliased to the
administrators of the system, who can take appropriate action.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="auditd_data_retention_action_mail_acct" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_auditd_action_mail_acct="<ns0:sub idref="var_auditd_action_mail_acct" />"

AUDITCONFIG=/etc/audit/auditd.conf

grep -q ^action_mail_acct $AUDITCONFIG &amp;&amp; \
  sed -i 's/^action_mail_acct.*/action_mail_acct = '"$var_auditd_action_mail_acct"'/g' $AUDITCONFIG
if ! [ $? -eq 0 ]; then
  echo "action_mail_acct = $var_auditd_action_mail_acct" &gt;&gt; $AUDITCONFIG
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_auditd_action_mail_acct:var:1" value-id="var_auditd_action_mail_acct" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-auditd_data_retention_action_mail_acct:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-auditd_data_retention_action_mail_acct_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="auditd_data_retention_flush" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Configure auditd flush priority</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> service can be configured to
synchronously write audit event data to disk. Add or correct the following
line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/auditd.conf</html:code> to ensure that audit event data is
fully synchronized with the log files on the disk:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">flush = <ns0:sub idref="var_auditd_flush" /></html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(1)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1576</ns0:reference>
          <ns0:rationale xml:lang="en-US">Audit data should be synchronously written to disk to ensure
log integrity. These parameters assure that all audit event data is fully
synchronized with the log files on the disk.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="auditd_data_retention_flush" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
var_auditd_flush="<ns0:sub idref="var_auditd_flush" />"

AUDITCONFIG=/etc/audit/auditd.conf

# if flush is present, flush param edited to var_auditd_flush
# else flush param is defined by var_auditd_flush
#
# the freq param is only used value 'incremental' and will be
# commented out if flush != incremental
#
# if flush == incremental &amp;&amp; freq param is not defined, it 
# will be defined as the package-default value of 20

grep -q ^flush $AUDITCONFIG &amp;&amp; \
  sed -i 's/^flush.*/flush = '"$var_auditd_flush"'/g' $AUDITCONFIG
if ! [ $? -eq 0 ]; then
  echo "flush = $var_auditd_flush" &gt;&gt; $AUDITCONFIG
fi

if ! [ "$var_auditd_flush" == "incremental" ]; then
  sed -i 's/^freq/##freq/g' $AUDITCONFIG
elif [ "$var_auditd_flush" == "incremental" ]; then
  grep -q freq $AUDITCONFIG &amp;&amp; \
    sed -i 's/^#\+freq/freq/g' $AUDITCONFIG
  if ! [ $? -eq 0 ]; then
    echo "freq = 20" &gt;&gt; $AUDITCONFIG
  fi
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-var_auditd_flush:var:1" value-id="var_auditd_flush" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-auditd_data_retention_flush:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-auditd_data_retention_flush_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="auditd_audispd_syslog_plugin_activated" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure auditd to use audispd's syslog plugin</ns0:title>
          <ns0:description xml:lang="en-US">To configure the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> service to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">syslog</html:code> plug-in of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">audispd</html:code> audit event multiplexor, set
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">active</html:code> line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audisp/plugins.d/syslog.conf</html:code> to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">yes</html:code>. Restart the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> service:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo service auditd restart</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-3(2)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">136</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.3</ns0:reference>
          <ns0:rationale xml:lang="en-US">The auditd service does not include the ability to send audit
records to a centralized server for management directly. It does, however,
include a plug-in for audit event multiplexor (audispd) to pass audit records
to the local syslog server</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="auditd_audispd_syslog_plugin_activated" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
grep -q ^active /etc/audisp/plugins.d/syslog.conf &amp;&amp; \
  sed -i "s/active.*/active = yes/g" /etc/audisp/plugins.d/syslog.conf
if ! [ $? -eq 0 ]; then
    echo "active = yes" &gt;&gt; /etc/audisp/plugins.d/syslog.conf
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-auditd_audispd_syslog_plugin_activated:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-auditd_audispd_syslog_plugin_activated_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="auditd_configure_rules">
        <ns0:title xml:lang="en-US">Configure auditd Rules for Comprehensive Auditing</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> program can perform comprehensive
monitoring of system activity. This section describes recommended
configuration settings for comprehensive auditing, but a full
description of the auditing system's capabilities is beyond the
scope of this guide. The mailing list <html:i xmlns:html="http://www.w3.org/1999/xhtml">linux-audit@redhat.com</html:i> exists
to facilitate community discussion of the auditing system.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The audit subsystem supports extensive collection of events, including:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>Tracing of arbitrary system calls (identified by name or number)
on entry or exit.</html:li><html:li>Filtering by PID, UID, call success, system call argument (with
some limitations), etc.</html:li><html:li>Monitoring of specific files for modifications to the file's
contents or metadata.</html:li></html:ul>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Auditing rules at startup are controlled by the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code>.
Add rules to it to meet the auditing requirements for your organization.
Each line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> represents a series of arguments
that can be passed to <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code> and can be individually tested
during runtime. See documentation in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/usr/share/doc/audit-<html:i>VERSION</html:i></html:code> and
in the related man pages for more details.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If copying any example audit rulesets from <html:code xmlns:html="http://www.w3.org/1999/xhtml">/usr/share/doc/audit-VERSION</html:code>,
be sure to comment out the
lines containing <html:code xmlns:html="http://www.w3.org/1999/xhtml">arch=</html:code> which are not appropriate for your system's
architecture. Then review and understand the following rules,
ensuring rules are activated as needed for the appropriate
architecture.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
After reviewing all the rules, reading the following sections, and
editing as needed, the new rules can be activated as follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo service auditd restart</html:pre>
</ns0:description>
        <ns0:Group id="audit_time_rules">
          <ns0:title xml:lang="en-US">Records Events that Modify Date and Time Information</ns0:title>
          <ns0:description xml:lang="en-US">Arbitrary changes to the system time can be used to obfuscate
nefarious activities in log files, as well as to confuse network services that
are highly dependent upon an accurate system time. All changes to the system
time should be audited.</ns0:description>
          <ns0:Rule id="audit_rules_time_adjtimex" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record attempts to alter time through adjtimex</ns0:title>
            <ns0:description xml:lang="en-US">If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the
default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the
directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S adjtimex -k audit_time_rules</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S adjtimex -k audit_time_rules</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S adjtimex -k audit_time_rules</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S adjtimex -k audit_time_rules</html:pre>
The -k option allows for the specification of a key in string form that can be
used for better reporting capability through ausearch and aureport. Multiple
system calls can be defined on the same line to save space if desired, but is
not required. See an example of multiple combined syscalls:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S adjtimex -S settimeofday -k audit_time_rules</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.4</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.4.2.b</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1487</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">169</ns0:reference>
            <ns0:rationale xml:lang="en-US">Arbitrary changes to the system time can be used to obfuscate
nefarious activities in log files, as well as to confuse network services that
are highly dependent upon an accurate system time (such as sshd). All changes
to the system time should be audited.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_time_adjtimex" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_rhel7_fedora_perform_audit_adjtimex_settimeofday_stime_remediation" />
rhel7_fedora_perform_audit_adjtimex_settimeofday_stime_remediation
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_time_adjtimex:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_time_adjtimex_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_time_settimeofday" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record attempts to alter time through settimeofday</ns0:title>
            <ns0:description xml:lang="en-US">If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the
default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the
directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S settimeofday -k audit_time_rules</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S settimeofday -k audit_time_rules</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S settimeofday -k audit_time_rules</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S settimeofday -k audit_time_rules</html:pre>
The -k option allows for the specification of a key in string form that can be
used for better reporting capability through ausearch and aureport. Multiple
system calls can be defined on the same line to save space if desired, but is
not required. See an example of multiple combined syscalls:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S adjtimex -S settimeofday -k audit_time_rules</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.4</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.4.2.b</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1487</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">169</ns0:reference>
            <ns0:rationale xml:lang="en-US">Arbitrary changes to the system time can be used to obfuscate
nefarious activities in log files, as well as to confuse network services that
are highly dependent upon an accurate system time (such as sshd). All changes
to the system time should be audited.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_time_settimeofday" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_rhel7_fedora_perform_audit_adjtimex_settimeofday_stime_remediation" />
rhel7_fedora_perform_audit_adjtimex_settimeofday_stime_remediation
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_time_settimeofday:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_time_settimeofday_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_time_stime" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Attempts to Alter Time Through stime</ns0:title>
            <ns0:description xml:lang="en-US">If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the
default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the
directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code> for both 32 bit and 64 bit systems:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S stime -k audit_time_rules</html:pre>
Since the 64 bit version of the "stime" system call is not defined in the audit
lookup table, the corresponding "-F arch=b64" form of this rule is not expected
to be defined on 64 bit systems (the aforementioned "-F arch=b32" stime rule
form itself is sufficient for both 32 bit and 64 bit systems). If the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code> utility to
read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file for both 32 bit and 64 bit systems:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S stime -k audit_time_rules</html:pre>
Since the 64 bit version of the "stime" system call is not defined in the audit
lookup table, the corresponding "-F arch=b64" form of this rule is not expected
to be defined on 64 bit systems (the aforementioned "-F arch=b32" stime rule
form itself is sufficient for both 32 bit and 64 bit systems). The -k option
allows for the specification of a key in string form that can be used for
better reporting capability through ausearch and aureport. Multiple system
calls can be defined on the same line to save space if desired, but is not
required. See an example of multiple combined system calls:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S adjtimex -S settimeofday -k audit_time_rules</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.4.2.b</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1487</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">169</ns0:reference>
            <ns0:rationale xml:lang="en-US">Arbitrary changes to the system time can be used to obfuscate
nefarious activities in log files, as well as to confuse network services that
are highly dependent upon an accurate system time (such as sshd). All changes
to the system time should be audited.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_time_stime" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_rhel7_fedora_perform_audit_adjtimex_settimeofday_stime_remediation" />
rhel7_fedora_perform_audit_adjtimex_settimeofday_stime_remediation
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_time_stime:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_time_stime_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_time_clock_settime" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Attempts to Alter Time Through clock_settime</ns0:title>
            <ns0:description xml:lang="en-US">If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the
default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the
directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -F key=time-change</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -F key=time-change</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -F key=time-change</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -F key=time-change</html:pre>
The -k option allows for the specification of a key in string form that can
be used for better reporting capability through ausearch and aureport.
Multiple system calls can be defined on the same line to save space if
desired, but is not required. See an example of multiple combined syscalls:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S adjtimex -S settimeofday -k audit_time_rules</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.4</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.4.2.b</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1487</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">169</ns0:reference>
            <ns0:rationale xml:lang="en-US">Arbitrary changes to the system time can be used to obfuscate
nefarious activities in log files, as well as to confuse network services that
are highly dependent upon an accurate system time (such as sshd). All changes
to the system time should be audited.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_time_clock_settime" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">

# First perform the remediation of the syscall rule
# Retrieve hardware architecture of the underlying system
[ "$(getconf LONG_BIT)" = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S clock_settime -F a0=.* \(-F key=\|-k \).*"
	GROUP="clock_settime"
	FULL_RULE="-a always,exit -F arch=$ARCH -S clock_settime -F a0=0x0 -k time-change"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_time_clock_settime:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_time_clock_settime_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_time_watch_localtime" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Attempts to Alter the localtime File</ns0:title>
            <ns0:description xml:lang="en-US">If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the default),
add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /etc/localtime -p wa -k audit_time_rules</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /etc/localtime -p wa -k audit_time_rules</html:pre>
The -k option allows for the specification of a key in string form that can
be used for better reporting capability through ausearch and aureport and
should always be used.
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.4</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.4.2.b</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1487</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">169</ns0:reference>
            <ns0:rationale xml:lang="en-US">Arbitrary changes to the system time can be used to obfuscate
nefarious activities in log files, as well as to confuse network services that
are highly dependent upon an accurate system time (such as sshd). All changes
to the system time should be audited.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_time_watch_localtime" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/localtime" "wa" "audit_time_rules"
fix_audit_watch_rule "augenrules" "/etc/localtime" "wa" "audit_time_rules"
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_time_watch_localtime:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_time_watch_localtime_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Rule id="audit_rules_usergroup_modification" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Record Events that Modify User/Group Information</ns0:title>
          <ns0:description xml:lang="en-US">If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the
directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>, in order to capture events that modify
account changes:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /etc/group -p wa -k audit_rules_usergroup_modification
-w /etc/passwd -p wa -k audit_rules_usergroup_modification
-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
-w /etc/shadow -p wa -k audit_rules_usergroup_modification
-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following lines to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file, in order to capture events that modify
account changes:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /etc/group -p wa -k audit_rules_usergroup_modification
-w /etc/passwd -p wa -k audit_rules_usergroup_modification
-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
-w /etc/shadow -p wa -k audit_rules_usergroup_modification
-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-2(4)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">18</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1403</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2130</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.5</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG&#8211;OS&#8211;000004&#8211;GPOS&#8211;00004</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG&#8211;OS&#8211;000239&#8211;GPOS&#8211;00089</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG&#8211;OS&#8211;000241&#8211;GPOS&#8211;00090</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG&#8211;OS&#8211;000241&#8211;GPOS&#8211;00091</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG&#8211;OS&#8211;000303&#8211;GPOS&#8211;00120</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG&#8211;OS&#8211;000476&#8211;GPOS&#8211;00221</ns0:reference>
          <ns0:rationale xml:lang="en-US">In addition to auditing new user and group accounts, these watches
will alert the system administrator(s) to any modifications. Any unexpected
users, groups, or modifications should be investigated for legitimacy.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_usergroup_modification" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation
# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/group" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "augenrules" "/etc/group" "wa" "audit_rules_usergroup_modification"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/passwd" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "augenrules" "/etc/passwd" "wa" "audit_rules_usergroup_modification"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/gshadow" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "augenrules" "/etc/gshadow" "wa" "audit_rules_usergroup_modification"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/shadow" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "augenrules" "/etc/shadow" "wa" "audit_rules_usergroup_modification"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/security/opasswd" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "augenrules" "/etc/security/opasswd" "wa" "audit_rules_usergroup_modification"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_usergroup_modification:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_usergroup_modification_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="audit_rules_networkconfig_modification" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Record Events that Modify the System's Network Environment</ns0:title>
          <ns0:description xml:lang="en-US">If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the
directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>, setting ARCH to either b32 or b64 as
appropriate for your system:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=ARCH -S sethostname -S setdomainname -k audit_rules_networkconfig_modification
-w /etc/issue -p wa -k audit_rules_networkconfig_modification
-w /etc/issue.net -p wa -k audit_rules_networkconfig_modification
-w /etc/hosts -p wa -k audit_rules_networkconfig_modification
-w /etc/sysconfig/network -p wa -k audit_rules_networkconfig_modification</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following lines to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file, setting ARCH to either b32 or b64 as
appropriate for your system:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=ARCH -S sethostname -S setdomainname -k audit_rules_networkconfig_modification
-w /etc/issue -p wa -k audit_rules_networkconfig_modification
-w /etc/issue.net -p wa -k audit_rules_networkconfig_modification
-w /etc/hosts -p wa -k audit_rules_networkconfig_modification
-w /etc/sysconfig/network -p wa -k audit_rules_networkconfig_modification</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.6</ns0:reference>
          <ns0:rationale xml:lang="en-US">The network environment should not be modified by anything other
than administrator action. Any change to network parameters should be
audited.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_networkconfig_modification" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# First perform the remediation of the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -k *"
	# Use escaped BRE regex to specify rule group
	GROUP="set\(host\|domain\)name"
	FULL_RULE="-a always,exit -F arch=$ARCH -S sethostname -S setdomainname -k audit_rules_networkconfig_modification"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done

# Then perform the remediations for the watch rules
# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/issue" "wa" "audit_rules_networkconfig_modification"
fix_audit_watch_rule "augenrules" "/etc/issue" "wa" "audit_rules_networkconfig_modification"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/issue.net" "wa" "audit_rules_networkconfig_modification"
fix_audit_watch_rule "augenrules" "/etc/issue.net" "wa" "audit_rules_networkconfig_modification"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/hosts" "wa" "audit_rules_networkconfig_modification"
fix_audit_watch_rule "augenrules" "/etc/hosts" "wa" "audit_rules_networkconfig_modification"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/sysconfig/network" "wa" "audit_rules_networkconfig_modification"
fix_audit_watch_rule "augenrules" "/etc/sysconfig/network" "wa" "audit_rules_networkconfig_modification"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_networkconfig_modification:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_networkconfig_modification_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="file_permissions_var_log_audit" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">System Audit Logs Must Have Mode 0640 or Less Permissive</ns0:title>
          <ns0:description xml:lang="en-US">
If <html:code xmlns:html="http://www.w3.org/1999/xhtml">log_group</html:code> in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/auditd.conf</html:code> is set to a group other than the <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code>
group account, change the mode of the audit log files with the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 0640 <html:i>audit_file</html:i></html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Otherwise, change the mode of the audit log files with the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 0600 <html:i>audit_file</html:i></html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5</ns0:reference>
          <ns0:rationale xml:lang="en-US">
If users can write to audit logs, audit trails can be modified or destroyed.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="file_permissions_var_log_audit" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
if `grep -q ^log_group /etc/audit/auditd.conf` ; then
  GROUP=$(awk -F "=" '/log_group/ {print $2}' /etc/audit/auditd.conf | tr -d ' ')
  if ! [ "${GROUP}" == 'root' ] ; then
    chmod 0640 /var/log/audit/audit.log
    chmod 0440 /var/log/audit/audit.log.*
  else
    chmod 0600 /var/log/audit/audit.log
    chmod 0400 /var/log/audit/audit.log.*
  fi

  chmod 0640 /etc/audit/audit*
  chmod 0640 /etc/audit/rules.d/*
else
  chmod 0600 /var/log/audit/audit.log
  chmod 0400 /var/log/audit/audit.log.*
  chmod 0640 /etc/audit/audit*
  chmod 0640 /etc/audit/rules.d/*
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_var_log_audit:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_var_log_audit_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="file_ownership_var_log_audit" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">System Audit Logs Must Be Owned By Root</ns0:title>
          <ns0:description xml:lang="en-US">
            
    To properly set the owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root /var/log </html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-9</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">163</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000058-GPOS-00028</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.1</ns0:reference>
          <ns0:rationale xml:lang="en-US">Unauthorized disclosure of audit records can reveal system and configuration data to
attackers, thus compromising its confidentiality.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="file_ownership_var_log_audit" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
if `grep -q ^log_group /etc/audit/auditd.conf` ; then
  GROUP=$(awk -F "=" '/log_group/ {print $2}' /etc/audit/auditd.conf | tr -d ' ')
  if ! [ "${GROUP}" == 'root' ] ; then
    chown root.${GROUP} /var/log/audit
    chown root.${GROUP} /var/log/audit/audit.log*
  else
    chown root.root /var/log/audit
    chown root.root /var/log/audit/audit.log*
  fi
else
  chown root.root /var/log/audit
  chown root.root /var/log/audit/audit.log*
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_ownership_var_log_audit:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_ownership_var_log_audit_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="audit_rules_mac_modification" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Record Events that Modify the System's Mandatory Access Controls</ns0:title>
          <ns0:description xml:lang="en-US">If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the
default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the
directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /etc/selinux/ -p wa -k MAC-policy</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /etc/selinux/ -p wa -k MAC-policy</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.7</ns0:reference>
          <ns0:rationale xml:lang="en-US">The system's mandatory access policy (SELinux) should not be
arbitrarily changed by anything other than administrator action. All changes to
MAC policy should be audited.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_mac_modification" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/selinux/" "wa" "MAC-policy"
fix_audit_watch_rule "augenrules" "/etc/selinux/" "wa" "MAC-policy"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_mac_modification:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_mac_modification_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="audit_dac_actions">
          <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls</ns0:title>
          <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root.  Note that the "-F arch=b32" lines should be
present even on a 64 bit system.  These commands identify system calls for
auditing.  Even if the system is 64 bit it can still execute 32 bit system
calls.  Additionally, these rules can be configured in a number of ways while
still achieving the desired effect.  An example of this is that the "-S" calls
could be split up and placed on separate lines, however, this is less efficient.
Add the following to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S chmod -S fchmod -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
    -a always,exit -F arch=b32 -S chown -S fchown -S fchownat -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
    -a always,exit -F arch=b32 -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If your system is 64 bit then these lines should be duplicated and the
arch=b32 replaced with arch=b64 as follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S chmod -S fchmod -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
    -a always,exit -F arch=b64 -S chown -S fchown -S fchownat -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod
    -a always,exit -F arch=b64 -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
          <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is
attempting to gain access to information that would otherwise be disallowed.
Auditing DAC modifications can facilitate the identification of patterns of
abuse among both authorized and unauthorized users.</ns0:rationale>
          <ns0:Rule id="audit_rules_dac_modification_chmod" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - chmod</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to
use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup
(the default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in
the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S chmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S chmod  -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S chmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S chmod  -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_chmod" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="chmod"
	FULL_RULE="-a always,exit -F arch=$ARCH -S chmod -S fchmod -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_chmod:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_chmod_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_chown" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - chown</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to
use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup
(the default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in
the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S chown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S chown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S chown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S chown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000474-GPOS-00219</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_chown" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=${ARCH} -S .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="chown"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S chown -S fchown -S fchownat -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_chown:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_chown_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_fchmod" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - fchmod</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to
use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup
(the default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in
the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fchmod -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_fchmod" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="chmod"
	FULL_RULE="-a always,exit -F arch=$ARCH -S chmod -S fchmod -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_fchmod:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_fchmod_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_fchmodat" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - fchmodat</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to
use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup
(the default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in
the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_fchmodat" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="chmod"
	FULL_RULE="-a always,exit -F arch=$ARCH -S chmod -S fchmod -S fchmodat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_fchmodat:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_fchmodat_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_fchown" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - fchown</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured
to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
<html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000474-GPOS-00219</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_fchown" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=${ARCH} -S .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="chown"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S chown -S fchown -S fchownat -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_fchown:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_fchown_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_fchownat" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - fchownat</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured
to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
<html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fchownat -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000474-GPOS-00219</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_fchownat" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=${ARCH} -S .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="chown"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S chown -S fchown -S fchownat -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_fchownat:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_fchownat_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_fremovexattr" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - fremovexattr</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured
to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
<html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_fremovexattr" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_fremovexattr:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_fremovexattr_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_fsetxattr" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - fsetxattr</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured
to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
<html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S fsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_fsetxattr" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_fsetxattr:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_fsetxattr_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_lchown" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - lchown</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured
to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
<html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000474-GPOS-00219</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_lchown" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=${ARCH} -S .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="chown"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S chown -S fchown -S fchownat -S lchown -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_lchown:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_lchown_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_lremovexattr" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - lremovexattr</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. 
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured
to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
<html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S lremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_lremovexattr" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_lremovexattr:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_lremovexattr_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_lsetxattr" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - lsetxattr</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured
to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
<html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S lsetxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000474-GPOS-00219</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_lsetxattr" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_lsetxattr:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_lsetxattr_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_removexattr" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - removexattr</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> 
program to read audit rules during daemon startup (the default), add the 
following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S removexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_removexattr" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_removexattr:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_removexattr_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="audit_rules_dac_modification_setxattr" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Record Events that Modify the System's Discretionary Access Controls - setxattr</ns0:title>
            <ns0:description xml:lang="en-US">At a minimum the audit system should collect file permission
changes for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured
to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon
startup (the default), add the following line to a file with suffix
<html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
If the system is 64 bit then also add the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b64 -S setxattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod</html:pre>
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note that these rules can be configured in a
number of ways while still achieving the desired effect.  Here the system calls
have been placed independent of other system calls.  Grouping these system
calls with others as identifying earlier in this guide is more efficient.
</ns0:warning>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
            <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.5</ns0:reference>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
            <ns0:rationale xml:lang="en-US">The changing of file permissions could indicate that a user is attempting to
gain access to information that would otherwise be disallowed. Auditing DAC modifications
can facilitate the identification of patterns of abuse among both authorized and
unauthorized users.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="audit_rules_dac_modification_setxattr" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid&gt;=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_dac_modification_setxattr:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_dac_modification_setxattr_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Rule id="audit_rules_login_events" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Record Attempts to Alter Logon and Logout Events</ns0:title>
          <ns0:description xml:lang="en-US">The audit system already collects login information for all users
and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the
directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code> in order to watch for attempted manual
edits of files involved in storing logon events:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /var/log/tallylog -p wa -k logins
-w /var/run/faillock/ -p wa -k logins
-w /var/log/lastlog -p wa -k logins</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following lines to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file in order to watch for unattempted manual
edits of files involved in storing logon events:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /var/log/tallylog -p wa -k logins
-w /var/run/faillock/ -p wa -k logins
-w /var/log/lastlog -p wa -k logins</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2884</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000470-GPOS-00214</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000473-GPOS-00218</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.3</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.8</ns0:reference>
          <ns0:rationale xml:lang="en-US">Manual editing of these files may indicate nefarious activity, such
as an attacker attempting to remove evidence of an intrusion.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_login_events" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">

# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/var/log/tallylog" "wa" "logins"
fix_audit_watch_rule "augenrules" "/var/log/tallylog" "wa" "logins"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/var/run/faillock/" "wa" "logins"
fix_audit_watch_rule "augenrules" "/var/run/faillock/" "wa" "logins"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/var/log/lastlog" "wa" "logins"
fix_audit_watch_rule "augenrules" "/var/log/lastlog" "wa" "logins"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_login_events:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="audit_rules_session_events" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Record Attempts to Alter Process and Session Initiation Information</ns0:title>
          <ns0:description xml:lang="en-US">The audit system already collects process information for all
users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the
default), add the following lines to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the
directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code> in order to watch for attempted manual
edits of files involved in storing such process information:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /var/run/utmp -p wa -k session
-w /var/log/btmp -p wa -k session
-w /var/log/wtmp -p wa -k session</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following lines to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file in order to watch for attempted manual
edits of files involved in storing such process information:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /var/run/utmp -p wa -k session
-w /var/log/btmp -p wa -k session
-w /var/log/wtmp -p wa -k session</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.3</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.9</ns0:reference>
          <ns0:rationale xml:lang="en-US">Manual editing of these files may indicate nefarious activity, such
as an attacker attempting to remove evidence of an intrusion.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_session_events" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation
# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/var/run/utmp" "wa" "session"
fix_audit_watch_rule "augenrules" "/var/run/utmp" "wa" "session"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/var/log/btmp" "wa" "session"
fix_audit_watch_rule "augenrules" "/var/log/btmp" "wa" "session"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/var/log/wtmp" "wa" "session"
fix_audit_watch_rule "augenrules" "/var/log/wtmp" "wa" "session"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_session_events:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="audit_rules_unsuccessful_file_modification" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure auditd Collects Unauthorized Access Attempts to Files (unsuccessful)</ns0:title>
          <ns0:description xml:lang="en-US">At a minimum the audit system should collect unauthorized file
accesses for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured
to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon
startup (the default), add the following lines to a file with suffix
<html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
-a always,exit -F arch=b32 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access</html:pre>
If the system is 64 bit then also add the following lines:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">
-a always,exit -F arch=b64 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
-a always,exit -F arch=b64 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following lines to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=b32 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
-a always,exit -F arch=b32 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access</html:pre>
If the system is 64 bit then also add the following lines:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">
-a always,exit -F arch=b64 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access
-a always,exit -F arch=b64 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2884</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000064-GPOS-00033</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000458-GPOS-00203</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000461-GPOS-00205</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.4</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.1</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
          <ns0:rationale xml:lang="en-US">Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing
these events could serve as evidence of potential system compromise.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_unsuccessful_file_modification" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation of the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do

	# First fix the -EACCES requirement
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k *"
	# Use escaped BRE regex to specify rule group
	GROUP="\(creat\|open\|truncate\)"
	FULL_RULE="-a always,exit -F arch=$ARCH -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EACCES -F auid&gt;=1000 -F auid!=4294967295 -k access"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"

	# Then fix the -EPERM requirement
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k *"
	# No need to change content of $GROUP variable - it's the same as for -EACCES case above
	FULL_RULE="-a always,exit -F arch=$ARCH -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EPERM -F auid&gt;=1000 -F auid!=4294967295 -k access"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"

done
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_unsuccessful_file_modification:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_unsuccessful_file_modification_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="audit_rules_privileged_commands" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure auditd Collects Information on the Use of Privileged Commands</ns0:title>
          <ns0:description xml:lang="en-US">At a minimum the audit system should collect the execution of
privileged commands for all users and root. To find the relevant setuid /
setgid programs, run the following command for each local partition
<html:i xmlns:html="http://www.w3.org/1999/xhtml">PART</html:i>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo find <html:i>PART</html:i> -xdev -type f -perm -4000 -o -type f -perm -2000 2&gt;/dev/null</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code>
program to read audit rules during daemon startup (the default), add a line of
the following form to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code> for each setuid / setgid program on the system,
replacing the <html:i xmlns:html="http://www.w3.org/1999/xhtml">SETUID_PROG_PATH</html:i> part with the full path of that setuid /
setgid program in the list:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F path=<html:i>SETUID_PROG_PATH</html:i> -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add a line of the following
form to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> for each setuid / setgid program on the
system, replacing the <html:i xmlns:html="http://www.w3.org/1999/xhtml">SETUID_PROG_PATH</html:i> part with the full path of that
setuid / setgid program in the list:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F path=<html:i>SETUID_PROG_PATH</html:i> -F perm=x -F auid&gt;=1000 -F auid!=4294967295 -k privileged</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(4)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-6(9)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2234</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000327-GPOS-00127</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.10</ns0:reference>
          <ns0:rationale xml:lang="en-US">Misuse of privileged functions, either intentionally or unintentionally by
authorized users, or by unauthorized external entities that have compromised system accounts,
is a serious and ongoing concern and can have significant adverse impacts on organizations. 
Auditing the use of privileged functions is one way to detect such misuse and identify
the risk from insider and advanced persistent threast.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Privileged programs are subject to escalation-of-privilege attacks,
which attempt to subvert their normal role of providing some necessary but
limited capability. As such, motivation exists to monitor these programs for
unusual activity.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_privileged_commands" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_perform_audit_rules_privileged_commands_remediation" />
perform_audit_rules_privileged_commands_remediation "auditctl" "1000"
perform_audit_rules_privileged_commands_remediation "augenrules" "1000"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_privileged_commands:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_privileged_commands_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="audit_rules_media_export" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure auditd Collects Information on Exporting to Media (successful)</ns0:title>
          <ns0:description xml:lang="en-US">At a minimum the audit system should collect media exportation
events for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to
use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup
(the default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in
the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>, setting ARCH to either b32 or b64 as
appropriate for your system:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=ARCH -S mount -F auid&gt;=1000 -F auid!=4294967295 -k export</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file, setting ARCH to either b32 or b64 as
appropriate for your system:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=ARCH -S mount -F auid&gt;=1000 -F auid!=4294967295 -k export</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-3(1)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">135</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2884</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000042-GPOS-00020</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000392-GPOS-00172</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.13</ns0:reference>
          <ns0:rationale xml:lang="en-US">The unauthorized exportation of data to external media could result in an information leak
where classified information, Privacy Act information, and intellectual property could be lost. An audit
trail should be created each time a filesystem is mounted to help identify and guard against information
loss.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_media_export" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation of the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	GROUP="mount"
	FULL_RULE="-a always,exit -F arch=$ARCH -S mount -F auid&gt;=1000 -F auid!=4294967295 -k export"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_media_export:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_media_export_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="audit_rules_file_deletion_events" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure auditd Collects File Deletion Events by User</ns0:title>
          <ns0:description xml:lang="en-US">At a minimum the audit system should collect file deletion events
for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the
default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the
directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>, setting ARCH to either b32 or b64 as
appropriate for your system:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=ARCH -S rmdir -S unlink -S unlinkat -S rename -S renameat -F auid&gt;=1000 -F auid!=4294967295 -k delete</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file, setting ARCH to either b32 or b64 as
appropriate for your system:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-a always,exit -F arch=ARCH -S rmdir -S unlink -S unlinkat -S rename -S renameat -F auid&gt;=1000 -F auid!=4294967295 -k delete</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.14</ns0:reference>
          <ns0:rationale xml:lang="en-US">Auditing file deletions will create an audit trail for files that are removed
from the system. The audit trail could aid in system troubleshooting, as well as, detecting
malicious processes that attempt to delete log files to conceal their presence.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_file_deletion_events" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for the syscall rule
# Retrieve hardware architecture of the underlying system
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b32" "b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F auid&gt;=1000 -F auid!=4294967295 -k *"
	# Use escaped BRE regex to specify rule group
	GROUP="\(rmdir\|unlink\|rename\)"
	FULL_RULE="-a always,exit -F arch=$ARCH -S rmdir -S unlink -S unlinkat -S rename -S renameat -F auid&gt;=1000 -F auid!=4294967295 -k delete"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_file_deletion_events:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_file_deletion_events_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="audit_rules_sysadmin_actions" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Ensure auditd Collects System Administrator Actions</ns0:title>
          <ns0:description xml:lang="en-US">At a minimum the audit system should collect administrator actions
for all users and root. If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the default),
add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /etc/sudoers -p wa -k actions</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /etc/sudoers -p wa -k actions</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-2(7)(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">126</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.2</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.5.b</ns0:reference>
          <ns0:rationale xml:lang="en-US">The actions taken by system administrators should be audited to keep a record
of what was executed on the system, as well as, for accountability purposes.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_sysadmin_actions" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/etc/sudoers" "wa" "actions"
fix_audit_watch_rule "augenrules" "/etc/sudoers" "wa" "actions"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_sysadmin_actions:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_sysadmin_actions_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="audit_rules_kernel_module_loading" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure auditd Collects Information on Kernel Module Loading and Unloading</ns0:title>
          <ns0:description xml:lang="en-US">If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program
to read audit rules during daemon startup (the default), add the following lines to a file
with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code> to capture kernel module
loading and unloading events, setting ARCH to either b32 or b64 as appropriate for your system:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /usr/sbin/insmod -p x -k modules
-w /usr/sbin/rmmod -p x -k modules
-w /usr/sbin/modprobe -p x -k modules
-a always,exit -F arch=<html:i>ARCH</html:i> -S init_module -S delete_module -k modules</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code> utility to read audit
rules during daemon startup, add the following lines to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file
in order to capture kernel module loading and unloading events, setting ARCH to either b32 or
b64 as appropriate for your system:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-w /usr/sbin/insmod -p x -k modules
-w /usr/sbin/rmmod -p x -k modules
-w /usr/sbin/modprobe -p x -k modules
-a always,exit -F arch=<html:i>ARCH</html:i> -S init_module -S delete_module -k modules</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(7)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000471-GPOS-00216</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000477</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">GPOS-00222</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.2.7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.17</ns0:reference>
          <ns0:rationale xml:lang="en-US">The addition/removal of kernel modules can be used to alter the behavior of
the kernel and potentially introduce malicious code into kernel space. It is important
to have an audit trail of modules that have been introduced into the kernel.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_kernel_module_loading" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

# First perform the remediation of the syscall rule
# Retrieve hardware architecture of the underlying system
# Note: 32-bit kernel modules can't be loaded / unloaded on 64-bit kernel =&gt;
#       it's not required on a 64-bit system to check also for the presence
#       of 32-bit's equivalent of the corresponding rule. Therefore for
#       each system it's enought to check presence of system's native rule form.
[ $(getconf LONG_BIT) = "32" ] &amp;&amp; RULE_ARCHS=("b32") || RULE_ARCHS=("b64")

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -k *"
	# Use escaped BRE regex to specify rule group
	GROUP="\(init\|delete\)_module"
	FULL_RULE="-a always,exit -F arch=$ARCH -S init_module -S delete_module -k modules"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_syscall_rule" />
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done

# Then perform the remediations for the watch rules
# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/usr/sbin/insmod" "x" "modules"
fix_audit_watch_rule "augenrules" "/usr/sbin/insmod" "x" "modules"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/usr/sbin/rmmod" "x" "modules"
fix_audit_watch_rule "augenrules" "/usr/sbin/rmmod" "x" "modules"
<ns0:sub idref="function_fix_audit_watch_rule" />
fix_audit_watch_rule "auditctl" "/usr/sbin/modprobe" "x" "modules"
fix_audit_watch_rule "augenrules" "/usr/sbin/modprobe" "x" "modules"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_kernel_module_loading:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-audit_rules_kernel_module_loading_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="audit_rules_immutable" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Make the auditd Configuration Immutable</ns0:title>
          <ns0:description xml:lang="en-US">If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">augenrules</html:code> program to read audit rules during daemon startup (the
default), add the following line to a file with suffix <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rules</html:code> in the
directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/rules.d</html:code> in order to make the auditd configuration
immutable:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-e 2</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditd</html:code> daemon is configured to use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">auditctl</html:code>
utility to read audit rules during daemon startup, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/audit/audit.rules</html:code> file in order to make the auditd configuration
immutable:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">-e 2</html:pre>
With this setting, a reboot will be required to change any audit rules.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-1(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-2(d)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IR-5</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.5.2</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">5.2.18</ns0:reference>
          <ns0:rationale xml:lang="en-US">Making the audit configuration immutable prevents accidental as
well as malicious modification of the audit rules, although it may be
problematic if legitimate changes are needed during system
operation</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="audit_rules_immutable" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
# Traverse all of:
#
# /etc/audit/audit.rules,			(for auditctl case)
# /etc/audit/rules.d/*.rules			(for augenrules case)
#
# files to check if '-e .*' setting is present in that '*.rules' file already.
# If found, delete such occurrence since auditctl(8) manual page instructs the
# '-e 2' rule should be placed as the last rule in the configuration
find /etc/audit /etc/audit/rules.d -maxdepth 1 -type f -name *.rules -exec sed -i '/-e[[:space:]]\+.*/d' {} ';'

# Append '-e 2' requirement at the end of both:
# * /etc/audit/audit.rules file 		(for auditctl case)
# * /etc/audit/rules.d/immutable.rules		(for augenrules case)

for AUDIT_FILE in "/etc/audit/audit.rules" "/etc/audit/rules.d/immutable.rules"
do
	echo '' &gt;&gt; $AUDIT_FILE
	echo '# Set the audit.rules configuration immutable per security requirements' &gt;&gt; $AUDIT_FILE
	echo '# Reboot is required to change audit rules once this setting is applied' &gt;&gt; $AUDIT_FILE
	echo '-e 2' &gt;&gt; $AUDIT_FILE
done
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-audit_rules_immutable:def:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
  </ns0:Group>
  <ns0:Group id="services">
    <ns0:title xml:lang="en-US">Services</ns0:title>
    <ns0:description xml:lang="en-US">
The best protection against vulnerable software is running less software. This section describes how to review
the software which Red Hat Enterprise Linux 7 installs on a system and disable software which is not needed. It
then enumerates the software packages installed on a default Red Hat Enterprise Linux 7 system and provides guidance about which
ones can be safely disabled.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Red Hat Enterprise Linux 7 provides a convenient minimal install option that essentially installs the bare necessities for a functional
system. When building Red Hat Enterprise Linux 7 systems, it is highly recommended to select the minimal packages and then build up
the system from there.
</ns0:description>
    <ns0:Group id="obsolete">
      <ns0:title xml:lang="en-US">Obsolete Services</ns0:title>
      <ns0:description xml:lang="en-US">This section discusses a number of network-visible
services which have historically caused problems for system
security, and for which disabling or severely limiting the service
has been the best available guidance for some time. As a result of
this, many of these services are not installed as part of Red Hat Enterprise Linux 7
by default.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Organizations which are running these services should
switch to more secure equivalents as soon as possible.
If it remains absolutely necessary to run one of
these services for legacy reasons, care should be taken to restrict
the service as much as possible, for instance by configuring host
firewall software such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> to restrict access to the
vulnerable service to only those remote hosts which have a known
need to use it.</ns0:description>
      <ns0:Group id="inetd_and_xinetd">
        <ns0:title xml:lang="en-US">Xinetd</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">xinetd</html:code> service acts as a dedicated listener for some
network services (mostly, obsolete ones) and can be used to provide access
controls and perform some logging. It has been largely obsoleted by other
features, and it is not installed by default. The older Inetd service
is not even available as part of Red Hat Enterprise Linux 7.</ns0:description>
        <ns0:Rule id="service_xinetd_disabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable xinetd Service</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">xinetd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable xinetd.service</html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">305</ns0:reference>
          <ns0:rationale xml:lang="en-US">
The xinetd service provides a dedicated listener service for some programs,
which is no longer necessary for commonly-used network services. Disabling
it ensures that these uncommon services are not running, and also prevents
attacks against xinetd itself.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_xinetd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable xinetd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_xinetd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service xinetd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - xinetd

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_xinetd_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_xinetd_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_xinetd_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Uninstall xinetd Package</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">xinetd</html:code> package can be uninstalled with the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase xinetd</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">305</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.11</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Removing the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xinetd</html:code> package decreases the risk of the
xinetd service's accidental (or intentional) activation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_xinetd_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove xinetd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_xinetd_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure xinetd is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - xinetd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_xinetd_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_xinetd

class remove_xinetd {
  package { 'xinetd':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_xinetd_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=xinetd
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_xinetd_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_xinetd_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_tcp_wrappers_installed" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Install tcp_wrappers Package</ns0:title>
          <ns0:description xml:lang="en-US">
When network services are using the <html:code xmlns:html="http://www.w3.org/1999/xhtml">xinetd</html:code> service, the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">tcp_wrappers</html:code> package should be installed.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">tcp_wrappers</html:code> package can be installed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install tcp_wrappers</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Access control methods provide the ability to enhance system security posture
by restricting services and known good IP addresses and address ranges. This
prevents connections from unknown hosts and protocols.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_tcp_wrappers_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command install tcp_wrappers
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_tcp_wrappers_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Ensure tcp_wrappers is installed
  package:
    name="{{item}}"
    state=present
  with_items:
    - tcp_wrappers
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_tcp_wrappers_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:puppet">include install_tcp_wrappers

class install_tcp_wrappers {
  package { 'tcp_wrappers':
    ensure =&gt; 'installed',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_tcp_wrappers_installed" reboot="false" strategy="enable" system="urn:redhat:anaconda:pre">
package --add=tcp_wrappers
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_tcp_wrappers_installed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_tcp_wrappers_installed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="telnet">
        <ns0:title xml:lang="en-US">Telnet</ns0:title>
        <ns0:description xml:lang="en-US">The telnet protocol does not provide confidentiality or integrity
for information transmitted on the network. This includes authentication
information such as passwords. Organizations which use telnet should be
actively working to migrate to a more secure protocol.</ns0:description>
        <ns0:Rule id="service_telnet_disabled" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Disable telnet Service</ns0:title>
          <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">telnet</html:code> service configuration file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/xinetd.d/telnet</html:code>
is not created automatically. If it was created manually, check the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/xinetd.d/telnet</html:code> file and ensure that <html:code xmlns:html="http://www.w3.org/1999/xhtml">disable = no</html:code>
is changed to read <html:code xmlns:html="http://www.w3.org/1999/xhtml">disable = yes</html:code> as follows below:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">
# description: The telnet server serves telnet sessions; it uses \\
#       unencrypted username/password pairs for authentication.
service telnet
{
        flags           = REUSE
        socket_type     = stream

        wait            = no
        user            = root
        server          = /usr/sbin/in.telnetd
        log_on_failure  += USERID
        disable         = yes
}
</html:pre>
If the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/xinetd.d/telnet</html:code> file does not exist, make sure that
the activation of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">telnet</html:code> service on system boot is disabled
via the following command:

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rexec</html:code> socket can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable rexec.socket</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(c)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
          <ns0:rationale xml:lang="en-US">
The telnet protocol uses unencrypted network communication, which
means that data from the login session, including passwords and
all other information transmitted during the session, can be
stolen by eavesdroppers on the network. The telnet protocol is also
subject to man-in-the-middle attacks.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_telnet_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">grep -qi disable /etc/xinetd.d/telnet &amp;&amp; \
  sed -i "s/disable.*/disable         = yes/gI" /etc/xinetd.d/telnet

#
# Disable telnet.socket for all systemd targets
#
systemctl disable telnet.socket

#
# Stop telnet.socket if currently running
#
systemctl stop telnet.socket
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_telnet_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_telnet_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_telnet-server_removed" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Uninstall telnet-server Package</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">telnet-server</html:code> package can be uninstalled with
the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase telnet-server</html:pre></ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7(a)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">381</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000095-GPOS-00049</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.1</ns0:reference>
          <ns0:rationale xml:lang="en-US">
It is detrimental for operating systems to provide, or install by default, functionality exceeding
requirements or mission objectives. These unnecessary capabilities are often overlooked and therefore
may remain unsecure. They increase the risk to the platform by providing additional attack vectors.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The telnet service provides an unencrypted remote access service which does not provide for the 
confidentiality and integrity of user passwords or the remote session. If a privileged user were
to login using this service, the privileged user password could be compromised.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Removing the <html:code xmlns:html="http://www.w3.org/1999/xhtml">telnet-server</html:code> package decreases the risk of the telnet service's accidental 
(or intentional) activation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_telnet-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove telnet-server
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_telnet-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure telnet-server is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - telnet-server
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_telnet-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_telnet-server

class remove_telnet-server {
  package { 'telnet-server':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_telnet-server_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=telnet-server
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_telnet-server_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_telnet-server_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_telnet_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Remove telnet Clients</ns0:title>
          <ns0:description xml:lang="en-US">The telnet client allows users to start connections to other 
systems via the telnet protocol.</ns0:description>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.2</ns0:reference>
          <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">telnet</html:code> protocol is insecure and unencrypted. The use
of an unencrypted transmission medium could allow an unauthorized user
to steal credentials. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ssh</html:code> package provides an
encrypted session and stronger security and is included in Red Hat
Enterprise Linux.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_telnet_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove telnet
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_telnet_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure telnet is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - telnet
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_telnet_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_telnet

class remove_telnet {
  package { 'telnet':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_telnet_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=telnet
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_telnet_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_telnet_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="r_services">
        <ns0:title xml:lang="en-US">Rlogin, Rsh, and Rexec</ns0:title>
        <ns0:description xml:lang="en-US">The Berkeley r-commands are legacy services which
allow cleartext remote access and have an insecure trust
model.</ns0:description>
        <ns0:Rule id="package_rsh-server_removed" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Uninstall rsh-server Package</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsh-server</html:code> package can be uninstalled with
the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase rsh-server</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7(a)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">381</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000095-GPOS-00049</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.3</ns0:reference>
          <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsh-server</html:code> service provides unencrypted remote access service which does not
provide for the confidentiality and integrity of user passwords or the remote session and has very weak
authentication. If a privileged user were to login using this service, the privileged user password
could be compromised. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsh-server</html:code> package provides several obsolete and insecure
network services. Removing it decreases the risk of those services' accidental (or intentional)
activation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_rsh-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove rsh-server
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_rsh-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure rsh-server is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - rsh-server
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_rsh-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_rsh-server

class remove_rsh-server {
  package { 'rsh-server':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_rsh-server_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=rsh-server
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_rsh-server_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_rsh-server_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="service_rexec_disabled" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Disable rexec Service</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rexec</html:code> service, which is available with
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsh-server</html:code> package and runs as a service through xinetd or separately
as a systemd socket, should be disabled.
If using xinetd, set <html:code xmlns:html="http://www.w3.org/1999/xhtml">disable</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">yes</html:code> in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/xinetd.d/rexec</html:code>. 
If using systemd, 
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rexec</html:code> socket can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable rexec.socket</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">68</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1436</ns0:reference>
          <ns0:rationale xml:lang="en-US">The rexec service uses unencrypted network communications, which
means that data from the login session, including passwords and
all other information transmitted during the session, can be
stolen by eavesdroppers on the network.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_rexec_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">grep -qi disable /etc/xinetd.d/rexec &amp;&amp; \
  sed -i "s/disable.*/disable         = yes/gI" /etc/xinetd.d/rexec

#
# Disable rexec.socket for all systemd targets
#
systemctl disable rexec.socket

#
# Stop rexec.socket if currently running
#
systemctl stop rexec.socket
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_rexec_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_rexec_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="service_rsh_disabled" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Disable rsh Service</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsh</html:code> service, which is available with
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsh-server</html:code> package and runs as a service through xinetd or separately
as a systemd socket, should be disabled.
If using xinetd, set <html:code xmlns:html="http://www.w3.org/1999/xhtml">disable</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">yes</html:code> in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/xinetd.d/rsh</html:code>.
If using systemd, 
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsh</html:code> socket can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable rsh.socket</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(c)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">68</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1436</ns0:reference>
          <ns0:rationale xml:lang="en-US">The rsh service uses unencrypted network communications, which
means that data from the login session, including passwords and
all other information transmitted during the session, can be
stolen by eavesdroppers on the network.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_rsh_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">grep -qi disable /etc/xinetd.d/rsh &amp;&amp; \
  sed -i "s/disable.*/disable         = yes/gI" /etc/xinetd.d/rsh

#
# Disable rsh.socket for all systemd targets
#
systemctl disable rsh.socket

#
# Stop rsh.socket if currently running
#
systemctl stop rsh.socket
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_rsh_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_rsh_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_rsh_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Uninstall rsh Package</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsh</html:code> package contains the client commands
for the rsh services</ns0:description>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.4</ns0:reference>
          <ns0:rationale xml:lang="en-US">These legacy clients contain numerous security exposures and have
been replaced with the more secure SSH package. Even if the server is removed,
it is best to ensure the clients are also removed to prevent users from
inadvertently attempting to use these commands and therefore exposing
their credentials. Note that removing the <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsh</html:code> package removes
the clients for <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsh</html:code>,<html:code xmlns:html="http://www.w3.org/1999/xhtml">rcp</html:code>, and <html:code xmlns:html="http://www.w3.org/1999/xhtml">rlogin</html:code>.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_rsh_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove rsh
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_rsh_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure rsh is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - rsh
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_rsh_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_rsh

class remove_rsh {
  package { 'rsh':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_rsh_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=rsh
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_rsh_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_rsh_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="service_rlogin_disabled" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Disable rlogin Service</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rlogin</html:code> service, which is available with
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">rsh-server</html:code> package and runs as a service through xinetd or separately
as a systemd socket, should be disabled.
If using xinetd, set <html:code xmlns:html="http://www.w3.org/1999/xhtml">disable</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">yes</html:code> in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/xinetd.d/rlogin</html:code>.
If using systemd, 
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rlogin</html:code> socket can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable rlogin.socket</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(c)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1436</ns0:reference>
          <ns0:rationale xml:lang="en-US">The rlogin service uses unencrypted network communications, which
means that data from the login session, including passwords and
all other information transmitted during the session, can be
stolen by eavesdroppers on the network.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_rlogin_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">grep -qi disable /etc/xinetd.d/rlogin &amp;&amp; \
  sed -i "s/disable.*/disable         = yes/gI" /etc/xinetd.d/rlogin

#
# Disable rlogin.socket for all systemd targets
#
systemctl disable rlogin.socket

#
# Stop rlogin.socket if currently running
#
systemctl stop rlogin.socket
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_rlogin_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_rlogin_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="no_rsh_trust_files" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Remove Rsh Trust Files</ns0:title>
          <ns0:description xml:lang="en-US">The files <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/hosts.equiv</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">~/.rhosts</html:code> (in
each user's home directory) list remote hosts and users that are trusted by the
local system when using the rshd daemon.
To remove these files, run the following command to delete them from any
location:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo rm /etc/hosts.equiv</html:pre>
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ rm ~/.rhosts</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1436</ns0:reference>
          <ns0:rationale xml:lang="en-US">Trust files are convenient, but when
used in conjunction with the R-services, they can allow
unauthenticated access to a system.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="no_rsh_trust_files" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">find -type f -name .rhosts -exec rm -f '{}' \;
rm /etc/hosts.equiv
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-no_rsh_trust_files:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-no_rsh_trust_files_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="nis">
        <ns0:title xml:lang="en-US">NIS</ns0:title>
        <ns0:description xml:lang="en-US">The Network Information Service (NIS), also known as 'Yellow
Pages' (YP), and its successor NIS+ have been made obsolete by
Kerberos, LDAP, and other modern centralized authentication
services. NIS should not be used because it suffers from security
problems inherent in its design, such as inadequate protection of
important authentication information.</ns0:description>
        <ns0:Rule id="package_ypserv_removed" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Uninstall ypserv Package</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ypserv</html:code> package can be uninstalled with
the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase ypserv</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7(a)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">381</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000095-GPOS-00049</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.6</ns0:reference>
          <ns0:rationale xml:lang="en-US">The NIS service provides an unencrypted authentication service which does not
provide for the confidentiality and integrity of user passwords or the remote session.

Removing the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ypserv</html:code> package decreases the risk of the accidental (or intentional) 
activation of NIS or NIS+ services.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_ypserv_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove ypserv
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_ypserv_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure ypserv is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - ypserv
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_ypserv_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_ypserv

class remove_ypserv {
  package { 'ypserv':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_ypserv_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=ypserv
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_ypserv_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_ypserv_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="service_ypbind_disabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable ypbind Service</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ypbind</html:code> service, which allows the system to act as a client in
a NIS or NIS+ domain, should be disabled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ypbind</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable ypbind.service</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">305</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Disabling the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ypbind</html:code> service ensures the system is not acting
as a client in a NIS or NIS+ domain.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_ypbind_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable ypbind
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_ypbind_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service ypbind
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - ypbind

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_ypbind_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_ypbind_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_ypbind_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Remove NIS Client</ns0:title>
          <ns0:description xml:lang="en-US">The Network Information Service (NIS), formerly known as Yellow Pages,
is a client-server directory service protocol used to distribute system configuration
files. The NIS client (<html:code xmlns:html="http://www.w3.org/1999/xhtml">ypbind</html:code>) was used to bind a machine to an NIS server
and receive the distributed configuration files.</ns0:description>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.5</ns0:reference>
          <ns0:rationale xml:lang="en-US">The NIS service is inherently an insecure system that has been vulnerable
to DOS attacks, buffer overflows and has poor authentication for querying NIS maps.
NIS generally has been replaced by such protocols as Lightweight Directory Access 
Protocol (LDAP). It is recommended that the service be removed.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_ypbind_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove ypbind
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_ypbind_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure ypbind is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - ypbind
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_ypbind_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_ypbind

class remove_ypbind {
  package { 'ypbind':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_ypbind_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=ypbind
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_ypbind_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_ypbind_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="tftp">
        <ns0:title xml:lang="en-US">TFTP Server</ns0:title>
        <ns0:description xml:lang="en-US">
TFTP is a lightweight version of the FTP protocol which has
traditionally been used to configure networking equipment. However,
TFTP provides little security, and modern versions of networking
operating systems frequently support configuration via SSH or other
more secure protocols. A TFTP server should be run only if no more
secure method of supporting existing equipment can be
found.</ns0:description>
        <ns0:Rule id="service_tftp_disabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable tftp Service</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp</html:code> service should be disabled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable tftp.service</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1436</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Disabling the <html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp</html:code> service ensures the system is not acting
as a TFTP server, which does not provide encryption or authentication.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_tftp_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_tftp_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_tftp-server_removed" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Uninstall tftp-server Package</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp-server</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase tftp-server</html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">318</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">368</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1812</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1813</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1814</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.8</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Removing the <html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp-server</html:code> package decreases the risk of the
accidental (or intentional) activation of tftp services.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If TFTP is required for operational support (such as transmission of router configurations),
its use must be documented with the Information Systems Securty Manager (ISSM), restricted to 
only authorized personnel, and have access control rules established.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_tftp-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove tftp-server
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_tftp-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure tftp-server is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - tftp-server
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_tftp-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_tftp-server

class remove_tftp-server {
  package { 'tftp-server':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_tftp-server_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=tftp-server
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_tftp-server_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_tftp-server_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_tftp_removed" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Remove tftp Daemon</ns0:title>
          <ns0:description xml:lang="en-US">Trivial File Transfer Protocol (TFTP) is a simple file transfer protocol,
typically used to automatically transfer configuration or boot files between machines.
TFTP does not support authentication and can be easily hacked. The package
<html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp</html:code> is a client program that allows for connections to a <html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp</html:code> server.
</ns0:description>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.7</ns0:reference>
          <ns0:rationale xml:lang="en-US">It is recommended that TFTP be removed, unless there is a specific need
for TFTP (such as a boot server). In that case, use extreme caution when configuring
the services.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_tftp_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_tftp_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="tftpd_uses_secure_mode" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure tftp Daemon Uses Secure Mode</ns0:title>
          <ns0:description xml:lang="en-US">If running the <html:code xmlns:html="http://www.w3.org/1999/xhtml">tftp</html:code> service is necessary, it should be configured
to change its root directory at startup. To do so, ensure
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/xinetd.d/tftp</html:code> includes <html:code xmlns:html="http://www.w3.org/1999/xhtml">-s</html:code> as a command line argument, as shown in
the following example (which is also the default):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">server_args = -s /var/lib/tftpboot</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">Using the <html:code xmlns:html="http://www.w3.org/1999/xhtml">-s</html:code> option causes the TFTP service to only serve files from the
given directory. Serving files from an intentionally-specified directory
reduces the risk of sharing files which should remain private.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-tftpd_uses_secure_mode:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-tftpd_uses_secure_mode_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="talk">
        <ns0:title xml:lang="en-US">Chat/Messaging Services</ns0:title>
        <ns0:description xml:lang="en-US">
The talk software makes it possible for users to send and receive messages
across systems through a terminal session.
</ns0:description>
        <ns0:Rule id="package_talk-server_removed" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Uninstall talk-server Package</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">talk-server</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase talk-server</html:pre>
          </ns0:description>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.10</ns0:reference>
          <ns0:rationale xml:lang="en-US">
The talk software presents a security risk as it uses unencrypted protocols
for communications. Removing the <html:code xmlns:html="http://www.w3.org/1999/xhtml">talk-server</html:code> package decreases the
risk of the accidental (or intentional) activation of talk services.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_talk-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove talk-server
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_talk-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure talk-server is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - talk-server
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_talk-server_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_talk-server

class remove_talk-server {
  package { 'talk-server':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_talk-server_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=talk-server
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_talk-server_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_talk-server_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_talk_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Uninstall talk Package</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">talk</html:code> package contains the client program for the
Internet talk protocol, which allows the user to chat with other users on
different systems. Talk is a communication program which copies lines from one
terminal to the terminal of another user.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">talk</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase talk</html:pre>
</ns0:description>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.9</ns0:reference>
          <ns0:rationale xml:lang="en-US">
The talk software presents a security risk as it uses unencrypted protocols
for communications. Removing the <html:code xmlns:html="http://www.w3.org/1999/xhtml">talk</html:code> package decreases the
risk of the accidental (or intentional) activation of talk client program.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_talk_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove talk
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_talk_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure talk is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - talk
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_talk_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_talk

class remove_talk {
  package { 'talk':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_talk_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=talk
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_talk_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_talk_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="base">
      <ns0:title xml:lang="en-US">Base Services</ns0:title>
      <ns0:description xml:lang="en-US">This section addresses the base services that are installed on a
Red Hat Enterprise Linux 7 default installation which are not covered in other
sections. Some of these services listen on the network and
should be treated with particular discretion. Other services are local
system utilities that may or may not be extraneous. In general, system services
should be disabled if not required.</ns0:description>
      <ns0:Rule id="service_abrtd_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Automatic Bug Reporting Tool (abrtd)</ns0:title>
        <ns0:description xml:lang="en-US">The Automatic Bug Reporting Tool (<html:code xmlns:html="http://www.w3.org/1999/xhtml">abrtd</html:code>) daemon collects
and reports crash data when an application crash is detected. Using a variety
of plugins, abrtd can email crash reports to system administrators, log crash
reports to files, or forward crash reports to a centralized issue tracking
system such as RHTSupport.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">abrtd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable abrtd.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
        <ns0:rationale xml:lang="en-US"> Mishandling crash data could expose sensitive information about
vulnerabilities in software executing on the local machine, as well as sensitive
information from within a process's address space or registers.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_abrtd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable abrtd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_abrtd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service abrtd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - abrtd

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_abrtd_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_abrtd_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_acpid_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Advanced Configuration and Power Interface (acpid)</ns0:title>
        <ns0:description xml:lang="en-US">The Advanced Configuration and Power Interface Daemon (<html:code xmlns:html="http://www.w3.org/1999/xhtml">acpid</html:code>)
dispatches ACPI events (such as power/reset button depressed) to userspace
programs.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">acpid</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable acpid.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">ACPI support is highly desirable for systems in some network roles,
such as laptops or desktops. For other systems, such as servers, it may permit
accidental or trivially achievable denial of service situations and disabling
it is appropriate.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_acpid_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable acpid
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_acpid_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service acpid
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - acpid

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_acpid_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_acpid_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_certmonger_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Certmonger Service (certmonger)</ns0:title>
        <ns0:description xml:lang="en-US">Certmonger is a D-Bus based service that attempts to simplify interaction
with certifying authorities on networks which use public-key infrastructure. It is often
combined with Red Hat's IPA (Identity Policy Audit) security information management
solution to aid in the management of certificates.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">certmonger</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable certmonger.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">The services provided by certmonger may be essential for systems
fulfilling some roles a PKI infrastructure, but its functionality is not necessary
for many other use cases.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_certmonger_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable certmonger
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_certmonger_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service certmonger
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - certmonger

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_certmonger_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_certmonger_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_cgconfig_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Control Group Config (cgconfig)</ns0:title>
        <ns0:description xml:lang="en-US">Control groups allow an administrator to allocate system resources (such as CPU,
memory, network bandwidth, etc) among a defined group (or groups) of processes executing on
a system. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cgconfig</html:code> daemon starts at boot and establishes the predefined control groups.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cgconfig</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable cgconfig.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">Unless control groups are used to manage system resources, running the cgconfig
service is not necessary.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_cgconfig_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable cgconfig
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_cgconfig_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service cgconfig
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - cgconfig

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_cgconfig_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_cgconfig_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_cgred_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Control Group Rules Engine (cgred)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cgred</html:code> service moves tasks into control groups according to
parameters set in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/cgrules.conf</html:code> configuration file.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cgred</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable cgred.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">Unless control groups are used to manage system resources, running the cgred service
service is not necessary.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_cgred_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable cgred
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_cgred_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service cgred
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - cgred

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_cgred_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_cgred_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_cpupower_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable CPU Speed (cpupower)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cpupower</html:code> service can adjust the clock speed of supported CPUs based upon
the current processing load thereby conserving power and reducing heat.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cpupower</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable cpupower.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cpupower</html:code> service is only necessary if adjusting the CPU clock speed
provides benefit. Traditionally this has included laptops (to enhance battery life),
but may also apply to server or desktop environments where conserving power is
highly desirable or necessary.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_cpupower_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_cpupower_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_irqbalance_enabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Enable IRQ Balance (irqbalance)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">irqbalance</html:code> service optimizes the balance between
power savings and performance through distribution of hardware interrupts across
multiple processors.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">irqbalance</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable irqbalance.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">In an environment with multiple processors (now common), the irqbalance service
provides potential speedups for handling interrupt requests.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_irqbalance_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command enable irqbalance
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_irqbalance_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Enable service irqbalance
  service:
    name="{{item}}"
    enabled="yes"
    state="started"
  with_items:
    - irqbalance

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_irqbalance_enabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_irqbalance_enabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_kdump_disabled" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Disable KDump Kernel Crash Analyzer (kdump)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">kdump</html:code> service provides a kernel crash dump analyzer. It uses the <html:code xmlns:html="http://www.w3.org/1999/xhtml">kexec</html:code>
system call to boot a secondary kernel ("capture" kernel) following a system
crash, which can load information from the crashed kernel for analysis.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">kdump</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable kdump.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
        <ns0:rationale xml:lang="en-US">
Kernel core dumps may contain the full contents of system memory at the time of the crash.
Kernel core dumps consume a considerable amount of disk space and may result in denial of 
service by exhausting the available space on the target file system partition.
Unless the system is used for kernel development or testing, there
is little need to run the kdump service.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_kdump_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable kdump
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_kdump_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service kdump
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - kdump

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_kdump_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_kdump_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_mdmonitor_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Software RAID Monitor (mdmonitor)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">mdmonitor</html:code> service is used for monitoring a software RAID array; hardware
RAID setups do not use this service.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">mdmonitor</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable mdmonitor.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">If software RAID monitoring is not required,
there is no need to run this service.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_mdmonitor_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable mdmonitor
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_mdmonitor_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service mdmonitor
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - mdmonitor

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_mdmonitor_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_mdmonitor_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_messagebus_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable D-Bus IPC Service (messagebus)</ns0:title>
        <ns0:description xml:lang="en-US">D-Bus provides an IPC mechanism used by 
a growing list of programs, such as those used for Gnome, Bluetooth, and Avahi.
Due to these dependencies, disabling D-Bus may not be practical for
many systems.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">messagebus</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable messagebus.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">If no services which require D-Bus are needed, then it
can be disabled. As a broker for IPC between processes of different privilege levels,
it could be a target for attack. However, disabling D-Bus is likely to be
impractical for any system which needs to provide
a graphical login session.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_messagebus_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable messagebus
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_messagebus_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service messagebus
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - messagebus

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_messagebus_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_messagebus_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_netconsole_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Network Console (netconsole)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">netconsole</html:code> service is responsible for loading the
netconsole kernel module, which logs kernel printk messages over UDP to a
syslog server. This allows debugging of problems where disk logging fails and
serial consoles are impractical.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">netconsole</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable netconsole.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">381</ns0:reference>
        <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">netconsole</html:code> service is not necessary unless there is a need to debug
kernel panics, which is not common.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_netconsole_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable netconsole
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_netconsole_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service netconsole
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - netconsole

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_netconsole_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_netconsole_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_ntpdate_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable ntpdate Service (ntpdate)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpdate</html:code> service sets the local hardware clock by polling NTP servers
when the system boots. It synchronizes to the NTP servers listed in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ntp/step-tickers</html:code> or <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ntp.conf</html:code>
and then sets the local hardware clock to the newly synchronized
system time.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpdate</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable ntpdate.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">382</ns0:reference>
        <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpdate</html:code> service may only be suitable for systems which
are rebooted frequently enough that clock drift does not cause problems between
reboots. In any event, the functionality of the ntpdate service is now
available in the ntpd program and should be considered deprecated.</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_ntpdate_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_ntpdate_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_oddjobd_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Odd Job Daemon (oddjobd)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">oddjobd</html:code> service exists to provide an interface and
access control mechanism through which
specified privileged tasks can run tasks for unprivileged client
applications. Communication with <html:code xmlns:html="http://www.w3.org/1999/xhtml">oddjobd</html:code> through the system message bus.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">oddjobd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable oddjobd.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">381</ns0:reference>
        <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">oddjobd</html:code> service may provide necessary functionality in
some environments, and can be disabled if it is not needed. Execution of
tasks by privileged programs, on behalf of unprivileged ones, has traditionally
been a source of privilege escalation security issues.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_oddjobd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable oddjobd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_oddjobd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service oddjobd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - oddjobd

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_oddjobd_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_oddjobd_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_portreserve_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Portreserve (portreserve)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">portreserve</html:code> service is a TCP port reservation utility that can
be used to prevent portmap from binding to well known TCP ports that are
required for other services.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">portreserve</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable portreserve.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">portreserve</html:code> service provides helpful functionality by
preventing conflicting usage of ports in the reserved port range, but it can be
disabled if not needed.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_portreserve_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable portreserve
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_portreserve_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service portreserve
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - portreserve

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_portreserve_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_portreserve_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_psacct_enabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Enable Process Accounting (psacct)</ns0:title>
        <ns0:description xml:lang="en-US">The process accounting service, <html:code xmlns:html="http://www.w3.org/1999/xhtml">psacct</html:code>, works with programs
including <html:code xmlns:html="http://www.w3.org/1999/xhtml">acct</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">ac</html:code> to allow system administrators to view
user activity, such as commands issued by users of the system.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">psacct</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable psacct.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">psacct</html:code> service can provide administrators a convenient
view into some user activities. However, it should be noted that the auditing
system and its audit records provide more authoritative and comprehensive
records.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_psacct_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command enable psacct
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_psacct_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Enable service psacct
  service:
    name="{{item}}"
    enabled="yes"
    state="started"
  with_items:
    - psacct

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_psacct_enabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_psacct_enabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_qpidd_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Apache Qpid (qpidd)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">qpidd</html:code> service provides high speed, secure,
guaranteed delivery services.  It is an implementation of the Advanced Message
Queuing Protocol.  By default the qpidd service will bind to port 5672 and
listen for connection attempts.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">qpidd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable qpidd.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">382</ns0:reference>
        <ns0:rationale xml:lang="en-US">The qpidd service is automatically installed when the "base" 
package selection is selected during installation.  The qpidd service listens 
for network connections, which increases the attack surface of the system.  If 
the system is not intended to receive AMQP traffic, then the <html:code xmlns:html="http://www.w3.org/1999/xhtml">qpidd</html:code> 
service is not needed and should be disabled or removed.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_qpidd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable qpidd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_qpidd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service qpidd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - qpidd

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_qpidd_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_qpidd_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_quota_nld_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Quota Netlink (quota_nld)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">quota_nld</html:code> service provides notifications to
users of disk space quota violations. It listens to the kernel via a netlink
socket for disk quota violations and notifies the appropriate user of the
violation using D-Bus or by sending a message to the terminal that the user has
last accessed.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">quota_nld</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable quota_nld.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">If disk quotas are enforced on the local system, then the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">quota_nld</html:code> service likely provides useful functionality and should
remain enabled. However, if disk quotas are not used or user notification of
disk quota violation is not desired then there is no need to run this
service.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_quota_nld_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable quota_nld
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_quota_nld_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service quota_nld
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - quota_nld

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_quota_nld_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_quota_nld_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_rdisc_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Network Router Discovery Daemon (rdisc)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rdisc</html:code> service implements the client side of the ICMP
Internet Router Discovery Protocol (IRDP), which allows discovery of routers on
the local subnet. If a router is discovered then the local routing table is
updated with a corresponding default route. By default this daemon is disabled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rdisc</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable rdisc.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-4</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">382</ns0:reference>
        <ns0:rationale xml:lang="en-US">General-purpose systems typically have their network and routing
information configured statically by a system administrator. Workstations or
some special-purpose systems often use DHCP (instead of IRDP) to retrieve
dynamic network configuration information.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_rdisc_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable rdisc
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_rdisc_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service rdisc
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - rdisc

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_rdisc_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_rdisc_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_rhnsd_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Red Hat Network Service (rhnsd)</ns0:title>
        <ns0:description xml:lang="en-US">The Red Hat Network service automatically queries Red Hat Network
servers to determine whether there are any actions that should be executed,
such as package updates. This only occurs if the system was registered to an
RHN server or satellite and managed as such.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rhnsd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable rhnsd.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">382</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">1.2.4</ns0:reference>
        <ns0:rationale xml:lang="en-US">Although systems management and patching is extremely important to
system security, management by a system outside the enterprise enclave is not
desirable for some environments.  However, if the system is being managed by RHN or
 RHN Satellite Server the <html:code xmlns:html="http://www.w3.org/1999/xhtml">rhnsd</html:code> daemon can remain on. </ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_rhnsd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable rhnsd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_rhnsd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service rhnsd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - rhnsd

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_rhnsd_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_rhnsd_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_rhsmcertd_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Red Hat Subscription Manager Daemon (rhsmcertd)</ns0:title>
        <ns0:description xml:lang="en-US">The Red Hat Subscription Manager (rhsmcertd) periodically checks for
changes in the entitlement certificates for a registered system and updates it
accordingly.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rhsmcertd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable rhsmcertd.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rhsmcertd</html:code> service can provide administrators with some
additional control over which of their systems are entitled to particular
subscriptions. However, for systems that are managed locally or which are not
expected to require remote changes to their subscription status, it is
unnecessary and can be disabled.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_rhsmcertd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable rhsmcertd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_rhsmcertd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service rhsmcertd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - rhsmcertd

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_rhsmcertd_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_rhsmcertd_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_saslauthd_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable Cyrus SASL Authentication Daemon (saslauthd)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">saslauthd</html:code> service handles plaintext authentication requests on
behalf of the SASL library. The service isolates all code requiring superuser
privileges for SASL authentication into a single process, and can also be used
to provide proxy authentication services to clients that do not understand SASL
based authentication.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">saslauthd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable saslauthd.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8)</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">saslauthd</html:code> service provides essential functionality for
performing authentication in some directory environments, such as those which
use Kerberos and LDAP. For others, however, in which only local files may be
consulted, it is not necessary and should be disabled.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_saslauthd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable saslauthd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_saslauthd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service saslauthd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - saslauthd

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_saslauthd_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_saslauthd_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_smartd_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable SMART Disk Monitoring Service (smartd)</ns0:title>
        <ns0:description xml:lang="en-US">SMART (Self-Monitoring, Analysis, and Reporting Technology) is a
feature of hard drives that allows them to detect symptoms of disk failure and
relay an appropriate warning.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">smartd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable smartd.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">SMART can help protect against denial of
service due to failing hardware. Nevertheless, if it is not needed or the
system's drives are not SMART-capable (such as solid state drives), it can be
disabled.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_smartd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable smartd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_smartd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service smartd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - smartd

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_smartd_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_smartd_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_sysstat_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable System Statistics Reset Service (sysstat)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">sysstat</html:code> service resets various I/O and CPU
performance statistics to zero in order to begin counting from a fresh state
at boot time.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">sysstat</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable sysstat.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">By default the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sysstat</html:code> service merely runs a program at
boot to reset the statistics, which can be retrieved using programs such as
<html:code xmlns:html="http://www.w3.org/1999/xhtml">sar</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">sadc</html:code>. These may provide useful insight into system
operation, but unless used this service can be disabled.</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_sysstat_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable sysstat
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_sysstat_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service sysstat
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - sysstat

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_sysstat_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_sysstat_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
    </ns0:Group>
    <ns0:Group id="cron_and_at">
      <ns0:title xml:lang="en-US">Cron and At Daemons</ns0:title>
      <ns0:description xml:lang="en-US">The cron and at services are used to allow commands to
be executed at a later time. The cron service is required by almost
all systems to perform necessary maintenance tasks, while at may or
may not be required on a given system. Both daemons should be
configured defensively.</ns0:description>
      <ns0:Rule id="service_crond_enabled" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Enable cron Service</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">crond</html:code> service is used to execute commands at
preconfigured times. It is required by almost all systems to perform necessary
maintenance tasks, such as notifying root of system activity.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">crond</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable crond.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.1.2</ns0:reference>
        <ns0:rationale xml:lang="en-US">Due to its usage for maintenance and security-supporting tasks,
enabling the cron daemon is essential.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_crond_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command enable crond
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_crond_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Enable service crond
  service:
    name="{{item}}"
    enabled="yes"
    state="started"
  with_items:
    - crond

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_crond_enabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_crond_enabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="disable_anacron" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable anacron Service</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cronie-anacron</html:code> package, which provides <html:code xmlns:html="http://www.w3.org/1999/xhtml">anacron</html:code>
functionality, is installed by default. 

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cronie-anacron</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase cronie-anacron</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">anacron</html:code> service provides <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron</html:code> functionality for systems
such as laptops and workstations that may be shut down during the normal times
that <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron</html:code> jobs are scheduled to run. On systems which do not require this
additional functionality, <html:code xmlns:html="http://www.w3.org/1999/xhtml">anacron</html:code> could needlessly increase the possible
attack surface for an intruder.
</ns0:rationale>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-disable_anacron_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_atd_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable At Service (atd)</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">at</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">batch</html:code> commands can be used to
schedule tasks that are meant to be executed only once. This allows delayed
execution in a manner similar to cron, except that it is not
recurring. The daemon <html:code xmlns:html="http://www.w3.org/1999/xhtml">atd</html:code> keeps track of tasks scheduled via
<html:code xmlns:html="http://www.w3.org/1999/xhtml">at</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">batch</html:code>, and executes them at the specified time.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">atd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable atd.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">381</ns0:reference>
        <ns0:rationale xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">atd</html:code> service could be used by an unsophisticated insider to carry
out activities outside of a normal login session, which could complicate
accountability. Furthermore, the need to schedule tasks with <html:code xmlns:html="http://www.w3.org/1999/xhtml">at</html:code> or
<html:code xmlns:html="http://www.w3.org/1999/xhtml">batch</html:code> is not common.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_atd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable atd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_atd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service atd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - atd

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_atd_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_atd_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Group id="restrict_at_cron_users">
        <ns0:title xml:lang="en-US">Restrict at and cron to Authorized Users if Necessary</ns0:title>
        <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/cron.allow</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/at.allow</html:code> files contain lists of
users who are allowed to use <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron</html:code> and at to delay execution of
processes. If these files exist and if the corresponding files
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/cron.deny</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/at.deny</html:code> do not exist, then only users
listed in the relevant allow files can run the crontab and <html:code xmlns:html="http://www.w3.org/1999/xhtml">at</html:code> commands
to submit jobs to be run at scheduled intervals. On many systems, only the
system administrator needs the ability to schedule jobs. Note that even if a
given user is not listed in <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron.allow</html:code>, cron jobs can still be run as
that user. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron.allow</html:code> file controls only administrative access
to the crontab command for scheduling and modifying cron jobs.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To restrict <html:code xmlns:html="http://www.w3.org/1999/xhtml">at</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">cron</html:code> to only authorized users:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>Remove the <html:code>cron.deny</html:code> file:<html:pre>$ sudo rm /etc/cron.deny</html:pre></html:li><html:li>Edit <html:code>/etc/cron.allow</html:code>, adding one line for each user allowed to use
the crontab command to create cron jobs.</html:li><html:li>Remove the <html:code>at.deny</html:code> file:<html:pre>$ sudo rm /etc/at.deny</html:pre></html:li><html:li>Edit <html:code>/etc/at.allow</html:code>, adding one line for each user allowed to use
the at command to create at jobs.</html:li></html:ul>
</ns0:description>
        <ns0:Rule id="file_owner_cron_allow" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Verify User Who Owns /etc/cron.allow file</ns0:title>
          <ns0:description xml:lang="en-US">
If <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/cron.allow</html:code> exists, it must be owned by <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code>.

    To properly set the owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/cron.allow</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root /etc/cron.allow </html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">If the owner of the cron.allow file is not set to root, the possibility exists for an
unauthorized user to view or edit sensitive information.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_owner_cron_allow:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_owner_cron_allow_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="file_groupowner_cron_allow" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Verify Group Who Owns /etc/cron.allow file</ns0:title>
          <ns0:description xml:lang="en-US">
If <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/cron.allow</html:code> exists, it must be group-owned by <html:code xmlns:html="http://www.w3.org/1999/xhtml">root</html:code>.

    To properly set the group owner of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/cron.allow</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chgrp root /etc/cron.allow </html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">If the owner of the cron.allow file is not set to root, the possibility exists for an
unauthorized user to view or edit sensitive information.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_groupowner_cron_allow:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_groupowner_cron_allow_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="docker">
      <ns0:title xml:lang="en-US">Docker Service</ns0:title>
      <ns0:description xml:lang="en-US">
  The docker service is necessary to create containers, which are
  self-sufficient and self-contained applications using the resource
  isolation features of the kernel.
</ns0:description>
      <ns0:Rule id="service_docker_enabled" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Enable the Docker service</ns0:title>
        <ns0:description xml:lang="en-US">The docker service is commonly needed to
  create containers.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">docker</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable docker.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf" />
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx" />
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx" />
        <ns0:rationale xml:lang="en-US">
To be able to find any problems with misconfiguration of
the docker daemon and running containers, the docker service
has to be enabled.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_docker_enabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_docker_enabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="docker_storage_configured" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Use direct-lvm with the Device Mapper Storage Driver</ns0:title>
        <ns0:description xml:lang="en-US">
To use Docker in production with the device mapper storage driver, the Docker
daemon should be configured to use direct-lvm instead of loopback device as
a storage. For setting up the LVM and configuring Docker, see the
<html:a href="https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/" xmlns:html="http://www.w3.org/1999/xhtml">Docker Device Mapper Storage Documentation</html:a>.
</ns0:description>
        <ns0:rationale xml:lang="en-US">
For using Docker in production, the device mapper storage driver with loopback
devices is discouraged. The suggested way of configuring device mapper storage
driver is direct-lvm. Choosing the right storage driver and backing filesystem
is crucial to stability and performance.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-docker_storage_configured:def:1" />
        </ns0:check>
      </ns0:Rule>
    </ns0:Group>
    <ns0:Group id="ssh">
      <ns0:title xml:lang="en-US">SSH Server</ns0:title>
      <ns0:description xml:lang="en-US">The SSH protocol is recommended for remote login and
remote file transfer. SSH provides confidentiality and integrity
for data exchanged between two systems, as well as server
authentication, through the use of public key cryptography. The
implementation included with the system is called OpenSSH, and more
detailed documentation is available from its website,
<html:a href="http://www.openssh.org" xmlns:html="http://www.w3.org/1999/xhtml">http://www.openssh.org</html:a>. Its server program 
is called <html:code xmlns:html="http://www.w3.org/1999/xhtml">sshd</html:code> and provided by the RPM package
<html:code xmlns:html="http://www.w3.org/1999/xhtml">openssh-server</html:code>.</ns0:description>
      <ns0:Value id="sshd_idle_timeout_value" operator="equals" type="number">
        <ns0:title xml:lang="en-US">SSH session Idle time</ns0:title>
        <ns0:description xml:lang="en-US">Specify duration of allowed idle time.</ns0:description>
        <ns0:value>300</ns0:value>
        <ns0:value selector="5_minutes">300</ns0:value>
        <ns0:value selector="10_minutes">600</ns0:value>
        <ns0:value selector="15_minutes">900</ns0:value>
        <ns0:value selector="60_minutes">3600</ns0:value>
        <ns0:value selector="120_minutes">7200</ns0:value>
      </ns0:Value>
      <ns0:Value id="sshd_listening_port" operator="equals" type="number">
        <ns0:title xml:lang="en-US">SSH Server Listening Port</ns0:title>
        <ns0:description xml:lang="en-US">Specify port the SSH server is listening.</ns0:description>
        <ns0:value>22</ns0:value>
        <ns0:value selector="default">22</ns0:value>
      </ns0:Value>
      <ns0:Rule id="package_openssh-server_installed" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Install the OpenSSH Server Package</ns0:title>
        <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">openssh-server</html:code> package should be installed.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">openssh-server</html:code> package can be installed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install openssh-server</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-8</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2418</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2420</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2421</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2422</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000423-GPOS-00187</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000423-GPOS-00188</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000423-GPOS-00189</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS000423-GPOS-00190</ns0:reference>
        <ns0:rationale xml:lang="en-US">
Without protection of the transmitted information, confidentiality, and
integrity may be compromised because unprotected communications can be
intercepted and either read or altered.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="package_openssh-server_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command install openssh-server
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="package_openssh-server_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Ensure openssh-server is installed
  package:
    name="{{item}}"
    state=present
  with_items:
    - openssh-server
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="package_openssh-server_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:puppet">include install_openssh-server

class install_openssh-server {
  package { 'openssh-server':
    ensure =&gt; 'installed',
  }
}
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="package_openssh-server_installed" reboot="false" strategy="enable" system="urn:redhat:anaconda:pre">
package --add=openssh-server
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_openssh-server_installed:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_openssh-server_installed_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_sshd_enabled" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Enable the OpenSSH Service</ns0:title>
        <ns0:description xml:lang="en-US">The SSH server service, sshd, is commonly needed.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">sshd</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable sshd.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-8</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2418</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2420</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2421</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2422</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000423-GPOS-00187</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000423-GPOS-00188</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000423-GPOS-00189</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS000423-GPOS-00190</ns0:reference>
        <ns0:rationale xml:lang="en-US">
Without protection of the transmitted information, confidentiality, and
integrity may be compromised because unprotected communications can be
intercepted and either read or altered.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
This checklist item applies to both internal and external networks and all types
of information system components from which information can be transmitted (e.g., servers,
mobile devices, notebook computers, printers, copiers, scanners, etc). Communication paths
outside the physical protection of a controlled boundary are exposed to the possibility
of interception and modification.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_sshd_enabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_sshd_enabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_sshd_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable SSH Server If Possible (Unusual)</ns0:title>
        <ns0:description xml:lang="en-US">The SSH server service, sshd, is commonly needed.
However, if it can be disabled, do so.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">sshd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable sshd.service</html:pre>
This is unusual, as SSH is a common method for encrypted and authenticated
remote access.
</ns0:description>
        <ns0:fix complexity="low" disruption="low" id="service_sshd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable sshd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_sshd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service sshd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - sshd

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_sshd_disabled:def:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="file_permissions_sshd_pub_key" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Verify Permissions on SSH Server Public *.pub Key Files</ns0:title>
        <ns0:description xml:lang="en-US">
          
    To properly set the permissions of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/*.pub</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 0644 /etc/ssh/*.pub</html:pre>
        </ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
        <ns0:rationale xml:lang="en-US">
If a public host key file is modified by an unauthorized user, the SSH service
may be compromised.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="file_permissions_sshd_pub_key" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
chmod 0644 /etc/ssh/*.pub
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="file_permissions_sshd_pub_key" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include ssh_public_key_perms

class ssh_public_key_perms {
  exec { 'sshd_pub_key':
    command =&gt; "chmod 0644 /etc/ssh/*.pub",
    path    =&gt; '/bin:/usr/bin'
  }
}
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_sshd_pub_key:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_sshd_pub_key_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="file_permissions_sshd_private_key" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Verify Permissions on SSH Server Private *_key Key Files</ns0:title>
        <ns0:description xml:lang="en-US">
          
    To properly set the permissions of <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/*_key</html:code>, run the command:
    <html:pre xml:space="preserve" xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 0640 /etc/ssh/*_key</html:pre>
        </ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
        <ns0:rationale xml:lang="en-US">
If an unauthorized user obtains the private SSH host key file, the host could be
impersonated.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="file_permissions_sshd_private_key" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
chmod 0640 /etc/ssh/*_key
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="file_permissions_sshd_private_key" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include ssh_private_key_perms

class ssh_private_key_perms {
  exec { 'sshd_priv_key':
    command =&gt; "chmod 0640 /etc/ssh/*_key",
    path    =&gt; '/bin:/usr/bin'
  }
}
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_sshd_private_key:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-file_permissions_sshd_private_key_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="firewalld_sshd_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Remove SSH Server firewalld Firewall exception (Unusual)</ns0:title>
        <ns0:description xml:lang="en-US">By default, inbound connections to SSH's port are allowed. If
the SSH server is not being used, this exception should be removed from the
firewall configuration.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />

        To configure <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> to not allow access, run the following command(s):
        <html:code xmlns:html="http://www.w3.org/1999/xhtml" />
</ns0:description>
        <ns0:rationale xml:lang="en-US">
If inbound SSH connections are not expected, disallowing access to the SSH port will
avoid possible exploitation of the port by an attacker.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-firewalld_sshd_disabled:def:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Group id="ssh_server">
        <ns0:title xml:lang="en-US">Configure OpenSSH Server if Necessary</ns0:title>
        <ns0:description xml:lang="en-US">If the system needs to act as an SSH server, then
certain changes should be made to the OpenSSH daemon configuration
file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code>. The following recommendations can be
applied to this file. See the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sshd_config(5)</html:code> man page for more
detailed information.</ns0:description>
        <ns0:Rule id="firewalld_sshd_port_enabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Enable SSH Server firewalld Firewall exception</ns0:title>
          <ns0:description xml:lang="en-US">By default, inbound connections to SSH's port are allowed. If
the SSH server is being used but denied by the firewall, this exception should
be added to the firewall configuration.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />

        To configure <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> to allow access, run the following command(s):
        <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewall-cmd --permanent --add-service=ssh</html:code>
</ns0:description>
          <ns0:rationale xml:lang="en-US">
If inbound SSH connections are expected, adding a firewall rule exception
will allow remote access through the SSH port.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="firewalld_sshd_port_enabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
sshd_listening_port="<ns0:sub idref="sshd_listening_port" />"

if [ $sshd_listening_port -ne 22] ; then
  firewall-cmd --permanent --add-port=$sshd_listening_port/tcp
else
  firewall-cmd --permanent --add-service=ssh
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-sshd_listening_port:var:1" value-id="sshd_listening_port" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-firewalld_sshd_port_enabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-firewalld_sshd_port_enabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_allow_only_protocol2" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Allow Only SSH Protocol 2</ns0:title>
          <ns0:description xml:lang="en-US">Only SSH protocol version 2 connections should be
permitted. The default setting in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code> is correct, and can be
verified by ensuring that the following
line appears:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">Protocol 2</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8).1(ii)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(c)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">197</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.2.1</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000074-GPOS-00042</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
SSH protocol version 1 is an insecure implementation of the SSH protocol and
has many well-known vulnerability exploits. Exploits of the SSH daemon could provide
immediate root access to the system.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_allow_only_protocol2" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^Protocol' '2' 'CCE-27320-1' '%s %s'
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_allow_only_protocol2:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_allow_only_protocol2_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_limit_user_access" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Limit Users' SSH Access</ns0:title>
          <ns0:description xml:lang="en-US">By default, the SSH configuration allows any user with an account
to access the system. In order to specify the users that are allowed to login
via SSH and deny all other users, add or correct the following line in the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">DenyUsers USER1 USER2</html:pre>
Where <html:code xmlns:html="http://www.w3.org/1999/xhtml">USER1</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">USER2</html:code> are valid user names.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Specifying which accounts are allowed SSH access into the system reduces the
possibility of unauthorized access to the system.
</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="sshd_disable_gssapi_auth" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable GSSAPI Authentication</ns0:title>
          <ns0:description xml:lang="en-US">Unless needed, SSH should not permit extraneous or unnecessary
authentication mechanisms like GSSAPI. To disable GSSAPI authentication, add or
correct the following line in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">GSSAPIAuthentication no</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(c)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">368</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">318</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1812</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1813</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1814</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000364-GPOS-00151</ns0:reference>
          <ns0:rationale xml:lang="en-US">
GSSAPI authentication is used to provide additional authentication mechanisms to
applications. Allowing GSSAPI authentication through SSH exposes the system's
GSSAPI to remote hosts, increasing the attack surface of the system.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_disable_gssapi_auth" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^GSSAPIAuthentication' 'no' 'CCE-80220-7' '%s %s'
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_disable_gssapi_auth:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_disable_gssapi_auth_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_disable_kerb_auth" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable Kerberos Authentication</ns0:title>
          <ns0:description xml:lang="en-US">Unless needed, SSH should not permit extraneous or unnecessary
authentication mechanisms like Kerberos. To disable Kerberos authentication, add
or correct the following line in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">KerberosAuthentication no</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(c)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">368</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">318</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1812</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1813</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1814</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000364-GPOS-00151</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Kerberos authentication for SSH is often implemented using GSSAPI. If Kerberos
is enabled through SSH, the SSH daemon provides a means of access to the
system's Kerberos implementation. Vulnerabilities in the system's Kerberos
implementations may be subject to exploitation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_disable_kerb_auth" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^KerberosAuthentication' 'no' 'CCE-80221-5' '%s %s'
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_disable_kerb_auth:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_disable_kerb_auth_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_enable_strictmodes" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable Use of Strict Mode Checking</ns0:title>
          <ns0:description xml:lang="en-US">SSHs StrictModes option checks file and ownership permissions in
the user's home directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">.ssh</html:code> folder before accepting login. If world-
writable permissions are found, logon is rejected. To enable StrictModes in SSH,
add or correct the following line in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">StrictModes yes</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
If other users have access to modify user-specific SSH configuration files, they
may be able to log into the system as another user.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_enable_strictmodes" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^StrictModes' 'yes' 'CCE-80222-3' '%s %s'
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_enable_strictmodes:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_enable_strictmodes_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_use_priv_separation" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable Use of Privilege Separation</ns0:title>
          <ns0:description xml:lang="en-US">When enabled, SSH will create an unprivileged child process that
has the privilege of the authenticated user. To enable privilege separation in
SSH, add or correct the following line in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">UsePrivilegeSeparation yes</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
SSH daemon privilege separation causes the SSH process to drop root privileges
when not needed which would decrease the impact of software vulnerabilities in
the unprivileged section.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_use_priv_separation" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^UsePrivilegeSeparation' 'yes' 'CCE-80223-1' '%s %s'
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_use_priv_separation:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_use_priv_separation_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_disable_compression" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable Compression Or Set Compression to delayed</ns0:title>
          <ns0:description xml:lang="en-US">Compression is useful for slow network connections over long
distances but can cause performance issues on local LANs. If use of compression
is required, it should be enabled only after a user has authenticated; otherwise
, it should be disabled. To disable compression or delay compression until after
a user has successfully authenticated, add or correct the following line in the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">Compression no</html:pre> or <html:pre xmlns:html="http://www.w3.org/1999/xhtml">Compression delayed</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
If compression is allowed in an SSH connection prior to authentication,
vulnerabilities in the compression software could result in compromise of the
system from an unauthenticated connection, potentially wih root privileges.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_disable_compression" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^Compression' 'no' 'CCE-80224-9' '%s %s'
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_disable_compression:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_disable_compression_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_print_last_log" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Print Last Log</ns0:title>
          <ns0:description xml:lang="en-US">When enabled, SSH will display the date and time of the last
successful account logon. To enable LastLog in
SSH, add or correct the following line in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code> file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">PrintLastLog yes</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-9</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Providing users feedback on when account accesses last occurred facilitates user
recognition and reporting of unauthorized account use.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_print_last_log:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_print_last_log_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_set_idle_timeout" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Set SSH Idle Timeout Interval</ns0:title>
          <ns0:description xml:lang="en-US">SSH allows administrators to set an idle timeout
interval.
After this interval has passed, the idle user will be
automatically logged out.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To set an idle timeout interval, edit the following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code> as
follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ClientAliveInterval <html:b>interval</html:b></html:pre>
The timeout <html:b xmlns:html="http://www.w3.org/1999/xhtml">interval</html:b> is given in seconds. To have a timeout
of 10 minutes, set <html:b xmlns:html="http://www.w3.org/1999/xhtml">interval</html:b> to 600.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If a shorter timeout has already been set for the login shell, that value will 
preempt any SSH setting made here. Keep in mind that some processes may stop SSH
from correctly detecting that the user is idle.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-2(5)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SA-8(i)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-12</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1133</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2361</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000163-GPOS-00072</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000279-GPOS-00109</ns0:reference>
          <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-8.1.8</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.2.12</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Terminating an idle ssh session within a short time period reduces the window of
opportunity for unauthorized personnel to take control of a management session
enabled on the console or console port that has been let unattended.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_set_idle_timeout" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
sshd_idle_timeout_value="<ns0:sub idref="sshd_idle_timeout_value" />"
<ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^ClientAliveInterval' $sshd_idle_timeout_value 'CCE-27433-2' '%s %s'
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="sshd_set_idle_timeout" reboot="false" strategy="configure" system="urn:xccdf:fix:script:ansible">- name: "SSHD: Set client alive interval"
  lineinfile:
    create=yes
    dest="/etc/ssh/sshd_config"
    regexp="^ClientAliveInterval"
    line="ClientAliveInterval <ns0:sub idref="sshd_idle_timeout_value" />"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-export export-name="oval:ssg-sshd_idle_timeout_value:var:1" value-id="sshd_idle_timeout_value" />
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_set_idle_timeout:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_set_idle_timeout_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_set_keepalive" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Set SSH Client Alive Count</ns0:title>
          <ns0:description xml:lang="en-US">To ensure the SSH idle timeout occurs precisely when the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ClientAliveCountMax</html:code> is set,
edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code> as
follows:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ClientAliveCountMax 0</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-2(5)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SA-8</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-12</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1133</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2361</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000163-GPOS-00072</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000279-GPOS-00109</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.2.12</ns0:reference>
          <ns0:rationale xml:lang="en-US">
This ensures a user login will be terminated as soon as the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ClientAliveCountMax</html:code>
is reached.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_set_keepalive" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^ClientAliveCountMax' '0' 'CCE-27082-7' '%s %s'
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_set_keepalive:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_set_keepalive_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_disable_rhosts" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable SSH Support for .rhosts Files</ns0:title>
          <ns0:description xml:lang="en-US">SSH can emulate the behavior of the obsolete rsh
command in allowing users to enable insecure access to their
accounts via <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rhosts</html:code> files.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To ensure this behavior is disabled, add or correct the
following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">IgnoreRhosts yes</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(a)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.2.6</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
SSH trust relationships mean a compromise on one host
can allow an attacker to move trivially to other hosts.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_disable_rhosts" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^IgnoreRhosts' 'yes' 'CCE-27377-1' '%s %s'
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_disable_rhosts:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_disable_rhosts_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_disable_user_known_hosts" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable SSH Support for User Known Hosts</ns0:title>
          <ns0:description xml:lang="en-US">SSH can allow system users user host-based authentication to connect
to systems if a cache of the remote systems public keys are available.
This should be disabled.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To ensure this behavior is disabled, add or correct the
following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">IgnoreUserKnownHosts yes</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(a)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Configuring this setting for the SSH daemon provides additional
assurance that remove login via SSH will require a password, even
in the event of misconfiguration elsewhere.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_disable_user_known_hosts:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_disable_user_known_hosts_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_disable_rhosts_rsa" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable SSH Support for Rhosts RSA Authentication</ns0:title>
          <ns0:description xml:lang="en-US">SSH can allow authentication through the obsolete rsh
command through the use of the authenticating user's SSH keys. This should be disabled.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To ensure this behavior is disabled, add or correct the
following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">RhostsRSAAuthentication no</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(a)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Configuring this setting for the SSH daemon provides additional
assurance that remove login via SSH will require a password, even
in the event of misconfiguration elsewhere.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_disable_rhosts_rsa:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_disable_rhosts_rsa_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="disable_host_auth" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable Host-Based Authentication</ns0:title>
          <ns0:description xml:lang="en-US">SSH's cryptographic host-based authentication is
more secure than <html:code xmlns:html="http://www.w3.org/1999/xhtml">.rhosts</html:code> authentication. However, it is
not recommended that hosts unilaterally trust one another, even
within an organization.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To disable host-based authentication, add or correct the
following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">HostbasedAuthentication no</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00229</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.2.7</ns0:reference>
          <ns0:rationale xml:lang="en-US">
SSH trust relationships mean a compromise on one host
can allow an attacker to move trivially to other hosts.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="disable_host_auth" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">grep -q ^HostbasedAuthentication /etc/ssh/sshd_config &amp;&amp; \
  sed -i "s/HostbasedAuthentication.*/HostbasedAuthentication no/g" /etc/ssh/sshd_config
if ! [ $? -eq 0 ]; then
    echo "HostbasedAuthentication no" &gt;&gt; /etc/ssh/sshd_config
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-disable_host_auth:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-disable_host_auth_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="enable_x11_forwarding" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Enable Encrypted X11 Fordwarding</ns0:title>
          <ns0:description xml:lang="en-US">By default, remote X11 connections are not encrypted when initiated
by users. SSH has the capability to encrypt remote X11 connections when SSH's
<html:code xmlns:html="http://www.w3.org/1999/xhtml">X11Forwarding</html:code> option is enabled.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To enable X11 Forwarding, add or correct the
following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">X11Forwarding yes</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-2(1)(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Open X displays allow an attacker to capture keystrokes and to execute commands
remotely.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-enable_x11_forwarding:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-enable_x11_forwarding_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_disable_root_login" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable SSH Root Login</ns0:title>
          <ns0:description xml:lang="en-US">The root user should never be allowed to login to a
system directly over a network.
To disable root login via SSH, add or correct the following line
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">PermitRootLogin no</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6(2)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-2(1)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-2(5)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.2.8</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Even though the communications channel may be encrypted, an additional layer of
security is gained by extending the policy of not logging directly on as root.
In addition, logging in with a user-specific account provides individual
accountability of actions performed on the system and also helps to minimize
direct attack attempts on root's password.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_disable_root_login" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">
SSHD_CONFIG='/etc/ssh/sshd_config'

# Obtain line number of first uncommented case-insensitive occurrence of Match
# block directive (possibly prefixed with whitespace) present in $SSHD_CONFIG
FIRST_MATCH_BLOCK=$(sed -n '/^[[:space:]]*Match[^\n]*/I{=;q}' $SSHD_CONFIG)

# Obtain line number of first uncommented case-insensitive occurence of
# PermitRootLogin directive (possibly prefixed with whitespace) present in
# $SSHD_CONFIG
FIRST_PERMIT_ROOT_LOGIN=$(sed -n '/^[[:space:]]*PermitRootLogin[^\n]*/I{=;q}' $SSHD_CONFIG)

# Case: Match block directive not present in $SSHD_CONFIG
if [ -z "$FIRST_MATCH_BLOCK" ]
then

    # Case: PermitRootLogin directive not present in $SSHD_CONFIG yet
    if [ -z "$FIRST_PERMIT_ROOT_LOGIN" ]
    then
        # Append 'PermitRootLogin no' at the end of $SSHD_CONFIG
        echo -e "\nPermitRootLogin no" &gt;&gt; $SSHD_CONFIG

    # Case: PermitRootLogin directive present in $SSHD_CONFIG already
    else
        # Replace first uncommented case-insensitive occurrence
        # of PermitRootLogin directive
        sed -i "$FIRST_PERMIT_ROOT_LOGIN s/^[[:space:]]*PermitRootLogin.*$/PermitRootLogin no/I" $SSHD_CONFIG
    fi

# Case: Match block directive present in $SSHD_CONFIG
else

    # Case: PermitRootLogin directive not present in $SSHD_CONFIG yet
    if [ -z "$FIRST_PERMIT_ROOT_LOGIN" ]
    then
        # Prepend 'PermitRootLogin no' before first uncommented
        # case-insensitive occurrence of Match block directive
        sed -i "$FIRST_MATCH_BLOCK s/^\([[:space:]]*Match[^\n]*\)/PermitRootLogin no\n\1/I" $SSHD_CONFIG

    # Case: PermitRootLogin directive present in $SSHD_CONFIG and placed
    #       before first Match block directive
    elif [ "$FIRST_PERMIT_ROOT_LOGIN" -lt "$FIRST_MATCH_BLOCK" ]
    then
        # Replace first uncommented case-insensitive occurrence
        # of PermitRootLogin directive
        sed -i "$FIRST_PERMIT_ROOT_LOGIN s/^[[:space:]]*PermitRootLogin.*$/PermitRootLogin no/I" $SSHD_CONFIG

    # Case: PermitRootLogin directive present in $SSHD_CONFIG and placed
    # after first Match block directive
    else
         # Prepend 'PermitRootLogin no' before first uncommented
         # case-insensitive occurrence of Match block directive
         sed -i "$FIRST_MATCH_BLOCK s/^\([[:space:]]*Match[^\n]*\)/PermitRootLogin no\n\1/I" $SSHD_CONFIG
    fi
fi
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_disable_root_login:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_disable_root_login_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_disable_empty_passwords" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Disable SSH Access via Empty Passwords</ns0:title>
          <ns0:description xml:lang="en-US">To explicitly disallow SSH login from accounts with
empty passwords, add or correct the following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code>:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">PermitEmptyPasswords no</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Any accounts with empty passwords should be disabled immediately, and PAM configuration
should prevent users from being able to assign themselves empty passwords.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00229</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Configuring this setting for the SSH daemon provides additional assurance that
remote login via SSH will require a password, even in the event of 
misconfiguration elsewhere.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_disable_empty_passwords" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^PermitEmptyPasswords' 'no' 'CCE-27471-2' '%s %s'
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="sshd_disable_empty_passwords" reboot="false" strategy="configure" system="urn:xccdf:fix:script:ansible">- name: "SSHD: Disable empty passwords"
  lineinfile:
    create=yes
    dest="/etc/ssh/sshd_config"
    regexp="^PermitEmptyPasswords"
    line="PermitEmptyPasswords no"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_disable_empty_passwords:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_disable_empty_passwords_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_enable_warning_banner" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Enable SSH Warning Banner</ns0:title>
          <ns0:description xml:lang="en-US">
To enable the warning banner and ensure it is consistent
across the system, add or correct the following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">Banner /etc/issue</html:pre>
Another section contains information on how to create an
appropriate system-wide warning banner.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(a)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(c)(1)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(c)(2)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-8(c)(3)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">48</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">50</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1384</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1385</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1386</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1387</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1388</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000023-GPOS-00006</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000024-GPOS-00007</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000228-GPOS-00088</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.2.14</ns0:reference>
          <ns0:rationale xml:lang="en-US">
The warning message reinforces policy awareness during the logon process and
facilitates possible legal action against attackers.  Alternatively, systems
whose ownership should not be obvious should ensure usage of a banner that does
not provide easy attribution.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_enable_warning_banner" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^Banner' '/etc/issue' 'CCE-27314-4' '%s %s'
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="sshd_enable_warning_banner" reboot="false" strategy="configure" system="urn:xccdf:fix:script:ansible">- name: "SSHD: Enable warning banner"
  lineinfile:
    create=yes
    dest="/etc/ssh/sshd_config"
    regexp="^Banner"
    line="Banner /etc/issue"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_enable_warning_banner:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_enable_warning_banner_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_do_not_permit_user_env" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Do Not Allow SSH Environment Options</ns0:title>
          <ns0:description xml:lang="en-US">To ensure users are not able to override environment
options to the SSH daemon, add or correct the following line
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">PermitUserEnvironment no</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00229</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.2.10</ns0:reference>
          <ns0:rationale xml:lang="en-US">
SSH environment options potentially allow users to bypass
access restriction in some configurations.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_do_not_permit_user_env" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^PermitUserEnvironment' 'no' 'CCE-27363-1' '%s %s'
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="sshd_do_not_permit_user_env" reboot="false" strategy="configure" system="urn:xccdf:fix:script:ansible">- name: "SSHD: Do not permit user environment"
  lineinfile:
    create=yes
    dest="/etc/ssh/sshd_config"
    regexp="^PermitUserEnvironment"
    line="PermitUserEnvironment no"
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_do_not_permit_user_env:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_do_not_permit_user_env_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_use_approved_ciphers" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Use Only Approved Ciphers</ns0:title>
          <ns0:description xml:lang="en-US">Limit the ciphers to those algorithms which are FIPS-approved.
Counter (CTR) mode is also preferred over cipher-block chaining (CBC) mode.
The following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code>
demonstrates use of FIPS-approved ciphers:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">Ciphers aes128-ctr,aes192-ctr,aes256-ctr</html:pre>
The man page <html:code xmlns:html="http://www.w3.org/1999/xhtml">sshd_config(5)</html:code> contains a list of supported ciphers.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(2)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-10(5)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(1)(c)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">68</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">803</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000033-GPOS-00014</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000120-GPOS-00061</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000125-GPOS-00065</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000250-GPOS-00093</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000393-GPOS-00173</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">6.2.11</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore
cannot be relied upon to provide confidentiality or integrity, and system data may be compromised.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to
cryptographic modules.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules
utilize authentication that meets industry and government requirements. For government systems, this allows
Security Levels 1, 2, 3, or 4 for use on Red Hat Enterprise Linux.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_use_approved_ciphers" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^Ciphers' 'aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc' 'CCE-27295-5' '%s %s'
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_use_approved_ciphers:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_use_approved_ciphers_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="sshd_use_approved_macs" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Use Only FIPS Approved MACs</ns0:title>
          <ns0:description xml:lang="en-US">Limit the MACs to those hash algorithms which are FIPS-approved.
The following line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ssh/sshd_config</html:code> demonstrates use 
of FIPS-approved MACs:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">MACs hmac-sha2-512,hmac-sha2-256</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(2)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-7</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-13</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1453</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000250-GPOS-00093</ns0:reference>
          <ns0:rationale xml:lang="en-US">
DoD Information Systems are required to use FIPS-approved cryptographic hash
functions. The only SSHv2 hash algorithms meeting this requirement is SHA2.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="sshd_use_approved_macs" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_replace_or_append" />
replace_or_append '/etc/ssh/sshd_config' '^MACs' 'hmac-sha2-512,hmac-sha2-256,hmac-sha1' 'CCE-27455-5' '%s %s'
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sshd_use_approved_macs:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sshd_use_approved_macs_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="sshd_strengthen_firewall">
          <ns0:title xml:lang="en-US">Strengthen Firewall Configuration if Possible</ns0:title>
          <ns0:description xml:lang="en-US">If the SSH server is expected to only receive connections from
the local network, then strengthen the default firewall rule for the SSH service
to only accept connections from the appropriate network segment(s).
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Determine an appropriate network block, <html:code xmlns:html="http://www.w3.org/1999/xhtml">netwk</html:code>, network mask, <html:code xmlns:html="http://www.w3.org/1999/xhtml">mask</html:code>, and
network protocol, <html:code xmlns:html="http://www.w3.org/1999/xhtml">ip_protocol</html:code>, representing the machines on your network which will
be allowed to access this SSH server.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Run the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">firewall-cmd --permanent --add-rich-rule='rule family="ip_protocol" source address="netwk/mask" service name="ssh" accept'</html:pre>
</ns0:description>
          <ns0:rationale xml:lang="en-US">
Restricting SSH access to only trusted network segments reduces exposure of the SSH
server to attacks from unauthorized networks.</ns0:rationale>
        </ns0:Group>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="sssd">
      <ns0:title xml:lang="en-US">System Security Services Daemon</ns0:title>
      <ns0:description xml:lang="en-US">
The System Security Services Daemon (SSSD) is a system daemon that provides access
to different identity and authentication providers such as Red Hat's IdM, Microsoft's AD,
openLDAP, MIT Kerberos, etc. It uses a common framework that can provide caching and offline
support to systems utilizing SSSD. SSSD using caching to reduce load on authentication
servers permit offline authentication as well as store extended user user data.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
For more information, see

<html:b xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="https://access.redhat.com/documentation/en_US/Red_Hat_Enterprise_Linux/7/html/System-Level_Authentication_Guide/SSSD.html">https://access.redhat.com/documentation/en_US/Red_Hat_Enterprise_Linux/7/html/System-Level_Authentication_Guide/SSSD.html</html:a></html:b>
</ns0:description>
      <ns0:Rule id="package_sssd_installed" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Install the SSSD Package</ns0:title>
        <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">sssd</html:code> package should be installed.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">sssd</html:code> package can be installed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install sssd</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(10)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
        <ns0:rationale xml:lang="en-US">
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="package_sssd_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command install sssd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="package_sssd_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Ensure sssd is installed
  package:
    name="{{item}}"
    state=present
  with_items:
    - sssd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="package_sssd_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:puppet">include install_sssd

class install_sssd {
  package { 'sssd':
    ensure =&gt; 'installed',
  }
}
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="package_sssd_installed" reboot="false" strategy="enable" system="urn:redhat:anaconda:pre">
package --add=sssd
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_sssd_installed:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_sssd_installed_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="service_sssd_enabled" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Enable the SSSD Service</ns0:title>
        <ns0:description xml:lang="en-US">The SSSD service should be enabled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">sssd</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable sssd.service</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(10)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">TBD</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">TBD</ns0:reference>
        <ns0:rationale xml:lang="en-US">
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_sssd_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command enable sssd
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_sssd_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Enable service sssd
  service:
    name="{{item}}"
    enabled="yes"
    state="started"
  with_items:
    - sssd

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_sssd_enabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_sssd_enabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="sssd_memcache_timeout" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Configure SSSD's Memory Cache to Expire</ns0:title>
        <ns0:description xml:lang="en-US">
SSSD's memory cache should be configured to set to expire records after 1 day.
To configure SSSD to expire memory cache, set <html:code xmlns:html="http://www.w3.org/1999/xhtml">memcache_timeout</html:code> to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">86400</html:code> under the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[nss]</html:code> section in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sssd/sssd.conf</html:code>.
For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[nss]
memcache_timeout = 86400
</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(13)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2007</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000383-GPOS-00166</ns0:reference>
        <ns0:rationale xml:lang="en-US">
If cached authentication information is out-of-date, the validity of the
authentication information may be questionable.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sssd_memcache_timeout:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sssd_memcache_timeout_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="sssd_offline_cred_expiration" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Configure SSSD to Expire Offline Credentials</ns0:title>
        <ns0:description xml:lang="en-US">
SSSD should be configured to expire offline credentials after 1 day.
To configure SSSD to expire offline credentials, set
<html:code xmlns:html="http://www.w3.org/1999/xhtml">offline_credentials_expiration</html:code> to <html:code xmlns:html="http://www.w3.org/1999/xhtml">1</html:code> under the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[pam]</html:code>
section in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sssd/sssd.conf</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[pam]
offline_credentials_expiration = 1
</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(13)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2007</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000383-GPOS-00166</ns0:reference>
        <ns0:rationale xml:lang="en-US">
If cached authentication information is out-of-date, the validity of the
authentication information may be questionable.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sssd_offline_cred_expiration:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sssd_offline_cred_expiration_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="sssd_ssh_known_hosts_timeout" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Configure SSSD to Expire SSH Known Hosts</ns0:title>
        <ns0:description xml:lang="en-US">
SSSD should be configured to expire keys from known SSH hosts after 1 day.
To configure SSSD to known SSH hosts, set <html:code xmlns:html="http://www.w3.org/1999/xhtml">ssh_known_hosts_timeout</html:code>
to <html:code xmlns:html="http://www.w3.org/1999/xhtml">86400</html:code> under the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[ssh]</html:code> section in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sssd/sssd.conf</html:code>. For example:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[ssh]
ssh_known_hosts_timeout = 86400
</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(13)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2007</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000383-GPOS-00166</ns0:reference>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5(13)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">2007</ns0:reference>
        <ns0:rationale xml:lang="en-US">
If cached authentication information is out-of-date, the validity of the
authentication information may be questionable.
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sssd_ssh_known_hosts_timeout:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sssd_ssh_known_hosts_timeout_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
    </ns0:Group>
    <ns0:Group id="xwindows">
      <ns0:title xml:lang="en-US">X Window System</ns0:title>
      <ns0:description xml:lang="en-US">The X Window System implementation included with the
system is called X.org.</ns0:description>
      <ns0:Group id="disabling_xwindows">
        <ns0:title xml:lang="en-US">Disable X Windows</ns0:title>
        <ns0:description xml:lang="en-US">Unless there is a mission-critical reason for the
system to run a graphical user interface, ensure X is not set to start
automatically at boot and remove the X Windows software packages.
There is usually no reason to run X Windows
on a dedicated server machine, as it increases the system's attack surface and consumes
system resources. Administrators of server systems should instead login via
SSH or on the text console.</ns0:description>
        <ns0:Rule id="xwindows_runlevel_setting" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable X Windows Startup By Setting Default Target</ns0:title>
          <ns0:description xml:lang="en-US">Systems that do not require a graphical user interface should only boot by
default into <html:code xmlns:html="http://www.w3.org/1999/xhtml">multi-user.target</html:code> mode. This prevents accidental booting of the system
into a <html:code xmlns:html="http://www.w3.org/1999/xhtml">graphical.target</html:code> mode. Setting the system's default target to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">multi-user.target</html:code> will prevent automatic startup of the X server. To do so, run:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ systemctl set-default multi-user.target</html:pre>
You should see the following output:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">rm '/etc/systemd/system/default.target'
ln -s '/usr/lib/systemd/system/multi-user.target' '/etc/systemd/system/default.target'</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8).1(ii)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">Services that are not required for system and application processes
must not be active to decrease the attack surface of the system. X windows has a
long history of security vulnerabilities and should not be used unless approved
and documented.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-xwindows_runlevel_setting:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-xwindows_runlevel_setting_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_xorg-x11-server-common_removed" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Remove the X Windows Package Group</ns0:title>
          <ns0:description xml:lang="en-US">By removing the xorg-x11-server-common package, the system no longer has X Windows
installed. If X Windows is not installed then the system cannot boot into graphical user mode.
This prevents the system from being accidentally or maliciously booted into a <html:code xmlns:html="http://www.w3.org/1999/xhtml">graphical.target</html:code>
mode. To do so, run the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum groupremove "X Window System"</html:pre>
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum remove xorg-x11-server-common</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(8).1(ii)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.2</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">Unnecessary service packages must not be installed to decrease the attack surface of the system. X windows has a long history of security
vulnerabilities and should not be installed unless approved and documented.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_xorg-x11-server-common_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_xorg-x11-server-common_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="avahi">
      <ns0:title xml:lang="en-US">Avahi Server</ns0:title>
      <ns0:description xml:lang="en-US">The Avahi daemon implements the DNS Service Discovery
and Multicast DNS protocols, which provide service and host
discovery on a network. It allows a system to automatically
identify resources on the network, such as printers or web servers.
This capability is also known as mDNSresponder and is a major part
of Zeroconf networking. </ns0:description>
      <ns0:Group id="disable_avahi_group">
        <ns0:title xml:lang="en-US">Disable Avahi Server if Possible</ns0:title>
        <ns0:description xml:lang="en-US">Because the Avahi daemon service keeps an open network
port, it is subject to network attacks.
Disabling it can reduce the system's vulnerability to such attacks.
</ns0:description>
        <ns0:Rule id="service_avahi-daemon_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Avahi Server Software</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">avahi-daemon</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable avahi-daemon.service</html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.3</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Because the Avahi daemon service keeps an open network
port, it is subject to network attacks. Its functionality
is convenient but is only appropriate if the local network
can be trusted.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_avahi-daemon_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">#
# Disable avahi-daemon.service for all systemd targets
#
systemctl disable avahi-daemon.service

#
# Stop avahi-daemon.service if currently running
# and disable avahi-daemon.socket so the avahi-daemon.service
# can't be activated
#
systemctl stop avahi-daemon.service
systemctl disable avahi-daemon.socket
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_avahi-daemon_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:ansible">- name: Disable service avahi
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - avahi-daemon

- name: Disable avahi socket
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - avahi-socket
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_avahi-daemon_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_avahi-daemon_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="avahi_configuration">
        <ns0:title xml:lang="en-US">Configure Avahi if Necessary</ns0:title>
        <ns0:description xml:lang="en-US">
If your system requires the Avahi daemon, its configuration can be restricted
to improve security. The Avahi daemon configuration file is
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/avahi/avahi-daemon.conf</html:code>. The following security recommendations
should be applied to this file:
See the <html:code xmlns:html="http://www.w3.org/1999/xhtml">avahi-daemon.conf(5)</html:code> man page, or documentation at
<html:a href="http://www.avahi.org" xmlns:html="http://www.w3.org/1999/xhtml">http://www.avahi.org</html:a>, for more detailed information
about the configuration options.
</ns0:description>
        <ns0:Rule id="avahi_ip_only" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Serve Avahi Only via Required Protocol</ns0:title>
          <ns0:description xml:lang="en-US">
If you are using only IPv4, edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/avahi/avahi-daemon.conf</html:code> and ensure
the following line exists in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[server]</html:code> section:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">use-ipv6=no</html:pre>
Similarly, if you are using only IPv6, disable IPv4 sockets with the line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">use-ipv4=no</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          </ns0:Rule>
        <ns0:Rule id="avahi_check_ttl" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Check Avahi Responses' TTL Field</ns0:title>
          <ns0:description xml:lang="en-US">
To make Avahi ignore packets unless the TTL field is 255, edit
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/avahi/avahi-daemon.conf</html:code> and ensure the following line
appears in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[server]</html:code> section:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">check-response-ttl=yes</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">
This helps to ensure that only mDNS responses from the local network are
processed, because the TTL field in a packet is decremented from its initial
value of 255 whenever it is routed from one network to another. Although a
properly-configured router or firewall should not allow mDNS packets into
the local network at all, this option provides another check to ensure they
are not permitted.
</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="avahi_prevent_port_sharing" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Prevent Other Programs from Using Avahi's Port</ns0:title>
          <ns0:description xml:lang="en-US">
To prevent other mDNS stacks from running, edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/avahi/avahi-daemon.conf</html:code>
and ensure the following line appears in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[server]</html:code> section:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">disallow-other-stacks=yes</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">
This helps ensure that only Avahi is responsible for mDNS traffic coming from
that port on the system.
</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="avahi_disable_publishing" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Avahi Publishing</ns0:title>
          <ns0:description xml:lang="en-US">
To prevent other mDNS stacks from running, edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/avahi/avahi-daemon.conf</html:code>
and ensure the following line appears in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[server]</html:code> section:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">disallow-other-stacks=yes</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">
This helps ensure that only Avahi is responsible for mDNS traffic coming from
that port on the system.
</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="avahi_restrict_published_information" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Restrict Information Published by Avahi</ns0:title>
          <ns0:description xml:lang="en-US">
If it is necessary to publish some information to the network, it should not be joined
by any extraneous information, or by information supplied by a non-trusted source
on the system.
Prevent user applications from using Avahi to publish services by adding or
correcting the following line in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[publish]</html:code> section:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">disable-user-service-publishing=yes</html:pre>
Implement as many of the following lines as possible, to restrict the information
published by Avahi.
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">publish-addresses=no
publish-hinfo=no
publish-workstation=no
publish-domain=no</html:pre>
Inspect the files in the directory <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/avahi/services/</html:code>. Unless there
is an operational need to publish information about each of these services,
delete the corresponding file.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">
These options prevent publishing attempts from succeeding,
and can be applied even if publishing is disabled entirely via
disable-publishing. Alternatively, these can be used to restrict
the types of published information in the event that some information
must be published.
</ns0:rationale>
          </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="printing">
      <ns0:title xml:lang="en-US">Print Support</ns0:title>
      <ns0:description xml:lang="en-US">The Common Unix Printing System (CUPS) service provides both local
and network printing support. A system running the CUPS service can accept
print jobs from other systems, process them, and send them to the appropriate
printer. It also provides an interface for remote administration through a web
browser. The CUPS service is installed and activated by default. The project
homepage and more detailed documentation are available at
<html:a href="http://www.cups.org" xmlns:html="http://www.w3.org/1999/xhtml">http://www.cups.org</html:a>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" /> </ns0:description>
      <ns0:Rule id="service_cups_disabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Disable the CUPS Service</ns0:title>
        <ns0:description xml:lang="en-US">
          
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cups</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable cups.service</html:pre>
        </ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.4</ns0:reference>
        <ns0:rationale xml:lang="en-US">Turn off unneeded services to reduce attack surface.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_cups_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">#
# Disable cups.service for all systemd targets
#
systemctl disable cups.service

#
# Stop cups.service if currently running
# and disable cups.path and cups.socket so
# cups.service can't be activated
#
systemctl stop cups.service
systemctl disable cups.path
systemctl disable cups.socket
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_cups_disabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_cups_disabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Group id="configure_printing">
        <ns0:title xml:lang="en-US">Configure the CUPS Service if Necessary</ns0:title>
        <ns0:description xml:lang="en-US">CUPS provides the ability to easily share local printers with
other machines over the network. It does this by allowing machines to share
lists of available printers. Additionally, each machine that runs the CUPS
service can potentially act as a print server. Whenever possible, the printer
sharing and print server capabilities of CUPS should be limited or disabled.
The following recommendations should demonstrate how to do just that.
</ns0:description>
        <ns0:Rule id="cups_disable_browsing" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Printer Browsing Entirely if Possible</ns0:title>
          <ns0:description xml:lang="en-US">By default, CUPS listens on the network for printer list
broadcasts on UDP port 631. This functionality is called printer browsing.
To disable printer browsing entirely, edit the CUPS configuration
file, located at <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/cups/cupsd.conf</html:code>, to include the following:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">Browsing Off</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">The CUPS print service can be configured to broadcast a list of
available printers to the network. Other machines on the network, also running
the CUPS print service, can be configured to listen to these broadcasts and add
and configure these printers for immediate use. By disabling this browsing
capability, the machine will no longer generate or receive such broadcasts.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-cups_disable_browsing:def:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="cups_disable_printserver" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Print Server Capabilities</ns0:title>
          <ns0:description xml:lang="en-US">To prevent remote users from potentially connecting to and using
locally configured printers, disable the CUPS print server sharing
capabilities. To do so, limit how the server will listen for print jobs by
removing the more generic port directive from /etc/cups/cupsd.conf:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">Port 631</html:pre>
and replacing it with the <html:code xmlns:html="http://www.w3.org/1999/xhtml">Listen</html:code> directive:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">Listen localhost:631</html:pre>
This will prevent remote users from printing to locally configured printers
while still allowing local users on the machine to print normally.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">By default, locally configured printers will not be shared over the
network, but if this functionality has somehow been enabled, these
recommendations will disable it again. Be sure to disable outgoing printer list
broadcasts, or remote users will still be able to see the locally configured
printers, even if they cannot actually print to them. To limit print serving to
a particular set of users, use the Policy directive.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-cups_disable_printserver:def:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="dhcp">
      <ns0:title xml:lang="en-US">DHCP</ns0:title>
      <ns0:description xml:lang="en-US">The Dynamic Host Configuration Protocol (DHCP) allows
systems to request and obtain an IP address and other configuration
parameters from a server.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
This guide recommends configuring networking on clients by manually editing
the appropriate files under <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig</html:code>.  Use of DHCP can make client 
systems vulnerable to compromise by rogue DHCP servers, and should be avoided 
unless necessary.  If using DHCP is necessary, however, there are best practices 
that should be followed to minimize security risk.
</ns0:description>
      <ns0:Group id="disabling_dhcp_server">
        <ns0:title xml:lang="en-US">Disable DHCP Server</ns0:title>
        <ns0:description xml:lang="en-US">
The DHCP server <html:code xmlns:html="http://www.w3.org/1999/xhtml">dhcpd</html:code> is not installed or activated by
default. If the software was installed and activated, but the
system does not need to act as a DHCP server, it should be disabled
and removed.
</ns0:description>
        <ns0:Rule id="service_dhcpd_disabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable DHCP Service</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">dhcpd</html:code> service should be disabled on
any system that does not need to act as a DHCP server.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">dhcpd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable dhcpd.service</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Unmanaged or unintentionally activated DHCP servers may provide faulty information
to clients, interfering with the operation of a legitimate site
DHCP server if there is one.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_dhcpd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable dhcpd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_dhcpd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service dhcpd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - dhcpd

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_dhcpd_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_dhcpd_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_dhcp_removed" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Uninstall DHCP Server Package</ns0:title>
          <ns0:description xml:lang="en-US">If the system does not need to act as a DHCP server,
the dhcp package can be uninstalled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">dhcp</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase dhcp</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.5</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Removing the DHCP server ensures that it cannot be easily or
accidentally reactivated and disrupt network operation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_dhcp_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove dhcp
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_dhcp_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure dhcp is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - dhcp
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_dhcp_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_dhcp

class remove_dhcp {
  package { 'dhcp':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_dhcp_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=dhcp
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_dhcp_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_dhcp_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="dhcp_server_configuration">
        <ns0:title xml:lang="en-US">Disable DHCP Server</ns0:title>
        <ns0:description xml:lang="en-US">If the system must act as a DHCP server, the configuration
information it serves should be minimized. Also, support for other protocols
and DNS-updating schemes should be explicitly disabled unless needed. The
configuration file for dhcpd is called <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dhcp/dhcpd.conf</html:code>. The file
begins with a number of global configuration options. The remainder of the file
is divided into sections, one for each block of addresses offered by dhcpd,
each of which contains configuration options specific to that address
block.</ns0:description>
        <ns0:Rule id="dhcp_server_disable_ddns" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Do Not Use Dynamic DNS</ns0:title>
          <ns0:description xml:lang="en-US">To prevent the DHCP server from receiving DNS information from
clients, edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dhcp/dhcpd.conf</html:code>, and add or correct the following global
option: <html:pre xmlns:html="http://www.w3.org/1999/xhtml">ddns-update-style none;</html:pre>
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">The ddns-update-style option controls only whether
the DHCP server will attempt to act as a Dynamic DNS client. As long as the DNS
server itself is correctly configured to reject DDNS attempts, an incorrect
ddns-update-style setting on the client is harmless (but should be fixed as a
best practice).</ns0:warning>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">The Dynamic DNS protocol is used to remotely update the data served
by a DNS server. DHCP servers can use Dynamic DNS to publish information about
their clients. This setup carries security risks, and its use is not
recommended.  If Dynamic DNS must be used despite the risks it poses, it is
critical that Dynamic DNS transactions be protected using TSIG or some other
cryptographic authentication mechanism. See dhcpd.conf(5) for more information
about protecting the DHCP server from passing along malicious DNS data from its
clients.  </ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="dhcp_server_deny_decline" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Deny Decline Messages</ns0:title>
          <ns0:description xml:lang="en-US">Edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dhcp/dhcpd.conf</html:code> and add or correct the following
global option to prevent the DHCP server from responding the DHCPDECLINE
messages, if possible: <html:pre xmlns:html="http://www.w3.org/1999/xhtml">deny declines;</html:pre> </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">The DHCPDECLINE message can be sent by a DHCP client to indicate
that it does not consider the lease offered by the server to be valid. By
issuing many DHCPDECLINE messages, a malicious client can exhaust the DHCP
server's pool of IP addresses, causing the DHCP server to forget old address
allocations.</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="dhcp_server_deny_bootp" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Deny BOOTP Queries</ns0:title>
          <ns0:description xml:lang="en-US">Unless your network needs to support older BOOTP clients, disable
support for the bootp protocol by adding or correcting the global option:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">deny bootp;</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">The bootp option tells dhcpd to respond to BOOTP queries. If support
for this simpler protocol is not needed, it should be disabled to remove attack
vectors against the DHCP server.
</ns0:rationale>
          </ns0:Rule>
        <ns0:Group id="dhcp_server_minimize_served_info">
          <ns0:title xml:lang="en-US">Minimize Served Information</ns0:title>
          <ns0:description xml:lang="en-US">Edit /etc/dhcp/dhcpd.conf. Examine each address range section within
the file, and ensure that the following options are not defined unless there is
an operational need to provide this information via DHCP:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">option domain-name
option domain-name-servers
option nis-domain
option nis-servers
option ntp-servers
option routers
option time-offset</html:pre>
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">By default, the Red Hat Enterprise Linux client installation uses DHCP
to request much of the above information from the DHCP server. In particular,
domain-name, domain-name-servers, and routers are configured via DHCP.  These
settings are typically necessary for proper network functionality, but are also
usually static across machines at a given site.</ns0:warning>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">Because the configuration information provided by the DHCP server
could be maliciously provided to clients by a rogue DHCP server, the amount of
information provided via DHCP should be minimized. Remove these definitions
from the DHCP server configuration to ensure that legitimate clients do not
unnecessarily rely on DHCP for this information.
</ns0:rationale>
        </ns0:Group>
        <ns0:Rule id="dhcp_server_configure_logging" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Configure Logging</ns0:title>
          <ns0:description xml:lang="en-US">Ensure that the following line exists in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/rsyslog.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">daemon.*           /var/log/daemon.log</html:pre>
Configure logwatch or other log monitoring tools to summarize error conditions
reported by the dhcpd process.</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-12</ns0:reference>
          <ns0:rationale xml:lang="en-US">By default, dhcpd logs notices to the daemon facility. Sending all
daemon messages to a dedicated log file is part of the syslog configuration
outlined in the Logging and Auditing section</ns0:rationale>
          </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="disabling_dhcp_client">
        <ns0:title xml:lang="en-US">Disable DHCP Client</ns0:title>
        <ns0:description xml:lang="en-US">
DHCP is the default network configuration method provided by the system
installer, and common on many networks. Nevertheless, manual management
of IP addresses for systems implies a greater degree of management and
accountability for network activity.
</ns0:description>
        <ns0:Rule id="sysconfig_networking_bootproto_ifcfg" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable DHCP Client</ns0:title>
          <ns0:description xml:lang="en-US">
For each interface on the system (e.g. eth0), edit
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/network-scripts/ifcfg-<html:i>interface</html:i></html:code> and make the
following changes:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li> Correct the BOOTPROTO line to read:
<html:pre>BOOTPROTO=none</html:pre>
</html:li><html:li> Add or correct the following lines, substituting the appropriate
values based on your site's addressing scheme:
<html:pre>NETMASK=255.255.255.0
IPADDR=192.168.1.2
GATEWAY=192.168.1.1</html:pre>
</html:li></html:ul>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:rationale xml:lang="en-US">
DHCP relies on trusting the local network. If the local network is not trusted,
then it should not be used.  However, the automatic configuration provided by
DHCP is commonly used and the alternative, manual configuration, presents an
unacceptable burden in many circumstances.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-sysconfig_networking_bootproto_ifcfg:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-sysconfig_networking_bootproto_ifcfg_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="dhcp_client_configuration">
        <ns0:title xml:lang="en-US">Configure DHCP Client if Necessary</ns0:title>
        <ns0:description xml:lang="en-US">If DHCP must be used, then certain configuration changes can
minimize the amount of information it receives and applies from the network,
and thus the amount of incorrect information a rogue DHCP server could
successfully distribute.  For more information on configuring dhclient, see the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">dhclient(8)</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">dhclient.conf(5)</html:code> man pages.  </ns0:description>
        <ns0:Group id="dhcp_client_restrict_options">
          <ns0:title xml:lang="en-US">Minimize the DHCP-Configured Options</ns0:title>
          <ns0:description xml:lang="en-US">Create the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dhcp/dhclient.conf</html:code>, and add an
appropriate setting for each of the ten configuration settings which can be
obtained via DHCP. For each setting, do one of the following:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the setting should <html:i xmlns:html="http://www.w3.org/1999/xhtml">not</html:i> be configured remotely by the DHCP server,
select an appropriate static value, and add the line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">supersede <html:code>setting value</html:code>;</html:pre>
If the setting should be configured remotely by the DHCP server, add the lines:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">request <html:code>setting</html:code>;
require <html:code>setting</html:code>;</html:pre>
For example, suppose the DHCP server should provide only the IP address itself
and the subnet mask. Then the entire file should look like:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">supersede domain-name "example.com";
supersede domain-name-servers 192.168.1.2;
supersede nis-domain "";
supersede nis-servers "";
supersede ntp-servers "ntp.example.com ";
supersede routers 192.168.1.1;
supersede time-offset -18000;
request subnet-mask;
require subnet-mask;</html:pre>
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">In this example, the options nis-servers and
nis-domain are set to empty strings, on the assumption that the deprecated NIS
protocol is not in use. It is necessary to supersede settings for unused
services so that they cannot be set by a hostile DHCP server. If an option is
set to an empty string, dhclient will typically not attempt to configure the
service.</ns0:warning>
          <ns0:rationale xml:lang="en-US">By default, the DHCP client program, dhclient, requests and applies
ten configuration options (in addition to the IP address) from the DHCP server.
subnet-mask, broadcast-address, time-offset, routers, domain-name,
domain-name-servers, host-name, nis-domain, nis-servers, and ntp-servers.  Many
of the options requested and applied by dhclient may be the same for every
system on a network. It is recommended that almost all configuration options be
assigned statically, and only options which must vary on a host-by-host basis
be assigned via DHCP. This limits the damage which can be done by a rogue DHCP
server.  If appropriate for your site, it is also possible to supersede the
host-name directive in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dhcp/dhclient.conf</html:code>, establishing a static
hostname for the machine. However, dhclient does not use the host name option
provided by the DHCP server (instead using the value provided by a reverse DNS
lookup).</ns0:rationale>
        </ns0:Group>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="ntp">
      <ns0:title xml:lang="en-US">Network Time Protocol</ns0:title>
      <ns0:description xml:lang="en-US">The Network Time Protocol is used to manage the system
clock over a network. Computer clocks are not very accurate, so
time will drift unpredictably on unmanaged systems. Central time
protocols can be used both to ensure that time is consistent among
a network of machines, and that their time is consistent with the
outside world.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If every system on a network reliably reports the same time, then it is much
easier to correlate log messages in case of an attack. In addition, a number of
cryptographic protocols (such as Kerberos) use timestamps to prevent certain
types of attacks. If your network does not have synchronized time, these
protocols may be unreliable or even unusable.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Depending on the specifics of the network, global time accuracy may be just as
important as local synchronization, or not very important at all. If your
network is connected to the Internet, using a public timeserver (or one
provided by your enterprise) provides globally accurate timestamps which may be
essential in investigating or responding to an attack which originated outside
of your network.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
A typical network setup involves a small number of internal systems operating
as NTP servers, and the remainder obtaining time information from those
internal servers.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
There is a choice between the daemons <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">chronyd</html:code>, which
are available from the repositories in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntp</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">chrony</html:code>
packages respectively.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The default <html:code xmlns:html="http://www.w3.org/1999/xhtml">chronyd</html:code> daemon can work well when external time references
are only intermittently accesible, can perform well even when the network is
congested for longer periods of time, can usually synchronize the clock faster
and with better time accuracy, and quickly adapts to sudden changes in the rate
of the clock, for example, due to changes in the temperature of the crystal
oscillator. <html:code xmlns:html="http://www.w3.org/1999/xhtml">Chronyd</html:code> should be considered for all systems which are
frequently suspended or otherwise intermittently disconnected and reconnected
to a network. Mobile and virtual systems for example.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code> NTP daemon fully supports NTP protocol version 4 (RFC 5905),
including broadcast, multicast, manycast clients and servers, and the orphan
mode. It also supports extra authentication schemes based on public-key
cryptography (RFC 5906). The NTP daemon (<html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code>) should be considered
for systems which are normally kept permanently on. Systems which are required
to use broadcast or multicast IP, or to perform authentication of packets with
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">Autokey</html:code> protocol, should consider using <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Refer to <html:a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html" xmlns:html="http://www.w3.org/1999/xhtml">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html</html:a> for more detailed comparison of features of <html:code xmlns:html="http://www.w3.org/1999/xhtml">chronyd</html:code>
and <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code> daemon features respectively, and for further guidance how to
choose between the two NTP daemons.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The upstream manual pages at <html:a href="http://chrony.tuxfamily.org/manual.html" xmlns:html="http://www.w3.org/1999/xhtml">http://chrony.tuxfamily.org/manual.html</html:a> for
<html:code xmlns:html="http://www.w3.org/1999/xhtml">chronyd</html:code> and <html:a href="http://www.ntp.org" xmlns:html="http://www.w3.org/1999/xhtml">http://www.ntp.org</html:a> for <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code> provide additional
information on the capabilities and configuration of each of the NTP daemons.
</ns0:description>
      <ns0:Value id="var_multiple_time_servers" type="string">
        <ns0:title xml:lang="en-US">Vendor Approved Time Servers</ns0:title>
        <ns0:description xml:lang="en-US">The list of vendor-approved time servers</ns0:description>
        <ns0:value selector="rhel">0.rhel.pool.ntp.org,1.rhel.pool.ntp.org,2.rhel.pool.ntp.org,3.rhel.pool.ntp.org</ns0:value>
        <ns0:value selector="fedora">0.fedora.pool.ntp.org,1.fedora.pool.ntp.org,2.fedora.pool.ntp.org,3.fedora.pool.ntp.org</ns0:value>
      </ns0:Value>
      <ns0:Rule id="service_chronyd_or_ntpd_enabled" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Enable the NTP Daemon</ns0:title>
        <ns0:description xml:lang="en-US">
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">chronyd</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable chronyd.service</html:pre>
Note: The <html:code xmlns:html="http://www.w3.org/1999/xhtml">chronyd</html:code> daemon is enabled by default.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable ntpd.service</html:pre>
Note: The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code> daemon is not enabled by default. Though as mentioned
in the previous sections in certain environments the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code> daemon might
be preferred to be used rather than the <html:code xmlns:html="http://www.w3.org/1999/xhtml">chronyd</html:code> one. Refer to:
<html:a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html" xmlns:html="http://www.w3.org/1999/xhtml">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html</html:a>
for guidance which NTP daemon to choose depending on the environment used.
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-8(1)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">160</ns0:reference>
        <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.4</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.6</ns0:reference>
        <ns0:rationale xml:lang="en-US">Enabling some of <html:code xmlns:html="http://www.w3.org/1999/xhtml">chronyd</html:code> or <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code> services ensures
that the NTP daemon will be running and that the system will synchronize its
time to any servers specified. This is important whether the system is
configured to be a client (and synchronize only its own clock) or it is also
acting as an NTP server to other systems.  Synchronizing time is essential for
authentication services such as Kerberos, but it is also important for
maintaining accurate logs and auditing possible security breaches.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">chronyd</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code> NTP daemons offer all of the
functionality of <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpdate</html:code>, which is now deprecated. Additional
information on this is available at
<html:a href="http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate" xmlns:html="http://www.w3.org/1999/xhtml">http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate</html:a></ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_chronyd_or_ntpd_enabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">

if ! `rpm -q --quiet chrony` &amp;&amp; ! `rpm -q --quiet ntp-`; then
<ns0:sub idref="function_package_command" />
  package_command install chrony
  service_command enable chronyd
elif `rpm -q --quiet chrony`; then
  if ! [ `/usr/sbin/pidof ntpd` ] ; then
<ns0:sub idref="function_service_command" />
    service_command enable chronyd
  fi
else
<ns0:sub idref="function_service_command" />
  service_command enable ntpd
fi
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_chronyd_or_ntpd_enabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_chronyd_or_ntpd_enabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="chronyd_or_ntpd_specify_remote_server" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Specify a Remote NTP Server</ns0:title>
        <ns0:description xml:lang="en-US">Depending on specific functional requirements of a concrete
production environment, the Red Hat Enterprise Linux 7 Server system can be
configured to utilize the services of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">chronyd</html:code> NTP daemon (the
default), or services of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code> NTP daemon. Refer to
<html:a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html" xmlns:html="http://www.w3.org/1999/xhtml">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html</html:a>
for more detailed comparison of the features of both of the choices, and for
further guidance how to choose between the two NTP daemons.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To specify a remote NTP server for time synchronization, perform the following:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li> if the system is configured to use the <html:code>chronyd</html:code> as the NTP daemon (the
default), edit the file <html:code>/etc/chrony.conf</html:code> as follows,</html:li><html:li> if the system is configured to use the <html:code>ntpd</html:code> as the NTP daemon,
edit the file <html:code>/etc/ntp.conf</html:code> as documented below.</html:li></html:ul>
Add or correct the following lines, substituting the IP or hostname of a remote
NTP server for <html:em xmlns:html="http://www.w3.org/1999/xhtml">ntpserver</html:em>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">server <html:i>ntpserver</html:i></html:pre>
This instructs the NTP software to contact that remote server to obtain time
data.
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-8(1)</ns0:reference>
        <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">160</ns0:reference>
        <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.4.1</ns0:reference>
        <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.4.3</ns0:reference>
        <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.6</ns0:reference>
        <ns0:rationale xml:lang="en-US">Synchronizing with an NTP server makes it possible to collate system
logs from multiple sources or correlate computer events with real time events.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="chronyd_or_ntpd_specify_remote_server" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_multiple_time_servers="<ns0:sub idref="var_multiple_time_servers" />"

if ! `/usr/sbin/pidof ntpd`; then
  if ! `grep -q ^server /etc/chrony.conf` ; then
    if ! `grep -q '#[[:space:]]*server' /etc/chrony.conf` ; then
      for i in `echo "$var_multiple_time_servers" | tr ',' '\n'` ; do
        echo -ne "\nserver $i iburst" &gt;&gt; /etc/chrony.conf
      done
    else
      sed -i 's/#[ ]*server/server/g' /etc/chrony.conf
    fi
  fi
else
  if ! `grep -q ^server /etc/ntp.conf` ; then
    if ! `grep -q '#[[:space:]]*server' /etc/ntp.conf` ; then
      for i in `echo "$var_multiple_time_servers" | tr ',' '\n'` ; do
        echo -ne "\nserver $i iburst" &gt;&gt; /etc/ntp.conf
      done
    else
      sed -i 's/#[ ]*server/server/g' /etc/ntp.conf
    fi
  fi
fi
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-chronyd_or_ntpd_specify_remote_server:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-chronyd_or_ntpd_specify_remote_server_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="chronyd_or_ntpd_specify_multiple_servers" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Specify Additional Remote NTP Servers</ns0:title>
        <ns0:description xml:lang="en-US">Depending on specific functional requirements of a concrete
production environment, the Red Hat Enterprise Linux 7 Server system can be
configured to utilize the services of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">chronyd</html:code> NTP daemon (the
default), or services of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ntpd</html:code> NTP daemon. Refer to
<html:a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html" xmlns:html="http://www.w3.org/1999/xhtml">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html</html:a>
for more detailed comparison of the features of both of the choices, and for
further guidance how to choose between the two NTP daemons.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Additional NTP servers can be specified for time synchronization. To do so,
perform the following:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li> if the system is configured to use the <html:code>chronyd</html:code> as the NTP daemon
(the default), edit the file <html:code>/etc/chrony.conf</html:code> as follows,</html:li><html:li> if the system is configured to use the <html:code>ntpd</html:code> as the NTP daemon,
edit the file <html:code>/etc/ntp.conf</html:code> as documented below.</html:li></html:ul>
Add additional lines of the following form, substituting the IP address or
hostname of a remote NTP server for <html:em xmlns:html="http://www.w3.org/1999/xhtml">ntpserver</html:em>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">server <html:i>ntpserver</html:i></html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-8(1)</ns0:reference>
        <ns0:reference href="https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf">Req-10.4.3</ns0:reference>
        <ns0:rationale xml:lang="en-US">Specifying additional NTP servers increases the availability of
accurate time data, in the event that one of the specified servers becomes
unavailable. This is typical for a system acting as an NTP server for
other systems.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="chronyd_or_ntpd_specify_multiple_servers" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">
var_multiple_time_servers="<ns0:sub idref="var_multiple_time_servers" />"

if ! `/usr/sbin/pidof ntpd`; then
  if [ `grep -c '^server' /etc/chrony.conf` -lt 2 ]; then 
    if ! `grep -q '#[[:space:]]*server' /etc/chrony.conf` ; then
      for i in `echo "$var_multiple_time_servers" | tr ',' '\n'` ; do
        echo -ne "\nserver $i iburst" &gt;&gt; /etc/chrony.conf
      done
    else
      sed -i 's/#[ ]*server/server/g' /etc/chrony.conf
    fi
  fi
else
  if [ `grep -c '^server' /etc/ntp.conf` -lt 2 ]; then
    if ! `grep -q '#[[:space:]]*server' /etc/ntp.conf` ; then
      for i in `echo "$var_multiple_time_servers" | tr ',' '\n'` ; do
        echo -ne "\nserver $i iburst" &gt;&gt; /etc/ntp.conf
      done
    else
      sed -i 's/#[ ]*server/server/g' /etc/ntp.conf
    fi
  fi
fi
</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-chronyd_or_ntpd_specify_multiple_servers:def:1" />
        </ns0:check>
      </ns0:Rule>
    </ns0:Group>
    <ns0:Group id="mail">
      <ns0:title xml:lang="en-US">Mail Server Software</ns0:title>
      <ns0:description xml:lang="en-US">
Mail servers are used to send and receive email over the network.
Mail is a very common service, and Mail Transfer Agents (MTAs) are obvious
targets of network attack.
Ensure that machines are not running MTAs unnecessarily,
and configure needed MTAs as defensively as possible.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Very few systems at any site should be configured to directly receive email over the
network. Users should instead use mail client programs to retrieve email
from a central server that supports protocols such as IMAP or POP3.
However, it is normal for most systems to be independently capable of sending email,
for instance so that cron jobs can report output to an administrator.
Most MTAs, including Postfix, support a submission-only mode in which mail can be sent from
the local system to a central site MTA (or directly delivered to a local account),
but the system still cannot receive mail directly over a network.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">alternatives</html:code> program in Red Hat Enterprise Linux permits selection of other mail server software
(such as Sendmail), but Postfix is the default and is preferred.
Postfix was coded with security in mind and can also be more effectively contained by
SELinux as its modular design has resulted in separate processes performing specific actions.
More information is available on its website, <html:a href="http://www.postfix.org" xmlns:html="http://www.w3.org/1999/xhtml">http://www.postfix.org</html:a>.
</ns0:description>
      <ns0:Rule id="service_postfix_enabled" selected="false" severity="low">
        <ns0:title xml:lang="en-US">Enable Postfix Service</ns0:title>
        <ns0:description xml:lang="en-US">The Postfix mail transfer agent is used for local mail delivery
within the system. The default configuration only listens for connections to
the default SMTP port (port 25) on the loopback interface (127.0.0.1).  It is
recommended to leave this service enabled for local mail delivery.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">postfix</html:code> service can be enabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl enable postfix.service</html:pre>
</ns0:description>
        <ns0:rationale xml:lang="en-US">Local mail delivery is essential to some system maintenance and
notification tasks.
</ns0:rationale>
        <ns0:fix complexity="low" disruption="low" id="service_postfix_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command enable postfix
</ns0:fix>
        <ns0:fix complexity="low" disruption="low" id="service_postfix_enabled" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Enable service postfix
  service:
    name="{{item}}"
    enabled="yes"
    state="started"
  with_items:
    - postfix

</ns0:fix>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_postfix_enabled:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_postfix_enabled_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Rule id="package_sendmail_removed" selected="false" severity="medium">
        <ns0:title xml:lang="en-US">Uninstall Sendmail Package</ns0:title>
        <ns0:description xml:lang="en-US">Sendmail is not the default mail transfer agent and is
not installed by default.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">sendmail</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase sendmail</html:pre>
</ns0:description>
        <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
        <ns0:rationale xml:lang="en-US">The sendmail software was not developed with security in mind and
its design prevents it from being effectively contained by SELinux.  Postfix
should be used instead.  
</ns0:rationale>
        <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
          <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_sendmail_removed:def:1" />
        </ns0:check>
        <ns0:check system="http://scap.nist.gov/schema/ocil/2">
          <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_sendmail_removed_ocil:questionnaire:1" />
        </ns0:check>
      </ns0:Rule>
      <ns0:Group id="postfix_client">
        <ns0:title xml:lang="en-US">Configure SMTP For Mail Clients</ns0:title>
        <ns0:description xml:lang="en-US">This section discusses settings for Postfix in a submission-only
e-mail configuration.</ns0:description>
        <ns0:Rule id="postfix_network_listening_disabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable Postfix Network Listening</ns0:title>
          <ns0:description xml:lang="en-US">
Edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/postfix/main.cf</html:code> to ensure that only the following
<html:code xmlns:html="http://www.w3.org/1999/xhtml">inet_interfaces</html:code> line appears:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">inet_interfaces = localhost</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">382</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.16</ns0:reference>
          <ns0:rationale xml:lang="en-US">
This ensures <html:code xmlns:html="http://www.w3.org/1999/xhtml">postfix</html:code> accepts mail messages
(such as cron job reports) from the local system only,
and not from the network, which protects it from network attack.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-postfix_network_listening_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-postfix_network_listening_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="postfix_harden_os">
        <ns0:title xml:lang="en-US">Configure Operating System to Protect Mail Server
</ns0:title>
        <ns0:description xml:lang="en-US">The guidance in this section is appropriate for any host which is
operating as a site MTA, whether the mail server runs using Sendmail, Postfix,
or some other software.
</ns0:description>
        <ns0:Group id="postfix_configure_ssl_certs">
          <ns0:title xml:lang="en-US">Configure SSL Certificates for Use with SMTP AUTH</ns0:title>
          <ns0:description xml:lang="en-US">
If SMTP AUTH is to be used, the use of SSL to protect credentials in transit is strongly recommended.
There are also configurations for which it may be desirable to encrypt all mail in transit from one MTA to another,
though such configurations are beyond the scope of this guide. In either event, the steps for creating and installing
an SSL certificate are independent of the MTA in use, and are described here.
</ns0:description>
          <ns0:Group id="postfix_install_ssl_cert">
            <ns0:title xml:lang="en-US">Ensure Security of Postfix SSL Certificate</ns0:title>
            <ns0:description xml:lang="en-US">Create the PKI directory for mail certificates, if it does not already exist:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo mkdir /etc/pki/tls/mail
$ sudo chown root:root /etc/pki/tls/mail
$ sudo chmod 755 /etc/pki/tls/mail</html:pre>
Using removable media or some other secure transmission format, install the files generated in the previous
step onto the mail server:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/etc/pki/tls/mail/serverkey.pem: the private key mailserverkey.pem
/etc/pki/tls/mail/servercert.pem: the certificate file mailservercert.pem</html:pre>
Verify the ownership and permissions of these files:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root:root /etc/pki/tls/mail/serverkey.pem
$ sudo chown root:root /etc/pki/tls/mail/servercert.pem
$ sudo chmod 600 /etc/pki/tls/mail/serverkey.pem
$ sudo chmod 644 /etc/pki/tls/mail/servercert.pem</html:pre>
Verify that the CA's public certificate file has been installed as <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pki/tls/CA/cacert.pem</html:code>, and has the
correct permissions:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root:root /etc/pki/tls/CA/cacert.pem
$ sudo chmod 644 /etc/pki/tls/CA/cacert.pem</html:pre>
</ns0:description>
          </ns0:Group>
        </ns0:Group>
        <ns0:Group id="postfix_server_configuration">
          <ns0:title xml:lang="en-US">Configure Postfix if Necessary</ns0:title>
          <ns0:description xml:lang="en-US">Postfix stores its configuration files in the directory
/etc/postfix by default. The primary configuration file is
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/postfix/main.cf</html:code>.
</ns0:description>
          <ns0:Rule id="postfix_server_banner" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Configure SMTP Greeting Banner</ns0:title>
            <ns0:description xml:lang="en-US">Edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/postfix/main.cf</html:code>, and add or correct the
following line, substituting some other wording for the banner information if
you prefer:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">smtpd_banner = $myhostname ESMTP</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-22</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AU-13</ns0:reference>
            <ns0:rationale xml:lang="en-US">The default greeting banner discloses that the listening mail
process is Postfix.  When remote mail senders connect to the MTA on port 25,
they are greeted by an initial banner as part of the SMTP dialogue. This banner
is necessary, but it frequently gives away too much information, including the
MTA software which is in use, and sometimes also its version number. Remote
mail senders do not need this information in order to send mail, so the banner
should be changed to reveal only the hostname (which is already known and may
be useful) and the word ESMTP, to indicate that the modern SMTP protocol
variant is supported.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-postfix_server_banner:def:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Group id="postfix_server_denial_of_service">
            <ns0:title xml:lang="en-US">Configure Postfix Resource Usage to Limit Denial of Service Attacks</ns0:title>
            <ns0:description xml:lang="en-US">Edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/postfix/main.cf</html:code>. Edit the following lines to
configure the amount of system resources Postfix can consume:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">default_process_limit = 100
smtpd_client_connection_count_limit = 10
smtpd_client_connection_rate_limit = 30
queue_minfree = 20971520
header_size_limit = 51200
message_size_limit = 10485760
smtpd_recipient_limit = 100</html:pre>
The values here are examples.
</ns0:description>
            <ns0:warning category="general" xml:lang="en-US">Note: The values given here are examples, and may
need to be modified for any particular site. By default, the Postfix anvil
process gathers mail receipt statistics. To get information about about what
connection rates are typical at your site, look in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log/maillog</html:code>
for lines with the daemon name postfix/anvil.
</ns0:warning>
            <ns0:rationale xml:lang="en-US">These configuration options serve to make it more difficult for
attackers to consume resources on the MTA host.  The
<html:code xmlns:html="http://www.w3.org/1999/xhtml">default_process_limit</html:code> parameter controls how many <html:code xmlns:html="http://www.w3.org/1999/xhtml">smtpd</html:code>
processes can exist at a time, while
<html:code xmlns:html="http://www.w3.org/1999/xhtml">smtpd_client_connection_count_limit</html:code> controls the number of those which
can be occupied by any one remote sender, and
<html:code xmlns:html="http://www.w3.org/1999/xhtml">smtpd_client_connection_rate_limit</html:code> controls the number of connections
any one client can make per minute. By default, local hosts (those in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">mynetworks</html:code>) are exempted from per-client rate limiting.  The
<html:code xmlns:html="http://www.w3.org/1999/xhtml">queue_minfree</html:code> parameter establishes a free space threshold, in order
to stop e-mail receipt before the queue filesystem is entirely full. The
<html:code xmlns:html="http://www.w3.org/1999/xhtml">header_size_limit</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">message_size_limit</html:code>, and
<html:code xmlns:html="http://www.w3.org/1999/xhtml">smtpd_recipient_limit</html:code> parameters place bounds on the legal sizes of
messages received via SMTP.
</ns0:rationale>
          </ns0:Group>
          <ns0:Group id="postfix_server_mail_relay">
            <ns0:title xml:lang="en-US">Control Mail Relaying</ns0:title>
            <ns0:description xml:lang="en-US">Postfix's mail relay controls are implemented with the help of the
smtpd recipient restrictions option, which controls the restrictions placed on
the SMTP dialogue once the sender and recipient envelope addresses are known.
The guidance in the following sections should be applied to all machines. If
there are machines which must be allowed to relay mail, but which cannot be
trusted to relay unconditionally, configure SMTP AUTH with SSL support.
</ns0:description>
            <ns0:Group id="postfix_server_mail_relay_set_trusted_networks">
              <ns0:title xml:lang="en-US">Configure Trusted Networks and Hosts</ns0:title>
              <ns0:description xml:lang="en-US">Edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/postfix/main.cf</html:code>, and configure the contents of
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mynetworks</html:code> variable in one of the following ways:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>If any machine in the subnet containing the MTA may be trusted to relay
messages, add or correct the following line:
<html:pre>mynetworks_style = subnet</html:pre>
This is also the default setting, and is in effect if all
<html:code>my_networks_style</html:code> directives are commented.</html:li><html:li>If only the MTA host itself is trusted to relay messages, add or correct
the following line:
<html:pre>mynetworks_style = host</html:pre></html:li><html:li>If the set of machines which can relay is more complicated, manually
specify an entry for each netblock or IP address which is trusted to relay by
setting the <html:code>mynetworks</html:code> variable directly:
<html:pre>mynetworks = 10.0.0.0/16, 192.168.1.0/24, 127.0.0.1</html:pre></html:li></html:ul>
</ns0:description>
              <ns0:rationale xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">mynetworks</html:code> variable must contain only the set of
machines for which this MTA should unconditionally relay mail. This is a trust
relationship - if spammers gain access to these machines, your site will
effectively become an open relay. It is recommended that only machines which
are managed by you or by another trusted organization be placed in mynetworks,
and users of all other machines be required to use SMTP AUTH to send mail.
</ns0:rationale>
            </ns0:Group>
            <ns0:Group id="postfix_server_mail_smtpd_relay_restrictions">
              <ns0:title xml:lang="en-US">Enact SMTP Relay Restrictions</ns0:title>
              <ns0:description xml:lang="en-US">
To configure Postfix to restrict addresses to which it
will send mail, see:
<html:a href="http://www.postfix.org/SMTPD_ACCESS_README.html#danger" xmlns:html="http://www.w3.org/1999/xhtml">http://www.postfix.org/SMTPD_ACCESS_README.html#danger</html:a>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The full contents of <html:code xmlns:html="http://www.w3.org/1999/xhtml">smtpd_recipient_restrictions</html:code> will
vary by site, since this is a common place to put spam restrictions and other
site-specific options. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">permit_mynetworks</html:code> option allows all mail to
be relayed from the machines in <html:code xmlns:html="http://www.w3.org/1999/xhtml">mynetworks</html:code>. Then, the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">reject_unauth_destination</html:code> option denies all mail whose destination
address is not local, preventing any other machines from relaying. These two
options should always appear in this order, and should usually follow one
another immediately unless SMTP AUTH is used.
</ns0:description>
            </ns0:Group>
            <ns0:Group id="postfix_server_mail_smtpd_recipient_restrictions">
              <ns0:title xml:lang="en-US">Enact SMTP Recipient Restrictions</ns0:title>
              <ns0:description xml:lang="en-US">
To configure Postfix to restrict addresses to which it
will send mail, see:
<html:a href="http://www.postfix.org/SMTPD_ACCESS_README.html#danger" xmlns:html="http://www.w3.org/1999/xhtml">http://www.postfix.org/SMTPD_ACCESS_README.html#danger</html:a>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The full contents of <html:code xmlns:html="http://www.w3.org/1999/xhtml">smtpd_recipient_restrictions</html:code> will
vary by site, since this is a common place to put spam restrictions and other
site-specific options. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">permit_mynetworks</html:code> option allows all mail to
be relayed from the machines in <html:code xmlns:html="http://www.w3.org/1999/xhtml">mynetworks</html:code>. Then, the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">reject_unauth_destination</html:code> option denies all mail whose destination
address is not local, preventing any other machines from relaying. These two
options should always appear in this order, and should usually follow one
another immediately unless SMTP AUTH is used.
</ns0:description>
            </ns0:Group>
            <ns0:Group id="postfix_server_mail_relay_smtp_auth_for_untrusted_networks">
              <ns0:title xml:lang="en-US">Require SMTP AUTH Before Relaying from Untrusted Clients</ns0:title>
              <ns0:description xml:lang="en-US">SMTP authentication allows remote clients to relay mail safely by
requiring them to authenticate before submitting mail. Postfix's SMTP AUTH uses
an authentication library called SASL, which is not part of Postfix itself.  To
enable the use of SASL authentication, see
<html:a href="http://www.postfix.org/SASL_README.html" xmlns:html="http://www.w3.org/1999/xhtml">http://www.postfix.org/SASL_README.html</html:a>
</ns0:description>
            </ns0:Group>
            <ns0:Group id="postfix_server_mail_relay_require_tls_for_smtp_auth">
              <ns0:title xml:lang="en-US">Use TLS for SMTP AUTH</ns0:title>
              <ns0:description xml:lang="en-US">
Postfix provides options to use TLS for certificate-based
authentication and encrypted sessions. An encrypted session protects the
information that is transmitted with SMTP mail or with SASL authentication.
To configure Postfix to protect all SMTP AUTH transactions
using TLS, see <html:a href="http://www.postfix.org/TLS_README.html" xmlns:html="http://www.w3.org/1999/xhtml">http://www.postfix.org/TLS_README.html</html:a>.
</ns0:description>
            </ns0:Group>
          </ns0:Group>
        </ns0:Group>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="ldap">
      <ns0:title xml:lang="en-US">LDAP</ns0:title>
      <ns0:description xml:lang="en-US">LDAP is a popular directory service, that is, a
standardized way of looking up information from a central database.
Red Hat Enterprise Linux 7 includes software that enables a system to act as both
an LDAP client and server.
</ns0:description>
      <ns0:Group id="openldap_client">
        <ns0:title xml:lang="en-US">Configure OpenLDAP Clients</ns0:title>
        <ns0:description xml:lang="en-US">This section provides information on which security settings are
important to configure in OpenLDAP clients by manually editing the appropriate
configuration files.  Red Hat Enterprise Linux 7 provides an automated configuration tool called
authconfig and a graphical wrapper for authconfig called
<html:code xmlns:html="http://www.w3.org/1999/xhtml">system-config-authentication</html:code>. However, these tools do not provide as
much control over configuration as manual editing of configuration files. The
authconfig tools do not allow you to specify locations of SSL certificate
files, which is useful when trying to use SSL cleanly across several protocols.
Installation and configuration of OpenLDAP on Red Hat Enterprise Linux 7 is available at
<html:a href="https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Directory_Servers.html" xmlns:html="http://www.w3.org/1999/xhtml">https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Directory_Servers.html</html:a>.
</ns0:description>
        <ns0:warning category="general" xml:lang="en-US">Before configuring any system to be an
LDAP client, ensure that a working LDAP server is present on the
network.</ns0:warning>
        <ns0:Rule id="ldap_client_start_tls" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure LDAP Client to Use TLS For All Transactions</ns0:title>
          <ns0:description xml:lang="en-US">This check verifies that RHEL7 impliments cryptography
to protect the integrity of remote LDAP authentication sessions.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To determine if LDAP is being used for authentication, use the following
command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo grep -i useldapauth /etc/sysconfig/authconfig</html:pre>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If <html:code xmlns:html="http://www.w3.org/1999/xhtml">USELDAPAUTH=yes</html:code>, then LDAP is being used. To check if LDAP is
configured to use TLS, use the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo grep -i ssl /etc/pam_ldap.conf</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-17(2)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1453</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000250-GPOS-00093</ns0:reference>
          <ns0:rationale xml:lang="en-US">Without cryptographic integrity protections, information can be
altered by unauthorized users without detection. The ssl directive specifies 
whether to use TLS or not. If not specified it will default to no. 
It should be set to start_tls rather than doing LDAP over SSL.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-ldap_client_start_tls:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-ldap_client_start_tls_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="ldap_client_tls_cacertpath" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure Certificate Directives for LDAP Use of TLS</ns0:title>
          <ns0:description xml:lang="en-US">Ensure a copy of a trusted CA certificate has been placed in
the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pki/tls/CA/cacert.pem</html:code>. Configure LDAP to enforce TLS 
use and to trust certificates signed by that CA. First, edit the file 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/nslcd.conf</html:code>, and add or correct either of the following lines:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">tls_cacertdir /etc/pki/tls/CA</html:pre>
or
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">tls_cacertfile /etc/pki/tls/CA/cacert.pem</html:pre>
Then review the LDAP server and ensure TLS has been configured.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">776</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">778</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1453</ns0:reference>
          <ns0:rationale xml:lang="en-US">The tls_cacertdir or tls_cacertfile directives are required when
tls_checkpeer is configured (which is the default for openldap versions 2.1 and
up). These directives define the path to the trust certificates signed by the
site CA.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-ldap_client_tls_cacertpath:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-ldap_client_tls_cacertpath_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="openldap_server">
        <ns0:title xml:lang="en-US">Configure OpenLDAP Server</ns0:title>
        <ns0:description xml:lang="en-US">This section details some security-relevant settings
for an OpenLDAP server.  Installation and configuration of OpenLDAP on Red Hat Enterprise Linux 7 is available at:
<html:a href="https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Directory_Servers.html" xmlns:html="http://www.w3.org/1999/xhtml">https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Directory_Servers.html</html:a>.
</ns0:description>
        <ns0:Rule id="package_openldap-servers_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Uninstall openldap-servers Package</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">openldap-servers</html:code> package should be removed if not in use.
Is this machine the OpenLDAP server? If not, remove the package.
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase openldap-servers</html:pre>
The openldap-servers RPM is not installed by default on Red Hat Enterprise Linux 7
machines. It is needed only by the OpenLDAP server, not by the
clients which use LDAP for authentication. If the system is not
intended for use as an LDAP Server it should be removed.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.7</ns0:reference>
          <ns0:rationale xml:lang="en-US">Unnecessary packages should not be installed to decrease the attack
surface of the system.  While this software is clearly essential on an LDAP
server, it is not necessary on typical desktop or workstation systems.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_openldap-servers_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_openldap-servers_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="ldap_server_config_certificate_files">
          <ns0:title xml:lang="en-US">Install and Protect LDAP Certificate Files</ns0:title>
          <ns0:description xml:lang="en-US">Create the PKI directory for LDAP certificates if it does not already exist:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo mkdir /etc/pki/tls/ldap
$ sudo chown root:root /etc/pki/tls/ldap
$ sudo chmod 755 /etc/pki/tls/ldap</html:pre>
Using removable media or some other secure transmission format, install the certificate files
onto the LDAP server:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li><html:code>/etc/pki/tls/ldap/serverkey.pem</html:code>: the private key <html:code>ldapserverkey.pem</html:code></html:li><html:li><html:code>/etc/pki/tls/ldap/servercert.pem</html:code>: the certificate file <html:code>ldapservercert.pem</html:code></html:li></html:ul>
Verify the ownership and permissions of these files:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chown root:ldap /etc/pki/tls/ldap/serverkey.pem
$ sudo chown root:ldap /etc/pki/tls/ldap/servercert.pem
$ sudo chmod 640 /etc/pki/tls/ldap/serverkey.pem
$ sudo chmod 640 /etc/pki/tls/ldap/servercert.pem</html:pre>
Verify that the CA's public certificate file has been installed as
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/pki/tls/CA/cacert.pem</html:code>, and has the correct permissions:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo mkdir /etc/pki/tls/CA
$ sudo chown root:root /etc/pki/tls/CA/cacert.pem
$ sudo chmod 644 /etc/pki/tls/CA/cacert.pem</html:pre>

As a result of these steps, the LDAP server will have access to its own private
certificate and the key with which that certificate is encrypted, and to the
public certificate file belonging to the CA. Note that it would be possible for
the key to be protected further, so that processes running as ldap could not
read it. If this were done, the LDAP server process would need to be restarted
manually whenever the server rebooted.
</ns0:description>
        </ns0:Group>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="nfs_and_rpc">
      <ns0:title xml:lang="en-US">NFS and RPC</ns0:title>
      <ns0:description xml:lang="en-US">The Network File System is a popular distributed filesystem for
the Unix environment, and is very widely deployed.  This section discusses the
circumstances under which it is possible to disable NFS and its dependencies,
and then details steps which should be taken to secure
NFS's configuration. This section is relevant to machines operating as NFS
clients, as well as to those operating as NFS servers.
</ns0:description>
      <ns0:Group id="disabling_nfs">
        <ns0:title xml:lang="en-US">Disable All NFS Services if Possible</ns0:title>
        <ns0:description xml:lang="en-US">If there is not a reason for the system to operate as either an
NFS client or an NFS server, follow all instructions in this section to disable
subsystems required by NFS.
</ns0:description>
        <ns0:warning category="general" xml:lang="en-US">The steps in this section will prevent a machine
from operating as either an NFS client or an NFS server. Only perform these
steps on machines which do not need NFS at all.</ns0:warning>
        <ns0:Group id="disabling_nfs_services">
          <ns0:title xml:lang="en-US">Disable Services Used Only by NFS</ns0:title>
          <ns0:description xml:lang="en-US">If NFS is not needed, disable the NFS client daemons nfslock, rpcgssd, and rpcidmapd.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
All of these daemons run with elevated privileges, and many listen for network
connections. If they are not needed, they should be disabled to improve system
security posture.</ns0:description>
          <ns0:Rule id="service_nfslock_disabled" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable Network File System Lock Service (nfslock)</ns0:title>
            <ns0:description xml:lang="en-US">The Network File System Lock (nfslock) service starts the required
remote procedure call (RPC) processes which allow clients to lock files on the
server. If the local machine is not configured to mount NFS filesystems then
this service should be disabled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nfslock</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable nfslock.service</html:pre>
</ns0:description>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.8</ns0:reference>
            <ns0:fix complexity="low" disruption="low" id="service_nfslock_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">#
# Disable nfs-lock.service for all systemd targets
#
systemctl disable nfs-lock.service

#
# Stop nfs-lock.service if currently running
#
systemctl stop nfs-lock.service
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_nfslock_disabled:def:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="service_rpcgssd_disabled" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable Secure RPC Client Service (rpcgssd)</ns0:title>
            <ns0:description xml:lang="en-US">
The rpcgssd service manages RPCSEC GSS contexts required to secure protocols
that use RPC (most often Kerberos and NFS). The rpcgssd service is the
client-side of RPCSEC GSS. If the system does not require secure RPC then this
service should be disabled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rpcgssd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable rpcgssd.service</html:pre>
</ns0:description>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.8</ns0:reference>
            <ns0:fix complexity="low" disruption="low" id="service_rpcgssd_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">#
# Disable nfs-secure.service (rpcgssd) for all systemd targets
#
systemctl disable nfs-secure.service

#
# Stop nfs-secure.service (rpcgssd) if currently running
#
systemctl stop nfs-secure.service
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_rpcgssd_disabled:def:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="service_rpcbind_disabled" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable rpcbind Service</ns0:title>
            <ns0:description xml:lang="en-US">
The rpcbind utility maps RPC services to the ports on which they listen. RPC
processes notify rpcbind when they start, registering the ports they are
listening on and the RPC program numbers they expect to serve. The rpcbind
service redirects the client to the proper port number so it can communicate 
with the requested service. If the system does not require RPC (such as for NFS
servers) then this service should be disabled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rpcbind</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable rpcbind.service</html:pre>
</ns0:description>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.8</ns0:reference>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_rpcbind_disabled:def:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="service_rpcidmapd_disabled" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable RPC ID Mapping Service (rpcidmapd)</ns0:title>
            <ns0:description xml:lang="en-US">The rpcidmapd service is used to map user names and groups to UID
and GID numbers on NFSv4 mounts. If NFS is not in use on the local system then
this service should be disabled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rpcidmapd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable rpcidmapd.service</html:pre>
</ns0:description>
            <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.8</ns0:reference>
            <ns0:fix complexity="low" disruption="low" id="service_rpcidmapd_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">#
# Disable nfs-idmap.service (rpcidmapd) for all systemd targets
#
systemctl disable nfs-idmap.service

#
# Stop nfs-idmap.service (rpcidmapd) if currently running
#
systemctl stop nfs-idmap.service
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_rpcidmapd_disabled:def:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="nfs_configuring_all_machines">
        <ns0:title xml:lang="en-US">Configure All Machines which Use NFS</ns0:title>
        <ns0:description xml:lang="en-US">The steps in this section are appropriate for all machines which
run NFS, whether they operate as clients or as servers.</ns0:description>
        <ns0:Group id="nfs_client_or_server_not_both">
          <ns0:title xml:lang="en-US">Make Each Machine a Client or a Server, not Both</ns0:title>
          <ns0:description xml:lang="en-US">If NFS must be used, it should be deployed in the simplest
configuration possible to avoid maintainability problems which may lead to
unnecessary security exposure. Due to the reliability and security problems
caused by NFS (specially NFSv3 and NFSv2), it is not a good idea for machines
which act as NFS servers to also mount filesystems via NFS. At the least,
crossed mounts (the situation in which each of two servers mounts a filesystem
from the other) should never be used.
</ns0:description>
        </ns0:Group>
        <ns0:Group id="nfs_configure_fixed_ports">
          <ns0:title xml:lang="en-US">Configure NFS Services to Use Fixed Ports (NFSv3 and NFSv2)</ns0:title>
          <ns0:description xml:lang="en-US">Firewalling should be done at each host and at the border
firewalls to protect the NFS daemons from remote access, since NFS servers
should never be accessible from outside the organization. However, by default
for NFSv3 and NFSv2, the RPC Bind service assigns each NFS service to a port
dynamically at service startup time. Dynamic ports cannot be protected by port
filtering firewalls such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Therefore, restrict each service to always use a given port, so that
firewalling can be done effectively. Note that, because of the way RPC is
implemented, it is not possible to disable the RPC Bind service even if ports
are assigned statically to all RPC services.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
In NFSv4, the mounting and locking protocols have been incorporated into the
protocol, and the server listens on the the well-known TCP port 2049. As such,
NFSv4 does not need to interact with the <html:code xmlns:html="http://www.w3.org/1999/xhtml">rpcbind, lockd, and rpc.statd</html:code>
daemons, which can and should be disabled in a pure NFSv4 environment. The
<html:code xmlns:html="http://www.w3.org/1999/xhtml">rpc.mountd</html:code> daemon is still required on the NFS server to setup
exports, but is not involved in any over-the-wire operations.
</ns0:description>
          <ns0:Rule id="nfs_fixed_lockd_tcp_port" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Configure lockd to use static TCP port</ns0:title>
            <ns0:description xml:lang="en-US">Configure the <html:code xmlns:html="http://www.w3.org/1999/xhtml">lockd</html:code> daemon to use a static TCP port as
opposed to letting the RPC Bind service dynamically assign a port. Edit the
file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/nfs</html:code>. Add or correct the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">LOCKD_TCPPORT=lockd-port</html:pre>
Where <html:code xmlns:html="http://www.w3.org/1999/xhtml">lockd-port</html:code> is a port which is not used by any other service on
your network. 
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Restrict service to always use a given port, so that firewalling can be done
effectively.
</ns0:rationale>
            </ns0:Rule>
          <ns0:Rule id="nfs_fixed_lockd_udp_port" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Configure lockd to use static UDP port</ns0:title>
            <ns0:description xml:lang="en-US">Configure the <html:code xmlns:html="http://www.w3.org/1999/xhtml">lockd</html:code> daemon to use a static UDP port as
opposed to letting the RPC Bind service dynamically assign a port. Edit the
file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/nfs</html:code>. Add or correct the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">LOCKD_UDPPORT=lockd-port</html:pre>
Where <html:code xmlns:html="http://www.w3.org/1999/xhtml">lockd-port</html:code> is a port which is not used by any other service on
your network.
</ns0:description>
            <ns0:rationale xml:lang="en-US"> Restricting services to always use a given port enables firewalling
to be done more effectively.
</ns0:rationale>
            </ns0:Rule>
          <ns0:Rule id="nfs_fixed_statd_port" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Configure statd to use static port</ns0:title>
            <ns0:description xml:lang="en-US">Configure the <html:code xmlns:html="http://www.w3.org/1999/xhtml">statd</html:code> daemon to use a static port as
opposed to letting the RPC Bind service dynamically assign a port. Edit the
file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/nfs</html:code>. Add or correct the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">STATD_PORT=statd-port</html:pre>
Where <html:code xmlns:html="http://www.w3.org/1999/xhtml">statd-port</html:code> is a port which is not used by any other service on your network. 
</ns0:description>
            <ns0:rationale xml:lang="en-US"> Restricting services to always use a given port enables firewalling
to be done more effectively.
</ns0:rationale>
            </ns0:Rule>
          <ns0:Rule id="nfs_fixed_mountd_port" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Configure mountd to use static port</ns0:title>
            <ns0:description xml:lang="en-US">Configure the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mountd</html:code> daemon to use a static port as
opposed to letting the RPC Bind service dynamically assign a port. Edit the
file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/nfs</html:code>. Add or correct the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">MOUNTD_PORT=statd-port</html:pre>
Where <html:code xmlns:html="http://www.w3.org/1999/xhtml">mountd-port</html:code> is a port which is not used by any other service on your network. 
</ns0:description>
            <ns0:rationale xml:lang="en-US"> Restricting services to always use a given port enables firewalling
to be done more effectively.
</ns0:rationale>
            </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="nfs_configuring_clients">
        <ns0:title xml:lang="en-US">Configure NFS Clients</ns0:title>
        <ns0:description xml:lang="en-US">The steps in this section are appropriate for machines which operate as NFS clients.</ns0:description>
        <ns0:Group id="disabling_nfsd">
          <ns0:title xml:lang="en-US">Disable NFS Server Daemons</ns0:title>
          <ns0:description xml:lang="en-US">
There is no need to run the NFS server daemons <html:code xmlns:html="http://www.w3.org/1999/xhtml">nfs</html:code> and
<html:code xmlns:html="http://www.w3.org/1999/xhtml">rpcsvcgssd</html:code> except on a small number of properly secured machines
designated as NFS servers. Ensure that these daemons are turned off on
clients.</ns0:description>
          <ns0:Rule id="nfs_no_anonymous" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Specify UID and GID for Anonymous NFS Connections</ns0:title>
            <ns0:description xml:lang="en-US">To specify the UID and GID for remote root users, edit the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/exports</html:code> file and add the following for each export:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">
anonuid=<html:code>value greater than UID_MAX from /etc/login.defs</html:code>
anongid=<html:code>value greater than GID_MAX from /etc/login.defs</html:code> 
</html:pre>
Alternatively, functionally equivalent values of 60001, 65534, 65535 may be used.
</ns0:description>
            <ns0:rationale xml:lang="en-US">Specifying the anonymous UID and GID ensures that the remote root user is mapped 
to a local account which has no permissions on the system.</ns0:rationale>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-nfs_no_anonymous_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="service_nfs_disabled" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable Network File System (nfs)</ns0:title>
            <ns0:description xml:lang="en-US">The Network File System (NFS) service allows remote hosts to mount
and interact with shared filesystems on the local machine. If the local machine
is not designated as a NFS server then this service should be disabled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">nfs</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable nfs.service</html:pre>
</ns0:description>
            <ns0:rationale xml:lang="en-US">Unnecessary services should be disabled to decrease the attack surface of the system.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="service_nfs_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable nfs
</ns0:fix>
            <ns0:fix complexity="low" disruption="low" id="service_nfs_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service nfs
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - nfs

</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_nfs_disabled:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_nfs_disabled_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="service_rpcsvcgssd_disabled" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable Secure RPC Server Service (rpcsvcgssd)</ns0:title>
            <ns0:description xml:lang="en-US">The rpcsvcgssd service manages RPCSEC GSS contexts required to
secure protocols that use RPC (most often Kerberos and NFS). The rpcsvcgssd
service is the server-side of RPCSEC GSS. If the system does not require secure
RPC then this service should be disabled.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">rpcsvcgssd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable rpcsvcgssd.service</html:pre>
</ns0:description>
            <ns0:rationale xml:lang="en-US">Unnecessary services should be disabled to decrease the attack surface of the system.</ns0:rationale>
            <ns0:fix complexity="low" disruption="low" id="service_rpcsvcgssd_disabled" reboot="false" strategy="configure" system="urn:xccdf:fix:script:sh">#
# Disable nfs-secure-server.service (rpcsvcgssd) for all systemd targets
#
systemctl disable nfs-secure-server.service

#
# Stop nfs-secure-server.service (rpcsvcgssd) if currently running
#
systemctl stop nfs-secure-server.service
</ns0:fix>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_rpcsvcgssd_disabled:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_rpcsvcgssd_disabled_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="mounting_remote_filesystems">
          <ns0:title xml:lang="en-US">Mount Remote Filesystems with Restrictive Options</ns0:title>
          <ns0:description xml:lang="en-US">Edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code>. For each filesystem whose type
(column 3) is <html:code xmlns:html="http://www.w3.org/1999/xhtml">nfs</html:code> or <html:code xmlns:html="http://www.w3.org/1999/xhtml">nfs4</html:code>, add the text
<html:code xmlns:html="http://www.w3.org/1999/xhtml">,nodev,nosuid</html:code> to the list of mount options in column 4. If
appropriate, also add <html:code xmlns:html="http://www.w3.org/1999/xhtml">,noexec</html:code>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
See the section titled "Restrict Partition Mount Options" for a description of
the effects of these options. In general, execution of files mounted via NFS
should be considered risky because of the possibility that an adversary could
intercept the request and substitute a malicious file. Allowing setuid files to
be executed from remote servers is particularly risky, both for this reason and
because it requires the clients to extend root-level trust to the NFS
server.</ns0:description>
          <ns0:Rule id="mount_option_nodev_remote_filesystems" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Mount Remote Filesystems with nodev</ns0:title>
            <ns0:description xml:lang="en-US">
              
	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nodev</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	any NFS mounts.
	
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">MP-2</ns0:reference>
            <ns0:rationale xml:lang="en-US">Legitimate device files should only exist in the /dev directory. NFS mounts
should not present device files to users.</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_nodev_remote_filesystems:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-mount_option_nodev_remote_filesystems_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="mount_option_nosuid_remote_filesystems" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Mount Remote Filesystems with nosuid</ns0:title>
            <ns0:description xml:lang="en-US">
              
	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">nosuid</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	any NFS mounts.
	
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-6</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">NFS mounts should not present suid binaries to users. Only vendor-supplied suid executables
should be installed to their default location on the local filesystem.</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_nosuid_remote_filesystems:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-mount_option_nosuid_remote_filesystems_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="mount_option_krb_sec_remote_filesystems" selected="false" severity="medium">
            <ns0:title xml:lang="en-US">Mount Remote Filesystems with Kerberos Security</ns0:title>
            <ns0:description xml:lang="en-US">
              
	Add the <html:code xmlns:html="http://www.w3.org/1999/xhtml">sec=krb5:krb5i:krb5p</html:code> option to the fourth column of
	<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code> for the line which controls mounting of
	any NFS mounts.
	
            </ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-14(1)</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
            <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
            <ns0:rationale xml:lang="en-US">
When an NFS server is configured to use AUTH_SYS a selected userid and groupid are used to handle
requests from the remote user. The userid and groupid could mistakenly or maliciously be set
incorrectly. The AUTH_GSS method of authentication uses certificates on the server and client
systems to more securely authenticate the remote mount request.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_krb_sec_remote_filesystems:def:1" />
            </ns0:check>
            <ns0:check system="http://scap.nist.gov/schema/ocil/2">
              <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-mount_option_krb_sec_remote_filesystems_ocil:questionnaire:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="nfs_configuring_servers">
        <ns0:title xml:lang="en-US">Configure NFS Servers</ns0:title>
        <ns0:description xml:lang="en-US">The steps in this section are appropriate for machines which operate as NFS servers.</ns0:description>
        <ns0:Group id="configure_exports_restrictively">
          <ns0:title xml:lang="en-US">Configure the Exports File Restrictively</ns0:title>
          <ns0:description xml:lang="en-US">Linux's NFS implementation uses the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/exports</html:code> to control what filesystems
and directories may be accessed via NFS. (See the <html:code xmlns:html="http://www.w3.org/1999/xhtml">exports(5)</html:code> manpage for more information about the
format of this file.)
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The syntax of the <html:code xmlns:html="http://www.w3.org/1999/xhtml">exports</html:code> file is not necessarily checked fully on reload, and syntax errors
can leave your NFS configuration more open than intended. Therefore, exercise caution when modifying
the file.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The syntax of each line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/exports</html:code> is:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">/DIR	host1(opt1,opt2) host2(opt3)</html:pre>
where <html:code xmlns:html="http://www.w3.org/1999/xhtml">/DIR</html:code> is a directory or filesystem to export, <html:code xmlns:html="http://www.w3.org/1999/xhtml">hostN</html:code> is an IP address, netblock,
hostname, domain, or netgroup to which to export, and <html:code xmlns:html="http://www.w3.org/1999/xhtml">optN</html:code> is an option.
</ns0:description>
        </ns0:Group>
        <ns0:Group id="use_acl_enforce_auth_restrictions">
          <ns0:title xml:lang="en-US">Use Access Lists to Enforce Authorization Restrictions</ns0:title>
          <ns0:description xml:lang="en-US">When configuring NFS exports, ensure that each export line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/exports</html:code> contains
a list of hosts which are allowed to access that export. If no hosts are specified on an export line,
then that export is available to any remote host which requests it. All lines of the exports file should
specify the hosts (or subnets, if needed) which are allowed to access the exported directory, so that
unknown or remote hosts will be denied.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Authorized hosts can be specified in several different formats:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>Name or alias that is recognized by the resolver</html:li><html:li>Fully qualified domain name</html:li><html:li>IP address</html:li><html:li>IP subnets in the format <html:code>address/netmask</html:code> or <html:code>address/CIDR</html:code></html:li></html:ul>
</ns0:description>
        </ns0:Group>
        <ns0:Group id="export_filesystems_read_only">
          <ns0:title xml:lang="en-US">Export Filesystems Read-Only if Possible</ns0:title>
          <ns0:description xml:lang="en-US">If a filesystem is being exported so that users can view the files in a convenient
fashion, but there is no need for users to edit those files, exporting the filesystem read-only
removes an attack vector against the server. The default filesystem export mode is <html:code xmlns:html="http://www.w3.org/1999/xhtml">ro</html:code>,
so do not specify <html:code xmlns:html="http://www.w3.org/1999/xhtml">rw</html:code> without a good reason.
</ns0:description>
        </ns0:Group>
        <ns0:Rule id="use_root_squashing_all_exports" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Use Root-Squashing on All Exports</ns0:title>
          <ns0:description xml:lang="en-US">If a filesystem is exported using root squashing, requests from root on the client
are considered to be unprivileged (mapped to a user such as nobody). This provides some mild
protection against remote abuse of an NFS server. Root squashing is enabled by default, and
should not be disabled.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Ensure that no line in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/exports</html:code> contains the option <html:code xmlns:html="http://www.w3.org/1999/xhtml">no_root_squash</html:code>.
</ns0:description>
          <ns0:rationale xml:lang="en-US">If the NFS server allows root access to local file systems from remote hosts, this
access could be used to compromise the system.
</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="restrict_nfs_clients_to_privileged_ports" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Restrict NFS Clients to Privileged Ports</ns0:title>
          <ns0:description xml:lang="en-US">By default, the server NFS implementation requires that all client requests be made
from ports less than 1024. If your organization has control over machines connected to its
network, and if NFS requests are prohibited at the border firewall, this offers some protection
against malicious requests from unprivileged users. Therefore, the default should not be changed.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To ensure that the default has not been changed, ensure no line in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/exports</html:code> contains the option <html:code xmlns:html="http://www.w3.org/1999/xhtml">insecure</html:code>.
</ns0:description>
          <ns0:rationale xml:lang="en-US">Allowing client requests to be made from ports higher than 1024 could allow a unprivileged
user to initiate an NFS connection. If the unprivileged user account has been compromised, an
attacker could gain access to data on the NFS server.</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="no_insecure_locks_exports" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Ensure Insecure File Locking is Not Allowed</ns0:title>
          <ns0:description xml:lang="en-US">By default the NFS server requires secure file-lock requests,
which require credentials from the client in order to lock a file. Most NFS
clients send credentials with file lock requests, however, there are a few
clients that do not send credentials when requesting a file-lock, allowing the
client to only be able to lock world-readable files. To get around this, the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">insecure_locks</html:code> option can be used so these clients can access the
desired export. This poses a security risk by potentially allowing the client
access to data for which it does not have authorization.
Remove any instances of the 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">insecure_locks</html:code> option from the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/exports</html:code>.
</ns0:description>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">764</ns0:reference>
          <ns0:rationale xml:lang="en-US">Allowing insecure file locking could allow for sensitive data to be
viewed or edited by an unauthorized user.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-no_insecure_locks_exports:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-no_insecure_locks_exports_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="use_kerberos_security_all_exports" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Use Kerberos Security on All Exports</ns0:title>
          <ns0:description xml:lang="en-US">
Using Kerberos on all exported mounts prevents a malicious client or user from
impersonating a system user. To cryptography authenticate users to the NFS server,
add <html:code xmlns:html="http://www.w3.org/1999/xhtml">sec=krb5:krb5i:krb5p</html:code> to each export in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/exports</html:code>.
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-14(1)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
When an NFS server is configured to use AUTH_SYS a selected userid and groupid are used to handle
requests from the remote user. The userid and groupid could mistakenly or maliciously be set
incorrectly. The AUTH_GSS method of authentication uses certificates on the server and client
systems to more securely authenticate the remote mount request.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-use_kerberos_security_all_exports:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-use_kerberos_security_all_exports_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="dns">
      <ns0:title xml:lang="en-US">DNS Server</ns0:title>
      <ns0:description xml:lang="en-US">Most organizations have an operational need to run at
least one nameserver. However, there are many common attacks
involving DNS server software, and this server software should
be disabled on any system
on which it is not needed.</ns0:description>
      <ns0:Group id="disabling_dns_server">
        <ns0:title xml:lang="en-US">Disable DNS Server</ns0:title>
        <ns0:description xml:lang="en-US">
DNS software should be disabled on any machine which does not
need to be a nameserver. Note that the BIND DNS server software is
not installed on Red Hat Enterprise Linux 7 by default. The remainder of this section
discusses secure configuration of machines which must be
nameservers.
</ns0:description>
        <ns0:Rule id="service_named_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable DNS Server</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">named</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable named.service</html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:rationale xml:lang="en-US">
All network services involve some risk of compromise due to
implementation flaws and should be disabled if possible.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_named_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable named
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_named_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service named
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - named

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_named_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_named_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_bind_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Uninstall bind Package</ns0:title>
          <ns0:description xml:lang="en-US">To remove the <html:code xmlns:html="http://www.w3.org/1999/xhtml">bind</html:code> package, which contains the
<html:code xmlns:html="http://www.w3.org/1999/xhtml">named</html:code> service, run the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase bind</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.9</ns0:reference>
          <ns0:rationale xml:lang="en-US">
If there is no need to make DNS server software available,
removing it provides a safeguard against its activation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_bind_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove bind
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_bind_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure bind is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - bind
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_bind_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_bind

class remove_bind {
  package { 'bind':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_bind_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=bind
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_bind_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_bind_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="dns_server_isolation">
        <ns0:title xml:lang="en-US">Isolate DNS from Other Services</ns0:title>
        <ns0:description xml:lang="en-US">This section discusses mechanisms for preventing the DNS server
from interfering with other services. This is done both to protect the
remainder of the network should a nameserver be compromised, and to make direct
attacks on nameservers more difficult.</ns0:description>
        <ns0:Group id="dns_server_dedicated">
          <ns0:title xml:lang="en-US">Run DNS Software on Dedicated Servers</ns0:title>
          <ns0:description xml:lang="en-US">Since DNS is
a high-risk service which must frequently be made available to the entire
Internet, it is strongly recommended that no other services be offered by
machines which act as organizational DNS servers.</ns0:description>
        </ns0:Group>
        <ns0:Group id="dns_server_chroot">
          <ns0:title xml:lang="en-US">Run DNS Software in a chroot Jail</ns0:title>
          <ns0:description xml:lang="en-US">Install the <html:code xmlns:html="http://www.w3.org/1999/xhtml">bind-chroot</html:code> package:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install bind-chroot</html:pre>
Place a valid named.conf file inside the chroot jail:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo cp /etc/named.conf /var/named/chroot/etc/named.conf
$ sudo chown root:root /var/named/chroot/etc/named.conf
$ sudo chmod 644 /var/named/chroot/etc/named.conf</html:pre>
Create and populate an appropriate zone directory within the jail, based on the
options directive. If your <html:code xmlns:html="http://www.w3.org/1999/xhtml">named.conf</html:code> includes:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">options {
directory "/path/to/DIRNAME ";
...
}</html:pre>
then copy that directory and its contents from the original zone directory:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo cp -r /path/to/DIRNAME /var/named/chroot/DIRNAME</html:pre>
Add or correct the following line within <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/sysconfig/named</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ROOTDIR=/var/named/chroot</html:pre>
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">If you are running BIND in a chroot jail, then you
should use the jailed <html:code xmlns:html="http://www.w3.org/1999/xhtml">named.conf</html:code> as the primary nameserver
configuration file. That is, when this guide recommends editing
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/named.conf</html:code>, you should instead edit
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/named/chroot/etc/named.conf</html:code>.
</ns0:warning>
          <ns0:rationale xml:lang="en-US">Chroot jails are not foolproof. However, they serve to make it more
difficult for a compromised program to be used to attack the entire host. They
do this by restricting a program's ability to traverse the directory upward, so
that files outside the jail are not visible to the chrooted process. Since RHEL
supports a standard mechanism for placing BIND in a chroot jail, you should
take advantage of this feature.</ns0:rationale>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="dns_server_protection">
        <ns0:title xml:lang="en-US">Protect DNS Data from Tampering or Attack</ns0:title>
        <ns0:description xml:lang="en-US">This section discusses DNS configuration options which make it
more difficult for attackers to gain access to private DNS data or to modify
DNS data.</ns0:description>
        <ns0:Group id="dns_server_separate_internal_external">
          <ns0:title xml:lang="en-US">Run Separate DNS Servers for External and Internal Queries</ns0:title>
          <ns0:description xml:lang="en-US">Is it possible to run external and internal nameservers on
separate machines? If so, follow the configuration guidance in this section. On
the external nameserver, edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/named.conf</html:code> to add or correct the
following directives:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">options {
  allow-query { any; };
  recursion no;
  ...
};
zone "example.com " IN {
  ...
};</html:pre>
On the internal nameserver, edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/named.conf</html:code>. Add or correct the
following directives, where SUBNET is the numerical IP representation of your
organization in the form xxx.xxx.xxx.xxx/xx:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">acl internal {
  SUBNET ;
  localhost;
};
options {
  allow-query { internal; };
  ...
};
zone "internal.example.com " IN {
  ...
};</html:pre>
</ns0:description>
          <ns0:rationale xml:lang="en-US">Enterprise nameservers generally serve two functions. One is to
provide public information about the machines in a domain for the benefit of
outside users who wish to contact those machines, for instance in order to send
mail to users in the enterprise, or to visit the enterprise's external web
page. The other is to provide nameservice to client machines within the
enterprise. Client machines require both private information about enterprise
machines (which may be different from the public information served to the rest
of the world) and public information about machines outside the enterprise,
which is used to send mail or visit websites outside of the organization.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
In order to provide the public nameservice function, it is necessary to share
data with untrusted machines which request it - otherwise, the enterprise
cannot be conveniently contacted by outside users. However, internal data
should be protected from disclosure, and serving irrelevant public name queries
for outside domains leaves the DNS server open to cache poisoning and other
attacks. Therefore, local network nameservice functions should not be provided
to untrusted machines.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Separate machines should be used to fill these two functions whenever possible.
</ns0:rationale>
        </ns0:Group>
        <ns0:Group id="dns_server_partition_with_views">
          <ns0:title xml:lang="en-US">Use Views to Partition External and Internal Information</ns0:title>
          <ns0:description xml:lang="en-US">If it is not possible to run external and internal nameservers on
separate physical machines, run BIND9 and simulate this feature using views.
Edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/named.conf</html:code>. Add or correct the following directives (where
SUBNET is the numerical IP representation of your organization in the form
xxx.xxx.xxx.xxx/xx):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">acl internal {
  SUBNET ;
  localhost;
};
view "internal-view" {
  match-clients { internal; };
  zone "." IN {
    type hint;
    file "db.cache";
  };
  zone "internal.example.com " IN {
    ...
  };
};

view "external-view" {
  match-clients { any; };
  recursion no;
  zone "example.com " IN {
    ...
  };
};</html:pre>
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">As shown in the example, database files which are
required for recursion, such as the root hints file, must be available to any
clients which are allowed to make recursive queries. Under typical
circumstances, this includes only the internal clients which are allowed to use
this server as a general-purpose nameserver.</ns0:warning>
          <ns0:rationale xml:lang="en-US">The view feature is provided by BIND9 as a way to allow a single
nameserver to make different sets of data available to different sets of
clients. If possible, it is always better to run external and internal
nameservers on separate machines, so that even complete compromise of the
external server cannot be used to obtain internal data or confuse internal DNS
clients. However, this is not always feasible, and use of a feature like views
is preferable to leaving internal DNS data entirely unprotected.</ns0:rationale>
        </ns0:Group>
        <ns0:Rule id="dns_server_disable_zone_transfers" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Zone Transfers from the Nameserver</ns0:title>
          <ns0:description xml:lang="en-US">Is it necessary for a secondary nameserver to receive zone data
via zone transfer from the primary server?  If not, follow the instructions in
this section. If so, see the next section for instructions on protecting zone
transfers.
Add or correct the following directive within <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/named.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">options {
  allow-transfer { none; };
  ...
}</html:pre>
</ns0:description>
          <ns0:rationale xml:lang="en-US">If both the primary and secondary nameserver are under your control,
or if you have only one nameserver, it may be possible to use an external
configuration management mechanism to distribute zone updates. In that case, it
is not necessary to allow zone transfers within BIND itself, so they should be
disabled to avoid the potential for abuse.</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="dns_server_authenticate_zone_transfers" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Authenticate Zone Transfers</ns0:title>
          <ns0:description xml:lang="en-US">If it is necessary for a secondary nameserver to receive zone data
via zone transfer from the primary server, follow the instructions here.  Use
dnssec-keygen to create a symmetric key file in the current directory:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ cd /tmp
$ sudo dnssec-keygen -a HMAC-MD5 -b 128 -n HOST dns.example.com
Kdns.example.com .+aaa +iiiii</html:pre>
This output is the name of a file containing the new key. Read the file to find
the base64-encoded key string:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo cat Kdns.example.com .+NNN +MMMMM .key
dns.example.com IN KEY 512 3 157 base64-key-string</html:pre>
Add the directives to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/named.conf</html:code> on the primary server:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">key zone-transfer-key {
  algorithm hmac-md5;
  secret "base64-key-string ";
};
zone "example.com " IN {
  type master;
  allow-transfer { key zone-transfer-key; };
  ...
};</html:pre>
Add the directives below to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/named.conf</html:code> on the secondary nameserver:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">key zone-transfer-key {
  algorithm hmac-md5;
  secret "base64-key-string ";
};

server IP-OF-MASTER {
  keys { zone-transfer-key; };
};

zone "example.com " IN {
  type slave;
  masters { IP-OF-MASTER ; };
  ...
};</html:pre>
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">The purpose of the dnssec-keygen command is to
create the shared secret string base64-key-string. Once this secret has been
obtained and inserted into named.conf on the primary and secondary servers, the
key files Kdns.example.com .+NNN +MMMMM .key and Kdns.example.com .+NNN +MMMMM
.private are no longer needed, and may safely be deleted.</ns0:warning>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">The BIND transaction signature (TSIG) functionality allows primary
and secondary nameservers to use a shared secret to verify authorization to
perform zone transfers. This method is more secure than using IP-based limiting
to restrict nameserver access, since IP addresses can be easily spoofed.
However, if you cannot configure TSIG between your servers because, for
instance, the secondary nameserver is not under your control and its
administrators are unwilling to configure TSIG, you can configure an
allow-transfer directive with numerical IP addresses or ACLs as a last resort.
</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="dns_server_disable_dynamic_updates" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Dynamic Updates</ns0:title>
          <ns0:description xml:lang="en-US">Is there a mission-critical reason to enable the risky dynamic
update functionality? If not, edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/named.conf</html:code>. For each zone
specification, correct the following directive if necessary:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">zone "example.com " IN {
  allow-update { none; };
  ...
};</html:pre>
</ns0:description>
          <ns0:rationale xml:lang="en-US">Dynamic updates allow remote servers to add, delete, or modify any
entries in your zone file. Therefore, they should be considered highly risky,
and disabled unless there is a very good reason for their use. If dynamic
updates must be allowed, IP-based ACLs are insufficient protection, since they
are easily spoofed. Instead, use TSIG keys (see the previous section for an
example), and consider using the update-policy directive to restrict changes to
only the precise type of change needed.</ns0:rationale>
          </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="ftp">
      <ns0:title xml:lang="en-US">FTP Server</ns0:title>
      <ns0:description xml:lang="en-US">FTP is a common method for allowing remote access to
files. Like telnet, the FTP protocol is unencrypted, which means
that passwords and other data transmitted during the session can be
captured and that the session is vulnerable to hijacking.
Therefore, running the FTP server software is not recommended.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
However, there are some FTP server configurations which may
be appropriate for some environments, particularly those which
allow only read-only anonymous access as a means of downloading
data available to the public.</ns0:description>
      <ns0:Group id="disabling_vsftpd">
        <ns0:title xml:lang="en-US">Disable vsftpd if Possible</ns0:title>
        <ns0:description xml:lang="en-US">To minimize attack surface, disable vsftpd if at all
possible.</ns0:description>
        <ns0:Rule id="service_vsftpd_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable vsftpd Service</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">vsftpd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable vsftpd.service</html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1436</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Running FTP server software provides a network-based avenue
of attack, and should be disabled if not needed.
Furthermore, the FTP protocol is unencrypted and creates
a risk of compromising sensitive information.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_vsftpd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable vsftpd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_vsftpd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service vsftpd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - vsftpd

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_vsftpd_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_vsftpd_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_vsftpd_removed" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Uninstall vsftpd Package</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">vsftpd</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase vsftpd</html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-6(b)</ns0:reference>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.10</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Removing the vsftpd package decreases the risk of its
accidental activation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_vsftpd_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove vsftpd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_vsftpd_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure vsftpd is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - vsftpd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_vsftpd_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_vsftpd

class remove_vsftpd {
  package { 'vsftpd':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_vsftpd_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=vsftpd
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_vsftpd_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_vsftpd_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="ftp_use_vsftpd">
        <ns0:title xml:lang="en-US">Use vsftpd to Provide FTP Service if Necessary</ns0:title>
        <ns0:description xml:lang="en-US">If your use-case requires FTP service, install and
set-up vsftpd to provide it.</ns0:description>
        <ns0:Rule id="package_vsftpd_installed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Install vsftpd Package</ns0:title>
          <ns0:description xml:lang="en-US">If this machine must operate as an FTP server, install the <html:code xmlns:html="http://www.w3.org/1999/xhtml">vsftpd</html:code> package via the standard channels.
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install vsftpd</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">After Red Hat Enterprise Linux 2.1, Red Hat switched from distributing wu-ftpd with Red Hat Enterprise Linux to distributing vsftpd. For security
and for consistency with future Red Hat releases, the use of vsftpd is recommended.</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_vsftpd_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command install vsftpd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_vsftpd_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Ensure vsftpd is installed
  package:
    name="{{item}}"
    state=present
  with_items:
    - vsftpd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_vsftpd_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:puppet">include install_vsftpd

class install_vsftpd {
  package { 'vsftpd':
    ensure =&gt; 'installed',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_vsftpd_installed" reboot="false" strategy="enable" system="urn:redhat:anaconda:pre">
package --add=vsftpd
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_vsftpd_installed:def:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="ftp_configure_vsftpd">
        <ns0:title xml:lang="en-US">Use vsftpd to Provide FTP Service if Necessary</ns0:title>
        <ns0:description xml:lang="en-US">The primary vsftpd configuration file is
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/vsftpd.conf</html:code>, if that file exists, or
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/vsftpd/vsftpd.conf</html:code> if it does not. 
</ns0:description>
        <ns0:Rule id="ftp_log_transactions" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Enable Logging of All FTP Transactions</ns0:title>
          <ns0:description xml:lang="en-US">Add or correct the following configuration options within the <html:code xmlns:html="http://www.w3.org/1999/xhtml">vsftpd</html:code>
configuration file, located at <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/vsftpd/vsftpd.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">xferlog_enable=YES
xferlog_std_format=NO
log_ftp_protocol=YES</html:pre>
</ns0:description>
          <ns0:warning category="general" xml:lang="en-US">If verbose logging to <html:code xmlns:html="http://www.w3.org/1999/xhtml">vsftpd.log</html:code> is done, sparse logging of downloads to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log/xferlog</html:code> will not also occur. However, the information about what files were downloaded is included in the information logged to <html:code xmlns:html="http://www.w3.org/1999/xhtml">vsftpd.log</html:code></ns0:warning>
          <ns0:rationale xml:lang="en-US">To trace malicious activity facilitated by the FTP service, it must be configured to ensure that all commands sent to
the FTP server are logged using the verbose vsftpd log
format. The default vsftpd log file is <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/log/vsftpd.log</html:code>.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-ftp_log_transactions:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-ftp_log_transactions_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="ftp_present_banner" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Create Warning Banners for All FTP Users</ns0:title>
          <ns0:description xml:lang="en-US">Edit the vsftpd configuration file, which resides at <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/vsftpd/vsftpd.conf</html:code>
by default. Add or correct the following configuration options:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">banner_file=/etc/issue</html:pre>
</ns0:description>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">48</ns0:reference>
          <ns0:rationale xml:lang="en-US">This setting will cause the system greeting banner to be used for FTP connections as well.</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-ftp_present_banner:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-ftp_present_banner_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="ftp_restrict_users">
          <ns0:title xml:lang="en-US">Restrict the Set of Users Allowed to Access FTP</ns0:title>
          <ns0:description xml:lang="en-US">This section describes how to disable non-anonymous (password-based) FTP logins, or, if it is not possible to
do this entirely due to legacy applications, how to restrict insecure FTP login to only those users who have an
identified need for this access.</ns0:description>
          <ns0:Rule id="ftp_restrict_to_anon" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Restrict Access to Anonymous Users if Possible</ns0:title>
            <ns0:description xml:lang="en-US">Is there a mission-critical reason for users to transfer files to/from their own accounts using FTP, rather than
using a secure protocol like SCP/SFTP? If not, edit the vsftpd configuration file. Add or correct the following configuration option:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">local_enable=NO</html:pre>
If non-anonymous FTP logins are necessary, follow the guidance in the remainder of this section to secure
these logins as much as possible.</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">AC-3</ns0:reference>
            <ns0:rationale xml:lang="en-US">The use of non-anonymous FTP logins is strongly discouraged. Since SSH clients and servers are widely available, and since SSH provides support for a transfer mode which resembles FTP in user interface, there is no good reason to allow password-based FTP access. </ns0:rationale>
            </ns0:Rule>
          <ns0:Group id="ftp_limit_users">
            <ns0:title xml:lang="en-US">Limit Users Allowed FTP Access if Necessary</ns0:title>
            <ns0:description xml:lang="en-US">If there is a mission-critical reason for users to access their accounts via the insecure FTP protocol, limit the set of users who are allowed this access. Edit the vsftpd configuration file. Add or correct the following configuration options:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">userlist_enable=YES
userlist_file=/etc/vsftp.ftpusers
userlist_deny=NO</html:pre>
Edit the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/vsftp.ftpusers</html:code>. For each user USERNAME who should be allowed to access the system via FTP, add a line containing that user's name:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">USERNAME</html:pre>
If anonymous access is also required, add the anonymous usernames to <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/vsftp.ftpusers</html:code> as well.
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">anonymous
ftp</html:pre>
</ns0:description>
            <ns0:rationale xml:lang="en-US">Historically, the file <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/ftpusers</html:code> contained a list of users who were not allowed to access the system via FTP. It was used to prevent system users such as the root user from logging in via the insecure FTP protocol. However, when the configuration option <html:code xmlns:html="http://www.w3.org/1999/xhtml">userlist deny=NO</html:code> is set, vsftpd interprets ftpusers as the set of users who are allowed to login via FTP. Since it should be possible for most users to access their accounts via secure protocols, it is recommended that this setting be used, so that non-anonymous FTP access can be limited to legacy users who have been explicitly identified.</ns0:rationale>
          </ns0:Group>
        </ns0:Group>
        <ns0:Rule id="ftp_disable_uploads" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable FTP Uploads if Possible</ns0:title>
          <ns0:description xml:lang="en-US">Is there a mission-critical reason for users to upload files via FTP? If not,
edit the vsftpd configuration file to add or correct the following configuration options:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">write_enable=NO</html:pre>
If FTP uploads are necessary, follow the guidance in the remainder of this section to secure these transactions
as much as possible.</ns0:description>
          <ns0:rationale xml:lang="en-US">Anonymous FTP can be a convenient way to make files available for universal download. However, it is less
common to have a need to allow unauthenticated users to place files on the FTP server. If this must be done, it
is necessary to ensure that files cannot be uploaded and downloaded from the same directory.
</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="ftp_home_partition" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Place the FTP Home Directory on its Own Partition</ns0:title>
          <ns0:description xml:lang="en-US">By default, the anonymous FTP root is the home directory of the FTP user account. The df command can
be used to verify that this directory is on its own partition.</ns0:description>
          <ns0:rationale xml:lang="en-US">If there is a mission-critical reason for anonymous users to upload files, precautions must be taken to prevent
these users from filling a disk used by other services.</ns0:rationale>
          </ns0:Rule>
        <ns0:Group id="ftp_configure_firewall">
          <ns0:title xml:lang="en-US">Configure Firewalls to Protect the FTP Server</ns0:title>
          <ns0:description xml:lang="en-US">By default, <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code>
blocks access to the ports used by the web server.

        To configure <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> to allow access, run the following command(s):
        <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewall-cmd --permanent --add-service=ftp</html:code>
</ns0:description>
          <ns0:rationale xml:lang="en-US">These settings configure firewalld to allow connections to an FTP server. The first line allows initial connections
to the FTP server port.
FTP is an older protocol which is not very compatible with firewalls. During the initial FTP dialogue, the client
and server negotiate an arbitrary port to be used for data transfer. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ip_conntrack_ftp</html:code>  module is used by
firewalld to listen to that dialogue and allow connections to the data ports which FTP negotiates. This allows an
FTP server to operate on a machine which is running a firewall.</ns0:rationale>
        </ns0:Group>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="http">
      <ns0:title xml:lang="en-US">Web Server</ns0:title>
      <ns0:description xml:lang="en-US">The web server is responsible for providing access to
content via the HTTP protocol. Web servers represent a significant
security risk because:
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>The HTTP port is commonly probed by malicious sources</html:li><html:li>Web server software is very complex, and includes a long
history of vulnerabilities</html:li><html:li>The HTTP protocol is unencrypted and vulnerable to passive
monitoring</html:li></html:ul>
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The system's default web server software is Apache 2 and is
provided in the RPM package <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code>.</ns0:description>
      <ns0:Group id="disabling_httpd">
        <ns0:title xml:lang="en-US">Disable Apache if Possible</ns0:title>
        <ns0:description xml:lang="en-US">If Apache was installed and activated, but the system
does not need to act as a web server, then it should be disabled
and removed from the system.
</ns0:description>
        <ns0:Rule id="service_httpd_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable httpd Service</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable httpd.service</html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Running web server software provides a network-based avenue
of attack, and should be disabled if not needed.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_httpd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable httpd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_httpd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service httpd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - httpd

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_httpd_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_httpd_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_httpd_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Uninstall httpd Package</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase httpd</html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.11</ns0:reference>
          <ns0:rationale xml:lang="en-US">
If there is no need to make the web server software available,
removing it provides a safeguard against its activation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_httpd_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove httpd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_httpd_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure httpd is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - httpd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_httpd_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_httpd

class remove_httpd {
  package { 'httpd':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_httpd_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=httpd
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_httpd_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_httpd_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="installing_httpd">
        <ns0:title xml:lang="en-US">Install Apache if Necessary</ns0:title>
        <ns0:description xml:lang="en-US">If <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> was not installed and activated, but the system
needs to act as a web server, then it should be installed on the system. Follow these
guidelines to install it defensively. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> package can be installed with
the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install httpd</html:pre>
This method of installation is recommended over installing the "Web Server"
package group during the system installation process. The Web Server package
group includes many packages which are likely extraneous, while the
command-line method installs only the required <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> package itself.
</ns0:description>
        <ns0:Group id="httpd_minimal_modules_installed">
          <ns0:title xml:lang="en-US">Confirm Minimal Built-in Modules Installed</ns0:title>
          <ns0:description xml:lang="en-US">The default <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> installation minimizes the number of
modules that are compiled directly into the binary (<html:code xmlns:html="http://www.w3.org/1999/xhtml">core prefork http_core
mod_so</html:code>). This minimizes risk by limiting the capabilities allowed by the
web server.

Query the set of compiled-in modules using the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ httpd -l</html:pre>
If the number of compiled-in modules is significantly larger than the
aforementioned set, this guide recommends re-installing <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> with a
reduced configuration. Minimizing the number of modules that are compiled into
the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> binary, reduces risk by limiting the capabilities allowed by
the webserver.
</ns0:description>
        </ns0:Group>
      </ns0:Group>
      <ns0:Group id="securing_httpd">
        <ns0:title xml:lang="en-US">Secure Apache Configuration</ns0:title>
        <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> configuration file is
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/httpd/conf/httpd.conf</html:code>. Apply the recommendations in the remainder
of this section to this file.</ns0:description>
        <ns0:Group id="httpd_restrict_info_leakage">
          <ns0:title xml:lang="en-US">Restrict Web Server Information Leakage</ns0:title>
          <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ServerTokens</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">ServerSignature</html:code> directives determine how
much information the web server discloses about the configuration of the
system.</ns0:description>
          <ns0:Rule id="httpd_servertokens_prod" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Set httpd ServerTokens Directive to Prod</ns0:title>
            <ns0:description xml:lang="en-US"><html:code xmlns:html="http://www.w3.org/1999/xhtml">ServerTokens Prod</html:code> restricts information in page headers, returning only the word "Apache."
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Add or correct the following directive in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/httpd/conf/httpd.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ServerTokens Prod</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Information disclosed to clients about the configuration of the web server and system could be used
to plan an attack on the given system. This information disclosure should be restricted to a minimum.
</ns0:rationale>
            </ns0:Rule>
          <ns0:Rule id="httpd_serversignature_off" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Set httpd ServerSignature Directive to Off</ns0:title>
            <ns0:description xml:lang="en-US"><html:code xmlns:html="http://www.w3.org/1999/xhtml">ServerSignature Off</html:code> restricts <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> from displaying server version number
on error pages.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Add or correct the following directive in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/httpd/conf/httpd.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ServerSignature Off</html:pre>
</ns0:description>
            <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
            <ns0:rationale xml:lang="en-US">
Information disclosed to clients about the configuration of the web server and system could be used
to plan an attack on the given system. This information disclosure should be restricted to a minimum.
</ns0:rationale>
            </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="httpd_minimize_loadable_modules">
          <ns0:title xml:lang="en-US">Minimize Web Server Loadable Modules</ns0:title>
          <ns0:description xml:lang="en-US">
A default installation of <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> includes a plethora of dynamically shared objects (DSO)
that are loaded at run-time. Unlike the aforementioned compiled-in modules, a DSO can be
disabled in the configuration file by removing the corresponding LoadModule directive.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Note: A DSO only provides additional functionality if associated directives are included
in the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> configuration file. It should also be noted that removing a DSO will produce
errors on <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> startup if the configuration file contains directives that apply to that
module. Refer to <html:code xmlns:html="http://www.w3.org/1999/xhtml"><html:a href="http://httpd.apache.org/docs/">http://httpd.apache.org/docs/</html:a></html:code> for details on which directives
are associated with each DSO.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Following each DSO removal, the configuration can be tested with the following command
to check if everything still works:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo service httpd configtest</html:pre>
The purpose of each of the modules loaded by default will now be addressed one at a time.
If none of a module's directives are being used, remove it.
</ns0:description>
          <ns0:Group id="httpd_core_modules">
            <ns0:title xml:lang="en-US">httpd Core Modules</ns0:title>
            <ns0:description xml:lang="en-US">
These modules comprise a basic subset of modules that are likely needed for base <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code>
functionality; ensure they are not commented out in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/httpd/conf/httpd.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule logio_module modules/mod_logio.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule mime_module modules/mod_mome.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule alias_module modules/mod_alias.so</html:pre>
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:description>
            <ns0:Group id="httpd_basic_authentication">
              <ns0:title xml:lang="en-US">Minimize Modules for HTTP Basic Authentication</ns0:title>
              <ns0:description xml:lang="en-US">
The following modules are necessary if this web server will provide content that will
be restricted by a password.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Authentication can be performed using local plain text password files (<html:code xmlns:html="http://www.w3.org/1999/xhtml">authn_file</html:code>),
local DBM password files (<html:code xmlns:html="http://www.w3.org/1999/xhtml">authn_dbm</html:code>) or an LDAP directory. The only module required by
the web server depends on your choice of authentication. Comment out the modules you don't
need from the following:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so</html:pre>
<html:code xmlns:html="http://www.w3.org/1999/xhtml">authn_alias</html:code> allows for authentication based on aliases. <html:code xmlns:html="http://www.w3.org/1999/xhtml">authn_anon</html:code>
allows anonymous authentication similar to that of anonymous ftp sites. <html:code xmlns:html="http://www.w3.org/1999/xhtml">authz_owner</html:code>
allows authorization based on file ownership. <html:code xmlns:html="http://www.w3.org/1999/xhtml">authz_dbm</html:code> allows for authorization
based on group membership if the web server is using DBM authentication.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If the above functionality is unnecessary, comment out the related module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule authn_alias_module modules/mod_authn_alias.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so</html:pre>
</ns0:description>
            </ns0:Group>
            <ns0:Rule id="httpd_digest_authentication" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable HTTP Digest Authentication</ns0:title>
              <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">auth_digest</html:code> module provides encrypted authentication sessions.
If this functionality is unnecessary, comment out the related module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule auth_digest_module modules/mod_auth_digest.so</html:pre>
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Rule id="httpd_mod_rewrite" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable HTTP mod_rewrite</ns0:title>
              <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_rewrite</html:code> module is very powerful and can protect against
certain classes of web attacks. However, it is also very complex and has a
significant history of vulnerabilities itself. If its functionality is
unnecessary, comment out the related module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule rewrite_module modules/mod_rewrite.so</html:pre>
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Rule id="httpd_ldap_support" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable LDAP Support</ns0:title>
              <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">ldap</html:code> module provides HTTP authentication via an LDAP directory.
If its functionality is unnecessary, comment out the related modules:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule ldap_module modules/mod_ldap.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so</html:pre>
If LDAP is to be used, SSL encryption should be used as well.
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Rule id="httpd_server_side_includes" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable Server Side Includes</ns0:title>
              <ns0:description xml:lang="en-US">
Server Side Includes provide a method of dynamically generating web pages through the
insertion of server-side code. However, the technology is also deprecated and
introduces significant security concerns.
If this functionality is unnecessary, comment out the related module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule include_module modules/mod_include.so</html:pre>
If there is a critical need for Server Side Includes, they should be enabled with the
option <html:code xmlns:html="http://www.w3.org/1999/xhtml">IncludesNoExec</html:code> to prevent arbitrary code execution. Additionally, user
supplied data should be encoded to prevent cross-site scripting vulnerabilities.
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Rule id="httpd_mime_magic" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable MIME Magic</ns0:title>
              <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">mime_magic</html:code> module provides a second layer of MIME support that in most configurations
is likely extraneous. If its functionality is unnecessary, comment out the related module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule mime_magic_module modules/mod_mime_magic.so</html:pre>
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Rule id="httpd_webdav" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable WebDAV (Distributed Authoring and Versioning)</ns0:title>
              <ns0:description xml:lang="en-US">
WebDAV is an extension of the HTTP protocol that provides distributed and
collaborative access to web content. If its functionality is unnecessary,
comment out the related modules:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so</html:pre>
If there is a critical need for WebDAV, extra care should be taken in its configuration.
Since DAV access allows remote clients to manipulate server files, any location on the
server that is DAV enabled should be protected by access controls.
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server, reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Rule id="httpd_server_activity_status" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable Server Activity Status</ns0:title>
              <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">status</html:code> module provides real-time access to statistics on the internal operation of
the web server. This may constitute an unnecessary information leak and should be disabled
unless necessary. To do so, comment out the related module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule status_module modules/mod_status.so</html:pre>
If there is a critical need for this module, ensure that access to the status
page is properly restricted to a limited set of hosts in the status handler
configuration.
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Rule id="httpd_server_configuration_display" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable Web Server Configuration Display</ns0:title>
              <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">info</html:code> module creates a web page illustrating the configuration of the web server. This
can create an unnecessary security leak and should be disabled.
If its functionality is unnecessary, comment out the module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule info_module modules/mod_info.so</html:pre>
If there is a critical need for this module, use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">Location</html:code> directive to provide
an access control list to restrict access to the information.
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Rule id="httpd_url_correction" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable URL Correction on Misspelled Entries</ns0:title>
              <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">speling</html:code> module attempts to find a document match by allowing one misspelling in an
otherwise failed request. If this functionality is unnecessary, comment out the module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule speling_module modules/mod_speling.so</html:pre>
This functionality weakens server security by making site enumeration easier.
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Rule id="httpd_proxy_support" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable Proxy Support</ns0:title>
              <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">proxy</html:code> module provides proxying support, allowing <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> to forward requests and
serve as a gateway for other servers. If its functionality is unnecessary, comment out the module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule proxy_module modules/mod_proxy.so</html:pre>

If proxy support is needed, load <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_proxy</html:code> and the appropriate proxy protocol handler
module (one of <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_proxy_http</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_proxy_ftp</html:code>, or <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_proxy_connect</html:code>). Additionally,
make certain that a server is secure before enabling proxying, as open proxy servers
are a security risk. <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_proxy_balancer</html:code> enables load balancing, but requires that
<html:code xmlns:html="http://www.w3.org/1999/xhtml">mod status</html:code> be enabled.
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Rule id="httpd_cache_support" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable Cache Support</ns0:title>
              <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cache</html:code> module allows <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> to cache data, optimizing access to
frequently accessed content. However, it introduces potential security flaws
such as the possibility of circumventing <html:code xmlns:html="http://www.w3.org/1999/xhtml">Allow</html:code> and
<html:code xmlns:html="http://www.w3.org/1999/xhtml">Deny</html:code> directives.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" /> If this functionality is
unnecessary, comment out the module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule cache_module modules/mod_cache.so</html:pre>
If caching is required, it should not be enabled for any limited-access content.
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Rule id="httpd_cgi_support" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Disable CGI Support</ns0:title>
              <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">cgi</html:code> module allows HTML to interact with the CGI web programming language.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If this functionality is unnecessary, comment out the module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#LoadModule cgi_module modules/mod_cgi.so</html:pre>

If the web server requires the use of CGI, enable <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_cgi</html:code>.

</ns0:description>
              <ns0:rationale xml:lang="en-US">
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
              </ns0:Rule>
            <ns0:Group id="httpd_optional_components">
              <ns0:title xml:lang="en-US">Minimize Various Optional Components</ns0:title>
              <ns0:description xml:lang="en-US">
The following modules perform very specific tasks, sometimes providing access to
just a few additional directives. If such functionality is not required (or if you
are not using these directives), comment out the associated module:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>External filtering (response passed through external program prior to client delivery)
<html:pre>#LoadModule ext_filter_module modules/mod_ext_filter.so</html:pre></html:li><html:li>User-specified Cache Control and Expiration
<html:pre>#LoadModule expires_module modules/mod_expires.so</html:pre></html:li><html:li>Compression Output Filter (provides content compression prior to client delivery)
<html:pre>#LoadModule deflate_module modules/mod_deflate.so</html:pre></html:li><html:li>HTTP Response/Request Header Customization
<html:pre>#LoadModule headers_module modules/mod_headers.so</html:pre></html:li><html:li>User activity monitoring via cookies
<html:pre>#LoadModule usertrack_module modules/mod_usertrack.so</html:pre></html:li><html:li>Dynamically configured mass virtual hosting
<html:pre>#LoadModule vhost_alias_module modules/mod_vhost_alias.so</html:pre></html:li></html:ul>
Minimizing the number of loadable modules available to the web server reduces risk
by limiting the capabilities allowed by the web server.
</ns0:description>
            </ns0:Group>
            <ns0:Group id="httpd_minimize_config_files_included">
              <ns0:title xml:lang="en-US">Minimize Configuration Files Included</ns0:title>
              <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">Include</html:code> directive directs <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> to load supplementary configuration files
from a provided path. The default configuration loads all files that end in <html:code xmlns:html="http://www.w3.org/1999/xhtml">.conf</html:code>
from the <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/httpd/conf.d</html:code> directory.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
To restrict excess configuration, the following line should be commented out and
replaced with <html:code xmlns:html="http://www.w3.org/1999/xhtml">Include</html:code> directives that only reference required configuration files:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">#Include conf.d/*.conf</html:pre>
If the above change was made, ensure that the SSL encryption remains loaded by
explicitly including the corresponding configuration file:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">Include conf.d/ssl.conf</html:pre>
If PHP is necessary, a similar alteration must be made:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">Include conf.d/php.conf</html:pre>

Explicitly listing the configuration files to be loaded during web server start-up avoids
the possibility of unwanted or malicious configuration files to be automatically included as
part of the server's running configuration.

</ns0:description>
            </ns0:Group>
          </ns0:Group>
        </ns0:Group>
        <ns0:Group id="httpd_directory_restrictions">
          <ns0:title xml:lang="en-US">Directory Restrictions</ns0:title>
          <ns0:description xml:lang="en-US">
The Directory tags in the web server configuration file allow finer grained access
control for a specified directory. All web directories should be configured on a
case-by-case basis, allowing access only where needed.
</ns0:description>
          <ns0:Rule id="httpd_restrict_root_directory" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Restrict Root Directory</ns0:title>
            <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> root directory should always have the most restrictive configuration enabled.
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">&lt;Directory / &gt;
   Options None
   AllowOverride None
   Order allow,deny
&lt;/Directory&gt;</html:pre>
</ns0:description>
            <ns0:rationale xml:lang="en-US">
The Web Server's root directory content should be protected from unauthorized access
by web clients.
</ns0:rationale>
            </ns0:Rule>
          <ns0:Rule id="httpd_restrict_web_directory" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Restrict Web Directory</ns0:title>
            <ns0:description xml:lang="en-US">
The default configuration for the web (<html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/www/html</html:code>) Directory allows directory
indexing (<html:code xmlns:html="http://www.w3.org/1999/xhtml">Indexes</html:code>) and the following of symbolic links (<html:code xmlns:html="http://www.w3.org/1999/xhtml">FollowSymLinks</html:code>).
Neither of these is recommended.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">/var/www/html</html:code> directory hierarchy should not be viewable via the web, and
symlinks should only be followed if the owner of the symlink also owns the linked file.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Ensure that this policy is adhered to by altering the related section of the configuration:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">&lt;Directory "/var/www/html"&gt;
#  ...
   Options SymLinksIfOwnerMatch
#  ...
&lt;/Directory&gt;</html:pre>
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Access to the web server's directory hierarchy could allow access to unauthorized files
by web clients. Following symbolic links could also allow such access.
</ns0:rationale>
            </ns0:Rule>
          <ns0:Rule id="httpd_restrict_critical_directories" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Restrict Other Critical Directories</ns0:title>
            <ns0:description xml:lang="en-US">
All accessible web directories should be configured with similarly restrictive settings.
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">Options</html:code> directive should be limited to necessary functionality and the <html:code xmlns:html="http://www.w3.org/1999/xhtml">AllowOverride</html:code>
directive should be used only if needed. The <html:code xmlns:html="http://www.w3.org/1999/xhtml">Order</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">Deny</html:code> access control tags
should be used to deny access by default, allowing access only where necessary.
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Directories accessible from a web client should be configured with the least amount of
access possible in order to avoid unauthorized access to restricted content or server information.
</ns0:rationale>
            </ns0:Rule>
          <ns0:Rule id="httpd_limit_available_methods" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Limit Available Methods</ns0:title>
            <ns0:description xml:lang="en-US">
Web server methods are defined in section 9 of RFC 2616 (<html:a href="http://www.ietf.org/rfc/rfc2616.txt" xmlns:html="http://www.w3.org/1999/xhtml">http://www.ietf.org/rfc/rfc2616.txt</html:a>).
If a web server does not require the implementation of all available methods,
they should be disabled.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Note: <html:code xmlns:html="http://www.w3.org/1999/xhtml">GET</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">POST</html:code> are the most common methods. A majority of the others
are limited to the WebDAV protocol.
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">&lt;Directory /var/www/html&gt;
# ...
   # Only allow specific methods (this command is case-sensitive!)
   &lt;LimitExcept GET POST&gt;
      Order allow,deny
   &lt;/LimitExcept&gt;
# ...
&lt;/Directory&gt;</html:pre>
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Minimizing the number of available methods to the web client reduces risk
by limiting the capabilities allowed by the web server.
</ns0:rationale>
            </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="httpd_modules_improve_security">
          <ns0:title xml:lang="en-US">Use Appropriate Modules to Improve httpd's Security</ns0:title>
          <ns0:description xml:lang="en-US">
Among the modules available for <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> are several whose use may improve the
security of the web server installation. This section recommends and discusses
the deployment of security-relevant modules.
</ns0:description>
          <ns0:Group id="httpd_deploy_mod_ssl">
            <ns0:title xml:lang="en-US">Deploy mod_ssl</ns0:title>
            <ns0:description xml:lang="en-US">
Because HTTP is a plain text protocol, all traffic is susceptible to passive
monitoring. If there is a need for confidentiality, SSL should be configured
and enabled to encrypt content.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Note: <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_nss</html:code> is a FIPS 140-2 certified alternative to <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_ssl</html:code>.
The modules share a considerable amount of code and should be nearly identical
in functionality. If FIPS 140-2 validation is required, then <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_nss</html:code> should
be used. If it provides some feature or its greater compatibility is required,
then <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_ssl</html:code> should be used.
</ns0:description>
            <ns0:Rule id="httpd_install_mod_ssl" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Install mod_ssl</ns0:title>
              <ns0:description xml:lang="en-US">
Install the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_ssl</html:code> module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install mod_ssl</html:pre>
</ns0:description>
              <ns0:rationale xml:lang="en-US"><html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_ssl</html:code> provides encryption capabilities for the <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> Web server. Unencrypted
content is transmitted in plain text which could be passively monitored and accessed by
unauthorized parties.
</ns0:rationale>
              </ns0:Rule>
          </ns0:Group>
          <ns0:Group id="httpd_deploy_mod_security">
            <ns0:title xml:lang="en-US">Deploy mod_security</ns0:title>
            <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">security</html:code> module provides an application level firewall for <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code>.
Following its installation with the base ruleset, specific configuration advice can be found at
<html:a href="http://www.modsecurity.org/" xmlns:html="http://www.w3.org/1999/xhtml">http://www.modsecurity.org/</html:a> to design a policy that best matches the security needs of
the web applications. Usage of <html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_security</html:code> is highly recommended for some environments,
but it should be noted this module does not ship with Red Hat Enterprise Linux itself,
and instead is provided via Extra Packages for Enterprise Linux (EPEL).
For more information on EPEL please refer to http://fedoraproject.org/wiki/EPEL.
</ns0:description>
            <ns0:Rule id="httpd_install_mod_security" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Install mod_security</ns0:title>
              <ns0:description xml:lang="en-US">
Install the <html:code xmlns:html="http://www.w3.org/1999/xhtml">security</html:code> module:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install mod_security</html:pre>

</ns0:description>
              <ns0:rationale xml:lang="en-US"><html:code xmlns:html="http://www.w3.org/1999/xhtml">mod_security</html:code> provides an additional level of protection for the web server by
enabling the administrator to implement content access policies and filters at the
application layer.
</ns0:rationale>
              </ns0:Rule>
          </ns0:Group>
        </ns0:Group>
        <ns0:Group id="httpd_use_dos_protection_modules">
          <ns0:title xml:lang="en-US">Use Denial-of-Service Protection Modules</ns0:title>
          <ns0:description xml:lang="en-US">
Denial-of-service attacks are difficult to detect and prevent while maintaining
acceptable access to authorized users. However, some traffic-shaping
modules can be used to address the problem. Well-known DoS protection modules include:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">mod_cband mod_bwshare mod_limitipconn mod_evasive</html:pre>
Denial-of-service prevention should be implemented for a web server if such a threat exists.
However, specific configuration details are very dependent on the environment and often best left
at the discretion of the administrator.
</ns0:description>
        </ns0:Group>
        <ns0:Group id="httpd_configure_php_securely">
          <ns0:title xml:lang="en-US">Configure PHP Securely</ns0:title>
          <ns0:description xml:lang="en-US">
PHP is a widely-used and often misconfigured server-side scripting language. It should
be used with caution, but configured appropriately when needed.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Review <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/php.ini</html:code> and make the following changes if possible:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml"># Do not expose PHP error messages to external users
display_errors = Off

# Enable safe mode
safe_mode = On

# Only allow access to executables in isolated directory
safe_mode_exec_dir = php-required-executables-path

# Limit external access to PHP environment
safe_mode_allowed_env_vars = PHP_

# Restrict PHP information leakage
expose_php = Off

# Log all errors
log_errors = On

# Do not register globals for input data
register_globals = Off

# Minimize allowable PHP post size
post_max_size = 1K

# Ensure PHP redirects appropriately
cgi.force_redirect = 0

# Disallow uploading unless necessary
file_uploads = Off

# Disallow treatment of file requests as fopen calls
allow_url_fopen = Off

# Enable SQL safe mode
sql.safe_mode = On
</html:pre>
</ns0:description>
        </ns0:Group>
        <ns0:Group id="httpd_configure_os_protect_web_server">
          <ns0:title xml:lang="en-US">Configure Operating System to Protect Web Server</ns0:title>
          <ns0:description xml:lang="en-US">
The following configuration steps should be taken on the machine which hosts the
web server, in order to provide as safe an environment as possible for the web server.
</ns0:description>
          <ns0:Group id="httpd_restrict_file_dir_access">
            <ns0:title xml:lang="en-US">Restrict File and Directory Access</ns0:title>
            <ns0:description xml:lang="en-US">
Minimize access to critical <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> files and directories.
</ns0:description>
            <ns0:Rule id="dir_perms_var_log_httpd" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Set Permissions on the /var/log/httpd/ Directory</ns0:title>
              <ns0:description xml:lang="en-US">
Ensure that the permissions on the web server log directory is set to 700:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 700 /var/log/httpd/</html:pre>
This is its default setting.
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Access to the web server's log files may allow an unauthorized user or attacker
to access information about the web server or alter the server's log files.
</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dir_perms_var_log_httpd:def:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="dir_perms_etc_httpd_conf" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Set Permissions on the /etc/httpd/conf/ Directory</ns0:title>
              <ns0:description xml:lang="en-US">
Set permissions on the web server configuration directory to 750:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 750 /etc/httpd/conf/</html:pre>
</ns0:description>
              <ns0:rationale xml:lang="en-US">
Access to the web server's configuration files may allow an unauthorized user or attacker
to access information about the web server or alter the server's configuration files.
</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dir_perms_etc_httpd_conf:def:1" />
              </ns0:check>
            </ns0:Rule>
            <ns0:Rule id="file_permissions_httpd_server_conf_files" selected="false" severity="low">
              <ns0:title xml:lang="en-US">Set Permissions on All Configuration Files Inside /etc/httpd/conf/</ns0:title>
              <ns0:description xml:lang="en-US">
Set permissions on the web server configuration files to 640:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo chmod 640 /etc/httpd/conf/*</html:pre>
</ns0:description>
              <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">CM-7</ns0:reference>
              <ns0:rationale xml:lang="en-US">
Access to the web server's configuration files may allow an unauthorized user or attacker
to access information about the web server or to alter the server's configuration files.
</ns0:rationale>
              <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
                <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-file_permissions_httpd_server_conf_files:def:1" />
              </ns0:check>
            </ns0:Rule>
          </ns0:Group>
          <ns0:Group id="httpd_configure_firewalld">
            <ns0:title xml:lang="en-US">Configure firewalld to Allow Access to the Web Server</ns0:title>
            <ns0:description xml:lang="en-US">
By default, <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code>
blocks access to the ports used by the web server.

        To configure <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> to allow access, run the following command(s):
        <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewall-cmd --permanent --add-service=http</html:code>

        To configure <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> to allow access, run the following command(s):
        <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewall-cmd --permanent --add-service=https</html:code>
</ns0:description>
          </ns0:Group>
          <ns0:Group id="httpd_chroot">
            <ns0:title xml:lang="en-US">Run httpd in a chroot Jail if Practical</ns0:title>
            <ns0:description xml:lang="en-US">
Running <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> inside a <html:code xmlns:html="http://www.w3.org/1999/xhtml">chroot</html:code> jail is designed to isolate the
web server process to a small section of the filesystem, limiting the damage if
it is compromised. Versions of Apache greater than 2.2.10 (such as the one
included with Red Hat Enterprise Linux 7) provide the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ChrootDir</html:code> directive. To run Apache
inside a chroot jail in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/chroot/apache</html:code>, add the following line to
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/httpd/conf/httpd.conf</html:code>: <html:pre xmlns:html="http://www.w3.org/1999/xhtml">ChrootDir /chroot/apache</html:pre> This
necessitates placing all files required by <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code> inside
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/chroot/apache</html:code> , including <html:code xmlns:html="http://www.w3.org/1999/xhtml">httpd</html:code>'s binaries, modules,
configuration files, and served web pages. The details of this configuration
are beyond the scope of this guide. This may also require additional SELinux
configuration.
</ns0:description>
          </ns0:Group>
        </ns0:Group>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="imap">
      <ns0:title xml:lang="en-US">IMAP and POP3 Server</ns0:title>
      <ns0:description xml:lang="en-US">Dovecot provides IMAP and POP3 services. It is not
installed by default. The project page at <html:a href="http://www.dovecot.org" xmlns:html="http://www.w3.org/1999/xhtml">http://www.dovecot.org</html:a>
contains more detailed information about Dovecot
configuration.</ns0:description>
      <ns0:Group id="disabling_dovecot">
        <ns0:title xml:lang="en-US">Disable Dovecot</ns0:title>
        <ns0:description xml:lang="en-US">If the system does not need to operate as an IMAP or
POP3 server, the dovecot software should be disabled and removed.
</ns0:description>
        <ns0:Rule id="service_dovecot_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Dovecot Service</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">dovecot</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable dovecot.service</html:pre>
          </ns0:description>
          <ns0:rationale xml:lang="en-US">
Running an IMAP or POP3 server provides a network-based
avenue of attack, and should be disabled if not needed.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_dovecot_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable dovecot
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_dovecot_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service dovecot
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - dovecot

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_dovecot_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_dovecot_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_dovecot_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Uninstall dovecot Package</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">dovecot</html:code> package can be uninstalled
with the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase dovecot</html:pre>
</ns0:description>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.12</ns0:reference>
          <ns0:rationale xml:lang="en-US">
If there is no need to make the Dovecot software available,
removing it provides a safeguard against its activation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_dovecot_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove dovecot
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_dovecot_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure dovecot is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - dovecot
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_dovecot_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_dovecot

class remove_dovecot {
  package { 'dovecot':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_dovecot_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=dovecot
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_dovecot_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_dovecot_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="configure_dovecot">
        <ns0:title xml:lang="en-US">Configure Dovecot if Necessary</ns0:title>
        <ns0:description xml:lang="en-US">If the system will operate as an IMAP or
POP3 server, the dovecot software should be configured securely by following
the recommendations below.
</ns0:description>
        <ns0:Group id="dovecot_support_necessary_protocols">
          <ns0:title xml:lang="en-US">Support Only the Necessary Protocols</ns0:title>
          <ns0:description xml:lang="en-US">Dovecot supports the IMAP and POP3 protocols, as well as 
SSL-protected versions of those protocols. Configure the Dovecot server 
to support only the protocols needed by your site. Edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dovecot/dovecot.conf</html:code>. 
Add or correct the following lines, replacing <html:code xmlns:html="http://www.w3.org/1999/xhtml">PROTOCOL</html:code> with 
only the subset of protocols (<html:code xmlns:html="http://www.w3.org/1999/xhtml">imap</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">imaps</html:code>, 
<html:code xmlns:html="http://www.w3.org/1999/xhtml">pop3</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">pop3s</html:code>) required:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">protocols = PROTOCOL</html:pre>
If possible, require SSL protection for all transactions. The SSL 
protocol variants listen on alternate ports (995 instead of 110 for 
pop3s, and 993 instead of 143 for imaps), and require SSL-aware clients. 
An alternate approach is to listen on the standard port and require the 
client to use the STARTTLS command before authenticating.
</ns0:description>
          <ns0:rationale xml:lang="en-US">
Configuring Dovecot to only support the protocols the protocols needed by
your site reduces the risk of an attacker using one of the unused protocols
to base an attack.</ns0:rationale>
        </ns0:Group>
        <ns0:Group id="dovecot_enabling_ssl">
          <ns0:title xml:lang="en-US">Enable SSL Support</ns0:title>
          <ns0:description xml:lang="en-US">SSL should be used to encrypt network traffic between the 
Dovecot server and its clients. Users must authenticate to the Dovecot 
server in order to read their mail, and passwords should never be 
transmitted in clear text. In addition, protecting mail as it is 
downloaded is a privacy measure, and clients may use SSL certificates 
to authenticate the server, preventing another system from impersonating 
the server.
</ns0:description>
          <ns0:Rule id="dovecot_enable_ssl" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Enable the SSL flag in /etc/dovecot.conf</ns0:title>
            <ns0:description xml:lang="en-US">To allow clients to make encrypted connections the <html:code xmlns:html="http://www.w3.org/1999/xhtml">ssl</html:code>
flag in Dovecot's configuration file needs to be set to <html:code xmlns:html="http://www.w3.org/1999/xhtml">yes</html:code>.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dovecot/conf.d/10-ssl.conf</html:code> and add or correct the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ssl = yes</html:pre>
</ns0:description>
            <ns0:rationale xml:lang="en-US">
SSL encrypt network traffic between the Dovecot server and its clients 
protecting user credentials, mail as it is downloaded, and clients may use 
SSL certificates to authenticate the server, preventing another system from 
impersonating the server.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dovecot_enable_ssl:def:1" />
            </ns0:check>
          </ns0:Rule>
          <ns0:Rule id="dovecot_configure_ssl_cert" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Configure Dovecot to Use the SSL Certificate file</ns0:title>
            <ns0:description xml:lang="en-US">This option tells Dovecot where to find the the mail 
server's SSL Certificate.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dovecot/conf.d/10-ssl.conf</html:code> and add or correct the following 
line (<html:i xmlns:html="http://www.w3.org/1999/xhtml">note: the path below is the default path set by the Dovecot installation. If 
you are using a different path, ensure you reference the appropriate file</html:i>):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ssl_cert = &lt;/etc/pki/dovecot/certs/dovecot.pem</html:pre>
</ns0:description>
            <ns0:rationale xml:lang="en-US">
SSL certificates are used by the client to authenticate the identity
of the server, as well as to encrypt credentials and message traffic.
Not using SSL to encrypt mail server traffic could allow unauthorized
access to credentials and mail messages since they are sent in plain 
text over the network.
</ns0:rationale>
            </ns0:Rule>
          <ns0:Rule id="dovecot_configure_ssl_key" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Configure Dovecot to Use the SSL Key file</ns0:title>
            <ns0:description xml:lang="en-US">This option tells Dovecot where to find the the mail 
server's SSL Key.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
Edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dovecot/conf.d/10-ssl.conf</html:code> and add or correct the following 
line (<html:i xmlns:html="http://www.w3.org/1999/xhtml">note: the path below is the default path set by the Dovecot installation. If 
you are using a different path, ensure you reference the appropriate file</html:i>):
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">ssl_key = &lt;/etc/pki/dovecot/private/dovecot.pem</html:pre>
</ns0:description>
            <ns0:rationale xml:lang="en-US">
SSL certificates are used by the client to authenticate the identity
of the server, as well as to encrypt credentials and message traffic.
Not using SSL to encrypt mail server traffic could allow unauthorized
access to credentials and mail messages since they are sent in plain 
text over the network.
</ns0:rationale>
            </ns0:Rule>
          <ns0:Rule id="dovecot_disable_plaintext_auth" selected="false" severity="low">
            <ns0:title xml:lang="en-US">Disable Plaintext Authentication</ns0:title>
            <ns0:description xml:lang="en-US">To prevent Dovecot from attempting plaintext 
authentication of clients, edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/dovecot/conf.d/10-auth.conf</html:code> and add
or correct the following line:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">disable_plaintext_auth = yes</html:pre>
</ns0:description>
            <ns0:rationale xml:lang="en-US">
Using plain text authentication to the mail server could allow an 
attacker access to credentials by monitoring network traffic.
</ns0:rationale>
            <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
              <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-dovecot_disable_plaintext_auth:def:1" />
            </ns0:check>
          </ns0:Rule>
        </ns0:Group>
        <ns0:Group id="dovecot_allow_imap_access">
          <ns0:title xml:lang="en-US">Allow IMAP Clients to Access the Server</ns0:title>
          <ns0:description xml:lang="en-US">The default <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> configuration does not allow inbound
access to any services. This modification will allow remote hosts to
initiate connections to the IMAP daemon, while keeping all other ports
on the server in their default protected state.

        To configure <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewalld</html:code> to allow access, run the following command(s):
        <html:code xmlns:html="http://www.w3.org/1999/xhtml">firewall-cmd --permanent --add-port=143/tcp</html:code> and
        
</ns0:description>
        </ns0:Group>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="routing">
      <ns0:title xml:lang="en-US">Network Routing</ns0:title>
      <ns0:description xml:lang="en-US">A router is a very desirable target for a
potential adversary because they fulfill a variety of 
infrastructure networking roles such as access to network segments,
gateways to other networks, filtering, etc. Therefore, if one is
required, the machine acting as a router should be dedicated
to that purpose alone and be stored in a physically secure
location. The system's default routing software is Quagga, and
provided in an RPM package of the same name.</ns0:description>
      <ns0:Group id="disabling_quagga">
        <ns0:title xml:lang="en-US">Disable Quagga if Possible</ns0:title>
        <ns0:description xml:lang="en-US">If Quagga was installed and activated, but the system
does not need to act as a router, then it should be disabled
and removed.
</ns0:description>
        <ns0:Rule id="service_zebra_disabled" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Disable Quagga Service</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">zebra</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable zebra.service</html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-32</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Routing protocol daemons are typically used on routers to exchange network
topology information with other routers. If routing daemons are used when not
required, system network information may be unnecessarily transmitted across
the network.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_zebra_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable zebra
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_zebra_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service zebra
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - zebra

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_zebra_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_zebra_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_quagga_removed" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Uninstall quagga Package</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">quagga</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase quagga</html:pre>
          </ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">SC-32</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Routing software is typically used on routers to exchange network topology information
with other routers. If routing software is used when not required, system network
information may be unnecessarily transmitted across the network.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" />
If there is no need to make the router software available,
removing it provides a safeguard against its activation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_quagga_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove quagga
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_quagga_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure quagga is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - quagga
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_quagga_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_quagga

class remove_quagga {
  package { 'quagga':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_quagga_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=quagga
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_quagga_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_quagga_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="smb">
      <ns0:title xml:lang="en-US">Samba(SMB) Microsoft Windows File Sharing Server</ns0:title>
      <ns0:description xml:lang="en-US">When properly configured, the Samba service allows
Linux machines to provide file and print sharing to Microsoft
Windows machines. There are two software packages that provide
Samba support. The first, <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba-client</html:code>, provides a series of
command line tools that enable a client machine to access Samba
shares. The second, simply labeled <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba</html:code>, provides the Samba
service. It is this second package that allows a Linux machine to
act as an Active Directory server, a domain controller, or as a
domain member. Only the <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba-client</html:code> package is installed by
default.</ns0:description>
      <ns0:Group id="disabling_samba">
        <ns0:title xml:lang="en-US">Disable Samba if Possible</ns0:title>
        <ns0:description xml:lang="en-US">
Even after the Samba server package has been installed, it
will remain disabled. Do not enable this service unless it is
absolutely necessary to provide Microsoft Windows file and print
sharing functionality.
</ns0:description>
        <ns0:Rule id="service_smb_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Samba</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">smb</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable smb.service</html:pre>
          </ns0:description>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1436</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Running a Samba server provides a network-based avenue of attack, and
should be disabled if not needed.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_smb_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable smb
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_smb_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service smb
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - smb

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_smb_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_smb_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_samba_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Uninstall Samba Package</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba</html:code> package can be uninstalled
with the following command:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase samba</html:pre>
</ns0:description>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.13</ns0:reference>
          <ns0:rationale xml:lang="en-US">
If there is no need to make the Samba software available,
removing it provides a safeguard against its activation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_samba_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove samba
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_samba_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure samba is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - samba
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_samba_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_samba

class remove_samba {
  package { 'samba':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_samba_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=samba
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_samba_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_samba_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="configuring_samba">
        <ns0:title xml:lang="en-US">Configure Samba if Necessary</ns0:title>
        <ns0:description xml:lang="en-US">All settings for the Samba daemon can be found in
<html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/samba/smb.conf</html:code>. Settings are divided between a
<html:code xmlns:html="http://www.w3.org/1999/xhtml">[global]</html:code> configuration section and a series of user
created share definition sections meant to describe file or print
shares on the system. By default, Samba will operate in user mode
and allow client machines to access local home directories and
printers. It is recommended that these settings be changed or that
additional limitations be set in place.</ns0:description>
        <ns0:Rule id="package_samba-common_installed" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Install the Samba Common Package</ns0:title>
          <ns0:description xml:lang="en-US">
The <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba-common</html:code> package should be installed.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">samba-common</html:code> package can be installed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum install samba-common</html:pre>
</ns0:description>
          <ns0:rationale xml:lang="en-US">
If the samba-common package is not installed, samba cannot be configured.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_samba-common_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command install samba-common
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_samba-common_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:ansible">- name: Ensure samba-common is installed
  package:
    name="{{item}}"
    state=present
  with_items:
    - samba-common
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_samba-common_installed" reboot="false" strategy="enable" system="urn:xccdf:fix:script:puppet">include install_samba-common

class install_samba-common {
  package { 'samba-common':
    ensure =&gt; 'installed',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_samba-common_installed" reboot="false" strategy="enable" system="urn:redhat:anaconda:pre">
package --add=samba-common
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_samba-common_installed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_samba-common_installed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="smb_restrict_file_sharing">
          <ns0:title xml:lang="en-US">Restrict SMB File Sharing to Configured Networks</ns0:title>
          <ns0:description xml:lang="en-US">Only users with local user accounts will be able to log in to
Samba shares by default. Shares can be limited to particular users or network
addresses. Use the <html:code xmlns:html="http://www.w3.org/1999/xhtml">hosts allow</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">hosts deny</html:code> directives
accordingly, and consider setting the valid users directive to a limited subset
of users or to a group of users. Separate each address, user, or user group
with a space as follows for a particular <html:i xmlns:html="http://www.w3.org/1999/xhtml">share</html:i> or global:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[<html:i>share</html:i>]
  hosts allow = 192.168.1. 127.0.0.1
  valid users = userone usertwo @usergroup</html:pre>
It is also possible to limit read and write access to particular users with the
read list and write list options, though the permissions set by the system
itself will override these settings. Set the read only attribute for each share
to ensure that global settings will not accidentally override the individual
share settings. Then, as with the valid users directive, separate each user or
group of users with a space:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[<html:i>share</html:i>]
  read only = yes
  write list = userone usertwo @usergroup</html:pre>
</ns0:description>
          <ns0:rationale xml:lang="en-US">The Samba service is only required for sharing files and printers
with Microsoft Windows workstations, and even then, other options may exist. 
</ns0:rationale>
        </ns0:Group>
        <ns0:Rule id="smb_server_disable_root" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Root Access to SMB Shares</ns0:title>
          <ns0:description xml:lang="en-US">Administrators should not use administrator accounts to access
Samba file and printer shares. Disable the root user and the wheel
administrator group:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[<html:i>share</html:i>]
  invalid users = root @wheel</html:pre>
If administrator accounts cannot be disabled, ensure that local machine
passwords and Samba service passwords do not match.</ns0:description>
          <ns0:rationale xml:lang="en-US">
Typically, administrator access is required when Samba must create user and
machine accounts and shares. Domain member servers and standalone servers may
not need administrator access at all. If that is the case, add the invalid
users parameter to <html:code xmlns:html="http://www.w3.org/1999/xhtml">[global]</html:code> instead.
</ns0:rationale>
          </ns0:Rule>
        <ns0:Rule id="require_smb_client_signing" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Require Client SMB Packet Signing, if using smbclient</ns0:title>
          <ns0:description xml:lang="en-US">
To require samba clients running <html:code xmlns:html="http://www.w3.org/1999/xhtml">smbclient</html:code> to use
packet signing, add the following to the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[global]</html:code> section
of the Samba configuration file, <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/samba/smb.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">client signing = mandatory</html:pre>
Requiring samba clients such as <html:code xmlns:html="http://www.w3.org/1999/xhtml">smbclient</html:code> to use packet
signing ensures they can
only communicate with servers that support packet signing.
</ns0:description>
          <ns0:rationale xml:lang="en-US">
Packet signing can prevent
man-in-the-middle attacks which modify SMB packets in
transit.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="require_smb_client_signing" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh">######################################################################
#By Luke "Brisk-OH" Brisk
#luke.brisk@boeing.com or luke.brisk@gmail.com
######################################################################

CLIENTSIGNING=$( grep -ic 'client signing' /etc/samba/smb.conf )

if [ "$CLIENTSIGNING" -eq 0 ];  then
	# Add to global section
	sed -i 's/\[global\]/\[global\]\n\n\tclient signing = mandatory/g' /etc/samba/smb.conf
else
	sed -i 's/[[:blank:]]*client[[:blank:]]signing[[:blank:]]*=[[:blank:]]*no/        client signing = mandatory/g' /etc/samba/smb.conf
fi

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-require_smb_client_signing:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-require_smb_client_signing_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="mount_option_smb_client_signing" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Require Client SMB Packet Signing, if using mount.cifs</ns0:title>
          <ns0:description xml:lang="en-US">Require packet signing of clients who mount Samba
shares using the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mount.cifs</html:code> program (e.g., those who specify shares
in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/fstab</html:code>). To do so, ensure signing options (either
<html:code xmlns:html="http://www.w3.org/1999/xhtml">sec=krb5i</html:code> or <html:code xmlns:html="http://www.w3.org/1999/xhtml">sec=ntlmv2i</html:code>) are used.
<html:br xmlns:html="http://www.w3.org/1999/xhtml" /><html:br xmlns:html="http://www.w3.org/1999/xhtml" />
See the <html:code xmlns:html="http://www.w3.org/1999/xhtml">mount.cifs(8)</html:code> man page for more information. A Samba
client should only communicate with servers who can support SMB
packet signing.
</ns0:description>
          <ns0:rationale xml:lang="en-US">
Packet signing can prevent man-in-the-middle
attacks which modify SMB packets in transit.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-mount_option_smb_client_signing:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-mount_option_smb_client_signing_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Group id="smb_disable_printing">
          <ns0:title xml:lang="en-US">Restrict Printer Sharing</ns0:title>
          <ns0:description xml:lang="en-US">By default, Samba utilizes the CUPS printing service to enable
printer sharing with Microsoft Windows workstations. If there are no printers
on the local machine, or if printer sharing with Microsoft Windows is not
required, disable the printer sharing capability by commenting out the
following lines, found in <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/samba/smb.conf</html:code>:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[global]
  load printers = yes
  cups options = raw
[printers]
  comment = All Printers
  path = /usr/spool/samba
  browseable = no
  guest ok = no
  writable = no
  printable = yes</html:pre>
There may be other options present, but these are the only options enabled and
uncommented by default. Removing the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[printers]</html:code> share should be enough
for most users.  If the Samba printer sharing capability is needed, consider
disabling the Samba network browsing capability or restricting access to a
particular set of users or network addresses. Set the <html:code xmlns:html="http://www.w3.org/1999/xhtml">valid users</html:code>
parameter to a small subset of users or restrict it to a particular group of
users with the shorthand <html:code xmlns:html="http://www.w3.org/1999/xhtml">@</html:code>. Separate each user or group of users with
a space. For example, under the <html:code xmlns:html="http://www.w3.org/1999/xhtml">[printers]</html:code> share:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">[printers]
  valid users = user @printerusers</html:pre>
</ns0:description>
          <ns0:rationale xml:lang="en-US">The Samba service is only required for sharing files and printers
with Microsoft Windows workstations, and even then, other options may exist. Do
not use the Samba service to share files between Unix or Linux machines.
</ns0:rationale>
        </ns0:Group>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="proxy">
      <ns0:title xml:lang="en-US">Proxy Server</ns0:title>
      <ns0:description xml:lang="en-US">A proxy server is a very desirable target for a
potential adversary because much (or all) sensitive data for a
given infrastructure may flow through it. Therefore, if one is
required, the machine acting as a proxy server should be dedicated
to that purpose alone and be stored in a physically secure
location. The system's default proxy server software is Squid, and
provided in an RPM package of the same name.</ns0:description>
      <ns0:Group id="disabling_squid">
        <ns0:title xml:lang="en-US">Disable Squid if Possible</ns0:title>
        <ns0:description xml:lang="en-US">If Squid was installed and activated, but the system
does not need to act as a proxy server, then it should be disabled
and removed.
</ns0:description>
        <ns0:Rule id="service_squid_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable Squid</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">squid</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable squid.service</html:pre>
          </ns0:description>
          <ns0:rationale xml:lang="en-US">
Running proxy server software provides a network-based avenue
of attack, and should be removed if not needed.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_squid_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable squid
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_squid_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service squid
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - squid

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_squid_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_squid_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_squid_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Uninstall squid Package</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">squid</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase squid</html:pre>
          </ns0:description>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.14</ns0:reference>
          <ns0:rationale xml:lang="en-US">
If there is no need to make the proxy server software available,
removing it provides a safeguard against its activation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_squid_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove squid
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_squid_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure squid is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - squid
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_squid_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_squid

class remove_squid {
  package { 'squid':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_squid_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=squid
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_squid_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_squid_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
    <ns0:Group id="snmp">
      <ns0:title xml:lang="en-US">SNMP Server</ns0:title>
      <ns0:description xml:lang="en-US">The Simple Network Management Protocol allows
administrators to monitor the state of network devices, including
computers. Older versions of SNMP were well-known for weak
security, such as plaintext transmission of the community string
(used for authentication) and usage of easily-guessable
choices for the community string.</ns0:description>
      <ns0:Group id="disabling_snmp_service">
        <ns0:title xml:lang="en-US">Disable SNMP Server if Possible</ns0:title>
        <ns0:description xml:lang="en-US">The system includes an SNMP daemon that allows for its remote
monitoring, though it not installed by default. If it was installed and
activated but is not needed, the software should be disabled and removed.
</ns0:description>
        <ns0:Rule id="service_snmpd_disabled" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Disable snmpd Service</ns0:title>
          <ns0:description xml:lang="en-US">
            
        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">snmpd</html:code> service can be disabled with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo systemctl disable snmpd.service</html:pre>
          </ns0:description>
          <ns0:rationale xml:lang="en-US">
Running SNMP software provides a network-based avenue of attack, and
should be disabled if not needed.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="service_snmpd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_service_command" />
service_command disable snmpd
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="service_snmpd_disabled" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Disable service snmpd
  service:
    name="{{item}}"
    enabled="no"
    state="stopped"
  with_items:
    - snmpd

</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-service_snmpd_disabled:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-service_snmpd_disabled_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="package_net-snmp_removed" selected="false" severity="low">
          <ns0:title xml:lang="en-US">Uninstall net-snmp Package</ns0:title>
          <ns0:description xml:lang="en-US">The <html:code xmlns:html="http://www.w3.org/1999/xhtml">net-snmp</html:code> package provides the snmpd service.

        The <html:code xmlns:html="http://www.w3.org/1999/xhtml">net-snmp</html:code> package can be removed with the following command:
        <html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo yum erase net-snmp</html:pre>
</ns0:description>
          <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">3.15</ns0:reference>
          <ns0:rationale xml:lang="en-US">
If there is no need to run SNMP server software,
removing the package provides a safeguard against its
activation.
</ns0:rationale>
          <ns0:fix complexity="low" disruption="low" id="package_net-snmp_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:sh"><ns0:sub idref="function_package_command" />
package_command remove net-snmp
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_net-snmp_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:ansible">- name: Ensure net-snmp is removed
  package:
    name="{{item}}"
    state=absent
  with_items:
    - net-snmp
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_net-snmp_removed" reboot="false" strategy="disable" system="urn:xccdf:fix:script:puppet">include remove_net-snmp

class remove_net-snmp {
  package { 'net-snmp':
    ensure =&gt; 'purged',
  }
}
</ns0:fix>
          <ns0:fix complexity="low" disruption="low" id="package_net-snmp_removed" reboot="false" strategy="disable" system="urn:redhat:anaconda:pre">
package -remove=net-snmp
</ns0:fix>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-package_net-snmp_removed:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-package_net-snmp_removed_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
      <ns0:Group id="snmp_configure_server">
        <ns0:title xml:lang="en-US">Configure SNMP Server if Necessary</ns0:title>
        <ns0:description xml:lang="en-US">If it is necessary to run the snmpd agent on the system, some best
practices should be followed to minimize the security risk from the
installation. The multiple security models implemented by SNMP cannot be fully
covered here so only the following general configuration advice can be offered:
<html:ul xmlns:html="http://www.w3.org/1999/xhtml"><html:li>use only SNMP version 3 security models and enable the use of authentication and encryption</html:li><html:li>write access to the MIB (Management Information Base) should be allowed only if necessary</html:li><html:li>all access to the MIB should be restricted following a principle of least privilege</html:li><html:li>network access should be limited to the maximum extent possible including restricting to expected network
addresses both in the configuration files and in the system firewall rules</html:li><html:li>ensure SNMP agents send traps only to, and accept SNMP queries only from, authorized management
stations</html:li><html:li>ensure that permissions on the <html:code>snmpd.conf</html:code> configuration file (by default, in <html:code>/etc/snmp</html:code>) are 640 or more restrictive</html:li><html:li>ensure that any MIB files' permissions are also 640 or more restrictive</html:li></html:ul>
</ns0:description>
        <ns0:Rule id="snmpd_use_newer_protocol" selected="false" severity="medium">
          <ns0:title xml:lang="en-US">Configure SNMP Service to Use Only SNMPv3 or Newer </ns0:title>
          <ns0:description xml:lang="en-US">
Edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/snmp/snmpd.conf</html:code>, removing any references to <html:code xmlns:html="http://www.w3.org/1999/xhtml">rocommunity</html:code>, <html:code xmlns:html="http://www.w3.org/1999/xhtml">rwcommunity</html:code>, or <html:code xmlns:html="http://www.w3.org/1999/xhtml">com2sec</html:code>.
Upon doing that, restart the SNMP service:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo service snmpd restart</html:pre>
</ns0:description>
          <ns0:rationale xml:lang="en-US">
Earlier versions of SNMP are considered insecure, as they potentially allow 
unauthorized access to detailed system management information.
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-snmpd_use_newer_protocol:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-snmpd_use_newer_protocol_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
        <ns0:Rule id="snmpd_not_default_password" selected="false" severity="high">
          <ns0:title xml:lang="en-US">Ensure Default SNMP Password Is Not Used</ns0:title>
          <ns0:description xml:lang="en-US">
Edit <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/snmp/snmpd.conf</html:code>, remove or change the default community strings of
<html:code xmlns:html="http://www.w3.org/1999/xhtml">public</html:code> and <html:code xmlns:html="http://www.w3.org/1999/xhtml">private</html:code>.
Once the default community strings have been changed, restart the SNMP service:
<html:pre xmlns:html="http://www.w3.org/1999/xhtml">$ sudo service snmpd restart</html:pre>
</ns0:description>
          <ns0:reference href="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf">IA-5.1(ii)</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">366</ns0:reference>
          <ns0:reference href="http://iase.disa.mil/stigs/srgs/Pages/index.aspx">SRG-OS-000480-GPOS-00227</ns0:reference>
          <ns0:rationale xml:lang="en-US">
Whether active or not, default simple network management protocol (SNMP) community
strings must be changed to maintain security. If the service is running with the
default authenticators, then anyone can gather data about the system and the network
and use the information to potentially compromise the integrity of the system and
network(s).
</ns0:rationale>
          <ns0:check system="http://oval.mitre.org/XMLSchema/oval-definitions-5">
            <ns0:check-content-ref href="ssg-rhel7-oval.xml" name="oval:ssg-snmpd_not_default_password:def:1" />
          </ns0:check>
          <ns0:check system="http://scap.nist.gov/schema/ocil/2">
            <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-snmpd_not_default_password_ocil:questionnaire:1" />
          </ns0:check>
        </ns0:Rule>
      </ns0:Group>
    </ns0:Group>
  </ns0:Group>
  <ns0:Group hidden="true" id="srg_support">
    <ns0:title xml:lang="en-US">Documentation to Support DISA OS SRG Mapping</ns0:title>
    <ns0:description xml:lang="en-US">These groups exist to document how the Red Hat Enterprise Linux
product meets (or does not meet) requirements listed in the DISA OS SRG, for
those cases where Groups or Rules elsewhere in scap-security-guide do
not clearly relate.
</ns0:description>
    <ns0:Rule id="met_inherently_generic" selected="false" severity="low">
      <ns0:title xml:lang="en-US">Product Meets this Requirement</ns0:title>
      <ns0:description xml:lang="en-US"> 
This requirement is a permanent not a finding. No fix is required.
</ns0:description>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">42</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">56</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">206</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1084</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">66</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">85</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">86</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">185</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">223</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">171</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">172</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1694</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">770</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">804</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">162</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">163</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">164</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">345</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">346</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1096</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1111</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1291</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">386</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">156</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">186</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1083</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1082</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1090</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">804</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1127</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1128</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1129</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1248</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1265</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1314</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1362</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1368</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1310</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1311</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1328</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1399</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1400</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1404</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1405</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1427</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1499</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1632</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1693</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1665</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1674</ns0:reference>
      <ns0:rationale xml:lang="en-US">
Red Hat Enterprise Linux meets this requirement through design and implementation.
</ns0:rationale>
      <ns0:check system="http://scap.nist.gov/schema/ocil/2">
        <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-met_inherently_generic_ocil:questionnaire:1" />
      </ns0:check>
    </ns0:Rule>
    <ns0:Rule id="met_inherently_auditing" selected="false" severity="low">
      <ns0:title xml:lang="en-US">Product Meets this Requirement</ns0:title>
      <ns0:description xml:lang="en-US"> 
This requirement is a permanent not a finding. No fix is required.
</ns0:description>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">130</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">157</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">131</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">132</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">133</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">134</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">135</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">159</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">174</ns0:reference>
      <ns0:rationale xml:lang="en-US">
The Red Hat Enterprise Linux audit system meets this requirement through design and implementation.
</ns0:rationale>
      <ns0:check system="http://scap.nist.gov/schema/ocil/2">
        <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-met_inherently_auditing_ocil:questionnaire:1" />
      </ns0:check>
    </ns0:Rule>
    <ns0:Rule id="met_inherently_nonselected" selected="false" severity="low">
      <ns0:title xml:lang="en-US">Product Meets this Requirement</ns0:title>
      <ns0:description xml:lang="en-US"> 
This requirement is a permanent not a finding. No fix is required.
</ns0:description>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">34</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">35</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">99</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">154</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">226</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">802</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">872</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1086</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1087</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1089</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1091</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1424</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1426</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1428</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1209</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1214</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1237</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1269</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1338</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1425</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1670</ns0:reference>
      <ns0:rationale xml:lang="en-US">
Red Hat Enterprise Linux meets this requirement through design and implementation.
</ns0:rationale>
      <ns0:check system="http://scap.nist.gov/schema/ocil/2">
        <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-met_inherently_nonselected_ocil:questionnaire:1" />
      </ns0:check>
    </ns0:Rule>
    <ns0:Rule id="unmet_nonfinding_nonselected_scope" selected="false" severity="low">
      <ns0:title xml:lang="en-US">Guidance Does Not Meet this Requirement Due to Impracticality or Scope</ns0:title>
      <ns0:description xml:lang="en-US"> 
This requirement is NA. No fix is required.
</ns0:description>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">21</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">25</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">28</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">29</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">30</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">165</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">221</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">354</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">553</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">779</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">780</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">781</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1009</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1094</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1123</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1124</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1125</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1132</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1135</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1140</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1141</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1142</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1143</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1145</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1147</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1148</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1166</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1339</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1340</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1341</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1350</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1356</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1373</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1374</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1383</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1391</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1392</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1395</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1662</ns0:reference>
      <ns0:rationale xml:lang="en-US">
The guidance does not meet this requirement.
The requirement is impractical or out of scope.
</ns0:rationale>
      <ns0:check system="http://scap.nist.gov/schema/ocil/2">
        <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-unmet_nonfinding_nonselected_scope_ocil:questionnaire:1" />
      </ns0:check>
    </ns0:Rule>
    <ns0:Rule id="unmet_finding_nonselected" selected="false" severity="low">
      <ns0:title xml:lang="en-US">Implementation of the Requirement is Not Supported</ns0:title>
      <ns0:description xml:lang="en-US">
This requirement is a permanent finding and cannot be fixed. An appropriate
mitigation for the system must be implemented but this finding cannot be
considered fixed.
</ns0:description>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">20</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">31</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">52</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">144</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1158</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1294</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1295</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1500</ns0:reference>
      <ns0:rationale xml:lang="en-US">
RHEL7 does not support this requirement.
</ns0:rationale>
      <ns0:check system="http://scap.nist.gov/schema/ocil/2">
        <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-unmet_finding_nonselected_ocil:questionnaire:1" />
      </ns0:check>
    </ns0:Rule>
    <ns0:Rule id="unmet_nonfinding_scope" selected="false" severity="low">
      <ns0:title xml:lang="en-US">Guidance Does Not Meet this Requirement Due to Impracticality or Scope</ns0:title>
      <ns0:description xml:lang="en-US"> 
This requirement is NA. No fix is required.
</ns0:description>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">15</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">27</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">218</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">219</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">371</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">372</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">535</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">537</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">539</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1682</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">370</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">37</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">24</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1112</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1126</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1143</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1149</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1157</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1159</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1210</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1211</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1274</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1372</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1376</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1377</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1352</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1401</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1555</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1556</ns0:reference>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1150</ns0:reference>
      <ns0:rationale xml:lang="en-US">
The guidance does not meet this requirement.
The requirement is impractical or out of scope.
</ns0:rationale>
      <ns0:check system="http://scap.nist.gov/schema/ocil/2">
        <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-unmet_nonfinding_scope_ocil:questionnaire:1" />
      </ns0:check>
    </ns0:Rule>
    <ns0:Rule id="update_process" selected="false" severity="low">
      <ns0:title xml:lang="en-US">A process for prompt installation of OS updates must exist.</ns0:title>
      <ns0:description xml:lang="en-US">
Procedures to promptly apply software updates must be established and
executed. The Red Hat operating system provides support for automating such a
process, by running the yum program through a cron job or by managing the
system and its packages through the Red Hat Network or a Satellite Server.
</ns0:description>
      <ns0:reference href="http://iase.disa.mil/stigs/cci/Pages/index.aspx">1232</ns0:reference>
      <ns0:rationale xml:lang="en-US">
This is a manual inquiry about update procedure.
</ns0:rationale>
      <ns0:check system="http://scap.nist.gov/schema/ocil/2">
        <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-update_process_ocil:questionnaire:1" />
      </ns0:check>
    </ns0:Rule>
  </ns0:Group>
  <ns0:Group hidden="true" id="c2s_support">
    <ns0:title xml:lang="en-US">Documentation to Support C2S/CIS  Mapping</ns0:title>
    <ns0:description xml:lang="en-US">These groups exist to document how the Red Hat Enterprise Linux
product meets (or does not meet) requirements listed in C2S/CIS, for
those cases where Groups or Rules elsewhere in scap-security-guide do
not clearly relate.
</ns0:description>
    <ns0:Rule id="c2s_procedural_requirement" selected="false" severity="low">
      <ns0:title xml:lang="en-US">Procedural Requirement</ns0:title>
      <ns0:description xml:lang="en-US">This requirement is procedural, and can not be met
through automated means.
</ns0:description>
      <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf" />
      <ns0:rationale xml:lang="en-US">This requirement is procedural, and can not be met through
automated means.</ns0:rationale>
      <ns0:check system="http://scap.nist.gov/schema/ocil/2">
        <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-c2s_procedural_requirement_ocil:questionnaire:1" />
      </ns0:check>
    </ns0:Rule>
    <ns0:Rule id="c2s_not_OS_applicable" selected="false" severity="low">
      <ns0:title xml:lang="en-US">Not Applicable to Operating System</ns0:title>
      <ns0:description xml:lang="en-US">While this requirement is applicable at an information system level, implementation
is not performed within the Operating System.</ns0:description>
      <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf" />
      <ns0:rationale xml:lang="en-US">This requirement is not applicable to an operating system.</ns0:rationale>
    </ns0:Rule>
    <ns0:Rule id="c2s_met_inherently" selected="false" severity="low">
      <ns0:title xml:lang="en-US">Product Meets this Requirement</ns0:title>
      <ns0:description xml:lang="en-US">
This requirement is permanent not a finding. No fix is required.
</ns0:description>
      <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf" />
      <ns0:rationale xml:lang="en-US">
Red Hat Enterprise Linux meets this requirement through design and implementation.
</ns0:rationale>
      <ns0:check system="http://scap.nist.gov/schema/ocil/2">
        <ns0:check-content-ref href="ssg-rhel7-ocil.xml" name="ocil:ssg-c2s_met_inherently_ocil:questionnaire:1" />
      </ns0:check>
    </ns0:Rule>
    <ns0:Rule id="apply_to_everything" selected="false" severity="low">
      <ns0:title xml:lang="en-US">Requirement Applies to All Rules</ns0:title>
      <ns0:description xml:lang="en-US">These are generic requirements, and apply to all rules</ns0:description>
      <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf" />
      <ns0:rationale xml:lang="en-US">The following requirements apply to all rules</ns0:rationale>
    </ns0:Rule>
    <ns0:Rule id="cis_xinetd" selected="false" severity="low">
      <ns0:title xml:lang="en-US">Rule Compliance through Removal of xinetd</ns0:title>
      <ns0:description xml:lang="en-US">The upstream CIS guidance is incorrect, stating that xinetd services can be managed through systemctl. The proper way to disable xinetd services, such as chargen-dgram, is to create a <html:code xmlns:html="http://www.w3.org/1999/xhtml">/etc/xinetd.d/SERVICE</html:code> file which disables the service. Regardless, these rules are inherently compliant with C2S/CIS policies through the removal of xinetd itself.</ns0:description>
      <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.12</ns0:reference>
      <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.13</ns0:reference>
      <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.14</ns0:reference>
      <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.15</ns0:reference>
      <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.16</ns0:reference>
      <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.17</ns0:reference>
      <ns0:reference href="https://benchmarks.cisecurity.org/tools2/linux/CIS_Red_Hat_Enterprise_Linux_7_Benchmark_v1.1.0.pdf">2.1.18</ns0:reference>
      <ns0:rationale xml:lang="en-US">These rules are inherently compliant when xinetd is removed
from the system</ns0:rationale>
    </ns0:Rule>
  </ns0:Group>
</ns0:Benchmark>