Guide to the Secure Configuration of Red Hat Enterprise Linux 7

with profile Common Profile for General-Purpose Systems

This guide presents a catalog of security-relevant configuration settings for Red Hat Enterprise Linux 7 formatted in the eXtensible Configuration Checklist Description Format (XCCDF).

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.
Do not attempt to implement any of the settings in this guide without first testing them in a non-operational environment. The creators of this guidance assume no responsibility whatsoever for its use by other parties, and makes no guarantees, expressed or implied, about its quality, reliability, or any other characteristic.

Evaluation Characteristics

Target machinelocalhost.localdomain
Benchmark URL/usr/share/xml/scap/ssg/content/ssg-rhel7-xccdf.xml
Profile IDcommon
Started at2015-07-17T10:50:19
Finished at2015-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

The target system did not satisfy the conditions of 27 rules! Please review rule results and consider applying remediation.

Rule results

9 passed
27 failed
0 other

Severity of failed rules

0 other
27 low
0 medium
0 high

Score

Scoring systemScoreMaximumPercent
urn:xccdf:scoring:default83.333328100.000000
83.33%

Rule Overview

TitleSeverityResult
Guide to the Secure Configuration of Red Hat Enterprise Linux 7 27x fail
Introduction
General Principles
Encrypt Transmitted Data Whenever Possible
Minimize Software to Minimize Vulnerability
Run Different Network Services on Separate Systems
Configure Security Tools to Improve System Robustness
Least Privilege
How to Use This Guide
Read Sections Completely and in Order
Test in Non-Production Environment
Root Shell Environment Assumed
Formatting Conventions
Reboot Required
System Settings 27x fail
Installing and Maintaining Software
Disk Partitioning
Ensure /tmp Located On Separate Partitionlow
notselected
Ensure /var Located On Separate Partitionlow
notselected
Ensure /var/log Located On Separate Partitionlow
notapplicable
Ensure /var/log/audit Located On Separate Partitionlow
notapplicable
Ensure /home Located On Separate Partitionlow
notselected
Encrypt Partitionslow
notselected
Updating Software
Ensure Red Hat GPG Key Installedhigh
notselected
Ensure gpgcheck Enabled In Main Yum Configurationhigh
notselected
Ensure gpgcheck Enabled For All Yum Package Repositorieshigh
notselected
Ensure Software Patches Installedhigh
notselected
Software Integrity Checking
Verify Integrity with AIDE
Install AIDEmedium
notselected
Build and Test AIDE Databasemedium
notselected
Configure Periodic Execution of AIDEmedium
notselected
Verify Integrity with RPM
Verify and Correct File Permissions with RPMlow
notselected
Verify File Hashes with RPMlow
notselected
Additional Security Software
Install Intrusion Detection Softwarehigh
notselected
Install Virus Scanning Softwarelow
notselected
File Permissions and Masks
Restrict Partition Mount Options
Add nodev Option to Non-Root Local Partitionslow
notselected
Add nodev Option to Removable Media Partitionslow
notselected
Add noexec Option to Removable Media Partitionslow
notselected
Add nosuid Option to Removable Media Partitionslow
notselected
Add nodev Option to /tmplow
notselected
Add noexec Option to /tmplow
notselected
Add nosuid Option to /tmplow
notselected
Add nodev Option to /dev/shmlow
notselected
Add noexec Option to /dev/shmlow
notselected
Add nosuid Option to /dev/shmlow
notselected
Bind Mount /var/tmp To /tmplow
notselected
Restrict Dynamic Mounting and Unmounting of Filesystems
Disable Modprobe Loading of USB Storage Driverlow
notselected
Disable Kernel Support for USB via Bootloader Configurationlow
notselected
Disable Booting from USB Devices in Boot Firmwarelow
notselected
Assign Password to Prevent Changes to Boot Firmware Configurationlow
notselected
Disable the Automounterlow
pass
Disable GNOME3 Automountinglow
notselected
Disable Mounting of cramfslow
notselected
Disable Mounting of freevxfslow
notselected
Disable Mounting of jffs2low
notselected
Disable Mounting of hfslow
notselected
Disable Mounting of hfspluslow
notselected
Disable Mounting of squashfslow
notselected
Disable Mounting of udflow
notselected
Disable All GNOME3 Thumbnailerslow
notselected
Verify Permissions on Important Files and Directories
Verify User Who Owns shadow Filemedium
notselected
Verify Group Who Owns shadow Filemedium
notselected
Verify Permissions on shadow Filemedium
notselected
Verify User Who Owns group Filemedium
notselected
Verify Group Who Owns group Filemedium
notselected
Verify Permissions on group Filemedium
notselected
Verify User Who Owns gshadow Filemedium
notselected
Verify Group Who Owns gshadow Filemedium
notselected
Verify Permissions on gshadow Filemedium
notselected
Verify User Who Owns passwd Filemedium
notselected
Verify Group Who Owns passwd Filemedium
notselected
Verify Permissions on passwd Filemedium
notselected
Verify File Permissions Within Some Important Directories
Verify that Shared Library Files Have Restrictive Permissionsmedium
notselected
Verify that Shared Library Files Have Root Ownershipmedium
notselected
Verify that System Executables Have Restrictive Permissionsmedium
notselected
Verify that System Executables Have Root Ownershipmedium
notselected
Verify that All World-Writable Directories Have Sticky Bits Setlow
notselected
Ensure No World-Writable Files Existmedium
notselected
Ensure All SGID Executables Are Authorizedlow
notselected
Ensure All SUID Executables Are Authorizedlow
notselected
Ensure All Files Are Owned by a Userlow
notselected
Ensure All Files Are Owned by a Grouplow
notselected
Ensure All World-Writable Directories Are Owned by a System Accountlow
notselected
Restrict Programs from Dangerous Execution Patterns
Daemon Umask
Set Daemon Umasklow
notselected
Disable Core Dumps
Disable Core Dumps for All Userslow
notselected
Disable Core Dumps for SUID programslow
notselected
Enable ExecShield
Enable ExecShieldmedium
notselected
Enable Randomized Layout of Virtual Address Spacemedium
notselected
Enable Execute Disable (XD) or No Execute (NX) Support on x86 Systems
Install PAE Kernel on Supported 32-bit x86 Systemslow
notselected
Enable NX or XD Support in the BIOSlow
notselected
Restrict Access to Kernel Message Bufferlow
notselected
SELinux
Ensure SELinux Not Disabled in /etc/grub.confmedium
notselected
Ensure SELinux State is Enforcingmedium
notselected
Configure SELinux Policylow
notselected
Uninstall setroubleshoot Packagelow
notselected
Uninstall mcstrans Packagelow
notselected
Ensure No Daemons are Unconfined by SELinuxmedium
notselected
Ensure No Device Files are Unlabeled by SELinuxlow
notselected
Account and Access Control
Protect Accounts by Restricting Password-Based Login
Restrict Root Logins
Direct root Logins Not Allowedmedium
notselected
Restrict Serial Port Root Loginslow
notselected
Restrict Web Browser Use for Administrative Accountslow
notselected
Ensure that System Accounts Do Not Run a Shell Upon Loginmedium
notselected
Verify Only Root Has UID 0medium
notselected
Root Path Must Be Vendor Defaultlow
notselected
Verify Proper Storage and Existence of Password Hashes
Prevent Log In to Accounts With Empty Passwordhigh
notselected
Verify All Account Password Hashes are Shadowedmedium
notselected
All GIDs referenced in /etc/passwd must be defined in /etc/grouplow
notselected
Verify No netrc Files Existmedium
notselected
Set Password Expiration Parameters
Protect Accounts by Configuring PAM
Set Password Quality Requirements
Set Password Quality Requirements with pam_pwquality
Set Password Retry Prompts Permitted Per-Sessionlow
notselected
Set Password to Maximum of Three Consecutive Repeating Characterslow
notselected
Set Password Strength Minimum Digit Characterslow
notselected
Set Password Minimum Lengthlow
notselected
Set Password Strength Minimum Uppercase Characterslow
notselected
Set Password Strength Minimum Special Characterslow
notselected
Set Password Strength Minimum Lowercase Characterslow
notselected
Set Password Strength Minimum Different Characterslow
notselected
Set Password Strength Minimum Different Categorieslow
notselected
Set Lockouts for Failed Password Attempts
Set Deny For Failed Password Attemptsmedium
notselected
Set Lockout Time For Failed Password Attemptsmedium
notselected
Set Interval For Counting Failed Password Attemptsmedium
notselected
Limit Password Reusemedium
notselected
Set Password Hashing Algorithm
Set Password Hashing Algorithm in /etc/pam.d/system-authmedium
notselected
Set Password Hashing Algorithm in /etc/login.defsmedium
notselected
Set Password Hashing Algorithm in /etc/libuser.confmedium
notselected
Secure Session Configuration Files for Login Accounts
Ensure that No Dangerous Directories Exist in Root's Path
Ensure that Root's Path Does Not Include Relative Paths or Null Directorieslow
notselected
Ensure that Root's Path Does Not Include World or Group-Writable Directorieslow
notselected
Ensure that Users Have Sensible Umask Values
Ensure the Default Bash Umask is Set Correctlylow
notselected
Ensure the Default C Shell Umask is Set Correctlylow
notselected
Ensure the Default Umask is Set Correctly in /etc/profilelow
notselected
Ensure that User Home Directories are not Group-Writable or World-Readablelow
notselected
Protect Physical Console Access
Set Boot Loader Password
Verify /boot/grub2/grub.cfg User Ownershipmedium
notselected
Verify /boot/grub2/grub.cfg Group Ownershipmedium
notselected
Verify /boot/grub2/grub.cfg Permissionsmedium
notselected
Set Boot Loader Passwordmedium
notselected
Configure Screen Locking
Configure GUI Screen Locking
Set GNOME3 Screensaver Inactivity Timeoutmedium
notselected
Enable GNOME3 Screensaver Idle Activationmedium
notselected
Enable GNOME3 Screensaver Lock After Idle Periodmedium
notselected
Implement Blank Screensaverlow
notselected
Configure Console Screen Locking
Install the screen Packagelow
notselected
Enable Smart Card Loginmedium
notselected
Require Authentication for Single User Modemedium
notselected
Disable Ctrl-Alt-Del Reboot Activationhigh
notselected
Disable Interactive Bootmedium
notselected
Warning Banners for System Accesses
Enable GNOME3 Login Warning Bannermedium
notselected
Modify the System Login Bannermedium
notselected
Disable the GNOME3 Login User Listlow
notselected
Network Configuration and Firewalls
Disable Unused Interfaces
Kernel Parameters Which Affect Networking
Network Parameters for Hosts Only
Disable Kernel Parameter for Sending ICMP Redirects by Defaultmedium
notselected
Disable Kernel Parameter for Sending ICMP Redirects for All Interfacesmedium
notselected
Disable Kernel Parameter for IP Forwardingmedium
notselected
Network Related Kernel Runtime Parameters for Hosts and Routers
Disable Kernel Parameter for Accepting Source-Routed Packets for All Interfacesmedium
notselected
Disable Kernel Parameter for Accepting ICMP Redirects for All Interfacesmedium
notselected
Disable Kernel Parameter for Accepting Secure Redirects for All Interfacesmedium
notselected
Enable Kernel Parameter to Log Martian Packetslow
notselected
Disable Kernel Parameter for Accepting Source-Routed Packets By Defaultmedium
notselected
Disable Kernel Parameter for Accepting ICMP Redirects By Defaultlow
notselected
Disable Kernel Parameter for Accepting Secure Redirects By Defaultmedium
notselected
Enable Kernel Parameter to Ignore ICMP Broadcast Echo Requestslow
notselected
Enable Kernel Parameter to Ignore Bogus ICMP Error Responseslow
notselected
Enable Kernel Parameter to Use TCP Syncookiesmedium
notselected
Enable Kernel Parameter to Use Reverse Path Filtering for All Interfacesmedium
notselected
Enable Kernel Parameter to Use Reverse Path Filtering by Defaultmedium
notselected
Wireless Networking
Disable Wireless Through Software Configuration
Disable WiFi or Bluetooth in BIOSlow
notselected
Deactivate Wireless Network Interfaceslow
notselected
Disable Bluetooth Servicemedium
notselected
Disable Bluetooth Kernel Modulesmedium
notselected
IPv6
Disable Support for IPv6 Unless Needed
Disable IPv6 Networking Support Automatic Loadingmedium
notselected
Disable Interface Usage of IPv6low
notselected
Disable Support for RPC IPv6low
notselected
Configure IPv6 Settings if Necessary
Disable Automatic Configuration
Disable Accepting IPv6 Router Advertisementslow
notselected
Disable Accepting IPv6 Redirectsmedium
notselected
Limit Network-Transmitted Configuration if Using Static IPv6 Addresses
Manually Assign Global IPv6 Addresslow
notselected
Use Privacy Extensions for Addresslow
notselected
Manually Assign IPv6 Router Addresslow
notselected
firewalld
Inspect and Activate Default firewalld Rules
Verify firewalld Enabledmedium
notselected
iptables and ip6tables
Inspect and Activate Default Rules
Verify ip6tables Enabled if Using IPv6medium
notselected
Set Default ip6tables Policy for Incoming Packetsmedium
notselected
Verify iptables Enabledmedium
notselected
Strengthen the Default Ruleset
Restrict ICMP Message Types
Log and Drop Packets with Suspicious Source Addresses
Set Default iptables Policy for Incoming Packetsmedium
notselected
Set Default iptables Policy for Forwarded Packetsmedium
notselected
Transport Layer Security Support
Uncommon Network Protocols
Disable DCCP Supportmedium
notselected
Disable SCTP Supportmedium
notselected
Disable RDS Supportlow
notselected
Disable TIPC Supportmedium
notselected
IPSec Support
Install libreswan Packagelow
notselected
Disable Zeroconf Networkinglow
notselected
Ensure System is Not Acting as a Network Snifferlow
notselected
Configure Syslog
Ensure Proper Configuration of Log Files
Ensure Log Files Are Owned By Appropriate Usermedium
notselected
Ensure Log Files Are Owned By Appropriate Groupmedium
notselected
Ensure System Log Files Have Correct Permissionsmedium
notselected
Rsyslog Logs Sent To Remote Host
Ensure Logs Sent To Remote Hostlow
notselected
Configure rsyslogd to Accept Remote Messages If Acting as a Log Server
Ensure rsyslog Does Not Accept Remote Messages Unless Acting As Log Serverlow
notselected
Enable rsyslog to Accept Messages via TCP, if Acting As Log Serverlow
notselected
Enable rsyslog to Accept Messages via UDP, if Acting As Log Serverlow
notselected
Ensure All Logs are Rotated by logrotate
Ensure Logrotate Runs Periodicallylow
notselected
Configure Logwatch on the Central Log Server
Configure Logwatch HostLimit Linelow
notselected
Configure Logwatch SplitHosts Linelow
notselected
Ensure rsyslog is Installedmedium
pass
Enable rsyslog Servicemedium
pass
Disable Logwatch on Clients if a Logserver Existslow
notselected
System Accounting with auditd 27x fail
Configure auditd Data Retention
Configure auditd Number of Logs Retainedmedium
notselected
Configure auditd Max Log File Sizemedium
notselected
Configure auditd max_log_file_action Upon Reaching Maximum Log Sizemedium
notselected
Configure auditd space_left Action on Low Disk Spacemedium
notselected
Configure auditd admin_space_left Action on Low Disk Spacemedium
notselected
Configure auditd mail_acct Action on Low Disk Spacemedium
notselected
Configure auditd to use audispd pluginmedium
notselected
Configure auditd Rules for Comprehensive Auditing 27x fail
Records Events that Modify Date and Time Information 5x fail
Record attempts to alter time through adjtimexlow
fail
Record attempts to alter time through settimeofdaylow
fail
Record Attempts to Alter Time Through stimelow
fail
Record Attempts to Alter Time Through clock_settimelow
fail
Record Attempts to Alter the localtime Filelow
fail
Record Events that Modify the System's Discretionary Access Controls 13x fail
Record Events that Modify the System's Discretionary Access Controls - chmodlow
fail
Record Events that Modify the System's Discretionary Access Controls - chownlow
fail
Record Events that Modify the System's Discretionary Access Controls - fchmodlow
fail
Record Events that Modify the System's Discretionary Access Controls - fchmodatlow
fail
Record Events that Modify the System's Discretionary Access Controls - fchownlow
fail
Record Events that Modify the System's Discretionary Access Controls - fchownatlow
fail
Record Events that Modify the System's Discretionary Access Controls - fremovexattrlow
fail
Record Events that Modify the System's Discretionary Access Controls - fsetxattrlow
fail
Record Events that Modify the System's Discretionary Access Controls - lchownlow
fail
Record Events that Modify the System's Discretionary Access Controls - lremovexattrlow
fail
Record Events that Modify the System's Discretionary Access Controls - lsetxattrlow
fail
Record Events that Modify the System's Discretionary Access Controls - removexattrlow
fail
Record Events that Modify the System's Discretionary Access Controls - setxattrlow
fail
Record Events that Modify User/Group Informationlow
fail
Record Events that Modify the System's Network Environmentlow
fail
System Audit Logs Must Have Mode 0640 or Less Permissivelow
notselected
System Audit Logs Must Be Owned By Rootlow
notselected
Record Events that Modify the System's Mandatory Access Controlslow
fail
Record Attempts to Alter Process and Session Initiation Informationlow
notselected
Ensure auditd Collects Unauthorized Access Attempts to Files (unsuccessful)low
fail
Ensure auditd Collects Information on the Use of Privileged Commandslow
fail
Ensure auditd Collects Information on Exporting to Media (successful)low
fail
Ensure auditd Collects File Deletion Events by Userlow
fail
Ensure auditd Collects System Administrator Actionslow
fail
Ensure auditd Collects Information on Kernel Module Loading and Unloadinglow
fail
Make the auditd Configuration Immutablelow
notselected
Enable auditd Servicemedium
notselected
Enable Auditing for Processes Which Start Prior to the Audit Daemonmedium
notselected
Services
Obsolete Services
Xinetd
Disable xinetd Servicemedium
notselected
Uninstall xinetd Packagelow
notselected
Telnet
Disable telnet Servicehigh
notselected
Uninstall telnet-server Packagehigh
notselected
Remove telnet Clientslow
notselected
Rlogin, Rsh, and Rexec
Uninstall rsh-server Packagehigh
notselected
Disable rexec Servicehigh
notselected
Disable rsh Servicehigh
notselected
Uninstal rsh Packagelow
notselected
Disable rlogin Servicehigh
notselected
Remove Rsh Trust Fileshigh
notselected
NIS
Uninstall ypserv Packagemedium
notselected
Disable ypbind Servicemedium
notselected
Remove NIS Clientlow
notselected
TFTP Server
Disable tftp Servicemedium
notselected
Uninstall tftp-server Packagemedium
notselected
Remove tftplow
notselected
Ensure tftp Daemon Uses Secure Modehigh
notselected
Chat/Messaging Services
Uninstall talk-server Packagemedium
notselected
Uninstall talk Packagelow
notselected
Base Services
Disable Automatic Bug Reporting Tool (abrtd)low
pass
Disable Advanced Configuration and Power Interface (acpid)low
notselected
Disable Certmonger Service (certmonger)low
notselected
Disable Control Group Config (cgconfig)low
notselected
Disable Control Group Rules Engine (cgred)low
notselected
Disable CPU Speed (cpuspeed)low
notselected
Enable IRQ Balance (irqbalance)low
notselected
Disable KDump Kernel Crash Analyzer (kdump)low
notselected
Disable Software RAID Monitor (mdmonitor)low
notselected
Disable D-Bus IPC Service (messagebus)low
notselected
Disable Network Console (netconsole)low
notselected
Disable ntpdate Service (ntpdate)low
pass
Disable Odd Job Daemon (oddjobd)low
pass
Disable Portreserve (portreserve)low
notselected
Enable Process Accounting (psacct)low
notselected
Disable Apache Qpid (qpidd)low
pass
Disable Quota Netlink (quota_nld)low
notselected
Disable Network Router Discovery Daemon (rdisc)low
pass
Disable Red Hat Network Service (rhnsd)low
notselected
Disable Red Hat Subscription Manager Daemon (rhsmcertd)low
notselected
Disable Cyrus SASL Authentication Daemon (saslauthd)low
notselected
Disable SMART Disk Monitoring Service (smartd)low
notselected
Disable System Statistics Reset Service (sysstat)low
notselected
Cron and At Daemons
Restrict at and cron to Authorized Users if Necessary
Enable cron Servicemedium
notselected
Disable anacron Servicelow
notselected
Disable At Service (atd)low
pass
SSH Server
Configure OpenSSH Server if Necessary
Strengthen Firewall Configuration if Possible
Allow Only SSH Protocol 2high
notselected
Limit Users' SSH Accesslow
notselected
Set SSH Idle Timeout Intervallow
notselected
Set SSH Client Alive Countlow
notselected
Disable SSH Support for .rhosts Filesmedium
notselected
Disable Host-Based Authenticationmedium
notselected
Disable SSH Access via Empty Passwordshigh
notselected
Enable SSH Warning Bannermedium
notselected
Do Not Allow SSH Environment Optionslow
notselected
Use Only Approved Ciphersmedium
notselected
Disable SSH Server If Possible (Unusual)low
notselected
Remove SSH Server iptables Firewall exception (Unusual)low
notselected
X Window System
Disable X Windows
Disable X Windows Startup By Setting Default Targetlow
notselected
Remove the X Windows Package Grouplow
notselected
Avahi Server
Disable Avahi Server if Possible
Disable Avahi Server Softwarelow
notselected
Configure Avahi if Necessary
Serve Avahi Only via Required Protocollow
notselected
Check Avahi Responses' TTL Fieldlow
notselected
Prevent Other Programs from Using Avahi's Portlow
notselected
Disable Avahi Publishinglow
notselected
Restrict Information Published by Avahilow
notselected
Print Support
Configure the CUPS Service if Necessary
Disable Printer Browsing Entirely if Possiblelow
notselected
Disable Print Server Capabilitieslow
notselected
Disable the CUPS Servicelow
notselected
DHCP
Disable DHCP Server
Disable DHCP Servicemedium
notselected
Uninstall DHCP Server Packagemedium
notselected
Disable DHCP Server
Minimize Served Information
Do Not Use Dynamic DNSlow
notselected
Deny Decline Messageslow
notselected
Deny BOOTP Querieslow
notselected
Configure Logginglow
notselected
Disable DHCP Client
Disable DHCP Clientlow
notselected
Configure DHCP Client if Necessary
Minimize the DHCP-Configured Options
Network Time Protocol
Enable the NTP Daemonmedium
notselected
Specify a Remote NTP Servermedium
notselected
Specify Additional Remote NTP Serverslow
notselected
Mail Server Software
Configure SMTP For Mail Clients
Disable Postfix Network Listeningmedium
notselected
Configure Operating System to Protect Mail Server
Configure SSL Certificates for Use with SMTP AUTH
Ensure Security of Postfix SSL Certificate
Configure Postfix if Necessary
Configure Postfix Resource Usage to Limit Denial of Service Attacks
Control Mail Relaying
Configure Trusted Networks and Hosts
Enact SMTP Relay Restrictions
Enact SMTP Recipient Restrictions
Require SMTP AUTH Before Relaying from Untrusted Clients
Use TLS for SMTP AUTH
Configure SMTP Greeting Bannermedium
notselected
Enable Postfix Servicelow
notselected
Uninstall Sendmail Packagemedium
notselected
LDAP
Configure OpenLDAP Clients
Configure LDAP Client to Use TLS For All Transactionsmedium
notselected
Configure Certificate Directives for LDAP Use of TLSmedium
notselected
Configure OpenLDAP Server
Install and Protect LDAP Certificate Files
Uninstall openldap-servers Packagelow
notselected
NFS and RPC
Disable All NFS Services if Possible
Disable Services Used Only by NFS
Disable Network File System Lock Service (nfslock)low
notselected
Disable Secure RPC Client Service (rpcgssd)low
notselected
Disable RPC ID Mapping Service (rpcidmapd)low
notselected
Disable netfs if Possible
Disable Network File Systems (netfs)low
notselected
Configure All Machines which Use NFS
Make Each Machine a Client or a Server, not Both
Configure NFS Services to Use Fixed Ports (NFSv3 and NFSv2)
Configure lockd to use static TCP portlow
notselected
Configure lockd to use static UDP portlow
notselected
Configure statd to use static portlow
notselected
Configure mountd to use static portlow
notselected
Configure NFS Clients
Disable NFS Server Daemons
Specify UID and GID for Anonymous NFS Connectionslow
notselected
Disable Network File System (nfs)low
notselected
Disable Secure RPC Server Service (rpcsvcgssd)low
notselected
Mount Remote Filesystems with Restrictive Options
Mount Remote Filesystems with nodevmedium
notselected
Mount Remote Filesystems with nosuidmedium
notselected
Configure NFS Servers
Configure the Exports File Restrictively
Use Access Lists to Enforce Authorization Restrictions
Export Filesystems Read-Only if Possible
Use Root-Squashing on All Exportslow
notselected
Restrict NFS Clients to Privileged Portslow
notselected
Ensure Insecure File Locking is Not Allowedmedium
notselected
DNS Server
Disable DNS Server
Disable DNS Serverlow
notselected
Uninstall bind Packagelow
notselected
Isolate DNS from Other Services
Run DNS Software on Dedicated Servers
Run DNS Software in a chroot Jail
Protect DNS Data from Tampering or Attack
Run Separate DNS Servers for External and Internal Queries
Use Views to Partition External and Internal Information
Disable Zone Transfers from the Nameserverlow
notselected
Authenticate Zone Transferslow
notselected
Disable Dynamic Updateslow
notselected
FTP Server
Disable vsftpd if Possible
Disable vsftpd Servicelow
notselected
Uninstall vsftpd Packagelow
notselected
Use vsftpd to Provide FTP Service if Necessary
Install vsftpd Packagelow
notselected
Use vsftpd to Provide FTP Service if Necessary
Restrict the Set of Users Allowed to Access FTP
Limit Users Allowed FTP Access if Necessary
Restrict Access to Anonymous Users if Possiblelow
notselected
Configure Firewalls to Protect the FTP Server
Enable Logging of All FTP Transactionslow
notselected
Create Warning Banners for All FTP Usersmedium
notselected
Disable FTP Uploads if Possiblelow
notselected
Place the FTP Home Directory on its Own Partitionlow
notselected
Web Server
Disable Apache if Possible
Disable httpd Servicelow
notselected
Uninstall httpd Packagelow
notselected
Install Apache if Necessary
Confirm Minimal Built-in Modules Installed
Secure Apache Configuration
Restrict Web Server Information Leakage
Set httpd ServerTokens Directive to Prodlow
notselected
Set httpd ServerSignature Directive to Offlow
notselected
Minimize Web Server Loadable Modules
httpd Core Modules
Minimize Modules for HTTP Basic Authentication
Minimize Various Optional Components
Minimize Configuration Files Included
Disable HTTP Digest Authenticationlow
notselected
Disable HTTP mod_rewritelow
notselected
Disable LDAP Supportlow
notselected
Disable Server Side Includeslow
notselected
Disable MIME Magiclow
notselected
Disable WebDAV (Distributed Authoring and Versioning)low
notselected
Disable Server Activity Statuslow
notselected
Disable Web Server Configuration Displaylow
notselected
Disable URL Correction on Misspelled Entrieslow
notselected
Disable Proxy Supportlow
notselected
Disable Cache Supportlow
notselected
Disable CGI Supportlow
notselected
Directory Restrictions
Restrict Root Directorylow
notselected
Restrict Web Directorylow
notselected
Restrict Other Critical Directorieslow
notselected
Limit Available Methodslow
notselected
Use Appropriate Modules to Improve httpd's Security
Deploy mod_ssl
Install mod_ssllow
notselected
Deploy mod_security
Install mod_securitylow
notselected
Use Denial-of-Service Protection Modules
Configure PHP Securely
Configure Operating System to Protect Web Server
Restrict File and Directory Access
Set Permissions on the /var/log/httpd/ Directorylow
notselected
Set Permissions on the /etc/httpd/conf/ Directorylow
notselected
Set Permissions on All Configuration Files Inside /etc/httpd/conf/low
notselected
Configure iptables to Allow Access to the Web Server
Run httpd in a chroot Jail if Practical
IMAP and POP3 Server
Disable Dovecot
Disable Dovecot Servicelow
notselected
Uninstall dovecot Packagelow
notselected
Configure Dovecot if Necessary
Support Only the Necessary Protocols
Enable SSL Support
Enable the SSL flag in /etc/dovecot.conflow
notselected
Configure Dovecot to Use the SSL Certificate filelow
notselected
Configure Dovecot to Use the SSL Key filelow
notselected
Disable Plaintext Authenticationlow
notselected
Allow IMAP Clients to Access the Server
Samba(SMB) Microsoft Windows File Sharing Server
Disable Samba if Possible
Disable Sambalow
notselected
Configure Samba if Necessary
Restrict SMB File Sharing to Configured Networks
Restrict Printer Sharing
Disable Root Access to SMB Shareslow
notselected
Require Client SMB Packet Signing, if using smbclientlow
notselected
Require Client SMB Packet Signing, if using mount.cifslow
notselected
Proxy Server
Disable Squid if Possible
Disable Squidlow
notselected
Uninstall squid Packagelow
notselected
SNMP Server
Disable SNMP Server if Possible
Disable snmpd Servicelow
notselected
Uninstall net-snmp Packagelow
notselected
Configure SNMP Server if Necessary
Configure SNMP Service to Use Only SNMPv3 or Newer medium
notselected
Ensure Default Password Is Not Usedmedium
notselected
Documentation to Support DISA OS SRG Mapping
Product Meets this Requirementlow
notselected
Product Meets this Requirementlow
notselected
Product Meets this Requirementlow
notselected
Guidance Does Not Meet this Requirement Due to Impracticality or Scopelow
notselected
Implementation of the Requirement is Not Supportedlow
notselected
Guidance Does Not Meet this Requirement Due to Impracticality or Scopelow
notselected
A process for prompt installation of OS updates must exist.low
notselected

