Intro
5 min
How Email Impersonation Actually Works
Last updated: January 26, 2026
Pro-Owner perspective: This document frames your systems as a technical estate — an asset to be stewarded, documented, and bequeathed. Treat these steps as craftsmanship: protect the continuity, auditability, and transferability of your digital legacy.
How Email Impersonation Actually Works
The 60-second version
Email impersonation is when attackers send emails pretending to be someone you trust—like a colleague, vendor, or bank—to steal money or data. They exploit weak email security (e.g., missing SPF/DKIM) or use lookalike domains (e.g., yourbank.com vs. yourbank-secure.com). These attacks rely on social engineering to trick victims into urgent actions, like wiring funds or sharing passwords.
What this solves (in real business terms)
- Fraud prevention: Stop unauthorized payments or data breaches.
- Reputation protection: Avoid damage from customers receiving fake emails "from" your business.
- Compliance: Meet regulatory requirements for email security (e.g., GDPR, PCI DSS).
- Operational continuity: Prevent disruptions from phishing attacks locking accounts.
What it costs (honest ranges)
-
Prevention:
- Email authentication (SPF/DKIM/DMARC): $0–$50/month for monitoring tools.
- Employee training: $500–$2,000/year for phishing simulations.
- Advanced filtering: $5–$20/user/month for AI-driven threat detection.
-
Recovery (if breached):
- Forensic investigation: $10,000–$50,000 per incident.
- Legal fees: $5,000–$20,000 for compliance violations.
- Lost funds: Average $25,000–$100,000 per successful attack (FBI 2025 data).
What can go wrong
- Over-reliance on filters: Assuming tools alone will catch all impersonation attempts.
- Ignoring human factors: Employees skipping verification steps under pressure.
- Misconfigured DMARC: Blocking legitimate emails or failing to stop spoofing.
- Delayed response: Not detecting attacks until after funds are transferred.
Vendor questions (copy/paste)
- "How does your solution detect lookalike domains and spoofed senders?"
- "Do you enforce DMARC policies to reject unauthenticated emails?"
- "What’s your false-positive rate for legitimate business emails?"
- "Can you integrate with our email provider (e.g., Microsoft 365, Google Workspace)?"
- "What training resources do you offer to educate employees?"
Minimum viable implementation
- Deploy SPF/DKIM/DMARC: Authenticate your domain to prevent spoofing.
- Train employees: Teach them to verify sender addresses and avoid urgent requests.
- Enable MFA: Require multi-factor authentication for email and financial systems.
- Use email filtering: Block known malicious domains and attachments.
- Monitor anomalies: Flag unusual login attempts or payment changes.
When to hire help
- After an attack: Forensic experts can trace the breach and recover funds.
- Compliance audits: Ensure email security meets industry standards.
- Tool deployment: Configure advanced filtering or DMARC policies correctly.
- Employee training: Develop customized phishing simulations.