@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

Daily Blog #415: The Death of a Unicorn

Hello Reader,
      If you followed the original Crowdstrike post or the follow on post from LMG security calling the Activities API a 'unicorn' of sorts then I'm sorry to say the technique now appears to no longer be functional. It's been a long time since I've seen the DFIR community be this obsessed with a single artifact but either Microsoft is closing this for good or is going to replace this with maybe default mailbox audit logging in the future.

To be clear this isn't the first or only evidence source that a company has retained as a secret. I'm not in the business of airing companies internal choices but I will point this out to put this in a larger context. DFIR is made up of two niche industries, Digital Forensics and Incident Response. There are differences between these two fields of work and while they may rely on each other to function those on the DF side need to document their new research in reports and disclose them to allow another party to verify and respond to their work. There are normally two or more experts from different companies working on every case.

Compare this to the very competitive Incident Response world where a company can get a substantial competitive advantage by finding a new evidence source. If one IR company can tell a client they can find evidence another can't they might win more business while if a DF expert tells a client they can find evidence no one else can it might not be admissible unless they can explain how to do it to the other side. There are many IR companies right now sitting on undisclosed evidence sources and threat intelligence sources. They will continue to do so until they are required not to.


The point? In this case the public disclosure of an evidence source has ended its use by all parties. Whether this was because
  •  it wasn't supposed to be used for these purposes
  •  too many people began taxing the use of the API
  • the powers that be at Microsoft were worried about people misinterpreting the results of the API 
  • or just a large company not enjoying being called unethical for people using an API that was documented but had a use that most within the company were not aware of
We won't know unless they come out publicly and state it, which seems highly unlikely.  What we do know is that they have responded in one way we can all see and that is by turning off the source of all the controversy in the first place.

If I was arguing to disclose a secret evidence source within my company I'm pretty sure I just lost that argument to those who worry it would stop working after disclosure.
Labels:

Post a Comment

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

Author Name

Contact Form

Name

Email *

Message *

Powered by Blogger.