How to read a story
CriticalExploited against OT, CVSS 9.0+ in an OT product, or an incident that disrupted operations.
HighCVSS 7.0–8.9 in an OT product, a confirmed intrusion at an operator, or new OT-capable malware.
MediumLower-rated flaws, incidents with no stated impact, notable guidance or regulation.
LowVendor news and minor updates, shown as routine items.
Known exploitedOn CISA's list of vulnerabilities attackers are using. Deal with it first.
CVSS 9.8The score the source states. Never estimated.
When to act
Act todayKnown exploited, or an attack that hit operations. Check today whether you are exposed; if so, control it now and patch at the first safe opportunity.
Plan aheadPublic exploit, EPSS 10%+, CVSS 8+ (7+ at the control levels), judged critical, or a confirmed intrusion. Fix in the next maintenance window.
For awarenessNews, research and guidance. Worth knowing; nothing to patch.
Judged by AI with quoted evidence, checked by code against fixed minimums. Loosely modelled on CISA's SSVC; not a CISA assessment. What the labels mean and how they are decided
What to do
Patch availableA fix exists; the story says which version.
Check your exposureNo fix yet, or it depends on how you are set up: find out whether it applies to you.
MonitorNothing to change today; watch for the signs the story names.
AwarenessGood to know: policy, research or a trend. Brief your people.
Every story has three facts (what happened, who is affected, what to do), when to act, and the editor's reading (open it under the story): who should act, the Purdue level and why, how to check whether you are exposed, what to do if you cannot fix it yet, what to watch for, and ATT&CK for ICS. The reading is inferred, and labelled so. How it's made