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
Hands-On Enterprise Automation on Linux

You're reading from   Hands-On Enterprise Automation on Linux Efficiently perform large-scale Linux infrastructure automation with Ansible

Arrow left icon
Product type Paperback
Published in Jan 2020
Publisher Packt
ISBN-13 9781789131611
Length 512 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
James Freeman James Freeman
Author Profile Icon James Freeman
James Freeman
Arrow right icon
View More author details
Toc

Table of Contents (23) Chapters Close

Preface 1. Section 1: Core Concepts
2. Building a Standard Operating Environment on Linux FREE CHAPTER 3. Automating Your IT Infrastructure with Ansible 4. Streamlining Infrastructure Management with AWX 5. Section 2: Standardizing Your Linux Servers
6. Deployment Methodologies 7. Using Ansible to Build Virtual Machine Templates for Deployment 8. Custom Builds with PXE Booting 9. Configuration Management with Ansible 10. Section 3: Day-to-Day Management
11. Enterprise Repository Management with Pulp 12. Patching with Katello 13. Managing Users on Linux 14. Database Management 15. Performing Routine Maintenance with Ansible 16. Section 4: Securing Your Linux Servers
17. Using CIS Benchmarks 18. CIS Hardening with Ansible 19. Auditing Security Policy with OpenSCAP 20. Tips and Tricks 21. Assessments 22. Other Books You May Enjoy

Chapter 14 - CIS Hardening with Ansible

  1. The modules wrap up a whole set of shell scripting functionality, including the conditionals that would be required to ensure that the script only makes changes when required and can report back on whether the change was made and whether it was successful.
  2. There are several ways—you can run the entire playbook with the --limit parameter set, or you can use the when clause within the playbook to ensure that the tasks only run on given hostnames.
  3. Name your tasks after the benchmark (including the number) so you can easily identify what they are for. Also, include the level and scoring detail to make it easy to interpret and audit results from playbook runs.
  4. Tag the tasks as level1 and level2 accordingly, and then run the playbook with the --tags level1 parameter.
  5. The --tags parameter only runs tasks with the tags specified, whereas...
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