Result Details

Ensure /tmp Located On Separate Partitionpartition_for_tmp CCE-27173-4

Ensure /tmp Located On Separate Partition

Rule IDpartition_for_tmp
Result
notselected
Time2015-07-17T10:50:19
Severitylow
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 /tmp directory is a world-writable directory used for temporary file storage. Ensure it has its own partition or logical volume at installation time, or migrate it using LVM.

Rationale

The /tmp partition is used as temporary storage by many programs. Placing /tmp in its own partition enables the setting of more restrictive mount options, which can help protect programs which use it.

Ensure /var Located On Separate Partitionpartition_for_var CCE-26404-4

Ensure /var Located On Separate Partition

Rule IDpartition_for_var
Result
notselected
Time2015-07-17T10:50:19
Severitylow
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 /var directory is used by daemons and other system services to store frequently-changing data. Ensure that /var has its own partition or logical volume at installation time, or migrate it using LVM.

Rationale

Ensuring that /var is mounted on its own partition enables the setting of more restrictive mount options. This helps protect system services such as daemons or other programs which use it. It is not uncommon for the /var directory to contain world-writable directories installed by other software packages.

Ensure /var/log Located On Separate Partitionpartition_for_var_log CCE-26967-0

Ensure /var/log Located On Separate Partition

