This whole hafnium situation struck just as we were moving to Exchange online, missed this transition by a few weeks – lucky us. Anyway, the exploit was active since January, Microsoft patched in March. That leaves almost two months where networks/servers were at risk with no patch.

At this point, despite patching and various testing tools, no one can be for sure what’s going on with their networks. That being the case, what is the best we can do in the short term when using sensitive passwords in our networks for network administration? Disable all accounts we use to interact with Exchange server right after using? Change all passwords twice after using?

If we continue to run testing tools on Exchange, that essentially means putting sensitive passwords INTO the Exchange server to check the health of the Exchange server – seems like a giant catch 22.

11 Spice ups

Yeah, it’s a sticky situation with passwords. Granted if the bad guys are in the network which is the perception organizations should be taking and making sure the critical assets and other sensitive data are protected fully.

Has there been any considered to use MFA to reduce some of the risk of the current vulnerability?

@KnowBe4

2 Spice ups

Hi there, thanks for the info, but attackers wouldn’t be using OWA to log in correct? So 2FA applies more to general security than dealing with HAFNIUM wouldn’t it?

1 Spice up

UserLock is designed to make it easy to add MFA (and contextual restrictions) to all users accessing resources on-premise and in the cloud. This includes protecting access to both Exchange Server and Exchange Online.

If you have an EDR tool - you can do a retro check for IoC (SHA256, Webshells, IP/URL, file paths) I checked mine back to December.

HIGHLY suggest looking into Azure Advanced Threat Protection (ATP) formerly Advanced Threat Analytics (ATA). This is an E5 license or ala-carte.

Agents run on Domain Controllers and correlate on-prem to Azure Cloud App Security alerts. It can detect golden ticket, over pass the hash, pass the hash, etc.

Thanks for the info, does it merely detect those issues, or does it halt them as well?

You may want to consider running this to look for IOCs.
https://us-cert.cisa.gov/ncas/current-activity/2021/03/18/using-chirp-detect-post-compromise-threat-activity-premises

That’s awesome, thanks. Does that have to be run on each server do you know? Or just a DC?

I believe you run it on any system you suspect trouble on.

There is also a nice script below that checks for webshells on your exchange server:

https://codeload.github.com/cert-lv/exchange_webshell_detection/zip/refs/heads/main

Justin,

Do you know a way to run the CHIRP tool and exclude OneDrive for Business folders? I have ODFB on my laptop set to use Files On-Demand, and when I ran the CHIRP tool on my laptop, it checked all files listed in ODFB, thereby triggering an unexpected 10GB download of all those files I didn’t need right now.

Gregg

@justingseiwi

Sorry, I’m not sure. I ran the tool once but I never got far into the documentation.

Justin

Bummer. I will update here if I find an answer.

Gregg

@justingseiwi