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 permitted should not be accepted.

Set Default iptables Policy for Forwarded Packetsset_iptables_default_rule_forward CCE-RHEL7-CCE-TBD

Set Default iptables Policy for Forwarded Packets

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 1109

Description

To set the default policy to DROP (instead of ACCEPT) for the built-in FORWARD chain which processes packets that will be forwarded from one interface to another, add or correct the following line in /etc/sysconfig/iptables:

:FORWARD 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 permitted should not be accepted.

Disable DCCP Supportkernel_module_dccp_disabled CCE-26828-4

Disable DCCP Support

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

identifiers:  CCE-26828-4

references:  CM-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS

Description

The Datagram Congestion Control Protocol (DCCP) is a relatively new transport layer protocol, designed to support streaming media and telephony. To configure the system to prevent the dccp kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install dccp /bin/true

Rationale

Disabling DCCP protects the system against exploitation of any flaws in its implementation.

Disable SCTP Supportkernel_module_sctp_disabled CCE-27106-4

Disable SCTP Support

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

identifiers:  CCE-27106-4

references:  CM-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS

Description

The Stream Control Transmission Protocol (SCTP) is a transport layer protocol, designed to support the idea of message-oriented communication, with several streams of messages within one connection. To configure the system to prevent the sctp kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install sctp /bin/true

Rationale

Disabling SCTP protects the system against exploitation of any flaws in its implementation.

Disable RDS Supportkernel_module_rds_disabled CCE-RHEL7-CCE-TBD

Disable RDS Support

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

The Reliable Datagram Sockets (RDS) protocol is a transport layer protocol designed to provide reliable high- bandwidth, low-latency communications between nodes in a cluster. To configure the system to prevent the rds kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install rds /bin/true

Rationale

Disabling RDS protects the system against exploitation of any flaws in its implementation.

Disable TIPC Supportkernel_module_tipc_disabled CCE-RHEL7-CCE-TBD

Disable TIPC Support

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

The Transparent Inter-Process Communication (TIPC) protocol is designed to provide communications between nodes in a cluster. To configure the system to prevent the tipc kernel module from being loaded, add the following line to a file in the directory /etc/modprobe.d:

install tipc /bin/true

Rationale

Disabling TIPC protects the system against exploitation of any flaws in its implementation.

Install libreswan Packagepackage_libreswan_installed CCE-RHEL7-CCE-TBD

Install libreswan Package

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17, MA-4, SC-9, 1130, 1131

Description

The Libreswan package provides an implementation of IPsec and IKE, which permits the creation of secure tunnels over untrusted networks. The libreswan package can be installed with the following command:

$ sudo yum install libreswan

Rationale

Providing the ability for remote users or systems to initiate a secure VPN connection protects information when it is transmitted over a wide area network.

Disable Zeroconf Networkingnetwork_disable_zeroconf CCE-RHEL7-CCE-TBD

Disable Zeroconf Networking

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

Zeroconf networking allows the system to assign itself an IP address and engage in IP communication without a statically-assigned address or even a DHCP server. Automatic address assignment via Zeroconf (or DHCP) is not recommended. To disable Zeroconf automatic route assignment in the 169.254.0.0 subnet, add or correct the following line in /etc/sysconfig/network:

NOZEROCONF=yes

Rationale

Zeroconf addresses are in the network 169.254.0.0. The networking scripts add entries to the system's routing table for these addresses. Zeroconf address assignment commonly occurs when the system is configured to use DHCP but fails to receive an address assignment from the DHCP server.

Ensure System is Not Acting as a Network Sniffernetwork_sniffer_disabled CCE-RHEL7-CCE-TBD

Ensure System is Not Acting as a Network Sniffer

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, MA-3

Description

The system should not be acting as a network sniffer, which can capture all traffic on the network to which it is connected. Run the following to determine if any interface is running in promiscuous mode:

$ ip link | grep PROMISC

Rationale

If any results are returned, then a sniffing process (such as tcpdump or Wireshark) is likely to be using the interface and this should be investigated.

Ensure Log Files Are Owned By Appropriate Useruserowner_rsyslog_files CCE-RHEL7-CCE-TBD

Ensure Log Files Are Owned By Appropriate User

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-6, 1314, Test attestation on 20121024 by DS

Description

The owner of all log files written by rsyslog should be root. These log files are determined by the second part of each Rule line in /etc/rsyslog.conf and typically all appear in /var/log. For each log file LOGFILE referenced in /etc/rsyslog.conf, run the following command to inspect the file's owner:

$ ls -l LOGFILE
If the owner is not root, run the following command to correct this:
$ sudo chown root LOGFILE

Rationale

The log files generated by rsyslog contain valuable information regarding system configuration, user authentication, and other such information. Log files should be protected from unauthorized access.

Ensure Log Files Are Owned By Appropriate Groupgroupowner_rsyslog_files CCE-RHEL7-CCE-TBD

Ensure Log Files Are Owned By Appropriate Group

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-6, 1314, Test attestation on 20121024 by DS

Description

The group-owner of all log files written by rsyslog should be root. These log files are determined by the second part of each Rule line in /etc/rsyslog.conf and typically all appear in /var/log. For each log file LOGFILE referenced in /etc/rsyslog.conf, run the following command to inspect the file's group owner:

$ ls -l LOGFILE
If the owner is not root, run the following command to correct this:
$ sudo chgrp root LOGFILE

Rationale

The log files generated by rsyslog contain valuable information regarding system configuration, user authentication, and other such information. Log files should be protected from unauthorized access.

Ensure System Log Files Have Correct Permissionsrsyslog_file_permissions CCE-RHEL7-CCE-TBD

Ensure System Log Files Have Correct Permissions

Rule IDrsyslog_file_permissions
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, 1314, Test attestation on 20121024 by DS

Description

The file permissions for all log files written by rsyslog should be set to 600, or more restrictive. These log files are determined by the second part of each Rule line in /etc/rsyslog.conf and typically all appear in /var/log. For each log file LOGFILE referenced in /etc/rsyslog.conf, run the following command to inspect the file's permissions:

$ ls -l LOGFILE
If the permissions are not 600 or more restrictive, run the following command to correct this:
$ sudo chmod 0600 LOGFILE

Rationale

Log files can contain valuable information regarding system configuration. If the system log files are not protected unauthorized users could change the logged data, eliminating their forensic value.

Ensure Logs Sent To Remote Hostrsyslog_send_messages_to_logserver CCE-RHEL7-CCE-TBD

Ensure Logs Sent To Remote Host

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-3(2), AU-9, 1348, 136

Description

To configure rsyslog to send logs to a remote log server, open /etc/rsyslog.conf and read and understand the last section of the file, which describes the multiple directives necessary to activate remote logging. Along with these other directives, the system can be configured to forward its logs to a particular log server by adding or correcting one of the following lines, substituting loghost.example.com appropriately. The choice of protocol depends on the environment of the system; although TCP and RELP provide more reliable message delivery, they may not be supported in all environments.
To use UDP for log message delivery:

*.* @loghost.example.com

To use TCP for log message delivery:
*.* @@loghost.example.com

To use RELP for log message delivery:
*.* :omrelp:loghost.example.com

Rationale

A log server (loghost) receives syslog messages from one or more systems. This data can be used as an additional log source in the event a system is compromised and its local logs are suspect. Forwarding log messages to a remote loghost also provides system administrators with a centralized place to view the status of multiple hosts within the enterprise.

Ensure rsyslog Does Not Accept Remote Messages Unless Acting As Log Serverrsyslog_accept_remote_messages_none CCE-RHEL7-CCE-TBD

Ensure rsyslog Does Not Accept Remote Messages Unless Acting As Log Server

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-9(2), AC-4

Description

The rsyslog daemon should not accept remote messages unless the system acts as a log server. To ensure that it is not listening on the network, ensure the following lines are not found in /etc/rsyslog.conf:

$ModLoad imtcp
$InputTCPServerRun port
$ModLoad imudp
$UDPServerRun port
$ModLoad imrelp
$InputRELPServerRun port

Rationale

Any process which receives messages from the network incurs some risk of receiving malicious messages. This risk can be eliminated for rsyslog by configuring it not to listen on the network.

Enable rsyslog to Accept Messages via TCP, if Acting As Log Serverrsyslog_accept_remote_messages_tcp CCE-RHEL7-CCE-TBD

Enable rsyslog to Accept Messages via TCP, if Acting As Log Server

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-9

Description

The rsyslog daemon should not accept remote messages unless the system acts as a log server. If the system needs to act as a central log server, add the following lines to /etc/rsyslog.conf to enable reception of messages over TCP:

$ModLoad imtcp
$InputTCPServerRun 514

Rationale

If the system needs to act as a log server, this ensures that it can receive messages over a reliable TCP connection.

Enable rsyslog to Accept Messages via UDP, if Acting As Log Serverrsyslog_accept_remote_messages_udp CCE-RHEL7-CCE-TBD

Enable rsyslog to Accept Messages via UDP, if Acting As Log Server

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-9

Description

The rsyslog daemon should not accept remote messages unless the system acts as a log server. If the system needs to act as a central log server, add the following lines to /etc/rsyslog.conf to enable reception of messages over UDP:

$ModLoad imudp
$UDPServerRun 514

Rationale

Many devices, such as switches, routers, and other Unix-like systems, may only support the traditional syslog transmission over UDP. If the system must act as a log server, this enables it to receive their messages as well.

Ensure Logrotate Runs Periodicallyensure_logrotate_activated CCE-RHEL7-CCE-TBD

Ensure Logrotate Runs Periodically

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-9, 366

Description

The logrotate utility allows for the automatic rotation of log files. The frequency of rotation is specified in /etc/logrotate.conf, which triggers a cron task. To configure logrotate to run daily, add or correct the following line in /etc/logrotate.conf:

# rotate log files frequency
daily

Rationale

Log files that are not properly rotated run the risk of growing so large that they fill up the /var/log partition. Valuable logging information could be lost if the /var/log partition becomes full.

Configure Logwatch HostLimit Lineconfigure_logwatch_hostlimit CCE-RHEL7-CCE-TBD

Configure Logwatch HostLimit Line

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

On a central logserver, you want Logwatch to summarize all syslog entries, including those which did not originate on the logserver itself. The HostLimit setting tells Logwatch to report on all hosts, not just the one on which it is running.

 HostLimit = no 

Configure Logwatch SplitHosts Lineconfigure_logwatch_splithosts CCE-RHEL7-CCE-TBD

Configure Logwatch SplitHosts Line

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

If SplitHosts is set, Logwatch will separate entries by hostname. This makes the report longer but significantly more usable. If it is not set, then Logwatch will not report which host generated a given log entry, and that information is almost always necessary

 SplitHosts = yes 

Ensure rsyslog is Installedpackage_rsyslog_installed CCE-RHEL7-CCE-TBD

Ensure rsyslog is Installed

Rule IDpackage_rsyslog_installed
Result
pass
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-9(2), 1311, 1312, Test attestation on 20121024 by DS

Description

Rsyslog is installed by default. The rsyslog package can be installed with the following command:

$ sudo yum install rsyslog

Rationale

The rsyslog package provides the rsyslog daemon, which provides system logging services.

Enable rsyslog Serviceservice_rsyslog_enabled CCE-RHEL7-CCE-TBD

Enable rsyslog Service

Rule IDservice_rsyslog_enabled
Result
pass
Time2015-07-17T10:50:20
Severitymedium
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-12, 1557, 1312, 1311, Test attestation on 20121024 by DS

Description

The rsyslog service provides syslog-style logging by default on RHEL 7. The rsyslog service can be enabled with the following command:

$ sudo systemctl enable rsyslog

Rationale

The rsyslog service must be running in order to provide logging services, which are essential to system administration.

Disable Logwatch on Clients if a Logserver Existsdisable_logwatch_for_logserver CCE-RHEL7-CCE-TBD

Disable Logwatch on Clients if a Logserver Exists

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Does your site have a central logserver which has been configured to report on logs received from all systems? If so:

 
$ sudo rm /etc/cron.daily/0logwatch 
If no logserver exists, it will be necessary for each machine to run Logwatch individually. Using a central logserver provides the security and reliability benefits discussed earlier, and also makes monitoring logs easier and less time-intensive for administrators.

Configure auditd Number of Logs Retainedconfigure_auditd_num_logs CCE-RHEL7-CCE-TBD

Configure auditd Number of Logs Retained

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-1(b), AU-11, IR-5, Test attestation on 20121024 by DS

Description

Determine how many log files auditd should retain when it rotates logs. Edit the file /etc/audit/auditd.conf. Add or modify the following line, substituting NUMLOGS with the correct value:

num_logs = NUMLOGS
Set the value to 5 for general-purpose systems. Note that values less than 2 result in no log rotation.

Rationale

The total storage for audit log files must be large enough to retain log information over the period required. This is a function of the maximum log file size and the number of logs retained.

Configure auditd Max Log File Sizeconfigure_auditd_max_log_file CCE-RHEL7-CCE-TBD

Configure auditd Max Log File Size

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-1(b), AU-11, IR-5, Test attestation on 20121024 by DS

Description

Determine the amount of audit data (in megabytes) which should be retained in each log file. Edit the file /etc/audit/auditd.conf. Add or modify the following line, substituting the correct value for STOREMB:

max_log_file = STOREMB
Set the value to 6 (MB) or higher for general-purpose systems. Larger values, of course, support retention of even more audit data.

Rationale

The total storage for audit log files must be large enough to retain log information over the period required. This is a function of the maximum log file size and the number of logs retained.

Configure auditd max_log_file_action Upon Reaching Maximum Log Sizeconfigure_auditd_max_log_file_action CCE-RHEL7-CCE-TBD

Configure auditd max_log_file_action Upon Reaching Maximum Log Size

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-1(b), AU-4, AU-11, IR-5, Test attestation on 20121024 by DS

Description

The default action to take when the logs reach their maximum size is to rotate the log files, discarding the oldest one. To configure the action taken by auditd, add or correct the line in /etc/audit/auditd.conf:

max_log_file_action = ACTION
Possible values for ACTION are described in the auditd.conf man page. These include:
  • ignore
  • syslog
  • suspend
  • rotate
  • keep_logs
Set the ACTION to rotate to ensure log rotation occurs. This is the default. The setting is case-insensitive.

Rationale

Automatically rotating logs (by setting this to rotate) minimizes the chances of the system unexpectedly running out of disk space by being overwhelmed with log data. However, for systems that must never discard log data, or which use external processes to transfer it and reclaim space, keep_logs can be employed.

Configure auditd space_left Action on Low Disk Spaceauditd_data_retention_space_left_action CCE-RHEL7-CCE-TBD

Configure auditd space_left Action on Low Disk Space

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-1(b), AU-4, AU-5(b), IR-5, 140, 143, Test attestation on 20121024 by DS

Description

The auditd service can be configured to take an action when disk space starts to run low. Edit the file /etc/audit/auditd.conf. Modify the following line, substituting ACTION appropriately:

space_left_action = ACTION
Possible values for ACTION are described in the auditd.conf man page. These include:
  • ignore
  • syslog
  • email
  • exec
  • suspend
  • single
  • halt
Set this to email (instead of the default, which is suspend) as it is more likely to get prompt attention. Acceptable values also include suspend, single, and halt.

Rationale

Notifying administrators of an impending disk space problem may allow them to take corrective action prior to any disruption.

Configure auditd admin_space_left Action on Low Disk Spaceauditd_data_retention_admin_space_left_action CCE-RHEL7-CCE-TBD

Configure auditd admin_space_left Action on Low Disk Space

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-1(b), AU-4, AU-5(b), IR-5, 140, 1343, Test attestation on 20121024 by DS

Description

The auditd service can be configured to take an action when disk space is running low but prior to running out of space completely. Edit the file /etc/audit/auditd.conf. Add or modify the following line, substituting ACTION appropriately:

