31

Sh#3 incident forensics

Embed Size (px)

DESCRIPTION

Presentation about real life security

Citation preview

Page 1: Sh#3 incident forensics
Page 2: Sh#3 incident forensics
Page 3: Sh#3 incident forensics

RISK = IMPACT x PROBABILITY

Page 4: Sh#3 incident forensics
Page 5: Sh#3 incident forensics
Page 6: Sh#3 incident forensics

Source: OWASP Testing Guide (www.owasp.org)

Page 7: Sh#3 incident forensics
Page 8: Sh#3 incident forensics
Page 9: Sh#3 incident forensics

INCIDENT INVESTIGATIONLessons Learned

Page 10: Sh#3 incident forensics

Everyone wants to cover their ass

Page 11: Sh#3 incident forensics

Incidents happen when…

Page 12: Sh#3 incident forensics

ISV often have IT Infrastructure CHAOS

Page 13: Sh#3 incident forensics

Clients Like to Repeat Mistakes

Page 14: Sh#3 incident forensics

R&D Security“To serve and protect”

Page 15: Sh#3 incident forensics

Participants Inquiry

Page 16: Sh#3 incident forensics

Tools (general)Computer Aided Investigative Environment (CAIE), Amazon EC2, VMware vCenter, Cent OS Linux, dd, netstat, utmpdump, debugfs, stat, dbg, find, lsof, whois, nslookup, winscp, domain tools, Metasploit Framework, OpenVAS, skypelogview, ProcHeapViewer, MessengerPasswordDecryptor, Wireshark, outlookattachview, chromepass, FirePasswordViewer, Elcomsoft Distributed Password Recovery

Page 17: Sh#3 incident forensics

Classical Hack

Page 18: Sh#3 incident forensics

Who is guilty?

Page 19: Sh#3 incident forensics

Romanian Hacker

Page 20: Sh#3 incident forensics

?

Page 21: Sh#3 incident forensics

PART II: Workshop

Take Down Dr. Evil

Page 22: Sh#3 incident forensics

Story

Dr. Evil has been on the run for months since stealing sensitive information from his former employer Factory Made Winning Pharmaceuticals (FMWP) and creating an explosion in their labs to fake his own death. The body was never recovered and no evidence of his existence has surfaced … until now.

Page 23: Sh#3 incident forensics

The 1337 pill was going to be the company's new flagship drug.

Page 24: Sh#3 incident forensics

You are the Forensic Investigator hired to analyze the mobile network traffic.

Are you ready ?

Page 25: Sh#3 incident forensics

ROUND ONE: Flight Plans

Dr. Evil is planning his escape. We know he is using an mobile device with various applications. Investigators need to stay hot on his trail. Can you figure out his escape plan?

Page 26: Sh#3 incident forensics

1.1) What is the name of the application Dr. Evil used to search for flights? 1.2) What is the date of his first flight?1.3) What are the airport codes in order for each leg of Dr.Evil trip? (beginning with the originating airport and ending at his final destination ex. “aaa-bbb,bbb-ccc,ccc-ddd,ddd-eee”)

Page 27: Sh#3 incident forensics

210 HONOLULU349 0:A:SLC:LAX:DL:2241:Mar:20:2012:0:A:GEG:SLC:DL:4442:Mar:20:2012:delta.comPrice=841.59$AndroidKayak/5.0.1Android 4.0.3

HONOLULU

Page 28: Sh#3 incident forensics

ROUND TWO: Secret Meeting

Before Dr. Evil left for his flight, he had to take care of some business with a prospective buyer for the 1337 pill formula. This packet capture begins at the start of his trip and ends when he reaches his estimation.

Page 29: Sh#3 incident forensics

2.1) One time during his trip, the doctor used his mobile device to search for the name of his destination. What were his search terms? 2.2) At the moment that the doctor searched for the name of his destination, what were his GPS coordinates? 2.3) During the trip, Dr.Evil mobile device alerted him that he was within eight hundred meters of another person. Based on the alert in the packet capture, was this person male or female?2.4) At what time did Dr.Evil arrive at his destination (in UNIX epoch time)?

Page 30: Sh#3 incident forensics

376 TCPSamantha Female5077frame.time_epoch == 1331150170.516925000

Samantha

Page 31: Sh#3 incident forensics

Thank you for attention.

Questions?