1. Honeypots: Not Just for Pooh
By: Miranda Alicia Bryant
COSC5010 – Jim Ward
Spring 2006

2. “All Warfare is based on Deception.”
A Thought…
“All Warfare is based on Deception.”
Sun Tzu

3. Honeypots Defined:
A honeypot is defined as “A resource whose value is being attacked or compromised. This means, that a honeypot is expected to get probed, attacked, and potentially exploited.”
(Spitzer)

4. Categories of Honeypots
Low Interaction
Simple, basic services only
Medium Interaction
More services, database or server
High Interaction
Complicated, entire OS available

5. Why use them? Research Tool Hide Main Machines in a web of “fake” ones
Part of the Security Software

6. Hidden Dangers Zombie Machines More Fodder for Black Hats
Major Danger with High Interaction
More Fodder for Black Hats
Learn as much as Security Pro’s from reports
Ethical Dangers for users
How much information is collected?

7. Legal Issues Wiretap Act Pen/Trap Statute Loopholes
Governs phone lines
Pen/Trap Statute
Realm of collection of information that pertains to the world outside the phone lines

8. The Honeynet Project www.honeynet.org
Information collected “To learn the tools, tactics and motives involved in computer network attacks, and share the lessons learned.”
Three goals:
Awareness, Information, and Tools.

9. Examples of Honeypot Software
Low Interaction:
LaBrea Tarpit
Bubblegum
Medium Interaction:
Mwcollect
Honeybot
High Interaction:
Sombria
Bait n Switch

10. References Honeynet: www.honeynet.org
LaBrea Tarpit:
BubbleGum:
Honeybot:

11. References (cont) MWCollect: http://www.mwcollect.org/
Sombria:
BaitnSwitch: