Labs / Logs & SIEM

Logs & SIEMThe medal for finishing it

Road 21 of 33

Logs & SIEM

The defender's desk: sensors that write down what crossed the wire, and a SIEM that finds the attack in it.

2 groups · 6 labs · builds on Observability

Start this road

The analyst box

Find a guessed-in SSH login across a host log and the SIEM.

  1. 01 Auth logs: the login that should not have worked Read a jump host's auth log, forward it to the SIEM, and tell a guessed-in login from an engineer's own.
  2. 02 Triage a captured attack offline Record a web server's traffic to a file, then triage it offline with Suricata, jq and tcpdump to find the attack.
  3. 03 Correlation: one intruder, scattered across the logs Join a SIEM's alerts, connections and requests by one source address to tell an intruder's whole path from a clerk's ordinary night.
  4. 04 Firewall logs: a port scan read from the drop log Hunt a port scan in a firewall's drop log through the SIEM, then close the door the scan found open.

Automate the response, hunt the beacon

Answer an alert automatically, then hunt an implant by its flows.

  1. 01 SOAR: a playbook that answers an alert on its own Turn a web-exploit alert into an automatic block at the gateway, record the action, and keep an authorised scan from locking out a real user.
  2. 02 Beaconing: catching an implant by the shape of its flows Hunt an implant that calls home on a timer by its flow pattern: chatty, byte-identical, and on a clock.

What its labs use

Concepts

Commands

Learn it on real machines.

Every lab is a small network of real Linux machines in your browser. Sign in with Google or email to start.

Start this lab