Cybersecurity News Today
Not yet loaded
Live cybersecurity news aggregated from 20+ trusted sources — covering vulnerabilities & CVEs, data breaches, ransomware, threat intelligence, and policy & regulation — filterable by topic and region.
Sources are free, publicly available RSS/Atom feeds. This dashboard runs entirely in your browser — no article data is stored server-side. Some government or regional feeds occasionally change URLs; check the Sources panel for load status.
Frequently Asked Questions
How often is the cybersecurity news dashboard updated?
Headlines are pulled live every time you open or refresh the page, so you always see the newest items each source has published. Nothing is cached on our side — press Refresh at any point to re-poll all feeds.
Which cybersecurity news sources are aggregated?
More than 20 public RSS and Atom feeds, spanning independent media (The Hacker News, BleepingComputer, Krebs on Security, The Record, Dark Reading, SecurityWeek, Infosecurity Magazine, The Register, Security Affairs, CyberScoop, Help Net Security, Schneier on Security), vendor research teams (Sophos News, ESET WeLiveSecurity) and national agencies (CISA, NCSC UK, Canadian Centre for Cyber Security, JPCERT/CC, ACSC Australia, SANS Internet Storm Center).
Can I filter the feed by topic or region?
Yes. Filter by topic — vulnerabilities and CVEs, data breaches, ransomware, threat intelligence, policy and regulation, or industry news — and by region: Global, North America, Europe, Asia-Pacific, Middle East and Africa. You can also search headlines by keyword and group results by region or topic.
Is any of my data stored when I use the news dashboard?
No. The dashboard runs entirely in your browser. Feeds are fetched client-side through a public CORS proxy, no account is required, and no article data or reading history is stored on our servers.
Why does a source show a red status dot?
A red dot means that feed could not be loaded — usually because the publisher changed its feed URL, the feed is temporarily down, or the public CORS proxy is rate-limiting the request. Other sources keep loading normally, and a refresh often clears it.