Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Triage is the rapid assessment that turns an alert into a decision: benign, true positive, or needs escalation. It is the single highest-volume activity in a SOC and the one most worth standardising.

What Is Alert Triage?
Triage is borrowed from emergency medicine, and the analogy holds: limited attention, more arrivals than capacity, and decisions made on partial information under time pressure. In a security operations centre it means taking an alert, establishing quickly whether it represents real malicious activity, and routing it accordingly. Most alerts are resolved here and never become incidents.
Every triage ends in one of four places, and naming them precisely matters because the numbers are used to judge detection quality.
Teams that collapse the first two categories end up tuning out real detections, since “false positive rate” then includes everything analysts found uninteresting.
A disciplined analyst works through roughly the same sequence regardless of the alert type. What fired, and what does the rule actually look for? Which host and which identity are involved, and what are they for? Is there a change record, a scheduled task, or a known project that explains this? What happened on that host in the ten minutes either side? Has the same rule fired for this entity before, and what was the outcome? Is the destination or the file known, and from where?
Documenting that sequence as a per-rule triage note is the highest-value writing a detection engineer does. An alert that arrives with a paragraph explaining what it means, what normally causes it, and which three searches to run cuts triage time by more than any tooling change.
Set a target per severity band and measure against it. Ten to fifteen minutes for a routine alert is typical once enrichment has done the obvious lookups. The useful metric is not average handling time on its own, which rewards closing things quickly, but handling time read alongside the proportion of cases that are later reopened and the proportion escalated. A team whose average time drops while reopenings rise is not getting faster; it is getting sloppier.
Triage degrades predictably under volume, which is what alert fatigue describes. Rotating analysts between triage, hunting, and detection work keeps judgement sharp and gives people a career path beyond the queue. It also closes the feedback loop, because an analyst who has spent a week writing rules triages differently.
UK organisations assessed against the NCSC Cyber Assessment Framework will find this in principle C1, which asks not whether alerts are generated but whether they are examined by people with the time, tooling, and skills to reach a sound conclusion. That is a fair description of triage, and a useful way to frame the staffing argument. At Privia Security, we build triage guidance alongside every detection we deliver through our managed security services.
A false positive means the rule misfired: the activity did not match what the detection was written to find. A benign true positive means the rule worked correctly but the behaviour was authorised, such as an administrator running a remote execution tool. The distinction drives different fixes. False positives need the logic corrected; benign true positives need scoped exceptions or a change to the underlying practice.
It is the most commonly outsourced SOC function and often sensibly so, because 24-hour coverage is expensive to staff internally. What cannot be outsourced is the business context: a provider cannot know that a particular server is being migrated this week. Successful arrangements give the provider access to change records and asset criticality data, and keep escalation decisions with a named internal contact.
Record it as inconclusive, state precisely which data would have resolved it, and raise that as a visibility gap. Guessing in either direction is worse: closing it as benign hides a possible compromise, and escalating everything unresolved overwhelms the response team. Inconclusive rates above a few per cent are a strong argument for additional log sources or longer retention.
Time from alert creation to first analyst decision, the percentage of cases reopened after closure, the escalation rate, and the inconclusive rate. Read them together. Falling handling time with rising reopenings indicates rushed work, while a very low escalation rate combined with incidents discovered by other means suggests real detections are being closed as noise.
You May Be Interested In These
Cybersecurity Terms
17 November 2026
What Is the Difference Between Authentication and Authorisation?
Read More
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.