Most security news does not concern your company, and the skill is sorting quickly. Use four buckets: your own stack, your vendors, your sector, and everything else. Spend real time on the first two, skim the third for patterns, and let the fourth go. A short written list of what you depend on makes this possible.
Start with a dependency list
You cannot sort news without knowing what you run. Write down your main languages and frameworks, your databases, your cloud and hosting, your identity provider, your developer tools, your key SaaS vendors and the open source libraries you could not live without. One page is enough to start.
Bucket 1: your stack
Stories naming something on the list. These get the full exposure check: version, reachability, exploitation evidence, fix. If CISA's Known Exploited Vulnerabilities catalog adds an item that matches your list, that is a strong signal to check the same day, since CISA describes the catalog as the authoritative source of vulnerabilities exploited in the wild.
Bucket 2: your vendors
Stories about companies that hold your data or credentials. The question is what you share with them and what you were told to do. Use the breach questions about source, data, dates and customer guidance.
Bucket 3: your sector
Stories about attacks on companies like yours: same regulators, same customers, same technology. These are less about your exposure and more about patterns. Ask what the attackers did first and whether you would catch it. A story about stolen credentials leading to access, for example, is a prompt to review your own access practices.
Bucket 4: everything else
Interesting, sometimes alarming, usually irrelevant. If a story is big enough that customers or executives will ask, write two lines on why it does not apply, and move on.
The sorting questions
Ask these in order: do we use the named product, do we share data or credentials with the named company, do attackers in the story target our kind of business, and would someone outside the team ask us about it. The first yes decides the bucket.
Keep the list alive
When you adopt a new tool or drop an old one, update the list. Review it every quarter. A stale list sends you to the wrong stories.
Share the sorting
Show the list to the team so anyone who reads a story can sort it themselves and know where to send it.
Quick check
How long should the dependency list be?
Start with one page of what you would panic about if it broke. Add detail later.
Should small teams follow sector news?
Skim it weekly for patterns. Do not treat it as a to do list.
Sources
Last reviewed: 19 October 2026.