Rule IDpartition_for_var_log
Result
notapplicable
Time2015-07-17T10:50:20
Severitylow
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 /var/log directory. Ensure that it has its own partition or logical volume at installation time, or migrate it using LVM.

Rationale

Placing /var/log in its own partition enables better separation between log files and other files in /var/.

Ensure /var/log/audit Located On Separate Partitionpartition_for_var_log_audit CCE-26971-2

Ensure /var/log/audit Located On Separate Partition

Rule IDpartition_for_var_log_audit
Result
notapplicable
Time2015-07-17T10:50:20
Severitylow
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 /var/log/audit directory. Ensure that it has its own partition or logical volume at installation time, or migrate it later using LVM. Make absolutely certain that it is large enough to store all audit logs that will be created by the auditing daemon.

Rationale

Placing /var/log/audit in its own partition enables better separation between audit files and other files, and helps ensure that auditing cannot be halted due to the partition running out of space.

Ensure /home Located On Separate Partitionpartition_for_home CCE-RHEL7-CCE-TBD

Ensure /home Located On Separate Partition

Rule IDpartition_for_home
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 /home at installation time (or migrate it later using LVM). If /home will be mounted from another system such as an NFS server, then creating a separate partition is not necessary at installation time, and the mountpoint can instead be configured later.

Rationale

Ensuring that /home is mounted on its own partition enables the setting of more restrictive mount options, and also helps ensure that users cannot trivially fill partitions used for log or audit data storage.

Encrypt Partitionsencrypt_partitions CCE-27128-8

Encrypt Partitions

Rule IDencrypt_partitions
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-27128-8

references:  SC-13, SC-28, 1019, 1199, 1200, 185

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.

For manual installations, select the Encrypt checkbox during partition creation to encrypt the partition. When this option is selected the system will prompt for a passphrase to use in decrypting the partition. The passphrase will subsequently need to be entered manually every time the system boots.

For automated/unattended installations, it is possible to use Kickstart by adding the --encrypted and --passphrase= options to the definition of each partition to be encrypted. For example, the following line would encrypt the root partition:

part / --fstype=ext4 --size=100 --onpart=hda1 --encrypted --passphrase=PASSPHRASE
Any PASSPHRASE is stored in the Kickstart in plaintext, and the Kickstart must then be protected accordingly. Omitting the --passphrase= option from the partition definition will cause the installer to pause and interactively ask for the passphrase during installation.

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 Installedensure_redhat_gpgkey_installed CCE-26957-1

Ensure Red Hat GPG Key Installed

Rule IDensure_redhat_gpgkey_installed
Result
notselected
Time2015-07-17T10:50:20
Severityhigh
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_register
If the system is not connected to the Internet or an RHN Satellite, then install the Red Hat GPG key from trusted media such as the Red Hat installation CD-ROM or DVD. Assuming the disc is mounted in /media/cdrom, use the following command as the root user to import it into the keyring:
$ sudo rpm --import /media/cdrom/RPM-GPG-KEY

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 Configurationensure_gpgcheck_globally_activated CCE-26989-4

Ensure gpgcheck Enabled In Main Yum Configuration

Rule IDensure_gpgcheck_globally_activated
Result
notselected
Time2015-07-17T10:50:20
Severityhigh
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 option controls whether RPM packages' signatures are always checked prior to installation. To configure yum to check package signatures before installing them, ensure the following line appears in /etc/yum.conf in the [main] section:

gpgcheck=1

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 Repositoriesensure_gpgcheck_never_disabled CCE-26876-3

Ensure gpgcheck Enabled For All Yum Package Repositories

Rule IDensure_gpgcheck_never_disabled
Result
notselected
Time2015-07-17T10:50:20
Severityhigh
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 /etc/yum.repos.d of the form:

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 Installedsecurity_patches_up_to_date CCE-26853-2

Ensure Software Patches Installed

Rule IDsecurity_patches_up_to_date
Result
notselected
Time2015-07-17T10:50:20
Severityhigh
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 update
If the system is not configured to use one of these sources, updates (in the form of RPM packages) can be manually downloaded from the Red Hat Network and installed using rpm.

Rationale

Installing software updates is a fundamental mitigation against the exploitation of publicly-known vulnerabilities.

Install AIDEpackage_aide_installed CCE-26741-9

Install AIDE

Rule IDpackage_aide_installed
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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.

Build and Test AIDE Databaseaide_build_database CCE-RHEL7-CCE-TBD

Build and Test AIDE Database

Rule IDaide_build_database
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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

Description

Run the following command to generate a new database:

$ sudo /usr/sbin/aide --init
By default, the database will be written to the file /var/lib/aide/aide.db.new.gz. Storing the database, the configuration file /etc/aide.conf, and the binary /usr/sbin/aide (or hashes of these files), in a secure location (such as on read-only media) provides additional assurance about their integrity. The newly-generated database can be installed as follows:
$ sudo cp /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz
To initiate a manual check, run the following command:
$ sudo /usr/sbin/aide --check
If this check produces any unexpected output, investigate.

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 AIDEaide_periodic_cron_checking CCE-RHEL7-CCE-TBD

Configure Periodic Execution of AIDE

Rule IDaide_periodic_cron_checking
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/crontab:

05 4 * * * root /usr/sbin/aide --check
AIDE 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 and Correct File Permissions with RPMrpm_verify_permissions CCE-RHEL7-CCE-TBD

Verify and Correct File Permissions with RPM

Rule IDrpm_verify_permissions
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-6, CM-6(d), CM-6(3), 1493, 1494, 1495

Description

The RPM package management system can check file access permissions of installed software packages, including many that are important to system security. After locating a file with incorrect permissions, run the following command to determine which package owns it:

$ rpm -qf FILENAME
Next, run the following command to reset its permissions to the correct values:
$ sudo rpm --setperms PACKAGENAME

Rationale

Permissions on system binaries and configuration files that are too generous could allow an unauthorized user to gain privileges that they should not have. The permissions set by the vendor should be maintained. Any deviations from this baseline should be investigated.

Verify File Hashes with RPMrpm_verify_hashes CCE-RHEL7-CCE-TBD

Verify File Hashes with RPM

Rule IDrpm_verify_hashes
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-6(d), CM-6(3), SI-7, 1496

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 FILENAME
The package can be reinstalled from a yum repository using the command:
$ sudo yum reinstall PACKAGENAME
Alternatively, the package can be reinstalled from trusted media using the command:
$ sudo rpm -Uvh PACKAGENAME

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 Softwareinstall_hids CCE-RHEL7-CCE-TBD

