Guide to the Secure Configuration of Red Hat Enterprise Linux 7
with profile Common Profile for General-Purpose Systems
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 catalog, not a checklist, 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 Profiles, 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 RHEL 7 is one example of a baseline created from this guidance.
Evaluation Characteristics
| Target machine | localhost.localdomain |
|---|---|
| Benchmark URL | /usr/share/xml/scap/ssg/content/ssg-rhel7-xccdf.xml |
| Profile ID | common |
| Started at | 2015-07-17T10:50:19 |
| Finished at | 2015-07-17T10:50:20 |
| Performed by |
CPE Platforms
- cpe:/o:redhat:enterprise_linux:7
- cpe:/o:redhat:enterprise_linux:7::client
Addresses
- IPv4 127.0.0.1
- IPv4 192.168.122.210
- IPv4 172.17.42.1
- IPv6 0:0:0:0:0:0:0:1
- IPv6 fe80:0:0:0:5054:ff:fee9:4899
- IPv6 fe80:0:0:0:5484:7aff:fefe:9799
- MAC 00:00:00:00:00:00
- MAC 52:54:00:E9:48:99
- MAC 56:84:7A:FE:97:99
Compliance and Scoring
Rule results
Severity of failed rules
Score
| Scoring system | Score | Maximum | Percent |
|---|---|---|---|
| urn:xccdf:scoring:default | 83.333328 | 100.000000 |
Rule Overview
Result Details
Ensure /tmp Located On Separate Partition
| Rule ID | partition_for_tmp |
| Result | notselected |
| Time | 2015-07-17T10:50:19 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27173-4 references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20120928 by MM |
| Description |
The |
| Rationale |
The |
Ensure /var Located On Separate Partition
| Rule ID | partition_for_var |
| Result | notselected |
| Time | 2015-07-17T10:50:19 |
| Severity | low |
| Identifiers and References | identifiers: CCE-26404-4 references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20120928 by MM |
| Description | The |
| Rationale |
Ensuring that |
Ensure /var/log Located On Separate Partition
| Rule ID | partition_for_var_log |
| Result | notapplicable |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-26967-0 references: AU-9, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20120928 by MM |
| Description |
System logs are stored in the |
| Rationale |
Placing |
Ensure /var/log/audit Located On Separate Partition
| Rule ID | partition_for_var_log_audit |
| Result | notapplicable |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-26971-2 references: AU-4, AU-9, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20120928 by MM |
| Description |
Audit logs are stored in the |
| Rationale |
Placing |
Ensure /home Located On Separate Partition
| Rule ID | partition_for_home |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, 1208, Test attestation on 20120928 by MM |
| Description |
If user home directories will be stored locally, create a separate partition
for |
| Rationale |
Ensuring that |
Encrypt Partitions
| Rule ID | encrypt_partitions |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27128-8 |
| Description |
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.
part / --fstype=ext4 --size=100 --onpart=hda1 --encrypted --passphrase=PASSPHRASEAny PASSPHRASE is stored in the Kickstart in plaintext, and the Kickstart must then be protected accordingly. Omitting the --passphrase= option from the partition definition will cause the
installer to pause and interactively ask for the passphrase during installation.
Detailed information on encrypting partitions using LUKS can be found on the Red Hat Documentation web site: https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/sec-Encryption.html |
| Rationale | 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. |
Ensure Red Hat GPG Key Installed
| Rule ID | ensure_redhat_gpgkey_installed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-26957-1 references: CM-5(3), SI-7, MA-1(b), 1749, 366, Test attestation on 20150407 by sdw |
| Description | To ensure the system can cryptographically verify base software packages come from Red Hat (and to connect to the Red Hat Network to receive them), the Red Hat GPG key must properly be installed. To install the Red Hat GPG key, run: $ sudo rhn_registerIf the system is not connected to the Internet or an RHN Satellite, then install the Red Hat GPG key from trusted media such as the Red Hat installation CD-ROM or DVD. Assuming the disc is mounted in /media/cdrom, use the following command as the root user to import
it into the keyring:
$ sudo rpm --import /media/cdrom/RPM-GPG-KEY |
| Rationale | 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. |
Ensure gpgcheck Enabled In Main Yum Configuration
| Rule ID | ensure_gpgcheck_globally_activated |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-26989-4 references: CM-5(3), SI-7, MA-1(b), 1749, 366, Test attestation on 20150407 by sdw |
| Description | The gpgcheck=1 |
| Rationale | 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). |
Ensure gpgcheck Enabled For All Yum Package Repositories
| Rule ID | ensure_gpgcheck_never_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-26876-3 references: CM-5(3), SI-7, MA-1(b), 1749, 366, Test attestation on 20150407 by sdw |
| Description | To ensure signature checking is not disabled for
any repos, remove any lines from files in gpgcheck=0 |
| Rationale | 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). |
Ensure Software Patches Installed
| Rule ID | security_patches_up_to_date |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-26853-2 references: SI-2, MA-1(b), http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20120928 by MM |
| Description | If the system is joined to the Red Hat Network, a Red Hat Satellite Server, or a yum server, run the following command to install updates: $ sudo yum updateIf the system is not configured to use one of these sources, updates (in the form of RPM packages) can be manually downloaded from the Red Hat Network and installed using rpm.
|
| Rationale | Installing software updates is a fundamental mitigation against the exploitation of publicly-known vulnerabilities. |
Install AIDE
| Rule ID | package_aide_installed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26741-9 references: CM-3(d), CM-3(e), CM-6(d), CM-6(3), SC-28, SI-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | Install the AIDE package with the command: $ sudo yum install aide |
| Rationale | The AIDE package must be installed if it is to be available for integrity checking. |
Disable Prelinking
| Rule ID | disable_prelink |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
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
PRELINKING=noNext, run the following command to return binaries to a normal, non-prelinked state: $ sudo /usr/sbin/prelink -ua |
| Rationale | The prelinking feature can interfere with the operation of AIDE, because it changes binaries. |
Build and Test AIDE Database
| Rule ID | aide_build_database |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Run the following command to generate a new database: $ sudo /usr/sbin/aide --initBy default, the database will be written to the file /var/lib/aide/aide.db.new.gz.
Storing the database, the configuration file /etc/aide.conf, and the binary
/usr/sbin/aide (or hashes of these files), in a secure location (such as on read-only media) provides additional assurance about their integrity.
The newly-generated database can be installed as follows:
$ sudo cp /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gzTo initiate a manual check, run the following command: $ sudo /usr/sbin/aide --checkIf this check produces any unexpected output, investigate. |
| Rationale | 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. |
Configure Periodic Execution of AIDE
| Rule ID | aide_periodic_cron_checking |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-3(d), CM-3(e), CM-6(d), CM-6(3), SC-28, SI-7, 374, 416, 1069, 1263, 1297, 1589 |
| Description |
To implement a daily execution of AIDE at 4:05am using cron, add the following line to 05 4 * * * root /usr/sbin/aide --checkAIDE can be executed periodically through other means; this is merely one example. |
| Rationale | By default, AIDE does not install itself for periodic execution. Periodically running AIDE is necessary to reveal unexpected changes in installed files. |
Verify File Hashes with RPM
| Rule ID | rpm_verify_hashes |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The RPM package management system can check the hashes of installed software packages, including many that are important to system security. Run the following command to list which files on the system have hashes that differ from what is expected by the RPM database: $ rpm -Va | grep '^..5'A "c" in the second column indicates that a file is a configuration file, which may appropriately be expected to change. If the file was not expected to change, investigate the cause of the change using audit logs or other means. The package can then be reinstalled to restore the file. Run the following command to determine which package owns the file: $ rpm -qf FILENAMEThe package can be reinstalled from a yum repository using the command: $ sudo yum reinstall PACKAGENAMEAlternatively, the package can be reinstalled from trusted media using the command: $ sudo rpm -Uvh PACKAGENAME |
| Rationale | 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. |
Install Intrusion Detection Software
| Rule ID | install_hids |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
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. |
| Rationale | Host-based intrusion detection tools provide a system-level defense when an intruder gains access to a system or network. |
Install Virus Scanning Software
| Rule ID | install_antivirus |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Install virus scanning software, which uses signatures to search for the presence of viruses on the filesystem. The McAfee VirusScan Enterprise for Linux virus scanning tool is provided for DoD systems. 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. |
| Rationale | 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. |
Add nodev Option to Non-Root Local Partitions
| Rule ID | mount_option_nodev_nonroot_local_partitions |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | The |
| Rationale | The |
Add nodev Option to Removable Media Partitions
| Rule ID | mount_option_nodev_removable_partitions |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The |
| Rationale | The only legitimate location for device files is the |
Add noexec Option to Removable Media Partitions
| Rule ID | mount_option_noexec_removable_partitions |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The |
| Rationale | Allowing users to execute binaries from removable media such as USB keys exposes the system to potential compromise. |
Add nosuid Option to Removable Media Partitions
| Rule ID | mount_option_nosuid_removable_partitions |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The |
| Rationale | 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. |
Add nodev Option to /tmp
| Rule ID | mount_option_tmp_nodev |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The |
| Rationale | The only legitimate location for device files is the |
Add noexec Option to /tmp
| Rule ID | mount_option_tmp_noexec |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The |
| Rationale | Allowing users to execute binaries from world-writable directories
such as |
Add nosuid Option to /tmp
| Rule ID | mount_option_tmp_nosuid |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The |
| Rationale | 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. |
Add nodev Option to /dev/shm
| Rule ID | mount_option_dev_shm_nodev |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The |
| Rationale | The only legitimate location for device files is the |
Add noexec Option to /dev/shm
| Rule ID | mount_option_dev_shm_noexec |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The |
| Rationale | Allowing users to execute binaries from world-writable directories
such as |
Add nosuid Option to /dev/shm
| Rule ID | mount_option_dev_shm_nosuid |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The |
| Rationale | 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. |
Bind Mount /var/tmp To /tmp
| Rule ID | mount_option_var_tmp_bind |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | The /tmp /var/tmp none rw,nodev,noexec,nosuid,bind 0 0See the mount(8) man page for further explanation of bind mounting.
|
| Rationale | Having multiple locations for temporary storage is not required. Unless absolutely
necessary to meet requirements, the storage location |
Disable Modprobe Loading of USB Storage Driver
| Rule ID | kernel_module_usb-storage_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
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 install usb-storage /bin/trueThis will prevent the modprobe program from loading the usb-storage
module, but will not prevent an administrator (or another program) from using the
insmod program to load the module manually. |
| Rationale | USB storage devices such as thumb drives can be used to introduce malicious software. |
Disable Kernel Support for USB via Bootloader Configuration
| Rule ID | bootloader_nousb_argument |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
All USB support can be disabled by adding the kernel /vmlinuz-VERSION ro vga=ext root=/dev/VolGroup00/LogVol00 rhgb quiet nousbWARNING: 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. |
| Rationale | 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. |
Disable Booting from USB Devices in Boot Firmware
| Rule ID | bios_disable_usb_boot |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Configure the system boot firmware (historically called BIOS on PC systems) to disallow booting from USB drives. |
| Rationale | 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. |
Assign Password to Prevent Changes to Boot Firmware Configuration
| Rule ID | bios_assign_password |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Assign a password to the system boot firmware (historically called BIOS on PC systems) to require a password for any configuration changes. |
| Rationale | 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. |
Disable the Automounter
| Rule ID | service_autofs_disabled |
| Result | pass |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The $ sudo systemctl disable autofs |
| Rationale | Disabling the automounter permits the administrator to
statically control filesystem mounting through |
Disable GNOME3 Automounting
| Rule ID | dconf_gnome_disable_automount |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | 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,
the |
| Rationale | 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. |
Disable Mounting of cramfs
| Rule ID | kernel_module_cramfs_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
To configure the system to prevent the install cramfs /bin/trueThis effectively prevents usage of this uncommon filesystem. |
| Rationale | Linux kernel modules which implement filesystems that are not needed by the local system should be disabled. |
Disable Mounting of freevxfs
| Rule ID | kernel_module_freevxfs_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
To configure the system to prevent the install freevxfs /bin/trueThis effectively prevents usage of this uncommon filesystem. |
| Rationale | Linux kernel modules which implement filesystems that are not needed by the local system should be disabled. |
Disable Mounting of jffs2
| Rule ID | kernel_module_jffs2_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
To configure the system to prevent the install jffs2 /bin/trueThis effectively prevents usage of this uncommon filesystem. |
| Rationale | Linux kernel modules which implement filesystems that are not needed by the local system should be disabled. |
Disable Mounting of hfs
| Rule ID | kernel_module_hfs_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
To configure the system to prevent the install hfs /bin/trueThis effectively prevents usage of this uncommon filesystem. |
| Rationale | Linux kernel modules which implement filesystems that are not needed by the local system should be disabled. |
Disable Mounting of hfsplus
| Rule ID | kernel_module_hfsplus_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
To configure the system to prevent the install hfsplus /bin/trueThis effectively prevents usage of this uncommon filesystem. |
| Rationale | Linux kernel modules which implement filesystems that are not needed by the local system should be disabled. |
Disable Mounting of squashfs
| Rule ID | kernel_module_squashfs_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
To configure the system to prevent the install squashfs /bin/trueThis effectively prevents usage of this uncommon filesystem. |
| Rationale | Linux kernel modules which implement filesystems that are not needed by the local system should be disabled. |
Disable Mounting of udf
| Rule ID | kernel_module_udf_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
To configure the system to prevent the install udf /bin/trueThis effectively prevents usage of this uncommon filesystem. |
| Rationale | Linux kernel modules which implement filesystems that are not needed by the local system should be disabled. |
Disable All GNOME3 Thumbnailers
| Rule ID | dconf_gnome_disable_thumbnailers |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | 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, the |
| Rationale | 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. |
Verify User Who Owns shadow File
| Rule ID | userowner_shadow_file |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26795-5 references: AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description |
To properly set the owner of $ sudo chown root /etc/shadow |
| Rationale | The |
Verify Group Who Owns shadow File
| Rule ID | groupowner_shadow_file |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27125-4 references: AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description |
To properly set the group owner of $ sudo chgrp root xsl:value-of select="@file"/> |
| Rationale | The |
Verify User Who Owns group File
| Rule ID | file_owner_etc_group |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26933-2 references: AC-6, Test attestation on 20121026 by DS |
| Description |
To properly set the owner of $ sudo chown root /etc/group |
| Rationale | The |
Verify Group Who Owns group File
| Rule ID | file_groupowner_etc_group |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27037-1 references: AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description |
To properly set the group owner of $ sudo chgrp root xsl:value-of select="@file"/> |
| Rationale | The |
Verify User Who Owns gshadow File
| Rule ID | file_owner_etc_gshadow |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27161-9 references: AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description |
To properly set the owner of $ sudo chown root /etc/gshadow |
| Rationale | The |
Verify Group Who Owns gshadow File
| Rule ID | file_groupowner_etc_gshadow |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26840-9 references: AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description |
To properly set the group owner of $ sudo chgrp root xsl:value-of select="@file"/> |
| Rationale | The |
Verify User Who Owns passwd File
| Rule ID | file_owner_etc_passwd |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27138-7 references: AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description |
To properly set the owner of $ sudo chown root /etc/passwd |
| Rationale | The |
Verify Group Who Owns passwd File
| Rule ID | file_groupowner_etc_passwd |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26639-5 references: AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description |
To properly set the group owner of $ sudo chgrp root xsl:value-of select="@file"/> |
| Rationale | The |
Verify that Shared Library Files Have Root Ownership
| Rule ID | file_ownership_library_dirs |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26648-6 references: AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20130914 by swells |
| Description | System-wide shared library files, which are linked to executables during process load time or run time, are stored in the following directories by default: /lib /lib64 /usr/lib /usr/lib64Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules. All files in these directories should be
owned by the root user. If the directory, or any file in these
directories, is found to be owned by a user other than root correct its
ownership with the following command:
$ sudo chown root FILE |
| Rationale | 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. |
Verify that System Executables Have Root Ownership
| Rule ID | file_ownership_binary_dirs |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27119-7 references: AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx |
| Description | System executables are stored in the following directories by default: /bin /usr/bin /usr/local/bin /sbin /usr/sbin /usr/local/sbinAll files in these directories should be owned by the root user.
If any file FILE in these directories is found
to be owned by a user other than root, correct its ownership with the
following command:
$ sudo chown root FILE |
| Rationale | 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. |
Verify that All World-Writable Directories Have Sticky Bits Set
| Rule ID | sticky_world_writable_dirs |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-6, Test attestation on 20120929 by swells |
| Description | 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.
$ sudo chmod +t DIR |
| Rationale |
Failing to set the sticky bit on public directories allows unauthorized users to delete files in the directory structure.
|
Ensure No World-Writable Files Exist
| Rule ID | world_writeable_files |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-6 |
| Description | 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. |
| Rationale | 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. |
Ensure All Files Are Owned by a User
| Rule ID | no_files_unowned_by_user |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | 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. |
| Rationale | 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. |
Ensure All Files Are Owned by a Group
| Rule ID | no_files_unowned_by_group |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | 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. |
| Rationale | 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. |
Ensure All World-Writable Directories Are Owned by a System Account
| Rule ID | world_writable_files_system_ownership |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-6, Test attestation on 20120929 by swells |
| Description | 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. |
| Rationale | 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. |
Set Daemon Umask
| Rule ID | umask_for_daemons |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-6, Test attestation on 20140912 by JL |
| Description | The file umask UMASKSetting 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. |
| Rationale | 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. |
Disable Core Dumps for All Users
| Rule ID | disable_users_coredumps |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: SC-5 |
| Description | To disable core dumps for all users, add the following line to
* hard core 0 |
| Rationale | 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. |
Disable Core Dumps for SUID programs
| Rule ID | sysctl_fs_suid_dumpable |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: SI-11 |
| Description |
To set the runtime status of the $ sudo sysctl -w fs.suid_dumpable=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
fs.suid_dumpable = 0 |
| Rationale | 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. |
Enable ExecShield
| Rule ID | sysctl_kernel_exec_shield |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, Test attestation on 20121024 by DS |
| Description | 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 |
| Rationale | 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. |
Enable Randomized Layout of Virtual Address Space
| Rule ID | sysctl_kernel_randomize_va_space |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w kernel.randomize_va_space=2If this is not the system's default value, add the following line to /etc/sysctl.conf:
kernel.randomize_va_space = 2 |
| Rationale | 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. |
Install PAE Kernel on Supported 32-bit x86 Systems
| Rule ID | install_PAE_kernel_on_x86-32 |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf |
| Description | 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: $ sudo yum install kernel-PAEThe installation process should also have configured the bootloader to load the new kernel at boot. Verify this at reboot and modify /etc/default/grub if necessary. |
| Rationale | 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. |
| Warnings | warning
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. |
Enable NX or XD Support in the BIOS
| Rule ID | bios_enable_execution_restrictions |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf |
| Description | 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. |
| Rationale | 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. |
Restrict Access to Kernel Message Buffer
| Rule ID | enable_dmesg_restriction |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
To set the runtime status of the $ sudo sysctl -w kernel.dmesg_restrict=1If this is not the system's default value, add the following line to /etc/sysctl.conf:
kernel.dmesg_restrict = 1 |
| Rationale | Unprivileged access to the kernel syslog can expose sensitive kernel address information. |
Ensure SELinux Not Disabled in /etc/grub.conf
| Rule ID | enable_selinux_bootloader |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-3, AC-3(3), AC-6, AU-9, 22, 32, Test attestation on 20121024 by DS |
| Description | SELinux can be disabled at boot time by an argument in
|
| Rationale | 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. |
Ensure SELinux State is Enforcing
| Rule ID | selinux_state |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26800-3 references: AC-3, AC-3(3), AC-4, AC-6, AU-9, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | The SELinux state should be set to SELINUX=enforcing |
| Rationale | 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. |
Configure SELinux Policy
| Rule ID | selinux_policytype |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27135-3 references: AC-3, AC-3(3), AC-4, AC-6, AU-9, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | The SELinux SELINUXTYPE=targetedOther policies, such as mls, provide additional security labeling
and greater confinement but are not compatible with many general-purpose
use cases.
|
| Rationale |
Setting the SELinux policy to |
Uninstall setroubleshoot Package
| Rule ID | package_setroubleshoot_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE- |
| Description | The SETroubleshoot service notifies desktop users of SELinux
denials. The service provides information around configuration errors,
unauthorized intrusions, and other potential errors.
The $ sudo yum erase setroubleshoot |
| Rationale | The SETroubleshoot service is an unnecessary daemon to have running on a server |
Uninstall mcstrans Package
| Rule ID | package_mcstrans_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE- |
| Description | The $ sudo yum erase mcstrans |
| Rationale | 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. |
Ensure No Daemons are Unconfined by SELinux
| Rule ID | selinux_confinement_of_daemons |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
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 $ sudo ps -eZ | egrep "initrc" | egrep -vw "tr|ps|egrep|bash|awk" | tr ':' ' ' | awk '{ print $NF }'
It should produce no output in a well-configured system.
|
| Rationale |
Daemons which run with the |
Ensure No Device Files are Unlabeled by SELinux
| Rule ID | selinux_all_devicefiles_labeled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-6, AU-9, CM-7, 22, 32, Test attestation on 20121024 by DS |
| Description | Device files, which are used for communication with important
system resources, should be labeled with proper SELinux types. If any device
files carry the SELinux type |
| Rationale |
If a device file carries the SELinux type |
Direct root Logins Not Allowed
| Rule ID | no_direct_root_logins |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: IA-2(1), Test attestation on 20121024 by DS |
| Description | To further limit access to the $ sudo echo > /etc/securetty |
| Rationale | 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. |
Restrict Virtual Console Root Logins
| Rule ID | securetty_root_login_console_only |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-6(2), 770, Test attestation on 20121024 by DS |
| Description |
To restrict root logins through the (deprecated) virtual console devices,
ensure lines of this form do not appear in vc/1 vc/2 vc/3 vc/4 |
| Rationale | Preventing direct root login to virtual console devices helps ensure accountability for actions taken on the system using the root account. |
Restrict Serial Port Root Logins
| Rule ID | restrict_serial_port_logins |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-6(2), 770, Test attestation on 20121024 by DS |
| Description | To restrict root logins on serial ports,
ensure lines of this form do not appear in ttyS0 ttyS1 |
| Rationale | Preventing direct root login to serial port interfaces helps ensure accountability for actions taken on the systems using the root account. |
Restrict Web Browser Use for Administrative Accounts
| Rule ID | no_root_webbrowsing |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Enforce policy requiring administrative accounts use web browsers only for local service administration. |
| Rationale | 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. |
Ensure that System Accounts Do Not Run a Shell Upon Login
| Rule ID | no_shelllogin_for_systemaccounts |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26448-1 references: AC-2, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description |
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.
$ sudo usermod -s /sbin/nologin SYSACCT |
| Rationale | Ensuring shells are not given to system accounts upon login makes it more difficult for attackers to make use of system accounts. |
| Warnings | warning
Do not perform the steps in this
section on the root account. Doing so might cause the system to
become inaccessible.
|
Verify Only Root Has UID 0
| Rule ID | accounts_no_uid_except_zero |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27175-9 references: AC-6, IA-2(1), http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | 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. |
| Rationale | 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. |
Root Path Must Be Vendor Default
| Rule ID | root_path_default |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: SA-8, Test attestation on 20121024 by DS |
| Description | Assuming root shell is bash, edit the following files: ~/.profile ~/.bashrcChange any PATH variables to the vendor default for root and remove any
empty PATH entries or references to relative paths.
|
| Rationale | The root account's executable search path must be the vendor default, and must contain only absolute paths. |
Prevent Log In to Accounts With Empty Password
| Rule ID | no_empty_passwords |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-27010-8 references: IA-5(b), IA-5(c), IA-5(1)(a), Test attestation on 20121024 by DS |
| Description | 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 |
| Rationale | 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. |
Verify All Account Password Hashes are Shadowed
| Rule ID | accounts_password_all_shadowed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27144-5 references: IA-5(h), http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description |
If any password hashes are stored in |
| Rationale |
The hashes for all user account passwords should be stored in
the file |
All GIDs referenced in /etc/passwd must be defined in /etc/group
| Rule ID | gid_passwd_group_same |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: 366, Test attestation on 20121024 by DS |
| Description | Add a group to the system for each GID referenced without a corresponding group. |
| Rationale |
Inconsistency in GIDs between |
Verify No netrc Files Exist
| Rule ID | no_netrc_files |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The |
| Rationale |
Unencrypted passwords for remote FTP servers may be stored in |
Set Password Minimum Length in login.defs
| Rule ID | accounts_password_minlen_login_defs |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27123-9 references: IA-5(f), IA-5(1)(a), http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description | To specify password length requirements for new accounts,
edit the file PASS_MIN_LEN 14 The DoD requirement is 14.
The FISMA requirement is 12.
If a program consults /etc/login.defs and also another PAM module
(such as pam_pwquality) during a password change operation,
then the most restrictive must be satisfied. See PAM section
for more information about enforcing password quality requirements.
|
| Rationale | 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. |
Set Password Minimum Age
| Rule ID | accounts_minimum_age_login_defs |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27002-5 references: IA-5(f), IA-5(1)(d), 198, 75, Test attestation on 20121026 by DS |
| Description | To specify password minimum age for new accounts,
edit the file PASS_MIN_DAYS DAYSA value of 1 day is considered for sufficient for many environments. The DoD requirement is 1. |
| Rationale | Setting the minimum password age protects against users cycling back to a favorite password after satisfying the password reuse requirement. |
Set Password Maximum Age
| Rule ID | accounts_maximum_age_login_defs |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27051-2 references: IA-5(f), IA-5(g), IA-5(1)(d), 180, 199, 76, Test attestation on 20121026 by DS |
| Description | To specify password maximum age for new accounts,
edit the file PASS_MAX_DAYS DAYSA value of 180 days is sufficient for many environments. The DoD requirement is 60. |
| Rationale | Setting the password maximum age ensures users are required to periodically change their passwords. This could possibly decrease the utility of a stolen password. Requiring shorter password lifetimes increases the risk of users writing down the password in a convenient location subject to physical compromise. |
Set Password Warning Age
| Rule ID | accounts_password_warn_age_login_defs |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-26486-1 references: AC-2(2), IA-5(f), Test attestation on 20121026 by DS |
| Description | To specify how many days prior to password
expiration that a warning will be issued to users,
edit the file PASS_WARN_AGE DAYSThe DoD requirement is 7. |
| Rationale | Setting the password warning age enables users to make the change at a practical time. |
Set Account Expiration Following Inactivity
| Rule ID | account_disable_post_pw_expiration |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-TBD |
| Description | 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 INACTIVE=NUM_DAYSA 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 useradd man page for more information. Determining the inactivity
timeout must be done with careful consideration of the length of a "normal"
period of inactivity for users in the particular environment. Setting
the timeout too low incurs support costs and also has the potential to impact
availability of the system to legitimate users.
|
| Rationale | Disabling inactive accounts ensures that accounts which may not have been responsibly removed are not available to attackers who may have compromised their credentials. |
Ensure All Accounts on the System Have Unique Names
Assign Expiration Date to Temporary Accounts
| Rule ID | account_temp_expire_date |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27498-5 |
| Description |
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 $ sudo chage -E YYYY-MM-DD USER YYYY-MM-DD indicates the documented expiration date for the account.
For U.S. Government systems, the operating system must be configured to automatically terminate
these typoes of accounts after a period of 72 hours.
|
| Rationale |
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.
|
Set Password Retry Prompts Permitted Per-Session
| Rule ID | accounts_password_pam_retry |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27131-2 references: IA-5(c), http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20140925 by swells |
| Description | To configure the number of retry prompts that are permitted per-session:
|
| Rationale | 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. |
Set Password to Maximum of Three Consecutive Repeating Characters
| Rule ID | accounts_password_pam_maxrepeat |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The pam_pwquality module's |
| Rationale | Passwords with excessive repeating characters may be more vulnerable to password-guessing attacks. |
Set Password Strength Minimum Digit Characters
| Rule ID | accounts_password_pam_dcredit |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27163-5 references: IA-5(b), IA-5(c), 194, 194, 71, Test attestation on 20121024 by DS |
| Description | The pam_pwquality module's |
| Rationale | Requiring digits makes password guessing attacks more difficult by ensuring a larger search space. |
Set Password Minimum Length
| Rule ID | accounts_password_pam_minlen |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-26615-5 references: IA-5(1)(a), 205, 78, Test attestation on 20140928 by swells |
| Description | The pam_pwquality module's |
| Rationale | Password length is one factor of several that helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password. |
Set Password Strength Minimum Uppercase Characters
| Rule ID | accounts_password_pam_ucredit |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-26988-6 references: IA-5(b), IA-5(c), IA-5(1)(a), 192, 69, Test attestation on 20121024 by DS |
| Description | The pam_pwquality module's |
| Rationale | Requiring a minimum number of uppercase characters makes password guessing attacks more difficult by ensuring a larger search space. |
Set Password Strength Minimum Special Characters
| Rule ID | accounts_password_pam_ocredit |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27151-0 references: IA-5(b), IA-5(c), IA-5(1)(a), 1619, 266, Test attestation on 20121024 by DS |
| Description | The pam_pwquality module's |
| Rationale | Requiring a minimum number of special characters makes password guessing attacks more difficult by ensuring a larger search space. |
Set Password Strength Minimum Lowercase Characters
| Rule ID | accounts_password_pam_lcredit |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27111-4 references: IA-5(b), IA-5(c), IA-5(1)(a), 193, 70, Test attestation on 20121024 by DS |
| Description | The pam_pwquality module's |
| Rationale | Requiring a minimum number of lowercase characters makes password guessing attacks more difficult by ensuring a larger search space. |
Set Password Strength Minimum Different Characters
| Rule ID | accounts_password_pam_difok |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-26631-2 references: IA-5(b), IA-5(c), IA-5(1)(b), 195, 72, Test attestation on 20121024 by DS |
| Description | The pam_pwquality module's |
| Rationale | 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. |
Set Password Strength Minimum Different Categories
| Rule ID | accounts_password_pam_minclass |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27115-5 references: Test attestation on 20140626 by JL |
| Description | The pam_pwquality module's * Upper-case characters * Lower-case characters * Digits * Special characters (for example, punctuation)Modify the minclass setting in /etc/security/pwquality.conf entry to require
differing categories of characters when changing passwords. The minimum requirement is 3.
|
| Rationale | Requiring a minimum number of character categories makes password guessing attacks more difficult by ensuring a larger search space. |
Set Deny For Failed Password Attempts
| Rule ID | accounts_passwords_pam_faillock_deny |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26891-2 |
| Description |
To configure the system to lock out accounts after a number of incorrect login
attempts using
|
| Rationale | Locking out user accounts after a number of incorrect attempts prevents direct password guessing attacks. |
Set Lockout Time For Failed Password Attempts
| Rule ID | accounts_passwords_pam_faillock_unlock_time |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26884-7 |
| Description |
To configure the system to lock out accounts after a number of incorrect login
attempts and require an administrator to unlock the account using
|
| Rationale | 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. |
Set Interval For Counting Failed Password Attempts
| Rule ID | accounts_passwords_pam_faillock_interval |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26763-3 |
| Description |
Utilizing
|
| Rationale | Locking out user accounts after a number of incorrect attempts within a specific period of time prevents direct password guessing attacks. |
Limit Password Reuse
| Rule ID | accounts_password_pam_unix_remember |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26923-3 references: IA-5(f), IA-5(1)(e), 200, 77, Test attestation on 20121024 by DS |
| Description | Do not allow users to reuse recent passwords. This can
be accomplished by using the password sufficient pam_unix.so existing_options remember=5The DoD STIG requirement is 5 passwords. |
| Rationale | Preventing re-use of previous passwords helps ensure that a compromised password is not re-used by a user. |
Set Password Hashing Algorithm in /etc/pam.d/system-auth
| Rule ID | set_password_hashing_algorithm_systemauth |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27104-9 references: IA-5(b), IA-5(c), IA-5(1)(c), IA-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description |
In password sufficient pam_unix.so sha512 other arguments...This will help ensure when local users change their passwords, hashes for the new passwords will be generated using the SHA-512 algorithm. This is the default. |
| Rationale | Using a stronger hashing algorithm makes password cracking attacks more difficult. |
Set Password Hashing Algorithm in /etc/login.defs
| Rule ID | set_password_hashing_algorithm_logindefs |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27124-7 references: IA-5(b), IA-5(c), IA-5(1)(c), IA-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description |
In ENCRYPT_METHOD SHA512 |
| Rationale | Using a stronger hashing algorithm makes password cracking attacks more difficult. |
Set Password Hashing Algorithm in /etc/libuser.conf
| Rule ID | set_password_hashing_algorithm_libuserconf |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27053-8 references: IA-5(b), IA-5(c), IA-5(1)(c), IA-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description |
In crypt_style = sha512 |
| Rationale | Using a stronger hashing algorithm makes password cracking attacks more difficult. |
Set Last Logon/Access Notification
| Rule ID | display_login_attempts |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: 53 |
| Description | To configure the system to notify users of last logon/access
using 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 |
| Rationale | 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. |
Ensure that Root's Path Does Not Include Relative Paths or Null Directories
| Rule ID | root_path_no_dot |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf |
| Description |
Ensure that none of the directories in root's path is equal to a single
PATH=:/bin PATH=/bin: PATH=/bin::/sbinThese empty elements have the same effect as a single . character.
|
| Rationale | Including these entries increases the risk that root could execute code from an untrusted location. |
Ensure that Root's Path Does Not Include World or Group-Writable Directories
| Rule ID | root_path_no_groupother_writable |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf |
| Description | For each element in root's path, run: # ls -ld DIRand ensure that write permissions are disabled for group and other. |
| Rationale | Such entries increase the risk that root could execute code provided by unprivileged users, and potentially malicious code. |
Ensure the Default Bash Umask is Set Correctly
| Rule ID | accounts_umask_bashrc |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: SA-8, 366, Test attestation on 20140912 by JL |
| Description |
To ensure the default umask for users of the Bash shell is set properly,
add or correct the umask 077 |
| Rationale | 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. |
Ensure the Default C Shell Umask is Set Correctly
| Rule ID | accounts_umask_cshrc |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: SA-8, 366, Test attestation on 20140912 by JL |
| Description |
To ensure the default umask for users of the C shell is set properly,
add or correct the umask 077 |
| Rationale | 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. |
Ensure the Default Umask is Set Correctly in /etc/profile
| Rule ID | accounts_umask_etc_profile |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: SA-8, 366, Test attestation on 20120929 by swells |
| Description |
To ensure the default umask controlled by umask 077 |
| Rationale | 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. |
Ensure the Default Umask is Set Correctly in login.defs
| Rule ID | accounts_umask_login_defs |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: SA-8, 366, Test attestation on 20140912 by JL |
| Description |
To ensure the default umask controlled by UMASK 077 |
| Rationale | 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. |
Limit the Number of Concurrent Login Sessions Allowed Per User
| Rule ID | accounts_max_concurrent_login_sessions |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27081-9 |
| Description |
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. The DoD requirement is 10. To set the number of concurrent
sessions per user add the following line in * hard maxlogins 1 |
| Rationale | 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. |
Ensure that User Home Directories are not Group-Writable or World-Readable
| Rule ID | homedir_perms_no_groupwrite_worldread |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-6 |
| Description | For each human user of the system, view the permissions of the user's home directory: # ls -ld /home/USEREnsure that the directory is not group-writable and that it is not world-readable. If necessary, repair the permissions: # chmod g-w /home/USER # chmod o-rwx /home/USER |
| Rationale | 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. |
| Warnings | warning
This action may involve
modifying user home directories. Notify your user community, and
solicit input if appropriate, before making this type of
change. |
Verify /boot/grub2/grub.cfg User Ownership
| Rule ID | file_user_owner_grub2_cfg |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26860-7 references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description | The file $ sudo chown root /boot/grub2/grub.cfg |
| Rationale | Only root should be able to modify important boot parameters. |
Verify /boot/grub2/grub.cfg Group Ownership
| Rule ID | file_group_owner_grub2_cfg |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26812-8 references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description | The file $ sudo chgrp root xsl:value-of select="@file"/> |
| Rationale |
The |
Set Boot Loader Password
| Rule ID | bootloader_password |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26809-4 references: IA-2(1), IA-5(e), AC-3, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description | The grub2 boot loader should have a superuser account and password
protection enabled to protect boot-time settings.
$ grub2-mkpasswd-pbkdf2When prompted, enter the password that was selected and insert the returned password hash into the appropriate grub2 configuration file(s) under /etc/grub.d immediately after the superuser account.
(Use the output from grub2-mkpasswd-pbkdf2 as the value of
password-hash):
password_pbkdf2 superusers-account password-hashNOTE: It is recommended not to use common administrator account names like root, admin, or administrator for the grub2 superuser account. 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 grub.cfg file by running:
grub2-mkconfig -o /boot/grub2/grub.cfgNOTE: Do NOT manually add the superuser account and password to the grub.cfg file as the grub2-mkconfig command overwrites this file.
|
| Rationale | 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
|
Set GNOME3 Screensaver Inactivity Timeout
| Rule ID | dconf_gnome_screensaver_idle_delay |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
To set the idle time-out value for inactivity in the GNOME3 desktop to 5 minutes (in seconds),
the |
| Rationale | Setting the idle delay controls when the screensaver will start, and can be combined with screen locking to prevent access from passersby. |
Enable GNOME3 Screensaver Idle Activation
| Rule ID | dconf_gnome_screensaver_idle_activation_enabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
To activate the screensaver in the GNOME3 desktop after a period of inactivity,
the |
| Rationale | 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. |
Enable GNOME3 Screensaver Lock After Idle Period
| Rule ID | dconf_gnome_screensaver_lock_enabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
To activate locking of the screensaver in the GNOME3 desktop when it is activated,
the |
| Rationale | Enabling the activation of the screen lock after an idle period ensures password entry will be required in order to access the system, preventing access by passersby. |
Implement Blank Screensaver
| Rule ID | dconf_gnome_screensaver_mode_blank |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
To set the screensaver mode in the GNOME3 desktop to a blank screen,
the |
| Rationale | Setting the screensaver mode to blank-only conceals the contents of the display from passersby. |
Install the screen Package
| Rule ID | package_screen_installed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: 58, Test attestation on 20121026 by DS |
| Description |
To enable console screen locking, install the $ sudo yum install screenInstruct users to begin new terminal sessions with the following command: $ screenThe console can now be locked with the following key combination: ctrl+a x |
| Rationale |
Installing |
Enable Smart Card Login
| Rule ID | smartcard_auth |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | To enable smart card authentication, consult the documentation at:
|
| Rationale | 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. |
Require Authentication for Single User Mode
| Rule ID | require_singleuser_auth |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27170-0 references: IA-2(1), AC-3, 213, Test attestation on 20121024 by DS |
| Description | 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.
|
| Rationale | 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. |
Disable Ctrl-Alt-Del Reboot Activation
| Rule ID | disable_ctrlaltdel_reboot |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
By default, the system includes the following line in
exec /sbin/shutdown -r now "Control-Alt-Delete pressed" To configure the system to log a message instead of rebooting the system, alter that line to read as follows: exec /usr/bin/logger -p security.info "Control-Alt-Delete pressed" |
| Rationale | 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. In the GNOME graphical environment, risk of unintentional reboot from the Ctrl-Alt-Del sequence is reduced because the user will be prompted before any action is taken. |
Disable Interactive Boot
| Rule ID | disable_interactive_boot |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: SC-2, AC-3, 213, Test attestation on 20121024 by DS |
| Description |
To disable the ability for users to perform interactive startups,
edit the file PROMPT=noThe PROMPT option allows the console user to perform an
interactive system startup, in which it is possible to select the
set of services which are started on boot.
|
| Rationale | Using interactive boot, the console user could disable auditing, firewalls, or other services, weakening system security. |
Disable the GNOME3 Login User List
| Rule ID | dconf_gnome_disable_user_list |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-23 |
| Description | 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.
|
| Rationale | 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. |
Disable Kernel Parameter for Sending ICMP Redirects by Default
| Rule ID | sysctl_net_ipv4_conf_default_send_redirects |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-4, CM-7, SC-5, SC-7, 1551, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.conf.default.send_redirects=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.conf.default.send_redirects = 0 |
| Rationale | Sending ICMP redirects permits the system to instruct other systems to update their routing information. The ability to send ICMP redirects is only appropriate for systems acting as routers. |
Disable Kernel Parameter for Sending ICMP Redirects for All Interfaces
| Rule ID | sysctl_net_ipv4_conf_all_send_redirects |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, SC-5(1), 1551, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.conf.all.send_redirects=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.conf.all.send_redirects = 0 |
| Rationale | Sending ICMP redirects permits the system to instruct other systems to update their routing information. The ability to send ICMP redirects is only appropriate for systems acting as routers. |
Disable Kernel Parameter for IP Forwarding
| Rule ID | sysctl_ipv4_ip_forward |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, SC-5, 366, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.ip_forward=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.ip_forward = 0 |
| Rationale | 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. |
Disable Kernel Parameter for Accepting Source-Routed Packets for All Interfaces
| Rule ID | sysctl_net_ipv4_conf_all_accept_source_route |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, SC-5, 1551, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.conf.all.accept_source_route=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.conf.all.accept_source_route = 0 |
| Rationale | Accepting source-routed packets in the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required. |
Disable Kernel Parameter for Accepting ICMP Redirects for All Interfaces
| Rule ID | sysctl_net_ipv4_conf_all_accept_redirects |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, SC-5, 1503, 1551, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.conf.all.accept_redirects=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.conf.all.accept_redirects = 0 |
| Rationale | Accepting ICMP redirects has few legitimate uses. It should be disabled unless it is absolutely required. |
Disable Kernel Parameter for Accepting Secure Redirects for All Interfaces
| Rule ID | sysctl_net_ipv4_conf_all_secure_redirects |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-4, CM-7, SC-5, 1503, 1551, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.conf.all.secure_redirects=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.conf.all.secure_redirects = 0 |
| Rationale | Accepting "secure" ICMP redirects (from those gateways listed as default gateways) has few legitimate uses. It should be disabled unless it is absolutely required. |
Enable Kernel Parameter to Log Martian Packets
| Rule ID | sysctl_net_ipv4_conf_all_log_martians |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), CM-7, SC-5(3), 126, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.conf.all.log_martians=1If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.conf.all.log_martians = 1 |
| Rationale | 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. |
Disable Kernel Parameter for Accepting Source-Routed Packets By Default
| Rule ID | sysctl_net_ipv4_conf_default_accept_source_route |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-4, CM-7, SC-5, SC-7, 1551, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.conf.default.accept_source_route=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.conf.default.accept_source_route = 0 |
| Rationale | Accepting source-routed packets in the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required. |
Disable Kernel Parameter for Accepting ICMP Redirects By Default
| Rule ID | sysctl_net_ipv4_conf_default_accept_redirects |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-4, CM-7, SC-5, SC-7, 1551, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.conf.default.accept_redirects=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.conf.default.accept_redirects = 0 |
| Rationale | This feature of the IPv4 protocol has few legitimate uses. It should be disabled unless it is absolutely required. |
Disable Kernel Parameter for Accepting Secure Redirects By Default
| Rule ID | sysctl_net_ipv4_conf_default_secure_redirects |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-4, CM-7, SC-5, SC-7, 1551, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.conf.default.secure_redirects=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.conf.default.secure_redirects = 0 |
| Rationale | Accepting "secure" ICMP redirects (from those gateways listed as default gateways) has few legitimate uses. It should be disabled unless it is absolutely required. |
Enable Kernel Parameter to Ignore ICMP Broadcast Echo Requests
| Rule ID | sysctl_net_ipv4_icmp_echo_ignore_broadcasts |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, SC-5, 1551, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.icmp_echo_ignore_broadcasts = 1 |
| Rationale | Ignoring ICMP echo requests (pings) sent to broadcast or multicast addresses makes the system slightly more difficult to enumerate on the network. |
Enable Kernel Parameter to Ignore Bogus ICMP Error Responses
| Rule ID | sysctl_net_ipv4_icmp_ignore_bogus_error_responses |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, SC-5, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.icmp_ignore_bogus_error_responses = 1 |
| Rationale | Ignoring bogus ICMP error responses reduces log size, although some activity would not be logged. |
Enable Kernel Parameter to Use Reverse Path Filtering for All Interfaces
| Rule ID | sysctl_net_ipv4_conf_all_rp_filter |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-4, SC-5, SC-7, 1551, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.conf.all.rp_filter=1If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.conf.all.rp_filter = 1 |
| Rationale | 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. |
Enable Kernel Parameter to Use Reverse Path Filtering by Default
| Rule ID | sysctl_net_ipv4_conf_default_rp_filter |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-4, SC-5, SC-7, Test attestation on 20121024 by DS |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv4.conf.default.rp_filter=1If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.conf.default.rp_filter = 1 |
| Rationale | 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. |
Disable WiFi or Bluetooth in BIOS
| Rule ID | wireless_disable_in_bios |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), AC-18(a), AC-18(d), AC-18(3), CM-7, 85 |
| Description | 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. |
| Rationale | Disabling wireless support in the BIOS prevents easy activation of the wireless interface, generally requiring administrators to reboot the system first. |
Deactivate Wireless Network Interfaces
| Rule ID | deactivate_wireless_interfaces |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), AC-18(a), AC-18(d), AC-18(3), CM-7, 85, Test attestation on 20121025 by DS |
| Description | Deactivating wireless network interfaces should prevent
normal usage of the wireless capability.
$ ifconfig -aAdditionally, 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: $ iwconfigAfter identifying any wireless interfaces (which may have names like wlan0, ath0, wifi0, em1 or
eth0), deactivate the interface with the command:
$ sudo ifdown interfaceThese changes will only last until the next reboot. To disable the interface for future boots, remove the appropriate interface file from /etc/sysconfig/network-scripts:
$ sudo rm /etc/sysconfig/network-scripts/ifcfg-interface |
| Rationale | 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. |
Disable Bluetooth Service
| Rule ID | service_bluetooth_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), AC-18(a), AC-18(d), AC-18(3), CM-7, 85, 1551, Test attestation on 20121025 by DS |
| Description |
The $ sudo systemctl disable bluetooth $ sudo service bluetooth stop |
| Rationale | Disabling the |
Disable Bluetooth Kernel Modules
| Rule ID | kernel_module_bluetooth_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), AC-18(a), AC-18(d), AC-18(3), CM-7, 85, 1551, Test attestation on 20141031 by JL |
| Description | The kernel's module loading system can be configured to prevent
loading of the Bluetooth module. Add the following to
the appropriate install bluetooth /bin/true |
| Rationale | If Bluetooth functionality must be disabled, preventing the kernel from loading the kernel module provides an additional safeguard against its activation. |
Disable IPv6 Networking Support Automatic Loading
| Rule ID | sysctl_kernel_ipv6_disable |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, 1551, Test attestation on 20121024 by DS |
| Description | To disable support for ( net.ipv6.conf.all.disable_ipv6 = 1This disables IPv6 on all network interfaces as other services and system functionality require the IPv6 stack loaded to work. |
| Rationale | Any unnecessary network stacks - including IPv6 - should be disabled, to reduce the vulnerability to exploitation. |
Disable Interface Usage of IPv6
| Rule ID | network_ipv6_disable_interfaces |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | To disable interface usage of IPv6, add or correct the following lines in NETWORKING_IPV6=no IPV6INIT=no |
Disable Support for RPC IPv6
| Rule ID | network_ipv6_disable_rpc |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | RPC services for NFSv4 try to load transport modules for
udp6 tpi_clts v inet6 udp - - tcp6 tpi_cots_ord v inet6 tcp - - |
Disable Accepting IPv6 Router Advertisements
| Rule ID | sysctl_net_ipv6_conf_default_accept_ra |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv6.conf.default.accept_ra=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv6.conf.default.accept_ra = 0 |
| Rationale | An illicit router advertisement message could result in a man-in-the-middle attack. |
Disable Accepting IPv6 Redirects
| Rule ID | sysctl_net_ipv6_conf_default_accept_redirects |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
To set the runtime status of the $ sudo sysctl -w net.ipv6.conf.default.accept_redirects=0If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv6.conf.default.accept_redirects = 0 |
| Rationale | An illicit ICMP redirect message could result in a man-in-the-middle attack. |
Manually Assign Global IPv6 Address
| Rule ID | network_ipv6_static_address |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf |
| Description | To manually assign an IP address for an interface, edit the
file IPV6ADDR=2001:0DB8::ABCD/64Manually 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. |
Use Privacy Extensions for Address
| Rule ID | network_ipv6_privacy_extensions |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf |
| Description | To introduce randomness into the automatic generation of IPv6
addresses, add or correct the following line in
IPV6_PRIVACY=rfc3041Automatically-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. |
Manually Assign IPv6 Router Address
| Rule ID | network_ipv6_default_gateway |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf |
| Description | Edit the file
IPV6_DEFAULTGW=2001:0DB8::0001Router addresses should be manually set and not accepted via any auto-configuration or router advertisement. |
Verify firewalld Enabled
| Rule ID | service_firewalld_enabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The $ sudo systemctl enable firewalld |
| Rationale |
The dynamic firewall daemon |
Verify ip6tables Enabled if Using IPv6
| Rule ID | service_ip6tables_enabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-4, CA-3(c), CM-7, 32, 66, 1115, 1118, 1092, 1117, 1098, 1100, 1097, 1414, Test attestation on 20121024 by DS |
| Description |
The $ sudo systemctl enable ip6tables |
| Rationale | The |
Set Default ip6tables Policy for Incoming Packets
| Rule ID | set_ip6tables_default_rule |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | To set the default policy to DROP (instead of ACCEPT) for
the built-in INPUT chain which processes incoming packets,
add or correct the following line in
:INPUT DROP [0:0]If changes were required, reload the ip6tables rules: $ sudo service ip6tables reload |
| Rationale | In |
Verify iptables Enabled
| Rule ID | service_iptables_enabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-4, CA-3(c), CM-7, 32, 66, 1115, 1118, 1092, 1117, 1098, 1100, 1097, 1414, Test attestation on 20140921 by JL |
| Description |
The $ sudo systemctl enable iptables |
| Rationale |
The |
Set Default iptables Policy for Incoming Packets
| Rule ID | set_iptables_default_rule |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | To set the default policy to DROP (instead of ACCEPT) for
the built-in INPUT chain which processes incoming packets,
add or correct the following line in
:INPUT DROP [0:0] |
| Rationale | In |
Set Default iptables Policy for Forwarded Packets
| Rule ID | set_iptables_default_rule_forward |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | To set the default policy to DROP (instead of ACCEPT) for
the built-in FORWARD chain which processes packets that will be forwarded from
one interface to another,
add or correct the following line in
:FORWARD DROP [0:0] |
| Rationale | In |
Disable DCCP Support
| Rule ID | kernel_module_dccp_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26828-4 references: CM-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description |
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 install dccp /bin/true |
| Rationale | Disabling DCCP protects the system against exploitation of any flaws in its implementation. |
Disable SCTP Support
| Rule ID | kernel_module_sctp_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27106-4 references: CM-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description |
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 install sctp /bin/true |
| Rationale | Disabling SCTP protects the system against exploitation of any flaws in its implementation. |
Disable RDS Support
| Rule ID | kernel_module_rds_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, 382, Test attestation on 20121024 by DS |
| Description |
The Reliable Datagram Sockets (RDS) protocol is a transport
layer protocol designed to provide reliable high- bandwidth,
low-latency communications between nodes in a cluster.
To configure the system to prevent the install rds /bin/true |
| Rationale | Disabling RDS protects the system against exploitation of any flaws in its implementation. |
Disable TIPC Support
| Rule ID | kernel_module_tipc_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, 382, Test attestation on 20121024 by DS |
| Description |
The Transparent Inter-Process Communication (TIPC) protocol
is designed to provide communications between nodes in a
cluster.
To configure the system to prevent the install tipc /bin/true |
| Rationale | Disabling TIPC protects the system against exploitation of any flaws in its implementation. |
Install libreswan Package
| Rule ID | package_libreswan_installed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The Libreswan package provides an implementation of IPsec
and IKE, which permits the creation of secure tunnels over
untrusted networks.
The $ sudo yum install libreswan |
| Rationale | 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. |
Disable Zeroconf Networking
| Rule ID | network_disable_zeroconf |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | 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 NOZEROCONF=yes |
| Rationale | 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. |
Ensure System is Not Acting as a Network Sniffer
| Rule ID | network_sniffer_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The system should not be acting as a network sniffer, which can capture all traffic on the network to which it is connected. Run the following to determine if any interface is running in promiscuous mode: $ ip link | grep PROMISC |
| Rationale | If any results are returned, then a sniffing process (such as tcpdump or Wireshark) is likely to be using the interface and this should be investigated. |
Ensure Log Files Are Owned By Appropriate User
| Rule ID | userowner_rsyslog_files |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-6, 1314, Test attestation on 20121024 by DS |
| Description | The owner of all log files written by
$ ls -l LOGFILEIf the owner is not root, run the following command to
correct this:
$ sudo chown root LOGFILE |
| Rationale | 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. |
Ensure Log Files Are Owned By Appropriate Group
| Rule ID | groupowner_rsyslog_files |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-6, 1314, Test attestation on 20121024 by DS |
| Description | The group-owner of all log files written by
$ ls -l LOGFILEIf the owner is not root, run the following command to
correct this:
$ sudo chgrp root LOGFILE |
| Rationale | 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. |
Ensure Logrotate Runs Periodically
| Rule ID | ensure_logrotate_activated |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The # rotate log files frequency daily |
| Rationale | 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. |
Configure Logwatch HostLimit Line
| Rule ID | configure_logwatch_hostlimit |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | On a central logserver, you want Logwatch to summarize all syslog entries, including those which did not originate
on the logserver itself. The HostLimit = no |
Configure Logwatch SplitHosts Line
| Rule ID | configure_logwatch_splithosts |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
If SplitHosts = yes |
Ensure rsyslog is Installed
| Rule ID | package_rsyslog_installed |
| Result | pass |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AU-9(2), 1311, 1312, Test attestation on 20121024 by DS |
| Description |
Rsyslog is installed by default.
The $ sudo yum install rsyslog |
| Rationale | The rsyslog package provides the rsyslog daemon, which provides system logging services. |
Enable rsyslog Service
| Rule ID | service_rsyslog_enabled |
| Result | pass |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AU-12, 1557, 1312, 1311, Test attestation on 20121024 by DS |
| Description | The $ sudo systemctl enable rsyslog |
| Rationale | The |
Disable Logwatch on Clients if a Logserver Exists
| Rule ID | disable_logwatch_for_logserver |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Does your site have a central logserver which has been configured to report on logs received from all systems? If so: $ sudo rm /etc/cron.daily/0logwatchIf 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. |
Configure auditd Number of Logs Retained
| Rule ID | configure_auditd_num_logs |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AU-1(b), AU-11, IR-5, Test attestation on 20121024 by DS |
| Description | Determine how many log files
num_logs = NUMLOGSSet the value to 5 for general-purpose systems. Note that values less than 2 result in no log rotation. |
| Rationale | 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. |
Configure auditd Max Log File Size
| Rule ID | configure_auditd_max_log_file |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AU-1(b), AU-11, IR-5, Test attestation on 20121024 by DS |
| Description | Determine the amount of audit data (in megabytes)
which should be retained in each log file. Edit the file
max_log_file = STOREMBSet the value to 6 (MB) or higher for general-purpose systems.
Larger values, of course,
support retention of even more audit data. |
| Rationale | 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. |
Configure auditd max_log_file_action Upon Reaching Maximum Log Size
| Rule ID | configure_auditd_max_log_file_action |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AU-1(b), AU-4, AU-11, IR-5, Test attestation on 20121024 by DS |
| Description | 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 max_log_file_action = ACTIONPossible values for ACTION are described in the auditd.conf man
page. These include:
ACTION to rotate to ensure log rotation
occurs. This is the default. The setting is case-insensitive.
|
| Rationale | Automatically rotating logs (by setting this to |
Configure auditd space_left Action on Low Disk Space
| Rule ID | auditd_data_retention_space_left_action |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AU-1(b), AU-4, AU-5(b), IR-5, 140, 143, Test attestation on 20121024 by DS |
| Description | The space_left_action = ACTIONPossible values for ACTION are described in the auditd.conf man page.
These include:
email (instead of the default,
which is suspend) as it is more likely to get prompt attention. Acceptable values
also include suspend, single, and halt.
|
| Rationale | Notifying administrators of an impending disk space problem may allow them to take corrective action prior to any disruption. |
Configure auditd admin_space_left Action on Low Disk Space
| Rule ID | auditd_data_retention_admin_space_left_action |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AU-1(b), AU-4, AU-5(b), IR-5, 140, 1343, Test attestation on 20121024 by DS |
| Description | The admin_space_left_action = ACTIONSet this value to single to cause the system to switch to single user
mode for corrective action. Acceptable values also include suspend and
halt. For certain systems, the need for availability
outweighs the need to log all actions, and a different setting should be
determined. Details regarding all possible values for ACTION are described in the
auditd.conf man page.
|
| Rationale | 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. |
Configure auditd mail_acct Action on Low Disk Space
| Rule ID | auditd_data_retention_action_mail_acct |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The action_mail_acct = root |
| Rationale | Email sent to the root account is typically aliased to the administrators of the system, who can take appropriate action. |
Configure auditd to use audispd plugin
| Rule ID | configure_auditd_audispd |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | To configure the $ sudo service auditd restart |
| Rationale | The auditd service does not include the ability to send audit records to a centralized server for management directly. It does, however, include an audit event multiplexor plugin (audispd) to pass audit records to the local syslog server |
Record attempts to alter time through adjtimex
| Rule ID | audit_rules_time_adjtimex |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 1487, 169 |
| Description | If the -a always,exit -F arch=b32 -S adjtimex -k audit_time_rulesIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S adjtimex -k audit_time_rulesIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S adjtimex -k audit_time_rulesIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S adjtimex -k audit_time_rulesThe -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined syscalls: -a always,exit -F arch=b64 -S adjtimex -S settimeofday -S clock_settime -k audit_time_rules |
| Rationale | 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. |
Record attempts to alter time through settimeofday
| Rule ID | audit_rules_time_settimeofday |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 1487, 169 |
| Description | If the -a always,exit -F arch=b32 -S settimeofday -k audit_time_rulesIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S settimeofday -k audit_time_rulesIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S settimeofday -k audit_time_rulesIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S settimeofday -k audit_time_rulesThe -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined syscalls: -a always,exit -F arch=b64 -S adjtimex -S settimeofday -S clock_settime -k audit_time_rules |
| Rationale | 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. |
Record Attempts to Alter Time Through stime
| Rule ID | audit_rules_time_stime |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 1487, 169 |
| Description | If the -a always,exit -F arch=b32 -S stime -k audit_time_rulesSince the 64 bit version of the "stime" system call is not defined in the audit lookup table, the corresponding "-F arch=b64" form of this rule is not expected to be defined on 64 bit systems (the aforementioned "-F arch=b32" stime rule form itself is sufficient for both 32 bit and 64 bit systems). If the auditd daemon is configured to use the auditctl utility to
read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file for both 32 bit and 64 bit systems:
-a always,exit -F arch=b32 -S stime -k audit_time_rulesSince the 64 bit version of the "stime" system call is not defined in the audit lookup table, the corresponding "-F arch=b64" form of this rule is not expected to be defined on 64 bit systems (the aforementioned "-F arch=b32" stime rule form itself is sufficient for both 32 bit and 64 bit systems). The -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined system calls: -a always,exit -F arch=b64 -S adjtimex -S settimeofday -S clock_settime -k audit_time_rules |
| Rationale | 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. |
Record Attempts to Alter Time Through clock_settime
| Rule ID | audit_rules_time_clock_settime |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 1487, 169 |
| Description | If the -a always,exit -F arch=b32 -S clock_settime -k audit_time_rulesIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S clock_settime -k audit_time_rulesIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S clock_settime -k audit_time_rulesIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S clock_settime -k audit_time_rulesThe -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined syscalls: -a always,exit -F arch=b64 -S adjtimex -S settimeofday -S clock_settime -k audit_time_rules |
| Rationale | 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. |
Record Attempts to Alter the localtime File
| Rule ID | audit_rules_time_watch_localtime |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(b), IR-5, 1487, 169 |
| Description | If the -w /etc/localtime -p wa -k audit_time_rulesIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-w /etc/localtime -p wa -k audit_time_rulesThe -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. |
| Rationale | 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. |
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - chmod
| Rule ID | audit_rules_dac_modification_chmod |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - chown
| Rule ID | audit_rules_dac_modification_chown |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - fchmod
| Rule ID | audit_rules_dac_modification_fchmod |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - fchmodat
| Rule ID | audit_rules_dac_modification_fchmodat |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - fchown
| Rule ID | audit_rules_dac_modification_fchown |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - fchownat
| Rule ID | audit_rules_dac_modification_fchownat |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - fremovexattr
| Rule ID | audit_rules_dac_modification_fremovexattr |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - fsetxattr
| Rule ID | audit_rules_dac_modification_fsetxattr |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - lchown
| Rule ID | audit_rules_dac_modification_lchown |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - lremovexattr
| Rule ID | audit_rules_dac_modification_lremovexattr |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - lsetxattr
| Rule ID | audit_rules_dac_modification_lsetxattr |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - removexattr
| Rule ID | audit_rules_dac_modification_removexattr |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify the System's Discretionary Access Controls - setxattr
| Rule ID | audit_rules_dac_modification_setxattr |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect file permission
changes for all users and root. If the -a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_modIf the system is 64 bit then also add the following line: -a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod |
| Rationale | 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. |
| Warnings | warning
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.
|
Remediation script: | |
Record Events that Modify User/Group Information
| Rule ID | audit_rules_usergroup_modification |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27192-4 references: AC-2(4), AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 18, 172, 1403, 1404, 1405, 1684, 1683, 1685, 1686, 476, 239 |
| Description | If the -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_modificationIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file, in order to capture events that modify
account changes:
-w /etc/group -p wa -k audit_rules_usergroup_modification -w /etc/passwd -p wa -k audit_rules_usergroup_modification -w /etc/gshadow -p wa -k audit_rules_usergroup_modification -w /etc/shadow -p wa -k audit_rules_usergroup_modification -w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification |
| Rationale | 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. |
Remediation script: | |
Record Events that Modify the System's Network Environment
| Rule ID | audit_rules_networkconfig_modification |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5 |
| Description | If the -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_modificationIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S sethostname -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 |
| Rationale | The network environment should not be modified by anything other than administrator action. Any change to network parameters should be audited. |
Remediation script: | |
System Audit Logs Must Be Owned By Root
| Rule ID | audit_logs_rootowner |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-6, AU-1(b), AU-9, IR-5, 166, Test attestation on 20121024 by DS |
| Description |
To properly set the owner of $ sudo chown root /var/log |
| Rationale | Failure to give ownership of the audit log files to root allows the designated owner, and unauthorized users, potential access to sensitive information. |
Record Events that Modify the System's Mandatory Access Controls
| Rule ID | audit_rules_mac_modification |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5 |
| Description | If the -w /etc/selinux/ -p wa -k MAC-policyIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-w /etc/selinux/ -p wa -k MAC-policy |
| Rationale | 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. |
Remediation script: | |
Record Attempts to Alter Logon and Logout Events
| Rule ID | audit_rules_login_events |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27204-7 |
| Description | The audit system already collects login information for all users
and root. If the -w /var/log/faillog -p wa -k logins -w /var/log/lastlog -p wa -k loginsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file in order to watch for unattempted manual
edits of files involved in storing logon events:
-w /var/log/faillog -p wa -k logins -w /var/log/lastlog -p wa -k logins |
| Rationale | Manual editing of these files may indicate nefarious activity, such as an attacker attempting to remove evidence of an intrusion. |
Record Attempts to Alter Process and Session Initiation Information
| Rule ID | audit_rules_session_events |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27301-1 references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5 |
| Description | The audit system already collects process information for all
users and root. If the -w /var/run/utmp -p wa -k session -w /var/log/btmp -p wa -k session -w /var/log/wtmp -p wa -k sessionIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file in order to watch for attempted manual
edits of files involved in storing such process information:
-w /var/run/utmp -p wa -k session -w /var/log/btmp -p wa -k session -w /var/log/wtmp -p wa -k session |
| Rationale | Manual editing of these files may indicate nefarious activity, such as an attacker attempting to remove evidence of an intrusion. |
Ensure auditd Collects Unauthorized Access Attempts to Files (unsuccessful)
| Rule ID | audit_rules_unsuccessful_file_modification |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126 |
| Description | At a minimum the audit system should collect unauthorized file
accesses for all users and root. If the -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>=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>=1000 -F auid!=4294967295 -k accessIf the system is 64 bit then also add the following lines: -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>=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>=1000 -F auid!=4294967295 -k accessIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following lines to
/etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EACCES -F auid>=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>=1000 -F auid!=4294967295 -k accessIf the system is 64 bit then also add the following lines: -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>=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>=1000 -F auid!=4294967295 -k access |
| Rationale | 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. |
Remediation script: | |
Ensure auditd Collects Information on the Use of Privileged Commands
| Rule ID | audit_rules_privileged_commands |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-2(4), AU-12(a), AU-12(c), IR-5, 40, Test attestation on 20121024 by DS |
| Description | At a minimum the audit system should collect the execution of privileged commands for all users and root. To find the relevant setuid / setgid programs, run the following command for each local partition PART: $ sudo find PART -xdev -type f -perm -4000 -o -type f -perm -2000 2>/dev/nullIf the auditd daemon is configured to use the augenrules
program to read audit rules during daemon startup (the default), add a line of
the following form to a file with suffix .rules in the directory
/etc/audit/rules.d for each setuid / setgid program on the system,
replacing the SETUID_PROG_PATH part with the full path of that setuid /
setgid program in the list:
-a always,exit -F path=SETUID_PROG_PATH -F perm=x -F auid>=1000 -F auid!=4294967295 -k privilegedIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add a line of the following
form to /etc/audit/audit.rules for each setuid / setgid program on the
system, replacing the SETUID_PROG_PATH part with the full path of that
setuid / setgid program in the list:
-a always,exit -F path=SETUID_PROG_PATH -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged |
| Rationale | 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. |
Ensure auditd Collects Information on Exporting to Media (successful)
| Rule ID | audit_rules_media_export |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126, Test attestation on 20121024 by DS |
| Description | At a minimum the audit system should collect media exportation
events for all users and root. If the -a always,exit -F arch=ARCH -S mount -F auid>=1000 -F auid!=4294967295 -k exportIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S mount -F auid>=1000 -F auid!=4294967295 -k export |
| Rationale | 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. |
Remediation script: | |
Ensure auditd Collects File Deletion Events by User
| Rule ID | audit_rules_file_deletion_events |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27206-2 references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 172, 468 |
| Description | At a minimum the audit system should collect file deletion events
for all users and root. If the -a always,exit -F arch=ARCH -S rmdir -S unlink -S unlinkat -S rename -S renameat -F auid>=1000 -F auid!=4294967295 -k deleteIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file, setting ARCH to either b32 or b64 as
appropriate for your system:
-a always,exit -F arch=ARCH -S rmdir -S unlink -S unlinkat -S rename -S renameat -F auid>=1000 -F auid!=4294967295 -k delete |
| Rationale | 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. |
Remediation script: | |
Ensure auditd Collects System Administrator Actions
| Rule ID | audit_rules_sysadmin_actions |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-2(7)(b), AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126, Test attestation on 20121024 by DS |
| Description | At a minimum the audit system should collect administrator actions
for all users and root. If the -w /etc/sudoers -p wa -k actionsIf the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file:
-w /etc/sudoers -p wa -k actions |
| Rationale | 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. |
Remediation script: | |
Ensure auditd Collects Information on Kernel Module Loading and Unloading
| Rule ID | audit_rules_kernel_module_loading |
| Result | fail |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27129-6 references: AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 172, 477 |
| Description | If the -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=ARCH -S init_module -S delete_module -k modulesIf the auditd daemon is configured to use the auditctl utility to read audit
rules during daemon startup, add the following lines to /etc/audit/audit.rules file
in order to capture kernel module loading and unloading events, setting ARCH to either b32 or
b64 as appropriate for your system:
-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=ARCH -S init_module -S delete_module -k modules |
| Rationale | 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. |
Remediation script: | |
Make the auditd Configuration Immutable
| Rule ID | audit_rules_immutable |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27097-5 |
| Description | If the -e 2If the auditd daemon is configured to use the auditctl
utility to read audit rules during daemon startup, add the following line to
/etc/audit/audit.rules file in order to make the auditd configuration
immutable:
-e 2With this setting, a reboot will be required to change any audit rules. |
| Rationale | 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 |
Enable auditd Service
| Rule ID | service_auditd_enabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(1), AU-1(b), AU-10, AU-12(a), AU-12(c), IR-5, 347, 157, 172, 880, 1353, 1462, 1487, 1115, 1454, 067, 158, 831, 1190, 1312, 1263, 130, 120, 1589, Test attestation on 20121024 by DS |
| Description | The $ sudo systemctl enable auditd |
| Rationale | Ensuring the |
Enable Auditing for Processes Which Start Prior to the Audit Daemon
| Rule ID | bootloader_audit_argument |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(1), AU-14(1), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-10, IR-5, 1464, 130 |
| Description | To ensure all processes can be audited, even
those which start prior to the audit daemon, add the argument
kernel /vmlinuz-version ro vga=ext root=/dev/VolGroup00/LogVol00 rhgb quiet audit=1 |
| Rationale |
Each process on the system carries an "auditable" flag which
indicates whether its activities can be audited. Although |
Disable xinetd Service
| Rule ID | disable_xinetd |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, 305, Test attestation on 20121026 by DS |
| Description |
The $ sudo systemctl disable xinetd |
| Rationale | 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. |
Uninstall xinetd Package
| Rule ID | uninstall_xinetd |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, 305, Test attestation on 20121026 by DS |
| Description | The $ sudo yum erase xinetd |
| Rationale |
Removing the |
Disable telnet Service
| Rule ID | service_telnetd_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-27158-5 references: AC-17(8), CM-7, IA-5(1)(c), http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20140922 by JL |
| Description |
The
# 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
}
Then the activation of the telnet service on system boot can be disabled
via the following command:
# systemctl disable telnet.socket |
| Rationale | 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. |
Uninstall telnet-server Package
| Rule ID | uninstall_telnet_server |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-27165-0 references: AC-17(8), CM-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS |
| Description | The $ sudo yum erase telnet-server |
| Rationale |
Removing the |
Remove telnet Clients
| Rule ID | package_telnet_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27039-7 |
| Description | The telnet client allows users to start connections to other systems via the telnet protocol. |
| Rationale | The |
Uninstall rsh-server Package
| Rule ID | package_rsh-server_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, 305, 381, Test attestation on 20121026 by DS |
| Description | The $ sudo yum erase rsh-server |
| Rationale | The |
Disable rexec Service
| Rule ID | service_rexec_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, 68, 1436, Test attestation on 20121026 by DS |
| Description | The $ sudo systemctl disable rexec |
| Rationale | 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. |
Disable rsh Service
| Rule ID | service_rsh_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, IA-5(1)(c), 68, 1436, Test attestation on 20121026 by DS |
| Description | The $ sudo systemctl disable rsh |
| Rationale | 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. |
Uninstal rsh Package
| Rule ID | package_rsh_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE- references: Test attestation on 20140530 by JL |
| Description | The |
| Rationale | 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 |
Disable rlogin Service
| Rule ID | service_rlogin_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, IA-5(1)(c), 1436, Test attestation on 20121026 by DS |
| Description | The $ sudo systemctl disable rlogin |
| Rationale | 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. |
Remove Rsh Trust Files
| Rule ID | no_rsh_trust_files |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, 1436, Test attestation on 20121026 by DS |
| Description | The files $ sudo rm /etc/hosts.equiv $ rm ~/.rhosts |
| Rationale | Trust files are convenient, but when used in conjunction with the R-services, they can allow unauthenticated access to a system. |
Uninstall ypserv Package
| Rule ID | uninstall_ypserv |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, 305, 381, Test attestation on 20121026 by DS |
| Description | The $ sudo yum erase ypserv |
| Rationale | Removing the |
Disable ypbind Service
| Rule ID | disable_ypbind |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, 305, Test attestation on 20121026 by DS |
| Description | The $ sudo systemctl disable ypbind |
| Rationale |
Disabling the |
Remove NIS Client
| Rule ID | package_ypbind_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE- |
| Description | 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 ( |
| Rationale | 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. |
Disable tftp Service
| Rule ID | service_tftp_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, 1436, Test attestation on 20121026 by DS |
| Description | The $ sudo systemctl disable tftp |
| Rationale |
Disabling the |
Uninstall tftp-server Package
| Rule ID | uninstall_tftp-server |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, 305, Test attestation on 20121026 by DS |
| Description |
The $ sudo yum erase tftp-server |
| Rationale |
Removing the |
Remove tftp
| Rule ID | package_tftp_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE- |
| Description | 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
|
| Rationale | It is recommended that TFTP be remvoed, unless there is a specific need for TFTP (such as a boot server). In that case, use extreme caution when configuring the services. |
Ensure tftp Daemon Uses Secure Mode
| Rule ID | tftpd_uses_secure_mode |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | If running the server_args = -s /var/lib/tftpboot |
| Rationale | Using the |
Uninstall talk-server Package
| Rule ID | uninstall_talk-server |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE- references: Test attestation on 20140625 by JL |
| Description |
The $ sudo yum erase talk-server |
| Rationale |
The talk software presents a security risk as it uses unencrypted protocols
for communications. Removing the |
Uninstall talk Package
| Rule ID | package_talk_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE- references: Test attestation on 20140625 by JL |
| Description | The |
| Rationale |
The talk software presents a security risk as it uses unencrypted protocols
for communications. Removing the |
Disable Automatic Bug Reporting Tool (abrtd)
| Rule ID | service_abrtd_disabled |
| Result | pass |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-26872-2 references: AC-17(8), CM-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20140921 by JL |
| Description | The Automatic Bug Reporting Tool ( $ sudo systemctl disable abrtd |
| Rationale | 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. |
Disable Advanced Configuration and Power Interface (acpid)
| Rule ID | service_acpid_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | The Advanced Configuration and Power Interface Daemon ( $ sudo systemctl disable acpid |
| Rationale | 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. |
Disable Certmonger Service (certmonger)
| Rule ID | service_certmonger_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | 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 $ sudo systemctl disable certmonger |
| Rationale | 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. |
Disable Control Group Config (cgconfig)
| Rule ID | service_cgconfig_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | 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 $ sudo systemctl disable cgconfig |
| Rationale | Unless control groups are used to manage system resources, running the cgconfig service is not necessary. |
Disable Control Group Rules Engine (cgred)
| Rule ID | service_cgred_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | The $ sudo systemctl disable cgred |
| Rationale | Unless control groups are used to manage system resources, running the cgred service service is not necessary. |
Disable CPU Speed (cpuspeed)
| Rule ID | service_cpuspeed_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | The $ sudo systemctl disable cpuspeed |
| Rationale | The |
Enable IRQ Balance (irqbalance)
| Rule ID | service_irqbalance_enabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | The $ sudo systemctl enable irqbalance |
| Rationale | In an environment with multiple processors (now common), the irqbalance service provides potential speedups for handling interrupt requests. |
Disable KDump Kernel Crash Analyzer (kdump)
| Rule ID | service_kdump_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The $ sudo systemctl disable kdump |
| Rationale | Unless the system is used for kernel development or testing, there is little need to run the kdump service. |
Disable Software RAID Monitor (mdmonitor)
| Rule ID | service_mdmonitor_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | The $ sudo systemctl disable mdmonitor |
| Rationale | If software RAID monitoring is not required, there is no need to run this service. |
Disable Network Console (netconsole)
| Rule ID | service_netconsole_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The $ sudo systemctl disable netconsole |
| Rationale | The |
Disable ntpdate Service (ntpdate)
| Rule ID | service_ntpdate_disabled |
| Result | pass |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, 382, Test attestation on 20121024 by DS |
| Description | The $ sudo systemctl disable ntpdate |
| Rationale | The |
Disable Odd Job Daemon (oddjobd)
| Rule ID | service_oddjobd_disabled |
| Result | pass |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, 381, Test attestation on 20121024 by DS |
| Description | The $ sudo systemctl disable oddjobd |
| Rationale | The |
Disable Portreserve (portreserve)
| Rule ID | service_portreserve_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, Test attestation on 20121024 by DS |
| Description | The $ sudo systemctl disable portreserve |
| Rationale | The |
Enable Process Accounting (psacct)
| Rule ID | service_psacct_enabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AU-12, CM-7, Test attestation on 20121024 by DS |
| Description | The process accounting service, $ sudo systemctl enable psacct |
| Rationale | The |
Disable Apache Qpid (qpidd)
| Rule ID | service_qpidd_disabled |
| Result | pass |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The $ sudo systemctl disable qpidd |
| Rationale | 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 |
Disable Quota Netlink (quota_nld)
| Rule ID | service_quota_nld_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, Test attestation on 20121024 by DS |
| Description | The $ sudo systemctl disable quota_nld |
| Rationale | If disk quotas are enforced on the local system, then the
|
Disable Network Router Discovery Daemon (rdisc)
| Rule ID | service_rdisc_disabled |
| Result | pass |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), AC-4, CM-7, 382, Test attestation on 20121024 by DS |
| Description | The $ sudo systemctl disable rdisc |
| Rationale | 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. |
Disable Red Hat Network Service (rhnsd)
| Rule ID | service_rhnsd_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, 382, Test attestation on 20121024 by DS |
| Description | 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 $ sudo systemctl disable rhnsd |
| Rationale | 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 |
Disable Red Hat Subscription Manager Daemon (rhsmcertd)
| Rule ID | service_rhsmcertd_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, Test attestation on 20121024 by DS |
| Description | The Red Hat Subscription Manager (rhsmcertd) periodically checks for
changes in the entitlement certificates for a registered system and updates it
accordingly.
The $ sudo systemctl disable rhsmcertd |
| Rationale | The |
Disable Cyrus SASL Authentication Daemon (saslauthd)
| Rule ID | service_saslauthd_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-17(8), CM-7, Test attestation on 20121024 by DS |
| Description | The $ sudo systemctl disable saslauthd |
| Rationale | The |
Disable SMART Disk Monitoring Service (smartd)
| Rule ID | service_smartd_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, Test attestation on 20121024 by DS |
| Description | 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 $ sudo systemctl disable smartd |
| Rationale | 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. |
Disable System Statistics Reset Service (sysstat)
| Rule ID | service_sysstat_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, Test attestation on 20121024 by DS |
| Description | The $ sudo systemctl disable sysstat |
| Rationale | By default the |
Enable cron Service
| Rule ID | service_crond_enabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, Test attestation on 20121024 by DS |
| Description | The $ sudo systemctl enable crond |
| Rationale | Due to its usage for maintenance and security-supporting tasks, enabling the cron daemon is essential. |
Disable anacron Service
| Rule ID | disable_anacron |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | The $ sudo yum erase cronie-anacron |
| Rationale |
The |
Disable At Service (atd)
| Rule ID | service_atd_disabled |
| Result | pass |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The $ sudo systemctl disable atd |
| Rationale |
The |
Allow Only SSH Protocol 2
| Rule ID | sshd_allow_only_protocol2 |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-27038-9 references: AC-17(7), IA-5(1)(c), http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | Only SSH protocol version 2 connections should be
permitted. The default setting in
Protocol 2 |
| Rationale | SSH protocol version 1 suffers from design flaws that result in security vulnerabilities and should not be used. |
Limit Users' SSH Access
| Rule ID | sshd_limit_user_access |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-3 |
| Description | 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
DenyUsers USER1 USER2Where USER1 and USER2 are valid user names.
|
| Rationale | Specifying which accounts are allowed SSH access into the system reduces the possibility of unauthorized access to the system. |
Set SSH Idle Timeout Interval
| Rule ID | sshd_set_idle_timeout |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-26611-4 references: AC-2(5), SA-8, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | SSH allows administrators to set an idle timeout
interval.
After this interval has passed, the idle user will be
automatically logged out.
ClientAliveInterval intervalThe timeout interval is given in seconds. To have a timeout of 15 minutes, set interval to 900. 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. |
| Rationale | Causing idle users to be automatically logged out guards against compromises one system leading trivially to compromises on another. |
Set SSH Client Alive Count
| Rule ID | sshd_set_keepalive |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-27066-0 references: AC-2(5), SA-8, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | To ensure the SSH idle timeout occurs precisely when the ClientAliveCountMax 0 |
| Rationale |
This ensures a user login will be terminated as soon as the |
Disable SSH Support for .rhosts Files
| Rule ID | sshd_disable_rhosts |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27035-5 references: AC-3, http://iase.disa.mil/stigs/cci/Pages/index.aspx |
| Description | SSH can emulate the behavior of the obsolete rsh
command in allowing users to enable insecure access to their
accounts via IgnoreRhosts yes |
| Rationale | SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. |
Disable Host-Based Authentication
| Rule ID | disable_host_auth |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26870-6 references: AC-3, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | SSH's cryptographic host-based authentication is
more secure than HostbasedAuthentication no |
| Rationale | SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. |
Disable SSH Root Login
| Rule ID | sshd_disable_root_login |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-26946-4 references: AC-3, AC-6(2), IA-2(1), http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | 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 PermitRootLogin no |
| Rationale | Permitting direct root login reduces auditable information about who ran privileged commands on the system and also allows direct attack attempts on root's password. |
Disable SSH Access via Empty Passwords
| Rule ID | sshd_disable_empty_passwords |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | high |
| Identifiers and References | identifiers: CCE-26864-9 references: AC-3, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | To explicitly disallow remote login from accounts with
empty passwords, add or correct the following line in
PermitEmptyPasswords noAny accounts with empty passwords should be disabled immediately, and PAM configuration should prevent users from being able to assign themselves empty passwords. |
| Rationale | 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. |
Do Not Allow SSH Environment Options
| Rule ID | sshd_do_not_permit_user_env |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-26974-6 references: http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | To ensure users are not able to present
environment options to the SSH daemon, add or correct the following line
in PermitUserEnvironment no |
| Rationale | SSH environment options potentially allow users to bypass access restriction in some configurations. |
Use Only Approved Ciphers
| Rule ID | sshd_use_approved_ciphers |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-27051-2 references: AC-3, AC-17(2), AU-10(5), IA-5(1)(c), IA-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS |
| Description | 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 Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbcThe man page sshd_config(5) contains a list of supported ciphers.
|
| Rationale | Approved algorithms should impart some level of confidence in their implementation. These are also required for compliance. |
Disable SSH Server If Possible (Unusual)
| Rule ID | ssh_server_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: Test attestation on 20121024 by DS |
| Description | The SSH server service, sshd, is commonly needed.
However, if it can be disabled, do so.
The $ sudo systemctl disable sshdThis is unusual, as SSH is a common method for encrypted and authenticated remote access. |
Remove SSH Server iptables Firewall exception (Unusual)
| Rule ID | ssh_server_iptables_exception |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | 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.
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPTThis is unusual, as SSH is a common method for encrypted and authenticated remote access. |
| Rationale | If inbound SSH connections are not expected, disallowing access to the SSH port will avoid possible exploitation of the port by an attacker. |
Disable X Windows Startup By Setting Default Target
| Rule ID | disable_xwindows_with_target |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AC-3, 366, Test attestation on 20121025 by DS |
| Description | Setting the system's default target to multi-user will prevent automatic startup of the X server. To do so, run: $ systemctl set-default multi-user.targetYou should see the following output: rm '/etc/systemd/system/default.target' ln -s '/usr/lib/systemd/system/multi-user.target' '/etc/systemd/system/default.target' |
| Rationale | Unnecessary services should be disabled to decrease the attack surface of the system. |
Remove the X Windows Package Group
| Rule ID | packagegroup_xwindows_remove |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: 366, Test attestation on 20121025 by DS |
| Description | Removing all packages which constitute the X Window System ensures users or malicious software cannot start X. To do so, run the following command: $ sudo yum groupremove "X Window System" |
| Rationale | Unnecessary packages should not be installed to decrease the attack surface of the system. |
Disable Avahi Server Software
| Rule ID | disable_avahi |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The $ sudo systemctl disable avahi-daemon |
| Rationale | 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. |
Serve Avahi Only via Required Protocol
| Rule ID | avahi_ip_only |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
If you are using only IPv4, edit use-ipv6=noSimilarly, if you are using only IPv6, disable IPv4 sockets with the line: use-ipv4=no |
Check Avahi Responses' TTL Field
| Rule ID | avahi_check_ttl |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
To make Avahi ignore packets unless the TTL field is 255, edit
check-response-ttl=yes |
| Rationale | 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. |
Prevent Other Programs from Using Avahi's Port
| Rule ID | avahi_prevent_port_sharing |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
To prevent other mDNS stacks from running, edit disallow-other-stacks=yes |
| Rationale | This helps ensure that only Avahi is responsible for mDNS traffic coming from that port on the system. |
Disable Avahi Publishing
| Rule ID | avahi_disable_publishing |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
To prevent other mDNS stacks from running, edit disallow-other-stacks=yes |
| Rationale | This helps ensure that only Avahi is responsible for mDNS traffic coming from that port on the system. |
Restrict Information Published by Avahi
| Rule ID | avahi_restrict_published_information |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
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 disable-user-service-publishing=yesImplement as many of the following lines as possible, to restrict the information published by Avahi. publish-addresses=no publish-hinfo=no publish-workstation=no publish-domain=noInspect the files in the directory /etc/avahi/services/. Unless there
is an operational need to publish information about each of these services,
delete the corresponding file.
|
| Rationale | 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. |
Disable Printer Browsing Entirely if Possible
| Rule ID | cups_disable_browsing |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | 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 Browsing Off |
| Rationale | 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. |
Disable Print Server Capabilities
| Rule ID | cups_disable_printserver |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | To prevent remote users from potentially connecting to and using locally configured printers, disable the CUPS print server sharing capabilities. To do so, limit how the server will listen for print jobs by removing the more generic port directive from /etc/cups/cupsd.conf: Port 631and replacing it with the Listen directive:
Listen localhost:631This will prevent remote users from printing to locally configured printers while still allowing local users on the machine to print normally. |
| Rationale | 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. |
Disable the CUPS Service
| Rule ID | service_cups_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
The $ sudo systemctl disable cups |
| Rationale | Turn off unneeded services to reduce attack surface. |
Disable DHCP Service
| Rule ID | disable_dhcp_server |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, 366, Test attestation on 20121024 by DS |
| Description | The $ sudo systemctl disable dhcpd |
| Rationale | 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. |
Uninstall DHCP Server Package
| Rule ID | uninstall_dhcp_server |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, 366, Test attestation on 20121024 by DS |
| Description | If the system does not need to act as a DHCP server,
the dhcp package can be uninstalled.
The $ sudo yum erase dhcp |
| Rationale | Removing the DHCP server ensures that it cannot be easily or accidentally reactivated and disrupt network operation. |
Do Not Use Dynamic DNS
| Rule ID | dhcp_server_disable_ddns |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | To prevent the DHCP server from receiving DNS information from
clients, edit ddns-update-style none; |
| Rationale | 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. |
| Warnings | warning
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). |
Deny Decline Messages
| Rule ID | dhcp_server_deny_decline |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | Edit deny declines; |
| Rationale | 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. |
Deny BOOTP Queries
| Rule ID | dhcp_server_deny_bootp |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | Unless your network needs to support older BOOTP clients, disable support for the bootp protocol by adding or correcting the global option: deny bootp; |
| Rationale | 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. |
Configure Logging
| Rule ID | dhcp_server_configure_logging |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf |
| Description | Ensure that the following line exists in
daemon.* /var/log/daemon.logConfigure logwatch or other log monitoring tools to summarize error conditions reported by the dhcpd process. |
| Rationale | 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 |
Disable DHCP Client
| Rule ID | disable_dhcp_client |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, 366, Test attestation on 20121024 by DS |
| Description |
For each interface on the system (e.g. eth0), edit
|
| Rationale | 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. |
Enable the NTP Daemon
| Rule ID | service_chronyd_or_ntpd_enabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AU-8(1), 160, Test attestation on 20121024 by DS |
| Description |
The $ sudo systemctl enable chronydNote: The chronyd daemon is enabled by default.
The ntpd service can be enabled with the following command:
$ sudo systemctl enable ntpdNote: The ntpd daemon is not enabled by default. Though as mentioned
in the previous sections in certain environments the ntpd daemon might
be preferred to be used rather than the chronyd one. Refer to:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html
for guidance which NTP daemon to choose depending on the environment used.
|
| Rationale | Enabling some of |
Specify a Remote NTP Server
| Rule ID | ntpd_specify_remote_server |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AU-8(1), 160, Test attestation on 20121024 by DS |
| Description | To specify a remote NTP server for time synchronization, edit
the file server ntpserverThis instructs the NTP software to contact that remote server to obtain time data. |
| Rationale | Synchronizing with an NTP server makes it possible to collate system logs from multiple sources or correlate computer events with real time events. |
Specify Additional Remote NTP Servers
| Rule ID | ntpd_specify_multiple_servers |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: AU-8(1) |
| Description | Additional NTP servers can be specified for time synchronization
in the file server ntpserver |
| Rationale | 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. |
Disable Postfix Network Listening
| Rule ID | postfix_network_listening_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, 382, Test attestation on 20121024 by DS |
| Description |
Edit the file inet_interfaces = localhost |
| Rationale |
This ensures |
Enable Postfix Service
| Rule ID | service_postfix_enabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: Test attestation on 20121024 by DS |
| Description | 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 $ sudo systemctl enable postfix |
| Rationale | Local mail delivery is essential to some system maintenance and notification tasks. |
Uninstall Sendmail Package
| Rule ID | package_sendmail_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, Test attestation on 20121024 by DS |
| Description | Sendmail is not the default mail transfer agent and is
not installed by default.
The $ sudo yum erase sendmail |
| Rationale | 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. |
Configure LDAP Client to Use TLS For All Transactions
| Rule ID | ldap_client_start_tls |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, 776, 778, 1453, Test attestation on 20121024 by DS |
| Description | Configure LDAP to enforce TLS use. First, edit the file
ssl start_tlsThen review the LDAP server and ensure TLS has been configured. |
| Rationale | The ssl directive specifies whether to use ssl or not. If not specified it will default to no. It should be set to start_tls rather than doing LDAP over SSL. |
Configure Certificate Directives for LDAP Use of TLS
| Rule ID | ldap_client_tls_cacertpath |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, 776, 778, 1453, Test attestation on 20121024 by DS |
| Description | Ensure a copy of a trusted CA certificate has been placed in
the file tls_cacertdir /etc/pki/tls/CAor tls_cacertfile /etc/pki/tls/CA/cacert.pemThen review the LDAP server and ensure TLS has been configured. |
| Rationale | 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. |
Uninstall openldap-servers Package
| Rule ID | package_openldap-servers_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, 366, Test attestation on 20121024 by DS |
| Description | The $ sudo yum erase openldap-serversThe openldap-servers RPM is not installed by default on RHEL 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. |
| Rationale | 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. |
Disable Network File System Lock Service (nfslock)
| Rule ID | service_nfslock_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | 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 $ sudo systemctl disable nfslock |
Disable Secure RPC Client Service (rpcgssd)
| Rule ID | service_rpcgssd_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
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 $ sudo systemctl disable rpcgssd |
Disable RPC ID Mapping Service (rpcidmapd)
| Rule ID | service_rpcidmapd_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | 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 $ sudo systemctl disable rpcidmapd |
Disable Network File Systems (netfs)
| Rule ID | service_netfs_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The netfs script manages the boot-time mounting of several types
of networked filesystems, of which NFS and Samba are the most common. If these
filesystem types are not in use, the script can be disabled, protecting the
system somewhat against accidental or malicious changes to $ sudo systemctl disable netfs |
Configure lockd to use static TCP port
| Rule ID | nfs_fixed_lockd_tcp_port |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Configure the LOCKD_TCPPORT=lockd-portWhere lockd-port is a port which is not used by any other service on
your network.
|
| Rationale | Restrict service to always use a given port, so that firewalling can be done effectively. |
Configure lockd to use static UDP port
| Rule ID | nfs_fixed_lockd_udp_port |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Configure the LOCKD_UDPPORT=lockd-portWhere lockd-port is a port which is not used by any other service on
your network.
|
| Rationale | Restricting services to always use a given port enables firewalling to be done more effectively. |
Configure statd to use static port
| Rule ID | nfs_fixed_statd_port |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Configure the STATD_PORT=statd-portWhere statd-port is a port which is not used by any other service on your network.
|
| Rationale | Restricting services to always use a given port enables firewalling to be done more effectively. |
Configure mountd to use static port
| Rule ID | nfs_fixed_mountd_port |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Configure the MOUNTD_PORT=statd-portWhere mountd-port is a port which is not used by any other service on your network.
|
| Rationale | Restricting services to always use a given port enables firewalling to be done more effectively. |
Specify UID and GID for Anonymous NFS Connections
| Rule ID | nfs_no_anonymous |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | To specify the UID and GID for remote root users, edit the anonuid=Alternatively, functionally equivalent values of 60001, 65534, 65535 may be used. |
| Rationale | 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. |
Disable Network File System (nfs)
| Rule ID | service_nfs_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: Test attestation on 20121025 by DS |
| Description | 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 $ sudo systemctl disable nfs |
| Rationale | Unnecessary services should be disabled to decrease the attack surface of the system. |
Disable Secure RPC Server Service (rpcsvcgssd)
| Rule ID | service_rpcsvcgssd_disabled |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: Test attestation on 20121025 by DS |
| Description | 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 $ sudo systemctl disable rpcsvcgssd |
| Rationale | Unnecessary services should be disabled to decrease the attack surface of the system. |
Mount Remote Filesystems with nodev
| Rule ID | use_nodev_option_on_nfs_mounts |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7, MP-2, Test attestation on 20121025 by DS |
| Description |
Add the |
| Rationale | Legitimate device files should only exist in the /dev directory. NFS mounts should not present device files to users. |
Mount Remote Filesystems with nosuid
| Rule ID | use_nosuid_option_on_nfs_mounts |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: Test attestation on 20121025 by DS |
| Description |
Add the |
| Rationale | 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. |
Use Root-Squashing on All Exports
| Rule ID | use_root_squashing_all_exports |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | 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.
|
| Rationale | If the NFS server allows root access to local file systems from remote hosts, this access could be used to compromise the system. |
Restrict NFS Clients to Privileged Ports
| Rule ID | restrict_nfs_clients_to_privileged_ports |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | 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.
|
| Rationale | 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. |
Ensure Insecure File Locking is Not Allowed
| Rule ID | no_insecure_locks_exports |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: 764 |
| Description | 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
|
| Rationale | Allowing insecure file locking could allow for sensitive data to be viewed or edited by an unauthorized user. |
Disable DNS Server
| Rule ID | disable_dns_server |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The $ sudo systemctl disable named |
| Rationale | All network services involve some risk of compromise due to implementation flaws and should be disabled if possible. |
Uninstall bind Package
| Rule ID | uninstall_bind |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | To remove the $ sudo yum erase bind |
| Rationale | If there is no need to make DNS server software available, removing it provides a safeguard against its activation. |
Disable Zone Transfers from the Nameserver
| Rule ID | dns_server_disable_zone_transfers |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | 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 options {
allow-transfer { none; };
...
}
|
| Rationale | 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. |
Authenticate Zone Transfers
| Rule ID | dns_server_authenticate_zone_transfers |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | If it is necessary for a secondary nameserver to receive zone data via zone transfer from the primary server, follow the instructions here. Use dnssec-keygen to create a symmetric key file in the current directory: $ cd /tmp $ sudo dnssec-keygen -a HMAC-MD5 -b 128 -n HOST dns.example.com Kdns.example.com .+aaa +iiiiiThis output is the name of a file containing the new key. Read the file to find the base64-encoded key string: $ sudo cat Kdns.example.com .+NNN +MMMMM .key dns.example.com IN KEY 512 3 157 base64-key-stringAdd the directives to /etc/named.conf on the primary server:
key zone-transfer-key {
algorithm hmac-md5;
secret "base64-key-string ";
};
zone "example.com " IN {
type master;
allow-transfer { key zone-transfer-key; };
...
};
Add the directives below to /etc/named.conf on the secondary nameserver:
key zone-transfer-key {
algorithm hmac-md5;
secret "base64-key-string ";
};
server IP-OF-MASTER {
keys { zone-transfer-key; };
};
zone "example.com " IN {
type slave;
masters { IP-OF-MASTER ; };
...
};
|
| Rationale | 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. |
| Warnings | warning
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. |
Disable Dynamic Updates
| Rule ID | dns_server_disable_dynamic_updates |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Is there a mission-critical reason to enable the risky dynamic
update functionality? If not, edit zone "example.com " IN {
allow-update { none; };
...
};
|
| Rationale | 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. |
Disable vsftpd Service
| Rule ID | disable_vsftpd |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The $ sudo systemctl disable vsftpd |
| Rationale | 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. |
Uninstall vsftpd Package
| Rule ID | uninstall_vsftpd |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The $ sudo yum erase vsftpd |
| Rationale | Removing the vsftpd package decreases the risk of its accidental activation. |
Install vsftpd Package
| Rule ID | package_vsftpd_installed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description | If this machine must operate as an FTP server, install the $ sudo yum install vsftpd |
| Rationale | After RHEL 2.1, Red Hat switched from distributing wu-ftpd with RHEL to distributing vsftpd. For security and for consistency with future Red Hat releases, the use of vsftpd is recommended. |
Restrict Access to Anonymous Users if Possible
| Rule ID | ftp_restrict_to_anon |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Is there a mission-critical reason for users to transfer files to/from their own accounts using FTP, rather than using a secure protocol like SCP/SFTP? If not, edit the vsftpd configuration file. Add or correct the following configuration option: local_enable=NOIf non-anonymous FTP logins are necessary, follow the guidance in the remainder of this section to secure these logins as much as possible. |
| Rationale | 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. |
Enable Logging of All FTP Transactions
| Rule ID | ftp_log_transactions |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Add or correct the following configuration options within the xferlog_enable=YES xferlog_std_format=NO log_ftp_protocol=YES |
| Rationale | 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 |
| Warnings | warning
If verbose logging to vsftpd.log is done, sparse logging of downloads to /var/log/xferlog will not also occur. However, the information about what files were downloaded is included in the information logged to vsftpd.log |
Disable FTP Uploads if Possible
| Rule ID | ftp_disable_uploads |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Is there a mission-critical reason for users to upload files via FTP? If not, edit the vsftpd configuration file to add or correct the following configuration options: write_enable=NOIf FTP uploads are necessary, follow the guidance in the remainder of this section to secure these transactions as much as possible. |
| Rationale | 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. |
Place the FTP Home Directory on its Own Partition
| Rule ID | ftp_home_partition |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | 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. |
| Rationale | 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. |
Disable httpd Service
| Rule ID | disable_httpd |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
The $ sudo systemctl disable httpd |
| Rationale | Running web server software provides a network-based avenue of attack, and should be disabled if not needed. |
Uninstall httpd Package
| Rule ID | package_httpd_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
The $ sudo yum erase httpd |
| Rationale | If there is no need to make the web server software available, removing it provides a safeguard against its activation. |
Set httpd ServerTokens Directive to Prod
| Rule ID | httpd_servertokens_prod |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
ServerTokens Prod |
| Rationale | 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. |
Set httpd ServerSignature Directive to Off
| Rule ID | httpd_serversignature_off |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: CM-7 |
| Description |
ServerSignature Off |
| Rationale | 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. |
Disable HTTP Digest Authentication
| Rule ID | httpd_digest_authentication |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The #LoadModule auth_digest_module modules/mod_auth_digest.so |
| Rationale | Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
Disable HTTP mod_rewrite
| Rule ID | httpd_mod_rewrite |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The #LoadModule rewrite_module modules/mod_rewrite.so |
| Rationale | Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
Disable LDAP Support
| Rule ID | httpd_ldap_support |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The #LoadModule ldap_module modules/mod_ldap.so #LoadModule authnz_ldap_module modules/mod_authnz_ldap.soIf LDAP is to be used, SSL encryption should be used as well. |
| Rationale | Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
Disable Server Side Includes
| Rule ID | httpd_server_side_includes |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Server Side Includes provide a method of dynamically generating web pages through the insertion of server-side code. However, the technology is also deprecated and introduces significant security concerns. If this functionality is unnecessary, comment out the related module: #LoadModule include_module modules/mod_include.soIf there is a critical need for Server Side Includes, they should be enabled with the option IncludesNoExec to prevent arbitrary code execution. Additionally, user
supplied data should be encoded to prevent cross-site scripting vulnerabilities.
|
| Rationale | Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
Disable MIME Magic
| Rule ID | httpd_mime_magic |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The #LoadModule mime_magic_module modules/mod_mime_magic.so |
| Rationale | Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
Disable WebDAV (Distributed Authoring and Versioning)
| Rule ID | httpd_webdav |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | WebDAV is an extension of the HTTP protocol that provides distributed and collaborative access to web content. If its functionality is unnecessary, comment out the related modules: #LoadModule dav_module modules/mod_dav.so #LoadModule dav_fs_module modules/mod_dav_fs.soIf 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. |
| Rationale | Minimizing the number of loadable modules available to the web server, reduces risk by limiting the capabilities allowed by the web server. |
Disable Server Activity Status
| Rule ID | httpd_server_activity_status |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The #LoadModule status_module modules/mod_status.soIf 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. |
| Rationale | Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
Disable Web Server Configuration Display
| Rule ID | httpd_server_configuration_display |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The #LoadModule info_module modules/mod_info.soIf there is a critical need for this module, use the Location directive to provide
an access control list to restrict access to the information.
|
| Rationale | Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
Disable URL Correction on Misspelled Entries
| Rule ID | httpd_url_correction |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The #LoadModule speling_module modules/mod_speling.soThis functionality weakens server security by making site enumeration easier. |
| Rationale | Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
Disable Proxy Support
| Rule ID | httpd_proxy_support |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The #LoadModule proxy_module modules/mod_proxy.soIf proxy support is needed, load mod_proxy and the appropriate proxy protocol handler
module (one of mod_proxy_http, mod_proxy_ftp, or mod_proxy_connect). Additionally,
make certain that a server is secure before enabling proxying, as open proxy servers
are a security risk. mod_proxy_balancer enables load balancing, but requires that
mod status be enabled.
|
| Rationale | Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
Disable Cache Support
| Rule ID | httpd_cache_support |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The #LoadModule cache_module modules/mod_cache.soIf caching is required, it should not be enabled for any limited-access content. |
| Rationale | Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
Disable CGI Support
| Rule ID | httpd_cgi_support |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The #LoadModule cgi_module modules/mod_cgi.soIf the web server requires the use of CGI, enable mod_cgi.
|
| Rationale | Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server. |
Restrict Root Directory
| Rule ID | httpd_restrict_root_directory |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The <Directory / > Options None AllowOverride None Order allow,deny </Directory> |
| Rationale | The Web Server's root directory content should be protected from unauthorized access by web clients. |
Restrict Web Directory
| Rule ID | httpd_restrict_web_directory |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The default configuration for the web ( <Directory "/var/www/html"> # ... Options SymLinksIfOwnerMatch # ... </Directory> |
| Rationale | 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. |
Restrict Other Critical Directories
| Rule ID | httpd_restrict_critical_directories |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
All accessible web directories should be configured with similarly restrictive settings.
The |
| Rationale | 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. |
Limit Available Methods
| Rule ID | httpd_limit_available_methods |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
Web server methods are defined in section 9 of RFC 2616 (http://www.ietf.org/rfc/rfc2616.txt).
If a web server does not require the implementation of all available methods,
they should be disabled.
<Directory /var/www/html>
# ...
# Only allow specific methods (this command is case-sensitive!)
<LimitExcept GET POST>
Order allow,deny
</LimitExcept>
# ...
</Directory>
|
| Rationale | Minimizing the number of available methods to the web client reduces risk by limiting the capabilities allowed by the web server. |
Install mod_ssl
| Rule ID | httpd_install_mod_ssl |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
Install the $ sudo yum install mod_ssl |
| Rationale |
|
Install mod_security
| Rule ID | httpd_install_mod_security |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
Install the $ sudo yum install mod_security |
| Rationale |
|
Disable Dovecot Service
| Rule ID | disable_dovecot |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The $ sudo systemctl disable dovecot |
| Rationale | Running an IMAP or POP3 server provides a network-based avenue of attack, and should be disabled if not needed. |
Uninstall dovecot Package
| Rule ID | package_dovecot_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The $ sudo yum erase dovecot |
| Rationale | If there is no need to make the Dovecot software available, removing it provides a safeguard against its activation. |
Enable the SSL flag in /etc/dovecot.conf
| Rule ID | dovecot_enable_ssl |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | To allow clients to make encrypted connections the ssl = yes |
| Rationale | 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. |
Configure Dovecot to Use the SSL Certificate file
| Rule ID | dovecot_configure_ssl_cert |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | This option tells Dovecot where to find the the mail
server's SSL Certificate.
ssl_cert = </etc/pki/dovecot/certs/dovecot.pem |
| Rationale | 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. |
Configure Dovecot to Use the SSL Key file
| Rule ID | dovecot_configure_ssl_key |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | This option tells Dovecot where to find the the mail
server's SSL Key.
ssl_key = </etc/pki/dovecot/private/dovecot.pem |
| Rationale | 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. |
Disable Plaintext Authentication
| Rule ID | dovecot_disable_plaintext_auth |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | To prevent Dovecot from attempting plaintext
authentication of clients, edit disable_plaintext_auth = yes |
| Rationale | Using plain text authentication to the mail server could allow an attacker access to credentials by monitoring network traffic. |
Disable Samba
| Rule ID | disable_smb_server |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: 1436 |
| Description |
The $ sudo systemctl disable smb |
| Rationale | Running a Samba server provides a network-based avenue of attack, and should be disabled if not needed. |
Disable Root Access to SMB Shares
| Rule ID | smb_server_disable_root |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Administrators should not use administrator accounts to access Samba file and printer shares. Disable the root user and the wheel administrator group: [share] invalid users = root @wheelIf administrator accounts cannot be disabled, ensure that local machine passwords and Samba service passwords do not match. |
| Rationale |
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 |
Require Client SMB Packet Signing, if using smbclient
| Rule ID | require_smb_client_signing |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
To require samba clients running client signing = mandatoryRequiring samba clients such as smbclient to use packet
signing ensures they can
only communicate with servers that support packet signing.
|
| Rationale | Packet signing can prevent man-in-the-middle attacks which modify SMB packets in transit. |
Require Client SMB Packet Signing, if using mount.cifs
| Rule ID | require_smb_client_signing_mount.cifs |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | Require packet signing of clients who mount Samba
shares using the |
| Rationale | Packet signing can prevent man-in-the-middle attacks which modify SMB packets in transit. |
Disable Squid
| Rule ID | disable_squid |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The $ sudo systemctl disable squid |
| Rationale | Running proxy server software provides a network-based avenue of attack, and should be removed if not needed. |
Uninstall squid Package
| Rule ID | uninstall_squid |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The $ sudo yum erase squid |
| Rationale | If there is no need to make the proxy server software available, removing it provides a safeguard against its activation. |
Disable snmpd Service
| Rule ID | disable_snmpd |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
The $ sudo systemctl disable snmpd |
| Rationale | Running SNMP software provides a network-based avenue of attack, and should be disabled if not needed. |
Uninstall net-snmp Package
| Rule ID | package_net-snmp_removed |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description | The $ sudo yum erase net-snmp |
| Rationale | If there is no need to run SNMP server software, removing the package provides a safeguard against its activation. |
Configure SNMP Service to Use Only SNMPv3 or Newer
| Rule ID | snmpd_use_newer_protocol |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD |
| Description |
Edit $ sudo service snmpd restart |
| Rationale | Earlier versions of SNMP are considered insecure, as they potentially allow unauthorized access to detailed system management information. |
Ensure Default Password Is Not Used
| Rule ID | snmpd_not_default_password |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | medium |
| Identifiers and References | identifiers: CCE-RHEL7-CCE-TBD references: Test attestation on 20121214 by MAN |
| Description |
Edit $ sudo service snmpd restart |
| Rationale | Presence of the default SNMP password enables querying of different system aspects and could result in unauthorized knowledge of the system. |
Product Meets this Requirement
| Rule ID | met_inherently_generic |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | references: 42, 56, 206, 1084, 66, 85, 86, 185, 223, 171, 172, 1694, 770, 804, 162, 163, 164, 345, 346, 1096, 1111, 1291, 386, 156, 186, 1083, 1082, 1090, 804, 1127, 1128, 1129, 1248, 1265, 1314, 1362, 1368, 1310, 1311, 1328, 1399, 1400, 1404, 1405, 1427, 1499, 1632, 1693, 1665, 1674 |
| Description | This requirement is a permanent not a finding. No fix is required. |
| Rationale | Red Hat Enterprise Linux meets this requirement through design and implementation. |
Product Meets this Requirement
| Rule ID | met_inherently_auditing |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | |
| Description | This requirement is a permanent not a finding. No fix is required. |
| Rationale | The Red Hat Enterprise Linux audit system meets this requirement through design and implementation. |
Product Meets this Requirement
| Rule ID | met_inherently_nonselected |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | references: 34, 35, 99, 154, 226, 802, 872, 1086, 1087, 1089, 1091, 1424, 1426, 1428, 1209, 1214, 1237, 1269, 1338, 1425, 1670 |
| Description | This requirement is a permanent not a finding. No fix is required. |
| Rationale | Red Hat Enterprise Linux meets this requirement through design and implementation. |
Guidance Does Not Meet this Requirement Due to Impracticality or Scope
| Rule ID | unmet_nonfinding_nonselected_scope |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | references: 21, 25, 28, 29, 30, 165, 221, 354, 553, 779, 780, 781, 1009, 1094, 1123, 1124, 1125, 1132, 1135, 1140, 1141, 1142, 1143, 1145, 1147, 1148, 1166, 1339, 1340, 1341, 1350, 1356, 1373, 1374, 1383, 1391, 1392, 1395, 1662 |
| Description | This requirement is NA. No fix is required. |
| Rationale | The guidance does not meet this requirement. The requirement is impractical or out of scope. |
Implementation of the Requirement is Not Supported
| Rule ID | unmet_finding_nonselected |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | |
| Description | 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. |
| Rationale | RHEL7 does not support this requirement. |
Guidance Does Not Meet this Requirement Due to Impracticality or Scope
| Rule ID | unmet_nonfinding_scope |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | references: 15, 27, 218, 219, 371, 372, 535, 537, 539, 1682, 370, 37, 24, 1112, 1126, 1143, 1149, 1157, 1159, 1210, 1211, 1274, 1372, 1376, 1377, 1352, 1401, 1555, 1556, 1150 |
| Description | This requirement is NA. No fix is required. |
| Rationale | The guidance does not meet this requirement. The requirement is impractical or out of scope. |
A process for prompt installation of OS updates must exist.
| Rule ID | update_process |
| Result | notselected |
| Time | 2015-07-17T10:50:20 |
| Severity | low |
| Identifiers and References | references: 1232 |
| Description | 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. |
| Rationale | This is a manual inquiry about update procedure. |