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

Database services

In OpenStack, all of the services, such as nova, neutron, Keystone, and Cinder, use the database to store the state and configuration details.

So, it's very critical to ensure security of the database used for OpenStack. Currently, OpenStack supports MySQL and postures SQL database.

In OpenStack, all of the services use a single database to store the configuration and state. There is no such policy defined at the granular level access of the database. This means that all of the services which need database access have been granted access and privileges to the database.

So, the nodes, having access to the database, have full permission to execute any statement such as drop, update, and insert.

Now, in this situation, if any component is compromised, it can lead to a disaster. Now, to get rid of this situation, the following are the few steps one should take: 

  • Communication with the database is only allowed on the management network.
  • Enable TLS-based communication for the database...