Cybersecurity & Information Security

End-to-End Phishing Investigation

6 min readPublished: August 5, 2026

Professional visual illustration on Phishing investigation in the field of Incident Response and DFIR

Quick answer

Phishing investigation is a controlled process that balances damage containment with evidence preservation. Document the source, time, and tools, save Hashes, build a Timeline, and separate fact, interpretation, and decision.

Incident Response and DFIR require a balance between speed, evidence preservation, business continuity, and documentation. The correct action is one that can be explained, reproduced, and reviewed after the incident. This article focuses on Phishing investigation and is intended for SOC analysts and students. The goal is to provide a methodology that can be applied in practice, during professional interviews, and in a work environment, without being limited to a dictionary definition.

The main challenge is that data is almost always incomplete. The Received chain, Return-Path, and SPF can indicate a direction, but their meaning depends on time, asset, user, and expected activity. Therefore, we will build the investigation around an investigative question, required evidence, and a clear completion criterion.

The practical scenario in the article is: A simulated Phishing scenario with a message, link, and suspicious login. All examples are laboratory data or process descriptions. When dealing with Penetration Testing, Web, or Cloud, work only with explicit permission, a defined Scope, and the ability to stop the test.

Report Intake and Safety

The topic 'Report Intake and Safety' is a central part of Phishing investigation work. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic use of tools without understanding the goal.

In practice, record the Received chain, Return-Path, SPF, DKIM, DMARC, compare them to expected behavior, and define at least one Pivot. The result should be verifiable by another analyst, including limitations and next steps.

Headers, Sender, and Authentication

In Phishing investigation, identity and authorization are two different questions: who is the client, and what are they allowed to do on the resource. Check Roles, Claims, Session, Object ownership, and changes throughout the lifecycle, and do not be satisfied that the user is 'logged in'.

A test matrix includes an anonymous user, a regular user, an object owner, another user, and an administrator. For each action, compare the Response and server-side impact. Changing an identifier or Header is only a testing means; the evidence is that the server approved or rejected an action contrary to policy.

Links and Files

The topic 'Links and Files' is a central part of Phishing investigation work. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic use of tools without understanding the goal.

Scoping within the Organization

The topic 'Scoping within the Organization' is a central part of Phishing investigation work. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic use of tools without understanding the goal.

Containment, Communication, and Lessons Learned

The response to Phishing investigation should mitigate risk without deleting necessary evidence. Start with a reversible and focused action, confirm ownership and authority, and document time, perpetrator, and outcome.

Long-term remediation addresses the root cause: permissions, configuration, Validation, Telemetry, process, or training. After implementation, perform Retest and monitor for signs of recurrence, instead of just closing the Ticket.

Unique Examination Points

In this topic, it is recommended to build a focused evidence map in advance. The main examination points are: Received chain, Return-Path, SPF, DKIM, DMARC, Message-ID, mailbox rules. The list is not an automatic Checklist; each item is chosen because it can link an entity, action, and time or explain legitimate behavior.

Received chain: Define the expected value, what would be considered anomalous, and what additional source would confirm the finding.
Return-Path: Define the expected value, what would be considered anomalous, and what additional source would confirm the finding.
SPF: Define the expected value, what would be considered anomalous, and what additional source would confirm the finding.
DKIM: Define the expected value, what would be considered anomalous, and what additional source would confirm the finding.
DMARC: Define the expected value, what would be considered anomalous, and what additional source would confirm the finding.
Message-ID: Define the expected value, what would be considered anomalous, and what additional source would confirm the finding.

When one of the focal points is unavailable, document the gap and choose an alternative. For example, if the Process identifier is unstable, you can use time, Host, User, and Parent; if the Payload is encrypted, use Metadata, volume, frequency, and TLS/DNS context.

Recommended Workflow

Define a Scope and one working question regarding Phishing investigation.
List the necessary data sources and evidence: Received chain, Return-Path, SPF, DKIM.
Create a brief Baseline of normal behavior or expected outcome.
Perform the minimum test in a laboratory environment and save time, input, and output.
Build a Timeline or comparison table and separate fact from interpretation.
Pivot to an additional source to confirm or refute the initial explanation.
Summarize the decision, limitations, recommended action, and Retest criteria.

Practical Scenario

The chosen scenario is a simulated Phishing scenario with a message, link, and suspicious login. The purpose of the exercise is not to prove attack capability, but to practice safe collection, comparison, and documentation. Before starting work, define simulated data, a time window, and an expected outcome.

At the end of the exercise, a deliverable that another analyst or tester can review should be submitted: a screenshot or Export of the evidence, a brief Timeline, initial hypothesis, corroborating evidence, limitation, and recommendation. When there is insufficient evidence, the correct conclusion is that the scenario was not proven.

Stage	What is performed	Deliverable
Preparation	Define Scope, time, and target. List which fields or evidence from Received chain, Return-Path, SPF are expected to appear.	Brief test plan
Data Generation	Perform a safe and simulated action related to Phishing investigation, without real information or impact on a production system.	Controlled Event/Request/Flow
Collection	Collect the raw evidence and context from an additional source. Verify Time zone, identifiers, and integrity.	Two linked pieces of evidence
Analysis	Write what each piece of evidence proves, what it does not prove, and what the possible legitimate explanation is.	Interim conclusion
Completion	Choose closure, escalation, Finding, or Tuning; add recommendation and Retest.	Documented deliverable

Practical Checklist

Check and document: Evidence source.
Check and document: Collection time and time zone.
Check and document: Hash and Chain of Custody.
Check and document: Tool and version.
Check and document: Response actions performed.
Check and document: Timeline and working assumptions.
Note Time zone, tool version, and collection time.
Save raw data before filtering or modifying.
Write what the finding proves and what is still unknown.
Define owner and next action with a deadline.

Common Mistakes

Modifying the system before preserving evidence.
Not documenting the time zone.
Not calculating Hash.
Mixing fact and conjecture.
Not documenting who held the evidence.
Prioritizing theoretical completeness over immediate damage containment.

Summary and CTA

End-to-End Phishing investigation is a topic that combines technical knowledge with work discipline. Start with a question, collect only relevant evidence, preserve context and time, and choose an action that can be justified and re-examined.

In HPI's Cybersecurity & AI track, these principles are practiced using systems, logs, and labs. A natural progression is to move on to the linked articles, complete the lab exercise, and save the output as part of a professional portfolio.

FAQ

Does Phishing investigation alone prove an attack or vulnerability?

No. It provides a signal or finding that requires context, validation, and an additional source. A professional conclusion relies on a sequence of evidence and consistency with expected behavior.

What to do when some data is missing?

Document the missing information, check an alternative source, and reduce the confidence level. Do not complete fields based on assumptions or present Unknown as legitimate.

How long should evidence be kept?

The time depends on policy, regulation, cost, and the type of incident. It is important to define Retention, Legal hold, and the ability to export evidence in a verifiable format in advance.

How to practice without endangering a real system?

Use virtual machines, simulated data, CTF, or a dedicated lab. In authorized tests, define Scope, Stop conditions, and backup before starting work.