admin_space_left_action = ACTION
Set this value to single to cause the system to switch to single user mode for corrective action. Acceptable values also include suspend and halt. For certain systems, the need for availability outweighs the need to log all actions, and a different setting should be determined. Details regarding all possible values for ACTION are described in the auditd.conf man page.

Rationale

Administrators should be made aware of an inability to record audit records. If a separate partition or logical volume of adequate size is used, running low on space for audit records should never occur.

Configure auditd mail_acct Action on Low Disk Spaceauditd_data_retention_action_mail_acct CCE-RHEL7-CCE-TBD

Configure auditd mail_acct Action on Low Disk Space

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-1(b), AU-4, AU-5(a), IR-5, 139, 144

Description

The auditd service can be configured to send email to a designated account in certain situations. Add or correct the following line in /etc/audit/auditd.conf to ensure that administrators are notified via email for those situations:

action_mail_acct = root

Rationale

Email sent to the root account is typically aliased to the administrators of the system, who can take appropriate action.

Configure auditd to use audispd pluginconfigure_auditd_audispd CCE-RHEL7-CCE-TBD

Configure auditd to use audispd plugin

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-1(b), AU-3(2), IR-5, 136

Description

To configure the auditd service to use the audispd plugin, set the active line in /etc/audisp/plugins.d/syslog.conf to yes. Restart the auditdservice:

$ sudo service auditd restart

Rationale

The auditd service does not include the ability to send audit records to a centralized server for management directly. It does, however, include an audit event multiplexor plugin (audispd) to pass audit records to the local syslog server

Record attempts to alter time through adjtimexaudit_rules_time_adjtimex CCE-RHEL7-CCE-TBD

Record attempts to alter time through adjtimex

Rule IDaudit_rules_time_adjtimex
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 1487, 169

Description

If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S adjtimex -k audit_time_rules
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S adjtimex -k audit_time_rules
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S adjtimex -k audit_time_rules
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S adjtimex -k audit_time_rules
The -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined syscalls:
-a always,exit -F arch=b64 -S adjtimex -S settimeofday -S clock_settime -k audit_time_rules

Rationale

Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such as sshd). All changes to the system time should be audited.

Record attempts to alter time through settimeofdayaudit_rules_time_settimeofday CCE-RHEL7-CCE-TBD

Record attempts to alter time through settimeofday

Rule IDaudit_rules_time_settimeofday
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 1487, 169

Description

If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S settimeofday -k audit_time_rules
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S settimeofday -k audit_time_rules
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S settimeofday -k audit_time_rules
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S settimeofday -k audit_time_rules
The -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined syscalls:
-a always,exit -F arch=b64 -S adjtimex -S settimeofday -S clock_settime -k audit_time_rules

Rationale

Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such as sshd). All changes to the system time should be audited.

Record Attempts to Alter Time Through stimeaudit_rules_time_stime CCE-RHEL7-CCE-TBD

Record Attempts to Alter Time Through stime

Rule IDaudit_rules_time_stime
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 1487, 169

Description

If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d for both 32 bit and 64 bit systems:

-a always,exit -F arch=b32 -S stime -k audit_time_rules
Since the 64 bit version of the "stime" system call is not defined in the audit lookup table, the corresponding "-F arch=b64" form of this rule is not expected to be defined on 64 bit systems (the aforementioned "-F arch=b32" stime rule form itself is sufficient for both 32 bit and 64 bit systems). If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file for both 32 bit and 64 bit systems:
-a always,exit -F arch=b32 -S stime -k audit_time_rules
Since the 64 bit version of the "stime" system call is not defined in the audit lookup table, the corresponding "-F arch=b64" form of this rule is not expected to be defined on 64 bit systems (the aforementioned "-F arch=b32" stime rule form itself is sufficient for both 32 bit and 64 bit systems). The -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined system calls:
-a always,exit -F arch=b64 -S adjtimex -S settimeofday -S clock_settime -k audit_time_rules

Rationale

Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such as sshd). All changes to the system time should be audited.

Record Attempts to Alter Time Through clock_settimeaudit_rules_time_clock_settime CCE-RHEL7-CCE-TBD

Record Attempts to Alter Time Through clock_settime

Rule IDaudit_rules_time_clock_settime
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 1487, 169

Description

If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S clock_settime -k audit_time_rules
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S clock_settime -k audit_time_rules
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S clock_settime -k audit_time_rules
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S clock_settime -k audit_time_rules
The -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport. Multiple system calls can be defined on the same line to save space if desired, but is not required. See an example of multiple combined syscalls:
-a always,exit -F arch=b64 -S adjtimex -S settimeofday -S clock_settime -k audit_time_rules

Rationale

Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such as sshd). All changes to the system time should be audited.

Record Attempts to Alter the localtime Fileaudit_rules_time_watch_localtime CCE-RHEL7-CCE-TBD

Record Attempts to Alter the localtime File

Rule IDaudit_rules_time_watch_localtime
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(b), IR-5, 1487, 169

Description

If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-w /etc/localtime -p wa -k audit_time_rules
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-w /etc/localtime -p wa -k audit_time_rules
The -k option allows for the specification of a key in string form that can be used for better reporting capability through ausearch and aureport and should always be used.

Rationale

Arbitrary changes to the system time can be used to obfuscate nefarious activities in log files, as well as to confuse network services that are highly dependent upon an accurate system time (such as sshd). All changes to the system time should be audited.

Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
fix_audit_watch_rule "auditctl" "/etc/localtime" "wa" "audit_time_rules"
fix_audit_watch_rule "augenrules" "/etc/localtime" "wa" "audit_time_rules"
Record Events that Modify the System's Discretionary Access Controls - chmodaudit_rules_dac_modification_chmod CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - chmod

Rule IDaudit_rules_dac_modification_chmod
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S chmod  -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S chmod  -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="chmod"
	FULL_RULE="-a always,exit -F arch=$ARCH -S chmod -S fchmod -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - chownaudit_rules_dac_modification_chown CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - chown

Rule IDaudit_rules_dac_modification_chown
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=${ARCH} -S .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="chown"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S chown -S fchown -S fchownat -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - fchmodaudit_rules_dac_modification_fchmod CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - fchmod

Rule IDaudit_rules_dac_modification_fchmod
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="chmod"
	FULL_RULE="-a always,exit -F arch=$ARCH -S chmod -S fchmod -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - fchmodataudit_rules_dac_modification_fchmodat CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - fchmodat

Rule IDaudit_rules_dac_modification_fchmodat
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="chmod"
	FULL_RULE="-a always,exit -F arch=$ARCH -S chmod -S fchmod -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - fchownaudit_rules_dac_modification_fchown CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - fchown

Rule IDaudit_rules_dac_modification_fchown
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=${ARCH} -S .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="chown"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S chown -S fchown -S fchownat -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - fchownataudit_rules_dac_modification_fchownat CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - fchownat

Rule IDaudit_rules_dac_modification_fchownat
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=${ARCH} -S .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="chown"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S chown -S fchown -S fchownat -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - fremovexattraudit_rules_dac_modification_fremovexattr CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - fremovexattr

Rule IDaudit_rules_dac_modification_fremovexattr
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - fsetxattraudit_rules_dac_modification_fsetxattr CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - fsetxattr

Rule IDaudit_rules_dac_modification_fsetxattr
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - lchownaudit_rules_dac_modification_lchown CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - lchown

Rule IDaudit_rules_dac_modification_lchown
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=${ARCH} -S .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="chown"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S chown -S fchown -S fchownat -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - lremovexattraudit_rules_dac_modification_lremovexattr CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - lremovexattr

Rule IDaudit_rules_dac_modification_lremovexattr
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - lsetxattraudit_rules_dac_modification_lsetxattr CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - lsetxattr

Rule IDaudit_rules_dac_modification_lsetxattr
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - removexattraudit_rules_dac_modification_removexattr CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - removexattr

Rule IDaudit_rules_dac_modification_removexattr
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify the System's Discretionary Access Controls - setxattraudit_rules_dac_modification_setxattr CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Discretionary Access Controls - setxattr

Rule IDaudit_rules_dac_modification_setxattr
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect file permission changes for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod
If the system is 64 bit then also add the following line:
-a always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod

Rationale

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users.

Warnings
warning  Note that these rules can be configured in a number of ways while still achieving the desired effect. Here the system calls have been placed independent of other system calls. Grouping these system calls with others as identifying earlier in this guide is more efficient.
Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="xattr"
	FULL_RULE="-a always,exit -F arch=${ARCH} -S setxattr -S lsetxattr -S fsetxattr -S removexattr -S lremovexattr -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Record Events that Modify User/Group Informationaudit_rules_usergroup_modification CCE-27192-4

Record Events that Modify User/Group Information

Rule IDaudit_rules_usergroup_modification
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-27192-4

references:  AC-2(4), AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 18, 172, 1403, 1404, 1405, 1684, 1683, 1685, 1686, 476, 239

Description

If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d, in order to capture events that modify account changes:

-w /etc/group -p wa -k audit_rules_usergroup_modification
-w /etc/passwd -p wa -k audit_rules_usergroup_modification
-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
-w /etc/shadow -p wa -k audit_rules_usergroup_modification
-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, in order to capture events that modify account changes:
-w /etc/group -p wa -k audit_rules_usergroup_modification
-w /etc/passwd -p wa -k audit_rules_usergroup_modification
-w /etc/gshadow -p wa -k audit_rules_usergroup_modification
-w /etc/shadow -p wa -k audit_rules_usergroup_modification
-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification

Rationale

In addition to auditing new user and group accounts, these watches will alert the system administrator(s) to any modifications. Any unexpected users, groups, or modifications should be investigated for legitimacy.

Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

# Perform the remediation
# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
fix_audit_watch_rule "auditctl" "/etc/group" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "augenrules" "/etc/group" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "auditctl" "/etc/passwd" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "augenrules" "/etc/passwd" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "auditctl" "/etc/gshadow" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "augenrules" "/etc/gshadow" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "auditctl" "/etc/shadow" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "augenrules" "/etc/shadow" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "auditctl" "/etc/security/opasswd" "wa" "audit_rules_usergroup_modification"
fix_audit_watch_rule "augenrules" "/etc/security/opasswd" "wa" "audit_rules_usergroup_modification"
Record Events that Modify the System's Network Environmentaudit_rules_networkconfig_modification CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Network Environment

Rule IDaudit_rules_networkconfig_modification
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5

Description

If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as appropriate for your system:

-a always,exit -F arch=ARCH -S sethostname -S setdomainname -k audit_rules_networkconfig_modification
-w /etc/issue -p wa -k audit_rules_networkconfig_modification
-w /etc/issue.net -p wa -k audit_rules_networkconfig_modification
-w /etc/hosts -p wa -k audit_rules_networkconfig_modification
-w /etc/sysconfig/network -p wa -k audit_rules_networkconfig_modification
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file, setting ARCH to either b32 or b64 as appropriate for your system:
-a always,exit -F arch=ARCH -S sethostname -S setdomainname -k audit_rules_networkconfig_modification
-w /etc/issue -p wa -k audit_rules_networkconfig_modification
-w /etc/issue.net -p wa -k audit_rules_networkconfig_modification
-w /etc/hosts -p wa -k audit_rules_networkconfig_modification
-w /etc/sysconfig/network -p wa -k audit_rules_networkconfig_modification

Rationale

The network environment should not be modified by anything other than administrator action. Any change to network parameters should be audited.

Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

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

# Then perform the remediations for the watch rules
# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
fix_audit_watch_rule "auditctl" "/etc/issue" "wa" "audit_rules_networkconfig_modification"
fix_audit_watch_rule "augenrules" "/etc/issue" "wa" "audit_rules_networkconfig_modification"
fix_audit_watch_rule "auditctl" "/etc/issue.net" "wa" "audit_rules_networkconfig_modification"
fix_audit_watch_rule "augenrules" "/etc/issue.net" "wa" "audit_rules_networkconfig_modification"
fix_audit_watch_rule "auditctl" "/etc/hosts" "wa" "audit_rules_networkconfig_modification"
fix_audit_watch_rule "augenrules" "/etc/hosts" "wa" "audit_rules_networkconfig_modification"
fix_audit_watch_rule "auditctl" "/etc/sysconfig/network" "wa" "audit_rules_networkconfig_modification"
fix_audit_watch_rule "augenrules" "/etc/sysconfig/network" "wa" "audit_rules_networkconfig_modification"
System Audit Logs Must Have Mode 0640 or Less Permissivefile_permissions_var_log_audit CCE-27004-1

System Audit Logs Must Have Mode 0640 or Less Permissive

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

identifiers:  CCE-27004-1

references:  AC-6, AU-1(b), AU-9, IR-5, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS

Description

Change the mode of the audit log files with the following command:

$ sudo chmod 0640 audit_file

Rationale

If users can write to audit logs, audit trails can be modified or destroyed.

System Audit Logs Must Be Owned By Rootaudit_logs_rootowner CCE-RHEL7-CCE-TBD

System Audit Logs Must Be Owned By Root

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-6, AU-1(b), AU-9, IR-5, 166, Test attestation on 20121024 by DS

Description

To properly set the owner of /var/log, run the command:

$ sudo chown root /var/log

Rationale

Failure to give ownership of the audit log files to root allows the designated owner, and unauthorized users, potential access to sensitive information.

Record Events that Modify the System's Mandatory Access Controlsaudit_rules_mac_modification CCE-RHEL7-CCE-TBD

Record Events that Modify the System's Mandatory Access Controls

Rule IDaudit_rules_mac_modification
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5

Description

If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-w /etc/selinux/ -p wa -k MAC-policy
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-w /etc/selinux/ -p wa -k MAC-policy

Rationale

The system's mandatory access policy (SELinux) should not be arbitrarily changed by anything other than administrator action. All changes to MAC policy should be audited.

Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
fix_audit_watch_rule "auditctl" "/etc/selinux/" "wa" "MAC-policy"
fix_audit_watch_rule "augenrules" "/etc/selinux/" "wa" "MAC-policy"
Record Attempts to Alter Process and Session Initiation Informationaudit_rules_session_events CCE-27301-1

Record Attempts to Alter Process and Session Initiation Information

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

identifiers:  CCE-27301-1

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5

Description

The audit system already collects process information for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d in order to watch for attempted manual edits of files involved in storing such process information:

-w /var/run/utmp -p wa -k session
-w /var/log/btmp -p wa -k session
-w /var/log/wtmp -p wa -k session
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file in order to watch for attempted manual edits of files involved in storing such process information:
-w /var/run/utmp -p wa -k session
-w /var/log/btmp -p wa -k session
-w /var/log/wtmp -p wa -k session

Rationale

Manual editing of these files may indicate nefarious activity, such as an attacker attempting to remove evidence of an intrusion.

Ensure auditd Collects Unauthorized Access Attempts to Files (unsuccessful)audit_rules_unsuccessful_file_modification CCE-RHEL7-CCE-TBD

Ensure auditd Collects Unauthorized Access Attempts to Files (unsuccessful)

Rule IDaudit_rules_unsuccessful_file_modification
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126

Description

At a minimum the audit system should collect unauthorized file accesses for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d:

-a always,exit -F arch=b32 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
-a always,exit -F arch=b32 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
If the system is 64 bit then also add the following lines:
-a always,exit -F arch=b64 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
-a always,exit -F arch=b64 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file:
-a always,exit -F arch=b32 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
-a always,exit -F arch=b32 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
If the system is 64 bit then also add the following lines:
-a always,exit -F arch=b64 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
-a always,exit -F arch=b64 -S creat -S open -S openat -S open_by_handle_at -S truncate -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access

Rationale

Unsuccessful attempts to access files could be an indicator of malicious activity on a system. Auditing these events could serve as evidence of potential system compromise.

Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

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

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

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

done
Ensure auditd Collects Information on the Use of Privileged Commandsaudit_rules_privileged_commands CCE-RHEL7-CCE-TBD

