Preserve evidence
Keep the original message with headers when possible. Screenshots alone often hide important delivery details.
Check the scope
Determine whether the message spoofed your domain, used a lookalike domain, or came from a compromised account.
Close the loop
Update controls, warn affected parties when needed, and document what changed after the incident.
Practical context
How to use this guidance
A spoofing report is easier to handle when evidence is preserved and the response path is clear. The first job is to understand what kind of abuse occurred.
A practical example
Imagine a team reviewing incident response for spoofed email after a new software vendor starts sending customer-facing mail. The immediate question is not whether the setup uses the right acronym; it is whether the business can explain the sender, prove that it is authorized, and spot problems before customers or employees lose trust.
That review usually starts with preserve evidence. From there, the team should compare the intended workflow with real message samples, provider settings, and any reporting data that shows how receivers are treating the mail. This turns the topic from an abstract security idea into a manageable operating task.
Action checklist
- Collect the original message with headers.
- Determine whether it is spoofing, lookalike-domain abuse, or account compromise.
- Warn affected teams if the message targets customers or payments.
- Document control changes after the incident.
Common traps
- Deleting the message before headers are captured.
- Assuming every fake message means an internal breach.
- Responding publicly before facts are clear.
Questions to ask internally
- What domain did the attacker actually use?
- Who received the message?
- What control would have reduced this risk?
Evidence to gather
Good decisions are easier when the team works from evidence instead of memory. For this topic, collect enough detail to connect technical records with the business process they support.
- A recent sample message from each important sending path.
- The DNS records or provider settings connected to the sender.
- The business owner who can confirm whether the sender is still needed.
- Any recent support tickets, delivery problems, or suspicious-message reports.
- The decision log for changes made after the review.
Review rhythm
Review this area whenever a new email platform is launched, a domain or subdomain is added, a vendor is retired, or a suspicious message is reported. For stable environments, a quarterly review is usually enough to catch drift before it becomes an urgent delivery or impersonation problem.
Keep the review lightweight. The useful output is a short list of confirmed senders, open questions, owner names, and next actions. If that list is understandable to IT, finance, marketing, and leadership, the email security program is much easier to maintain.
What good looks like
A good response is calm, evidence-based, and focused on reducing repeat abuse rather than just closing the single report.
Where Lappu AI fits
Teams that want help turning these ideas into a working DMARC, DKIM, and SPF plan can review the email security work at Lappu AI.