Book Image

Enterprise Cloud Security and Governance

By : Zeal Vora
Book Image

Enterprise Cloud Security and Governance

By: Zeal Vora

Overview of this book

Modern day businesses and enterprises are moving to the Cloud, to improve efficiency and speed, achieve flexibility and cost effectiveness, and for on-demand Cloud services. However, enterprise Cloud security remains a major concern because migrating to the public Cloud requires transferring some control over organizational assets to the Cloud provider. There are chances these assets can be mismanaged and therefore, as a Cloud security professional, you need to be armed with techniques to help businesses minimize the risks and misuse of business data. The book starts with the basics of Cloud security and offers an understanding of various policies, governance, and compliance challenges in Cloud. This helps you build a strong foundation before you dive deep into understanding what it takes to design a secured network infrastructure and a well-architected application using various security services in the Cloud environment. Automating security tasks, such as Server Hardening with Ansible, and other automation services, such as Monit, will monitor other security daemons and take the necessary action in case these security daemons are stopped maliciously. In short, this book has everything you need to secure your Cloud environment with. It is your ticket to obtain industry-adopted best practices for developing a secure, highly available, and fault-tolerant architecture for organizations.
Table of Contents (11 chapters)

Attaining the desired state with Ansible pull

We used to run Ansible pull across 500+ servers to maintain a consistent image across all servers. It happens many times that a system administrator flushes iptables if things are not working or stops OSSEC if it blocks scans.

This leads to a lot of unexpected configurations everywhere, and during an audit period, OSSEC may be disabled in a few servers from the past few weeks.

So, our entire hardening stack was based on Ansible pull that used to run at midnight on all servers. If there were any configuration changes, then Ansible would update it back to the original consistent state.

This is extremely useful and makes the auditors smile as well.

Auditing servers with Ansible notifications

...