applied security research
Rik van Duijn - 13 mei 2020

Office 365 – Exchange rules

This blog is part of our Office 365 attack & defense series. We also maintain a Github page where we share our Office 365 tools and queries.

Exchange rules can be useful in managing the emails we receive on a daily basis. For example, it allows users to automatically respond or move specific emails to specific folders. The same rules can also used to exfiltrate information. A hacker adds a rule to forward specific emails. This method is sometimes used to gain information or to intercept specific email communication in order to manipulate internal payment procedures. We’ve encountered companies that became victim of a scam where the invoices were intercepted and modified just before being delivered to the intended destination. The attackers just changed the bank account number where the money had to go to. This can become quite costly; we’ve seen one instance where attackers were able to do this with a payment for multiple vehicles. As you can imagine this was an expensive lesson for the company. These types of scams are part of what they call Business Email Compromise (BEC) scams.

The way they are executed differs per type of scam. One of the tricks is to intercept emails sent, this gives the ability to modify emails before sending to the intended recipient. There are different ways to forward emails. Most of them can be done with user privileges, others require admin privileges on the exchange server itself. Using the admin privileges, it’s possible to steal emails for the entire organization. The user privileges only allow an attacker to steal the emails for the compromised user.


  • Rules:Forward to
  • Rules:Forward as attachment
  • Rules:Redirect to
  • Forwarding: Forward all email


  • Mail flow: rules
  • Mail flow: connectors

Depending on your Office 365 license you have you’ll be able to use Office 365 Advanced Threat Protection (ATP). ATP is an effective solution because it already detects many of the tricks you can use to steal emails. If ATP is included in your license, make sure the alert emails are sent to someone or a group of people that can check on alerts from the system. For the purpose of this blog we assume your organization does not have ATP. Which is not a problem we can detect any of these threats with limited resources.

Enabling audit logging

For companies that have an enterprise E3/E5 license there is no need to enable logging. Without an E3 or E5 license, audit logging has to be enabled. Next to this an additional step is required. In that case, auditing has to be enabled on every individual mailbox manually. In order to do so, we have written a PowerShell script that retrieves all available mailboxes, loops over all mailboxes to individually enable the logging per mailbox. For more information see:

We’ve added 2 scripts to fix your logging:

Connecting Exchange audit logging to Sentinel

Although using Sentinel in combination with Office 365 is free, it does require an Azure subscription. Adding Sentinel is easy, navigate to Azure portal, search for “Azure Sentinel” and select add. The wizard will guide you through, make sure to add everything to a unique resource group, it will allow you to see all related components and to see any cost you might incur. Instead of us re-iterating how to add sentinel exactly, its better to go to the source:

Creating Rules

