Major Hayden 932bae76d2 Add /etc/apparmor.d/ for auditing
As noted in https://review.openstack.org/319438 , the /etc/apparmor.d/
directory was missing from the auditd rules applied for V-38541.

This is a manual backport of I564b72d103fa13af4562e4b21d68ef6097cecf37.
An clean cherry pick wasn't possible because of CentOS/SELinux changes
in the master/Newton branch that don't belong in mitaka and liberty.

Change-Id: Idf169538e3e155a9b9aa9119f65dc31428c9680c
2016-06-01 12:50:30 +00:00
2016-05-24 16:17:32 +00:00
2015-10-14 21:23:11 -05:00
2016-05-24 16:17:32 +00:00
2016-02-29 14:15:29 -06:00
2016-05-05 16:34:22 +01:00
2016-04-08 16:34:10 +01:00
2015-10-09 08:25:56 -05:00
2016-05-05 16:34:22 +01:00
2016-05-05 16:34:22 +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