Install Intrusion Detection Software

Rule IDinstall_hids
Result
notselected
Time2015-07-17T10:50:20
Severityhigh
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  SC-7, 1263

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.
In DoD environments, supplemental intrusion detection tools, such as, the McAfee Host-based Security System, are available to integrate with existing infrastructure. When these supplemental tools interfere with the proper functioning of SELinux, SELinux takes precedence.

Rationale

Host-based intrusion detection tools provide a system-level defense when an intruder gains access to a system or network.

Install Virus Scanning Softwareinstall_antivirus CCE-RHEL7-CCE-TBD

Install Virus Scanning Software

Rule IDinstall_antivirus
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  SC-28, SI-3, 1239, 1668

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 Partitionsmount_option_nodev_nonroot_local_partitions CCE-RHEL7-CCE-TBD

Add nodev Option to Non-Root Local Partitions

Rule IDmount_option_nodev_nonroot_local_partitions
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

The nodev mount option prevents files from being interpreted as character or block devices. Legitimate character and block devices should exist only in the /dev directory on the root partition or within chroot jails built for system services. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of any non-root local partitions.

Rationale

The nodev mount option prevents files from being interpreted as character or block devices. The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails, for which it is not advised to set nodev on these filesystems.

Add nodev Option to Removable Media Partitionsmount_option_nodev_removable_partitions CCE-RHEL7-CCE-TBD

Add nodev Option to Removable Media Partitions

Rule IDmount_option_nodev_removable_partitions
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-19(a), AC-19(d), AC-19(e), CM-7, MP-2

Description

The nodev mount option prevents files from being interpreted as character or block devices. Legitimate character and block devices should exist only in the /dev directory on the root partition or within chroot jails built for system services. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of any removable media partitions.

Rationale

The only legitimate location for device files is the /dev directory located on the root partition. An exception to this is chroot jails, and it is not advised to set nodev on partitions which contain their root filesystems.

Add noexec Option to Removable Media Partitionsmount_option_noexec_removable_partitions CCE-RHEL7-CCE-TBD

Add noexec Option to Removable Media Partitions

Rule IDmount_option_noexec_removable_partitions
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-19(a), AC-19(d), AC-19(e), CM-7, MP-2, 87

Description

The noexec mount option prevents the direct execution of binaries on the mounted filesystem. Preventing the direct execution of binaries from removable media (such as a USB key) provides a defense against malicious software that may be present on such untrusted media. Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of any removable media partitions.

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 Partitionsmount_option_nosuid_removable_partitions CCE-RHEL7-CCE-TBD

Add nosuid Option to Removable Media Partitions

Rule IDmount_option_nosuid_removable_partitions
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-19(a), AC-19(d), AC-19(e), CM-7, MP-2

Description

The nosuid mount option prevents set-user-identifier (SUID) and set-group-identifier (SGID) permissions from taking effect. These permissions allow users to execute binaries with the same permissions as the owner and group of the file respectively. Users should not be allowed to introduce SUID and SGID files into the system via partitions mounted from removeable media. Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of any removable media partitions.

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 /tmpmount_option_tmp_nodev CCE-RHEL7-CCE-TBD

Add nodev Option to /tmp

Rule IDmount_option_tmp_nodev
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, MP-2

Description

The nodev mount option can be used to prevent device files from being created in /tmp. Legitimate character and block devices should not exist within temporary directories like /tmp. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of /tmp.

Rationale

The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails.

Add noexec Option to /tmpmount_option_tmp_noexec CCE-RHEL7-CCE-TBD

Add noexec Option to /tmp

Rule IDmount_option_tmp_noexec
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, MP-2

Description

The noexec mount option can be used to prevent binaries from being executed out of /tmp. Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of /tmp.

Rationale

Allowing users to execute binaries from world-writable directories such as /tmp should never be necessary in normal operation and can expose the system to potential compromise.

Add nosuid Option to /tmpmount_option_tmp_nosuid CCE-RHEL7-CCE-TBD

Add nosuid Option to /tmp

Rule IDmount_option_tmp_nosuid
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, MP-2

Description

The nosuid mount option can be used to prevent execution of setuid programs in /tmp. The SUID and SGID permissions should not be required in these world-writable directories. Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of /tmp.

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/shmmount_option_dev_shm_nodev CCE-RHEL7-CCE-TBD

Add nodev Option to /dev/shm

Rule IDmount_option_dev_shm_nodev
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, MP-2

Description

The nodev mount option can be used to prevent creation of device files in /dev/shm. Legitimate character and block devices should not exist within temporary directories like /dev/shm. Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of /dev/shm.

Rationale

The only legitimate location for device files is the /dev directory located on the root partition. The only exception to this is chroot jails.

Add noexec Option to /dev/shmmount_option_dev_shm_noexec CCE-RHEL7-CCE-TBD

Add noexec Option to /dev/shm

Rule IDmount_option_dev_shm_noexec
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, MP-2

Description

The noexec mount option can be used to prevent binaries from being executed out of /dev/shm. It can be dangerous to allow the execution of binaries from world-writable temporary storage directories such as /dev/shm. Add the noexec option to the fourth column of /etc/fstab for the line which controls mounting of /dev/shm.

Rationale

Allowing users to execute binaries from world-writable directories such as /dev/shm can expose the system to potential compromise.

Add nosuid Option to /dev/shmmount_option_dev_shm_nosuid CCE-RHEL7-CCE-TBD

Add nosuid Option to /dev/shm

Rule IDmount_option_dev_shm_nosuid
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, MP-2

Description

The nosuid mount option can be used to prevent execution of setuid programs in /dev/shm. The SUID and SGID permissions should not be required in these world-writable directories. Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of /dev/shm.

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 /tmpmount_option_var_tmp_bind CCE-RHEL7-CCE-TBD

Bind Mount /var/tmp To /tmp

Rule IDmount_option_var_tmp_bind
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

The /var/tmp directory is a world-writable directory. Bind-mount it to /tmp in order to consolidate temporary storage into one location protected by the same techniques as /tmp. To do so, edit /etc/fstab and add the following line:

/tmp     /var/tmp     none     rw,nodev,noexec,nosuid,bind     0 0
See the mount(8) man page for further explanation of bind mounting.

Rationale

Having multiple locations for temporary storage is not required. Unless absolutely necessary to meet requirements, the storage location /var/tmp should be bind mounted to /tmp and thus share the same protections.

Disable Modprobe Loading of USB Storage Driverkernel_module_usb-storage_disabled CCE-RHEL7-CCE-TBD

Disable Modprobe Loading of USB Storage Driver

Rule IDkernel_module_usb-storage_disabled
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-19(a), AC-19(d), AC-19(e), 1250, 85

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 usb-storage kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install usb-storage /bin/true
This will prevent the modprobe program from loading the usb-storage module, but will not prevent an administrator (or another program) from using the insmod program to load the module manually.

Rationale

USB storage devices such as thumb drives can be used to introduce malicious software.

Disable Kernel Support for USB via Bootloader Configurationbootloader_nousb_argument CCE-RHEL7-CCE-TBD

Disable Kernel Support for USB via Bootloader Configuration

Rule IDbootloader_nousb_argument
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-19(a), AC-19(d), AC-19(e), 1250

Description

All USB support can be disabled by adding the nousb argument to the kernel's boot loader configuration. To do so, append "nousb" to the kernel line in /etc/grub.conf as shown:

kernel /vmlinuz-VERSION ro vga=ext root=/dev/VolGroup00/LogVol00 rhgb quiet nousb
WARNING: 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 Firmwarebios_disable_usb_boot CCE-RHEL7-CCE-TBD

Disable Booting from USB Devices in Boot Firmware

Rule IDbios_disable_usb_boot
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-19(a), AC-19(d), AC-19(e), 1250

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 Configurationbios_assign_password CCE-RHEL7-CCE-TBD

Assign Password to Prevent Changes to Boot Firmware Configuration

Rule IDbios_assign_password
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 Automounterservice_autofs_disabled CCE-RHEL7-CCE-TBD

Disable the Automounter

Rule IDservice_autofs_disabled
Result
pass
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-19(a), AC-19(d), AC-19(e), 1250, 85

Description

The autofs daemon mounts and unmounts filesystems, such as user home directories shared via NFS, on demand. In addition, autofs can be used to handle removable media, and the default configuration provides the cdrom device as /misc/cd. However, this method of providing access to removable media is not common, so autofs can almost always be disabled if NFS is not in use. Even if NFS is required, it may be possible to configure filesystem mounts statically by editing /etc/fstab rather than relying on the automounter.

The autofs service can be disabled with the following command:

$ sudo systemctl disable autofs

Rationale

Disabling the automounter permits the administrator to statically control filesystem mounting through /etc/fstab.

Disable GNOME3 Automountingdconf_gnome_disable_automount CCE-RHEL7-CCE-TBD

Disable GNOME3 Automounting

Rule IDdconf_gnome_disable_automount
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-19(a), AC-19(d), AC-19(e)

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 automount, automount-open, and autorun-never settings must be set under an appropriate configuration file(s) in the /etc/dconf/db/local.d directory and locked in /etc/dconf/db/local.d/locks directory to prevent user modification. After the settings have been set, run dconf update.

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 cramfskernel_module_cramfs_disabled CCE-RHEL7-CCE-TBD

Disable Mounting of cramfs

Rule IDkernel_module_cramfs_disabled
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To configure the system to prevent the cramfs kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install cramfs /bin/true
This effectively prevents usage of this uncommon filesystem.

Rationale

Linux kernel modules which implement filesystems that are not needed by the local system should be disabled.

Disable Mounting of freevxfskernel_module_freevxfs_disabled CCE-RHEL7-CCE-TBD

Disable Mounting of freevxfs

Rule IDkernel_module_freevxfs_disabled
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To configure the system to prevent the freevxfs kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install freevxfs /bin/true
This effectively prevents usage of this uncommon filesystem.

Rationale

Linux kernel modules which implement filesystems that are not needed by the local system should be disabled.

Disable Mounting of jffs2kernel_module_jffs2_disabled CCE-RHEL7-CCE-TBD

Disable Mounting of jffs2

Rule IDkernel_module_jffs2_disabled
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To configure the system to prevent the jffs2 kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install jffs2 /bin/true
This effectively prevents usage of this uncommon filesystem.

Rationale

Linux kernel modules which implement filesystems that are not needed by the local system should be disabled.

Disable Mounting of hfskernel_module_hfs_disabled CCE-RHEL7-CCE-TBD

Disable Mounting of hfs

Rule IDkernel_module_hfs_disabled
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To configure the system to prevent the hfs kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install hfs /bin/true
This effectively prevents usage of this uncommon filesystem.

Rationale

Linux kernel modules which implement filesystems that are not needed by the local system should be disabled.

Disable Mounting of hfspluskernel_module_hfsplus_disabled CCE-RHEL7-CCE-TBD

Disable Mounting of hfsplus

Rule IDkernel_module_hfsplus_disabled
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To configure the system to prevent the hfsplus kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install hfsplus /bin/true
This effectively prevents usage of this uncommon filesystem.

Rationale

Linux kernel modules which implement filesystems that are not needed by the local system should be disabled.

Disable Mounting of squashfskernel_module_squashfs_disabled CCE-RHEL7-CCE-TBD

Disable Mounting of squashfs

Rule IDkernel_module_squashfs_disabled
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To configure the system to prevent the squashfs kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install squashfs /bin/true
This effectively prevents usage of this uncommon filesystem.

Rationale

Linux kernel modules which implement filesystems that are not needed by the local system should be disabled.

Disable Mounting of udfkernel_module_udf_disabled CCE-RHEL7-CCE-TBD

Disable Mounting of udf

Rule IDkernel_module_udf_disabled
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To configure the system to prevent the udf kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install udf /bin/true
This effectively prevents usage of this uncommon filesystem.

Rationale

Linux kernel modules which implement filesystems that are not needed by the local system should be disabled.

Disable All GNOME3 Thumbnailersdconf_gnome_disable_thumbnailers CCE-RHEL7-CCE-TBD

Disable All GNOME3 Thumbnailers

Rule IDdconf_gnome_disable_thumbnailers
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 disable-all setting must be set under an appropriate configuration file(s) in the /etc/dconf/db/local.d directory and locked in /etc/dconf/db/local.d/locks directory to prevent user modification. After the settings have been set, run dconf update. This effectively prevents an attacker from gaining access to a system through a flaw in GNOME3's Nautilus thumbnail creators.

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 Fileuserowner_shadow_file CCE-26795-5

Verify User Who Owns shadow File

Rule IDuserowner_shadow_file
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/shadow, run the command:

$ sudo chown root /etc/shadow

Rationale