Ensure auditd Collects Information on the Use of Privileged Commands

Rule IDaudit_rules_privileged_commands
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-2(4), AU-12(a), AU-12(c), IR-5, 40, Test attestation on 20121024 by DS

Description

At a minimum the audit system should collect the execution of privileged commands for all users and root. To find the relevant setuid / setgid programs, run the following command for each local partition PART:

$ sudo find PART -xdev -type f -perm -4000 -o -type f -perm -2000 2>/dev/null
If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add a line of the following form to a file with suffix .rules in the directory /etc/audit/rules.d for each setuid / setgid program on the system, replacing the SETUID_PROG_PATH part with the full path of that setuid / setgid program in the list:
-a always,exit -F path=SETUID_PROG_PATH -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add a line of the following form to /etc/audit/audit.rules for each setuid / setgid program on the system, replacing the SETUID_PROG_PATH part with the full path of that setuid / setgid program in the list:
-a always,exit -F path=SETUID_PROG_PATH -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged

Rationale

Privileged programs are subject to escalation-of-privilege attacks, which attempt to subvert their normal role of providing some necessary but limited capability. As such, motivation exists to monitor these programs for unusual activity.

Ensure auditd Collects Information on Exporting to Media (successful)audit_rules_media_export CCE-RHEL7-CCE-TBD

Ensure auditd Collects Information on Exporting to Media (successful)

Rule IDaudit_rules_media_export
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126, Test attestation on 20121024 by DS

Description

At a minimum the audit system should collect media exportation events for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as appropriate for your system:

-a always,exit -F arch=ARCH -S mount -F auid>=1000 -F auid!=4294967295 -k export
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file, setting ARCH to either b32 or b64 as appropriate for your system:
-a always,exit -F arch=ARCH -S mount -F auid>=1000 -F auid!=4294967295 -k export

Rationale

The unauthorized exportation of data to external media could result in an information leak where classified information, Privacy Act information, and intellectual property could be lost. An audit trail should be created each time a filesystem is mounted to help identify and guard against information loss.

Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F auid>=1000 -F auid!=4294967295 -k *"
	GROUP="mount"
	FULL_RULE="-a always,exit -F arch=$ARCH -S mount -F auid>=1000 -F auid!=4294967295 -k export"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Ensure auditd Collects File Deletion Events by Useraudit_rules_file_deletion_events CCE-27206-2

Ensure auditd Collects File Deletion Events by User

Rule IDaudit_rules_file_deletion_events
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-27206-2

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 172, 468

Description

At a minimum the audit system should collect file deletion events for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d, setting ARCH to either b32 or b64 as appropriate for your system:

-a always,exit -F arch=ARCH -S rmdir -S unlink -S unlinkat -S rename -S renameat -F auid>=1000 -F auid!=4294967295 -k delete
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file, setting ARCH to either b32 or b64 as appropriate for your system:
-a always,exit -F arch=ARCH -S rmdir -S unlink -S unlinkat -S rename -S renameat -F auid>=1000 -F auid!=4294967295 -k delete

Rationale

Auditing file deletions will create an audit trail for files that are removed from the system. The audit trail could aid in system troubleshooting, as well as, detecting malicious processes that attempt to delete log files to conceal their presence.

Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

for ARCH in "${RULE_ARCHS[@]}"
do
	PATTERN="-a always,exit -F arch=$ARCH -S .* -F auid>=1000 -F auid!=4294967295 -k *"
	# Use escaped BRE regex to specify rule group
	GROUP="\(rmdir\|unlink\|rename\)"
	FULL_RULE="-a always,exit -F arch=$ARCH -S rmdir -S unlink -S unlinkat -S rename -S renameat -F auid>=1000 -F auid!=4294967295 -k delete"
	# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
	fix_audit_syscall_rule "auditctl" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
	fix_audit_syscall_rule "augenrules" "$PATTERN" "$GROUP" "$ARCH" "$FULL_RULE"
done
Ensure auditd Collects System Administrator Actionsaudit_rules_sysadmin_actions CCE-RHEL7-CCE-TBD

Ensure auditd Collects System Administrator Actions

Rule IDaudit_rules_sysadmin_actions
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-2(7)(b), AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 126, Test attestation on 20121024 by DS

Description

At a minimum the audit system should collect administrator actions for all users and root. If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d:

-w /etc/sudoers -p wa -k actions
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file:
-w /etc/sudoers -p wa -k actions

Rationale

The actions taken by system administrators should be audited to keep a record of what was executed on the system, as well as, for accountability purposes.

Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
fix_audit_watch_rule "auditctl" "/etc/sudoers" "wa" "actions"
fix_audit_watch_rule "augenrules" "/etc/sudoers" "wa" "actions"
Ensure auditd Collects Information on Kernel Module Loading and Unloadingaudit_rules_kernel_module_loading CCE-27129-6

Ensure auditd Collects Information on Kernel Module Loading and Unloading

Rule IDaudit_rules_kernel_module_loading
Result
fail
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-27129-6

references:  AC-17(7), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-12(a), AU-12(c), IR-5, 172, 477

Description

If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following lines to a file with suffix .rules in the directory /etc/audit/rules.d to capture kernel module loading and unloading events, setting ARCH to either b32 or b64 as appropriate for your system:

-w /usr/sbin/insmod -p x -k modules
-w /usr/sbin/rmmod -p x -k modules
-w /usr/sbin/modprobe -p x -k modules
-a always,exit -F arch=ARCH -S init_module -S delete_module -k modules
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following lines to /etc/audit/audit.rules file in order to capture kernel module loading and unloading events, setting ARCH to either b32 or b64 as appropriate for your system:
-w /usr/sbin/insmod -p x -k modules
-w /usr/sbin/rmmod -p x -k modules
-w /usr/sbin/modprobe -p x -k modules
-a always,exit -F arch=ARCH -S init_module -S delete_module -k modules

Rationale

The addition/removal of kernel modules can be used to alter the behavior of the kernel and potentially introduce malicious code into kernel space. It is important to have an audit trail of modules that have been introduced into the kernel.

Remediation script:

# Include source function library.
. /usr/share/scap-security-guide/remediation_functions

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

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

# Then perform the remediations for the watch rules
# Perform the remediation for both possible tools: 'auditctl' and 'augenrules'
fix_audit_watch_rule "auditctl" "/usr/sbin/insmod" "x" "modules"
fix_audit_watch_rule "augenrules" "/usr/sbin/insmod" "x" "modules"
fix_audit_watch_rule "auditctl" "/usr/sbin/rmmod" "x" "modules"
fix_audit_watch_rule "augenrules" "/usr/sbin/rmmod" "x" "modules"
fix_audit_watch_rule "auditctl" "/usr/sbin/modprobe" "x" "modules"
fix_audit_watch_rule "augenrules" "/usr/sbin/modprobe" "x" "modules"
Make the auditd Configuration Immutableaudit_rules_immutable CCE-27097-5

Make the auditd Configuration Immutable

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

identifiers:  CCE-27097-5

references:  AC-6, AU-1(b), AU-2(a), AU-2(c), AU-2(d), IR-5

Description

If the auditd daemon is configured to use the augenrules program to read audit rules during daemon startup (the default), add the following line to a file with suffix .rules in the directory /etc/audit/rules.d in order to make the auditd configuration immutable:

-e 2
If the auditd daemon is configured to use the auditctl utility to read audit rules during daemon startup, add the following line to /etc/audit/audit.rules file in order to make the auditd configuration immutable:
-e 2
With this setting, a reboot will be required to change any audit rules.

Rationale

Making the audit configuration immutable prevents accidental as well as malicious modification of the audit rules, although it may be problematic if legitimate changes are needed during system operation

Enable auditd Serviceservice_auditd_enabled CCE-RHEL7-CCE-TBD

Enable auditd Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(1), AU-1(b), AU-10, AU-12(a), AU-12(c), IR-5, 347, 157, 172, 880, 1353, 1462, 1487, 1115, 1454, 067, 158, 831, 1190, 1312, 1263, 130, 120, 1589, Test attestation on 20121024 by DS

Description

The auditd service is an essential userspace component of the Linux Auditing System, as it is responsible for writing audit records to disk. The auditd service can be enabled with the following command:

$ sudo systemctl enable auditd

Rationale

Ensuring the auditd service is active ensures audit records generated by the kernel can be written to disk, or that appropriate actions will be taken if other obstacles exist.

Enable Auditing for Processes Which Start Prior to the Audit Daemonbootloader_audit_argument CCE-RHEL7-CCE-TBD

Enable Auditing for Processes Which Start Prior to the Audit Daemon

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(1), AU-14(1), AU-1(b), AU-2(a), AU-2(c), AU-2(d), AU-10, IR-5, 1464, 130

Description

To ensure all processes can be audited, even those which start prior to the audit daemon, add the argument audit=1 to the kernel line in /etc/grub.conf, in the manner below:

kernel /vmlinuz-version ro vga=ext root=/dev/VolGroup00/LogVol00 rhgb quiet audit=1

Rationale

Each process on the system carries an "auditable" flag which indicates whether its activities can be audited. Although auditd takes care of enabling this for all processes which launch after it does, adding the kernel argument ensures it is set for every process during boot.

Disable xinetd Servicedisable_xinetd CCE-RHEL7-CCE-TBD

Disable xinetd Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 305, Test attestation on 20121026 by DS

Description

The xinetd service can be disabled with the following command:

$ sudo systemctl disable xinetd

Rationale

The xinetd service provides a dedicated listener service for some programs, which is no longer necessary for commonly-used network services. Disabling it ensures that these uncommon services are not running, and also prevents attacks against xinetd itself.

Uninstall xinetd Packageuninstall_xinetd CCE-RHEL7-CCE-TBD

Uninstall xinetd Package

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 305, Test attestation on 20121026 by DS

Description

The xinetd package can be uninstalled with the following command:

$ sudo yum erase xinetd

Rationale

Removing the xinetd package decreases the risk of the xinetd service's accidental (or intentional) activation.

Disable telnet Serviceservice_telnetd_disabled CCE-27158-5

Disable telnet Service

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

identifiers:  CCE-27158-5

references:  AC-17(8), CM-7, IA-5(1)(c), http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20140922 by JL

Description

The telnet service configuration file /etc/xinetd.d/telnet is not created automatically. If it was created manually, check the /etc/xinetd.d/telnet file and ensure that disable = no is changed to read disable = yes as follows below:

# description: The telnet server serves telnet sessions; it uses \\
#       unencrypted username/password pairs for authentication.
service telnet
{
        flags           = REUSE
        socket_type     = stream

        wait            = no
        user            = root
        server          = /usr/sbin/in.telnetd
        log_on_failure  += USERID
        disable         = yes
}
Then the activation of the telnet service on system boot can be disabled via the following command:
# systemctl disable telnet.socket

Rationale

The telnet protocol uses unencrypted network communication, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network. The telnet protocol is also subject to man-in-the-middle attacks.

Uninstall telnet-server Packageuninstall_telnet_server CCE-27165-0

Uninstall telnet-server Package

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

identifiers:  CCE-27165-0

references:  AC-17(8), CM-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121026 by DS

Description

The telnet-server package can be uninstalled with the following command:

$ sudo yum erase telnet-server

Rationale

Removing the telnet-server package decreases the risk of the telnet service's accidental (or intentional) activation.

Remove telnet Clientspackage_telnet_removed CCE-27039-7

Remove telnet Clients

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

identifiers:  CCE-27039-7

Description

The telnet client allows users to start connections to other systems via the telnet protocol.

Rationale

The telnet protocol is insecure and unencrypted. The use of an unencrypted transmission medium could allow an unauthorized user to steal credentials. The ssh package provides an encrypted session and stronger security and is included in Red Hat Enterprise Linux.

Uninstall rsh-server Packagepackage_rsh-server_removed CCE-RHEL7-CCE-TBD

Uninstall rsh-server Package

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 305, 381, Test attestation on 20121026 by DS

Description

The rsh-server package can be uninstalled with the following command:

$ sudo yum erase rsh-server

Rationale

The rsh-server package provides several obsolete and insecure network services. Removing it decreases the risk of those services' accidental (or intentional) activation.

Disable rexec Serviceservice_rexec_disabled CCE-RHEL7-CCE-TBD

Disable rexec Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 68, 1436, Test attestation on 20121026 by DS

Description

The rexec service, which is available with the rsh-server package and runs as a service through xinetd, should be disabled. The rexec service can be disabled with the following command:

$ sudo systemctl disable rexec

Rationale

The rexec service uses unencrypted network communications, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network.

Disable rsh Serviceservice_rsh_disabled CCE-RHEL7-CCE-TBD

Disable rsh Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, IA-5(1)(c), 68, 1436, Test attestation on 20121026 by DS

Description

The rsh service, which is available with the rsh-server package and runs as a service through xinetd, should be disabled. The rsh service can be disabled with the following command:

$ sudo systemctl disable rsh

Rationale

The rsh service uses unencrypted network communications, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network.

Uninstal rsh Packagepackage_rsh_removed CCE-

Uninstal rsh Package

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

identifiers:  CCE-

references:  Test attestation on 20140530 by JL

Description

The rsh package contains the client commands for the rsh services

Rationale

These legacy clients contain numerous security exposures and have been replaced with the more secure SSH package. Even if the server is removed, it is best to ensure the clients are also removed to prevent users from inadvertently attempting to use these commands and therefore exposing their credentials. Note that removing the rsh package removes the clients for rsh,rcp, and rlogin.

Disable rlogin Serviceservice_rlogin_disabled CCE-RHEL7-CCE-TBD

Disable rlogin Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, IA-5(1)(c), 1436, Test attestation on 20121026 by DS

Description

The rlogin service, which is available with the rsh-server package and runs as a service through xinetd, should be disabled. The rlogin service can be disabled with the following command:

$ sudo systemctl disable rlogin

Rationale

The rlogin service uses unencrypted network communications, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network.

Remove Rsh Trust Filesno_rsh_trust_files CCE-RHEL7-CCE-TBD

Remove Rsh Trust Files

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 1436, Test attestation on 20121026 by DS

Description