Luckily, we don’t have to build all of the rules ourselves. Microsoft publishes some detection rules on their GIT repository. ( However i havent seen any complete set of rules to detect all different types. Let’s reiterate the things we want to detect.


  • Rules:Forward to
  • Rules:Forward as attachment
  • Rules:Redirect to
  • Forwarding: Forward all email
  • Mail Flow via ExchangeAdmin center (Administrator privileges required)

In order to build proper rules to detect the above tricks, its easiest to just create the rules and then see what type of logging shows up. So we know what we are dealing with. Using the ‘search “rulename”’ command will allow you to find entries pertaining to your rule creation. Looking for our rules the most important operations to look for are:

  • New-InboxRule with ruletype being one of the following:
    • ForwardTo
    • ForwardAsAttachmentTo
    • RedirectTo
  • Set-Mailbox with type: “ForwardingSmtpAddress”
  • New-TransportRule

Just detecting one of the above activities might incur allot of false positives as these mail rules are often used for legitimate purposes. One of the ways to reduce the number of false positives would be to filter out any internal mail forwards.

  let TimeFrame = 1d;
  let domains = dynamic(["" ""]);
  | where TimeGenerated >= ago(TimeFrame) 
  | where Operation == "Set-InboxRule"
  | extend details = parse_json(Parameters)
  | extend ruletype = tostring(details[0].Name) 
  | where ruletype in ( "ForwardTo" , "ForwardAsAttachmentTo", "RedirectTo")
  | extend forwardaddr = tostring(details[0].Value) 
  | extend forwarddomain = tostring(split(forwardaddr, "@")[1])
  | where isempty(forwarddomain) == false and forwarddomain !in (domains)
  1. Create an array of valid forward domains
  2. Parse the forward address
  3. Only trigger if the forward domain is not in our whitelist

There is a disadvantage to doing this, its unclear if Microsoft ever chooses to modify the order of the Parameters object. Once this changes we would not trigger. Unfortunately, the parameter order changes per operation.


While testing a rule to detect the creation of multiple forwarding rules across different users within one organization. So, I asked Wesley to add some extra rules. After waiting for a couple of minutes my rule failed. I asked Wesley if he added a rule and asked the rule-name. Turns out Wesley didn’t want to add new rules, so he copied an existing one. Those are modified using the “Set-InboxRule” function which is not part of our and the Microsoft provided rule. Turns out the ATP suite has a broader set of detections and already detects rules created via “Set-InboxRule”. For those that don’t have the luxury of ATP we can create a set of different rules.

Based on our experience a more complete set of operations to detect would be:

We could create one rule-to-rule them all, but it would be easy to make a mistake. Better to have atomic rules that detect one specific thing. This makes testing easier and the rules are easier to understand. The rules are available in our Github repo, dont forget to change the valid domains.

Yet another caveat: As if there aren’t enough deviations we have to contend with there is another way of adding rules. The EWS API has the “UpdateInboxRules” operation. Logging for this operation lacks information, there doesnt seem to be a way to have propper logs for this. A way to solve this would be to log into our Exchange instance and query them with the “Get-InboxRule” cmdlet. Unfortunately it only returns the name of the rule but often lacks any additional information. The only way to get those is through the EWS API and for each user search through their inbox to find the rules. There is a usefull script in the O365-InvestigationTooling Github repo that dumps all rules and forms. A nice future project would be to create a playbook that triggers once the “UpdateInboxRules” operation is spotted, queries the rules and checks for irregularities.


Mailbox rules are just one of the methods criminals try to maintain access to your emails. Storing audit logging in a tool like Sentinel will give your organization the ability to look back once something goes wrong. Using Sentinel in combination with Office 365 is free and even has 90 days retention, it’s a no brainer for any organization using Office365[1]. In future blogs we’ll discuss other detection methods related to BEC fraud. And how to respond once an attacker has gained access to one or more user accounts. In a future blog we’ll go more into the BEC fraud tactics, we plan on releasing rules and scripts to detect BEC-specific abuse.

[1] Storing different logs or creating playbooks can incur additional cost.


Public SharePoint sites - the new open shares

Wesley Neelen - 16 sep 2021
During one of our engagements we were investigating a Microsoft 365 environment. My colleague Rik discovered that many SharePoint sites were publicly available within the organization. We were surprised by the amount sites that were wide open this way. A lot of sensitive information was located on those sites, for example PII-information and passwords for […] Lees verder

Decrypt passwords from Xerox Workcentre config backups

Rik van Duijn - 29 aug 2021
During a recent engagement we encountered Xerox WorkCentre printers using default credentials (admin:1111). Usually it’s just another finding, but this time we noticed the printer had SMB and e-mail credentials configured. For LDAP we usually point the printer to our own IP and get access to the plaintext creds that way. But in the case […] Lees verder

Office 365 audit logging

Rik van Duijn - 19 aug 2021
It’s important to enable audit logging for o365 even if you are not monitoring them actively. Atleast if you get hacked there’s logging to investigate :). The audit log is not always enabled by default, it seems to rely on license levels. However there are some important things to take into consideration. You can enable […] Lees verder

Ransomware, nationale crisis?

Erik Remmelzwaal - 04 aug 2021
Als er 1 digitale dreiging is die veel in het nieuws komt, dan is het ransomware. Er wordt zelfs gesproken van een nationale crisis. Lees verder

Mijlpalen en hoe het gaat

Zolder B.V. - 02 jul 2021
Vandaag gebeurden er op Zolder toch een paar dingen die blogwaardig zijn. Dus prima aanleiding om nog maar eens de laptop open te klappen en te vertellen hoe het gaat. Nieuwe collega’s Het is 1 juli 2021 en we zijn ruim een jaartje onderweg als Zolder. De belangrijkste stap die we vandaag zetten, is dat […] Lees verder

Zolder wordt hoofdsponsor HCZ

Zolder B.V. - 01 jul 2021
Vandaag is bekend geworden dat Zolder de nieuwe hoofdsponsor is van HCZ – Hockeyclub Zevenbergen. De komende drie seizoenen zal het logo van Zolder daarom voorop de shirts van alle HCZ leden prijken. We zijn heel erg trots op deze nieuwe stap voor ons jonge bedrijf, en hopen zo de relatie met onze regio te […] Lees verder

Breda Robotics

Erik Remmelzwaal - 10 mei 2021
Zolder BV is toegetreden tot het netwerk van Breda Robotics. Deze vereniging brengt organisaties bij elkaar die actief zijn rondom robotisering in de regio West-Brabant. Voor Zolder geeft Breda Robotics de mogelijkheid om samen te werken met de robotiseringsindustrie. Te begrijpen hoe die sector precies werk en op welke vlakken cybersecurity kennis kan worden ingezet […] Lees verder

27% .nl domeinen slecht beschermd tegen spoofing

Erik Remmelzwaal - 29 apr 2021
TLDR: We scanden de DNS records van 1,6 miljoen .nl domeinen en vonden uit: 9% is rechtstreeks gekoppeld aan Microsoft 365, daarmee is Microsoft veruit de grootste Google is nr2 en heeft 4% van de domeinen aan zich verbonden, nagenoeg gelijk aan een aantal andere spelers. Van alle mail-enabled domeinen heeft 27% geen SPF record […] Lees verder

Zolder biedt MKB betaalbare en eenvoudige security-app

