e57593dfd4
With the upcoming changes to rebase onto the RHEL 7 STIG controls, there needs to be a new solution for documentation that is easier to manage and filter. This patch automates the generation of the STIG control documentation in the following way: * A Sphinx extension runs early in the doc build process that writes all of the individual STIG control docs as well as ToC pages. * ToC pages are now sorted by severity, tag, and implementation status. * A giant listing of controls is easier to navigate now. * Docs are generated from metadata in the /doc/metadata directory. New documentation only needs to be added there. (Will explain this in the developer notes in a subsequent patch.) Implements: blueprint security-rhel7-stig Change-Id: I455af1121049f52193e98e2c9cb1ba5d4c292386
openstack-ansible-security
The goal of the openstack-ansible-security role is to improve security within openstack-ansible deployments. The role is based on the Security Technical Implementation Guide (STIG) for Red Hat Enterprise Linux 6.
Requirements
This role can be used with or without the openstack-ansible role. It requires Ansible 1.8.3 at a minimum.
Role Variables
All of the variables for this role are in defaults/main.yml.
Dependencies
This role has no dependencies.
Example Playbook
Using the role is fairly straightforward:
- hosts: servers
roles:
- openstack-ansible-security
Running with Vagrant
This role can be tested easily on multiple platforms using Vagrant.
The Vagrantfile supports testing on:
- Ubuntu 14.04
- Ubuntu 16.04
- CentOS 7
To test on all platforms:
vagrant destroy --force && vagrant up
To test on Ubuntu 14.04 only:
vagrant destroy ubuntu1404 --force && vagrant up ubuntu1404
To test on Ubuntu 16.04 only:
vagrant destroy ubuntu1604 --force && vagrant up ubuntu1604
To test on CentOS 7 only:
vagrant destroy centos7 --force && vagrant up centos7
License
Apache 2.0
Author Information
For more information, join #openstack-ansible on Freenode.