Start here: choose your path

About 2 min read

On this page

ASSURED is one method read by very different people. An analyst with an alert open needs the desk card now; a new analyst needs the chapters in order; a SOC lead needs the operating pages. Pick the route that matches why you are here. Every route ends in the same seven questions.

On shift now

You have an alert open and minutes, not hours.

  1. The one-page reference: the seven questions, the escalation criteria, the verdict vocabulary and the priority bands on one card.
  2. The fast path: pick the depth (Level 0, 1 or 2) and run the eligibility gate before you close anything.
  3. When an identity is involved, the identity-persistence sweep.

Learning triage

Read the introduction, then the seven chapters in order. Each chapter closes with a worked example on the same cases and a quiz. Reading times cover each chapter’s pages except the quiz, at a steady 230 words a minute; a first read with the exercises takes longer.

ChapterQuestionReading time
AlertWhat fired, and why?about 75 min
SubjectWho is involved?about 1 hr 45 min
ScopeWhere are the lines?about 80 min
UncoverWhat does the evidence say?about 85 min
RiskHow bad is it, and how confident are we?about 50 min
Escalation decisionClose or escalate, and who needs to know?about 80 min
DocumentationWhat did we decide, and what did we learn?about 50 min

Then the case files put each worked case back together, and cognitive traps names the reasoning failures the method is built to catch.

Leading a SOC

  1. Adopting ASSURED: rollout, roles and maturity.
  2. Measuring triage: the metric set and how each metric gets gamed.
  3. Shift handover and operating variants: shifts, MSSP and MDR models, the one-person SOC.
  4. Governing automated triage: what an AI agent may close, and under which controls.

Teaching

  1. Teaching ASSURED: sessions, routing with a pre-assessment, and assessment design.
  2. Hands-on exercises and telemetry labs for practice.
  3. The facilitator kit for grading and the capstone.

Detection engineering

  1. Triage and detection engineering: what triage owes detection engineering, and the tuning request.
  2. How detections work and alert provenance: what an analyst can and cannot learn from a rule.
  3. What a benign close teaches: turning closes into tuning.

Evaluating ASSURED

  1. How ASSURED compares with incident-response frameworks and SOC models.
  2. Standards mapping: NIST, ISO, SANS DAIR, CERT and FIRST, with the records an auditor can sample.
  3. Development and evidence: what is established, what is not, and the planned evaluation.

Technical details verified . Product names, defaults and retention change; check your own tenant.

Edit this page on GitHub Report a correction