Topic · Threats

Phishing

Phishing is a deceptive message or interaction intended to obtain credentials, money or sensitive information.

Email Security Glossary·Practical guidance
Share this definition LinkedIn X WhatsApp Email
01 / How it works

How it works

Attackers impersonate trusted senders or create urgency through links, attachments and conversation tactics.

02 / What can go wrong

What can go wrong

Authentication can stop some domain spoofing but cannot detect every compromised or lookalike sender.

03 / What to check or do

What to check or do

Train reporting workflows, protect accounts with MFA and validate unusual requests.

Practical scenario

Practical scenario

A recipient receives a realistic invoice request linking to a site that visually copies a supplier’s portal. The sender display name resembles the supplier, but the actual domain differs. A technically authenticated attacker-controlled domain is not proof the invoice is genuine.

Verification checklist

  1. Inspect full sender and destination domains without trusting display names.
  2. Verify urgent payment or credential requests through a known independent channel.
  3. Preserve full headers, URLs and screenshots for investigation.
  4. Use user reporting and domain monitoring alongside SPF, DKIM and DMARC controls.
Practical diagnosis

How to investigate Phishing

Signal to investigate
A convincing login page appears in an email that passes authentication for an attacker-owned domain.
Evidence to collect
Inspect requested action, destination URL, domain ownership and account-sign-in evidence.
Common wrong conclusion
Passing SPF, DKIM and DMARC does not make an unrelated malicious sender safe.

How to interpret the evidence

A malicious actor may send authenticated messages from a domain they control, or use a real account compromised through stolen credentials or tokens. Consequently a passing authentication summary cannot distinguish benign from harmful intent. The meaningful signal may be an anomalous request, deceptive URL, suspicious attachment or changed payment instruction.

What to change and how to verify it

Verify sensitive actions through independent channels. Preserve the original message and evidence, isolate unsafe URLs, and review affected account/session activity when compromise is plausible. Report or block domains using accurate artifacts instead of relying on visual brand similarity alone.

NEXT STEP

Put this into practice

Run a focused check, then explore protection if your domain needs it.