The files /etc/hosts.equiv and ~/.rhosts (in each user's home directory) list remote hosts and users that are trusted by the local system when using the rshd daemon. To remove these files, run the following command to delete them from any location:

$ sudo rm /etc/hosts.equiv
$ rm ~/.rhosts

Rationale

Trust files are convenient, but when used in conjunction with the R-services, they can allow unauthenticated access to a system.

Uninstall ypserv Packageuninstall_ypserv CCE-RHEL7-CCE-TBD

Uninstall ypserv Package

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 305, 381, Test attestation on 20121026 by DS

Description

The ypserv package can be uninstalled with the following command:

$ sudo yum erase ypserv

Rationale

Removing the ypserv package decreases the risk of the accidental (or intentional) activation of NIS or NIS+ services.

Disable ypbind Servicedisable_ypbind CCE-RHEL7-CCE-TBD

Disable ypbind Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 305, Test attestation on 20121026 by DS

Description

The ypbind service, which allows the system to act as a client in a NIS or NIS+ domain, should be disabled. The ypbind service can be disabled with the following command:

$ sudo systemctl disable ypbind

Rationale

Disabling the ypbind service ensures the system is not acting as a client in a NIS or NIS+ domain.

Remove NIS Clientpackage_ypbind_removed CCE-

Remove NIS Client

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

identifiers:  CCE-

Description

The Network Information Service (NIS), formerly known as Yellow Pages, is a client-server directory service protocol used to distribute system configuration files. The NIS client (ypbind) was used to bind a machine to an NIS server and receive the distributed configuration files.

Rationale

The NIS service is inherently an insecure system that has been vulnerable to DOS attacks, buffer overflows and has poor authentication for querying NIS maps. NIS generally has been replaced by such protocols as Lightweight Directory Access Protocol (LDAP). It is recommended that the service be removed.

Disable tftp Serviceservice_tftp_disabled CCE-RHEL7-CCE-TBD

Disable tftp Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 1436, Test attestation on 20121026 by DS

Description

The tftp service should be disabled. The tftp service can be disabled with the following command:

$ sudo systemctl disable tftp

Rationale

Disabling the tftp service ensures the system is not acting as a TFTP server, which does not provide encryption or authentication.

Uninstall tftp-server Packageuninstall_tftp-server CCE-RHEL7-CCE-TBD

Uninstall tftp-server Package

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 305, Test attestation on 20121026 by DS

Description

The tftp-server package can be removed with the following command:

$ sudo yum erase tftp-server

Rationale

Removing the tftp-server package decreases the risk of the accidental (or intentional) activation of tftp services.

Remove tftppackage_tftp_removed CCE-

Remove tftp

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

identifiers:  CCE-

Description

Trivial File Transfer Protocol (TFTP) is a simple file transfer protocol, typically used to automatically transfer configuration or boot files between machines. TFTP does not support authentication and can be easily hacked. The package tftp is a client program that allows for connections to a tftp server.

Rationale

It is recommended that TFTP be remvoed, unless there is a specific need for TFTP (such as a boot server). In that case, use extreme caution when configuring the services.

Ensure tftp Daemon Uses Secure Modetftpd_uses_secure_mode CCE-RHEL7-CCE-TBD

Ensure tftp Daemon Uses Secure Mode

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 366

Description

If running the tftp service is necessary, it should be configured to change its root directory at startup. To do so, ensure /etc/xinetd.d/tftp includes -s as a command line argument, as shown in the following example (which is also the default):

server_args = -s /var/lib/tftpboot

Rationale

Using the -s option causes the TFTP service to only serve files from the given directory. Serving files from an intentionally-specified directory reduces the risk of sharing files which should remain private.

Uninstall talk-server Packageuninstall_talk-server CCE-

Uninstall talk-server Package

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

identifiers:  CCE-

references:  Test attestation on 20140625 by JL

Description

The talk-server package can be removed with the following command:

$ sudo yum erase talk-server

Rationale

The talk software presents a security risk as it uses unencrypted protocols for communications. Removing the talk-server package decreases the risk of the accidental (or intentional) activation of talk services.

Uninstall talk Packagepackage_talk_removed CCE-

Uninstall talk Package

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

identifiers:  CCE-

references:  Test attestation on 20140625 by JL

Description

The talk package contains the client program for the Internet talk protocol, which allows the user to chat with other users on different systems. Talk is a communication program which copies lines from one terminal to the terminal of another user.

Rationale

The talk software presents a security risk as it uses unencrypted protocols for communications. Removing the talk package decreases the risk of the accidental (or intentional) activation of talk client program.

Disable Automatic Bug Reporting Tool (abrtd)service_abrtd_disabled CCE-26872-2

Disable Automatic Bug Reporting Tool (abrtd)

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

identifiers:  CCE-26872-2

references:  AC-17(8), CM-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20140921 by JL

Description

The Automatic Bug Reporting Tool (abrtd) daemon collects and reports crash data when an application crash is detected. Using a variety of plugins, abrtd can email crash reports to system administrators, log crash reports to files, or forward crash reports to a centralized issue tracking system such as RHTSupport. The abrtd service can be disabled with the following command:

$ sudo systemctl disable abrtd

Rationale

Mishandling crash data could expose sensitive information about vulnerabilities in software executing on the local machine, as well as sensitive information from within a process's address space or registers.

Disable Advanced Configuration and Power Interface (acpid)service_acpid_disabled CCE-RHEL7-CCE-TBD

Disable Advanced Configuration and Power Interface (acpid)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

The Advanced Configuration and Power Interface Daemon (acpid) dispatches ACPI events (such as power/reset button depressed) to userspace programs. The acpid service can be disabled with the following command:

$ sudo systemctl disable acpid

Rationale

ACPI support is highly desirable for systems in some network roles, such as laptops or desktops. For other systems, such as servers, it may permit accidental or trivially achievable denial of service situations and disabling it is appropriate.

Disable Certmonger Service (certmonger)service_certmonger_disabled CCE-RHEL7-CCE-TBD

Disable Certmonger Service (certmonger)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

Certmonger is a D-Bus based service that attempts to simplify interaction with certifying authorities on networks which use public-key infrastructure. It is often combined with Red Hat's IPA (Identity Policy Audit) security information management solution to aid in the management of certificates. The certmonger service can be disabled with the following command:

$ sudo systemctl disable certmonger

Rationale

The services provided by certmonger may be essential for systems fulfilling some roles a PKI infrastructure, but its functionality is not necessary for many other use cases.

Disable Control Group Config (cgconfig)service_cgconfig_disabled CCE-RHEL7-CCE-TBD

Disable Control Group Config (cgconfig)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

Control groups allow an administrator to allocate system resources (such as CPU, memory, network bandwidth, etc) among a defined group (or groups) of processes executing on a system. The cgconfig daemon starts at boot and establishes the predefined control groups. The cgconfig service can be disabled with the following command:

$ sudo systemctl disable cgconfig

Rationale

Unless control groups are used to manage system resources, running the cgconfig service is not necessary.

Disable Control Group Rules Engine (cgred)service_cgred_disabled CCE-RHEL7-CCE-TBD

Disable Control Group Rules Engine (cgred)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

The cgred service moves tasks into control groups according to parameters set in the /etc/cgrules.conf configuration file. The cgred service can be disabled with the following command:

$ sudo systemctl disable cgred

Rationale

Unless control groups are used to manage system resources, running the cgred service service is not necessary.

Disable CPU Speed (cpuspeed)service_cpuspeed_disabled CCE-RHEL7-CCE-TBD

Disable CPU Speed (cpuspeed)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

The cpuspeed service can adjust the clock speed of supported CPUs based upon the current processing load thereby conserving power and reducing heat. The cpuspeed service can be disabled with the following command:

$ sudo systemctl disable cpuspeed

Rationale

The cpuspeed service is only necessary if adjusting the CPU clock speed provides benefit. Traditionally this has included laptops (to enhance battery life), but may also apply to server or desktop environments where conserving power is highly desirable or necessary.

Enable IRQ Balance (irqbalance)service_irqbalance_enabled CCE-RHEL7-CCE-TBD

Enable IRQ Balance (irqbalance)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

The irqbalance service optimizes the balance between power savings and performance through distribution of hardware interrupts across multiple processors. The irqbalance service can be enabled with the following command:

$ sudo systemctl enable irqbalance

Rationale

In an environment with multiple processors (now common), the irqbalance service provides potential speedups for handling interrupt requests.

Disable KDump Kernel Crash Analyzer (kdump)service_kdump_disabled CCE-RHEL7-CCE-TBD

Disable KDump Kernel Crash Analyzer (kdump)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7

Description

The kdump service provides a kernel crash dump analyzer. It uses the kexec system call to boot a secondary kernel ("capture" kernel) following a system crash, which can load information from the crashed kernel for analysis. The kdump service can be disabled with the following command:

$ sudo systemctl disable kdump

Rationale

Unless the system is used for kernel development or testing, there is little need to run the kdump service.

Disable Software RAID Monitor (mdmonitor)service_mdmonitor_disabled CCE-RHEL7-CCE-TBD

Disable Software RAID Monitor (mdmonitor)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

The mdmonitor service is used for monitoring a software RAID array; hardware RAID setups do not use this service. The mdmonitor service can be disabled with the following command:

$ sudo systemctl disable mdmonitor

Rationale

If software RAID monitoring is not required, there is no need to run this service.

Disable D-Bus IPC Service (messagebus)service_messagebus_disabled CCE-RHEL7-CCE-TBD

Disable D-Bus IPC Service (messagebus)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

D-Bus provides an IPC mechanism used by a growing list of programs, such as those used for Gnome, Bluetooth, and Avahi. Due to these dependencies, disabling D-Bus may not be practical for many systems. The messagebus service can be disabled with the following command:

$ sudo systemctl disable messagebus

Rationale

If no services which require D-Bus are needed, then it can be disabled. As a broker for IPC between processes of different privilege levels, it could be a target for attack. However, disabling D-Bus is likely to be impractical for any system which needs to provide a graphical login session.

Disable Network Console (netconsole)service_netconsole_disabled CCE-RHEL7-CCE-TBD

Disable Network Console (netconsole)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 381

Description

The netconsole service is responsible for loading the netconsole kernel module, which logs kernel printk messages over UDP to a syslog server. This allows debugging of problems where disk logging fails and serial consoles are impractical. The netconsole service can be disabled with the following command:

$ sudo systemctl disable netconsole

Rationale

The netconsole service is not necessary unless there is a need to debug kernel panics, which is not common.

Disable ntpdate Service (ntpdate)service_ntpdate_disabled CCE-RHEL7-CCE-TBD

Disable ntpdate Service (ntpdate)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 382, Test attestation on 20121024 by DS

Description

The ntpdate service sets the local hardware clock by polling NTP servers when the system boots. It synchronizes to the NTP servers listed in /etc/ntp/step-tickers or /etc/ntp.conf and then sets the local hardware clock to the newly synchronized system time. The ntpdate service can be disabled with the following command:

$ sudo systemctl disable ntpdate

Rationale

The ntpdate service may only be suitable for systems which are rebooted frequently enough that clock drift does not cause problems between reboots. In any event, the functionality of the ntpdate service is now available in the ntpd program and should be considered deprecated.

Disable Odd Job Daemon (oddjobd)service_oddjobd_disabled CCE-RHEL7-CCE-TBD

Disable Odd Job Daemon (oddjobd)

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

The oddjobd service exists to provide an interface and access control mechanism through which specified privileged tasks can run tasks for unprivileged client applications. Communication with oddjobd through the system message bus. The oddjobd service can be disabled with the following command:

$ sudo systemctl disable oddjobd

Rationale

The oddjobd service may provide necessary functionality in some environments, and can be disabled if it is not needed. Execution of tasks by privileged programs, on behalf of unprivileged ones, has traditionally been a source of privilege escalation security issues.

Disable Portreserve (portreserve)service_portreserve_disabled CCE-RHEL7-CCE-TBD

Disable Portreserve (portreserve)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, Test attestation on 20121024 by DS

Description

The portreserve service is a TCP port reservation utility that can be used to prevent portmap from binding to well known TCP ports that are required for other services. The portreserve service can be disabled with the following command:

$ sudo systemctl disable portreserve

Rationale

The portreserve service provides helpful functionality by preventing conflicting usage of ports in the reserved port range, but it can be disabled if not needed.

Enable Process Accounting (psacct)service_psacct_enabled CCE-RHEL7-CCE-TBD

Enable Process Accounting (psacct)

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

The process accounting service, psacct, works with programs including acct and ac to allow system administrators to view user activity, such as commands issued by users of the system. The psacct service can be enabled with the following command:

$ sudo systemctl enable psacct

Rationale

The psacct service can provide administrators a convenient view into some user activities. However, it should be noted that the auditing system and its audit records provide more authoritative and comprehensive records.

Disable Apache Qpid (qpidd)service_qpidd_disabled CCE-RHEL7-CCE-TBD

Disable Apache Qpid (qpidd)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 382

Description

The qpidd service provides high speed, secure, guaranteed delivery services. It is an implementation of the Advanced Message Queuing Protocol. By default the qpidd service will bind to port 5672 and listen for connection attempts. The qpidd service can be disabled with the following command:

$ sudo systemctl disable qpidd

Rationale

The qpidd service is automatically installed when the "base" package selection is selected during installation. The qpidd service listens for network connections, which increases the attack surface of the system. If the system is not intended to receive AMQP traffic, then the qpidd service is not needed and should be disabled or removed.

Disable Quota Netlink (quota_nld)service_quota_nld_disabled CCE-RHEL7-CCE-TBD

Disable Quota Netlink (quota_nld)

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

The quota_nld service provides notifications to users of disk space quota violations. It listens to the kernel via a netlink socket for disk quota violations and notifies the appropriate user of the violation using D-Bus or by sending a message to the terminal that the user has last accessed. The quota_nld service can be disabled with the following command:

$ sudo systemctl disable quota_nld

Rationale

If disk quotas are enforced on the local system, then the quota_nld service likely provides useful functionality and should remain enabled. However, if disk quotas are not used or user notification of disk quota violation is not desired then there is no need to run this service.

Disable Network Router Discovery Daemon (rdisc)service_rdisc_disabled CCE-RHEL7-CCE-TBD

Disable Network Router Discovery Daemon (rdisc)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), AC-4, CM-7, 382, Test attestation on 20121024 by DS

Description

The rdisc service implements the client side of the ICMP Internet Router Discovery Protocol (IRDP), which allows discovery of routers on the local subnet. If a router is discovered then the local routing table is updated with a corresponding default route. By default this daemon is disabled. The rdisc service can be disabled with the following command:

$ sudo systemctl disable rdisc

Rationale

General-purpose systems typically have their network and routing information configured statically by a system administrator. Workstations or some special-purpose systems often use DHCP (instead of IRDP) to retrieve dynamic network configuration information.

Disable Red Hat Network Service (rhnsd)service_rhnsd_disabled CCE-RHEL7-CCE-TBD

Disable Red Hat Network Service (rhnsd)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, 382, Test attestation on 20121024 by DS

Description

The Red Hat Network service automatically queries Red Hat Network servers to determine whether there are any actions that should be executed, such as package updates. This only occurs if the system was registered to an RHN server or satellite and managed as such. The rhnsd service can be disabled with the following command:

$ sudo systemctl disable rhnsd

Rationale

Although systems management and patching is extremely important to system security, management by a system outside the enterprise enclave is not desirable for some environments. However, if the system is being managed by RHN or RHN Satellite Server the rhnsd daemon can remain on.

Disable Red Hat Subscription Manager Daemon (rhsmcertd)service_rhsmcertd_disabled CCE-RHEL7-CCE-TBD

Disable Red Hat Subscription Manager Daemon (rhsmcertd)

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

The Red Hat Subscription Manager (rhsmcertd) periodically checks for changes in the entitlement certificates for a registered system and updates it accordingly. The rhsmcertd service can be disabled with the following command:

$ sudo systemctl disable rhsmcertd

Rationale

The rhsmcertd service can provide administrators with some additional control over which of their systems are entitled to particular subscriptions. However, for systems that are managed locally or which are not expected to require remote changes to their subscription status, it is unnecessary and can be disabled.

Disable Cyrus SASL Authentication Daemon (saslauthd)service_saslauthd_disabled CCE-RHEL7-CCE-TBD

Disable Cyrus SASL Authentication Daemon (saslauthd)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-17(8), CM-7, Test attestation on 20121024 by DS

Description

The saslauthd service handles plaintext authentication requests on behalf of the SASL library. The service isolates all code requiring superuser privileges for SASL authentication into a single process, and can also be used to provide proxy authentication services to clients that do not understand SASL based authentication. The saslauthd service can be disabled with the following command:

$ sudo systemctl disable saslauthd

Rationale

The saslauthd service provides essential functionality for performing authentication in some directory environments, such as those which use Kerberos and LDAP. For others, however, in which only local files may be consulted, it is not necessary and should be disabled.

Disable SMART Disk Monitoring Service (smartd)service_smartd_disabled CCE-RHEL7-CCE-TBD

Disable SMART Disk Monitoring Service (smartd)

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

SMART (Self-Monitoring, Analysis, and Reporting Technology) is a feature of hard drives that allows them to detect symptoms of disk failure and relay an appropriate warning. The smartd service can be disabled with the following command:

$ sudo systemctl disable smartd

Rationale

SMART can help protect against denial of service due to failing hardware. Nevertheless, if it is not needed or the system's drives are not SMART-capable (such as solid state drives), it can be disabled.

Disable System Statistics Reset Service (sysstat)service_sysstat_disabled CCE-RHEL7-CCE-TBD