The /etc/shadow file contains the list of local system accounts and stores password hashes. Protection of this file is critical for system security. Failure to give ownership of this file to root provides the designated owner with access to sensitive information which could weaken the system security posture.

Verify Group Who Owns shadow Filegroupowner_shadow_file CCE-27125-4

Verify Group Who Owns shadow File

Rule IDgroupowner_shadow_file
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/shadow, run the command:

$ sudo chgrp root xsl:value-of select="@file"/> 

Rationale

The /etc/shadow file stores password hashes. Protection of this file is critical for system security.

Verify Permissions on shadow Filefile_permissions_etc_shadow CCE-27100-7

Verify Permissions on shadow File

Rule IDfile_permissions_etc_shadow
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-27100-7

references:  AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS

Description

To properly set the permissions of /etc/shadow, run the command:

$ sudo chmod 0000 /etc/shadow

Rationale

The /etc/shadow file contains the list of local system accounts and stores password hashes. Protection of this file is critical for system security. Failure to give ownership of this file to root provides the designated owner with access to sensitive information which could weaken the system security posture.

Verify User Who Owns group Filefile_owner_etc_group CCE-26933-2

Verify User Who Owns group File

Rule IDfile_owner_etc_group
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-26933-2

references:  AC-6, Test attestation on 20121026 by DS

Description

To properly set the owner of /etc/group, run the command:

$ sudo chown root /etc/group

Rationale

The /etc/group file contains information regarding groups that are configured on the system. Protection of this file is important for system security.

Verify Group Who Owns group Filefile_groupowner_etc_group CCE-27037-1

Verify Group Who Owns group File

Rule IDfile_groupowner_etc_group
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/group, run the command:

$ sudo chgrp root xsl:value-of select="@file"/> 

Rationale

The /etc/group file contains information regarding groups that are configured on the system. Protection of this file is important for system security.

Verify Permissions on group Filefile_permissions_etc_group CCE-26949-8

Verify Permissions on group File

Rule IDfile_permissions_etc_group
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-26949-8

references:  AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS

Description

To properly set the permissions of /etc/group, run the command:

$ sudo chmod 644 /etc/group

Rationale

The /etc/group file contains information regarding groups that are configured on the system. Protection of this file is important for system security.

Verify User Who Owns gshadow Filefile_owner_etc_gshadow CCE-27161-9

Verify User Who Owns gshadow File

Rule IDfile_owner_etc_gshadow
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/gshadow, run the command:

$ sudo chown root /etc/gshadow

Rationale

The /etc/gshadow file contains group password hashes. Protection of this file is critical for system security.

Verify Group Who Owns gshadow Filefile_groupowner_etc_gshadow CCE-26840-9

Verify Group Who Owns gshadow File

Rule IDfile_groupowner_etc_gshadow
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/gshadow, run the command:

$ sudo chgrp root xsl:value-of select="@file"/> 

Rationale

The /etc/gshadow file contains group password hashes. Protection of this file is critical for system security.

Verify Permissions on gshadow Filefile_permissions_etc_gshadow CCE-27162-7

Verify Permissions on gshadow File

Rule IDfile_permissions_etc_gshadow
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-27162-7

references:  AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS

Description

To properly set the permissions of /etc/gshadow, run the command:

$ sudo chmod 0000 /etc/gshadow

Rationale

The /etc/gshadow file contains group password hashes. Protection of this file is critical for system security.

Verify User Who Owns passwd Filefile_owner_etc_passwd CCE-27138-7

Verify User Who Owns passwd File

Rule IDfile_owner_etc_passwd
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/passwd, run the command:

$ sudo chown root /etc/passwd

Rationale

The /etc/passwd file contains information about the users that are configured on the system. Protection of this file is critical for system security.

Verify Group Who Owns passwd Filefile_groupowner_etc_passwd CCE-26639-5

Verify Group Who Owns passwd File

Rule IDfile_groupowner_etc_passwd
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/passwd, run the command:

$ sudo chgrp root xsl:value-of select="@file"/> 

Rationale

The /etc/passwd file contains information about the users that are configured on the system. Protection of this file is critical for system security.

Verify Permissions on passwd Filefile_permissions_etc_passwd CCE-26887-0

Verify Permissions on passwd File

Rule IDfile_permissions_etc_passwd
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-26887-0

references:  AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS

Description

To properly set the permissions of /etc/passwd, run the command:

$ sudo chmod 0644 /etc/passwd

Rationale

If the /etc/passwd file is writable by a group-owner or the world the risk of its compromise is increased. The file contains the list of accounts on the system and associated information, and protection of this file is critical for system security.

Verify that Shared Library Files Have Restrictive Permissionsfile_permissions_library_dirs CCE-26966-2

Verify that Shared Library Files Have Restrictive Permissions

Rule IDfile_permissions_library_dirs
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-26966-2

references:  AC-6, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS

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/lib64
Kernel modules, which can be added to the kernel during runtime, are stored in /lib/modules. All files in these directories should not be group-writable or world-writable. If any file in these directories is found to be group-writable or world-writable, correct its permission with the following command:
$ sudo chmod go-w FILE

Rationale

Files from shared library directories are loaded into the address space of processes (including privileged ones) or of the kernel itself at runtime. Restrictive permissions are necessary to protect the integrity of the system.

Verify that Shared Library Files Have Root Ownershipfile_ownership_library_dirs CCE-26648-6

Verify that Shared Library Files Have Root Ownership

Rule IDfile_ownership_library_dirs
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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/lib64
Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules. All files in these directories should be owned by the root user. If the directory, or any file in these directories, is found to be owned by a user other than root correct its ownership with the following command:
$ sudo chown root FILE

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 Restrictive Permissionsfile_permissions_binary_dirs CCE-27075-1

Verify that System Executables Have Restrictive Permissions

Rule IDfile_permissions_binary_dirs
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-27075-1

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/sbin
All files in these directories should not be group-writable or world-writable. If any file FILE in these directories is found to be group-writable or world-writable, correct its permission with the following command:
$ sudo chmod go-w FILE

Rationale

System binaries are executed by privileged users, as well as system services, and restrictive permissions are necessary to ensure execution of these programs cannot be co-opted.

Verify that System Executables Have Root Ownershipfile_ownership_binary_dirs CCE-27119-7

Verify that System Executables Have Root Ownership

Rule IDfile_ownership_binary_dirs
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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/sbin
All files in these directories should be owned by the root user. If any file FILE in these directories is found to be owned by a user other than root, correct its ownership with the following command:
$ sudo chown root FILE

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 Setsticky_world_writable_dirs CCE-RHEL7-CCE-TBD

Verify that All World-Writable Directories Have Sticky Bits Set

Rule IDsticky_world_writable_dirs
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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.
To set the sticky bit on a world-writable directory DIR, run the following command:

$ sudo chmod +t DIR

Rationale

Failing to set the sticky bit on public directories allows unauthorized users to delete files in the directory structure.

The only authorized public directories are those temporary directories supplied with the system, or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system, by users for temporary file storage (such as /tmp), and for directories requiring global read/write access.

Ensure No World-Writable Files Existworld_writeable_files CCE-RHEL7-CCE-TBD

Ensure No World-Writable Files Exist

Rule IDworld_writeable_files
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 SGID Executables Are Authorizedfile_permissions_unauthorized_sgid CCE-RHEL7-CCE-TBD

Ensure All SGID Executables Are Authorized

Rule IDfile_permissions_unauthorized_sgid
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf

Description

The SGID (set group id) bit should be set only on files that were installed via authorized means. A straightforward means of identifying unauthorized SGID files is determine if any were not installed as part of an RPM package, which is cryptographically verified. Investigate the origin of any unpackaged SGID files.

Rationale

Executable files with the SGID permission run with the privileges of the owner of the file. SGID files of uncertain provenance could allow for unprivileged users to elevate privileges. The presence of these files should be strictly controlled on the system.

Ensure All SUID Executables Are Authorizedfile_permissions_unauthorized_suid CCE-RHEL7-CCE-TBD

Ensure All SUID Executables Are Authorized

Rule IDfile_permissions_unauthorized_suid
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-6(1)

Description

The SUID (set user id) bit should be set only on files that were installed via authorized means. A straightforward means of identifying unauthorized SGID files is determine if any were not installed as part of an RPM package, which is cryptographically verified. Investigate the origin of any unpackaged SUID files.

Rationale

Executable files with the SUID permission run with the privileges of the owner of the file. SUID files of uncertain provenance could allow for unprivileged users to elevate privileges. The presence of these files should be strictly controlled on the system.

Ensure All Files Are Owned by a Userno_files_unowned_by_user CCE-RHEL7-CCE-TBD

Ensure All Files Are Owned by a User

Rule IDno_files_unowned_by_user
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-6, 224

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 Groupno_files_unowned_by_group CCE-RHEL7-CCE-TBD

Ensure All Files Are Owned by a Group

Rule IDno_files_unowned_by_group
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-6, 224

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 Accountworld_writable_files_system_ownership CCE-RHEL7-CCE-TBD

Ensure All World-Writable Directories Are Owned by a System Account

Rule IDworld_writable_files_system_ownership
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 Umaskumask_for_daemons CCE-RHEL7-CCE-TBD

Set Daemon Umask

Rule IDumask_for_daemons
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-6, Test attestation on 20140912 by JL

Description

The file /etc/init.d/functions includes initialization parameters for most or all daemons started at boot time. The default umask of 022 prevents creation of group- or world-writable files. To set the default umask for daemons, edit the following line, inserting 022 or 027 for UMASK appropriately:

umask UMASK
Setting the umask to too restrictive a setting can cause serious errors at runtime. Many daemons on the system already individually restrict themselves to a umask of 077 in their own init scripts.

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 Usersdisable_users_coredumps CCE-RHEL7-CCE-TBD

Disable Core Dumps for All Users

Rule IDdisable_users_coredumps
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  SC-5

Description

To disable core dumps for all users, add the following line to /etc/security/limits.conf:

*     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 programssysctl_fs_suid_dumpable CCE-RHEL7-CCE-TBD

Disable Core Dumps for SUID programs

Rule IDsysctl_fs_suid_dumpable
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  SI-11

Description

To set the runtime status of the fs.suid_dumpable kernel parameter, run the following command:

$ sudo sysctl -w fs.suid_dumpable=0
If 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 ExecShieldsysctl_kernel_exec_shield CCE-RHEL7-CCE-TBD

Enable ExecShield

Rule IDsysctl_kernel_exec_shield
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/default/grub. For Red Hat Enterprise Linux 7 32-bit systems, sysctl can be used to enable ExecShield.

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 Spacesysctl_kernel_randomize_va_space CCE-RHEL7-CCE-TBD

Enable Randomized Layout of Virtual Address Space

Rule IDsysctl_kernel_randomize_va_space
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 kernel.randomize_va_space kernel parameter, run the following command:

$ sudo sysctl -w kernel.randomize_va_space=2
If 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 Systemsinstall_PAE_kernel_on_x86-32 CCE-RHEL7-CCE-TBD

Install PAE Kernel on Supported 32-bit x86 Systems

Rule IDinstall_PAE_kernel_on_x86-32
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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-PAE
The 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 BIOSbios_enable_execution_restrictions CCE-RHEL7-CCE-TBD

Enable NX or XD Support in the BIOS

Rule IDbios_enable_execution_restrictions
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 Bufferenable_dmesg_restriction CCE-RHEL7-CCE-TBD

Restrict Access to Kernel Message Buffer

Rule IDenable_dmesg_restriction
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

Description

To set the runtime status of the kernel.dmesg_restrict kernel parameter, run the following command:

$ sudo sysctl -w kernel.dmesg_restrict=1
If 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.confenable_selinux_bootloader CCE-RHEL7-CCE-TBD

Ensure SELinux Not Disabled in /etc/grub.conf

Rule IDenable_selinux_bootloader
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/grub.conf. Remove any instances of selinux=0 from the kernel arguments in that file to prevent SELinux from being disabled at boot.

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 Enforcingselinux_state CCE-26800-3

Ensure SELinux State is Enforcing

Rule IDselinux_state
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 enforcing at system boot time. In the file /etc/selinux/config, add or correct the following line to configure the system to boot into enforcing mode:

SELINUX=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 Policyselinux_policytype CCE-27135-3

Configure SELinux Policy

Rule IDselinux_policytype
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 targeted policy is appropriate for general-purpose desktops and servers, as well as systems in many other roles. To configure the system to use this policy, add or correct the following line in /etc/selinux/config:

SELINUXTYPE=targeted
Other 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 targeted or a more specialized policy ensures the system will confine processes that are likely to be targeted for exploitation, such as network or system services. Note: During the development or debugging of SELinux modules, it is common to temporarily place non-production systems in permissive mode. In such temporary cases, SELinux policies should be developed, and once work is completed, the system should be reconfigured to targeted.

