6/1/2014flocon 2009, scottsdale, az. dod disclaimer 6/1/2014flocon 2009, scottsdale, az this...

17
06/22/22 FLOCON 2009, Scottsdale, AZ

Upload: dillan-cullom

Post on 28-Mar-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 2: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

DoD Disclaimer

04/10/23 FLOCON 2009, Scottsdale, AZ

This document was prepared as a service to the DoD community. Neither the United States Government nor any of their employees, makes any warranty, expressed or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial products, process, or service by trade name, trademark manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government. The opinions of the authors expressed herein do not necessarily state or reflect those of the United States Government, and shall not be used for advertising or product endorsement purposes.

Page 3: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Outline Objective Previous work Approach Framework Future work Acknowledgements

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 4: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Objective Design a framework that:

Accurately auto-labels and captures full packet / flow level data sets from different classes of cyber defense exercises

Produces data sets that are of value to the intrusion detection and or security community

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 5: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Previous WorkDARPA IDEVAL DATA SETS

ProsWell-known, publicly-available data set for repeatable

intrusion detection experimentationFairly rich emulation of live network trafficWell-documented and well-controlled data sets

ConsThe included threats and protocols are showing their ageModest traffic rate and network size, discrete attack eventsStatistical artifacts exploitable by anomaly detection

NoteThis work is not intended to replace the IDEVAL data sets,

but to explore techniques to provide additional resources for researchers and developers

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 6: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Approach Survey opportunity

What aspects of a data sets are of value to researchers

Design frameworkObjectivesRequirements

Implement framework○ USMA Internal Cadet Cyber Defense Exercise (March)○ Inter-Service Academy CDX 2009 (April)

Package and share data Analyze data Gather feedback Repeat

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 7: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Variety of Cyber Defense/Offense Exercises The framework must be robust enough,

and generic enough, to ensure that it can be applied to most CND/CNO exerciseInter-military service Cyber Defense Exercise

(Defend only)DEFCON Capture The Flag (Attack Only)Colligate Cyber Defense Exercise (Defend Only)Intra-USMA Cadet Cyber Warfare Exercise

(Mixed)

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 8: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Design Framework Objectives (What do we want out of our data

captures)Recorded traffic from multiple sensor locationsAttack event labelingNetwork, host and service status information

Exercise reportsNetwork and host configuration change logHost-base LOGSExercise IDS Alert DB or logs

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 9: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Design Framework Requirements (what do we need in

order to meet our objectives)Complete recordings of traffic at sensor

locationsAccurate description, source, destination

and timing of Red Cell attack eventsRecording of network, host and service

status

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 10: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Abstract Network Design

Placement of network ‘taps’ is critical when evaluating the type and amount of data capturedAre we only interested in the attacks?Are we interested in the attacks and

resulting traffic?Are we interested in flow patterns without

regard to type of traffic?

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 11: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Limitations and Concerns One of the biggest concerns is to not

impact the exercise/game in any wayNeed to have the monitoring boxes and network

config completely invisible to the participantsLimited number of monitoring boxes means that

there may data loss from unmonitored portions of the network

Human recording is needed to know exactly what malicious events were occurring at what times○ We cannot guarantee that every event will be

recorded

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 12: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Abstract Network Design

04/10/23 FLOCON 2009, Scottsdale, AZ

End User Space

DMZ

Internet

VPN

“Red Hosts”Computers sendingOnly malicious traffic

(count: 1 to N)

Network DataCapture Tap

VPN

Border Router

Network DataCapture Tap

Border Router

Network DataCapture Tap

Internal Router(count: 1 to N)

Network DataCapture Tap

SPAN Encompassing all VLANs

SPAN Encompassing all VLANs

SPAN Encompassing all VLANs

Page 13: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Network Design – CDX 2008 Example

04/10/23 FLOCON 2009, Scottsdale, AZ

Internet

VPN

1 or more ComputersSending only malicious

Traffic.“Red Hosts”

Network DataCapture Tap

VPN

Border RouterUsing NAT/PAT

Network DataCapture Tap

Border Router

Network DataCapture Tap

Internal RouterUsing NAT/PAT

DMZ Server

DMZ Server

Lariat Traffic Generators(count: 3)

End User Workstations

Network DataCapture Tap

VLAN-X

VLAN-Y

VLAN-Z

SPAN Encompassing all VLANs

SPAN Encompassing all VLANs

Page 14: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Software Implementation Network taps (capturing boxes) will be

running FreeBSD 7.1○ Will be using tcpdump with the capturing

interface in promiscuous mode to dump traffic directly to 1 Gigabyte files

○ Will capture during the entire exercise

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 15: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Hardware Implementation

4Data Capture Nodes:Dual-CPU (Intel Xeon 2.33 GHz)24 GB RAM (DDR2-667)1 .5 TB RAID-5

Will be at the listening end of a one-way Ethernet cable

That Ethernet cable will be plugged into a spanned port on a Cisco switch to allow monitoring of all traffic in all VLANs

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 16: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Future Work

Package and share data Community analysis Gather feedback Adjust Framework according to

feedback Repeat

04/10/23 FLOCON 2009, Scottsdale, AZ

Page 17: 6/1/2014FLOCON 2009, Scottsdale, AZ. DoD Disclaimer 6/1/2014FLOCON 2009, Scottsdale, AZ This document was prepared as a service to the DoD community

Conclusion

Need for revitalized IDEVAL data sets A number of existing opportunities to

capture data Proposed framework to capture and

label relevant Data Infuse into existing IDEVAL data sets

04/10/23 FLOCON 2009, Scottsdale, AZ