Introduction

You know that security is important.

And whether your system is cloud native, has transitioned into the cloud with a traditional archi‐ tecture, or is just starting that journey, you know that the shift into the cloud has made security more complex than ever.

What’s more, security is now everyone’s job.

For decades, software development and delivery were slow pro‐ cesses.

Early enterprise software was delivered to customers by hand and installed by a trained technician.

Cloud providers have changed all that, leveraging economies of scale to offer capabilities that many organizations couldn’t achieve on their own and making it cheaper and easier to use virtualization technologies.

Fortunately, as more application hosting is outsourced to cloud pro‐ viders, the resulting changes have brought design, development, testing, deployment, and management teams closer together.

That’s important, because while virtualization offers fantastic opportunities and capabilities, it also means there are many more moving pieces than there used to be.

To handle that, not only do you need solid management capabilities—you also need automation.

In the cloud, automation is often referred to as orchestration, because there is one piece in the middle that has to keep all the ele‐ ments in tempo and on key.

Using a tool like Kubernetes to orches‐ trate the development, deployment, and runtime phases of containerized applications can help immensely with automating and scaling application delivery, but it’s not magic.

You’ll still need to bring together all of the groups involved in development, orchestra‐ tion, and deployment, because all of them will have different and important insights.

For example, when you introduce orchestration,