Share this page!

Enter URL or ID to Unroll

You can paste full URL like: https://x.com/threadreaderapp/status/1644127596119195649
or just the ID like: 1644127596119195649

How to get URL link on X (Twitter) App

  1. On the Twitter thread, click on or icon on the bottom
  2. Click again on or Share Via icon
  3. Click on Copy Link to Tweet
  4. Paste it above and click "Unroll Thread"!
  5. More info at Twitter Help
Aura Profile picture
Aura
@SecurityAura
GCIH, GCFE | Sr. Security Consultant | Digital Forensics, Incident Response & SOC | @CuratedIntel Contributing DFIR Member
Dec 18 • 14 tweets • 4 min read
@EricaZelic @NathanMcNulty @b3njam1n3ng3l @InvictusIR @DylanInfosec @Evild3ad79 I'm going to answer @b3njam1n3ng3l earlier question here because it's still relevant to that part of the discussion.

The way I do it, and that's honestly up for debate is that: we consider that every single InternetMessageId and ObjectId involved in flagged UAL events are gone. @EricaZelic @NathanMcNulty @b3njam1n3ng3l @InvictusIR @DylanInfosec @Evild3ad79 Which means, the threat actor had access to them. So may it be: Create, Send, Update, MoveToDeletedItems, etc. we tell the client to consider these as being "exfil'd".

This includes MailItemsAccessed events but we run additional checks: Sync vs Bind.
Dec 17 • 8 tweets • 2 min read
@EricaZelic Just did a similar exercise today for reasons.

Every single time I pull a UAL for a BEC, I end up learning something I didn't know from the last time I looked at one.

Could probably do a whole course on analyzing the UAL.

And I'm only talking about Azure, Exch, SP and OD here. @EricaZelic The more you dig in the UAL, the more you start raging that the logging is not unified and you can clearly see that some teams didn't talk with each other when they decided to add X or Z events to the UAL.

And don't even get me started on the IP addresses that are logged there.
Sep 21 • 8 tweets • 2 min read
We were discussing this at one point in @CuratedIntel. A lot of these classes uses Zeek, Sysmon, EID 4688, etc. The purpose being to expose you to what can be done with these logs and what you can find.

The reality though is that you'll deal with defaults for the most part in IR Forget your Sysmon, forget even your 4688. If you have it, chances are command line logging won't be enabled.

Default 20 MB EVTX (Security, etc.) on all endpoints, even DCs. That is, if they weren't cleaned by the TA.

No SIEM, no EDR. Default Linux logging. Nothing fancy.
Jun 10, 2022 • 4 tweets • 2 min read
Ever wondered what happens when #MicrosoftDefender quarantines a PUP, but then you go in the notification, and select to "Allow" the application in the future? Well, a Registry value with the name of ThreatId (detected threat) is set in the Registry with a Data of 6 for Ignore. It seems that this Regkey is regularly cleaned however, since the application gets flagged every few days and I need to restart the process.

Registry key for copy/paste:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Threats\ThreatIDDefaultAction