Zolder B.V. - 12 apr 2021
“Attic voorkomt dat security een luchtbel wordt” Security is bij mkb-bedrijven vaak het ondergeschoven kindje. Ze hebben er de mensen en het budget niet voor. Dat maakt deze doelgroep een aantrekkelijk doelwit voor cybercriminelen. Voor de vier doorgewinterde cybersecurity-experts van start-up Zolder reden om Attic te introduceren. Deze eenvoudige, goedkope en toekomstbestendige app maakt mkb’ers […] Lees verder

Nieuwe Themesong voor Zoldersessions

Erik Remmelzwaal - 13 mrt 2021
Ik vond het tijd worden voor een nieuw liedje voor onze Zoldersessions. Tot nu toe hadden we er een rechtenvrij liedje onder staan, namelijk EVA_失望した, maar wilden toch iets meer 'eigens'. Daar schakelden we Bjørgen van Essen voor in met dit eindresultaat. Dit is hoe dat tot stand kwam. Lees verder

Zolder.App Open Beta

Zolder B.V. - 02 feb 2021
We launched the final beta release to the Google and Apple appstores. Any business running on Microsoft 365 is more than welcome to join. As a beta-tester you will receive a free subscription to the Zolder.App Premium Plan for the remainder of the beta phase, which is scheduled to run through April 30th 2021. Zolder.App […] Lees verder

GGD data is topje van ijsberg

Erik Remmelzwaal - 26 jan 2021
Maandag kwam RTL Nieuws, na onderzoek van Daniël Verlaan, naar buiten met het nieuws dat gestolen data van de GGD online wordt verhandeld door criminelen. Het gaat om data die onderdeel uitmaakt van het bron- en contactonderzoek dat de GGD uitvoert als onderdeel van de bestrijding van Corona/COVID-19. De data bevat gevoelige persoonsgegevens en criminelen […] Lees verder

#CES2021 - We Are Ready!

Erik Remmelzwaal - 06 jan 2021
We are very excited to be part of the #CES2021NL mission! Meet us at CES (Januari 11-14) in our online booth 10609 and see how we solve global challenges with NLTech. Erik Remmelzwaal, Co-Founder & CEO Yes I indeed think we are ready for CES. At this virtual event we will showcase Zolder.App. I am […] Lees verder

Zolder.App Blog 3 - Feedback

Erik Remmelzwaal - 27 nov 2020
Bij het ontwikkelen van een nieuwe dienst, zeker als dit Software-as-a-Service betreft, is feedback vanuit (potentiële) afnemers cruciaal. In het geval van Zolder.App is de doelgroep het MKB. We zijn al gelijk na lancering van het merk Zolder gestart met het vinden van MKB-ers die als tester wilden helpen. Oproep 19-apr-2020 Dit leidde tot best […] Lees verder

Azure App Consent Policies

Rik van Duijn - 11 nov 2020
OAuth consent phishing has been on the rise for a while now. Unsurprisingly, Microsoft has gradually introduced measures to protect from this type of attack. Latest: Risk-Based Step-Up Consent. Lees verder

Honeytokens using Azure Keyvaults

Rik van Duijn - 15 okt 2020
In 2017 Wesley and I gave a presentation at SHA2017 about honey/pot/tokens. We actually planned on building a fully fledged platform. But never came further then the POC phase of that project. This week we got a product demo from the guys at Thinkst, i’ve always loved this way of thinking: let the attacker come […] Lees verder

Zolder.App Blog 2 - Probleem & Oplossing

Zolder B.V. - 08 okt 2020
Het is best een goed idee om voordat je begint met het bouwen van een product of dienst, te weten welk probleem je ermee gaat oplossen. Voor Zolder.App: we lossen het probleem dat MKB-ers slecht beveiligd zijn op door enterprise-niveau security voor hen toegankelijk te maken. In feite zijn er een aantal problemen die we […] Lees verder

Risk of exposed home automation services

Wesley Neelen - 24 sep 2020
At home, I am automating many things for fun. Currently I am using Home Assistant, an incredibly powerful piece of software for automating your home. Regularly I am combining the home automation experiences with security. Home automation is often related to physical things such as changing lights, moving curtains, opening door locks or turning the […] Lees verder

Zoldersessions Studio Setup

Zolder B.V. - 27 aug 2020
Here is the kitlist which we end up with to record our Zoldersessions 🙂 Audio Input 4x Rode Procaster microphone 4x Triton Audio FetHead Microphone PreAmp 4x YellowTec m!ka Mic Boom Focusrite Scarlett 18i8 3rd gen Audio Output 4x Shure SRH840 Headphone ART HeadAmp 4 headphone amplifier Video Input 2x Sony Handycam main cameras Logitech […] Lees verder

Zolder.App blog 1 - het idee

Erik Remmelzwaal - 27 aug 2020
Op Zolder bouwen wij aan een mobiele app die MKB’ers op een baanbrekende manier moet helpen digitaal weerbaar te zijn. We verwachten in het vierde kwartaal van 2020 de app te kunnen lanceren. In deze blogreeks neem ik je mee in de ontwikkeling van Zolder.App. Eigenlijk was er niet 1 idee, maar is Zolder.App het […] Lees verder