Preventive Controls

Email SecurityThe Controls That Actually Prevent Phishing Attacks

Most email security programs fail in the same predictable places: authentication published but never enforced, multifactor deployed in a bypassable form, and logging that was never turned on until it was needed. This page covers the controls that measurably reduce compromise and the configuration choices that determine whether an investigation is even possible.

Updated August 2026 · Reviewed by Elite Digital Forensics examiners · Nationwide breach response

Enforcement gapMany domains publish a DMARC record in monitoring mode and never advance to quarantine or reject.
Phishing resistantHardware backed authentication removes the session relay attack that defeats app based factors.
Logging firstAudit settings cannot be applied retroactively, so what was not enabled before the incident cannot be recovered after it.

Quick answer

Effective email security combines three layers. Domain authentication (SPF, DKIM, and an enforced DMARC policy) stops impersonation of your domain. Identity controls (phishing resistant multifactor authentication, conditional access, and OAuth application governance) stop stolen credentials from becoming account takeover. Forensic readiness (mailbox auditing, extended log retention, and alerting on rule creation) determines whether you can prove what happened if the first two layers fail.

Common questions, answered in one line

QuestionOne line answer
Does SPF alone stop spoofing?No. Without an enforced DMARC policy, a failing message is still commonly delivered.
Which multifactor method is safest?Hardware security keys and platform passkeys, because they are bound to the legitimate site.
Are external sender banners useful?Modestly, and they lose effect quickly as users habituate to them.
What is the most overlooked control?Governance of OAuth applications that hold standing access to mailboxes and files.
Should mailbox auditing be on?Yes, for every mailbox, along with the longest retention your licensing supports.
Does training solve phishing?It helps, but technical controls carry the load. Assume some users will click.

Key terms defined

TermWhat it means
SPFSender Policy Framework. A DNS record listing the servers permitted to send mail for a domain.
DKIMDomainKeys Identified Mail. A cryptographic signature on outbound messages that survives normal forwarding paths.
DMARCA published policy telling receivers what to do with messages that fail authentication, and where to send reports.
AlignmentThe requirement that the authenticated domain match the visible From domain. Without alignment, authentication does not prevent impersonation.
Phishing resistant MFAAuthentication cryptographically bound to the real site, so a proxy page cannot relay it.
Conditional accessPolicy that evaluates user, device, location, and risk before granting or blocking a sign in.

Domain authentication, and why publishing is not protecting

Domain authentication protects your customers and partners from messages that impersonate your domain. It does not protect your own users from inbound phishing that uses lookalike domains, which is why it is one layer rather than the answer.

ControlWhat it doesCommon failure
SPFAuthorizes sending servers by addressToo many lookups, or a permissive softfail that receivers ignore
DKIMCryptographically signs outbound mailNot enabled on every sending service, or weak key length
DMARCInstructs receivers how to handle failures and requests reportsLeft permanently in monitoring mode, so nothing is ever blocked
BIMIDisplays a verified logo on authenticated mailAttempted before DMARC enforcement is in place
MTA-STS and TLS-RPTEnforces encrypted transport and reports failuresRarely deployed, leaving downgrade paths available

Moving to enforcement without breaking business mail

  1. Publish DMARC in monitoring mode and collect aggregate reports for several weeks.
  2. Inventory every legitimate sender, including marketing platforms, ticketing systems, and payroll providers.
  3. Bring each sender into alignment with DKIM signing on your domain.
  4. Advance to quarantine at a partial percentage, monitor, then increase.
  5. Reach a reject policy and keep report review as an ongoing operational task.

Identity controls, where most compromises are actually decided

Since adversary in the middle phishing defeats app based multifactor authentication, identity architecture now matters more than mail filtering. The controls below address the specific techniques seen repeatedly in business email compromise investigations.

Phishing resistant factors

Security keys and platform passkeys are bound to the legitimate origin, so a relay proxy cannot complete the exchange.

Legacy protocol shutdown

Older protocols that cannot enforce modern authentication remain a favored bypass and should be disabled tenant wide.

Conditional access

Device compliance, location, and risk signals block sessions that fall outside normal patterns even with valid credentials.

Token lifetime and revocation

Shorter session lifetimes and a practiced revocation procedure limit how long a stolen token remains useful.

OAuth app governance

Restrict user consent, review applications holding mailbox permissions, and alert on new grants.

Privileged account separation

