← All projects

SECURITY OPERATIONS · INVESTIGATION & DETECTION

Email Security
& Threat Hunting

Investigated phishing and spoofing incidents, validated threats with DNS analysis and sandbox environments, and wrote targeted rules and Regex detections to identify malicious patterns.

Phishing analysisDNS analysisSandbox testingRegexDetection rules
Contributions, impact & lessons

Contributions. Analyzed sending patterns and targeted high-volume spam campaigns to block repeat attempts before messages reached inboxes.

Impact. Improved malicious-email detection, reduced employee exposure to malicious mass emails, and strengthened enterprise email security.

What I learned. How attackers use spoofing and phishing, how real-world incident investigation works, and why layered security controls matter. Sending patterns help reveal campaigns beyond individual messages.

SYNTHETIC WALKTHROUGH

From a suspicious message to a documented decision.

This fictional example illustrates my investigation approach. It is not a workplace incident or a measured project result. Domains ending in .example are illustrative.

  1. 01 / COLLECT

    Preserve evidence

    Record message headers, sender and reply-to addresses, URLs, timestamps, and recipient scope without opening links on a normal workstation.

  2. 02 / CORRELATE

    Test the explanation

    Compare identity, authentication results, link destination, and business context. Treat any single signal as a lead rather than a verdict.

  3. 03 / DOCUMENT

    Decide and escalate

    Record the evidence, confidence, scope, and proposed action. Follow approved procedures for containment and further analysis.

Illustrative invoice email review
ObservationInterpretationNext check
Display name says Finance; reply-to is [email protected].Identity mismatch warrants investigation; it is not sufficient proof by itself.Validate the sender through a known contact channel.
Visible link text names an internal portal; the destination is login-review.example.Destination mismatch suggests possible credential collection.Inspect the URL in an approved analysis environment.
Message urges immediate action on an unexpected invoice.Urgency and an unexpected request strengthen the concern when combined with technical evidence.Check related messages and document recipient scope.

Example disposition: Suspected phishing; escalate for approved containment and URL analysis. No credential submission or malware execution is assumed.

See the investigation runbook template ↗