@night 1803 access accessdata active directory admissibility ads aduc aim aix ajax alex levinson 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 lateral movement leanpub libtsk libvshadow linux linux forensics linux-3g live systems lnk files log analysis log2timeline login logs london love notes lznt1 mac mac_apt macmini magnet magnet user summit mari degrazia 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 sarah edwards 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 updates 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 winscp wmi write head xboot xfs xways yarp yogesh zimmerman zone.identifier

Daily Blog #526: Where are we going?

Hello Reader,
         A long day of flying but luckily I have inflight wifi. Today I wanted to point you to a tweet from Pasquale Stirparo


I have a dream where, in our community, everyone would stop building his/her own "yet another new" #FOSS tool to fix the same problem as may other already there, instead of joining forces and build fewer but better and longer term solutions. #FridayThoughts #DFIR #InfoSec

I wanted to talk about this because while there are exceptions to any generalization (in this case things like plaso, volatiloty, autopsy, reg ripper and more) there are many of us who are putting out one off tools that we develop to prove a concept or learn an artifact that then becomes abandonware over time , left for some examiner to find in the future hoping it will solve their issue.

I'm not here to criticize this method, I think I've done many times as have others who work with me, but I can see Pasquale's point. If we could work together to bring our tools and research into something that could be integrated and maintained long term everyone would benefit. You see this in these larger projects but eachbis purpose built for the needs of the users.

Plaso -timeline creation
Volatility - memory forensics
Reg ripper - registry analysis

The big exception i see is:
Autopsy - forensic suite

But autopsy is written in Java and uses ipython which means it's outside of whereany of us feel comfortable.

Our commercial vendors are trying hard (for the most part) to create solutions for us but they can't keep up with a worldwide community that finds new artifacts almost every day. So we need to figure out how we can work together to take advantage of the brain trust that's out there who through good code review and sample projects can lead the next generation of examiners to learn how to solve their own problems and build and hopefully maintain their own future.

I don't have the answers yet, but I'm very interested in talking about what it could look like and how it could work together. The dfir future isn't windows, or Macs, or Linux, or Java, or elk, or python, or rust (sorry Matt) it's all of these things because we have to be where the data is no matter the shape, form or storage.

I know several academic grants are focusing on these macro problems like CASE (https://github.com/casework/case) so there are potential solutions out there we just need to start getting our industry to seriously talk about how we want to approach the problem. While I'm sure different answers will be reached , any profrprotowards a solution will eventually find a winner in the minds of the examiners eho use it.
Labels: , ,

Post a Comment


Author Name

Contact Form


Email *

Message *

Powered by Blogger.