Implementation

Preserving Email Evidence: Why Forwarding Destroys What You Need Most

· Regonance Cybersecurity · 8 min read

Forwarding a suspicious email strips the original message headers, sender authentication results, and routing information that investigators need to trace an attack. When an employee hits "Forward" instead of using "Forward as Attachment" or a dedicated reporting button, the organisation loses the forensic trail before the investigation even begins. In a regulatory environment where NIS2, DORA, CRA, and GDPR all demand documented evidence of incident detection and response, this is not a minor inconvenience — it is an evidence destruction problem.

What Forwarding Destroys

When you forward an email normally, your email client creates a new message that contains the body text and attachments of the original. What it does not carry forward includes:

Original Received headers. These headers trace every server the email passed through from sender to recipient. They reveal the originating IP address, intermediate relays, and delivery timestamps. This is how investigators determine where an email actually came from — not where it claims to have come from.

Authentication results. SPF, DKIM, and DMARC results are evaluated at delivery time and recorded in the headers. These tell investigators whether the sender's domain was spoofed, whether the email was tampered with in transit, and whether the sending infrastructure was authorised. A forwarded copy has new authentication results — for the internal forward, not the original delivery.

Original sender IP address. The IP address of the sending mail server is recorded in the Received headers. This is often the most direct indicator of the attacker's infrastructure. Forwarding replaces this with internal server addresses.

Message envelope data. The SMTP envelope (MAIL FROM and RCPT TO) is separate from the visible From and To headers. This envelope data, which can reveal BCC recipients and actual routing, is lost on forward.

Attachment metadata. Some attachment metadata, including original timestamps, may be altered when an email is forwarded depending on the email client.

In short: a forwarded suspicious email tells you what the attacker wanted the recipient to see. The original, with headers, tells you where the attacker actually is.

How to Preserve Email Evidence Correctly

Method 1: Forward as Attachment

Most email clients support "Forward as Attachment" — this sends the original email as an .eml or .msg file attached to a new message, preserving all headers and metadata.

Outlook (Desktop):

  • Select the suspicious email (do not open it)
  • Go to Home → More → Forward as Attachment (or press Ctrl+Alt+F)
  • Send to your reporting address

Outlook (Web):

  • Select the suspicious email
  • Click the three dots (⋯) → Forward as attachment
  • Send to your reporting address

Gmail:

  • Select the suspicious email
  • Click the three dots (⋮) → Forward as attachment
  • Send to your reporting address

Apple Mail:

  • Select the suspicious email
  • Go to Message → Forward as Attachment
  • Send to your reporting address

Method 2: Reporting Button / Plugin

Dedicated phishing reporting plugins (available for Outlook and Gmail) capture the original email in its complete format and send it to the security team automatically. These are the most reliable method because they eliminate user error.

Method 3: Save and Upload

  • Save the email as an .eml file (drag from inbox to desktop in most clients)
  • Upload to the designated secure location or attach to a report ticket
  • Do not rename the file or open it outside of a sandboxed environment

What to Preserve Beyond the Email

The email itself is the primary evidence, but a complete evidence package may include:

Evidence TypeWhy It MattersHow to Capture
Original email (.eml/.msg)Full headers, authentication results, payloadForward as attachment or save
ScreenshotsShows what the recipient saw — useful for non-technical audiencesScreenshot the email as displayed, including sender and subject
Timestamp of reportEstablishes awareness for regulatory purposesAutomatic when using a dedicated reporting channel
Reporter identityEnables follow-up investigation (who else received this?)Captured by the reporting system
Interaction recordDid the recipient click, reply, open attachments?Self-report by the employee; supplement with log data

Why Preserved Evidence Matters

For incident investigation

The original headers reveal the attacker's infrastructure — sending IP, mail server, domain registration. Without these, investigators are working blind, limited to analysing the visible content of the email rather than its technical origin.

For regulatory notifications

NIS2, DORA, CRA, and GDPR all require documented evidence of incident detection, assessment, and response. The preserved email with its timestamp is often the primary evidence for: when the organisation became aware, what the nature of the threat was, and what indicators of compromise were identified.

For law enforcement

If the incident is referred to law enforcement, preserved email evidence with an intact chain of custody is admissible. A forwarded copy, with altered headers and no chain of custody documentation, has significantly less evidentiary value.

For insurance claims

Cyber insurance claims increasingly require documented evidence of the attack vector and the organisation's response. Preserved email evidence supports the claim; destroyed evidence may give insurers grounds to question it.

Chain of Custody Basics

For evidence that may be used in legal or regulatory proceedings, maintain a basic chain of custody:

  1. Record who reported the email, when, and through which channel
  2. Preserve the original without alteration — do not open attachments, click links, or modify the message
  3. Store in a secure, access-controlled location — a dedicated evidence folder with restricted access, not a general shared drive
  4. Hash the preserved file — a SHA-256 hash at the time of preservation proves the file has not been altered since capture
  5. Document every access — who accessed the evidence, when, and for what purpose

This does not require forensic laboratory procedures. It requires a consistent process that a reasonable investigator or regulator would consider adequate.

Frequently Asked Questions


This article is part of the Every Report Matters knowledge series by Regonance Cybersecurity.

Related articles:

Download the free Every Report Matters Methodology Brief → Download (email required)

Download the free Every Report Matters Methodology Brief

The reporting gap, the 9-stage lifecycle, and why EU regulation now makes this urgent. 11 pages.

We publish practical cybersecurity reporting articles. No spam. Unsubscribe with one click.