Administrative accounts should be dedicated, key protected, and excluded from routine mail use.

Payment process controls belong here too

Every business email compromise that results in loss passes through a payment approval step. Out of band verification of banking changes using a known telephone number, dual approval above a threshold, and a policy that email alone never authorizes a change in payment instructions will stop the loss even when the mailbox is compromised.

Find the gaps before an attacker does

We assess authentication, identity, and logging configuration against what we actually see in breach investigations.

Forensic readiness, the control nobody misses until it matters

Preventive controls reduce the odds. Logging determines what you can prove when the odds do not go your way. Audit configuration is never retroactive, so the settings in place before an incident define the ceiling on any later investigation.

  • Enable mailbox auditing for every mailbox and confirm that message level access events are being captured under your license.
  • Extend audit log retention to the longest period your licensing supports, and export to independent storage beyond that.
  • Retain sign in logs outside the provider default window through a log analytics workspace or SIEM.
  • Alert on high signal events: new inbox rules, new forwarding, new authentication methods, new OAuth consents, and impossible travel.
  • Document the tenant configuration, since an examiner needs to know what was and was not being recorded.
  • Test an export before an incident, so nobody is learning the process under pressure.

What a defensible email security program looks like

Regulators, carriers, and opposing counsel increasingly evaluate whether reasonable controls were in place before the incident. A documented program is both a preventive measure and a legal position.

Quarterly

Review DMARC reports, sender inventory, and any authentication drift introduced by new vendors.

Quarterly

Audit OAuth applications with mailbox or file permissions and remove anything unused or unrecognized.

Semiannual

Test the account compromise runbook end to end, including session revocation and evidence export.

Annual

Independent assessment of tenant configuration and logging readiness, documented for carriers and regulators.

Ongoing

Track phishing simulation and reporting rates as a signal, without treating training as the primary control.

What matters most

  • Enforcement rather than publication, since a monitoring only DMARC policy blocks nothing.
  • Phishing resistant authentication for anyone who touches money, data, or administrative access.
  • Application governance, because a consented app survives every password reset.
  • Logging enabled in advance, since audit settings cannot be applied to the past.
  • Payment verification procedures that do not depend on email being trustworthy.

Common misconceptions

We have DMARC, so we are protected

A record in monitoring mode instructs receivers to do nothing. Protection begins at quarantine and reject.

Multifactor authentication is multifactor authentication

App and SMS factors are relayed by modern phishing kits. Hardware bound factors are not.

Security awareness training will fix this

Training reduces click rates but cannot be the control of record when a convincing proxy page is involved.

The provider default settings are adequate

Default audit retention and consent settings are frequently the reason an investigation cannot answer basic questions.

When this applies, and when it does not

This applies when

  • You are preparing for a cyber insurance renewal or a customer security questionnaire.
  • Your domain is being used in phishing against your own clients.
  • You have already suffered one mailbox compromise and want to prevent the next.
  • Counsel needs documentation that reasonable safeguards were in place.

This does not apply when

  • An active intrusion is under way, where containment and preservation come first.
  • The organization has no control over its own DNS or tenant configuration.
  • The question is about a personal email account rather than a business tenant.
  • A specific fraud loss needs to be traced, which is an investigation rather than an assessment.

Multifactor methods ranked by resistance to real attacks

MethodResists relay phishingResists SIM swapPractical note
SMS one time codeNoNoBetter than nothing, but the weakest common option
Authenticator app codeNoYesRelayed in real time by proxy phishing kits
Push with number matchingPartiallyYesReduces fatigue attacks but can still be relayed
Platform passkeyYesYesOrigin bound and widely supported on modern devices
Hardware security keyYesYesThe strongest option for administrators and finance staff

How Elite Digital Forensics helps

We assess email security from the perspective of investigators who spend their time reconstructing compromises after the fact. That means we test the configuration choices that determine both whether an attack succeeds and whether you can prove what happened when one does.

Tenant configuration assessment

Review of authentication, conditional access, consent policy, and audit settings against observed attacker techniques.

DMARC enforcement program

Sender inventory, alignment remediation, and a staged path from monitoring to reject without disrupting business mail.

Forensic readiness review

Verification that the logging needed to answer post incident questions is enabled, retained, and exportable.

Post incident hardening

Prioritized remediation after a compromise, tied to the specific technique used against you.

Carrier and questionnaire support

