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.
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
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.
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.
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.
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?
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.
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.
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.
FAQ
Frequently asked questions
What is a false positive?
An alert that fired correctly by rule but the activity was legitimate. Record why, so the rule can be tuned.
Should a junior analyst contain a threat?
Only the actions the playbook allows at their level, such as isolating a single client. Bigger actions go to the shift lead.
Keep learning
Related guides
What is a SOC?
Read more →Incident response: the first hour
Read more →SOC analyst shift handover
Read more →How to Set Up a WireGuard VPN Server for Remote Access
WireGuard is a fast, modern VPN with a small, auditable code base. Build a WireGuard server on Linux, add users with their own keys and route them only to the networks they need.
Read more →How to Scan Your Network for Vulnerabilities With Nmap and OpenVAS
Find open ports, outdated services and known vulnerabilities before attackers do. Discover hosts with Nmap, then run authenticated vulnerability scans with Greenbone OpenVAS and fix what matters first.
Read more →How to Build a Free SIEM With Wazuh for Network and Server Logs
A SIEM collects logs from servers, firewalls and switches in one place and alerts on attacks. Install Wazuh, add agents and syslog sources, and tune the first alerts.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.