This repository has been archived by the owner on Jun 10, 2024. It is now read-only.
Lockdown
THIS PAGE IS OLD and no longer maintained. For questions, please use the Ansible forum.
INACTIVE, THE INFO BELOW IS IRRELEVANT
The Lockdown Working group focuses on developing out roles that automate well known security standards. At the moment the principal focus is around hardening via STIG and CIS guidance.
| Project | Status |
|---|---|
| RHEL7 STIG |
 
|
| RHEL7 CIS |
 
|
| RHEL6 STIG |
 
|
| Windows 2008R2 MS STIG |
 
|
| Windows 2012 MS STIG |
 
|
Every other Thursday at 4PM UTC on #ansible-lockdown
Calendar iCal Link (REMOVED)
- Auto-gen documentation per role and aggregate them in a single portal
- Migrate all testing to Molecule
- Support applying roles against containers
- Combine efforts as much as possible with the Ansible Hardening and Compliance as Code projects
- Collect new ideas (including feature reqeust, issue, scenario, documentation feedback)
- Work together and have fun
- Define action plan and track progress
- Update focus as necessary
Project status is tracked and monitored via Lockdown GitHub Project
- David Federlein, dfederlein
- George Nalen, georgenalen
- James Cassell, jamescassell
TBD
-
#ansible-lockdownIRC channel (refer to the Communication guide for details). - ansible-lockdown mailing list on Google Groups.
- For security-related concerns email ansible@mindpointgroup.com. A security concern would be something where the content of a role leads to a vulnerability in the targeted system.