Uninstall setroubleshoot Packagepackage_setroubleshoot_removed CCE-

Uninstall setroubleshoot Package

Rule IDpackage_setroubleshoot_removed
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 setroubleshoot package can be removed with the following command:

$ sudo yum erase setroubleshoot

Rationale

The SETroubleshoot service is an unnecessary daemon to have running on a server

Uninstall mcstrans Packagepackage_mcstrans_removed CCE-

Uninstall mcstrans Package

Rule IDpackage_mcstrans_removed
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-

Description

The mcstransd daemon provides category label information to client processes requesting information. The label translations are defined in /etc/selinux/targeted/setrans.conf. The mcstrans package can be removed with the following command:

$ sudo yum erase mcstrans

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 SELinuxselinux_confinement_of_daemons CCE-RHEL7-CCE-TBD

Ensure No Daemons are Unconfined by SELinux

Rule IDselinux_confinement_of_daemons
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-6, AU-9, CM-7

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 init process, they inherit the initrc_t context.

To check for unconfined daemons, run the following command:

$ sudo ps -eZ | egrep "initrc" | egrep -vw "tr|ps|egrep|bash|awk" | tr ':' ' ' | awk '{ print $NF }'
It should produce no output in a well-configured system.

Rationale

Daemons which run with the initrc_t context may cause AVC denials, or allow privileges that the daemon does not require.

Ensure No Device Files are Unlabeled by SELinuxselinux_all_devicefiles_labeled CCE-RHEL7-CCE-TBD

Ensure No Device Files are Unlabeled by SELinux

Rule IDselinux_all_devicefiles_labeled
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 unlabeled_t, investigate the cause and correct the file's context.

Rationale

If a device file carries the SELinux type unlabeled_t, then SELinux cannot properly restrict access to the device file.

Direct root Logins Not Allowedno_direct_root_logins CCE-RHEL7-CCE-TBD

Direct root Logins Not Allowed

Rule IDno_direct_root_logins
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 root account, administrators can disable root logins at the console by editing the /etc/securetty file. This file lists all devices the root user is allowed to login to. If the file does not exist at all, the root user can login through any communication device on the system, whether via the console or via a raw network interface. This is dangerous as user can login to his machine as root via Telnet, which sends the password in plain text over the network. By default, Red Hat Enteprise Linux's /etc/securetty file only allows the root user to login at the console physically attached to the machine. To prevent root from logging in, remove the contents of this file. To prevent direct root logins, remove the contents of this file by typing the following command:

$ 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 Serial Port Root Loginsrestrict_serial_port_logins CCE-RHEL7-CCE-TBD

Restrict Serial Port Root Logins

Rule IDrestrict_serial_port_logins
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 /etc/securetty:

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 Accountsno_root_webbrowsing CCE-RHEL7-CCE-TBD

Restrict Web Browser Use for Administrative Accounts

Rule IDno_root_webbrowsing
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 Loginno_shelllogin_for_systemaccounts CCE-26448-1

Ensure that System Accounts Do Not Run a Shell Upon Login

Rule IDno_shelllogin_for_systemaccounts
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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.

The login shell for each local account is stored in the last field of each line in /etc/passwd. System accounts are those user accounts with a user ID less than 1000. The user ID is stored in the third field. If any system account SYSACCT (other than root) has a login shell, disable it with the command:

$ sudo usermod -s /sbin/nologin SYSACCT

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 0accounts_no_uid_except_zero CCE-27175-9

Verify Only Root Has UID 0

Rule IDaccounts_no_uid_except_zero
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 Defaultroot_path_default CCE-RHEL7-CCE-TBD

Root Path Must Be Vendor Default

Rule IDroot_path_default
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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
~/.bashrc
Change 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 Passwordno_empty_passwords CCE-27010-8

Prevent Log In to Accounts With Empty Password

Rule IDno_empty_passwords
Result
notselected
Time2015-07-17T10:50:20
Severityhigh
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 nullok option in /etc/pam.d/system-auth to prevent logins with empty passwords.

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 Shadowedaccounts_password_all_shadowed CCE-27144-5

Verify All Account Password Hashes are Shadowed

Rule IDaccounts_password_all_shadowed
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/passwd (in the second field, instead of an x), the cause of this misconfiguration should be investigated. The account should have its password reset and the hash should be properly stored, or the account should be deleted entirely.

Rationale

The hashes for all user account passwords should be stored in the file /etc/shadow and never in /etc/passwd, which is readable by all users.

All GIDs referenced in /etc/passwd must be defined in /etc/groupgid_passwd_group_same CCE-RHEL7-CCE-TBD

All GIDs referenced in /etc/passwd must be defined in /etc/group

Rule IDgid_passwd_group_same
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 /etc/passwd and /etc/group could lead to a user having unintended rights.

Verify No netrc Files Existno_netrc_files CCE-RHEL7-CCE-TBD

Verify No netrc Files Exist

Rule IDno_netrc_files
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  IA-5(h), AC-3, 196

Description

The .netrc files contain login information used to auto-login into FTP servers and reside in the user's home directory. These files may contain unencrypted passwords to remote FTP servers making them susceptible to access by unauthorized users and should not be used. Any .netrc files should be removed.

Rationale

Unencrypted passwords for remote FTP servers may be stored in .netrc files. DoD policy requires passwords be encrypted in storage and not used in access scripts.

Set Password Retry Prompts Permitted Per-Sessionaccounts_password_pam_retry CCE-27131-2

Set Password Retry Prompts Permitted Per-Session

Rule IDaccounts_password_pam_retry
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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:

Edit the pam_pwquality.so statement in /etc/pam.d/system-auth to show retry=3, or a lower value if site policy is more restrictive.

The DoD requirement is a maximum of 3 prompts 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 Charactersaccounts_password_pam_maxrepeat CCE-RHEL7-CCE-TBD

Set Password to Maximum of Three Consecutive Repeating Characters

Rule IDaccounts_password_pam_maxrepeat
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  IA-5(c), 366

Description

The pam_pwquality module's maxrepeat parameter controls requirements for consecutive repeating characters. When set to a positive number, it will reject passwords which contain more than that number of consecutive characters. Modify the maxrepeat setting in /etc/security/pwquality.conf to prevent a run of (3 + 1) or more identical characters.

Rationale

Passwords with excessive repeating characters may be more vulnerable to password-guessing attacks.

Set Password Strength Minimum Digit Charactersaccounts_password_pam_dcredit CCE-27163-5

Set Password Strength Minimum Digit Characters

Rule IDaccounts_password_pam_dcredit
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 dcredit parameter controls requirements for usage of digits in a password. When set to a negative number, any password will be required to contain that many digits. When set to a positive number, pam_pwquality will grant +1 additional length credit for each digit. Modify the dcredit setting in /etc/security/pwquality.conf to require the use of a digit in passwords.

Rationale

Requiring digits makes password guessing attacks more difficult by ensuring a larger search space.

Set Password Minimum Lengthaccounts_password_pam_minlen CCE-26615-5

Set Password Minimum Length

Rule IDaccounts_password_pam_minlen
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 minlen parameter controls requirements for minimum characters required in a password. Add minlen=15 after pam_pwquality to set minimum password length requirements.

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 Charactersaccounts_password_pam_ucredit CCE-26988-6

Set Password Strength Minimum Uppercase Characters

Rule IDaccounts_password_pam_ucredit
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 ucredit= parameter controls requirements for usage of uppercase letters in a password. When set to a negative number, any password will be required to contain that many uppercase characters. When set to a positive number, pam_pwquality will grant +1 additional length credit for each uppercase character. Modify the ucredit setting in /etc/security/pwquality.conf to require the use of an uppercase character in passwords.

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 Charactersaccounts_password_pam_ocredit CCE-27151-0

Set Password Strength Minimum Special Characters

Rule IDaccounts_password_pam_ocredit
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 ocredit= parameter controls requirements for usage of special (or "other") characters in a password. When set to a negative number, any password will be required to contain that many special characters. When set to a positive number, pam_pwquality will grant +1 additional length credit for each special character. Modify the ocredit setting in /etc/security/pwquality.conf to require use of a special character in passwords.

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 Charactersaccounts_password_pam_lcredit CCE-27111-4

Set Password Strength Minimum Lowercase Characters

Rule IDaccounts_password_pam_lcredit
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 lcredit parameter controls requirements for usage of lowercase letters in a password. When set to a negative number, any password will be required to contain that many lowercase characters. When set to a positive number, pam_pwquality will grant +1 additional length credit for each lowercase character. Modify the lcredit setting in /etc/security/pwquality.conf to require the use of a lowercase character in passwords.

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 Charactersaccounts_password_pam_difok CCE-26631-2

Set Password Strength Minimum Different Characters

Rule IDaccounts_password_pam_difok
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 difok parameter controls requirements for usage of different characters during a password change. Modify the difok setting in /etc/security/pwquality.conf to require differing characters when changing passwords. The DoD requirement is 4.

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 Categoriesaccounts_password_pam_minclass CCE-27115-5

Set Password Strength Minimum Different Categories

Rule IDaccounts_password_pam_minclass
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-27115-5

references:  Test attestation on 20140626 by JL

Description

The pam_pwquality module's minclass parameter controls requirements for usage of different character classes, or types, of character that must exist in a password before it is considered valid. For example, setting this value to three (3) requires that any password must have characters from at least three different categories in order to be approved. The default value is zero (0), meaning there are no required classes. There are four categories available:

* Upper-case characters
* Lower-case characters
* Digits
* Special characters (for example, punctuation)
Modify the minclass setting in /etc/security/pwquality.conf entry to require differing categories of characters when changing passwords. 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 Attemptsaccounts_passwords_pam_faillock_deny CCE-26891-2

Set Deny For Failed Password Attempts

Rule IDaccounts_passwords_pam_faillock_deny
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-26891-2

references:  AC-7(a), 44, 21

Description

To configure the system to lock out accounts after a number of incorrect login attempts using pam_faillock.so, modify the content of both /etc/pam.d/system-auth and /etc/pam.d/password-auth as follows:

  • add the following line immediately before the pam_unix.so statement in the AUTH section:
    auth required pam_faillock.so preauth silent deny=3 unlock_time=604800 fail_interval=900
  • add the following line immediately after the pam_unix.so statement in the AUTH section:
    auth [default=die] pam_faillock.so authfail deny=3 unlock_time=604800 fail_interval=900
  • add the following line immediately before the pam_unix.so statement in the ACCOUNT section:
    account required pam_faillock.so

Rationale

Locking out user accounts after a number of incorrect attempts prevents direct password guessing attacks.

Set Lockout Time For Failed Password Attemptsaccounts_passwords_pam_faillock_unlock_time CCE-26884-7

Set Lockout Time For Failed Password Attempts

Rule IDaccounts_passwords_pam_faillock_unlock_time
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-26884-7

references:  AC-7(b), 47

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 pam_faillock.so, modify the content of both /etc/pam.d/system-auth and /etc/pam.d/password-auth as follows:

  • add the following line immediately before the pam_unix.so statement in the AUTH section:
    auth required pam_faillock.so preauth silent deny=3 unlock_time=604800 fail_interval=900
  • add the following line immediately after the pam_unix.so statement in the AUTH section:
    auth [default=die] pam_faillock.so authfail deny=3 unlock_time=604800 fail_interval=900
  • add the following line immediately before the pam_unix.so statement in the ACCOUNT section:
    account required pam_faillock.so

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 Attemptsaccounts_passwords_pam_faillock_interval CCE-26763-3

Set Interval For Counting Failed Password Attempts

Rule IDaccounts_passwords_pam_faillock_interval
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-26763-3

references:  AC-7(a), 44, 21

Description

Utilizing pam_faillock.so, the fail_interval directive configures the system to lock out accounts after a number of incorrect login attempts. Modify the content of both /etc/pam.d/system-auth and /etc/pam.d/password-auth as follows:

  • add the following line immediately before the pam_unix.so statement in the AUTH section:
    auth required pam_faillock.so preauth silent deny=3 unlock_time=604800 fail_interval=900
  • add the following line immediately after the pam_unix.so statement in the AUTH section:
    auth [default=die] pam_faillock.so authfail deny=3 unlock_time=604800 fail_interval=900
  • add the following line immediately before the pam_unix.so statement in the ACCOUNT section:
    account required pam_faillock.so

Rationale

Locking out user accounts after a number of incorrect attempts within a specific period of time prevents direct password guessing attacks.

Limit Password Reuseaccounts_password_pam_unix_remember CCE-26923-3

Limit Password Reuse

Rule IDaccounts_password_pam_unix_remember
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 remember option for the pam_unix PAM module. In the file /etc/pam.d/system-auth, append remember=5 to the line which refers to the pam_unix.so module, as shown:

