Skip to content

InSpec profile to validate the secure configuration of Red Hat Enterprise Linux 6, against DISA's Red Hat Enterprise Linux 6 Security Technical Implementation Guide (STIG) Version 1, Release 21.

License

Notifications You must be signed in to change notification settings

mitre/redhat-enterprise-linux-6-stig-baseline

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

33 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

red-hat-enterprise-linux-6-stig-baseline

InSpec profile to validate the secure configuration of Red Hat Enterprise Linux 6, against DISA's Red Hat Enterprise Linux 6 Security Technical Implementation Guide (STIG) Version 1, Release 21.

Getting Started

It is intended and recommended that InSpec run this profile from a "runner" host (such as a DevOps orchestration server, an administrative management system, or a developer's workstation/laptop) against the target remotely over ssh.

For the best security of the runner, always install on the runner the latest version of InSpec and supporting Ruby language components.

Latest versions and installation options are available at the InSpec site.

Tailoring to Your Environment

The following inputs must be configured in an inputs ".yml" file for the profile to run correctly for your specific environment. More information about InSpec inputs can be found in the InSpec Profile Documentation.

auditd_space_left: ''

banner_text: ''

pam_faillock_fail_interval: 900

pam_cracklib_difok: 8

pam_faillock_deny: 3

pam_faillock_unlock_time: 604800

client_alive_interval: 900

# The minimum number of generations before a password can be reused.
min_reuse_generations: 6

# The number of days of inactivity before an account is disabled.
days_of_inactivity: 35

max_logins: 10

emergency_accounts: []

emergency_accounts_expiration_days: 1

temporary_accounts: []

temporary_accounts_expiration_days: 30

package_signing_keys: []

Running This Baseline Directly from Github

# How to run
inspec exec https://github.com/mitre/red-hat-enterprise-linux-6-stig-baseline/archive/master.tar.gz --target=ssh://<your_target_host_name_or_ip_address> --user=<target_account_with_administrative_privileges> --password=<password_for_target_account> --sudo --sudo-password=<sudo_password_for_target_if_required> --input-file=<path_to_your_inputs_file/name_of_your_inputs_file.yml> --reporter=cli json:<path_to_your_output_file/name_of_your_output_file.json>

Different Run Options

Full exec options

Running This Baseline from a local Archive copy

If your runner is not always expected to have direct access to GitHub, use the following steps to create an archive bundle of this baseline and all of its dependent tests:

(Git is required to clone the InSpec profile using the instructions below. Git can be downloaded from the Git site.)

When the "runner" host uses this profile baseline for the first time, follow these steps:

mkdir profiles
cd profiles
git clone https://github.com/mitre/red-hat-enterprise-linux-6-stig-baseline
inspec archive red-hat-enterprise-linux-6-stig-baseline
inspec exec <name of generated archive> --target=ssh://<your_target_host_name_or_ip_address> --user=<target_account_with_administrative_privileges> --password=<password_for_target_account> --sudo --sudo-password=<sudo_password_for_target_if_required> --input-file=<path_to_your_inputs_file/name_of_your_inputs_file.yml> --reporter=cli json:<path_to_your_output_file/name_of_your_output_file.json>

For every successive run, follow these steps to always have the latest version of this baseline:

cd red-hat-enterprise-linux-6-stig-baseline
git pull
cd ..
inspec archive red-hat-enterprise-linux-6-stig-baseline --overwrite
inspec exec <name of generated archive> --target=ssh://<your_target_host_name_or_ip_address> --user=<target_account_with_administrative_privileges> --password=<password_for_target_account> --sudo --sudo-password=<sudo_password_for_target_if_required> --input-file=<path_to_your_inputs_file/name_of_your_inputs_file.yml> --reporter=cli json:<path_to_your_output_file/name_of_your_output_file.json>

Viewing the JSON Results

The JSON results output file can be loaded into heimdall-lite for a user-interactive, graphical view of the InSpec results.

The JSON InSpec results file may also be loaded into a full heimdall server, allowing for additional functionality such as to store and compare multiple profile runs.

Authors

  • Sam Cornwell

Special Thanks

Contributing and Getting Help

To report a bug or feature request, please open an issue.

NOTICE

© 2018-2020 The MITRE Corporation.

Approved for Public Release; Distribution Unlimited. Case Number 18-3678.

NOTICE

MITRE hereby grants express written permission to use, reproduce, distribute, modify, and otherwise leverage this software to the extent permitted by the licensed terms provided in the LICENSE.md file included with this project.

NOTICE

This software was produced for the U. S. Government under Contract Number HHSM-500-2012-00008I, and is subject to Federal Acquisition Regulation Clause 52.227-14, Rights in Data-General.

No other use other than that granted to the U. S. Government, or to those acting on behalf of the U. S. Government under that Clause is authorized without the express written permission of The MITRE Corporation.

For further information, please contact The MITRE Corporation, Contracts Management Office, 7515 Colshire Drive, McLean, VA 22102-7539, (703) 983-6000.

NOTICE

DISA STIGs are published by DISA IASE, see: https://iase.disa.mil/Pages/privacy_policy.aspx

About

InSpec profile to validate the secure configuration of Red Hat Enterprise Linux 6, against DISA's Red Hat Enterprise Linux 6 Security Technical Implementation Guide (STIG) Version 1, Release 21.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages