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?
- IntermediateLevel
- 25 minAbout
- New detailsEvery attempt
- KQL or SPLQuery language
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
- Read the escalation from an L1 colleague and the events they attached.
- Hunt the logs in KQL (Microsoft Sentinel) or SPL (Splunk) and pin the evidence.
- Find the root cause and scope the incident: which accounts and hosts are affected.
- Map what you found to MITRE ATT&CK, set the severity and choose the response.
- Get a debrief: what happened, the evidence you missed, and what the attacker does next if you were wrong.
Logs you will query
| Microsoft Sentinel | Splunk |
|---|---|
SigninLogs | index=azure sourcetype=azure:monitor:aad |
EmailEvents | index=o365 sourcetype=o365:reporting:messagetrace |
WebProxy_CL | index=proxy sourcetype=cisco:cloud_security:proxy |
Sysmon | index=sysmon sourcetype=XmlWinEventLog |
AuditLogs | index=azure sourcetype=azure:monitor:aad |
SecurityEvent | index=wineventlog sourcetype=XmlWinEventLog |


