Automated security hardening for Linux hosts¶

What does the role do?¶

It all starts with the Security Technical Implementation Guide (STIG) from the Defense Information Systems Agency (DISA), part of the United States Department of Defense. The guide is released with a public domain license and it is commonly used to secure systems at public and private organizations around the world.

Each configuration from the STIG is analyzed to determine what impact it could have on a live production environment and how to implement it in Ansible. Tasks are added to the role that configure a host to meet the configuration requirement. Each task is documented to explain what was changed, why it was changed, and what deployers need to understand about the change.

Deployers have the option to pick and choose which configurations are applied using Ansible variables and tags. Some tasks allow deployers to provide custom configurations to tighten down or relax certain requirements.

For more details, review the Documentation section below.

Documentation¶

The following documentation applies to the Ocata release. Documentation from previous releases are available in the Releases section below.

The RHEL 7 STIG content was first added in the Ocata release. The original RHEL 6 STIG content is deprecated in the Ocata release and will be removed in the next OpenStack release (Pike). The documentation for the RHEL 6 STIG content is still available:

Releases¶

Deployers should use the latest stable release for all production deployments.