-
Notifications
You must be signed in to change notification settings - Fork 144
Security Automation
The Security Automation Working Group collaborates on Topics in Information Security Automation in Ansible.
Ansible can be the automation glue between disjoint systems and security appliances that have little to no integrations. Security Operators can utilize Ansible to be more productive, adapt to the growing demand of the modern IT landscape, ensure consistency in their IT environments, and respond to security incidents faster. Beyond that, Ansible can be utilized for automated implementation of security standards, systems hardening, and compliance. Our goal here is to help foster a cross discipline and cross functional collaborative community of Information Security Professionals through the power of automation via Ansible.
- Welcome! We're just getting started!
- Weekly meetings will be held starting in October 2019, meeting information below.
Name | GitHub (+ IRC) | Role | Affiliation |
---|---|---|---|
Adam Miller | maxamillion | Lead | Red Hat/Ansible |
Sumit Jaiswal | justjais | Lead | Red Hat/Ansible |
Abhijeet Kasurde | Akasurde | Member | Red Hat/Ansible |
James Cassell | jamescassell | Reviewer | Independent |
Thomas Young | tyoung2018 | Reviewer | Red Hat |
Jonathan Lozada De La Matta | jlozadad | Member | Red Hat |
Francisco Ramirez | Cisco-redhat | Member | Red Hat |
Add yourself to this list as a Reviewer (help review PRs) or as a Member (discuss issues/roadmap) and join the IRC Channel! :)
Ansible Security Use-case Roles
If you want to bring up an issue, a review-request or a PR to discuss on the meeting, just put it on the meeting agenda.
We have weekly meetings on Mondays at 15:00 UTC on IRC channel #ansible-security.
Meeting minutes and logs are available by channel or by team.
- Help foster a community of automation practitioners in Information Security
- Collaborative development on various efforts in the community space
- Engagement with the broader InfoSec Community (meetups, events, online communities, etc)
- Your idea here!
- Ansible Lockdown - (Lockdown Working Group)
- Ansible Hardening
- Compliance As Code
- Dev Sec
- Ansible Security and Compliance Use Case
- [Book] Security Automation with Ansible 2
- [Udemy Course] Ansible 2 for Security Automation and Implementing DevOps
- Using OpenSCAP with Ansible
Project | Status |
---|---|
IBM QRadar Collection | |
Splunk Enterprise Security Collection | |
ids_install Role | |
ids_config Role | |
ids_rule Role | |
ids_rule_facts Role | |
log_manager Role | |
acl_manager Role |
You can find roadmaps at Roadmaps.
We exist within the Ansible Community and therefore use all typical outlets you would expect us to. However, we do have our own IRC channel on freenode as our discussions would often be off-topic for other channels.
IRC: #ansible-security
on irc.freenode.net
Join with Freenode Webchat
Join with Matrix
This Wiki is used for quick notes, not for support or documentation.
Working groups are now in the Ansible forum
Ansible project:
Community,
Contributor Experience,
Docs,
News,
Outreach,
RelEng,
Testing
Cloud:
AWS,
Azure,
CloudStack,
Container,
DigitalOcean,
Docker,
hcloud,
Kubernetes,
Linode,
OpenStack,
oVirt,
Virt,
VMware
Networking:
ACI,
AVI,
F5,
Meraki,
Network,
NXOS
Ansible Developer Tools:
Ansible-developer-tools
Software:
Crypto,
Foreman,
GDrive,
GitLab,
Grafana,
IPA,
JBoss,
MongoDB,
MySQL,
PostgreSQL,
RabbitMQ,
Zabbix
System:
AIX,
BSD,
HP-UX,
macOS,
Remote Management,
Solaris,
Windows
Security:
Security-Automation,
Lockdown
Tooling:
AWX,
Galaxy,
Molecule
Plugins:
httpapi