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

Message queue 

Message queue is the backbone of OpenStack. It's used to provide interprocess communication in OpenStack. There are multiple message queuing services such as RabbitMQ and Apache Qpid.

RabbitMQ and Qpid both work on AMQP for interprocess communication. Message queue is used to decouple the architecture.

The best part about message queues in OpenStack is, after permitting queue access, there is no additional authorization check that happens. Services accessible using message queue only validate the token within the actual message payload. Here, one must consider the token expiration time. Because queues can be replayed and they also authorize other services in the infrastructure.

In the OpenStack message, signing is not available. For high availability configuration, one must have complete queue-to-queue authentication and encryption.

Now, let's see the way to secure the message queue or AMQP:

  • AMQP services such as RabbitMQ and Qpid both support TLS. So, we must enable TLS-based...