thinQtankLABS

Authentication Attack Detection & Incident Response

Respond to a Authentication Weakness (brute force) compromise (CWE-307) in Acme Accounts. Reconstruct the timeline from the access and service logs, scope the impact, engineer a detection rule tuned past a benign look-alike, then contain, eradicate, verify and report.

Intermediate 21 guided steps 6 tasks About 75 minutes Runs in your browser

Skills you will practice

  • Log analysis
  • detection and IR; Incident-handling lifecycle; Authentication Weakness (brute force) detection and IOCs; Security Operations domain

The scenario

A Acme Accounts host (CWE-307 open in the login feature) logged a burst of failed logins against many accounts from one source (a dictionary attack). You are the responder.

What you will do

  1. Open and classify the incident4 steps

    Open the incident · Read the alert · Read the ticket · Classify it

  2. Reconstruct the timeline3 steps

    Pull the attacker's requests · Correlate the service log · What is the impact?

  3. Scope the exposure3 steps

    Inspect the triage capture · What persistence/impact? · Record IOCs

  4. Engineer a detection rule4 steps

    Study the sample · Write a rule · Test and tune · Why this pattern?

  5. Contain, eradicate, verify5 steps

    Contain · Eradicate the foothold · Verify the host · Confirm detection holds · …

  6. Report2 steps

    Write the report · Why eradicate, not just fix?

How this lab works

A real Linux-style console. Commands run against real files, so hashes, hex dumps and comparisons give real results.

A file browser where you can place evidence into the lab, either the file provided or one of your own.

Reset a single step, a whole task or the entire lab. The environment is rebuilt so you can try again cleanly.

Progress saves after every step. Close the tab and come back later; your files and answers are waiting.