Go to file
Major Hayden 373a03ebf8 Fix duplicated config options in auditd.conf
The regular expressions for max_log_file and space_left
were not specific enough and the options were repeated in the
auditd.conf over multiple runs of the security role. This patch
makes those regular expressions more specific.

A manual backport was required due to some variable namespacing
work done in master.

Closes-bug: 1604958
Change-Id: I56925d6b983d156543ba853b3dca846fb460949e
2016-07-21 11:13:36 -05:00
2016-06-13 08:36:31 -05:00
2016-06-27 20:42:41 +00:00
2015-10-14 21:23:11 -05:00
2016-06-13 18:52:58 +00:00
2016-06-13 13:37:04 +00:00
2016-05-04 14:13:33 +00:00
2016-04-02 14:46:00 -04:00
2016-05-03 21:00:42 +00:00
2016-07-08 17:14:04 +01:00
2016-07-08 17:14:04 +01: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
RETIRED, Security Role for OpenStack-Ansible
Readme 8.4 MiB