Elevating Cyber Defense through Expertise and Innovation. Contact Us

 

Transform Your Use Cases Into High-fidelity Alerts

NSecurity Consulting > Uncategorized  > Transform Your Use Cases Into High-fidelity Alerts
3ddbdf9c 451e 49c1 b36b 106ef728fd47 NSecurity Consulting

Transform Your Use Cases Into High-fidelity Alerts

  1. Phishing Email + Endpoint Execution Correlation

Objective: Detect when a phishing email results in malicious execution on an endpoint.

Data Sources Involved

  • Email security gateway logs (O365, Proofpoint, Mimecast)
  • EDR logs (CrowdStrike, SentinelOne, Defender)
  • Host process logs (Sysmon, EDR telemetry)

Detection Logic

  1. Identify an email containing:
    • Suspicious attachment (macro-enabled docs, HTML smuggling, ISO/VHD)
    • Or a URL flagged by threat intelligence
  2. Extract sender, subject, and attachment hash.
  3. Correlate with:
    • File execution events on the recipient’s workstation
    • New binary spawned within 15–20 minutes of receiving the message
  4. Trigger alert when execution path matches known phishing → malware patterns.

Why It’s High-Fidelity:

It only fires when a phishing email leads to an actual action on the endpoint — not just when a suspicious email is received.

  1. Business Email Compromise (BEC) + Impossible Travel + MFA Abuse

Objective: Detect compromised email accounts used in fraudulent activity.

Data Sources

  • Email logs (O365 Unified Audit, Gmail)
  • Identity logs (Azure AD / Okta)
  • MFA provider logs
  • External threat intel

Detection Logic

  1. Email forwarding rules added (to external domains).
  2. Combined with impossible travel or new login location.
  3. Followed by MFA fatigue attempts or new MFA enrollment.
  4. Optional: suspicious mailbox searches (invoice terms, banking keywords).

Why It’s High-Fidelity

This is the exact chain used in modern BEC attacks. Very few false positives.

  1. Phishing Click → DNS Request → C2 Beacon Correlation

Objective: Identify when a user clicks a phishing link AND the endpoint reaches out to malicious infrastructure.

Data Sources

  • Email click logs (Proofpoint TAP, O365 SafeLinks)
  • DNS logs (Infoblox, Windows DNS, network sensors)
  • Firewall logs
  • Network proxy logs

Detection Logic

  1. User clicks a suspicious or TI-flagged URL.
  2. Within 5 minutes, workstation issues DNS query for the same or related domain.
  3. DNS lookup followed by outbound connection to high-risk IP or ASN.
  4. Additional weight if the domain was newly registered (NRD).

Why It’s High-Fidelity

You’re detecting action + intent + external communication, not just a click.

  1. Credential Harvesting Email + Unusual Authentication Behavior

Objective: Detect when a phishing page successfully steals credentials.

Data Sources

  • Email logs (phishing URL indicators)
  • Cloud auth logs (Azure AD, Okta)
  • Conditional Access logs
  • VPN logs

Detection Logic

  1. User receives or clicks an email with a login-themed phishing link.
  2. Within 1 hour:
    • New login from unknown IP/ASN
    • User-Agent mismatch (login from Firefox while user always uses Chrome)
    • Login from Tor/VPN/anonymizer
  3. Optional: mailbox rule creation or MFA reset attempts.

Why It’s High-Fidelity

Correlating suspicious email → suspicious login is extremely effective at catching credential theft early.

  1. Internal Phishing (Lateral Movement) Detection

Objective: Detect when an attacker uses a compromised account to send internal phishing emails.

Data Sources

  • Internal email logs
  • Identity logs (Azure AD / Okta)
  • Endpoint logs
  • Threat intel

Detection Logic

  1. Sudden spike in internal messages from a single user.
  2. Emails containing unusual links or attachment types.
  3. Sent to many recipients outside normal behavior patterns.
  4. Correlate with suspicious login from prior use case (#4).

Why It’s High-Fidelity

Internal phishing is a strong indicator of active lateral movement.

  1. Malicious Attachment → File Write → Child Process Explosion

Objective: Detect attachment-based malware droppers and loaders.

Data Sources

  • Email logs (attachment info)
  • Sysmon/EDR process creation
  • File write operations
  • Registry modification logs

Detection Logic

  1. User receives email with suspicious file extension.
  2. File is saved to disk.
  3. Execution leads to abnormal child processes — e.g.:
    • Word → PowerShell
    • PDF → cmd
    • Excel → rundll32
  4. Registry values or scheduled tasks created afterward.

Why It’s High-Fidelity

This maps directly to the MITRE ATT&CK kill chain (Initial Access → Execution → Persistence).

  1. VIP/Executive Targeting Detection

Objective: Detect targeted phishing against executives or finance staff.

Data Sources

  • Email logs
  • VIP user list / CMDB data
  • Threat intelligence
  • Identity logs

Detection Logic

  1. Email flagged by TI containing:
    • Finance-themed lures
    • BEC-style keywords
    • Malicious attachments or links
  2. Sent to VIP or finance department user.
  3. Correlate with authentication anomalies or mailbox rule creation.

Why It’s High-Fidelity

Executives are prime targets for BEC and ransomware initial access.

  1. Email Delivery Failure → Spam Campaign → Compromised Host

Objective: Detect compromised internal mail servers or endpoints distributing spam.

Data Sources

  • Email server logs
  • Firewall logs
  • Endpoint logs

Detection Logic

  1. Outbound emails from host → high volume of SMTP failures.
  2. Host simultaneously connecting to suspicious external SMTP servers.
  3. Endpoint shows signs of malware or unauthorized processes.

Why It’s High-Fidelity

Internal spam bursts are a reliable indicator of worm-like malware or compromised accounts.

Let us elevate use cases into high-fidelity alerts

Schedule a call