Disable System Statistics Reset Service (sysstat)

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

The sysstat service resets various I/O and CPU performance statistics to zero in order to begin counting from a fresh state at boot time. The sysstat service can be disabled with the following command:

$ sudo systemctl disable sysstat

Rationale

By default the sysstat service merely runs a program at boot to reset the statistics, which can be retrieved using programs such as sar and sadc. These may provide useful insight into system operation, but unless used this service can be disabled.

Enable cron Serviceservice_crond_enabled CCE-RHEL7-CCE-TBD

Enable cron Service

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

The crond service is used to execute commands at preconfigured times. It is required by almost all systems to perform necessary maintenance tasks, such as notifying root of system activity. The crond service can be enabled with the following command:

$ sudo systemctl enable crond

Rationale

Due to its usage for maintenance and security-supporting tasks, enabling the cron daemon is essential.

Disable anacron Servicedisable_anacron CCE-RHEL7-CCE-TBD

Disable anacron Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

The cronie-anacron package, which provides anacron functionality, is installed by default. The cronie-anacron package can be removed with the following command:

$ sudo yum erase cronie-anacron

Rationale

The anacron service provides cron functionality for systems such as laptops and workstations that may be shut down during the normal times that cron jobs are scheduled to run. On systems which do not require this additional functionality, anacron could needlessly increase the possible attack surface for an intruder.

Disable At Service (atd)service_atd_disabled CCE-RHEL7-CCE-TBD

Disable At Service (atd)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 381

Description

The at and batch commands can be used to schedule tasks that are meant to be executed only once. This allows delayed execution in a manner similar to cron, except that it is not recurring. The daemon atd keeps track of tasks scheduled via at and batch, and executes them at the specified time. The atd service can be disabled with the following command:

$ sudo systemctl disable atd

Rationale

The atd service could be used by an unsophisticated insider to carry out activities outside of a normal login session, which could complicate accountability. Furthermore, the need to schedule tasks with at or batch is not common.

Allow Only SSH Protocol 2sshd_allow_only_protocol2 CCE-27038-9

Allow Only SSH Protocol 2

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

identifiers:  CCE-27038-9

references:  AC-17(7), IA-5(1)(c), http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS

Description

Only SSH protocol version 2 connections should be permitted. The default setting in /etc/ssh/sshd_config is correct, and can be verified by ensuring that the following line appears:

Protocol 2

Rationale

SSH protocol version 1 suffers from design flaws that result in security vulnerabilities and should not be used.

Limit Users' SSH Accesssshd_limit_user_access CCE-RHEL7-CCE-TBD

Limit Users' SSH Access

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-3

Description

By default, the SSH configuration allows any user with an account to access the system. In order to specify the users that are allowed to login via SSH and deny all other users, add or correct the following line in the /etc/ssh/sshd_config file:

DenyUsers USER1 USER2
Where USER1 and USER2 are valid user names.

Rationale

Specifying which accounts are allowed SSH access into the system reduces the possibility of unauthorized access to the system.

Set SSH Idle Timeout Intervalsshd_set_idle_timeout CCE-26611-4

Set SSH Idle Timeout Interval

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

identifiers:  CCE-26611-4

references:  AC-2(5), SA-8, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS

Description

SSH allows administrators to set an idle timeout interval. After this interval has passed, the idle user will be automatically logged out.

To set an idle timeout interval, edit the following line in /etc/ssh/sshd_config as follows:

ClientAliveInterval interval
The timeout interval is given in seconds. To have a timeout of 15 minutes, set interval to 900.

If a shorter timeout has already been set for the login shell, that value will preempt any SSH setting made here. Keep in mind that some processes may stop SSH from correctly detecting that the user is idle.

Rationale

Causing idle users to be automatically logged out guards against compromises one system leading trivially to compromises on another.

Set SSH Client Alive Countsshd_set_keepalive CCE-27066-0

Set SSH Client Alive Count

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

identifiers:  CCE-27066-0

references:  AC-2(5), SA-8, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS

Description

To ensure the SSH idle timeout occurs precisely when the ClientAliveCountMax is set, edit /etc/ssh/sshd_config as follows:

ClientAliveCountMax 0

Rationale

This ensures a user login will be terminated as soon as the ClientAliveCountMax is reached.

Disable SSH Support for .rhosts Filessshd_disable_rhosts CCE-27035-5

Disable SSH Support for .rhosts Files

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

identifiers:  CCE-27035-5

references:  AC-3, http://iase.disa.mil/stigs/cci/Pages/index.aspx

Description

SSH can emulate the behavior of the obsolete rsh command in allowing users to enable insecure access to their accounts via .rhosts files.

To ensure this behavior is disabled, add or correct the following line in /etc/ssh/sshd_config:

IgnoreRhosts yes

Rationale

SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts.

Disable Host-Based Authenticationdisable_host_auth CCE-26870-6

Disable Host-Based Authentication

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

identifiers:  CCE-26870-6

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

Description

SSH's cryptographic host-based authentication is more secure than .rhosts authentication. However, it is not recommended that hosts unilaterally trust one another, even within an organization.

To disable host-based authentication, add or correct the following line in /etc/ssh/sshd_config:

HostbasedAuthentication no

Rationale

SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts.

Disable SSH Access via Empty Passwordssshd_disable_empty_passwords CCE-26864-9

Disable SSH Access via Empty Passwords

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

identifiers:  CCE-26864-9

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

Description

To explicitly disallow remote login from accounts with empty passwords, add or correct the following line in /etc/ssh/sshd_config:

PermitEmptyPasswords no
Any accounts with empty passwords should be disabled immediately, and PAM configuration should prevent users from being able to assign themselves empty passwords.

Rationale

Configuring this setting for the SSH daemon provides additional assurance that remote login via SSH will require a password, even in the event of misconfiguration elsewhere.

Enable SSH Warning Bannersshd_enable_warning_banner CCE-27314-4

Enable SSH Warning Banner

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

identifiers:  CCE-27314-4

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

Description

To enable the warning banner and ensure it is consistent across the system, add or correct the following line in /etc/ssh/sshd_config:

Banner /etc/issue
Another section contains information on how to create an appropriate system-wide warning banner.

Rationale

The warning message reinforces policy awareness during the logon process and facilitates possible legal action against attackers. Alternatively, systems whose ownership should not be obvious should ensure usage of a banner that does not provide easy attribution.

Do Not Allow SSH Environment Optionssshd_do_not_permit_user_env CCE-26974-6

Do Not Allow SSH Environment Options

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

identifiers:  CCE-26974-6

references:  http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS

Description

To ensure users are not able to present environment options to the SSH daemon, add or correct the following line in /etc/ssh/sshd_config:

PermitUserEnvironment no

Rationale

SSH environment options potentially allow users to bypass access restriction in some configurations.

Use Only Approved Cipherssshd_use_approved_ciphers CCE-27051-2

Use Only Approved Ciphers

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

identifiers:  CCE-27051-2

references:  AC-3, AC-17(2), AU-10(5), IA-5(1)(c), IA-7, http://iase.disa.mil/stigs/cci/Pages/index.aspx, Test attestation on 20121024 by DS

Description

Limit the ciphers to those algorithms which are FIPS-approved. Counter (CTR) mode is also preferred over cipher-block chaining (CBC) mode. The following line in /etc/ssh/sshd_config demonstrates use of FIPS-approved ciphers:

Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc
The man page sshd_config(5) contains a list of supported ciphers.

Rationale

Approved algorithms should impart some level of confidence in their implementation. These are also required for compliance.

Disable SSH Server If Possible (Unusual)ssh_server_disabled CCE-RHEL7-CCE-TBD

Disable SSH Server If Possible (Unusual)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  Test attestation on 20121024 by DS

Description

The SSH server service, sshd, is commonly needed. However, if it can be disabled, do so. The sshd service can be disabled with the following command:

$ sudo systemctl disable sshd
This is unusual, as SSH is a common method for encrypted and authenticated remote access.

Remove SSH Server iptables Firewall exception (Unusual)ssh_server_iptables_exception CCE-RHEL7-CCE-TBD

Remove SSH Server iptables Firewall exception (Unusual)

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

By default, inbound connections to SSH's port are allowed. If the SSH server is not being used, this exception should be removed from the firewall configuration.

Edit the files /etc/sysconfig/iptables and /etc/sysconfig/ip6tables (if IPv6 is in use). In each file, locate and delete the line:

-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
This is unusual, as SSH is a common method for encrypted and authenticated remote access.

Rationale

If inbound SSH connections are not expected, disallowing access to the SSH port will avoid possible exploitation of the port by an attacker.

Disable X Windows Startup By Setting Default Targetdisable_xwindows_with_target CCE-RHEL7-CCE-TBD

Disable X Windows Startup By Setting Default Target

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-3, 366, Test attestation on 20121025 by DS

Description

Setting the system's default target to multi-user will prevent automatic startup of the X server. To do so, run:

$ systemctl set-default multi-user.target
You should see the following output:
rm '/etc/systemd/system/default.target'
ln -s '/usr/lib/systemd/system/multi-user.target' '/etc/systemd/system/default.target'

Rationale

Unnecessary services should be disabled to decrease the attack surface of the system.

Remove the X Windows Package Grouppackagegroup_xwindows_remove CCE-RHEL7-CCE-TBD

Remove the X Windows Package Group

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  366, Test attestation on 20121025 by DS

Description

Removing all packages which constitute the X Window System ensures users or malicious software cannot start X. To do so, run the following command:

$ sudo yum groupremove "X Window System"

Rationale

Unnecessary packages should not be installed to decrease the attack surface of the system.

Disable Avahi Server Softwaredisable_avahi CCE-RHEL7-CCE-TBD

Disable Avahi Server Software

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 366

Description

The avahi-daemon service can be disabled with the following command:

$ sudo systemctl disable avahi-daemon

Rationale

Because the Avahi daemon service keeps an open network port, it is subject to network attacks. Its functionality is convenient but is only appropriate if the local network can be trusted.

Serve Avahi Only via Required Protocolavahi_ip_only CCE-RHEL7-CCE-TBD

Serve Avahi Only via Required Protocol

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

If you are using only IPv4, edit /etc/avahi/avahi-daemon.conf and ensure the following line exists in the [server] section:

use-ipv6=no
Similarly, if you are using only IPv6, disable IPv4 sockets with the line:
use-ipv4=no

Check Avahi Responses' TTL Fieldavahi_check_ttl CCE-RHEL7-CCE-TBD

Check Avahi Responses' TTL Field

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To make Avahi ignore packets unless the TTL field is 255, edit /etc/avahi/avahi-daemon.conf and ensure the following line appears in the [server] section:

check-response-ttl=yes

Rationale

This helps to ensure that only mDNS responses from the local network are processed, because the TTL field in a packet is decremented from its initial value of 255 whenever it is routed from one network to another. Although a properly-configured router or firewall should not allow mDNS packets into the local network at all, this option provides another check to ensure they are not permitted.

Prevent Other Programs from Using Avahi's Portavahi_prevent_port_sharing CCE-RHEL7-CCE-TBD

Prevent Other Programs from Using Avahi's Port

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To prevent other mDNS stacks from running, edit /etc/avahi/avahi-daemon.conf and ensure the following line appears in the [server] section:

disallow-other-stacks=yes

Rationale

This helps ensure that only Avahi is responsible for mDNS traffic coming from that port on the system.

Disable Avahi Publishingavahi_disable_publishing CCE-RHEL7-CCE-TBD

Disable Avahi Publishing

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To prevent other mDNS stacks from running, edit /etc/avahi/avahi-daemon.conf and ensure the following line appears in the [server] section:

disallow-other-stacks=yes

Rationale

This helps ensure that only Avahi is responsible for mDNS traffic coming from that port on the system.

Restrict Information Published by Avahiavahi_restrict_published_information CCE-RHEL7-CCE-TBD

Restrict Information Published by Avahi

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

If it is necessary to publish some information to the network, it should not be joined by any extraneous information, or by information supplied by a non-trusted source on the system. Prevent user applications from using Avahi to publish services by adding or correcting the following line in the [publish] section:

disable-user-service-publishing=yes
Implement as many of the following lines as possible, to restrict the information published by Avahi.
publish-addresses=no
publish-hinfo=no
publish-workstation=no
publish-domain=no
Inspect the files in the directory /etc/avahi/services/. Unless there is an operational need to publish information about each of these services, delete the corresponding file.

Rationale

These options prevent publishing attempts from succeeding, and can be applied even if publishing is disabled entirely via disable-publishing. Alternatively, these can be used to restrict the types of published information in the event that some information must be published.

Disable Printer Browsing Entirely if Possiblecups_disable_browsing CCE-RHEL7-CCE-TBD

Disable Printer Browsing Entirely if Possible

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

By default, CUPS listens on the network for printer list broadcasts on UDP port 631. This functionality is called printer browsing. To disable printer browsing entirely, edit the CUPS configuration file, located at /etc/cups/cupsd.conf, to include the following:

Browsing Off

Rationale

The CUPS print service can be configured to broadcast a list of available printers to the network. Other machines on the network, also running the CUPS print service, can be configured to listen to these broadcasts and add and configure these printers for immediate use. By disabling this browsing capability, the machine will no longer generate or receive such broadcasts.

Disable Print Server Capabilitiescups_disable_printserver CCE-RHEL7-CCE-TBD

Disable Print Server Capabilities

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To prevent remote users from potentially connecting to and using locally configured printers, disable the CUPS print server sharing capabilities. To do so, limit how the server will listen for print jobs by removing the more generic port directive from /etc/cups/cupsd.conf:

Port 631
and replacing it with the Listen directive:
Listen localhost:631
This will prevent remote users from printing to locally configured printers while still allowing local users on the machine to print normally.

Rationale

By default, locally configured printers will not be shared over the network, but if this functionality has somehow been enabled, these recommendations will disable it again. Be sure to disable outgoing printer list broadcasts, or remote users will still be able to see the locally configured printers, even if they cannot actually print to them. To limit print serving to a particular set of users, use the Policy directive.

Disable the CUPS Serviceservice_cups_disabled CCE-RHEL7-CCE-TBD

Disable the CUPS Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

The cups service can be disabled with the following command:

$ sudo systemctl disable cups

Rationale

Turn off unneeded services to reduce attack surface.

Disable DHCP Servicedisable_dhcp_server CCE-RHEL7-CCE-TBD

Disable DHCP Service

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

The dhcpd service should be disabled on any system that does not need to act as a DHCP server. The dhcpd service can be disabled with the following command:

$ sudo systemctl disable dhcpd

Rationale

Unmanaged or unintentionally activated DHCP servers may provide faulty information to clients, interfering with the operation of a legitimate site DHCP server if there is one.

Uninstall DHCP Server Packageuninstall_dhcp_server CCE-RHEL7-CCE-TBD

Uninstall DHCP Server Package

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

If the system does not need to act as a DHCP server, the dhcp package can be uninstalled. The dhcp package can be removed with the following command:

$ sudo yum erase dhcp

Rationale

Removing the DHCP server ensures that it cannot be easily or accidentally reactivated and disrupt network operation.

Do Not Use Dynamic DNSdhcp_server_disable_ddns CCE-RHEL7-CCE-TBD

Do Not Use Dynamic DNS

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

To prevent the DHCP server from receiving DNS information from clients, edit /etc/dhcp/dhcpd.conf, and add or correct the following global option:

ddns-update-style none;

Rationale

The Dynamic DNS protocol is used to remotely update the data served by a DNS server. DHCP servers can use Dynamic DNS to publish information about their clients. This setup carries security risks, and its use is not recommended. If Dynamic DNS must be used despite the risks it poses, it is critical that Dynamic DNS transactions be protected using TSIG or some other cryptographic authentication mechanism. See dhcpd.conf(5) for more information about protecting the DHCP server from passing along malicious DNS data from its clients.

