@night 1803 access accessdata active directory admissibility ads aduc aim aix ajax alissa torres amcache analysis anjp anssi answer key antiforensics apfs appcompat appcompatflags applocker april fools argparse arman gungor arsenal artifact extractor attachments attacker tools austin automating automation awards aws azure azuread back to basics backstage base16 best finds beta bias bitcoin bitlocker blackbag blackberry enterprise server blackhat blacklight blade blanche lagny book book review brute force bsides bulk extractor c2 carved carving case ccdc cd burning ceic cfp challenge champlain chat logs Christmas Christmas eve chrome cit client info cloud forensics command line computer forensics computername conference schedule consulting contest cool tools. tips copy and paste coreanalytics cortana court approved credentials cryptocurrency ctf cti summit cut and paste cyberbox Daily Blog dbir deep freeze defcon defender ata deviceclasses dfa dfir dfir automation dfir exposed dfir in 120 seconds dfir indepth dfir review dfir summit dfir wizard dfrws dfvfs dingo stole my baby directories directory dirty file system disablelastaccess discount download dropbox dvd burning e01 elastic search elcomsoft elevated email recovery email searching emdmgmt Encyclopedia Forensica enfuse eric huber es eshandler esxi evalexperience event log event logs evidence execution exfat ext3 ext4 extended mapi external drives f-response factory access mode false positive fat fde firefox for408 for498 for500 for526 for668 forenisc toolkit forensic 4cast forensic lunch forensic soundness forensic tips fraud free fsutil ftk ftk 2 full disk encryption future gcfe gcp github go bag golden ticket google gsuite guardduty gui hackthebox hal pomeranz hashlib hfs honeypot honeypots how does it work how i use it how to howto IE10 imaging incident response indepth information theft infosec pro guide intern internetusername Interview ios ip theft iphone ir itunes encrypted backups jailbreak jeddah jessica hyde joe sylve journals json jump lists kali kape kevin stokes kibana knowledgec korman labs lance mueller last access last logon leanpub libtsk libvshadow linux linux-3g live systems lnk files log analysis log2timeline login logs london love notes lznt1 mac mac_apt macmini magnet magnet user summit mathias fuchs md viewer memorial day memory forensics metaspike mft mftecmd mhn microsoft milestones mimikatz missing features mlocate mobile devices mojave mount mtp multiboot usb mus mus 2019 mus2019 nccdc netanalysis netbios netflow new book new years eve new years resolutions nominations nosql notifications ntfs ntfsdisablelastaccessupdate nuc nw3c objectid offensive forensics office office 2016 office 365 oleg skilkin osx outlook outlook web access owa packetsled paladin path specification pdf perl persistence pfic plists posix powerforensics powerpoint powershell prefetch psexec py2exe pyewf pyinstaller python pytsk rallysecurity raw images rdp re-c re-creation testing reader project recipes recon recursive hashing recycle bin redteam regipy registry registry explorer registry recon regripper remote research reverse engineering rhel rootless runas sample images san diego SANS sans dfir summit saturday Saturday reading sbe sccm scrap files search server 2008 server 2008 r2 server 2012 server 2019 setmace setupapi sha1 shadowkit shadows shell items shellbags shimcache silv3rhorn skull canyon skype slow down smb solution solution saturday sop speed sponsors sqlite srum ssd stage 1 stories storport sunday funday swgde syscache system t2 takeout telemetry temporary files test kitchen thanksgiving threat intel timeline times timestamps timestomp timezone tool tool testing training transaction logs triage triforce truecrypt tsk tun naung tutorial typed paths typedpaths uac unc understanding unicorn unified logs unread usb usb detective usbstor user assist userassist usnjrnl validation vhd video video blog videopost vlive vmug vmware volatility vote vss web2.0 webcast webinar webmail weekend reading what are you missing what did they take what don't we know What I wish I knew whitfield windows windows 10 windows 2008 windows 7 windows forensics windows server winfe winfe lite wmi write head xboot xfs xways yarp yogesh zimmerman zone.identifier

