| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| SIEM platforms | Security operations | 0% | 60 of 61 | 49% | 55 | criticized challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| AI SOC agents | Security operations | 0% | 30 of 104 | 0% | 7 | under 10 labels · led by Dropzone AI at 24% | |
| Threat intelligence platforms | Security operations | 0% | 35 of 119 | 0% | 4 | under 10 labels · led by MISP at 12% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| SIEM | 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 44 → 60 of 61 |
| AI SOC agents | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 30 of 104, unchanged |
| Threat intel | 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 101 → 35 of 119 |
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 | 1 | 1 | 1 | 3 |
| GPT-5.4 mini | 1 | 1 | 1 | 2 | 5 |
| Gemini 3.5 Flash | 1 | 1 | 1 | 3 | 6 |
| Perplexity Sonar | 0 | 0 | 1 | 1 | 2 |
| Grok 4.20 | 0 | 3 | 2 | 3 | 8 |
| Mistral Small | 0 | 2 | 4 | 0 | 6 |
| DeepSeek V4 Flash | 1 | 0 | 0 | 4 | 5 |
| Llama 4 Maverick | 0 | 0 | 0 | 1 | 1 |
| Qwen 3.7 Flash | 1 | 0 | 3 | 4 | 8 |
| Kimi K2 | 0 | 1 | 2 | 2 | 5 |
| GLM 4.7 FlashX | 1 | 2 | 1 | 1 | 5 |
| MiniMax M2.5 | 0 | 2 | 4 | 1 | 7 |
| GPT-6 Luna | 0 | 0 | 1 | 1 | 2 |
| Muse Glimmer 30B | 0 | 0 | 0 | 3 | 3 |
Verbatim evidence the judge attached to positive labels.
“The Industry Gold Standard... arguably the most popular SIEM due to its unparalleled flexibility and processing power” Qwen 3.7 Flash · SIEM · comparative prompt · first choice
“Best for: Large enterprises with complex, heterogeneous environments; mature SOCs... Trade-off: Expensive at scale” DeepSeek V4 Flash · SIEM · comparative prompt · first choice
“Industry leader with powerful search, AI/ML capabilities, and extensive marketplace” GLM 4.7 FlashX · SIEM · comparative prompt · first choice
“Splunk remains the undisputed "gold standard" for enterprise-wide data analytics.” Gemini 3.5 Flash · SIEM · comparative 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.
“A Note on Avoiding: While Splunk is the industry leader, it is often the wrong choice for mid-sized companies due to licensing complexity.” Qwen 3.7 Flash · SIEM · paraphrase prompt · hard negative
“they would "steer clear" of Splunk, citing its complexity” Llama 4 Maverick · SIEM · negative prompt · hard negative
“Avoid Splunk unless you truly need it” DeepSeek V4 Flash · SIEM · direct prompt · hard negative
“the biggest mistake organizations make is buying a complex, enterprise-grade SIEM (like Splunk or IBM QRadar) only to realize they don't have the staff to manage it” Gemini 3.5 Flash · SIEM · scale prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 170 of the 191 answers that named Splunk Enterprise Security and are not a share of its labels.
416 of the 457 domain citations in answers naming Splunk Enterprise Security 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 Splunk Enterprise Security's own pages state, read September 28, 2026: lantern.splunk.com/Security_Use_Cases/Advanced_Threat_Detection/Creating_an_incident_workflow_in_Splunk_Enterprise_Security, help.splunk.com/en/splunk-enterprise-security-7/mission-control/investigate-and-respond-to-threats/example-incident-response-workflow-in-splunk-mission-control, help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/soc-operations-dashboard, help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.6/analytics/soc-operations-dashboard, help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.5/analytics/soc-operations-dashboard. 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 Splunk Enterprise Security'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 Splunk Enterprise Security, 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 Splunk Enterprise Security by email, built from the raw record of the edition. It shows: