Best Practice Checklists
An exclusive publication of

Essentials every leader should understand about IT
Issue 4 – Email Security & Solutions
Email Security & Solutions
The most attacked door into your organization is the one everyone uses all day
Email is the channel attackers probe first, because it reaches every employee and carries the organization’s identity with it. Most of what protects it is invisible: a handful of authentication records, a filtering layer, and a few server settings that decide whether a stolen password, a spoofed domain, or an exposed server turns into a real loss. When one of those layers is missing, the failure is usually silent until money or data has already moved. The situations below are ordinary, not exotic.
When it goes wrong
No single control stops every email threat, and that is expected. Email security works in layers, and each layer closes a specific gap. The point here is not to alarm. It is to show what a missing layer actually looks like in practice, so you can decide which gaps you are comfortable leaving open.
The Spoofed Domain
A vendor, or an executive, appears to email accounts payable with new wire instructions. The address looks right, because the domain publishes no rules telling receiving servers which systems may send on its behalf. The request is convincing, and the payment goes out.
A fraudulent wire is sent under a trusted name.The Password That Skipped MFA
An employee’s password is phished. Multi-factor authentication is enabled, so the account should be safe. But an older mail protocol that does not enforce that second factor is still switched on, and the attacker signs in through it.
The mailbox is read quietly for weeks, and MFA never fires.The Unapproved Phone
With nothing more than a stolen username and password, an attacker connects a personal mobile device to the mail system. By default, little stands in the way, and mobile connections often sit outside the multi-factor rules that protect a browser login.
An unapproved device synchronizes the entire mailbox.The Exposed On-Premises Server
An organization runs its own Exchange server, published directly to the internet so staff can reach mail from anywhere. A new vulnerability is discovered, and automated scans reach the server directly, before a patch is available to install.
A backdoor is planted before a fix even exists.Regulated Data by Email
Under time pressure, a staff member emails a spreadsheet of Social Security or account numbers to keep a deal moving. There is no scanning layer to catch sensitive content on the way out, so nothing intervenes.
Regulated data leaves the organization unencrypted.The common thread
None of these required a sophisticated attack. Each one exploited a specific setting that was never turned on, or a server left exposed when it did not need to be. Email security is not one product. It is a set of individual, checkable controls.
Every one of these outcomes is addressed by configuration you can verify, not by a larger budget. The purpose of this issue is to help you confirm that each layer is actually in place, rather than assumed.
What to Ask Your IT Manager or Provider
and how to know if the answers are good ones
You do not need to administer a mail system to oversee one. You need to know what to ask. A fuller primer on the on-premises mail gateway and DMZ reverse proxy, and on how the email authentication records work, is provided at the end for those who want the detail. First, the part that matters: run the checklist below with your IT professional. If any item is not marked green, it may warrant a closer look.
Spam and Malware Pre-Filtering
Content Scanning to Limit Legal Exposure
Certificate and Transport Security
DMZ Reverse Proxy
SPF Published
DKIM Enabled
DMARC Configured
Mobile Device Approval
Legacy Protocols Disabled
Going deeper: the on-premises mail gateway and DMZ reverse proxyFor organizations that host their own Exchange server. Optional.+
Organizations that run their own internal mail server, rather than using a cloud service, take on the job of protecting a system that must be reachable from the internet. Best practice for that situation is to place a mail gateway between the outside world and the mail server, so inbound connections are inspected and filtered before they ever reach the server itself.
What a DMZ reverse proxy does
A DMZ is a buffer network that separates externally reachable services from the internal network, with tightly restricted traffic between them. An SMTP mail gateway receives and filters email before relaying it to Exchange. A reverse proxy for HTTPS services handles connections to features such as Outlook on the web and other published Exchange endpoints. These are different functions and must be configured for the protocols in use. Neither placement in a DMZ nor a proxy guarantees that forwarded traffic is safe; patching, access controls, and monitoring remain necessary.

Why this earned its own section
In early 2021, a set of Microsoft Exchange Server vulnerabilities, later known collectively as ProxyLogon, was disclosed and widely exploited. As soon as the exploits became known, our organization applied the associated patches to active Exchange clients, and then went further, scanning each environment for signs that a backdoor had been installed during the weeks the vulnerabilities were believed to have been exploited before disclosure. Industry reporting at the time indicated that a substantial share of internet-facing Exchange servers had been probed or compromised. In our review, the clients whose Exchange servers sat behind a DMZ reverse proxy showed no evidence of successful tampering. Those specific vulnerabilities are long patched and now historical, but the lesson they illustrate is durable: a server that is not directly reachable is a far smaller target.
On-premises or the cloud
Where security or workflow requirements favor on-premises Exchange, plan SMTP filtering and the secure publication of any HTTPS services separately. A DMZ, mail gateway, or reverse proxy is one part of that design and does not replace prompt patching and access controls. Virtualization may make additional components practical, but licensing, infrastructure, and support costs depend on the deployment. Migrating to Microsoft 365 shifts operation of the mail infrastructure to Microsoft while leaving the organization responsible for its identities, access settings, and data practices. The right choice depends on the organization’s needs.
The email authentication trio, in plain termsWhat SPF, DKIM and DMARC actually do. Optional.+
SPF, the guest list
Sender Policy Framework is a DNS record that publicly lists which servers are allowed to send email for a domain. A receiving server can check that list and treat mail from anywhere else with suspicion.
DKIM, the tamper-evident seal
DomainKeys Identified Mail adds a cryptographic signature associated with a signing domain. A receiving server verifies it using that domain’s DNS public key and checks the parts of the message covered by the signature. A valid DKIM signature does not by itself establish the identity of an individual sender or prove that a request is legitimate.
DMARC, the instructions
Domain-based Message Authentication, Reporting and Conformance ties authentication to the domain in the visible From address. DMARC passes when at least one SPF or DKIM result both passes and aligns with that domain. It lets the domain owner request handling of messages that fail DMARC and obtain reports; receiving servers can also apply their own policies. Failure of SPF alone does not mean DMARC fails if aligned DKIM passes, and the reverse is also true.
All three are published in DNS and apply whether email is hosted on-premises or with a cloud provider such as Microsoft 365.
Contact Sandbox Technologies for a free, no-obligation consultation.
Headquartered in Los Angeles. Serving clients nationwide and internationally since 1997.
Nationwide (Toll-Free)
877-930-8324
Los Angeles
424-207-5130
Support Helpdesk
424-207-5140

