Major Hayden ee00627b7a Add check/audit to gate testing
Checking or auditing an existing environment is a first class feature
in the security role, but we're not currently checking that feature
in the gate. A few users of the role have come forward with some
bugs around the check mode functionality and we should test this
more regularly.

This patch adds a quick audit check right before the functional test runs.
This adds about 30-60 seconds onto the gate test, but it should help
with catching these bugs.

Change-Id: I5f4adc292f027b2eb7429be843c167d152c0169d
2016-06-07 13:22:12 +00:00
2016-06-03 10:49:52 -05:00
2016-06-07 13:22:12 +00:00
2016-05-04 08:56:41 -05:00
2015-10-05 17:37:21 +00:00
2016-05-03 08:58:41 +01:00
2016-06-07 13:22:12 +00:00

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

Security Ansible can be easily run for testing using Vagrant.

To do so run: vagrant destroy To destroy any previously created Vagrant setup vagrant up Spin up Ubuntu Trusty VM and run ansible-security against it

License

Apache 2.0

Author Information

For more information, join #openstack-ansible on Freenode.

Description
Ansible role for security hardening
Readme 5.4 MiB
Languages
Jinja 44.5%
Python 41.2%
Shell 14.3%