Skip to content
CyberSimStart training
Illustration for the case: Phished user, token replay and internal phishing

Identity case

Phished user, token replay and internal phishing

A user clicked a doc-share link that was flagged after delivery. The domain is brand new. Did the attacker get in, and who else is affected?

Open this case

Free. Read the briefing as a guest; investigating needs a free account.

The alert

User clicked flagged link

Hey, jjohnson clicked a doc-share link that got flagged after delivery. Not sure if creds got phished, but the domain is brand new. Escalating to be safe.

From one version of the case: the company, the people and the details change with every attempt.

About this kind of alert

Adversary-in-the-middle phishing: a fake sign-in page relays the login and keeps the session, so a second factor alone does not stop it. Business email compromise often follows.

What you do

  1. Read the escalation from an L1 colleague and the events they attached.
  2. Hunt the logs in KQL (Microsoft Sentinel) or SPL (Splunk) and pin the evidence.
  3. Find the root cause and scope the incident: which accounts and hosts are affected.
  4. Map what you found to MITRE ATT&CK, set the severity and choose the response.
  5. Get a debrief: what happened, the evidence you missed, and what the attacker does next if you were wrong.

Logs you will query

Microsoft SentinelSplunk
SigninLogsindex=azure sourcetype=azure:monitor:aad
EmailEventsindex=o365 sourcetype=o365:reporting:messagetrace
WebProxy_CLindex=proxy sourcetype=cisco:cloud_security:proxy
Sysmonindex=sysmon sourcetype=XmlWinEventLog
AuditLogsindex=azure sourcetype=azure:monitor:aad
SecurityEventindex=wineventlog sourcetype=XmlWinEventLog

Part of

More identity cases