Guide to the Secure Configuration of Red Hat Enterprise Linux 6
with profile Red Hat Corporate Profile for Certified Cloud Providers (RH CCP)
scap-security-guide
package which is developed at
http://fedorahosted.org/scap-security-guide.
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 any operational scenario. 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 6, which provides required settings for US Department of Defense systems, is one example of a baseline created from this guidance.
Profile Title | Red Hat Corporate Profile for Certified Cloud Providers (RH CCP) |
---|---|
Profile ID | xccdf_org.ssgproject.content_profile_rht-ccp |
Revision History
Current version: 0.9
- draft (as of 2015-07-30)
Platforms
- cpe:/o:redhat:enterprise_linux:6
- cpe:/o:redhat:enterprise_linux:6::client
Table of Contents
- System Settings
- Installing and Maintaining Software
- File Permissions and Masks
- SELinux
- Account and Access Control
- Network Configuration and Firewalls
- System Accounting with auditd
- Services
Checklist
contains 94 rules |
System Settingsgroup |
contains 65 rules |
Installing and Maintaining SoftwaregroupThe following sections contain information on security-relevant choices during the initial operating system installation process and the setup of software updates. |
contains 9 rules |
Disk PartitioninggroupTo ensure separation and protection of data, there
are top-level system directories which should be placed on their
own physical partition or logical volume. The installer's default
partitioning scheme creates separate logical volumes for
|
contains 4 rules |
Ensure /tmp Located On Separate Partitionrule
The
The identifiers: CCE-26435-8, DISA FSO RHEL-06-000001 references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, 1208, Test attestation on 20120928 by MM |
Ensure /var Located On Separate PartitionruleThe
Ensuring that identifiers: CCE-26639-5, DISA FSO RHEL-06-000002 references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, 1208, Test attestation on 20120928 by MM |
Ensure /var/log Located On Separate Partitionrule
System logs are stored in the
Placing identifiers: CCE-26215-4, DISA FSO RHEL-06-000003 references: AU-9, 1208, Test attestation on 20120928 by MM |
Ensure /var/log/audit Located On Separate Partitionrule
Audit logs are stored in the
Placing identifiers: CCE-26436-6, DISA FSO RHEL-06-000004 references: AU-4, AU-9, 137, 138, 1208, Test attestation on 20120928 by MM |
Updating SoftwaregroupThe |
contains 4 rules |
Ensure Red Hat GPG Key InstalledruleTo ensure the system can cryptographically verify base software packages come from Red Hat (and to connect to the Red Hat Network to receive them), the Red Hat GPG key must properly be installed. To install the Red Hat GPG key, run: $ sudo rhn_registerIf the system is not connected to the Internet or an RHN Satellite, then install the Red Hat GPG key from trusted media such as the Red Hat installation CD-ROM or DVD. Assuming the disc is mounted in /media/cdrom , use the following command as the root user to import
it into the keyring:
$ sudo rpm --import /media/cdrom/RPM-GPG-KEYRationale: The Red Hat GPG key is necessary to cryptographically verify packages are from Red Hat. identifiers: CCE-26506-6, DISA FSO RHEL-06-000008 references: SI-7, MA-1(b), 351, Test attestation on 20120928 by MM Remediation script:
|
Ensure gpgcheck Enabled In Main Yum ConfigurationruleThe gpgcheck=1Rationale: Ensuring the validity of packages' cryptographic signatures prior to installation ensures the authenticity of the software and protects against malicious tampering. identifiers: CCE-26709-6, DISA FSO RHEL-06-000013 references: SI-7, MA-1(b), 352, 663, Test attestation on 20120928 by MM |
Ensure gpgcheck Enabled For All Yum Package RepositoriesruleTo ensure signature checking is not disabled for
any repos, remove any lines from files in gpgcheck=0Rationale: Ensuring all packages' cryptographic signatures are valid prior to installation ensures the authenticity of the software and protects against malicious tampering. identifiers: CCE-26647-8, DISA FSO RHEL-06-000015 references: SI-7, MA-1(b), 352, 663, Test attestation on 20120928 by MM |
Ensure Software Patches InstalledruleIf the system is joined to the Red Hat Network, a Red Hat Satellite Server, or a yum server, run the following command to install updates: $ sudo yum updateIf the system is not configured to use one of these sources, updates (in the form of RPM packages) can be manually downloaded from the Red Hat Network and installed using rpm .
Rationale:Installing software updates is a fundamental mitigation against the exploitation of publicly-known vulnerabilities. identifiers: CCE-27635-2, DISA FSO RHEL-06-000011 references: SI-2, MA-1(b), 1227, 1233, Test attestation on 20120928 by MM |
Software Integrity Checkinggroup
Both the AIDE (Advanced Intrusion Detection Environment)
software and the RPM package management system provide
mechanisms for verifying the integrity of installed software.
AIDE uses snapshots of file metadata (such as hashes) and compares these
to current system files in order to detect changes.
The RPM package management system can conduct integrity
checks by comparing information in its metadata database with
files installed on the system.
|
contains 1 rule |
Verify Integrity with AIDEgroupAIDE conducts integrity checks by comparing information about
files with previously-gathered information. Ideally, the AIDE database is
created immediately after initial system configuration, and then again after any
software update. AIDE is highly configurable, with further configuration
information located in |
contains 1 rule |
Install AIDEruleInstall the AIDE package with the command: $ sudo yum install aideRationale: The AIDE package must be installed if it is to be available for integrity checking. identifiers: CCE-27024-9, DISA FSO RHEL-06-000016 references: CM-3(d), CM-3(e), CM-6(d), SC-28, SI-7, 1069, Test attestation on 20121024 by DS Remediation script:
|
File Permissions and MasksgroupTraditional Unix security relies heavily on file and
directory permissions to prevent unauthorized users from reading or
modifying files to which they should not have access.
$ mount -t ext4 | awk '{print $3}'For any systems that use a different local filesystem type, modify this command as appropriate. |
contains 19 rules |
Restrict Dynamic Mounting and Unmounting of FilesystemsgroupLinux includes a number of facilities for the automated addition
and removal of filesystems on a running system. These facilities may be
necessary in many environments, but this capability also carries some risk -- whether direct
risk from allowing users to introduce arbitrary filesystems,
or risk that software flaws in the automated mount facility itself could
allow an attacker to compromise the system.
$ find /lib/modules/`uname -r`/kernel/fs -type f -name '*.ko'If these filesystems are not required then they can be explicitly disabled in a configuratio file in /etc/modprobe.d .
|
contains 1 rule |
Disable the AutomounterruleThe $ sudo chkconfig autofs offRationale: Disabling the automounter permits the administrator to
statically control filesystem mounting through identifiers: CCE-26976-1, DISA FSO RHEL-06-000526 references: AC-19(a), AC-19(d), AC-19(e), 1250, 85 Remediation script:
|
Verify Permissions on Important Files and DirectoriesgroupPermissions for many files on a system must be set restrictively to ensure sensitive information is properly protected. This section discusses important permission restrictions which can be verified to ensure that no harmful discrepancies have arisen. |
contains 16 rules |
Verify Permissions on Files with Local Account Information and CredentialsgroupThe default restrictive permissions for files which act as
important security databases such as |
contains 12 rules |
Verify User Who Owns shadow Filerule
To properly set the owner of $ sudo chown root /etc/shadowRationale: The identifiers: CCE-26947-2, DISA FSO RHEL-06-000033 references: AC-6, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify Group Who Owns shadow Filerule
To properly set the group owner of $ sudo chgrp root /etc/shadowRationale: The identifiers: CCE-26967-0, DISA FSO RHEL-06-000034 references: AC-6, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify Permissions on shadow Filerule
To properly set the permissions of $ sudo chmod 0000 /etc/shadowRationale: The identifiers: CCE-26992-8, DISA FSO RHEL-06-000035 references: AC-6, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify User Who Owns group Filerule
To properly set the owner of $ sudo chown root /etc/groupRationale: The identifiers: CCE-26822-7, DISA FSO RHEL-06-000042 references: AC-6, Test attestation on 20121026 by DS Remediation script:
|
Verify Group Who Owns group Filerule
To properly set the group owner of $ sudo chgrp root /etc/groupRationale: The identifiers: CCE-26930-8, DISA FSO RHEL-06-000043 references: AC-6, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify Permissions on group Filerule
To properly set the permissions of $ sudo chmod 644 /etc/groupRationale: The identifiers: CCE-26954-8, DISA FSO RHEL-06-000044 references: AC-6, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify User Who Owns gshadow Filerule
To properly set the owner of $ sudo chown root /etc/gshadowRationale: The identifiers: CCE-27026-4, DISA FSO RHEL-06-000036 references: AC-6, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify Group Who Owns gshadow Filerule
To properly set the group owner of $ sudo chgrp root /etc/gshadowRationale: The identifiers: CCE-26975-3, DISA FSO RHEL-06-000037 references: AC-6, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify Permissions on gshadow Filerule
To properly set the permissions of $ sudo chmod 0000 /etc/gshadowRationale: The identifiers: CCE-26951-4, DISA FSO RHEL-06-000038 references: AC-6, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify User Who Owns passwd Filerule
To properly set the owner of $ sudo chown root /etc/passwdRationale: The identifiers: CCE-26953-0, DISA FSO RHEL-06-000039 references: AC-6, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify Group Who Owns passwd Filerule
To properly set the group owner of $ sudo chgrp root /etc/passwdRationale: The identifiers: CCE-26856-5, DISA FSO RHEL-06-000040 references: AC-6, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify Permissions on passwd Filerule
To properly set the permissions of $ sudo chmod 0644 /etc/passwdRationale: If the identifiers: CCE-26868-0, DISA FSO RHEL-06-000041 references: AC-6, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify File Permissions Within Some Important DirectoriesgroupSome directories contain files whose confidentiality or integrity is notably important and may also be susceptible to misconfiguration over time, particularly if unpackaged software is installed. As such, an argument exists to verify that files' permissions within these directories remain configured correctly and restrictively. |
contains 4 rules |
Verify that Shared Library Files Have Restrictive PermissionsruleSystem-wide shared library files, which are linked to executables during process load time or run time, are stored in the following directories by default: /lib /lib64 /usr/lib /usr/lib64Kernel modules, which can be added to the kernel during runtime, are 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 FILERationale: 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. identifiers: CCE-27381-3, DISA FSO RHEL-06-000045 references: AC-6, 1499, Test attestation on 20121026 by DS Remediation script:
|
Verify that Shared Library Files Have Root OwnershipruleSystem-wide shared library files, which are linked to executables during process load time or run time, are stored in the following directories by default: /lib /lib64 /usr/lib /usr/lib64Kernel modules, which can be added to the kernel during runtime, are also stored in /lib/modules . All files in these directories should be
owned by the root user. If the directory, or any file in these
directories, is found to be owned by a user other than root correct its
ownership with the following command:
$ sudo chown root FILERationale: 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. identifiers: CCE-27424-1, DISA FSO RHEL-06-000046 references: AC-6, 1499, Test attestation on 20130914 by swells Remediation script:
|
Verify that System Executables Have Restrictive PermissionsruleSystem executables are stored in the following directories by default: /bin /usr/bin /usr/local/bin /sbin /usr/sbin /usr/local/sbinAll files in these directories should 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 FILERationale: 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. identifiers: CCE-27289-8, DISA FSO RHEL-06-000047 Remediation script:
|
Verify that System Executables Have Root OwnershipruleSystem executables are stored in the following directories by default: /bin /usr/bin /usr/local/bin /sbin /usr/sbin /usr/local/sbinAll files in these directories should be owned by the root user.
If any file FILE in these directories is found
to be owned by a user other than root, correct its ownership with the
following command:
$ sudo chown root FILERationale: 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. identifiers: CCE-27623-8, DISA FSO RHEL-06-000048 Remediation script:
|
Restrict Programs from Dangerous Execution PatternsgroupThe recommendations in this section are designed to ensure that the system's features to protect against potentially dangerous program execution are activated. These protections are applied at the system initialization or kernel level, and defend against certain types of badly-configured or compromised programs. |
contains 2 rules |
Enable ExecShieldgroupExecShield describes kernel features that provide
protection against exploitation of memory corruption errors such as buffer
overflows. These features include random placement of the stack and other
memory regions, prevention of execution in memory that should only hold data,
and special handling of text buffers. These protections are enabled by default and
controlled through |
contains 2 rules |
Enable ExecShieldrule
To set the runtime status of the $ sudo sysctl -w kernel.exec-shield=1If this is not the system's default value, add the following line to /etc/sysctl.conf :
kernel.exec-shield = 1Rationale: 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. identifiers: CCE-27007-4, DISA FSO RHEL-06-000079 references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, Test attestation on 20121024 by DS Remediation script:
|
Enable Randomized Layout of Virtual Address Spacerule
To set the runtime status of the $ sudo sysctl -w kernel.randomize_va_space=2If this is not the system's default value, add the following line to /etc/sysctl.conf :
kernel.randomize_va_space = 2Rationale: 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. identifiers: CCE-26999-3, DISA FSO RHEL-06-000078 references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, Test attestation on 20121024 by DS Remediation script:
|
SELinuxgroupSELinux is a feature of the Linux kernel which can be
used to guard against misconfigured or compromised programs.
SELinux enforces the idea that programs should be limited in what
files they can access and what actions they can take.
|
contains 4 rules |
Ensure SELinux Not Disabled in /etc/grub.confruleSELinux can be disabled at boot time by an argument in
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. identifiers: CCE-26956-3, DISA FSO RHEL-06-000017 references: AC-3, AC-3(3), AC-6, AU-9, 22, 32, Test attestation on 20121024 by DS Remediation script:
|
Ensure SELinux State is EnforcingruleThe SELinux state should be set to SELINUX=enforcingRationale: 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. identifiers: CCE-26969-6, DISA FSO RHEL-06-000020 references: AC-3, AC-3(3), AC-4, AC-6, AU-9, 22, 32, 26, Test attestation on 20121024 by DS Remediation script:
|
Configure SELinux PolicyruleThe SELinux SELINUXTYPE=targetedOther policies, such as mls , provide additional security labeling
and greater confinement but are not compatible with many general-purpose
use cases.
Rationale:
Setting the SELinux policy to identifiers: CCE-26875-5, DISA FSO RHEL-06-000023 references: AC-3, AC-3(3), AC-4, AC-6, AU-9, 22, 32, Test attestation on 20121024 by DS Remediation script:
|
Ensure No Device Files are Unlabeled by SELinuxruleDevice 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
If a device file carries the SELinux type identifiers: CCE-26774-0, DISA FSO RHEL-06-000025 references: AC-6, AU-9, CM-7, 22, 32, Test attestation on 20121024 by DS |
Account and Access ControlgroupIn traditional Unix security, if an attacker gains shell access to a certain login account, they can perform any action or access any file to which that account has access. Therefore, making it more difficult for unauthorized people to gain shell access to accounts, particularly to privileged accounts, is a necessary part of securing a system. This section introduces mechanisms for restricting access to accounts under RHEL 6. |
contains 24 rules |
Protect Accounts by Restricting Password-Based LogingroupConventionally, Unix shell accounts are accessed by
providing a username and password to a login program, which tests
these values for correctness using the |
contains 8 rules |
Restrict Root Loginsgroup
Direct root logins should be allowed only for emergency use.
In normal situations, the administrator should access the system
via a unique unprivileged account, and then use |
contains 2 rules |
Ensure that System Accounts Do Not Run a Shell Upon Loginrule
Some accounts are not associated with a human
user of the system, and exist to perform some administrative
function. Should an attacker be able to log into these accounts,
they should not be granted access to a shell.
$ sudo usermod -s /sbin/nologin SYSACCT warning
Do not perform the steps in this
section on the root account. Doing so might cause the system to
become inaccessible.
Ensuring shells are not given to system accounts upon login makes it more difficult for attackers to make use of system accounts. identifiers: CCE-26966-2 references: AC-2, 178, Test attestation on 20121024 by DS |
Verify Only Root Has UID 0ruleIf 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. identifiers: CCE-26971-2, DISA FSO RHEL-06-000032 references: AC-6, IA-2(1), 366, Test attestation on 20121024 by DS Remediation script:
|
Verify Proper Storage and Existence of Password Hashesgroup
By default, password hashes for local accounts are stored
in the second field (colon-separated) in
|
contains 2 rules |
Prevent Log In to Accounts With Empty PasswordruleIf an account is configured for password authentication
but does not have an assigned password, it may be possible to log
onto the account without authentication. Remove any instances of the 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. identifiers: CCE-27038-9, DISA FSO RHEL-06-000030 references: IA-5(b), IA-5(c), IA-5(1)(a), Test attestation on 20121024 by DS Remediation script:
|
Verify All Account Password Hashes are Shadowedrule
If any password hashes are stored in
The hashes for all user account passwords should be stored in
the file identifiers: CCE-26476-2, DISA FSO RHEL-06-000031 references: IA-5(h), 201, Test attestation on 20121024 by DS |
Set Password Expiration ParametersgroupThe file $ sudo chage -M 180 -m 7 -W 7 USER |
contains 4 rules |
Set Password Minimum Length in login.defsruleTo specify password length requirements for new accounts,
edit the file PASS_MIN_LEN 6 The DoD requirement is 14 .
The FISMA requirement is 12 .
If a program consults /etc/login.defs and also another PAM module
(such as pam_cracklib ) during a password change operation,
then the most restrictive must be satisfied. See PAM section
for more information about enforcing password quality requirements.
Rationale:Requiring a minimum password length makes password cracking attacks more difficult by ensuring a larger search space. However, any security benefit from an onerous requirement must be carefully weighed against usability problems, support costs, or counterproductive behavior that may result. identifiers: CCE-27002-5, DISA FSO RHEL-06-000050 references: IA-5(f), IA-5(1)(a), 205, Test attestation on 20121026 by DS Remediation script:
|
Set Password Minimum AgeruleTo specify password minimum age for new accounts,
edit the file PASS_MIN_DAYS 7A value of 1 day is considered for sufficient for many environments. The DoD requirement is 1. Rationale: Setting the minimum password age protects against users cycling back to a favorite password after satisfying the password reuse requirement. identifiers: CCE-27013-2, DISA FSO RHEL-06-000051 references: IA-5(f), IA-5(1)(d), 198, Test attestation on 20121026 by DS Remediation script:
|
Set Password Maximum AgeruleTo specify password maximum age for new accounts,
edit the file PASS_MAX_DAYS 60A value of 180 days is sufficient for many environments. The DoD requirement is 60. Rationale: Setting the password maximum age ensures users are required to periodically change their passwords. This could possibly decrease the utility of a stolen password. Requiring shorter password lifetimes increases the risk of users writing down the password in a convenient location subject to physical compromise. identifiers: CCE-26985-2, DISA FSO RHEL-06-000053 references: IA-5(f), IA-5(g), IA-5(1)(d), 180, 199, 76, Test attestation on 20121026 by DS Remediation script:
|
Set Password Warning AgeruleTo specify how many days prior to password
expiration that a warning will be issued to users,
edit the file PASS_WARN_AGE 7The DoD requirement is 7. Rationale: Setting the password warning age enables users to make the change at a practical time. identifiers: CCE-26988-6, DISA FSO RHEL-06-000054 references: AC-2(2), IA-5(f), Test attestation on 20121026 by DS Remediation script:
|
Protect Accounts by Configuring PAMgroupPAM, or Pluggable Authentication Modules, is a system
which implements modular authentication for Linux programs. PAM provides
a flexible and configurable architecture for authentication, and it should be configured
to minimize exposure to unnecessary risk. This section contains
guidance on how to accomplish that.
warning
Be careful when making changes to PAM's
configuration files. The syntax for these files is complex, and
modifications can have unexpected consequences. The default
configurations shipped with applications should be sufficient for
most users. warning
Running authconfig or
system-config-authentication will re-write the PAM configuration
files, destroying any manually made changes and replacing them with
a series of system defaults. One reference to the configuration
file syntax can be found at
http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/sag-configuration-file.html. |
contains 11 rules |
Set Password Quality RequirementsgroupThe default |
contains 6 rules |
Set Password Quality Requirements, if using pam_cracklibgroupThe password requisite pam_cracklib.so try_first_pass retry=3and then alter it to read: password required pam_cracklib.so try_first_pass retry=3 maxrepeat=3 minlen=14 dcredit=-1 ucredit=-1 ocredit=-1 lcredit=-1 difok=4If no such line exists, add one as the first line of the password section in /etc/pam.d/system-auth .
The arguments can be modified to ensure compliance with
your organization's security policy. Discussion of each parameter follows.
warning
Note that the password quality
requirements are not enforced for the root account for some
reason. |
contains 6 rules |
Set Password Retry Prompts Permitted Per-SessionruleTo configure the number of retry prompts that are permitted per-session:
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. identifiers: CCE-27123-9 references: IA-5(c), 1092, Test attestation on 20121024 by DS |
Set Password Strength Minimum Digit CharactersruleThe pam_cracklib module's Requiring digits makes password guessing attacks more difficult by ensuring a larger search space. identifiers: CCE-26374-9, DISA FSO RHEL-06-000056 references: IA-5(b), IA-5(c), 194, 194, Test attestation on 20121024 by DS Remediation script:
|
Set Password Strength Minimum Uppercase CharactersruleThe pam_cracklib module's Requiring a minimum number of uppercase characters makes password guessing attacks more difficult by ensuring a larger search space. identifiers: CCE-26601-5, DISA FSO RHEL-06-000057 references: IA-5(b), IA-5(c), IA-5(1)(a), 192, Test attestation on 20121024 by DS Remediation script:
|
Set Password Strength Minimum Special CharactersruleThe pam_cracklib module's Requiring a minimum number of special characters makes password guessing attacks more difficult by ensuring a larger search space. identifiers: CCE-26409-3, DISA FSO RHEL-06-000058 references: IA-5(b), IA-5(c), IA-5(1)(a), 1619, 266, Test attestation on 20121024 by DS Remediation script:
|
Set Password Strength Minimum Lowercase CharactersruleThe pam_cracklib module's Requiring a minimum number of lowercase characters makes password guessing attacks more difficult by ensuring a larger search space. identifiers: CCE-26631-2, DISA FSO RHEL-06-000059 references: IA-5(b), IA-5(c), IA-5(1)(a), 193, Test attestation on 20121024 by DS Remediation script:
|
Set Password Strength Minimum Different CharactersruleThe pam_cracklib module's 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. identifiers: CCE-26615-5, DISA FSO RHEL-06-000060 references: IA-5(b), IA-5(c), IA-5(1)(b), 195, Test attestation on 20121024 by DS Remediation script:
|
Set Lockouts for Failed Password AttemptsgroupThe warning
Locking out user accounts presents the
risk of a denial-of-service attack. The lockout policy
must weigh whether the risk of such a
denial-of-service attack outweighs the benefits of thwarting
password guessing attacks. |
contains 2 rules |
Set Deny For Failed Password Attemptsrule
To configure the system to lock out accounts after a number of incorrect login
attempts using
Locking out user accounts after a number of incorrect attempts prevents direct password guessing attacks. identifiers: CCE-26844-1, DISA FSO RHEL-06-000061 Remediation script:
|
Limit Password ReuseruleDo not allow users to reuse recent passwords. This can
be accomplished by using the password sufficient pam_unix.so existing_options remember=5The DoD STIG requirement is 5 passwords.Rationale: Preventing re-use of previous passwords helps ensure that a compromised password is not re-used by a user. identifiers: CCE-26741-9, DISA FSO RHEL-06-000274 references: IA-5(f), IA-5(1)(e), 200, Test attestation on 20121024 by DS Remediation script:
|
Set Password Hashing AlgorithmgroupThe system's default algorithm for storing password hashes in
|
contains 3 rules |
Set Password Hashing Algorithm in /etc/pam.d/system-authrule
In password sufficient pam_unix.so sha512 other arguments...This will help ensure when local users change their passwords, hashes for the new passwords will be generated using the SHA-512 algorithm. This is the default. Rationale: Using a stronger hashing algorithm makes password cracking attacks more difficult. identifiers: CCE-26303-8, DISA FSO RHEL-06-000062 references: IA-5(b), IA-5(c), IA-5(1)(c), IA-7, 803, Test attestation on 20121024 by DS Remediation script:
|
Set Password Hashing Algorithm in /etc/login.defsrule
In ENCRYPT_METHOD SHA512Rationale: Using a stronger hashing algorithm makes password cracking attacks more difficult. identifiers: CCE-27228-6, DISA FSO RHEL-06-000063 references: IA-5(b), IA-5(c), IA-5(1)(c), IA-7, 803, Test attestation on 20121024 by DS Remediation script:
|
Set Password Hashing Algorithm in /etc/libuser.confrule
In crypt_style = sha512Rationale: Using a stronger hashing algorithm makes password cracking attacks more difficult. identifiers: CCE-27229-4, DISA FSO RHEL-06-000064 references: IA-5(b), IA-5(c), IA-5(1)(c), IA-7, 803, Test attestation on 20121026 by DS |
Protect Physical Console AccessgroupIt is impossible to fully protect a system from an attacker with physical access, so securing the space in which the system is located should be considered a necessary step. However, there are some steps which, if taken, make it more difficult for an attacker to quickly or undetectably modify a system from its console. |
contains 5 rules |
Set Boot Loader PasswordgroupDuring the boot process, the boot loader is responsible for starting the execution of the kernel and passing options to it. The boot loader allows for the selection of different kernels - possibly on different partitions or media. The default RHEL boot loader for x86 systems is called GRUB. Options it can pass to the kernel include single-user mode, which provides root access without any authentication, and the ability to disable SELinux. To prevent local users from modifying the boot parameters and endangering security, protect the boot loader configuration with a password and ensure its configuration file's permissions are set properly. |
contains 4 rules |
Verify /etc/grub.conf User OwnershipruleThe file $ sudo chown root /etc/grub.confRationale: Only root should be able to modify important boot parameters. identifiers: CCE-26995-1, DISA FSO RHEL-06-000065 references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify /etc/grub.conf Group OwnershipruleThe file $ sudo chgrp root /etc/grub.confRationale:
The identifiers: CCE-27022-3, DISA FSO RHEL-06-000066 references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, 225, Test attestation on 20121026 by DS Remediation script:
|
Verify /boot/grub/grub.conf PermissionsruleFile permissions for $ sudo chmod 600 /boot/grub/grub.confRationale: Proper permissions ensure that only the root user can modify important boot parameters. identifiers: CCE-26949-8, DISA FSO RHEL-06-000067 references: http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf, 225, Test attestation on 20121026 by DS Remediation script:
|
Set Boot Loader PasswordruleThe grub boot loader should have password protection enabled to protect boot-time settings. To do so, select a password and then generate a hash from it by running the following command: $ grub-crypt --sha-512When prompted to enter a password, insert the following line into /etc/grub.conf
immediately after the header comments. (Use the output from grub-crypt as the
value of password-hash):
password --encrypted password-hashNOTE: To meet FISMA Moderate, the bootloader password MUST differ from the root password. 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. identifiers: CCE-26911-8, DISA FSO RHEL-06-000068 references: IA-2(1), IA-5(e) AC-3, 213, Test attestation on 20121026 by DS |
Require Authentication for Single User ModeruleSingle-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.
SINGLE=/sbin/suloginRationale: 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. identifiers: CCE-27040-5, DISA FSO RHEL-06-000069 references: IA-2(1), AC-3, 213, Test attestation on 20121024 by DS Remediation script:
|
Network Configuration and FirewallsgroupMost machines must be connected to a network of some
sort, and this brings with it the substantial risk of network
attack. This section discusses the security impact of decisions
about networking which must be made when configuring a system.
|
contains 8 rules |
IPv6groupThe system includes support for Internet Protocol version 6. A major and often-mentioned improvement over IPv4 is its enormous increase in the number of available addresses. Another important feature is its support for automatic configuration of many network settings. |
contains 1 rule |
Disable Support for IPv6 Unless NeededgroupDespite configuration that suggests support for IPv6 has been disabled, link-local IPv6 address auto-configuration occurs even when only an IPv4 address is assigned. The only way to effectively prevent execution of the IPv6 networking stack is to instruct the system not to activate the IPv6 kernel module. |
contains 1 rule |
Disable IPv6 Networking Support Automatic LoadingruleTo prevent the IPv6 kernel module ( options ipv6 disable=1This permits the IPv6 module to be loaded (and thus satisfy other modules that depend on it), while disabling support for the IPv6 protocol. Rationale: Any unnecessary network stacks - including IPv6 - should be disabled, to reduce the vulnerability to exploitation. identifiers: CCE-27153-6, DISA FSO RHEL-06-000098 references: CM-7, 1551, Test attestation on 20121024 by DS Remediation script:
|
iptables and ip6tablesgroupA host-based firewall called |
contains 3 rules |
Inspect and Activate Default RulesgroupView the currently-enforced $ sudo iptables -nL --line-numbersThe command is analogous for ip6tables .
If the firewall does not appear to be active (i.e., no rules appear), activate it and ensure that it starts at boot by issuing the following commands (and analogously for ip6tables ):
$ sudo service iptables restartThe default iptables rules are: Chain INPUT (policy ACCEPT) num target prot opt source destination 1 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 2 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 3 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 4 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 5 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain FORWARD (policy ACCEPT) num target prot opt source destination 1 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT) num target prot opt source destinationThe ip6tables default rules are essentially the same. |
contains 2 rules |
Verify ip6tables Enabled if Using IPv6rule
The $ sudo chkconfig --level 2345 ip6tables onRationale: The identifiers: CCE-27006-6, DISA FSO RHEL-06-000103 references: AC-4, CA-3(c), CM-7, 32, 66, 1115, 1118, 1092, 1117, 1098, 1100, 1097, 1414, Test attestation on 20121024 by DS Remediation script:
|
Verify iptables Enabledrule
The $ sudo chkconfig --level 2345 iptables onRationale:
The identifiers: CCE-27018-1, DISA FSO RHEL-06-000117 references: AC-4, CA-3(c), CM-7, 32, 66, 1115, 1118, 1092, 1117, 1098, 1100, 1097, 1414, Test attestation on 20121024 by DS Remediation script:
|
Strengthen the Default RulesetgroupThe default rules can be strengthened. The system
scripts that activate the firewall rules expect them to be defined
in the configuration files warning
The program system-config-securitylevel
allows additional services to penetrate the default firewall rules
and automatically adjusts /etc/sysconfig/iptables . This program
is only useful if the default ruleset meets your security
requirements. Otherwise, this program should not be used to make
changes to the firewall configuration because it re-writes the
saved configuration file. |
contains 1 rule |
Set Default iptables Policy for Incoming PacketsruleTo set the default policy to DROP (instead of ACCEPT) for
the built-in INPUT chain which processes incoming packets,
add or correct the following line in
:INPUT DROP [0:0]Rationale: In identifiers: CCE-26444-0, DISA FSO RHEL-06-000120 references: CM-7, 66, 1109, 1154, 1414 Remediation script:
|
Uncommon Network ProtocolsgroupThe system includes support for several network protocols which are not commonly used. Although security vulnerabilities in kernel networking code are not frequently discovered, the consequences can be dramatic. Ensuring uncommon network protocols are disabled reduces the system's risk to attacks targeted at its implementation of those protocols. warning
Although these protocols are not commonly used, avoid disruption
in your network environment by ensuring they are not needed
prior to disabling them.
|
contains 4 rules |
Disable DCCP Supportrule
The Datagram Congestion Control Protocol (DCCP) is a
relatively new transport layer protocol, designed to support
streaming media and telephony.
To configure the system to prevent the install dccp /bin/trueRationale: Disabling DCCP protects the system against exploitation of any flaws in its implementation. identifiers: CCE-26448-1, DISA FSO RHEL-06-000124 references: CM-7, 382, Test attestation on 20121024 by DS Remediation script:
|
Disable SCTP Supportrule
The Stream Control Transmission Protocol (SCTP) is a
transport layer protocol, designed to support the idea of
message-oriented communication, with several streams of messages
within one connection.
To configure the system to prevent the install sctp /bin/trueRationale: Disabling SCTP protects the system against exploitation of any flaws in its implementation. identifiers: CCE-26410-1, DISA FSO RHEL-06-000125 references: CM-7, 382, Test attestation on 20121024 by DS Remediation script:
|
Disable RDS Supportrule
The Reliable Datagram Sockets (RDS) protocol is a transport
layer protocol designed to provide reliable high- bandwidth,
low-latency communications between nodes in a cluster.
To configure the system to prevent the install rds /bin/trueRationale: Disabling RDS protects the system against exploitation of any flaws in its implementation. identifiers: CCE-26239-4, DISA FSO RHEL-06-000126 references: CM-7, 382, Test attestation on 20121024 by DS Remediation script:
|
Disable TIPC Supportrule
The Transparent Inter-Process Communication (TIPC) protocol
is designed to provide communications between nodes in a
cluster.
To configure the system to prevent the install tipc /bin/trueRationale: Disabling TIPC protects the system against exploitation of any flaws in its implementation. identifiers: CCE-26696-5, DISA FSO RHEL-06-000127 references: CM-7, 382, Test attestation on 20121024 by DS Remediation script:
|
System Accounting with auditdgroupThe audit service provides substantial capabilities
for recording system activities. By default, the service audits about
SELinux AVC denials and certain types of security-relevant events
such as system logins, account modifications, and authentication
events performed by programs such as sudo.
Under its default configuration, type=AVC msg=audit(1226874073.147:96): avc: denied { getattr } for pid=2465 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file type=SYSCALL msg=audit(1226874073.147:96): arch=40000003 syscall=196 success=no exit=-13 a0=b98df198 a1=bfec85dc a2=54dff4 a3=2008171 items=0 ppid=2463 pid=2465 auid=502 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=6 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
|
contains 1 rule |
Configure auditd Rules for Comprehensive AuditinggroupThe
Auditing rules at startup are controlled by the file /etc/audit/audit.rules .
Add rules to it to meet the auditing requirements for your organization.
Each line in /etc/audit/audit.rules represents a series of arguments
that can be passed to auditctl and can be individually tested
during runtime. See documentation in /usr/share/doc/audit-VERSION and
in the related man pages for more details.
If copying any example audit rulesets from /usr/share/doc/audit-VERSION ,
be sure to comment out the
lines containing arch= which are not appropriate for your system's
architecture. Then review and understand the following rules,
ensuring rules are activated as needed for the appropriate
architecture.
After reviewing all the rules, reading the following sections, and editing as needed, the new rules can be activated as follows: $ sudo service auditd restart |
contains 1 rule |
System Audit Logs Must Have Mode 0640 or Less PermissiveruleChange the mode of the audit log files with the following command: $ sudo chmod 0640 audit_fileRationale: If users can write to audit logs, audit trails can be modified or destroyed. identifiers: CCE-27243-5, DISA FSO RHEL-06-000383 references: AC-6, AU-1(b), AU-9, IR-5, 166, Test attestation on 20121024 by DS Remediation script:
|
Servicesgroup
The best protection against vulnerable software is running less software. This section describes how to review
the software which Red Hat Enterprise Linux 6 installs on a system and disable software which is not needed. It
then enumerates the software packages installed on a default RHEL 6 system and provides guidance about which
ones can be safely disabled.
|
contains 29 rules |
Obsolete ServicesgroupThis section discusses a number of network-visible
services which have historically caused problems for system
security, and for which disabling or severely limiting the service
has been the best available guidance for some time. As a result of
this, many of these services are not installed as part of RHEL 6
by default.
|
contains 12 rules |
XinetdgroupThe |
contains 2 rules |
Disable xinetd Servicerule
The $ sudo chkconfig xinetd offRationale: 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. identifiers: CCE-27046-2, DISA FSO RHEL-06-000203 references: CM-7, 305, Test attestation on 20121026 by DS |
Uninstall xinetd PackageruleThe $ sudo yum erase xinetdRationale:
Removing the identifiers: CCE-27005-8, DISA FSO RHEL-06-000204 references: CM-7, 305, Test attestation on 20121026 by DS Remediation script:
|
TelnetgroupThe telnet protocol does not provide confidentiality or integrity for information transmitted on the network. This includes authentication information such as passwords. Organizations which use telnet should be actively working to migrate to a more secure protocol. |
contains 2 rules |
Disable telnet Servicerule
The $ sudo chkconfig telnet offRationale: 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. identifiers: CCE-26836-7, DISA FSO RHEL-06-000211 references: CM-7, IA-5(1)(c), 68, 1436, 197, 877, 888, Test attestation on 20121026 by DS |
Uninstall telnet-server PackageruleThe $ sudo yum erase telnet-serverRationale:
Removing the identifiers: CCE-27073-6, DISA FSO RHEL-06-000206 references: CM-7, 305, 381, Test attestation on 20121026 by DS Remediation script:
|
Rlogin, Rsh, and RexecgroupThe Berkeley r-commands are legacy services which allow cleartext remote access and have an insecure trust model. |
contains 4 rules |
Uninstall rsh-server PackageruleThe $ sudo yum erase rsh-serverRationale: The identifiers: CCE-27062-9, DISA FSO RHEL-06-000213 references: CM-7, 305, 381, Test attestation on 20121026 by DS Remediation script:
|
Disable rexec ServiceruleThe $ sudo chkconfig rexec offRationale: 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. identifiers: CCE-27208-8, DISA FSO RHEL-06-000216 references: CM-7, 68, 1436, Test attestation on 20121026 by DS |
Disable rsh ServiceruleThe $ sudo chkconfig rsh offRationale: 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. identifiers: CCE-26994-4, DISA FSO RHEL-06-000214 references: CM-7, IA-5(1)(c), 68, 1436, Test attestation on 20121026 by DS |
Disable rlogin ServiceruleThe $ sudo chkconfig rlogin offRationale: 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. identifiers: CCE-26865-6, DISA FSO RHEL-06-000218 references: CM-7, IA-5(1)(c), 1436, Test attestation on 20121026 by DS |
NISgroupThe Network Information Service (NIS), also known as 'Yellow Pages' (YP), and its successor NIS+ have been made obsolete by Kerberos, LDAP, and other modern centralized authentication services. NIS should not be used because it suffers from security problems inherent in its design, such as inadequate protection of important authentication information. |
contains 2 rules |
Uninstall ypserv PackageruleThe $ sudo yum erase ypservRationale: Removing the identifiers: CCE-27079-3, DISA FSO RHEL-06-000220 references: CM-7, 305, 381, Test attestation on 20121026 by DS Remediation script:
|
Disable ypbind ServiceruleThe $ sudo chkconfig ypbind offRationale:
Disabling the identifiers: CCE-26894-6, DISA FSO RHEL-06-000221 references: CM-7, 305, Test attestation on 20121026 by DS |
TFTP ServergroupTFTP is a lightweight version of the FTP protocol which has traditionally been used to configure networking equipment. However, TFTP provides little security, and modern versions of networking operating systems frequently support configuration via SSH or other more secure protocols. A TFTP server should be run only if no more secure method of supporting existing equipment can be found. |
contains 2 rules |
Disable tftp ServiceruleThe $ sudo chkconfig tftp offRationale:
Disabling the identifiers: CCE-27055-3, DISA FSO RHEL-06-000223 references: CM-7, 1436, Test attestation on 20121026 by DS Remediation script:
|
Uninstall tftp-server Packagerule
The $ sudo yum erase tftp-serverRationale:
Removing the identifiers: CCE-26946-4, DISA FSO RHEL-06-000222 references: CM-7, 305, Test attestation on 20121026 by DS |
Base ServicesgroupThis section addresses the base services that are installed on a RHEL 6 default installation which are not covered in other sections. Some of these services listen on the network and should be treated with particular discretion. Other services are local system utilities that may or may not be extraneous. In general, system services should be disabled if not required. |
contains 5 rules |
Disable Automatic Bug Reporting Tool (abrtd)ruleThe Automatic Bug Reporting Tool ( $ sudo chkconfig abrtd offRationale: 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. identifiers: CCE-27247-6, DISA FSO RHEL-06-000261 Remediation script:
|
Disable ntpdate Service (ntpdate)ruleThe $ sudo chkconfig ntpdate offRationale: The identifiers: CCE-27256-7, DISA FSO RHEL-06-000265 references: CM-7, 382, Test attestation on 20121024 by DS |
Disable Odd Job Daemon (oddjobd)ruleThe $ sudo chkconfig oddjobd offRationale: The identifiers: CCE-27257-5, DISA FSO RHEL-06-000266 references: CM-7, 381, Test attestation on 20121024 by DS Remediation script:
|
Disable Apache Qpid (qpidd)ruleThe $ sudo chkconfig qpidd offRationale: 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 identifiers: CCE-26928-2, DISA FSO RHEL-06-000267 Remediation script:
|
Disable Network Router Discovery Daemon (rdisc)ruleThe $ sudo chkconfig rdisc offRationale: 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. identifiers: CCE-27261-7, DISA FSO RHEL-06-000268 references: AC-4, CM-7, 382, Test attestation on 20121024 by DS Remediation script:
|
Cron and At DaemonsgroupThe cron and at services are used to allow commands to be executed at a later time. The cron service is required by almost all systems to perform necessary maintenance tasks, while at may or may not be required on a given system. Both daemons should be configured defensively. |
contains 1 rule |
Disable At Service (atd)ruleThe $ sudo chkconfig atd offRationale:
The identifiers: CCE-27249-2, DISA FSO RHEL-06-000262 Remediation script:
|
SSH ServergroupThe SSH protocol is recommended for remote login and
remote file transfer. SSH provides confidentiality and integrity
for data exchanged between two systems, as well as server
authentication, through the use of public key cryptography. The
implementation included with the system is called OpenSSH, and more
detailed documentation is available from its website,
http://www.openssh.org. Its server program is called |
contains 10 rules |
Configure OpenSSH Server if NecessarygroupIf the system needs to act as an SSH server, then
certain changes should be made to the OpenSSH daemon configuration
file |
contains 10 rules |
Allow Only SSH Protocol 2ruleOnly SSH protocol version 2 connections should be
permitted. The default setting in
Protocol 2Rationale: SSH protocol version 1 suffers from design flaws that result in security vulnerabilities and should not be used. identifiers: CCE-27072-8, DISA FSO RHEL-06-000227 references: AC-3(10), IA-5(1)(c), 776, 774, 1436, Test attestation on 20121024 by DS Remediation script:
|
Set SSH Idle Timeout IntervalruleSSH allows administrators to set an idle timeout
interval.
After this interval has passed, the idle user will be
automatically logged out.
ClientAliveInterval 5The 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. identifiers: CCE-26919-1, DISA FSO RHEL-06-000230 references: AC-2(5), SA-8, 879, 1133, Test attestation on 20121024 by DS Remediation script:
|
Set SSH Client Alive CountruleTo ensure the SSH idle timeout occurs precisely when the ClientAliveCountMax 0Rationale:
This ensures a user login will be terminated as soon as the identifiers: CCE-26282-4, DISA FSO RHEL-06-000231 references: AC-2(5), SA-8, 879, 1133, Test attestation on 20121024 by DS Remediation script:
|
Disable SSH Support for .rhosts FilesruleSSH can emulate the behavior of the obsolete rsh
command in allowing users to enable insecure access to their
accounts via IgnoreRhosts yesRationale: SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. identifiers: CCE-27124-7, DISA FSO RHEL-06-000234 Remediation script:
|
Disable Host-Based AuthenticationruleSSH's cryptographic host-based authentication is
more secure than HostbasedAuthentication noRationale: SSH trust relationships mean a compromise on one host can allow an attacker to move trivially to other hosts. identifiers: CCE-27091-8, DISA FSO RHEL-06-000236 references: AC-3, 765, 766, Test attestation on 20121024 by DS Remediation script:
|
Disable SSH Root LoginruleThe root user should never be allowed to login to a
system directly over a network.
To disable root login via SSH, add or correct the following line
in PermitRootLogin noRationale: Permitting direct root login reduces auditable information about who ran privileged commands on the system and also allows direct attack attempts on root's password. identifiers: CCE-27100-7, DISA FSO RHEL-06-000237 references: AC-3, AC-6(2), IA-2(1), 770, Test attestation on 20121024 by DS Remediation script:
|
Disable SSH Access via Empty PasswordsruleTo explicitly disallow remote login from accounts with
empty passwords, add or correct the following line in
PermitEmptyPasswords noAny accounts with empty passwords should be disabled immediately, and PAM configuration should prevent users from being able to assign themselves empty passwords. Rationale: Configuring this setting for the SSH daemon provides additional assurance that remote login via SSH will require a password, even in the event of misconfiguration elsewhere. identifiers: CCE-26887-0, DISA FSO RHEL-06-000239 references: AC-3, 765, 766, Test attestation on 20121024 by DS Remediation script:
|
Enable SSH Warning Bannerrule
To enable the warning banner and ensure it is consistent
across the system, add or correct the following line in Banner /etc/issueAnother section contains information on how to create an appropriate system-wide warning banner. Rationale: The warning message reinforces policy awareness during the login 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. identifiers: CCE-27112-2, DISA FSO RHEL-06-000240 references: AC-8(a), 48, Test attestation on 20121024 by DS Remediation script:
|
Do Not Allow SSH Environment OptionsruleTo ensure users are not able to present
environment options to the SSH daemon, add or correct the following line
in PermitUserEnvironment noRationale: SSH environment options potentially allow users to bypass access restriction in some configurations. identifiers: CCE-27201-3, DISA FSO RHEL-06-000241 references: 1414, Test attestation on 20121024 by DS Remediation script:
|
Use Only Approved CiphersruleLimit the ciphers to those algorithms which are FIPS-approved.
Counter (CTR) mode is also preferred over cipher-block chaining (CBC) mode.
The following line in Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbcThe man page sshd_config(5) contains a list of supported ciphers.
Rationale:Approved algorithms should impart some level of confidence in their implementation. These are also required for compliance. identifiers: CCE-26555-3, DISA FSO RHEL-06-000243 references: AC-3, AC-17(2), SI-7, IA-5(1)(c), IA-7, 803, 1144, 1145, 1146, Test attestation on 20121024 by DS Remediation script:
|
Avahi ServergroupThe Avahi daemon implements the DNS Service Discovery and Multicast DNS protocols, which provide service and host discovery on a network. It allows a system to automatically identify resources on the network, such as printers or web servers. This capability is also known as mDNSresponder and is a major part of Zeroconf networking. |
contains 1 rule |
Disable Avahi Server if PossiblegroupBecause the Avahi daemon service keeps an open network port, it is subject to network attacks. Disabling it can reduce the system's vulnerability to such attacks. |
contains 1 rule |
Disable Avahi Server Softwarerule
The $ sudo chkconfig avahi-daemon offRationale: 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. identifiers: CCE-27087-6, DISA FSO RHEL-06-000246 |