Purple teaming Cyber Kill Chain

@haydnjohnson @carnal0wnage
Purple Teaming the
Cyber Kill Chain
Practical Exercises for Management Everyone

whoami

Chris Gates - Sr. Incident Response Engineer - Uber Inc.
Twitter: @carnal0wnage
Blog: carnal0wnage.attackresearch.com
Talks: slideshare.net/chrisgates

Haydn Johnson - Security Consultant - “Researcher”
Twitter: @haydnjohnson
Talks: BsidesTO, Circle City Con, BsidesLV
Big 4 experience
http://www.slideshare.net/HaydnJohnson

Overview
1.  Terminology for our discussion
2.  Explain this Cyber Kill Chain (CKC) thing
3.  Use CKC to plan possible Purple Team exercises
4.  Purple Team Story Time

Terminology

Terminology
Vulnerability Assessment Person - Run Vuln Scanner….hey client you
suck
Penetration Tester - Metasploit /MSF PRO (FTW)...hey client you suck
Red Teaming - Phish, move laterally, find “sensitive stuff”, maybe
custom implant...hey client you suck
Purple Teaming - You did all the above, but got to charge for an extra
body and to tell the client how they suck in person

No Really...
Red Teaming -
“Red Team engagements are the full spectrum warfare of
security assessments. In a red team engagement, the
consultants attack the client organization using physical
means, social engineering, and technological avenues. “
From: http://winterspite.com/security/phrasing/

@haydnjohnson @carnal0wnageFrom: Chris Nickerson Lares Consulting

You can’t Red Team yourself
But you sure as hell can conduct training...and detection/protection validation
http://redteamjournal.com/red-teaming-laws/

Purple Team Process

No Really...
Purple Teaming -
Conducting focused pentesting (up to Red Teaming) with
clear training objectives for the Blue Team.
It isn't a "can you get access to X" exercise it is a "train the
Blue Team on X" exercise. The pentesting activities are a
means to conduct realistic training.
More here: http://carnal0wnage.attackresearch.com/2016/03/more-on-purple-
teaming.html

Purple Teaming Process
Training Exercise!
1.  Primary result of the exercise is to create an intrusion
event (aka get caught) to test instrumentation (host/
network), validate detection processes and procedures,
validate protections in place, force response procedures
and post mortems.
Differs from Red Team where primary goal is to NOT get
caught

Purple Teaming Process
Training Exercise + work the IR process
Investigate Logging vs Alert + action
○  Is the event logged at all?
○  Logged event != alert
○  Does alert == action taken?
○  Purple Team it!

But I need ideas for scenarios!
https://github.com/kbandla/APTnotes https://github.com/aptnotes/

TRANSITION SLIDE
Handy transition slide

Pyramid of Pain
http://detect-respond.blogspot.com/2013/03/the-pyramid-of-pain.html https://www.youtube.com/watch?v=Mke74a9guNk

Lockheed Martin Cyber Kill Chain
Worst. Name. Ever.
“The seven steps of the Lockheed Martin Cyber
Kill Chain® enhance visibility into an attack and
enrich an analyst’s understanding of an
adversary’s tactics, techniques and
procedures.”
http://cyber.lockheedmartin.com/solutions/cyber-kill-chain

CKC is a great idea!
This is an integrated, end-to-end process described as a “chain” because
any one deficiency will interrupt the entire process.
AKA:
Any deficiency in the attackers chain, will interrupt the entire process

How to use CKC

Using the CKC to drive Exercises
http://csrc.nist.gov/cyberframework/framework_comments/20131213_charles_alsup_insa_part3.pdf

Using the CKC to drive Exercises
●  Rather than consolidate all attacker activities into a single
chart. We **could** create charts for various attack types
or CKC steps.
●  This would force us to identify and DOCUMENT an
organization’s methods to Detect, Deny, Disrupt, Degrade,
Deceive & Contain (Destroy) for any attack type.
●  As an added bonus, it creates Purple Team exercises for
us when we create a plan to validate the info in the chart.

Example Attack Types
https://attack.mitre.org/wiki/Main_Page
W
I
N
D
O
W
S

https://attack.mitre.org/wiki/Main_Page

Mimikatz Example
●  Mimikatz affects almost all organizations
●  Outline your defenses against the tool
○  AV
○  Md5
○  Command line usage
○  Code certificate details
○  Windows Hardening
○  Detection (via ATA)
●  https://adsecurity.org/?page_id=1821

Mimikatz Example

