About Cyber Digest

What this is

Cyber Digest is an independent publication covering publicly reported cybersecurity developments. It publishes a daily sector-by-sector roundup, aggregated monthly editions, a searchable story database and a reference wiki of incidents, vulnerabilities, actors and concepts. It is written for practitioners and analysts who need a fast, source-attributed read on what changed, and why it matters.

How it is produced

Everything on the site is generated from one corpus: the published digest archive and the story database behind it. Collection is largely automated, drafting and fact-checking support are AI-assisted, and output is reviewed before publication. The full disclosure — what is automated, what is AI-assisted, and what the ratings mean — is in the methodology & reading guide.

Nothing here is hand-entered. The homepage threat index, the sector counts, the reporting-activity charts and every per-story rating are computed from the database at build time, from the same data the Story DB and the digests publish.

How sources are treated

Every item carries a deep link to the specific article it came from — never a homepage or a syndication redirect — and each source is graded by reliability tier. Confidence is the gate: a single-source, unattributed claim is labelled Unverified and can never be rated Critical severity or Observed urgency. Reported-but-not-verified material is labelled as such rather than smoothed into the narrative.

What this site does not do

• It does not predict attacks. Ratings describe the severity and urgency of already reported activity, and are an ordinal heuristic — not a probability, and not a measure of real-world danger.
• It does not give security, legal or investment advice.
• It runs no advertising and no cross-site tracking, and collects no visitor data — see the privacy policy.
• It does not publish an unattributed claim as fact to fill a gap in a quiet news cycle.

Corrections

Factual errors are fixed and disclosed rather than silently overwritten, with the original claim recorded alongside the correction — see corrections & retractions. If a headline, date, figure or attribution here is wrong, it will be corrected against the source.

Rights and reuse

The site's own analysis, ratings and build code are original; the news being summarised belongs to the outlets that reported it, and every item links back so attribution and traffic stay with the source. See licensing & terms.

Reporting a security issue

Vulnerability reports about this site itself go to the address published in security.txt (RFC 9116) — not through the corrections channel.