Severity Daily

IT and AI security incidents, checked against the primary source

About Severity Daily

Severity Daily is a daily publication about security incidents and the IT and AI developments around them. It is written for the people who run technology inside organizations and have to decide what to deal with first.

What makes it different

Every story is checked against a primary source before it runs: the vendor advisory, the CVE record, the CISA Known Exploited Vulnerabilities catalog, the organization’s own statement, or the regulatory filing. Coverage from other publications is treated as a lead, not a source.

That checking often turns up the story itself: a fixed version that was never released, a severity score that contradicts the advisory it came from, a record that names the wrong product. When the record is the problem, we say so, and those stories are filed under The Record.

Where to start

  • Patch Now: known exploitation, federal deadlines, and fixes that cannot wait.
  • Patch Soon: high-severity flaws with a fix available and no exploitation observed.
  • Breach: a named organization confirms an incident.
  • Research: new attack techniques, and AI and infrastructure security research.
  • Developing: stories that are still moving, labeled as such.
  • The Record: stories where the finding is that the official record is wrong, empty, or contradicts itself.
  • Daily Recaps: each evening, which of the day’s stories matters most, and why.

Who is behind it

Severity Daily is published by Express Development Group LLC. Tim is the editor. He sets the editorial standards, decides what the publication covers, and is accountable for everything that appears on this site.

How it is made

Severity Daily is produced with AI. An AI system researches, verifies, and drafts stories four times a day, under standards Tim wrote and maintains. Stories publish when they meet those standards. Tim reviews what runs, and when something is wrong, it is corrected in public. The full method, including what gets published and what does not, is on How this is made.

Corrections

Errors are corrected on the story with a dated note and logged on the Corrections page. Nothing is quietly edited.

Contact

Tips, corrections, and questions go to the addresses on the Contact page.