Warnings
warning  The ddns-update-style option controls only whether the DHCP server will attempt to act as a Dynamic DNS client. As long as the DNS server itself is correctly configured to reject DDNS attempts, an incorrect ddns-update-style setting on the client is harmless (but should be fixed as a best practice).
Deny Decline Messagesdhcp_server_deny_decline CCE-RHEL7-CCE-TBD

Deny Decline Messages

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

Edit /etc/dhcp/dhcpd.conf and add or correct the following global option to prevent the DHCP server from responding the DHCPDECLINE messages, if possible:

deny declines;

Rationale

The DHCPDECLINE message can be sent by a DHCP client to indicate that it does not consider the lease offered by the server to be valid. By issuing many DHCPDECLINE messages, a malicious client can exhaust the DHCP server's pool of IP addresses, causing the DHCP server to forget old address allocations.

Deny BOOTP Queriesdhcp_server_deny_bootp CCE-RHEL7-CCE-TBD

Deny BOOTP Queries

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

Unless your network needs to support older BOOTP clients, disable support for the bootp protocol by adding or correcting the global option:

deny bootp;

Rationale

The bootp option tells dhcpd to respond to BOOTP queries. If support for this simpler protocol is not needed, it should be disabled to remove attack vectors against the DHCP server.

Configure Loggingdhcp_server_configure_logging CCE-RHEL7-CCE-TBD

Configure Logging

Rule IDdhcp_server_configure_logging
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 the following line exists in /etc/rsyslog.conf:

daemon.*           /var/log/daemon.log
Configure logwatch or other log monitoring tools to summarize error conditions reported by the dhcpd process.

Rationale

By default, dhcpd logs notices to the daemon facility. Sending all daemon messages to a dedicated log file is part of the syslog configuration outlined in the Logging and Auditing section

Disable DHCP Clientdisable_dhcp_client CCE-RHEL7-CCE-TBD

Disable DHCP Client

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

For each interface on the system (e.g. eth0), edit /etc/sysconfig/network-scripts/ifcfg-interface and make the following changes:

  • Correct the BOOTPROTO line to read:
    BOOTPROTO=none
  • Add or correct the following lines, substituting the appropriate values based on your site's addressing scheme:
    NETMASK=255.255.255.0
    IPADDR=192.168.1.2
    GATEWAY=192.168.1.1

Rationale

DHCP relies on trusting the local network. If the local network is not trusted, then it should not be used. However, the automatic configuration provided by DHCP is commonly used and the alternative, manual configuration, presents an unacceptable burden in many circumstances.

Enable the NTP Daemonservice_chronyd_or_ntpd_enabled CCE-RHEL7-CCE-TBD

Enable the NTP Daemon

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-8(1), 160, Test attestation on 20121024 by DS

Description

The chronyd service can be enabled with the following command:

$ sudo systemctl enable chronyd
Note: The chronyd daemon is enabled by default.

The ntpd service can be enabled with the following command:
$ sudo systemctl enable ntpd
Note: The ntpd daemon is not enabled by default. Though as mentioned in the previous sections in certain environments the ntpd daemon might be preferred to be used rather than the chronyd one. Refer to: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Configuring_NTP_Using_the_chrony_Suite.html for guidance which NTP daemon to choose depending on the environment used.

Rationale

Enabling some of chronyd or ntpd services ensures that the NTP daemon will be running and that the system will synchronize its time to any servers specified. This is important whether the system is configured to be a client (and synchronize only its own clock) or it is also acting as an NTP server to other systems. Synchronizing time is essential for authentication services such as Kerberos, but it is also important for maintaining accurate logs and auditing possible security breaches.

The chronyd and ntpd NTP daemons offer all of the functionality of ntpdate, which is now deprecated. Additional information on this is available at http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate

Specify a Remote NTP Serverntpd_specify_remote_server CCE-RHEL7-CCE-TBD

Specify a Remote NTP Server

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-8(1), 160, Test attestation on 20121024 by DS

Description

To specify a remote NTP server for time synchronization, edit the file /etc/ntp.conf. Add or correct the following lines, substituting the IP or hostname of a remote NTP server for ntpserver:

server ntpserver
This instructs the NTP software to contact that remote server to obtain time data.

Rationale

Synchronizing with an NTP server makes it possible to collate system logs from multiple sources or correlate computer events with real time events.

Specify Additional Remote NTP Serversntpd_specify_multiple_servers CCE-RHEL7-CCE-TBD

Specify Additional Remote NTP Servers

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AU-8(1)

Description

Additional NTP servers can be specified for time synchronization in the file /etc/ntp.conf. To do so, add additional lines of the following form, substituting the IP address or hostname of a remote NTP server for ntpserver:

server ntpserver

Rationale

Specifying additional NTP servers increases the availability of accurate time data, in the event that one of the specified servers becomes unavailable. This is typical for a system acting as an NTP server for other systems.

Disable Postfix Network Listeningpostfix_network_listening_disabled CCE-RHEL7-CCE-TBD

Disable Postfix Network Listening

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

Edit the file /etc/postfix/main.cf to ensure that only the following inet_interfaces line appears:

inet_interfaces = localhost

Rationale

This ensures postfix accepts mail messages (such as cron job reports) from the local system only, and not from the network, which protects it from network attack.

Configure SMTP Greeting Bannerpostfix_server_banner CCE-RHEL7-CCE-TBD

Configure SMTP Greeting Banner

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  AC-22, AU-13

Description

Edit /etc/postfix/main.cf, and add or correct the following line, substituting some other wording for the banner information if you prefer:

smtpd_banner = $myhostname ESMTP

Rationale

The default greeting banner discloses that the listening mail process is Postfix. When remote mail senders connect to the MTA on port 25, they are greeted by an initial banner as part of the SMTP dialogue. This banner is necessary, but it frequently gives away too much information, including the MTA software which is in use, and sometimes also its version number. Remote mail senders do not need this information in order to send mail, so the banner should be changed to reveal only the hostname (which is already known and may be useful) and the word ESMTP, to indicate that the modern SMTP protocol variant is supported.

Enable Postfix Serviceservice_postfix_enabled CCE-RHEL7-CCE-TBD

Enable Postfix Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  Test attestation on 20121024 by DS

Description

The Postfix mail transfer agent is used for local mail delivery within the system. The default configuration only listens for connections to the default SMTP port (port 25) on the loopback interface (127.0.0.1). It is recommended to leave this service enabled for local mail delivery. The postfix service can be enabled with the following command:

$ sudo systemctl enable postfix

Rationale

Local mail delivery is essential to some system maintenance and notification tasks.

Uninstall Sendmail Packagepackage_sendmail_removed CCE-RHEL7-CCE-TBD

Uninstall Sendmail Package

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

Sendmail is not the default mail transfer agent and is not installed by default. The sendmail package can be removed with the following command:

$ sudo yum erase sendmail

Rationale

The sendmail software was not developed with security in mind and its design prevents it from being effectively contained by SELinux. Postfix should be used instead.

Configure LDAP Client to Use TLS For All Transactionsldap_client_start_tls CCE-RHEL7-CCE-TBD

Configure LDAP Client to Use TLS For All Transactions

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 776, 778, 1453, Test attestation on 20121024 by DS

Description

Configure LDAP to enforce TLS use. First, edit the file /etc/pam_ldap.conf, and add or correct the following lines:

ssl start_tls
Then review the LDAP server and ensure TLS has been configured.

Rationale

The ssl directive specifies whether to use ssl or not. If not specified it will default to no. It should be set to start_tls rather than doing LDAP over SSL.

Configure Certificate Directives for LDAP Use of TLSldap_client_tls_cacertpath CCE-RHEL7-CCE-TBD

Configure Certificate Directives for LDAP Use of TLS

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 776, 778, 1453, Test attestation on 20121024 by DS

Description

Ensure a copy of a trusted CA certificate has been placed in the file /etc/pki/tls/CA/cacert.pem. Configure LDAP to enforce TLS use and to trust certificates signed by that CA. First, edit the file /etc/pam_ldap.conf, and add or correct either of the following lines:

tls_cacertdir /etc/pki/tls/CA
or
tls_cacertfile /etc/pki/tls/CA/cacert.pem
Then review the LDAP server and ensure TLS has been configured.

Rationale

The tls_cacertdir or tls_cacertfile directives are required when tls_checkpeer is configured (which is the default for openldap versions 2.1 and up). These directives define the path to the trust certificates signed by the site CA.

Uninstall openldap-servers Packagepackage_openldap-servers_removed CCE-RHEL7-CCE-TBD

Uninstall openldap-servers Package

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

identifiers:  CCE-RHEL7-CCE-TBD

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

Description

The openldap-servers package should be removed if not in use. Is this machine the OpenLDAP server? If not, remove the package.

$ sudo yum erase openldap-servers
The openldap-servers RPM is not installed by default on RHEL 7 machines. It is needed only by the OpenLDAP server, not by the clients which use LDAP for authentication. If the system is not intended for use as an LDAP Server it should be removed.

Rationale

Unnecessary packages should not be installed to decrease the attack surface of the system. While this software is clearly essential on an LDAP server, it is not necessary on typical desktop or workstation systems.

Disable Network File System Lock Service (nfslock)service_nfslock_disabled CCE-RHEL7-CCE-TBD

Disable Network File System Lock Service (nfslock)

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The Network File System Lock (nfslock) service starts the required remote procedure call (RPC) processes which allow clients to lock files on the server. If the local machine is not configured to mount NFS filesystems then this service should be disabled. The nfslock service can be disabled with the following command:

$ sudo systemctl disable nfslock

Disable Secure RPC Client Service (rpcgssd)service_rpcgssd_disabled CCE-RHEL7-CCE-TBD

Disable Secure RPC Client Service (rpcgssd)

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The rpcgssd service manages RPCSEC GSS contexts required to secure protocols that use RPC (most often Kerberos and NFS). The rpcgssd service is the client-side of RPCSEC GSS. If the system does not require secure RPC then this service should be disabled. The rpcgssd service can be disabled with the following command:

$ sudo systemctl disable rpcgssd

Disable RPC ID Mapping Service (rpcidmapd)service_rpcidmapd_disabled CCE-RHEL7-CCE-TBD

Disable RPC ID Mapping Service (rpcidmapd)

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The rpcidmapd service is used to map user names and groups to UID and GID numbers on NFSv4 mounts. If NFS is not in use on the local system then this service should be disabled. The rpcidmapd service can be disabled with the following command:

$ sudo systemctl disable rpcidmapd

Disable Network File Systems (netfs)service_netfs_disabled CCE-RHEL7-CCE-TBD

Disable Network File Systems (netfs)

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The netfs script manages the boot-time mounting of several types of networked filesystems, of which NFS and Samba are the most common. If these filesystem types are not in use, the script can be disabled, protecting the system somewhat against accidental or malicious changes to /etc/fstab and against flaws in the netfs script itself. The netfs service can be disabled with the following command:

$ sudo systemctl disable netfs

Configure lockd to use static TCP portnfs_fixed_lockd_tcp_port CCE-RHEL7-CCE-TBD

Configure lockd to use static TCP port

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Configure the lockd daemon to use a static TCP port as opposed to letting the RPC Bind service dynamically assign a port. Edit the file /etc/sysconfig/nfs. Add or correct the following line:

LOCKD_TCPPORT=lockd-port
Where lockd-port is a port which is not used by any other service on your network.

Rationale

Restrict service to always use a given port, so that firewalling can be done effectively.

Configure lockd to use static UDP portnfs_fixed_lockd_udp_port CCE-RHEL7-CCE-TBD

Configure lockd to use static UDP port

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Configure the lockd daemon to use a static UDP port as opposed to letting the RPC Bind service dynamically assign a port. Edit the file /etc/sysconfig/nfs. Add or correct the following line:

LOCKD_UDPPORT=lockd-port
Where lockd-port is a port which is not used by any other service on your network.

Rationale

Restricting services to always use a given port enables firewalling to be done more effectively.

Configure statd to use static portnfs_fixed_statd_port CCE-RHEL7-CCE-TBD

Configure statd to use static port

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Configure the statd daemon to use a static port as opposed to letting the RPC Bind service dynamically assign a port. Edit the file /etc/sysconfig/nfs. Add or correct the following line:

STATD_PORT=statd-port
Where statd-port is a port which is not used by any other service on your network.

Rationale

Restricting services to always use a given port enables firewalling to be done more effectively.

Configure mountd to use static portnfs_fixed_mountd_port CCE-RHEL7-CCE-TBD

Configure mountd to use static port

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Configure the mountd daemon to use a static port as opposed to letting the RPC Bind service dynamically assign a port. Edit the file /etc/sysconfig/nfs. Add or correct the following line:

MOUNTD_PORT=statd-port
Where mountd-port is a port which is not used by any other service on your network.

Rationale

Restricting services to always use a given port enables firewalling to be done more effectively.

Specify UID and GID for Anonymous NFS Connectionsnfs_no_anonymous CCE-RHEL7-CCE-TBD

Specify UID and GID for Anonymous NFS Connections

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

To specify the UID and GID for remote root users, edit the /etc/exports file and add the following for each export:

anonuid=value greater than UID_MAX from /etc/login.defs
anongid=value greater than GID_MAX from /etc/login.defs 
Alternatively, functionally equivalent values of 60001, 65534, 65535 may be used.

Rationale

Specifying the anonymous UID and GID ensures that the remote root user is mapped to a local account which has no permissions on the system.

Disable Network File System (nfs)service_nfs_disabled CCE-RHEL7-CCE-TBD

Disable Network File System (nfs)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  Test attestation on 20121025 by DS

Description

The Network File System (NFS) service allows remote hosts to mount and interact with shared filesystems on the local machine. If the local machine is not designated as a NFS server then this service should be disabled. The nfs service can be disabled with the following command:

$ sudo systemctl disable nfs

Rationale

Unnecessary services should be disabled to decrease the attack surface of the system.

Disable Secure RPC Server Service (rpcsvcgssd)service_rpcsvcgssd_disabled CCE-RHEL7-CCE-TBD

Disable Secure RPC Server Service (rpcsvcgssd)

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  Test attestation on 20121025 by DS

Description

The rpcsvcgssd service manages RPCSEC GSS contexts required to secure protocols that use RPC (most often Kerberos and NFS). The rpcsvcgssd service is the server-side of RPCSEC GSS. If the system does not require secure RPC then this service should be disabled. The rpcsvcgssd service can be disabled with the following command:

$ sudo systemctl disable rpcsvcgssd

Rationale

Unnecessary services should be disabled to decrease the attack surface of the system.

Mount Remote Filesystems with nodevuse_nodev_option_on_nfs_mounts CCE-RHEL7-CCE-TBD

Mount Remote Filesystems with nodev

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, MP-2, Test attestation on 20121025 by DS

Description

Add the nodev option to the fourth column of /etc/fstab for the line which controls mounting of any NFS mounts.

Rationale

Legitimate device files should only exist in the /dev directory. NFS mounts should not present device files to users.

Mount Remote Filesystems with nosuiduse_nosuid_option_on_nfs_mounts CCE-RHEL7-CCE-TBD

Mount Remote Filesystems with nosuid

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  Test attestation on 20121025 by DS

Description

Add the nosuid option to the fourth column of /etc/fstab for the line which controls mounting of any NFS mounts.

Rationale

NFS mounts should not present suid binaries to users. Only vendor-supplied suid executables should be installed to their default location on the local filesystem.

Use Root-Squashing on All Exportsuse_root_squashing_all_exports CCE-RHEL7-CCE-TBD

Use Root-Squashing on All Exports

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

If a filesystem is exported using root squashing, requests from root on the client are considered to be unprivileged (mapped to a user such as nobody). This provides some mild protection against remote abuse of an NFS server. Root squashing is enabled by default, and should not be disabled.

Ensure that no line in /etc/exports contains the option no_root_squash.

Rationale

