Phishing: Traditional and Direct Email Creation whitelisting methods compared
In this article, we will discuss the two methods of whitelisting phishing simulations in our tool: Traditional Whitelisting and Direct Email Creation (Injection) and explain why one might choose one over the other.
Traditional Whitelisting
The traditional method of whitelisting involves excepting Sending IP addresses and domains within Microsoft Defender and other email security tools you may have to ensure delivery of your simulations. To learn more about traditional whitelisting, please view the guide here: Getting Started: Phish Whitelisting
Direct Email Creation
Direct Email Creation (DEC) is a useful feature that eliminates the need for whitelisting simulated phishing emails. Generally, DEC should be used when traditional whitelisting does not produce the desired result. This will require you to integrate our API with your Azure tenant accepting permission like:
This will also require a Service Account with the following permissions:
-
Application Impersonation from the Microsoft 365 Exchange Admin Center
-
Application Administrator from the Microsoft Azure Portal
Note: you may still have click-based scanning or filtering in other email security solutions that you'll have to consider. To learn more about DEC and how to configure it, please view the guide