NewResilience, Continuity, the Pro levels and Agentic Verification: from safekeeping to proof you can recover.The new line-up is here.See what's new
ResourcesGuides and case studiesMagazineVideo guidesNews tickerIntegrationsEscrow agreement
Why the ticker hub changed. Production's /ticker opens on a scrolling "BREAKING" banner, repeated three times: "DORA compliance now mandatory for EU financial firms" (Check readiness), "NIS2 enforcement accelerates across member states" (Stay compliant), "APRA's CPS 230 standard now in effect" (Get solutions) and "Cyber Resilience Act implementation timeline confirmed" (Prepare now). None is news, none is sourced, and "Stay compliant" breaks the vocabulary rules. The banner is gone; the regulation pages are linked calmly below instead. The headline matches the navigation label ("Software risk, as it happens").
  • Production shows every item's full text twice on the hub (the capture repeats each body), and labels each "NEW". This rebuild lists title, date and topic, and the full item stays on its own page.
  • The 743 ticker posts aren't rebuilt; links go to production.
News ticker

Software risk, as it happens.

Short summaries of the attacks, outages and software flaws that hit the systems businesses run on, each crediting the publication that reported it.

Book a demo Get the sample evidence pack
  • Every item names its source
  • Trusted by 3,500+ teams
  • ISO/IEC 27001:2022 certified
Step 1, the exposure, told through real events. A short intro says why a software resilience company runs a news feed: many incidents that stop a business start at a supplier. Three cards, no statistics and no fear lines: the stories themselves make the point. The cards follow the patterns in this week's items (a supplier breach reaching customers, patched systems hit again, attacks through shared tools), without naming anyone.

Why we track it

Many outages start somewhere else.

The software a business runs on belongs to many companies. When one of them is attacked or ships a flaw, the effect can reach everyone who depends on it. The ticker follows those stories, so you can see where the risk sits before you need a recovery plan.

Supplier incidents travel

A breach or outage at a vendor reaches the customers whose systems run on its software.

A patch isn't always the end

Flaws can resurface in systems that were just patched, so recovery plans need more than an update schedule.

Real cases test your plan

Each story is a quick check: if it happened to a supplier of yours, how would you get back?

The latest ten items, as production lists them on 7 Oct 2026. Titles, dates and topics are production's; each links to the item on production. Editorial issues to fix at source:
  • Duplicate story: the Citrix NetScaler zero-day (CVE-2026-88779) appears twice, on 5 and 7 Oct, under different headlines. Merge or update one item.
  • Named individuals: the ShinyHunters item names two people as suspects who, by the item's own account, haven't been charged; the Trump Mobile item names an executive listed in leaked data. Have legal review the policy on naming people in ticker items.
  • Sources are named but not linked ("Source: Dark Reading", "Source: SecurityWeek", "Source: BBC News"). Link each original report.
  • Images come from a "Generated Blog Post Images" folder: label them as illustrations, or drop them.

Latest

The latest stories.

ClickFix Attacks Are Getting Sneakier About Hiding Their PayloadsCyberattacks ASOS App Hijacked by Hackers to Send Extortion MessageCyberattacks New Citrix NetScaler Zero-Day Hits Already-Patched SystemsCyberattacks Hacker Group Claims Breach of Trump Mobile Customer DataCyberattacks Jordan Detains Alleged ShinyHunters LeaderCyberattacks Citrix NetScaler Zero-Day Leaves Freshly Patched Appliances ExposedCyberattacks Critical GitLab AI Gateway Flaw Allows Remote Code ExecutionSoftware security Critical Flaw Let Any Website Run Code on Machines Used for SWIFTSoftware security China-Linked Warlock Ransomware Still Breaking Into UtilitiesCyberattacks Critical Fortinet FortiMail Zero-Day Under Active AttackCyberattacks

More by topic: Cyberattacks · Software security

Say what the ticker is, and what it isn't. The note sets expectations: summaries of public reporting with the source named, written at the time, not advice. Every claim in it is visible on production's items (each ends with "Source: …"). The links send readers who want analysis or a plan to the magazine and the regulation pages, replacing production's "BREAKING" banner. Both tag pages exist on production (Cyberattacks is linked in the capture; Software security checked on 7 Oct).

Editorial note

How we write the ticker.

Summaries, with sources. Each item summarises what a named publication has reported, and says which one. Items are written at the time, so details can change as an investigation goes on. They describe events; they aren't advice for your organisation.

For analysis, read the Software Resilience Magazine. For what regulators expect of your suppliers, see the evidence pages for DORA, NIS2, the CRA and CPS 230.

The secondary conversion, on every page. Visitors who aren't ready to talk can still leave their email. The sample evidence pack is the same offer on every page, so the site has one lead magnet instead of a different e-book per page. It also carries the launch story: proof, not promises. The button goes to the sample evidence pack page.

Sample evidence pack

See what your auditor would receive.

An anonymised set of outputs from a real Agentic Verification run, so you can judge the evidence before you talk to us.

  • Recoverability Certificate
  • Run report
  • SBOM and Exit workbook excerpts
Get the sample evidence pack
The same close on every page. The ticker closes by turning someone else's incident into the visitor's own question: could we recover? Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

When it's your supplier, be ready to recover.

Book a demo and we'll look at the applications you can't lose. Not ready to talk? See the evidence a rebuild produces.

Book a demoGet the sample evidence pack
Chat widget goes here. Production runs HubSpot chat in this corner. Keep it on launch: it catches visitors with a quick question who won't book a demo yet. Route it to sales during office hours.