Book Image

Cloud Security Automation

By : Prashant Priyam
Book Image

Cloud Security Automation

By: Prashant Priyam

Overview of this book

Security issues are still a major concern for all IT organizations. For many enterprises, the move to cloud computing has raised concerns for security, but when applications are architected with focus on security, cloud platforms can be made just as secure as on-premises platforms. Cloud instances can be kept secure by employing security automation that helps make your data meet your organization's security policy. This book starts with the basics of why cloud security is important and how automation can be the most effective way of controlling cloud security. You will then delve deeper into the AWS cloud environment and its security services by dealing with security functions such as Identity and Access Management and will also learn how these services can be automated. Moving forward, you will come across aspects such as cloud storage and data security, automating cloud deployments, and so on. Then, you'll work with OpenStack security modules and learn how private cloud security functions can be automated for better time- and cost-effectiveness. Toward the end of the book, you will gain an understanding of the security compliance requirements for your Cloud. By the end of this book, you will have hands-on experience of automating your cloud security and governance.
Table of Contents (15 chapters)
Title Page
Packt Upsell

Chapter 7. Private Cloud Security

In the first chapter, we learned about the different types of cloud, which are private, public, and hybrid.

A private cloud is a type of cloud that is deployed for any organization for their internal use. A private cloud is intended to enable the organization to have a self-service, elastic, and scalable model of IT infrastructure and services.

Prior to the private cloud, organizations used to host their applications either on bare metal servers or in a virtualized environment. Bare metal or virtualized environments lacked self-service features; however, scaling and elasticity could be achieved, but with great expenses in terms of human operations.

Making the environment fault tolerant and decoupled was still a challenge. For a development organization, where different technology groups are busy in development operations, it was a very difficult and a time-consuming task to provide the organization and keep track of infrastructure to run their staging and production...