| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Insider risk management | Security operations | 7% | 5 of 84 | 22% | 9 | under 10 labels · led by Microsoft Purview Insider Risk Management at 22% | |
| Extended detection and response | Security operations | 2% | 8 of 58 | 0% | 3 | under 10 labels · led by Microsoft Defender XDR at 40% | ▼−5Since September 2026: 7% → 2%, −5 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Data loss prevention | Security operations | 2% | 10 of 89 | 0% | 5 | under 10 labels · led by Microsoft Purview DLP at 46% | ▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 1 | 0 | 0 | 1 |
| Gemini 3.5 Flash | 0 | 2 | 0 | 0 | 2 |
| Perplexity Sonar | 1 | 1 | 0 | 1 | 3 |
| Grok 4.20 | 0 | 1 | 0 | 0 | 1 |
| Mistral Small | 1 | 0 | 0 | 0 | 1 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 0 | 0 |
| Llama 4 Maverick | 0 | 0 | 1 | 1 | 2 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 1 | 1 | 0 | 0 | 2 |
| GLM 4.7 FlashX | 1 | 1 | 0 | 0 | 2 |
| MiniMax M2.5 | 1 | 0 | 0 | 0 | 1 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 1 | 1 | 0 | 2 |
Verbatim evidence the judge attached to positive labels.
“Coro and Microsoft Purview are highly recommended for small businesses and startups (under 500 employees)” Mistral Small · Insider risk · budget prompt · first choice
“For the tightest budget, Coro offers the best balance of features and cost” MiniMax M2.5 · Insider risk · budget prompt · first choice
“the strongest fit is usually Coro if you want an SMB-focused XDR platform” Perplexity Sonar · XDR · budget prompt · first choice
“Coro Cybersecurity — *Best Overall for Mid-Market*” Kimi K2 · DLP · paraphrase prompt · first choice
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“Teramind, Veriato, and Coro/Metomic, which are not recommended for large enterprises due to performance issues or limited features” Llama 4 Maverick · Insider risk · negative prompt · hard negative
“flags Coro/Metomic as SMB-focused SaaS solutions and says they should be avoided for large enterprises” Perplexity Sonar · Insider risk · negative prompt · hard negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 111 of the 112 answers that named Coro and are not a share of its labels.
307 of the 307 domain citations in answers naming Coro came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
| Kind | Pages | Last 90 days | 2025-10 to 2026-09 | Latest | Categories named |
|---|---|---|---|---|---|
| Blog | 238 | 12 | 2026-09-24 | EDR, Awareness training | |
| News or press | 63 | 4 | 2026-08-04 | Email security, Awareness training | |
| Glossary or explainer | 38 | 1 | 2026-09-09 | SIEM, Threat intel | |
| Case study | 6 | 2 | 2026-08-17 | ||
| Report or ebook | 5 | 1 | 2026-09-28 | ||
| Podcast or video | 4 | 0 | 2025-09-11 | ||
| Conference or event | 3 | 0 | 2025-04-28 | ||
| Webinar or virtual event | 2 | 0 | 2024-04-01 | ||
| Comparison | 2 | 0 | 2024-07-09 |
Every page coro.net exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. An event counts as online when its address or title says so (webinar, on demand, virtual or online summit); a conference, summit, trade show, expo or roadshow that does not say so is counted as a conference or event, which on a vendor's site is mostly in person. Read September 29, 2026.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Coro's own pages state, read September 28, 2026: coro.net, coro.net/compliance, coro.net/platform, coro.net/resources/case-studies, coro.net/platform/integrations. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Coro's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Coro, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Coro by email, built from the raw record of the edition. It shows: