Labs / Security Basics

Security BasicsThe medal for finishing it

Road 15 of 33

Security Basics

The ideas every defender starts from: what security protects, how risk is scored, why defence comes in layers, what keeps a test legal, how an alert becomes a verdict, who attacks and why, the kinds of weak spot they use, what each kind of control is for, how to read an advisory and decide what to patch first, how one break-in comes apart into stages that a control can break, and how to review a new system's design before it goes into use.

3 groups · 11 labs · builds on Network Basics

Start this road

Security foundations

The ideas every defender starts from: CIA, risk, layered defence, scope, triage.

  1. 01 The CIA triad: the three promises a system makes Break confidentiality, integrity and availability on one real server, and see the fix each one needs.
  2. 02 Risk scoring: turn a pile of findings into a ranked queue Score four real findings on two of a studio's servers by likelihood and impact, checked from inside and outside, then rank them.
  3. 03 Defense in depth: why one lock is never the whole wall Walk an attacker's path to a bike shop's customer data through three controls, and watch each one stop a different step.
  4. 04 Rules of engagement: the line between a test and a crime Read a signed scope for a bank's pentest, sweep only what it names, test inside its rules, and stop at the boundary.
  5. 05 Alert verdicts: true, benign or false positive? Triage two look-alike port-scan alerts, one from a sweep you run yourself, with the firewall log and the asset inventory.

Threats and weaknesses

Who attacks, weak spots, controls, patch order, and an attack's stages.

  1. 01 Threat actors: who is behind an attack, and why Read the logs of three incidents at one small studio and sort them by attacker: an automated scan, an insider, a patient outsider.
  2. 02 Types of vulnerabilities: five findings, five kinds of fix Audit one inherited ticket server and sort its five findings by kind: missing patch, default password, open port, unchecked input and exposed key.
  3. 03 Types of security controls: what each control is for Go through one radio station's list of controls and sort each by its job: preventive, detective, corrective, deterrent, directive or compensating.
  4. 04 CVEs and advisories: four criticals, one to patch tonight Read a vendor advisory, take its CVSS vector apart, then check four machines to find the one that is affected and exposed.
  5. 05 Kill chain: the stages of an attack, and where each one breaks Read what one closed break-in left behind, sort it into six stages, and name the control that would have ended it at each.

Design review

Review a new system's design before it goes into use.

  1. 01 Threat modelling: four questions before a new app goes live Review a new loan-desk app before it goes live: draw its data flows, mark trust boundaries, ask STRIDE's six questions and confirm three gaps.

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