password sufficient pam_unix.so existing_options remember=5
The 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-authset_password_hashing_algorithm_systemauth CCE-27104-9

Set Password Hashing Algorithm in /etc/pam.d/system-auth

Rule IDset_password_hashing_algorithm_systemauth
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/pam.d/system-auth, the password section of the file controls which PAM modules execute during a password change. Set the pam_unix.so module in the password section to include the argument sha512, as shown below:

password    sufficient    pam_unix.so sha512 other arguments...
This will help ensure when local users change their passwords, hashes for the new passwords will be generated using the SHA-512 algorithm. This is the default.

Rationale

Using a stronger hashing algorithm makes password cracking attacks more difficult.

Set Password Hashing Algorithm in /etc/login.defsset_password_hashing_algorithm_logindefs CCE-27124-7

Set Password Hashing Algorithm in /etc/login.defs

Rule IDset_password_hashing_algorithm_logindefs
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/login.defs, add or correct the following line to ensure the system will use SHA-512 as the hashing algorithm:

ENCRYPT_METHOD SHA512

Rationale

Using a stronger hashing algorithm makes password cracking attacks more difficult.

Set Password Hashing Algorithm in /etc/libuser.confset_password_hashing_algorithm_libuserconf CCE-27053-8

Set Password Hashing Algorithm in /etc/libuser.conf

Rule IDset_password_hashing_algorithm_libuserconf
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/libuser.conf, add or correct the following line in its [defaults] section to ensure the system will use the SHA-512 algorithm for password hashing:

crypt_style = sha512

Rationale

Using a stronger hashing algorithm makes password cracking attacks more difficult.

Ensure that Root's Path Does Not Include Relative Paths or Null Directoriesroot_path_no_dot CCE-RHEL7-CCE-TBD

Ensure that Root's Path Does Not Include Relative Paths or Null Directories

Rule IDroot_path_no_dot
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 . character, or that it contains any instances that lead to relative path traversal, such as .. or beginning a path without the slash (/) character. Also ensure that there are no "empty" elements in the path, such as in these examples:

PATH=:/bin
PATH=/bin:
PATH=/bin::/sbin
These empty elements have the same effect as a single . character.

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 Directoriesroot_path_no_groupother_writable CCE-RHEL7-CCE-TBD

Ensure that Root's Path Does Not Include World or Group-Writable Directories

Rule IDroot_path_no_groupother_writable
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 DIR
and 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 Correctlyaccounts_umask_bashrc CCE-RHEL7-CCE-TBD

Ensure the Default Bash Umask is Set Correctly

Rule IDaccounts_umask_bashrc
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 setting in /etc/bashrc to read as follows:

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 Correctlyaccounts_umask_cshrc CCE-RHEL7-CCE-TBD

Ensure the Default C Shell Umask is Set Correctly

Rule IDaccounts_umask_cshrc
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 setting in /etc/csh.cshrc to read as follows:

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/profileaccounts_umask_etc_profile CCE-RHEL7-CCE-TBD

Ensure the Default Umask is Set Correctly in /etc/profile

Rule IDaccounts_umask_etc_profile
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 /etc/profile is set properly, add or correct the umask setting in /etc/profile to read as follows:

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 that User Home Directories are not Group-Writable or World-Readablehomedir_perms_no_groupwrite_worldread CCE-RHEL7-CCE-TBD

Ensure that User Home Directories are not Group-Writable or World-Readable

Rule IDhomedir_perms_no_groupwrite_worldread
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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/USER
Ensure that the directory is not group-writable and that it is not world-readable. If necessary, repair the permissions:
# chmod g-w /home/USER
# chmod o-rwx /home/USER

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 Ownershipfile_user_owner_grub2_cfg CCE-26860-7

Verify /boot/grub2/grub.cfg User Ownership

Rule IDfile_user_owner_grub2_cfg
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /boot/grub2/grub.cfg should be owned by the root user to prevent destruction or modification of the file. To properly set the owner of /boot/grub2/grub.cfg, run the command:

$ sudo chown root /boot/grub2/grub.cfg

Rationale

Only root should be able to modify important boot parameters.

Verify /boot/grub2/grub.cfg Group Ownershipfile_group_owner_grub2_cfg CCE-26812-8

Verify /boot/grub2/grub.cfg Group Ownership

Rule IDfile_group_owner_grub2_cfg
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /boot/grub2/grub.cfg should be group-owned by the root group to prevent destruction or modification of the file. To properly set the group owner of /boot/grub2/grub.cfg, run the command:

$ sudo chgrp root xsl:value-of select="@file"/> 

Rationale

The root group is a highly-privileged group. Furthermore, the group-owner of this file should not have any access privileges anyway.

Verify /boot/grub2/grub.cfg Permissionsfile_permissions_grub2_cfg CCE-27054-6

Verify /boot/grub2/grub.cfg Permissions

Rule IDfile_permissions_grub2_cfg
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-27054-6

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

File permissions for /boot/grub2/grub.cfg should be set to 600. To properly set the permissions of /boot/grub2/grub.cfg, run the command:

$ sudo chmod 600 /boot/grub2/grub.cfg

Rationale

Proper permissions ensure that only the root user can modify important boot parameters.

Set Boot Loader Passwordbootloader_password CCE-26809-4

Set Boot Loader Password

Rule IDbootloader_password
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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.

To do so, select a superuser account and password and add them into the appropriate grub2 configuration file(s) under /etc/grub.d. Since plaintext passwords are a security risk, generate a hash for the pasword by running the following command:

$ grub2-mkpasswd-pbkdf2
When 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-hash
NOTE: 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.cfg
NOTE: 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

  • https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html
  • .

Set GNOME3 Screensaver Inactivity Timeoutdconf_gnome_screensaver_idle_delay CCE-RHEL7-CCE-TBD

Set GNOME3 Screensaver Inactivity Timeout

Rule IDdconf_gnome_screensaver_idle_delay
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-11(a), 57

Description

To set the idle time-out value for inactivity in the GNOME3 desktop to 5 minutes (in seconds), the idle-delay setting must be set under an appropriate configuration file(s) in the /etc/dconf/db/local.d directory and locked in /etc/dconf/db/local.d/locks directory to prevent user modification. After the settings have been set, run dconf update.

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 Activationdconf_gnome_screensaver_idle_activation_enabled CCE-RHEL7-CCE-TBD

Enable GNOME3 Screensaver Idle Activation

Rule IDdconf_gnome_screensaver_idle_activation_enabled
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-11(a), 57

Description

To activate the screensaver in the GNOME3 desktop after a period of inactivity, the idle-activation-enabled setting must be set under an appropriate configuration file(s) in the /etc/dconf/db/local.d directory and locked in /etc/dconf/db/local.d/locks directory to prevent user modification. After the settings have been set, run dconf update.

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 Perioddconf_gnome_screensaver_lock_enabled CCE-RHEL7-CCE-TBD

Enable GNOME3 Screensaver Lock After Idle Period

Rule IDdconf_gnome_screensaver_lock_enabled
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-11(a), 57

Description

To activate locking of the screensaver in the GNOME3 desktop when it is activated, the lock-enabled and lock-delay setting must be set under an appropriate configuration file(s) in the /etc/dconf/db/local.d directory and locked in /etc/dconf/db/local.d/locks directory to prevent user modification. After the settings have been set, run dconf update.

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 Screensaverdconf_gnome_screensaver_mode_blank CCE-RHEL7-CCE-TBD

Implement Blank Screensaver

Rule IDdconf_gnome_screensaver_mode_blank
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-11(b), 60

Description

To set the screensaver mode in the GNOME3 desktop to a blank screen, the picture-uri setting must be set under an appropriate configuration file(s) in the /etc/dconf/db/local.d directory and locked in /etc/dconf/db/local.d/locks directory to prevent user modification. After the settings have been set, run dconf update.

Rationale

Setting the screensaver mode to blank-only conceals the contents of the display from passersby.

Install the screen Packagepackage_screen_installed CCE-RHEL7-CCE-TBD

Install the screen Package

Rule IDpackage_screen_installed
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  58, Test attestation on 20121026 by DS

Description

To enable console screen locking, install the screen package:

$ sudo yum install screen
Instruct users to begin new terminal sessions with the following command:
$ screen
The console can now be locked with the following key combination:
ctrl+a x

Rationale

Installing screen ensures a console locking capability is available for users who may need to suspend console logins.

Enable Smart Card Loginsmartcard_auth CCE-RHEL7-CCE-TBD

Enable Smart Card Login

Rule IDsmartcard_auth
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  765, 766, 767, 768, 771, 772, 884

Description

To enable smart card authentication, consult the documentation at:

  • https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Managing_Smart_Cards/enabling-smart-card-login.html
For guidance on enabling SSH to authenticate against a Common Access Card (CAC), consult documentation at:
  • https://access.redhat.com/solutions/82273

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 Moderequire_singleuser_auth CCE-27170-0

Require Authentication for Single User Mode

Rule IDrequire_singleuser_auth
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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.

By default, single-user mode is protected by requiring a password and is set in /usr/lib/systemd/system/rescue.service.

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 Activationdisable_ctrlaltdel_reboot CCE-RHEL7-CCE-TBD

Disable Ctrl-Alt-Del Reboot Activation

Rule IDdisable_ctrlaltdel_reboot
Result
notselected
Time2015-07-17T10:50:20
Severityhigh
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

Description

By default, the system includes the following line in /etc/init/control-alt-delete.conf to reboot the system when the Ctrl-Alt-Del key sequence is pressed:

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 Bootdisable_interactive_boot CCE-RHEL7-CCE-TBD

Disable Interactive Boot

Rule IDdisable_interactive_boot
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/sysconfig/init. Add or correct the line:

PROMPT=no
The 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.

Enable GNOME3 Login Warning Bannerdconf_gnome_banner_enabled CCE-26970-4

Enable GNOME3 Login Warning Banner

Rule IDdconf_gnome_banner_enabled
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-26970-4

references:  AC-8(a), AC-8(b), AC-8(c), 48, 50, 23

Description

To enable displaying a login warning banner in the GNOME Display Manager's login screen, the banner-message-enable setting must be set under an appropriate configuration file(s) in the /etc/dconf/db/gdm.d directory and locked in /etc/dconf/db/gdm.d/locks directory to prevent user modification. After the settings have been set, run dconf update. To display a banner, this setting must be enabled, and the user must be prevented from making changes. The banner text must also be set.

Rationale

An appropriate warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers.

Modify the System Login Bannerbanner_etc_issue CCE-27303-7

Modify the System Login Banner

Rule IDbanner_etc_issue
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-27303-7

references:  AC-8(a), AC-8(b), AC-8(c)(1), AC-8(c)(2), AC-8(c)(3), 48, 50, 1384, 1385, 1386, 1387, 1388, 23, 228, Test attestation on 20121026 by DS

Description

To configure the system login banner:

Edit /etc/issue. Replace the default text with a message compliant with the local site policy or a legal disclaimer. The DoD required text is either:

You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions:
-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
-At any time, the USG may inspect and seize data stored on this IS.
-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
-This IS includes security measures (e.g., authentication and access controls) to protect USG interests -- not for your personal benefit or privacy.
-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.


OR:

I've read & consent to terms in IS user agreem't.

Rationale

An appropriate warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers.

Disable the GNOME3 Login User Listdconf_gnome_disable_user_list CCE-RHEL7-CCE-TBD

Disable the GNOME3 Login User List

Rule IDdconf_gnome_disable_user_list
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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.

The disable-user-list setting must be set under an appropriate configuration file(s) in the /etc/dconf/db/gdm.d directory and locked in /etc/dconf/db/gdm.d/locks directory to prevent user modification. After the settings have been set, run dconf update.

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 Defaultsysctl_net_ipv4_conf_default_send_redirects CCE-RHEL7-CCE-TBD

Disable Kernel Parameter for Sending ICMP Redirects by Default

Rule IDsysctl_net_ipv4_conf_default_send_redirects
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 net.ipv4.conf.default.send_redirects kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.conf.default.send_redirects=0
If 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 Interfacessysctl_net_ipv4_conf_all_send_redirects CCE-RHEL7-CCE-TBD

Disable Kernel Parameter for Sending ICMP Redirects for All Interfaces

Rule IDsysctl_net_ipv4_conf_all_send_redirects
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 net.ipv4.conf.all.send_redirects kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.conf.all.send_redirects=0
If 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 Forwardingsysctl_ipv4_ip_forward CCE-RHEL7-CCE-TBD

Disable Kernel Parameter for IP Forwarding

Rule IDsysctl_ipv4_ip_forward
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 net.ipv4.ip_forward kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.ip_forward=0
If 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 Interfacessysctl_net_ipv4_conf_all_accept_source_route CCE-RHEL7-CCE-TBD

