Book Image

Purple Team Strategies

By : David Routin, Simon Thoores, Samuel Rossier
Book Image

Purple Team Strategies

By: David Routin, Simon Thoores, Samuel Rossier

Overview of this book

With small to large companies focusing on hardening their security systems, the term "purple team" has gained a lot of traction over the last couple of years. Purple teams represent a group of individuals responsible for securing an organization’s environment using both red team and blue team testing and integration – if you’re ready to join or advance their ranks, then this book is for you. Purple Team Strategies will get you up and running with the exact strategies and techniques used by purple teamers to implement and then maintain a robust environment. You’ll start with planning and prioritizing adversary emulation, and explore concepts around building a purple team infrastructure as well as simulating and defending against the most trendy ATT&CK tactics. You’ll also dive into performing assessments and continuous testing with breach and attack simulations. Once you’ve covered the fundamentals, you'll also learn tips and tricks to improve the overall maturity of your purple teaming capabilities along with measuring success with KPIs and reporting. With the help of real-world use cases and examples, by the end of this book, you'll be able to integrate the best of both sides: red team tactics and blue team security measures.
Table of Contents (20 chapters)
Part 1: Concept, Model, and Methodology
Part 2: Building a Purple Infrastructure
Part 3: The Most Common Tactics, Techniques, and Procedures (TTPs) and Defenses
Part 4: Assessing and Improving

Enabling purple teaming with DevOps

Before heading straight into the DevOps theory, we'd like to highlight that Chapter 13, PTX – Automation and DevOps Approach, will be dedicated to applying the DevOps concept.

The DevOps concept is not only dedicated to applications and operations teams. If we want to start and build a modern and efficient software factory, we will need to think about security. All tools and security processes must be incorporated into the workflow from the beginning of the project. Before the emergence of the DevOps methodology, deployment cycles could take months, even years to complete one release or version. It was fine to include security testing at the end of the cycle. But these times are over with continuous integration and continuous delivery (CI/CD). Security must, therefore, be part of the integrated team during the whole development cycle. DevOps, and more recently DevSecOps, should be seen in a similar way to purple teaming. While it is...