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

Data sources of interest

There are obviously many different data sources that could be interesting to integrate, and they depend on each organization's activity, specific use cases, and risk appetite. A key point to mention is that throughout our experience, we have often seen that companies spent months (even years) adding each and every data source within their SIEM. To caricature the approach, let's collect everything and we'll see what we do with the data later. More specifically, companies usually tend to focus on bias risk analysis, which identifies the most critical assets, that is to say, the crown jewels, in order to create detection rules. It often ends up with complex integration and low-value detection use cases. Of course, it might work with the necessary resources (staff, budget, and time) but might still not focus on what real threats would be doing. Indeed, risk assessment very often doesn't leverage cyber threat intelligence (CTI) inputs as it should...