Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Classification says what kind of incident you have; prioritisation says what order to deal with them in. Together they decide who gets woken up, what gets escalated, and what can wait until Monday.

What Is Incident Classification and Prioritisation?
A security team with ten open incidents and three responders has to answer one question before anything else: which of these matters most right now? Classification and prioritisation are how that answer is produced consistently rather than by whoever is loudest. Classification assigns an incident to a category — malware, phishing, unauthorised access, denial of service, data loss, policy violation. Prioritisation assigns it a severity that drives response times, staffing, and escalation.
Categories matter less for the individual incident than for the pattern across hundreds. Six months of consistently tagged data tells you that phishing accounts for most of your volume but almost none of your impact, that the same business unit generates a third of the policy violations, or that credential abuse is rising while malware detections fall. None of that is visible if every analyst invents their own label.
Established taxonomies save argument. The Reference Security Incident Taxonomy used widely among European response teams defines categories and sub-categories that map cleanly to reporting obligations, and mapping your own scheme to it makes information sharing with other teams considerably easier. Keep the list short enough that analysts pick the right one without deliberating, and add a technique reference to MITRE ATT&CK for the detail.
NIST SP 800-61 recommends scoring three dimensions rather than guessing a single number:
A malware infection on an isolated test machine scores low on all three. Ransomware on a file server holding client records scores high on all three. The interesting cases are the uneven ones: a quiet credential compromise with no functional impact at all can still be the most serious thing on the board, because the information impact and the trajectory are what count. That is why trajectory belongs in the assessment — severity should reflect where the incident is heading, not only where it is.
Four levels are enough. What turns them from labels into a working system is attaching concrete consequences to each one:
Write down the authority that comes with each level too. A severity one incident should give the incident lead the power to isolate production systems without waiting for a change advisory board, and that has to be agreed in advance by people with the standing to agree it.
Initial severity is set with the least information you will ever have. Build in formal review points so incidents can be upgraded and, just as importantly, downgraded without embarrassment. Teams that treat de-escalation as an admission of error end up running every incident at high severity, which exhausts responders and devalues the scheme.
Track the accuracy of your scoring in the lessons learned review: how often an incident was upgraded after initial triage, and what signal was missed. Those adjustments are the most direct feedback available on whether your criteria match your business. Our SOC maturation services include building and calibrating exactly this scheme against the way an organisation actually escalates.
Four works for most organisations: critical, high, medium, and low. Three tends to push too much into the middle, and five or more invites argument about boundaries during the minutes when speed matters. What distinguishes a useful scheme is not the number of levels but whether each one carries defined response times, contact lists, and decision authority.
The analyst who triages it sets an initial level against published criteria, and the incident lead confirms or changes it once scope is clearer. Avoid making severity a negotiation with affected business units, which systematically inflates it. Build in review points so the level can be raised or lowered as facts emerge without anyone having to defend the original call.
No. The reporting test under UK GDPR is whether a personal data breach is likely to result in a risk to people’s rights and freedoms, which is a separate judgement from your operational severity. Link the two in the playbook so that any incident involving personal data triggers an assessment, but do not let an internal severity label substitute for the legal test.
Classification records what kind of incident it is, which supports reporting, trend analysis, and the choice of playbook. Prioritisation records how urgent and serious it is, which drives response times, staffing, and escalation. Two incidents in the same category can sit at opposite ends of the severity scale, so both dimensions are needed.
You May Be Interested In These
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.