| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| SOAR platforms | Security operations | 0% | 67 of 67 | 52% | 27 | criticized challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Incident management and on-call | IT operations and endpoint | 0% | 52 of 65 | 50% | 2 | under 10 labels · led by incident.io at 32% | newNew since September 2026: not ranked then, 0% now. |
| Business continuity management | Security operations | 0% | 104 of 114 | 100% | 1 | under 10 labels · led by LogicManager at 24% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| SOAR | 0% | 0% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 15 → 67 of 67 |
| Incidents | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 52 of 65, unchanged |
| Business continuity | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 104 of 114, unchanged |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-5.4 mini | 0 | 2 | 0 | 0 | 2 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 1 | 1 |
| Perplexity Sonar | 0 | 0 | 1 | 3 | 4 |
| Grok 4.20 | 0 | 0 | 0 | 1 | 1 |
| Mistral Small | 0 | 0 | 2 | 1 | 3 |
| DeepSeek V4 Flash | 0 | 1 | 0 | 3 | 4 |
| Llama 4 Maverick | 0 | 0 | 0 | 1 | 1 |
| Qwen 3.7 Flash | 0 | 1 | 0 | 2 | 3 |
| Kimi K2 | 0 | 1 | 0 | 2 | 3 |
| GLM 4.7 FlashX | 0 | 0 | 2 | 0 | 2 |
| MiniMax M2.5 | 0 | 1 | 0 | 1 | 2 |
| GPT-6 Luna | 0 | 0 | 1 | 0 | 1 |
| Muse Glimmer 30B | 0 | 1 | 0 | 1 | 2 |
Verbatim evidence the judge attached to positive labels.
“Exceptional case management and breach response tracking; designed for incident response teams that need rigorous audit trails” DeepSeek V4 Flash · SOAR · comparative prompt · alternative
“Choose IBM QRadar SOAR if compliance, breach workflows, and enterprise process control are top priorities.” GPT-5.4 mini · SOAR · comparative prompt · alternative
“Best for: Regulated industries requiring breach response workflows and audit-ready documentation” MiniMax M2.5 · SOAR · comparative prompt · alternative
“Best for regulated industries that need privacy breach workflows baked into incident response” Muse Glimmer 30B · SOAR · comparative prompt · alternative
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.
“Currently considered one of the biggest "avoid" options due to significant lifecycle and roadmap risks.” Mistral Small · SOAR · negative prompt · hard negative
“At least one analysis explicitly recommends avoiding due to uncertainty about future development” MiniMax M2.5 · SOAR · negative prompt · hard negative
“explicitly flagged by analysts as potentially the biggest "avoid" right now” Kimi K2 · SOAR · negative prompt · hard negative
“has been flagged as a potential "avoid" due to lifecycle/roadmap risk.” Llama 4 Maverick · SOAR · 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 83 of the 89 answers that named IBM QRadar SOAR and are not a share of its labels.
393 of the 393 domain citations in answers naming IBM QRadar SOAR 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.
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 IBM QRadar SOAR's own pages state, read September 28, 2026: ibm.com/products/qradar, ibm.com/products/qradar-soar, developer.ibm.com/articles/awb-tracking-slas-security-incidents-using-qradar-soar, ibm.com/es-es/products/qradar-soar, ibm.com/id-id/products/qradar-soar. 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 IBM QRadar SOAR'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 IBM QRadar SOAR, 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 IBM QRadar SOAR by email, built from the raw record of the edition. It shows: