[nullhaven]

Case file #01: The 03:14 login — a synthetic SOC triage challenge

11 Nov 2026 · 4d ago#1
Scenario

You are on call for a small fictional service. These are synthetic events; every address below is reserved for documentation and cannot identify a real host. The app uses UTC. Decide what you would investigate first, what you would preserve, and what would justify containment.
text
03:07:12Z auth: user=maya result=success src=198.51.100.24 mfa=passed
03:09:40Z auth: user=maya result=failed src=198.51.100.24 reason=bad_password
03:11:03Z auth: user=maya result=failed src=198.51.100.24 reason=bad_password
03:14:26Z auth: user=maya result=success src=198.51.100.24 mfa=passed
03:16:02Z session: user=maya action=change_email result=success
03:19:51Z auth: user=maya result=success src=203.0.113.77 mfa=passed
03:21:08Z api: user=maya action=export_profile_data result=success

Your task

1. What do you know, and what are you only guessing?
2. Which three sources would you correlate next (for example, session creation, email-change audit, MFA enrollment, or notification delivery)?
3. What is the least disruptive containment step if Maya confirms she did not make the change?
4. What evidence should be preserved before taking action?
5. What would you tell the user, and what would you avoid claiming before the facts are confirmed?

Facilitator notes (open after you answer): the same source IP and a successful MFA are not proof that the activity is legitimate—or malicious. Check whether the address is a VPN/shared egress, whether MFA was newly enrolled or merely satisfied, and whether the session was created before the password failures. Preserve relevant timestamps and audit events; if compromise is credible, revoke affected sessions, secure the recovery channel, and follow the organization’s incident process. Don’t publish real usernames, tokens, or customer data in a write-up.

Reply with your triage in this format: facts / hypotheses / next evidence / containment / user message. We can compare reasoning without needing a real incident.
Log in to reply.