Skip to content
Threat Brief

Editorial rules and methodology

How incidents and vulnerabilities get onto this site, and what each label means.

What counts as a major breach

An incident is listed as major when at least one of these is supported by a credible source:

  • Verified data exposure. A primary source confirms personal, financial, health or credential data was exposed.
  • Operational disruption. Services were taken offline or materially degraded, confirmed by the organization or a regulator.
  • Critical infrastructure impact. The organization operates critical infrastructure and the incident touched its operations.
  • Systemic supply-chain impact. A vendor compromise that exposes or disrupts multiple downstream organizations.

Reports reach an editor through a review queue. Nothing from a news feed is published automatically, so coverage depends on editorial review and is not exhaustive.

Sources and attribution

  • Primary sources come first: company disclosures, regulator notices and national CERT reports.
  • Reputable security reporting is used as secondary, attributed reporting.
  • Every statement about affected data or services names its source. When sources disagree, each account is shown separately with its attribution.
  • A date or detail no credible source has established is shown as “Unknown”.

Incident status labels

  • Reported: credibly reported, not yet confirmed by the organization, a regulator or a national CERT.
  • Confirmed: confirmed by one of those parties.
  • Disputed: the organization or another credible source disputes the report.
  • Retracted: the report was withdrawn or shown to be wrong; the record stays for transparency.

Editors merge duplicate records into one incident and publish corrections with their name and the fields that changed.

Vulnerability signals

  • CISA KEV is evidence of known exploitation. Its remediation due date applies to relevant U.S. federal agencies.
  • EPSS is a probability estimate from FIRST, shown with its score date. It never counts as exploitation.
  • Zero-day means a credible source establishes the issue was publicly disclosed or exploited before a fix was available. KEV membership alone does not qualify.
  • CVSS scores are shown with their version and the authority that assigned them, because authorities can differ.
  • Watchlist matches are “confirmed” only when your version falls inside a documented affected range. Otherwise the match says “version impact unknown”.

What is never published

Stolen records, credentials, leak samples, links to criminal infrastructure, exploit payloads, proof-of-concept code and targeting workflows. Pages focus on affected assets, impact, patching, mitigations and vendor guidance.