Hacker Tracking â A Case Study - Tracking Hackers

Recommendations

Info

Next Steps Create legal consensus on viability of this methodology for use in prosecuting hackers and organized criminal networks Assess practicality of international law enforcement cooperation Draft protective language for legitimate owners of repository systems Explore and deepen options of this type available to investigators
Conclusions We Exercised and Honed our skills The project gave us practical, real-world data to work with Created an environment that allowed us to hunt the hackers under realistic circumstances Out-of-Pocket costs in were minimal ($0 in our case) Total set-up time was minimal, approximately 10 man hours. Incident cost, in time, was significant. (20 plus man hours per incident).
Page 1 and 2: Hacker Tracking - A Case Study Gide
Page 3 and 4: What is a Research Honeypot? A syst
Page 5 and 6: The Servers Default but patched ins
Page 7 and 8: Network Traffic Monitoring SNORT Si
Page 10 and 11: Case Study Red Hat 6.2 System (the
Page 12 and 13: The log begins from: Nov 9 19:44:42
Page 14 and 15: lpd 6295 root cwd DIR 3,1 4096 8897
Page 16 and 17: lpd 6372 root 424u IPv4 26262 TCP *
Page 18: added:/usr/bin/kidz/emech-2.8.1/con
Page 22 and 23: #!/bin/sh clear echo "Educational p
Page 24 and 25: #!/bin/sh echo "+------------------
Page 26 and 27: ¡ Let's Find Him Things we know ab
Page 28 and 29: Modified 'install' script From: cat
Page 30 and 31: Following the Hacker
Page 32 and 33: Zombie Attacks Victim
Page 34 and 35: Victim Sends Email Notification to
Page 36 and 37: Attacker's Browser Contacts our Ser
Page 38 and 39: Embedded HTTP cgi calls Date: Wed,
Page 42: Thank You Gideon J. Lenkey, CISSP 1

Hacker Tracking â A Case Study - Tracking Hackers

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?

Hacker Tracking â A Case Study - Tracking Hackers