Labs / Threat Frameworks

Threat FrameworksThe medal for finishing it

Road 20 of 33

Threat Frameworks

The shared models a defender reasons in: map an intrusion's techniques onto MITRE ATT&CK, pivot a single event into an activity group with the Diamond Model, and audit a host against a baseline, mapping every gap to the CIS Controls and the NIST Cybersecurity Framework.

1 groups · 3 labs · builds on Security Basics

Start this road

Name, place and map: the analyst's frameworks

Map an intrusion, pivot on an event, audit a host.

  1. 01 ATT&CK: map one intrusion to the matrix Label each step of a real hands-on-keyboard intrusion with its ATT&CK tactic and technique id, and see why a shared map beats a prose write-up.
  2. 02 Diamond Model: pivot one event into a campaign Fill the Diamond Model's four corners for one intrusion, then pivot along the edges until a single alert becomes a two-host activity group.
  3. 03 Control baselines: audit one host, map every gap Audit one host against a written baseline, then map every pass and fail to its CIS safeguard and NIST CSF subcategory.

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