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

Rundeck initialization

It's very important to store our jobs in the right project from the beginning. All Rundeck projects are independent of each other. The main advantage of creating a different Rundeck is access management. For example, our organization manages multiples customers and we need to define an access policy between different teams:

  • Security Analysts: List and run all the jobs for the projects' customer XYZ
  • Security Engineers: Allowed to read, modify, and execute all the projects except for projects classified as internal
  • Security Architects: Allowed to read, write, and run all projects

Another benefit of splitting Rundeck into multiple projects is that an Ansible inventory is dedicated to each project. We want to ensure the security workflow will be run on the right customer infrastructure:

Figure 13.2 – Rundeck projects list

Here, we can see a project called Lab-Purple-Teaming that's in charge of...