Operations

7/13/2016
04:30 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Purple Teaming: Red & Blue Living Together, Mass Hysteria

When you set focused objectives for the red team, you get your blue team to work the weak muscles they need trained most.

Red teams beat up on blue teams all the time. However, while there can be plenty of sore muscles on both sides, they're not always the muscles that needed the most exercise: security teams don't always learn as much from the bruising and battering as they could. Enter "purple teaming" -- an exercise in which every bruise and muscle strain has a purpose.

In a purple team exercise, the red team's objective is to test the effectiveness of a specific security control or to challenge the blue team on a specific skill set. The objective would usually be set by someone who is familiar with the security team's needs -- an incident response manager, CISO, or security operations director. 

Chris Gates, senior incident response engineer at Uber, and Haydn Johnson, senior consultant of KPMG Canada, will outline the ins and outs of the technique Oct. 18 at SecTor Canada in their session, "Purple Teaming the Cyber Kill Chain: Practical Exercises for Management."  

"The mindset is about working together," says Johnson. He likens it to sparring with a partner instead of merely shadowboxing in a mirror. It's also better than getting into a street fight.

Gates says the idea appealed to him because after years of being on the red team side and watching most blue teams fail to improve their defenses even after an exercise, he'd become disillusioned with his role.    

"I wanted to be a fixer instead of a breaker," he says.

Johnson and Gates gave a few examples of how purple teaming can be used: If an organization has implemented ways to limit the effectiveness of Mimikatz, for example, the red team's efforts would focus on trying to run Mimikatz. If the sec ops director wants his or her team to have practice responding to a malware attack on a corporate device on corporate wifi, the red team would build their attack accordingly. Generally, the blue team would not be informed ahead of time, and they approach the event as a real incident.

Purple teaming does not need to be a Herculean endeavor; it merely needs to accomplish the particular objective. At Uber, Gates says, the exercise might be an "active adversarial simulation," but it might also just be a controlled test or a table-top exercise. If the goal is simply to test the effectiveness of a security tool, Johnson and Gates explain, a purple team exercise may be as simple as an attempt to get a malicious email past the mail proxy. 

Another key part of purple teaming is what happens after the exercise: both red and blue teams share information about their experiences -- the attacks, the alerting and instrumentation, the detection and response procedures. The goal of a blue team vs. red team exercise in this case is ultimately to make the organization better, not to be adversarial. 

By purple teaming, "I get to see what my attacks look like on the other side, which makes me a better attacker," Gates says. 

You might think that this takes giant squadrons of people and months of planning. Johnson and Gates say it needn't be that way: One or two internal people, plus consultants as necessary, can get the job done.  

Gates says, though, that while purple teaming doesn't need a big team, it does need a mature team. An immature security organization won't have the knowhow to set the objectives and "know where the gaps in knowledge are."

"I don't think you can do it with a one-man shop" without consultants, Gates says.

Though they wouldn't go quite as far as to say that purple teaming would save an organization money, Gates and Johnson say purple teaming lets them put time and money where it's most needed in an organization. 

Related Content:

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
MichaelS90701
50%
50%
MichaelS90701,
User Rank: Apprentice
7/14/2016 | 8:20:32 AM
This isn't new
This concept has been around for several years. Mark Kikta was on of the pioneers of the concept in his BSides Jackson talk in 2013 and Dave Kennedy has been speaking about it fit several years, At least one company uses it in their business model, since the own trademark on the term, while several others use the actions of purple teaming in their business model. A quick Google search of the term Purple team will show some examples of Mark and Daves talks. Just saying, the article makes it sound like Gates and Johnson pioneered this concept and they did not. While a very relevant talk, this would be better served delving into the history behind it, I'd recommend contacting both Mark and Dave for background.
WebAuthn, FIDO2 Infuse Browsers, Platforms with Strong Authentication
John Fontana, Standards & Identity Analyst, Yubico,  9/19/2018
NSS Labs Files Antitrust Suit Against Symantec, CrowdStrike, ESET, AMTSO
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/19/2018
Turn the NIST Cybersecurity Framework into Reality: 5 Steps
Mukul Kumar & Anupam Sahai, CISO & VP of Cyber Practice and VP Product Management, Cavirin Systems,  9/20/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Are you sure this is how we get our data into the cloud?
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14633
PUBLISHED: 2018-09-25
A security flaw was found in the chap_server_compute_md5() function in the ISCSI target code in the Linux kernel in a way an authentication request from an ISCSI initiator is processed. An unauthenticated remote attacker can cause a stack buffer overflow and smash up to 17 bytes of the stack. The at...
CVE-2018-14647
PUBLISHED: 2018-09-25
Python's elementtree C accelerator failed to initialise Expat's hash salt during initialization. This could make it easy to conduct denial of service attacks against Expat by contructing an XML document that would cause pathological hash collisions in Expat's internal data structures, consuming larg...
CVE-2018-10502
PUBLISHED: 2018-09-24
This vulnerability allows local attackers to escalate privileges on vulnerable installations of Samsung Galaxy Apps Fixed in version 4.2.18.2. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exist...
CVE-2018-11614
PUBLISHED: 2018-09-24
This vulnerability allows remote attackers to escalate privileges on vulnerable installations of Samsung Members Fixed in version 2.4.25. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists wit...
CVE-2018-14318
PUBLISHED: 2018-09-24
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Samsung Galaxy S8 G950FXXU1AQL5. User interaction is required to exploit this vulnerability in that the target must have their cellular radios enabled. The specific flaw exists within the handling of ...