If the NFS server allows root access to local file systems from remote hosts, this access could be used to compromise the system.

Restrict NFS Clients to Privileged Portsrestrict_nfs_clients_to_privileged_ports CCE-RHEL7-CCE-TBD

Restrict NFS Clients to Privileged Ports

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

By default, the server NFS implementation requires that all client requests be made from ports less than 1024. If your organization has control over machines connected to its network, and if NFS requests are prohibited at the border firewall, this offers some protection against malicious requests from unprivileged users. Therefore, the default should not be changed.

To ensure that the default has not been changed, ensure no line in /etc/exports contains the option insecure.

Rationale

Allowing client requests to be made from ports higher than 1024 could allow a unprivileged user to initiate an NFS connection. If the unprivileged user account has been compromised, an attacker could gain access to data on the NFS server.

Ensure Insecure File Locking is Not Allowedno_insecure_locks_exports CCE-RHEL7-CCE-TBD

Ensure Insecure File Locking is Not Allowed

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  764

Description

By default the NFS server requires secure file-lock requests, which require credentials from the client in order to lock a file. Most NFS clients send credentials with file lock requests, however, there are a few clients that do not send credentials when requesting a file-lock, allowing the client to only be able to lock world-readable files. To get around this, the insecure_locks option can be used so these clients can access the desired export. This poses a security risk by potentially allowing the client access to data for which it does not have authorization. Remove any instances of the insecure_locks option from the file /etc/exports.

Rationale

Allowing insecure file locking could allow for sensitive data to be viewed or edited by an unauthorized user.

Disable DNS Serverdisable_dns_server CCE-RHEL7-CCE-TBD

Disable DNS Server

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 366

Description

The named service can be disabled with the following command:

$ sudo systemctl disable named

Rationale

All network services involve some risk of compromise due to implementation flaws and should be disabled if possible.

Uninstall bind Packageuninstall_bind CCE-RHEL7-CCE-TBD

Uninstall bind Package

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 366

Description

To remove the bind package, which contains the named service, run the following command:

$ sudo yum erase bind

Rationale

If there is no need to make DNS server software available, removing it provides a safeguard against its activation.

Disable Zone Transfers from the Nameserverdns_server_disable_zone_transfers CCE-RHEL7-CCE-TBD

Disable Zone Transfers from the Nameserver

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Is it necessary for a secondary nameserver to receive zone data via zone transfer from the primary server? If not, follow the instructions in this section. If so, see the next section for instructions on protecting zone transfers. Add or correct the following directive within /etc/named.conf:

options {
  allow-transfer { none; };
  ...
}

Rationale

If both the primary and secondary nameserver are under your control, or if you have only one nameserver, it may be possible to use an external configuration management mechanism to distribute zone updates. In that case, it is not necessary to allow zone transfers within BIND itself, so they should be disabled to avoid the potential for abuse.

Authenticate Zone Transfersdns_server_authenticate_zone_transfers CCE-RHEL7-CCE-TBD

Authenticate Zone Transfers

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

If it is necessary for a secondary nameserver to receive zone data via zone transfer from the primary server, follow the instructions here. Use dnssec-keygen to create a symmetric key file in the current directory:

$ cd /tmp
$ sudo dnssec-keygen -a HMAC-MD5 -b 128 -n HOST dns.example.com
Kdns.example.com .+aaa +iiiii
This output is the name of a file containing the new key. Read the file to find the base64-encoded key string:
$ sudo cat Kdns.example.com .+NNN +MMMMM .key
dns.example.com IN KEY 512 3 157 base64-key-string
Add the directives to /etc/named.conf on the primary server:
key zone-transfer-key {
  algorithm hmac-md5;
  secret "base64-key-string ";
};
zone "example.com " IN {
  type master;
  allow-transfer { key zone-transfer-key; };
  ...
};
Add the directives below to /etc/named.conf on the secondary nameserver:
key zone-transfer-key {
  algorithm hmac-md5;
  secret "base64-key-string ";
};

server IP-OF-MASTER {
  keys { zone-transfer-key; };
};

zone "example.com " IN {
  type slave;
  masters { IP-OF-MASTER ; };
  ...
};

Rationale

The BIND transaction signature (TSIG) functionality allows primary and secondary nameservers to use a shared secret to verify authorization to perform zone transfers. This method is more secure than using IP-based limiting to restrict nameserver access, since IP addresses can be easily spoofed. However, if you cannot configure TSIG between your servers because, for instance, the secondary nameserver is not under your control and its administrators are unwilling to configure TSIG, you can configure an allow-transfer directive with numerical IP addresses or ACLs as a last resort.

Warnings
warning  The purpose of the dnssec-keygen command is to create the shared secret string base64-key-string. Once this secret has been obtained and inserted into named.conf on the primary and secondary servers, the key files Kdns.example.com .+NNN +MMMMM .key and Kdns.example.com .+NNN +MMMMM .private are no longer needed, and may safely be deleted.
Disable Dynamic Updatesdns_server_disable_dynamic_updates CCE-RHEL7-CCE-TBD

Disable Dynamic Updates

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Is there a mission-critical reason to enable the risky dynamic update functionality? If not, edit /etc/named.conf. For each zone specification, correct the following directive if necessary:

zone "example.com " IN {
  allow-update { none; };
  ...
};

Rationale

Dynamic updates allow remote servers to add, delete, or modify any entries in your zone file. Therefore, they should be considered highly risky, and disabled unless there is a very good reason for their use. If dynamic updates must be allowed, IP-based ACLs are insufficient protection, since they are easily spoofed. Instead, use TSIG keys (see the previous section for an example), and consider using the update-policy directive to restrict changes to only the precise type of change needed.

Disable vsftpd Servicedisable_vsftpd CCE-RHEL7-CCE-TBD

Disable vsftpd Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 1436

Description

The vsftpd service can be disabled with the following command:

$ sudo systemctl disable vsftpd

Rationale

Running FTP server software provides a network-based avenue of attack, and should be disabled if not needed. Furthermore, the FTP protocol is unencrypted and creates a risk of compromising sensitive information.

Uninstall vsftpd Packageuninstall_vsftpd CCE-RHEL7-CCE-TBD

Uninstall vsftpd Package

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, 1436

Description

The vsftpd package can be removed with the following command:

$ sudo yum erase vsftpd

Rationale

Removing the vsftpd package decreases the risk of its accidental activation.

Install vsftpd Packagepackage_vsftpd_installed CCE-RHEL7-CCE-TBD

Install vsftpd Package

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

If this machine must operate as an FTP server, install the vsftpd package via the standard channels.

$ sudo yum install vsftpd

Rationale

After RHEL 2.1, Red Hat switched from distributing wu-ftpd with RHEL to distributing vsftpd. For security and for consistency with future Red Hat releases, the use of vsftpd is recommended.

Restrict Access to Anonymous Users if Possibleftp_restrict_to_anon CCE-RHEL7-CCE-TBD

Restrict Access to Anonymous Users if Possible

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7, AC-3

Description

Is there a mission-critical reason for users to transfer files to/from their own accounts using FTP, rather than using a secure protocol like SCP/SFTP? If not, edit the vsftpd configuration file. Add or correct the following configuration option:

local_enable=NO
If non-anonymous FTP logins are necessary, follow the guidance in the remainder of this section to secure these logins as much as possible.

Rationale

The use of non-anonymous FTP logins is strongly discouraged. Since SSH clients and servers are widely available, and since SSH provides support for a transfer mode which resembles FTP in user interface, there is no good reason to allow password-based FTP access.

Enable Logging of All FTP Transactionsftp_log_transactions CCE-RHEL7-CCE-TBD

Enable Logging of All FTP Transactions

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Add or correct the following configuration options within the vsftpd configuration file, located at /etc/vsftpd/vsftpd.conf:

xferlog_enable=YES
xferlog_std_format=NO
log_ftp_protocol=YES

Rationale

To trace malicious activity facilitated by the FTP service, it must be configured to ensure that all commands sent to the FTP server are logged using the verbose vsftpd log format. The default vsftpd log file is /var/log/vsftpd.log.

Warnings
warning  If verbose logging to vsftpd.log is done, sparse logging of downloads to /var/log/xferlog will not also occur. However, the information about what files were downloaded is included in the information logged to vsftpd.log
Create Warning Banners for All FTP Usersftp_present_banner CCE-RHEL7-CCE-TBD

Create Warning Banners for All FTP Users

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  48

Description

Edit the vsftpd configuration file, which resides at /etc/vsftpd/vsftpd.conf by default. Add or correct the following configuration options:

banner_file=/etc/issue

Rationale

This setting will cause the system greeting banner to be used for FTP connections as well.

Disable FTP Uploads if Possibleftp_disable_uploads CCE-RHEL7-CCE-TBD

Disable FTP Uploads if Possible

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Is there a mission-critical reason for users to upload files via FTP? If not, edit the vsftpd configuration file to add or correct the following configuration options:

write_enable=NO
If FTP uploads are necessary, follow the guidance in the remainder of this section to secure these transactions as much as possible.

Rationale

Anonymous FTP can be a convenient way to make files available for universal download. However, it is less common to have a need to allow unauthenticated users to place files on the FTP server. If this must be done, it is necessary to ensure that files cannot be uploaded and downloaded from the same directory.

Place the FTP Home Directory on its Own Partitionftp_home_partition CCE-RHEL7-CCE-TBD

Place the FTP Home Directory on its Own Partition

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

By default, the anonymous FTP root is the home directory of the FTP user account. The df command can be used to verify that this directory is on its own partition.

Rationale

If there is a mission-critical reason for anonymous users to upload files, precautions must be taken to prevent these users from filling a disk used by other services.

Disable httpd Servicedisable_httpd CCE-RHEL7-CCE-TBD

Disable httpd Service

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

The httpd service can be disabled with the following command:

$ sudo systemctl disable httpd

Rationale

Running web server software provides a network-based avenue of attack, and should be disabled if not needed.

Uninstall httpd Packagepackage_httpd_removed CCE-RHEL7-CCE-TBD

Uninstall httpd Package

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

The httpd package can be removed with the following command:

$ sudo yum erase httpd

Rationale

If there is no need to make the web server software available, removing it provides a safeguard against its activation.

Set httpd ServerTokens Directive to Prodhttpd_servertokens_prod CCE-RHEL7-CCE-TBD

Set httpd ServerTokens Directive to Prod

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

ServerTokens Prod restricts information in page headers, returning only the word "Apache."

Add or correct the following directive in /etc/httpd/conf/httpd.conf:

ServerTokens Prod

Rationale

Information disclosed to clients about the configuration of the web server and system could be used to plan an attack on the given system. This information disclosure should be restricted to a minimum.

Set httpd ServerSignature Directive to Offhttpd_serversignature_off CCE-RHEL7-CCE-TBD

Set httpd ServerSignature Directive to Off

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

ServerSignature Off restricts httpd from displaying server version number on error pages.

Add or correct the following directive in /etc/httpd/conf/httpd.conf:

ServerSignature Off

Rationale

Information disclosed to clients about the configuration of the web server and system could be used to plan an attack on the given system. This information disclosure should be restricted to a minimum.

Disable HTTP Digest Authenticationhttpd_digest_authentication CCE-RHEL7-CCE-TBD

Disable HTTP Digest Authentication

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The auth_digest module provides encrypted authentication sessions. If this functionality is unnecessary, comment out the related module:

#LoadModule auth_digest_module modules/mod_auth_digest.so

Rationale

Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server.

Disable HTTP mod_rewritehttpd_mod_rewrite CCE-RHEL7-CCE-TBD

Disable HTTP mod_rewrite

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The mod_rewrite module is very powerful and can protect against certain classes of web attacks. However, it is also very complex and has a significant history of vulnerabilities itself. If its functionality is unnecessary, comment out the related module:

#LoadModule rewrite_module modules/mod_rewrite.so

Rationale

Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server.

Disable LDAP Supporthttpd_ldap_support CCE-RHEL7-CCE-TBD

Disable LDAP Support

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The ldap module provides HTTP authentication via an LDAP directory. If its functionality is unnecessary, comment out the related modules:

#LoadModule ldap_module modules/mod_ldap.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
If LDAP is to be used, SSL encryption should be used as well.

Rationale

Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server.

Disable Server Side Includeshttpd_server_side_includes CCE-RHEL7-CCE-TBD

Disable Server Side Includes

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Server Side Includes provide a method of dynamically generating web pages through the insertion of server-side code. However, the technology is also deprecated and introduces significant security concerns. If this functionality is unnecessary, comment out the related module:

#LoadModule include_module modules/mod_include.so
If there is a critical need for Server Side Includes, they should be enabled with the option IncludesNoExec to prevent arbitrary code execution. Additionally, user supplied data should be encoded to prevent cross-site scripting vulnerabilities.

Rationale

Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server.

Disable MIME Magichttpd_mime_magic CCE-RHEL7-CCE-TBD

Disable MIME Magic

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The mime_magic module provides a second layer of MIME support that in most configurations is likely extraneous. If its functionality is unnecessary, comment out the related module:

#LoadModule mime_magic_module modules/mod_mime_magic.so

Rationale

Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server.

Disable WebDAV (Distributed Authoring and Versioning)httpd_webdav CCE-RHEL7-CCE-TBD

Disable WebDAV (Distributed Authoring and Versioning)

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

WebDAV is an extension of the HTTP protocol that provides distributed and collaborative access to web content. If its functionality is unnecessary, comment out the related modules:

#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
If there is a critical need for WebDAV, extra care should be taken in its configuration. Since DAV access allows remote clients to manipulate server files, any location on the server that is DAV enabled should be protected by access controls.

Rationale

Minimizing the number of loadable modules available to the web server, reduces risk by limiting the capabilities allowed by the web server.

Disable Server Activity Statushttpd_server_activity_status CCE-RHEL7-CCE-TBD

Disable Server Activity Status

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The status module provides real-time access to statistics on the internal operation of the web server. This may constitute an unnecessary information leak and should be disabled unless necessary. To do so, comment out the related module:

#LoadModule status_module modules/mod_status.so
If there is a critical need for this module, ensure that access to the status page is properly restricted to a limited set of hosts in the status handler configuration.

Rationale

Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server.

Disable Web Server Configuration Displayhttpd_server_configuration_display CCE-RHEL7-CCE-TBD

Disable Web Server Configuration Display

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The info module creates a web page illustrating the configuration of the web server. This can create an unnecessary security leak and should be disabled. If its functionality is unnecessary, comment out the module:

#LoadModule info_module modules/mod_info.so
If there is a critical need for this module, use the Location directive to provide an access control list to restrict access to the information.

Rationale

Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server.

Disable URL Correction on Misspelled Entrieshttpd_url_correction CCE-RHEL7-CCE-TBD

Disable URL Correction on Misspelled Entries

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The speling module attempts to find a document match by allowing one misspelling in an otherwise failed request. If this functionality is unnecessary, comment out the module:

#LoadModule speling_module modules/mod_speling.so
This functionality weakens server security by making site enumeration easier.

Rationale

Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server.

Disable Proxy Supporthttpd_proxy_support CCE-RHEL7-CCE-TBD

Disable Proxy Support

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The proxy module provides proxying support, allowing httpd to forward requests and serve as a gateway for other servers. If its functionality is unnecessary, comment out the module:

#LoadModule proxy_module modules/mod_proxy.so
If proxy support is needed, load mod_proxy and the appropriate proxy protocol handler module (one of mod_proxy_http, mod_proxy_ftp, or mod_proxy_connect). Additionally, make certain that a server is secure before enabling proxying, as open proxy servers are a security risk. mod_proxy_balancer enables load balancing, but requires that mod status be enabled.

Rationale

Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server.

Disable Cache Supporthttpd_cache_support CCE-RHEL7-CCE-TBD

Disable Cache Support

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The cache module allows httpd to cache data, optimizing access to frequently accessed content. However, it introduces potential security flaws such as the possibility of circumventing Allow and Deny directives.

