Topic · Investigation
Email artifact preservation
Email artifact preservation retains original message evidence for reliable incident analysis.
How it works
Investigators collect raw RFC 5322 messages, headers, attachments and related event logs with access controls.
What can go wrong
Screenshots alone omit routing and cryptographic detail needed for accurate authentication analysis.
What to check or do
Save original message sources securely and track collection time, provenance and authorized access.
Practical scenario
An employee forwards a suspicious email to security as an inline screenshot. The screenshot shows the lure but omits original Received, Authentication-Results and MIME attachment details, weakening trace analysis.
Verification checklist
- Export the original message in a raw message format when possible.
- Preserve complete headers and attachment hashes securely.
- Record collector, timestamp, source mailbox and handling history.
- Use copies for analysis and restrict access to sensitive recipient data.
How to investigate Email artifact preservation
- Signal to investigate
- A phishing report is forwarded as plain text and key original headers are lost.
- Evidence to collect
- Preserve the original RFC 5322 message, hashes, delivery IDs and acquisition timestamps.
- Common wrong conclusion
- Screenshots alone cannot preserve authentication or transport metadata needed for forensics.
Put this into practice
Run a focused check, then explore protection if your domain needs it.