Forum Discussion
Disable users ability to create rules...
Andy David Well in this case the bad actor, we will call him Jimmy, intercepted an email about a incoming wire from a client to our company of a VERY large amount, using stolen credentials. Jimmy convinced the client to send the money to another bank account, telling them our original account was compromised. The client, thinking that the contact was still the proper person in our company, complied and sent them the money.
Jimmy was smart enough to set up a rule for all incoming and sent emails to and from the clients domain to be moved to the RSS feeds folder, which no one on God's green earth uses, so that the real employee, whose credentials were stolen, within our company would never see them.
A lot of things were done wrong by the client, there were quite a few red flags and they never called to confirm with us. We also should have had better security long ago. But one of the measures the company partners would like to make to help ensure this never happens again, is to stop all rules from being created. Or at the very least some form of alert whenever one is created. This is not a terrible request as it is a VERY common way the Jimmies of the world operate.
You may think it unnecessary, but if you lost this amount of money maybe you would change your mind?
It may be extreme, but thankfully almost no one in our company uses rules. And it will put the minds of our accounting folks and partners at rest.
Thanks for your input!
Hi, just wondering if you have a solution to this. I just got hit with exactly the same attack that you mentioned. We will be implementing MFA shortly but I also want to disable rules in OWA. Can you point me in the right direction? tks
- BdCvCSep 15, 2021Copper ContributorMy 2 pennies: Cart before the horse? Rules are good, hackers are bad, First stop hackers (MFA, block basic auth, P1 conditional access etc, whatever works for your situation). Run daily reports on successful Logins (are they coming from your offices or from Nigeria), run reports on Failed Logins (has the Hacker community found another way trying to bypass MFA?), train users on phishing techniques. All this can be automated for pennies, and will stop any successful hacks (if they are good enough) within hours or less. Still too long but you can't always win them all.
Blocking rules does nothing to help you imho, modern hackers don't even create rules anymore, too obvious. But again, just my opinion. Next month it might all change again, that's the fun of it.... - rickisavailableSep 14, 2021Copper Contributor
Does anyone know how to prevent the creation of rules?
I introduced MFA but my account was broken into again and this time horrible Jimmy (lets call him) created a rule to hide emails as well as changing the fone number of my MFA to his fone.
RESULT: emails hacked and money fraudulently transferred out of accounts.
some one please help. How do you prevent rules altogether? - polylazaroAug 06, 2020Copper Contributor
Ken_Runyon Try this
Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -RulesEnabled $false
"OwaMailboxPolicy-Default" is the name of OWA policy that's assigned to the target user which can be found on Exchange Admin Center (as seen on screenshot).