If this functionality is unnecessary, comment out the module:

#LoadModule cache_module modules/mod_cache.so
If caching is required, it should not be enabled for any limited-access content.

Rationale

Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server.

Disable CGI Supporthttpd_cgi_support CCE-RHEL7-CCE-TBD

Disable CGI Support

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The cgi module allows HTML to interact with the CGI web programming language.

If this functionality is unnecessary, comment out the module:

#LoadModule cgi_module modules/mod_cgi.so
If the web server requires the use of CGI, enable mod_cgi.

Rationale

Minimizing the number of loadable modules available to the web server reduces risk by limiting the capabilities allowed by the web server.

Restrict Root Directoryhttpd_restrict_root_directory CCE-RHEL7-CCE-TBD

Restrict Root Directory

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The httpd root directory should always have the most restrictive configuration enabled.

<Directory / >
   Options None
   AllowOverride None
   Order allow,deny
</Directory>

Rationale

The Web Server's root directory content should be protected from unauthorized access by web clients.

Restrict Web Directoryhttpd_restrict_web_directory CCE-RHEL7-CCE-TBD

Restrict Web Directory

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The default configuration for the web (/var/www/html) Directory allows directory indexing (Indexes) and the following of symbolic links (FollowSymLinks). Neither of these is recommended.

The /var/www/html directory hierarchy should not be viewable via the web, and symlinks should only be followed if the owner of the symlink also owns the linked file.

Ensure that this policy is adhered to by altering the related section of the configuration:

<Directory "/var/www/html">
#  ...
   Options SymLinksIfOwnerMatch
#  ...
</Directory>

Rationale

Access to the web server's directory hierarchy could allow access to unauthorized files by web clients. Following symbolic links could also allow such access.

Restrict Other Critical Directorieshttpd_restrict_critical_directories CCE-RHEL7-CCE-TBD

Restrict Other Critical Directories

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

All accessible web directories should be configured with similarly restrictive settings. The Options directive should be limited to necessary functionality and the AllowOverride directive should be used only if needed. The Order and Deny access control tags should be used to deny access by default, allowing access only where necessary.

Rationale

Directories accessible from a web client should be configured with the least amount of access possible in order to avoid unauthorized access to restricted content or server information.

Limit Available Methodshttpd_limit_available_methods CCE-RHEL7-CCE-TBD

Limit Available Methods

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Web server methods are defined in section 9 of RFC 2616 (http://www.ietf.org/rfc/rfc2616.txt). If a web server does not require the implementation of all available methods, they should be disabled.

Note: GET and POST are the most common methods. A majority of the others are limited to the WebDAV protocol.

<Directory /var/www/html>
# ...
   # Only allow specific methods (this command is case-sensitive!)
   <LimitExcept GET POST>
      Order allow,deny
   </LimitExcept>
# ...
</Directory>

Rationale

Minimizing the number of available methods to the web client reduces risk by limiting the capabilities allowed by the web server.

Install mod_sslhttpd_install_mod_ssl CCE-RHEL7-CCE-TBD

Install mod_ssl

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Install the mod_ssl module:

$ sudo yum install mod_ssl

Rationale

mod_ssl provides encryption capabilities for the httpd Web server. Unencrypted content is transmitted in plain text which could be passively monitored and accessed by unauthorized parties.

Install mod_securityhttpd_install_mod_security CCE-RHEL7-CCE-TBD

Install mod_security

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Install the security module:

$ sudo yum install mod_security

Rationale

mod_security provides an additional level of protection for the web server by enabling the administrator to implement content access policies and filters at the application layer.

Set Permissions on the /var/log/httpd/ Directoryhttpd_logs_permissions CCE-RHEL7-CCE-TBD

Set Permissions on the /var/log/httpd/ Directory

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

Ensure that the permissions on the web server log directory is set to 700:

$ sudo chmod 700 /var/log/httpd/
This is its default setting.

Rationale

Access to the web server's log files may allow an unauthorized user or attacker to access information about the web server or alter the server's log files.

Set Permissions on the /etc/httpd/conf/ Directoryhttpd_conf_dir_permissions CCE-RHEL7-CCE-TBD

Set Permissions on the /etc/httpd/conf/ Directory

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Set permissions on the web server configuration directory to 750:

$ sudo chmod 750 /etc/httpd/conf/

Rationale

Access to the web server's configuration files may allow an unauthorized user or attacker to access information about the web server or alter the server's configuration files.

Set Permissions on All Configuration Files Inside /etc/httpd/conf/httpd_conf_files_permissions CCE-RHEL7-CCE-TBD

Set Permissions on All Configuration Files Inside /etc/httpd/conf/

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  CM-7

Description

Set permissions on the web server configuration files to 640:

$ sudo chmod 640 /etc/httpd/conf/*

Rationale

Access to the web server's configuration files may allow an unauthorized user or attacker to access information about the web server or to alter the server's configuration files.

Disable Dovecot Servicedisable_dovecot CCE-RHEL7-CCE-TBD

Disable Dovecot Service

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The dovecot service can be disabled with the following command:

$ sudo systemctl disable dovecot

Rationale

Running an IMAP or POP3 server provides a network-based avenue of attack, and should be disabled if not needed.

Uninstall dovecot Packagepackage_dovecot_removed CCE-RHEL7-CCE-TBD

Uninstall dovecot Package

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The dovecot package can be uninstalled with the following command:

$ sudo yum erase dovecot

Rationale

If there is no need to make the Dovecot software available, removing it provides a safeguard against its activation.

Enable the SSL flag in /etc/dovecot.confdovecot_enable_ssl CCE-RHEL7-CCE-TBD

Enable the SSL flag in /etc/dovecot.conf

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

To allow clients to make encrypted connections the ssl flag in Dovecot's configuration file needs to be set to yes.

Edit /etc/dovecot/conf.d/10-ssl.conf and add or correct the following line:

ssl = yes

Rationale

SSL encrypt network traffic between the Dovecot server and its clients protecting user credentials, mail as it is downloaded, and clients may use SSL certificates to authenticate the server, preventing another system from impersonating the server.

Configure Dovecot to Use the SSL Certificate filedovecot_configure_ssl_cert CCE-RHEL7-CCE-TBD

Configure Dovecot to Use the SSL Certificate file

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

This option tells Dovecot where to find the the mail server's SSL Certificate.

Edit /etc/dovecot/conf.d/10-ssl.conf and add or correct the following line (note: the path below is the default path set by the Dovecot installation. If you are using a different path, ensure you reference the appropriate file):

ssl_cert = </etc/pki/dovecot/certs/dovecot.pem

Rationale

SSL certificates are used by the client to authenticate the identity of the server, as well as to encrypt credentials and message traffic. Not using SSL to encrypt mail server traffic could allow unauthorized access to credentials and mail messages since they are sent in plain text over the network.

Configure Dovecot to Use the SSL Key filedovecot_configure_ssl_key CCE-RHEL7-CCE-TBD

Configure Dovecot to Use the SSL Key file

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

This option tells Dovecot where to find the the mail server's SSL Key.

Edit /etc/dovecot/conf.d/10-ssl.conf and add or correct the following line (note: the path below is the default path set by the Dovecot installation. If you are using a different path, ensure you reference the appropriate file):

ssl_key = </etc/pki/dovecot/private/dovecot.pem

Rationale

SSL certificates are used by the client to authenticate the identity of the server, as well as to encrypt credentials and message traffic. Not using SSL to encrypt mail server traffic could allow unauthorized access to credentials and mail messages since they are sent in plain text over the network.

Disable Plaintext Authenticationdovecot_disable_plaintext_auth CCE-RHEL7-CCE-TBD

Disable Plaintext Authentication

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

To prevent Dovecot from attempting plaintext authentication of clients, edit /etc/dovecot/conf.d/10-auth.conf and add or correct the following line:

disable_plaintext_auth = yes

Rationale

Using plain text authentication to the mail server could allow an attacker access to credentials by monitoring network traffic.

Disable Sambadisable_smb_server CCE-RHEL7-CCE-TBD

Disable Samba

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  1436

Description

The smb service can be disabled with the following command:

$ sudo systemctl disable smb

Rationale

Running a Samba server provides a network-based avenue of attack, and should be disabled if not needed.

Disable Root Access to SMB Sharessmb_server_disable_root CCE-RHEL7-CCE-TBD

Disable Root Access to SMB Shares

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Administrators should not use administrator accounts to access Samba file and printer shares. Disable the root user and the wheel administrator group:

[share]
  invalid users = root @wheel
If administrator accounts cannot be disabled, ensure that local machine passwords and Samba service passwords do not match.

Rationale

Typically, administrator access is required when Samba must create user and machine accounts and shares. Domain member servers and standalone servers may not need administrator access at all. If that is the case, add the invalid users parameter to [global] instead.

Require Client SMB Packet Signing, if using smbclientrequire_smb_client_signing CCE-RHEL7-CCE-TBD

Require Client SMB Packet Signing, if using smbclient

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

To require samba clients running smbclient to use packet signing, add the following to the [global] section of the Samba configuration file, /etc/samba/smb.conf:

client signing = mandatory
Requiring samba clients such as smbclient to use packet signing ensures they can only communicate with servers that support packet signing.

Rationale

Packet signing can prevent man-in-the-middle attacks which modify SMB packets in transit.

Require Client SMB Packet Signing, if using mount.cifsrequire_smb_client_signing_mount.cifs CCE-RHEL7-CCE-TBD

Require Client SMB Packet Signing, if using mount.cifs

Rule IDrequire_smb_client_signing_mount.cifs
Result
notselected
Time2015-07-17T10:50:20
Severitylow
Identifiers and References

identifiers:  CCE-RHEL7-CCE-TBD

Description

Require packet signing of clients who mount Samba shares using the mount.cifs program (e.g., those who specify shares in /etc/fstab). To do so, ensure signing options (either sec=krb5i or sec=ntlmv2i) are used.

See the mount.cifs(8) man page for more information. A Samba client should only communicate with servers who can support SMB packet signing.

Rationale

Packet signing can prevent man-in-the-middle attacks which modify SMB packets in transit.

Disable Squiddisable_squid CCE-RHEL7-CCE-TBD

Disable Squid

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The squid service can be disabled with the following command:

$ sudo systemctl disable squid

Rationale

Running proxy server software provides a network-based avenue of attack, and should be removed if not needed.

Uninstall squid Packageuninstall_squid CCE-RHEL7-CCE-TBD

Uninstall squid Package

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The squid package can be removed with the following command:

$ sudo yum erase squid

Rationale

If there is no need to make the proxy server software available, removing it provides a safeguard against its activation.

Disable snmpd Servicedisable_snmpd CCE-RHEL7-CCE-TBD

Disable snmpd Service

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The snmpd service can be disabled with the following command:

$ sudo systemctl disable snmpd

Rationale

Running SNMP software provides a network-based avenue of attack, and should be disabled if not needed.

Uninstall net-snmp Packagepackage_net-snmp_removed CCE-RHEL7-CCE-TBD

Uninstall net-snmp Package

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

The net-snmp package provides the snmpd service. The net-snmp package can be removed with the following command:

$ sudo yum erase net-snmp

Rationale

If there is no need to run SNMP server software, removing the package provides a safeguard against its activation.

Configure SNMP Service to Use Only SNMPv3 or Newer snmpd_use_newer_protocol CCE-RHEL7-CCE-TBD

Configure SNMP Service to Use Only SNMPv3 or Newer

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

identifiers:  CCE-RHEL7-CCE-TBD

Description

Edit /etc/snmp/snmpd.conf, removing any references to rocommunity, rwcommunity, or com2sec. Upon doing that, restart the SNMP service:

$ sudo service snmpd restart

Rationale

Earlier versions of SNMP are considered insecure, as they potentially allow unauthorized access to detailed system management information.

Ensure Default Password Is Not Usedsnmpd_not_default_password CCE-RHEL7-CCE-TBD

Ensure Default Password Is Not Used

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

identifiers:  CCE-RHEL7-CCE-TBD

references:  Test attestation on 20121214 by MAN

Description

Edit /etc/snmp/snmpd.conf, remove default community string public. Upon doing that, restart the SNMP service:

$ sudo service snmpd restart

Rationale

Presence of the default SNMP password enables querying of different system aspects and could result in unauthorized knowledge of the system.

Product Meets this Requirementmet_inherently_generic

Product Meets this Requirement

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

references:  42, 56, 206, 1084, 66, 85, 86, 185, 223, 171, 172, 1694, 770, 804, 162, 163, 164, 345, 346, 1096, 1111, 1291, 386, 156, 186, 1083, 1082, 1090, 804, 1127, 1128, 1129, 1248, 1265, 1314, 1362, 1368, 1310, 1311, 1328, 1399, 1400, 1404, 1405, 1427, 1499, 1632, 1693, 1665, 1674

Description

This requirement is a permanent not a finding. No fix is required.

Rationale

Red Hat Enterprise Linux meets this requirement through design and implementation.

Product Meets this Requirementmet_inherently_auditing

Product Meets this Requirement

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

references:  130, 157, 131, 132, 133, 134, 135, 159, 174

Description

This requirement is a permanent not a finding. No fix is required.

Rationale

The Red Hat Enterprise Linux audit system meets this requirement through design and implementation.

Product Meets this Requirementmet_inherently_nonselected

Product Meets this Requirement

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

references:  34, 35, 99, 154, 226, 802, 872, 1086, 1087, 1089, 1091, 1424, 1426, 1428, 1209, 1214, 1237, 1269, 1338, 1425, 1670

Description

This requirement is a permanent not a finding. No fix is required.

Rationale

Red Hat Enterprise Linux meets this requirement through design and implementation.

Guidance Does Not Meet this Requirement Due to Impracticality or Scopeunmet_nonfinding_nonselected_scope

Guidance Does Not Meet this Requirement Due to Impracticality or Scope

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

references:  21, 25, 28, 29, 30, 165, 221, 354, 553, 779, 780, 781, 1009, 1094, 1123, 1124, 1125, 1132, 1135, 1140, 1141, 1142, 1143, 1145, 1147, 1148, 1166, 1339, 1340, 1341, 1350, 1356, 1373, 1374, 1383, 1391, 1392, 1395, 1662

Description

This requirement is NA. No fix is required.

Rationale

The guidance does not meet this requirement. The requirement is impractical or out of scope.

Implementation of the Requirement is Not Supportedunmet_finding_nonselected

Implementation of the Requirement is Not Supported

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

references:  20, 31, 52, 144, 1158, 1294, 1295, 1500

Description

This requirement is a permanent finding and cannot be fixed. An appropriate mitigation for the system must be implemented but this finding cannot be considered fixed.

Rationale

RHEL7 does not support this requirement.

Guidance Does Not Meet this Requirement Due to Impracticality or Scopeunmet_nonfinding_scope

Guidance Does Not Meet this Requirement Due to Impracticality or Scope

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

references:  15, 27, 218, 219, 371, 372, 535, 537, 539, 1682, 370, 37, 24, 1112, 1126, 1143, 1149, 1157, 1159, 1210, 1211, 1274, 1372, 1376, 1377, 1352, 1401, 1555, 1556, 1150

Description

This requirement is NA. No fix is required.

Rationale

The guidance does not meet this requirement. The requirement is impractical or out of scope.

A process for prompt installation of OS updates must exist.update_process

A process for prompt installation of OS updates must exist.

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

references:  1232

Description

Procedures to promptly apply software updates must be established and executed. The Red Hat operating system provides support for automating such a process, by running the yum program through a cron job or by managing the system and its packages through the Red Hat Network or a Satellite Server.

Rationale

This is a manual inquiry about update procedure.

Red Hat and Red Hat Enterprise Linux are either registered trademarks or trademarks of Red Hat, Inc. in the United States and other countries. All other names are registered trademarks or trademarks of their respective companies.