SCYTHE Purple Team Exercise Framework
SCYTHE Purple Team Exercise Framework
SCYTHE Purple Team Exercise Framework
Exercise Framework
Goals 3
Methodology 3
Preparation 12
Logistics 12
Target Systems 13
Security Tools 13
Target Accounts 13
Attack Infrastructure 14
External Infrastructure 14
Internal Infrastructure 14
Red Team Preparation 14
Blue Team Preparation 15
Exercise Execution 16
Kick Off 16
Exercise Flow 16
Tracking Exercise 17
Lessons Learned 18
Tracking Action items 18
Retesting 18
About SCYTHE 18
● Cyber Threat Intelligence - analyst and team that creates Cyber Threat Intelligence
● Red Team - offensive team in charge of emulating adversaries
● Blue Team - the defenders. Security Operations Center (SOC), Hunt Team, Digital
Forensics and Incident Response (DFIR), and/or Managed Security Service Provides
(MSSP)
While Red Team Engagements are considered “zero knowledge” engagements, where Blue
Teams are unaware of the adversary emulation prior to or during the engagement, a Purple
Team Exercise is a full knowledge engagement where the attack activity is exposed and
explained to the Blue Team as it occurs. Purple Team Exercises are "hands-on keyboard"
exercises where Red and Blue teams work together with an open discussion about each attack
technique and defense expectation to improve people, process, and technology in real-time.
Purple Team Exercises are Cyber Threat Intelligence led, emulating Tactics, Techniques, and
Procedures (TTPs) leveraged by known malicious actors actively targeting the organization to
identify and remediate gaps in the organization’s security posture.
At a high level, a Purple Team Exercise is executed with the following flow:
1. Cyber Threat Intelligence, Exercise Coordinator, or Red Team presents the adversary,
TTPs, and technical details
2. Attendees have a table-top discussion of security controls and expectations for TTP
3. Red Team emulates the TTP
4. Blue Team (SOC and Hunt team) and DFIR analysts follow process to detect and
respond to TTP
5. Share screen if TTP was identified, received alert, logs, or any forensic artifacts
6. Document results - what worked and what did not
7. Perform any adjustments or tuning to security controls to increase visibility
8. Repeat TTP
9. Document any feedback and/or additional Action Items for Lessons Learned
10. Repeat from step 1 for next TTP
Methodology
Purple Team Exercises follow similar methodologies as zero-knowledge Adversary Emulations.
Purple Team Exercises are Cyber Threat Intelligence led, emulating Tactics, Techniques, and
Procedures (TTPs) leveraged by known malicious actors actively targeting the organization to
identify and remediate gaps in the organization’s security posture. The following methodology is
a good starting point for the development of a Purple Team Program and useful for Purple
Team Exercises and Continuous Purple Teaming Operations.
Sponsors
Management from all participating functions must approve and support the Purple Team
Exercise, including the goals, budget, and scope prior to any additional work in the Preparation
or other phases of the exercise. Following management approval, operational managers must
provide approval as operations will most likely be impacted during the exercise period; analysts
that have daily work duties will need to be focused on the exercise. Operational managers are
responsible for choosing exercise attendees from their teams and removing daily obligations
from those individuals during the exercise period.
Red Team
The Red Team is required to complete a number of responsibilities during the preparation
phase and be active during the Exercise Execution. Preparation is similar to the amount of time
dedicated to the planning phase of a zero-knowledge Red Team Engagement. Operational
manager(s) should remove other tasks from Red Team members for successful preparation.
Organizations that do not have a Security Operations Center and leverage Managed Security
Service Providers (MSSP) can also perform Purple Team Exercises. It will require planning and
approval from the MSSP to ensure they approve participation in the exercise.
The type of Cyber Threat Intelligence needed for performing Adversary Emulation and our
Purple Team Exercises are at the top of the Pyramid of Pain:
● Tactics, Techniques and Procedures (TTPs): How the adversary goes about
accomplishing their goals, from initial access all the way through exfiltration and impact.
Here is where we can map to MITRE ATT&CK.
● Tools: Software used by the adversary to accomplish their goals. These may be custom
malware, open source tools, or tools that come with the systems (often referred to as
Living of the Land). A great list of Command and Control frameworks and tools is
available at The C2 Matrix.
● Host Artifacts: Observables caused by adversary activities on one or more hosts.
Examples can be registry keys and values, files or directories, and/or services that are
created or modified.
Extract TTPs
At this step, the Cyber Threat Intelligence analysts should extract TTPs from the Threat
Intelligence acquired and map it to a framework like ATT&CK, the industry standard to identify
and document common TTPs of adversaries. Tactics, Techniques, and Procedures are often
abbreviated as TTPs and clustered together as one thing: “The adversary’s TTPs.” However,
they represent three different aspects of adversary activity at different levels of abstraction.
Tactics are high-level methods to achieve a goal (e.g. Initial Access, Exfiltration). Techniques
and sub-techniques (introduced in July 2020) are one step down that refer to how that goal will
Tactic Description
MITRE has developed the ATT&CK Navigator, a web application that represents the ATT&CK
techniques in a dynamic fashion. It can be used to select specific techniques based on a threat
group or software, after which modifications and annotations can be made. It may have TTPs
assigned to an adversary that was not provided in the Cyber Threat Intelligence. Note that the
techniques for Groups/Software in Navigator are fully referenced to open sources on MITRE
ATT&CK Groups and Software pages. Navigator is open-source and can be self-hosted.
A management level meeting should occur to cover what controls are expected for those TTPs
and which teams should have visibility of the TTP activity. TTPs chosen for the exercise should
be classified as follows:
● TTPs that are not blocked or prevented - these will provide little value in the exercise but
could be emulated if the TTP needs to be highlighted as a concern
● TTPs that may be logged - these are ideal to train hunt teams and have detection
engineers create better detection and alerting
● TTPs that may be alerted - these are ideal to train SOC analysts to action and test
defensive processes.
Examples of Adversary Emulation Plans are available from the following resources:
● SCYTHE Community Threats Github
● Mordor project has multiple plans
● MITRE ATT&CK Adversary Emulation Plan for APT3
● MITRE ATT&CK Adversary Emulation Plan for APT29
Logistics
Once attendees have been chosen, logistics planning can begin. Determining the appropriate
location for Purple Team Exercises is critical to the preparation time as travel can be a deciding
factor in exercises moving forward. The ideal location is generally SOC locations where SOC,
Hunt Team, and/or Digital Forensics and Incident Response analysts are present. If travel is not
possible, Purple Team Exercises can be performed remotely through video conferencing.
Choose a video conferencing solution that fits your threat model. Note that various attack
techniques that
Standard processes should be followed to obtain travel approval, which should be completed at
least a month prior to the Purple Team Exercise to ensure all required attendees are approved.
Exercise attendees should plan to arrive the day before the kick off to ensure timely arrival to
the exercise environment.
One dedicated conference room with sufficient space for all attendees, sponsors and observers
and their equipment is required for the length of the week. Moving spaces throughout the week
will delay exercise activity as technology must be retested and attendees may not easily find the
new location. A training room may be leveraged as the exercise location but sharing every
screen with a projector or TV will not be as efficient as with the technology in conference rooms.
Every attendee should arrive with a workstation with media output to quickly show the current
screen to other participants (HDMI, DVI, and VGA). If being done remotely, screen sharing
should be trivial with the selected video conferencing solution.
Based on the approved goals and TTPs, the target systems may be requested following normal
process to ensure consistency with production systems:
Security Tools
Request the target systems have standard, production security tools deployed in the
organization:
● Anti-Virus/Anti-Malware/Anti-Exploit
● Endpoint Detection & Response (EDR)
● Forensic Tools
○ Image acquisition
○ Live forensics
● Ensure flow of traffic goes through standard, production network-based devices such as
firewalls and proxy logs
Target Accounts
Target accounts (a.k.a service accounts, functional IDs) should be created for logging into
systems, accessing proxies/internet, email, etc. and to ensure real production credentials are
not compromised during the Purple Team Exercise.
Attack Infrastructure
Red Team is responsible for establishing the Purple Team Exercise attack infrastructure
(internal or external dependent upon TTPs). This involves acquiring the tools that will emulate
the adversary behaviors and TTPs. SCYTHE is the industry leading Purple Team platform.
External Infrastructure
Internal Infrastructure
○ Sysmon
○ Processmon
● Video conference
● Presentation mode
● Attack Infrastructure accessible
● Target systems accessible
Kick Off
A Manager of one of the teams, or the CISO, should kick the Purple Team Exercise off by
stating the value Purple Team Exercises bring to resiliency while highlighting the progress made
due to previous Purple Team Exercises. The kick off should consist of a 10-15 minute
motivation speech that gains interest from attendees about the value of the work to be done in
the week ahead. The flow of the Purple Team Exercise should be presented.
Exercise Flow
1. Cyber Threat Intelligence, Exercise Coordinator, and/or Red Team presents the
adversary, TTPs, and technical details:
a. Adversary behavior
b. Procedure
c. Tool used
d. Attack Vector
e. Delivery Method
f. Privilege gained
2. Purple Team discussion of expected controls based on TTP
a. SOC: Any logs or alerts for this TTP
b. Hunt Team: Any Hunt Cases for this TTP
c. DFIR: Documented methods to identify if TTP was leveraged
3. Red Team executes the TTP
a. Provides attacker IP
b. Provides target
c. Provides exact time
d. Shows the attack on projector
4. SOC, Hunt, and DFIR follow process to identify evidence of TTP
a. Time should be monitored to meet expectation and move exercise along
5. Share screen if TTP was identified, received alert, logs, or forensics
a. Time to detect
Tracking Exercise
At least one dedicated Exercise Coordinator should be on site to take minutes, notes, action
items, and attendee or sponsor feedback. Daily emails should be sent to all attendees and
sponsors with minutes, action items, as well as what is planned for the next day. Tracking of the
TTPs can be done through a variety of ways:
● VECTR is a great, free solution for tracking and reporting Purple Team Exercises
● Detect Tactics, Techniques & Combat Threats (DeTT&CT)
An example of a Purple Team Exercise report is available at Defensive Origins Github. Other
resources include CyberWarDogs post “How Hot is Your Hunt Team”.
Retesting
The emulation may need to be performed a number of times, over and over, while the detection
engineers work to tune the defensive controls. SCYTHE is a platform that allows the consistent,
repetitive emulation of adversary behavior.
About SCYTHE
SCYTHE provides an advanced attack emulation platform for the enterprise and cybersecurity
consulting market. The SCYTHE platform enables Red, Blue, and Purple teams to build and
emulate real-world adversarial campaigns in a matter of minutes. Customers are in turn enabled
to validate the risk posture and exposure of their business and employees and the performance
of enterprise security teams and existing security solutions. Based in Arlington, VA, the
company is privately held and is funded by Gula Tech Adventures, Paladin Capital, Evolution
Equity, and private industry investors. For more information email [email protected], visit
https://scythe.io, or follow on Twitter @scythe_io.
Thank you to the reviewers and contributors of this document: Ben Goerz, Bryson Bort
(SCYTHE), Dave Mayer (GRIMM), Erik van Buggenhout (NVISO), Katie Nickels, Mauricio
Velazco, and Xena Olsen.