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)
1
Part 1: Concept, Model, and Methodology
6
Part 2: Building a Purple Infrastructure
12
Part 3: The Most Common Tactics, Techniques, and Procedures (TTPs) and Defenses
14
Part 4: Assessing and Improving

Detection engineering and as code

Detection engineering is the art of building a detection approach and life cycle. It has many different names within the industry, from use case development to threat content development or detection content development. Even though there is no official definition of what detection engineering is, it seems that the community has adopted this terminology when it comes to developing detection rules. While the role of a detection engineer might be broader than just building detection rules (think about tuning and tweaking systems, developing tools, ensuring the quality of detections, and so on), we agree that it is one of its main focuses.

In this section, we will see the three main rule formats that are essential for a detection engineer to understand and master: SIGMA, YARA, and SNORT.

In the previous section, we saw the example of the HAFNIUM threat actor. We built queries using Splunk SPL, but obviously, we might have used other SIEM/log management...