BY JETPLAIN /
Five Failed Logons and One Success
Cyber Lab 002: investigate six fictional authentication events without jumping to conclusions.
Six events. One account. Something worth investigating.
You're a junior SOC analyst reviewing authentication activity from a Windows workstation.
An alert identifies several failed logons followed by a successful one.
Is somebody guessing passwords? Or did an employee simply forget theirs?
Your job is to examine the evidence without jumping to conclusions.
The evidence
All events below are fictional training data.
- 09:14:02 — 4625 · account labuser · logon type 3 · source 192.0.2.25
- 09:14:08 — 4625 · account labuser · logon type 3 · source 192.0.2.25
- 09:14:15 — 4625 · account labuser · logon type 3 · source 192.0.2.25
- 09:14:22 — 4625 · account labuser · logon type 3 · source 192.0.2.25
- 09:14:30 — 4625 · account labuser · logon type 3 · source 192.0.2.25
- 09:14:39 — 4624 · account labuser · logon type 3 · source 192.0.2.25
The source IP belongs to a documentation-only address range. It is not an actual identified attacker.
Minutes 0–5: Establish the facts
Identify:
- Number of failures
- Number of successes
- Account involved
- Source IP
- Time between first and last event
- Logon type
Do not assign an attacker or motive yet.
Minutes 5–10: Develop hypotheses
Hypothesis A: Someone was attempting to guess the account password.
Hypothesis B: An authorized user or application had outdated credentials and eventually authenticated.
Hypothesis C: An automated process retried authentication until valid credentials became available.
Which explanation is most likely?
At this stage, we don't have enough evidence to know.
Minutes 10–15: Recommend next steps
Write a short incident note answering:
- What did you observe?
- Why might it matter?
- What evidence would distinguish the hypotheses?
- What should the analyst do next?
Consider examining related events, the account's expected behavior, the originating device, and whether the successful session performed unusual actions.
Try it: check your analysis
Work through the questions before you read the answer key.
Answer key
Observed: Five failures followed by one success, involving the same account and source over 37 seconds.
Why it matters: A successful authentication after repeated failures can indicate a credential-guessing attempt, but also has legitimate explanations.
Important context: Logon type 3 indicates network logon. These events do not establish that someone physically sat at the workstation.
Recommended disposition: Investigate further. Do not declare a confirmed compromise from this sequence alone.
Example analyst report
Title: Repeated Network Logon Failures Followed by Success
Severity: Undetermined
Evidence: Six authentication events affecting one account, originating from the same recorded source.
Assessment: Suspicious authentication pattern requiring context. No confirmed malicious activity based on the supplied records.
Next steps: Correlate with source-device activity, expected account usage, additional authentication records, and subsequent session behavior.
Jetplain takeaway: A pattern is a clue, not a verdict.
Next lesson: Build a detection rule that finds repeated authentication failures without flooding the analyst with false alarms.
Official references
Reference definitions checked November 9, 2026. These are educational exercises, not reports of a tested Jetplain incident.
