Packt+ | Advance your knowledge in tech

You're reading from Security Automation with Ansible 2 Leverage Ansible 2 to automate complex security tasks like application security, network security, and malware analysis

Product type Paperback

Published in Dec 2017

Publisher Packt

ISBN-13 9781788394512

Length 364 pages

Edition 1st Edition

Tools

Ansible

Concepts

Application Security

Authors (2):

Akash Mahajan

MADHU AKULA

View More author details

Table of Contents (12) Chapters

Preface

1. Introduction to Ansible Playbooks and Roles FREE CHAPTER

2. Ansible Tower, Jenkins, and Other Automation Tools

3. Setting Up a Hardened WordPress with Encrypted Automated Backups

4. Log Monitoring and Serverless Automated Defense (Elastic Stack in AWS)

5. Automating Web Application Security Testing Using OWASP ZAP

6. Vulnerability Scanning with Nessus

7. Security Hardening for Applications and Networks

8. Continuous Security Scanning for Docker Containers

9. Automating Lab Setups for Forensics Collection and Malware Analysis

10. Writing an Ansible Module for Security Testing

11. Ansible Security Best Practices, References, and Further Reading

Planning and what to keep in mind

The Ansible Developer Guide has a section on how should you develop a module (http://docs.ansible.com/ansible/latest/dev_guide/developing_modules.html#should-you-develop-a-module).

In the section, they have multiple points on what to keep in mind before going ahead and developing a module.

Does a similar module already exist? It's always a good idea to check the current modules to see whether what you plan to build has been done before. The good news is, so far nobody has built an Open Web Application Security Project (OWASP) Zed Attack Proxy (ZAP) module.

Has someone already worked on a similar Pull Request? Again, maybe the module hasn't been published but that doesn't mean that folks are not working on it already. The document provides three convenient links to check if a similar PR is already in place.

Additionally, it asks if rather than a module, we should look at an action plugin or role. The main reason we think it makes sense for us to develop the...