Skip to content
Tutorials Center
My learning

Topics

Lesson 7 of 37 ยท SOC Concepts and Roles

Alert Triage Workflow Step by Step

Learn a repeatable alert triage method: validate, enrich, scope, decide and document. Includes true/false positive vocabulary and a runnable scoring helper in Python.

Triage is the art of deciding quickly and correctly what an alert means. A consistent workflow prevents two costly mistakes: dismissing a real attack and spending an hour on a harmless event. This lesson gives you a five-step method you can apply to nearly any alert.

Vocabulary

Term Meaning
True positive (TP) Alert fired and the activity is really malicious
False positive (FP) Alert fired but the activity is harmless
Benign true positive The rule did what it should, but the activity is authorized (for example a scheduled vulnerability scan)
False negative A real attack produced no alert
True negative Normal activity, no alert

"Benign true positive" is useful because it tells you the rule works while the context needs an exception or documentation.

The five steps

flowchart LR
    A["1. Validate<br/>what exactly fired?"] --> B["2. Enrich<br/>who, what, where"]
    B --> C["3. Scope<br/>other related activity?"]
    C --> D["4. Decide<br/>close, escalate, contain"]
    D --> E["5. Document<br/>case notes"]

Write notes as you go, not at the end.

1. Validate

Read the rule logic and the raw events. Ask: did the condition really occur? Rules can misparse. Check timestamps and time zones.

2. Enrich

Add context to every entity in the alert:

  • User: role, department, usual login hours, privileged?
  • Host: owner, criticality, patch level, is it a server?
  • IP / domain: internal or external, reputation, first time seen?
  • File / process: hash reputation, signer, parent process.

3. Scope

Look around the alert. Same user elsewhere? Same source IP against other hosts? Same file hash on other machines? A single alert is often one piece of a larger picture.

4. Decide

  • Close: benign, with a short reason and, ideally, a tuning suggestion.
  • Escalate: possible incident, with a summary.
  • Contain now: if impact is clear and fast (for example, active ransomware), follow the playbook's containment steps.

5. Document

Record what you saw, what you checked, what you decided and why. Another analyst should be able to repeat your reasoning in two minutes.

A worked example

Alert: Failed logins then success for alice from 203.0.113.66.

  1. Validate: 10 failures in 20 seconds, then success. Real.
  2. Enrich: alice normally logs in from 198.51.100.10; 203.0.113.66 has never appeared for her; alice works day hours but this is 03:00 local time.
  3. Scope: the same IP failed against 4 other accounts; alice created a mailbox forwarding rule 2 minutes after login.
  4. Decide: true positive, likely account takeover. Escalate and contain: disable the account and revoke sessions.
  5. Document: all of the above with timestamps.
Python Triage scoring helper

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The weights are invented for teaching. Real SOCs derive theirs from experience and review them regularly.

Enrichment by lookup

Python Enrich an alert with asset and user context

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Common triage mistakes

  • Anchoring: deciding from the rule name before reading events.
  • Alert fatigue shortcuts: closing the tenth identical alert without checking.
  • Missing time zones: comparing local time with UTC.
  • Tunnel vision: investigating the alert only, never its neighbors.
  • No notes: the next analyst repeats everything.

Set a time box. If you cannot decide in about ten minutes at Tier 1, escalate with what you have rather than going down a rabbit hole.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a benign true positive?

    The detection is correct; the context makes it harmless. It may need an exception or documentation.
  2. 2. Which is step 3 of the workflow?

    Validate, enrich, scope, decide, document.
  3. 3. What does enrichment add to an alert?

    Enrichment attaches user role, asset criticality and reputation so you can judge impact.
  4. 4. Why time-box your triage?

    A time box forces a decision or an honest escalation instead of a long unproductive hunt.

Summary

  • Triage follows five steps: validate, enrich, scope, decide, document.
  • Know TP, FP, benign TP, FN and TN, and use them precisely.
  • Scoring and enrichment make decisions consistent but do not replace judgment.
  • Notes and time boxes make triage repeatable and safe.

Next: The SOC Technology Stack