Hands-on tutorial

Tutorials · Security Operations

How to Triage a Security Alert: A Step-by-Step SOC Playbook

A repeatable way for a junior SOC analyst to handle any alert: confirm it is real, scope who and what is affected, decide severity, contain or escalate, and write it down so the next shift understands it.

Beginner15 min7 steps

Before you start

  • Read access to your SIEM or log platform
  • Access to NavCloud (or your network management system) for device and client lookups
  • The escalation list and on-call numbers for your organisation

Step by step

  1. Read the alert completely

    Note the rule name, time, source and destination, user, device and the raw event behind it. Never judge an alert by its title alone.

  2. Check whether it is expected

    Look for a change ticket, a scheduled scan, a known backup job or a test. Many alerts are legitimate activity at an unusual time.

  3. Enrich the evidence

    Look up the client in NavCloud: which site, switch port or access point, which VLAN, which user signed in. Check the external address against threat intelligence and your own block lists.

  4. Scope the activity

    Search the same user, device and address over the last 24 hours and 7 days. Is it one event or a pattern? One device or several?

  5. Set the severity

    Use a simple matrix: impact (what could be lost) against confidence (how sure you are it is malicious). High impact with medium confidence is still escalated.

  6. Contain if the playbook allows

    Typical first actions: move the client to a quarantine VLAN, disable the account, block the address on the NavGATE firewall. Act only within your playbook authority.

  7. Escalate or close with a note

    Write what you saw, what you checked, what you did and why. A good closing note lets anyone repeat your reasoning in two minutes.

Pro tips

  • Time-box triage: if you cannot decide in 15 minutes, escalate.
  • Tune noisy rules weekly instead of closing the same false positive every day.
  • Keep screenshots and query text in the ticket, not only conclusions.