Documentation of controls in the form insurers and enterprise customers expect to see.

Payment fraud controls

Process design for out of band verification and dual approval on banking changes.

Problems we solve

  • Your domain is being spoofed and customers are receiving fraudulent invoices.
  • A carrier or enterprise customer is demanding evidence of specific email controls.
  • You survived one mailbox compromise and cannot afford a second.
  • You do not know whether your tenant is logging enough to investigate an incident.
  • Finance approves payment changes based on email alone and no one has fixed the process.

Talk with a forensic examiner about your incident

Consultations are confidential. We work directly with affected businesses, with outside counsel, and with cyber insurance carriers and brokers nationwide.

About Elite Digital Forensics

Elite Digital Forensics is an independent digital forensics firm serving businesses, attorneys, and insurers nationwide. Our examiners include former law enforcement forensic examiners who have testified as court qualified expert witnesses in state and federal proceedings. We do not sell security software and we do not manage client networks, so our findings carry no conflict of interest when the question is whether an environment was adequately secured.

Every engagement follows documented chain of custody, defensible acquisition methods, and reporting written for attorney review, insurer submission, regulator response, or courtroom use. Work performed at the direction of counsel is generally treated as attorney work product prepared in anticipation of litigation. Call (833) 292-3733 or request a confidential consultation.

Frequently asked questions

What is the single most effective email security control?

Phishing resistant multifactor authentication using hardware security keys or platform passkeys, deployed at minimum for administrators, finance, executives, and anyone with access to regulated data. It removes the session relay technique that defeats app based factors in most modern business email compromise cases.

Does DMARC stop us from being phished?

No. DMARC prevents others from sending mail that appears to come from your domain, which protects your customers and partners. Inbound phishing usually arrives from lookalike domains or already compromised third party mailboxes, which DMARC on your own domain cannot address.

How long should we keep email audit logs?

Keep them for at least one year where licensing allows, and export to independent storage for longer. Median discovery time for intrusions is measured in months, so a 30 or 90 day window frequently expires before anyone knows to look.

Are OAuth applications really a significant risk?

Yes. A consented application retains access to mailbox and file data through password resets and multifactor changes. Consent phishing is a well established technique, and unreviewed application permissions are among the most common findings in our assessments.

Is security awareness training worth the investment?

It has value for reporting rates and general vigilance, but it should never be the primary control. Modern proxy phishing pages are visually identical to the real login, so a program that depends on users detecting them is a program that will eventually fail.

What should we do first if we only have limited resources?

Enforce DMARC, deploy phishing resistant authentication to high risk roles, disable legacy authentication protocols, restrict user OAuth consent, enable mailbox auditing everywhere, and require out of band verification for any change to payment instructions.

References and authoritative sources

  1. CISA, Implementing Phishing Resistant MFA — https://www.cisa.gov/resources-tools/resources/implementing-phishing-resistant-mfa
  2. Google, Email sender guidelines — https://support.google.com/a/answer/81126
  3. Microsoft Purview, Manage audit log retention policies — https://learn.microsoft.com/purview/audit-log-retention-policies
  4. FBI Internet Crime Complaint Center (IC3) — https://www.ic3.gov/
  5. NIST SP 800-61 Rev. 3, Incident Response Recommendations (April 2025) — https://csrc.nist.gov/pubs/sp/800/61/r3/final
  6. Verizon Data Breach Investigations Report — https://www.verizon.com/business/resources/reports/dbir/

#DigitalForensics #ComputerForensics #CellPhoneForensics #ExpertWitness #DigitalForensicExperts #EliteDigitalForensics #ForensicInvestigation #DataBreachResponse #DataBreachInvestigation #IncidentResponse #CyberForensics #EmailSecurity #DMARC #Phishing #MFA

This content is for educational and informational purposes only and does not constitute legal advice. Elite Digital Forensics provides independent digital forensic services and expert witness testimony; we do not provide legal representation. Every case is fact specific; outcomes depend on the evidence, jurisdiction, and counsel. Retain qualified legal counsel for advice about your matter.

Assistant Icon Elite Digital Forensics Assistant
πŸ‘‹ Live Chat Now!
Free Virtual Consultation 24/7
Chat Now!

By submitting this form, you consent to be contacted by email, text, or phone. Your information is kept secure and confidential. Reply Stop to opt out at anytime.Β 

IMPORTANT: Please remember to check your spam or junk folder