Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Security Automation with Ansible 2

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

Arrow left icon
Product type Paperback
Published in Dec 2017
Publisher Packt
ISBN-13 9781788394512
Length 364 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Akash Mahajan Akash Mahajan
Author Profile Icon Akash Mahajan
Akash Mahajan
MADHU AKULA MADHU AKULA
Author Profile Icon MADHU AKULA
MADHU AKULA
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

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

Security hardening with benchmarks such as CIS, STIGs, and NIST


Benchmarks provide a great way for anyone to gain assurance of their individual security efforts. Created by security experts globally or led by security mature government departments such as NIST, benchmarks cover a whole range of systems, configurations, software, and more.

Hardening for security mostly boils down to do the following: 

  1. Agreeing on what is the minimal set of configuration that qualifies as secure configuration. This is usually defined as a hardening benchmark or framework.
  2. Making changes to all the aspects of the system that are touched by such configuration.
  3. Measuring periodically if the application and system are still in line with the configuration or if there is any deviation.
  4. If any deviation is found, take corrective action to fix that. 
  5. If no deviation is found, log that.
  6. Since software is always getting upgraded, staying on top of the latest configuration guidelines and benchmarks is most important.

The three...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime