The Root Brief #0: How we triage vulnerabilities

Before the first weekly issue, here is exactly how we decide what goes in, how we prioritise it, and what each label means.

2 min readIntermediate

Welcome to The Root Brief. Every week we tell you what attackers are actually exploiting, what to patch first and which research is worth your time. Before issue #1, here is how we make those calls, so you can trust them and adapt them to your environment.

What goes into an issue

  1. Triage: the vulnerabilities that matter this week, each with a patch priority.
  2. Research: three to five pieces of technical research worth reading, with one line on why.
  3. One tool: an open-source tool or detection resource we have actually tried.

The signals we use

CVSS measures how bad a vulnerability could be. It doesn't tell you whether anyone is exploiting it. So we combine several signals:

  • CISA Known Exploited Vulnerabilities (KEV): confirmed exploitation in the wild. The strongest signal there is.
  • EPSS: the Exploit Prediction Scoring System's estimate of how likely exploitation is in the next 30 days.
  • Vendor and CERT advisories: including CERT-In for organisations in India.
  • Exposure: whether affected products are commonly internet-facing.
  • CVSS: used for context, never on its own.

Patch priority labels

Label Meaning Act within
PATCH NOW Exploited in the wild or in KEV, and commonly exposed Days
THIS WEEK High chance of exploitation, or a public proof of concept This patch cycle
SCHEDULED Serious, but harder to exploit or less exposed Normal patching
MONITOR Worth knowing about No action unless your environment is unusual

How to use the labels

The labels are a starting point. A SCHEDULED bug in a system that holds your crown jewels may deserve PATCH NOW for you. A PATCH NOW bug in a product you don't run is noise. Map each item to your own asset inventory before you act.

Sources worth bookmarking

The first weekly issue lands soon. If a colleague would find it useful, forward it. They can subscribe on the home page.

HackersRoot Research · Research team

The HackersRoot research team investigates attack techniques across AI systems, cloud and identity, and enterprise networks, then publishes the detections and hardening guidance that stop them.

More from HackersRoot →

Related research