Disable Kernel Parameter for Accepting Source-Routed Packets for All Interfaces

Rule IDsysctl_net_ipv4_conf_all_accept_source_route
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 net.ipv4.conf.all.accept_source_route kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.conf.all.accept_source_route=0
If 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 Interfacessysctl_net_ipv4_conf_all_accept_redirects CCE-RHEL7-CCE-TBD

Disable Kernel Parameter for Accepting ICMP Redirects for All Interfaces

Rule IDsysctl_net_ipv4_conf_all_accept_redirects
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 net.ipv4.conf.all.accept_redirects kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.conf.all.accept_redirects=0
If 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 Interfacessysctl_net_ipv4_conf_all_secure_redirects CCE-RHEL7-CCE-TBD

Disable Kernel Parameter for Accepting Secure Redirects for All Interfaces

Rule IDsysctl_net_ipv4_conf_all_secure_redirects
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 net.ipv4.conf.all.secure_redirects kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.conf.all.secure_redirects=0
If 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 Packetssysctl_net_ipv4_conf_all_log_martians CCE-RHEL7-CCE-TBD

Enable Kernel Parameter to Log Martian Packets

Rule IDsysctl_net_ipv4_conf_all_log_martians
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 net.ipv4.conf.all.log_martians kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.conf.all.log_martians=1
If 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 Defaultsysctl_net_ipv4_conf_default_accept_source_route CCE-RHEL7-CCE-TBD

Disable Kernel Parameter for Accepting Source-Routed Packets By Default

Rule IDsysctl_net_ipv4_conf_default_accept_source_route
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 net.ipv4.conf.default.accept_source_route kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.conf.default.accept_source_route=0
If 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 Defaultsysctl_net_ipv4_conf_default_accept_redirects CCE-RHEL7-CCE-TBD

Disable Kernel Parameter for Accepting ICMP Redirects By Default

Rule IDsysctl_net_ipv4_conf_default_accept_redirects
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 net.ipv4.conf.default.accept_redirects kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.conf.default.accept_redirects=0
If 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 Defaultsysctl_net_ipv4_conf_default_secure_redirects CCE-RHEL7-CCE-TBD

Disable Kernel Parameter for Accepting Secure Redirects By Default

Rule IDsysctl_net_ipv4_conf_default_secure_redirects
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 net.ipv4.conf.default.secure_redirects kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.conf.default.secure_redirects=0
If 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 Requestssysctl_net_ipv4_icmp_echo_ignore_broadcasts CCE-RHEL7-CCE-TBD

Enable Kernel Parameter to Ignore ICMP Broadcast Echo Requests

Rule IDsysctl_net_ipv4_icmp_echo_ignore_broadcasts
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 net.ipv4.icmp_echo_ignore_broadcasts kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1
If 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 Responsessysctl_net_ipv4_icmp_ignore_bogus_error_responses CCE-RHEL7-CCE-TBD

Enable Kernel Parameter to Ignore Bogus ICMP Error Responses

Rule IDsysctl_net_ipv4_icmp_ignore_bogus_error_responses
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 net.ipv4.icmp_ignore_bogus_error_responses kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1
If 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 TCP Syncookiessysctl_net_ipv4_tcp_syncookies CCE-RHEL7-CCE-TBD

Enable Kernel Parameter to Use TCP Syncookies

Rule IDsysctl_net_ipv4_tcp_syncookies
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-4, SC-5(2), SC-5(3), 1092, 1095, Test attestation on 20121024 by DS

Description

To set the runtime status of the net.ipv4.tcp_syncookies kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.tcp_syncookies=1
If this is not the system's default value, add the following line to /etc/sysctl.conf:
net.ipv4.tcp_syncookies = 1

Rationale

A TCP SYN flood attack can cause a denial of service by filling a system's TCP connection table with connections in the SYN_RCVD state. Syncookies can be used to track a connection when a subsequent ACK is received, verifying the initiator is attempting a valid connection and is not a flood source. This feature is activated when a flood condition is detected, and enables the system to continue servicing valid connection requests.

Enable Kernel Parameter to Use Reverse Path Filtering for All Interfacessysctl_net_ipv4_conf_all_rp_filter CCE-RHEL7-CCE-TBD

Enable Kernel Parameter to Use Reverse Path Filtering for All Interfaces

Rule IDsysctl_net_ipv4_conf_all_rp_filter
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 net.ipv4.conf.all.rp_filter kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.conf.all.rp_filter=1
If 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 Defaultsysctl_net_ipv4_conf_default_rp_filter CCE-RHEL7-CCE-TBD

Enable Kernel Parameter to Use Reverse Path Filtering by Default

Rule IDsysctl_net_ipv4_conf_default_rp_filter
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 net.ipv4.conf.default.rp_filter kernel parameter, run the following command:

$ sudo sysctl -w net.ipv4.conf.default.rp_filter=1
If 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 BIOSwireless_disable_in_bios CCE-RHEL7-CCE-TBD

Disable WiFi or Bluetooth in BIOS

Rule IDwireless_disable_in_bios
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 Interfacesdeactivate_wireless_interfaces CCE-RHEL7-CCE-TBD

Deactivate Wireless Network Interfaces

Rule IDdeactivate_wireless_interfaces
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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.

First, identify the interfaces available with the command:

$ ifconfig -a
Additionally, the following command may be used to determine whether wireless support is included for a particular interface, though this may not always be a clear indicator:
$ iwconfig
After identifying any wireless interfaces (which may have names like wlan0, ath0, wifi0, em1 or eth0), deactivate the interface with the command:
$ sudo ifdown interface
These 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 Serviceservice_bluetooth_disabled CCE-RHEL7-CCE-TBD

Disable Bluetooth Service

Rule IDservice_bluetooth_disabled
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 bluetooth service can be disabled with the following command:

$ sudo systemctl disable bluetooth
$ sudo service bluetooth stop

Rationale

Disabling the bluetooth service prevents the system from attempting connections to Bluetooth devices, which entails some security risk. Nevertheless, variation in this risk decision may be expected due to the utility of Bluetooth connectivity and its limited range.

Disable Bluetooth Kernel Moduleskernel_module_bluetooth_disabled CCE-RHEL7-CCE-TBD

Disable Bluetooth Kernel Modules

Rule IDkernel_module_bluetooth_disabled
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 /etc/modprobe.d configuration file to prevent the loading of the Bluetooth module:

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 Loadingsysctl_kernel_ipv6_disable CCE-RHEL7-CCE-TBD

Disable IPv6 Networking Support Automatic Loading

Rule IDsysctl_kernel_ipv6_disable
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 1551, Test attestation on 20121024 by DS

Description

To disable support for (ipv6) add the following line to /etc/sysctl.d/ipv6.conf (or another file in /etc/sysctl.d):

net.ipv6.conf.all.disable_ipv6 = 1
This disables IPv6 on all network interfaces as other services and system functionality require the IPv6 stack loaded to work.

Rationale

Any unnecessary network stacks - including IPv6 - should be disabled, to reduce the vulnerability to exploitation.

Disable Interface Usage of IPv6network_ipv6_disable_interfaces CCE-RHEL7-CCE-TBD

Disable Interface Usage of IPv6

Rule IDnetwork_ipv6_disable_interfaces
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

Description

To disable interface usage of IPv6, add or correct the following lines in /etc/sysconfig/network:

NETWORKING_IPV6=no
IPV6INIT=no

Disable Support for RPC IPv6network_ipv6_disable_rpc CCE-RHEL7-CCE-TBD

Disable Support for RPC IPv6

Rule IDnetwork_ipv6_disable_rpc
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

RPC services for NFSv4 try to load transport modules for udp6 and tcp6 by default, even if IPv6 has been disabled in /etc/modprobe.d. To prevent RPC services such as rpc.mountd from attempting to start IPv6 network listeners, remove or comment out the following two lines in /etc/netconfig:

udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -

Disable Accepting IPv6 Router Advertisementssysctl_net_ipv6_conf_default_accept_ra CCE-RHEL7-CCE-TBD

Disable Accepting IPv6 Router Advertisements

Rule IDsysctl_net_ipv6_conf_default_accept_ra
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To set the runtime status of the net.ipv6.conf.default.accept_ra kernel parameter, run the following command:

$ sudo sysctl -w net.ipv6.conf.default.accept_ra=0
If 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 Redirectssysctl_net_ipv6_conf_default_accept_redirects CCE-RHEL7-CCE-TBD

Disable Accepting IPv6 Redirects

Rule IDsysctl_net_ipv6_conf_default_accept_redirects
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 1551

Description

To set the runtime status of the net.ipv6.conf.default.accept_redirects kernel parameter, run the following command:

$ sudo sysctl -w net.ipv6.conf.default.accept_redirects=0
If 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 Addressnetwork_ipv6_static_address CCE-RHEL7-CCE-TBD

Manually Assign Global IPv6 Address

Rule IDnetwork_ipv6_static_address
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 /etc/sysconfig/network-scripts/ifcfg-interface. Add or correct the following line (substituting the correct IPv6 address):

IPV6ADDR=2001:0DB8::ABCD/64
Manually assigning an IP address is preferable to accepting one from routers or from the network otherwise. The example address here is an IPv6 address reserved for documentation purposes, as defined by RFC3849.

Use Privacy Extensions for Addressnetwork_ipv6_privacy_extensions CCE-RHEL7-CCE-TBD

Use Privacy Extensions for Address

Rule IDnetwork_ipv6_privacy_extensions
Result
notselected
Time2015-07-17T10:50:20
Severitylow
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 /etc/sysconfig/network-scripts/ifcfg-interface:

IPV6_PRIVACY=rfc3041
Automatically-generated IPv6 addresses are based on the underlying hardware (e.g. Ethernet) address, and so it becomes possible to track a piece of hardware over its lifetime using its traffic. If it is important for a system's IP address to not trivially reveal its hardware address, this setting should be applied.

Manually Assign IPv6 Router Addressnetwork_ipv6_default_gateway CCE-RHEL7-CCE-TBD

Manually Assign IPv6 Router Address

Rule IDnetwork_ipv6_default_gateway
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf

Description

Edit the file /etc/sysconfig/network-scripts/ifcfg-interface, and add or correct the following line (substituting your gateway IP as appropriate):

IPV6_DEFAULTGW=2001:0DB8::0001
Router addresses should be manually set and not accepted via any auto-configuration or router advertisement.

Verify firewalld Enabledservice_firewalld_enabled CCE-RHEL7-CCE-TBD

Verify firewalld Enabled

Rule IDservice_firewalld_enabled
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

Description

The firewalld service can be enabled with the following command:

$ sudo systemctl enable firewalld

Rationale

The dynamic firewall daemon firewalld provides a dynamically managed firewall with support for network “zones”, Ethernet bridges, and has a separation of runtime and permanent configuration options. It has support for both IPv4 and IPv6 firewall settings.

Verify ip6tables Enabled if Using IPv6service_ip6tables_enabled CCE-RHEL7-CCE-TBD

Verify ip6tables Enabled if Using IPv6

Rule IDservice_ip6tables_enabled
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 ip6tables service can be enabled with the following command:

$ sudo systemctl enable ip6tables

Rationale

The ip6tables service provides the system's host-based firewalling capability for IPv6 and ICMPv6.

Set Default ip6tables Policy for Incoming Packetsset_ip6tables_default_rule CCE-RHEL7-CCE-TBD

Set Default ip6tables Policy for Incoming Packets

Rule IDset_ip6tables_default_rule
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 66, 1109, 1154, 1414

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 /etc/sysconfig/ip6tables:

:INPUT DROP [0:0]
If changes were required, reload the ip6tables rules:
$ sudo service ip6tables reload

Rationale

In ip6tables, the default policy is applied only after all the applicable rules in the table are examined for a match. Setting the default policy to DROP implements proper design for a firewall, i.e. any packets which are not explicitly permitted should not be accepted.

Verify iptables Enabledservice_iptables_enabled CCE-RHEL7-CCE-TBD

Verify iptables Enabled

Rule IDservice_iptables_enabled
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
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 iptables service can be enabled with the following command:

$ sudo systemctl enable iptables

Rationale

The iptables service provides the system's host-based firewalling capability for IPv4 and ICMP.

Set Default iptables Policy for Incoming Packetsset_iptables_default_rule CCE-RHEL7-CCE-TBD

Set Default iptables Policy for Incoming Packets

Rule IDset_iptables_default_rule
Result
notselected
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 66, 1109, 1154, 1414

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 /etc/sysconfig/iptables:

:INPUT DROP [0:0]

Rationale

In iptables the default policy is applied only after all the applicable rules in the table are examined for a match. Setting the default policy to DROP implements proper design for a firewall, i.e. any packets which are not explicitly pe