Skip to content

Latest commit

 

History

History
67 lines (40 loc) · 3.2 KB

README.md

File metadata and controls

67 lines (40 loc) · 3.2 KB

Ansible-Lockdown

Intro

Ansible-Lockdown is a collaborative effort between Ansible and our IT Security partner MindPoint Group to provide you with thorough, vetted, and trusted security roles that you can integrate with any of your existing playbooks or as the building blocks for completely new playbooks.

The initial effort is for the development of roles centered around STIG and CIS benchmark baselines. Based on community feedback we'll then proceed with other security guidelines for additional operating systems and applications.

This repository in particular is intended to serve as a centralized repository utilizing submodules that point to all security-role repositories that are jointly maintained Ansible and MindPoint Group.

Mailing List

Most of the communication around the project happens on the mailing list which can be accessed and subscribed to here: https://groups.google.com/forum/#!forum/ansible-lockdown

Instructions

In order to use the roles you should first ensure that you have Ansible installed. You can then download the roles in their entirety through git by following the appropriate links in the table or you can leverage ansible-galaxy.

STIGS

The standards are pulled directly from DISA.

CIS

The standards are pulled directly from CIS.

Contributing

Contributions to ansible-lockdown and STIG roles will follow a similar process to the main Ansible project. Fork the repository, make changes, and submit a pull-request. Pull-request should not contain any merges or merge-conflicts.

Feature request, bug reports, etc, should all be opened as GitHub tickets. An ansible-lockdown mailing list is in the works.

Current Build Statuses For Security Roles

Standard OS Repo Galaxy Link Status
DISA STIG RedHat 6.* Repo Galaxy STATUS
DISA STIG RedHat 7.* Repo TBD TBD

Note: A green badge represents a successful build which consists of:

  1. Creating an AWS EC2 instance from the AMI's provided by AWS as defaults.
  2. Applying the STIG baselines.
  3. Using OpenSCAP and STIGMA to further validate the application of the baselines.