Super Sunday Funday Forensic Challenge - Update 3

Current Contest


Six people are made it to Level 4, and only one has passed it and moved on to Level 5. Level 5 remains unsolved but that may not last long as our leading contender is really flexing his forensicator muscles on this one. For anyone frustrated please know that these challenges are made to be difficult and really push you. With a prize as good as a $5,000 class its hard to ask for anything else!

If you have questions I am planning to be in #dfir on irc.freenode.net on 9/11, 9/12, 9/15 and 9/16. If you have questions get an IRC client and come ask them. I may be on during the evening weekends but no guarantee to do so. Other players are in the channel though and you are welcome to talk amongst your selves.

For those of you not playing, or looking for a break here is some more good information.

Learn Windows Forensics from me!

I'll be co-teaching SANS FOR408 with Rob Lee in Ft. Lauderdale, FL at DFIRCon East Nov 3rd-8th 2014. If you want to spend a week learning everything you can about Windows forensics, and nights going deeper into the artifacts/structures if you want, I can't wait to meet you. As a bonus SANS has put out a $400 coupon for the event, go here to claim it.

Solutions to the past contest

Something I have not posted that I've been promising is the answers to the last 5 stage challenge. Let's continue that now. 

Stage 3 Question:
You have determined the remote IP address of the attacker, identified the process they injected and when they loaded into memory. Please list those sources available on most large networks where you could determine the following:

1. What quantity of data was sent to an ip address
2. The earliest known time traffic was seen to an ip address
3. What other ips are sending traffic to an ip address
4. Who all has queried a DNS address
5. How to impair the attacker's ip address from successfully ex-filtrating dat
Stage 3 Answer from a winner: 
1. What quantity of data was sent to an ip address:
We use Netwitness at my firm to keep metadata from the packet captures that Netwitness does.  I wrote a Python script to key off the group number for a session and build a key: value dictionary off that group number, then put that dictionary into an Excel friendly format with headers for the 40+ fields captured by Netwitness.  That would allow me to filter my Excel sheet from whatever months of Netwitness logs I parsed with my script for the destination IP address then sum the size column.

2. The earliest known time traffic was seen to an ip address
I would like to think I could query that information in the REST API for netwitness. I don’t honestly have an account on our netwitness UI yet.  I ask someone in the SOC to send me logs for whatever timeframe I need at this point, and for whatever servers etc.  If that could not be queried in the REST query from the Netwitness UI, then I would ask for the logs for as many months as I could and filter to the destination IP, then sort by timestamp to find the earliest incident. 

3. What other ips are sending traffic to an ip address:
I could still do this with the Netwitness metadata logs parsed into Excel by my script.  If there were a lot of source IPs sending data to a particular destination IP though I would probably want to break away from Excel and Grep for lines that have the destination IP, then sort uniq for the source IP’s and output them to a text file. 

4. Who all has queried a DNS address
This question would be best handled by proxy logs.  It would be a nightmare to search my entire firm’s proxy logs for users looking up a particular web address, but it could be done.  I watched Phil Hagen’s webcast on Logstash+Kibaba+Elastisearch and that seemed like a really elegant solution for ingesting proxy logs to show visits to addresses. It can be used to filter down for information for the GETS and POSTS, to determine what level of sites a user is visiting, and if there is the same type of activity happening for visits to those sites.

5. How to impair the attacker's ip address from successfully ex-filtrating data 
Firewall rules can be put into place for blocking the IP.  Proxy filters can be set with the IP as blacklisted.  The IPS can be set with a rule against that IP. 

The only answer I needed:
In this question I was looking for a lot. An understanding of what default network sources would be available in a normal network and how to use that data to answer the questions. 

Post a Comment

[blogger][disqus][facebook][spotim]

Author Name

Contact Form

Name

Email *

Message *

Powered by Blogger.