JETPLAIN / FIELD NOTES / 003
← Cyber Lab

BY JETPLAIN /

Your First $0 SOC Lab: Investigating a Windows Sign-In

Cyber Lab 001: a 15-minute introduction to Windows authentication evidence.

You don't need a rack of servers to start thinking like a security analyst.

A Security Operations Center (SOC) investigates signals that something unusual may be happening.

One of the first places an analyst might look is authentication activity.

Windows can record successful and failed sign-in events in its Security log.

Two useful event IDs are:

  • 4624: A logon session was successfully created
  • 4625: A failed logon attempt

These events aren't proof of an attack. They're evidence that needs context.

FIELD NOTES / 01

The 15-minute investigation

FIELD NOTES / 02

Minutes 0–5: Open the evidence

  • Press Windows + R.
  • Enter eventvwr.msc.
  • Open Windows Logs → Security.
  • Select Filter Current Log.
  • Enter 4624,4625 in the Event IDs field.

If the events are missing, don't change audit settings yet. Logging depends on Windows configuration, retention, and permissions. If you cannot access the Security log, stop here and try the fictional timeline exercise instead.

If you do not find a failed sign-in, examine one successful event instead. The goal is to understand the evidence, not manufacture suspicious activity.

FIELD NOTES / 03

Minutes 5–10: Examine the events

Select a recent event and examine its details.

Look for:

  • Timestamp
  • Event ID
  • Account name
  • Logon type
  • Source network address, if present
  • Failure reason or status, when available

Some entries involve Windows services, background processes, or routine network activity.

For example, logon type 2 generally means an interactive sign-in, while type 3 indicates a network logon. Type 10 relates to Remote Desktop sessions.

The event type alone does not establish malicious activity.

FIELD NOTES / 04

Minutes 10–15: Write your analyst finding

Answer these questions:

  • What happened?
  • Which account was involved?
  • When did it happen?
  • Was it a success or failure?
  • What additional evidence would help determine whether it was suspicious?

Example finding (fictional):

At 14:32, Windows recorded a failed logon event for a local account. The event alone does not establish malicious activity. Next steps would include checking nearby authentication events, expected account activity, and relevant device context.

FIELD NOTES / 05

Check your understanding

You see five failed logons followed by one successful logon.

Is that an attack?

Answer: Not necessarily. The pattern warrants investigation, but could also result from a legitimate user correcting a password. Examine the account, timing, logon types, source details, and surrounding events.

FIELD NOTES / 06

Safety and privacy

Investigate only computers you own or are authorized to administer.

Do not deliberately lock accounts, generate repeated failed logons, change audit policies, or disable security controls for this introductory exercise.

Security logs can contain usernames, device names, and network addresses. Redact identifying information before sharing screenshots.

What you learned: How to find authentication evidence, interpret basic Windows events, and separate an observation from a conclusion.

Next lab: Build a simple sign-in timeline and identify events that deserve further investigation.

FIELD NOTES / 07

Official references

Reference definitions checked November 9, 2026. These are educational exercises, not reports of a tested Jetplain incident.

Browse Cyber Lab

Continue the lesson

Back to the Field Guide