For MSPs
Updated 16 October 2026 12:22 UTC
Every service you can sell, and how many distinct news items from the last 90 days it addresses. A story counts once per service and may count under several.
Part A turns the week into work you do for clients; Part B turns the same evidence toward your own business.
554 stories · 19 services · 90 days · not-evidence cohort per-service breakdown
- Service90d30d
- Vulnerability Management442132
- Managed XDR393131
- Firewall26988
- SASE/SSE24985
- WAF23682
- End-user elevation19363
- DLP4916
- AI-enabled attack detection4718
- Compliance4614
- Third-party293
- MFA238
- SSO227
- AI/ML system security2013
- Gateway196
- IEP (M365 email protection)133
- Phishing simulation133
- Training133
- Risk Management61
- Help Desk validation30
Open the Coverage Demonstrator to sort, filter and see the stories →
Part A — Protect your customers
What happened this week, and which of your services answer it. How to drive the Weekly →
MSP Weekly
What happened this week, and which of your services address each item.
Action list
The same week as imperative sentences, bucketed by how soon each matters.
Weekly client KEV Advisory
A ready-to-send note built from this week's newly exploited vulnerabilities.
Portfolio exposure
Which products common across your client base picked up an exploited bug.
Part B — Protect your business
Your own exposure, your proof of coverage, and how to bill for it. How to drive the Demonstrator →
Your toolchain
Your own supply chain: recent activity in the remote-management, ticketing and security software you run to manage clients.
Coverage demonstrator
Pick the services you sell and see the threats each one addresses — the evidence for a review or a renewal.
The playbook
How to package the patch cadence as a recurring, billable service.
What this lane does not cover yet
Governance and compliance services are thin. Not because they matter less, but because public breach-disclosure filings are thin in the record we read. Dedicated filing coverage is being added; until it lands, compliance and risk work show fewer stories behind them than they deserve.
Backup and recovery often has no story behind it. A leak-site listing says an intrusion happened somewhere; it does not say which platform was hit or whether anything was encrypted. Rather than guess, the pages say plainly when no story ties to a specific backup service — an honest empty rather than a gap quietly filled.
Every number on this page is computed when the page is built, and it is the number you will find on the page it links to.