Mimikatz Example
Purple Team
●  Pack, Recompile, Sign with different code sign certificate
●  Powershell mimikatz
●  Various whitelist bypass techniques
●  Validate
○  Protected User Groups
○  LSA Protection
○  Registry changes prevent wdigest clear text
○  Alerting!

Lateral Movement Example
●  We could attempt to document every Lateral Movement
tool / technique
●  Instead focus on how you detect/protect/respond to a tool
or suite of tools
○  Ex: impacket

Lateral Movement -- impacket-psexec.py
Place holder for lateral movement example

Lateral Movement Example
Purple Team
●  Run impacket.py in default config
○  Did you detect it?
○  Tweak detection/deny/etc until you do!
●  Let your Red Team modify impacket
○  Repeat the detect/deny process until the tool is
unusable in your org
●  Do your GPO settings prevent most use cases?

Malicious Attachments
●  Everyone employs’ some sort of malicious attachment
protection
○  Google mail for business
○  Office 365
○  Proofpoint
○  FireEye
●  Do you test it? Or do you just hope for the best?

https://github.com/carnal0wnage/malicious_file_maker

Purple Team
•  Send various types of malicious attachments via multiple
sources
•  Compare to your chart of assumptions
•  How many emails does it take to block a sender?
•  What types of attachments generate alerts?
•  Does suspicious stuff get moved to spam or deleted; do people open spam
emails?
•  If sent to employees, do they report?
•  Did any automated actions take place?

CKC Exercise Outcomes
●  Mental exercise of how we Detect/Respond/etc to attacks
●  Document defense posture
●  Answer the “Do the Blinky Boxes work?” question
The Purple Team component
●  Validate the spreadsheet is accurate
●  Validate the blinky box is doing “something”
●  Identify training and coverage gaps for the org
○  Test plan for the above

CKC Exercise Outcomes
●  ITERATIVE PROCESS
○  Starts as simple detection validation exercises
○  Based on maturity, moves into gap analysis/detection
evasion by your attack team
○  You build up to Red Teaming
●  Does what we have for detection/protection work?
○  Then how easy is it to bypass
○  Track last test date, drive exercises and training

Story Time #1
Privilege
Escalation
Assume
Breach
Meterpreter
C2
Exfiltration -
FTP
“Red Team” @ $canadian Bank

Story Time #1
•  Receive call “Check this IP address”
•  $secretpoliceinvestigation
•  IP address seen - Investigators go to meeting + lunch
•  2 hours later, identify data exfil
•  Sh*t hits fan
•  Log into FTP server to delete data
•  Execute processes
Alerts triggered purposely

Story Time #1
Debrief
Red TeamBlue Team
What we saw
What was done
The
GAP
Improvements==

Story Time #1
•  Process not as effective as
it looks
•  Road Blocks in
communication
Lessons learned

Story Time #1
•  Process bypassed
•  Hard to collaborate
•  Rotating Shifts
Lessons learned

Story Time #1
•  IR equipment == slow
•  Infrastructure out of date
Lessons learned

Story Time #1
•  Big company hard to change quickly
•  Issues clearly acknowledged
•  Long term plans
Nothing changed in short term

Story Time #1
•  Create defined and clear process for hierarchy
•  Training on hacking back - DON’T
•  Budget for prioritized upgrade of Lab
•  Shift style lunches
Solutions

Story Time #1
•  Better equipment
•  Better processes
•  Better security culture
•  Better collaboration
2nd time around

Story Time #1
•  Faster detection
•  Faster containment
•  Faster win
2nd time improvements

The Point
•  What you think works, probably doesn’t
•  Test it
•  Humans will be humans, including your Blue Team

Story Time #2
•  IR Manager had identified some gaps plus had new incident
responders
•  Mobile Forensics
•  Response to Golden Ticket attack
•  Work thru IR process as a team
•  Fully internal -- No external Contractors
•  Partnered with senior Blue Team member
•  Took things I found pentesting…chained together story for the
exercise
•  “Create internal havoc” attackers
Overview of a Purple Teaming Exercise

Story Time #2
SMS Phish**

Story Time #2

Purple Bucket

So the take away!

Please remember:
•  Document your defenses and protections
•  Find a way to (iteratively) build your attacks/validation
•  Start simple, grow to more complex attacks/scenarios
•  Pwn all the things...but in a way that helps your
organization

Purple teaming Cyber Kill Chain

More Related Content

Purple teaming Cyber Kill Chain