Evidence comparison
Splunk and Palo Alto XSIAM: what the public record shows about each
Both products turn up on siem and log analytics shortlists, so this page puts their two evidence records next to each other: 86 items on Splunk and 28 on Palo Alto XSIAM, each one linked to the source it came from. It does not name a winner, and the section below explains why the numbers cannot be subtracted from one another.
Read the counts correctly
More advisories does not mean less secure. A vulnerability register records what researchers found and what the vendor disclosed. A product deployed in thousands of organisations with a mature disclosure process accumulates far more entries than a product nobody audits. A low count can mean a small install base, a young product or a vendor that publishes little, and a high count often marks the opposite.
The two counts are not measured with equal precision. An advisory is only listed against a vendor when the register ties it to one of its products by name, and vendors differ enormously in how consistently their products are named. Here that gap is 39 unattributable entries for Splunk against 25 for Palo Alto XSIAM, which moves the advisory row far more than the products do. Both numbers are in the table so the difference is visible rather than hidden.
Treat this page as two records shown together, never as one score minus another.
The two records side by side
| Measure | Splunk | Palo Alto XSIAM |
|---|---|---|
| Evidence items in the recordSize of the record, not a quality signal. | 86 | 28 |
| Kinds of source | 5 | 2 |
| Advisories attributed to the vendor's productsCounts scrutiny and deployment breadth. See the caution above. | 29 | 0 |
| Register entries that could not be attributedEntries naming the vendor that could not be tied to one of its products, so they are excluded from the row above. Read the two rows together: where this number is high, the registers describe that vendor's products less consistently, and the advisory count above says more about naming than about the product. | 39 | 25 |
| Of those, in the CISA known-exploited catalogueExploitation observed in the wild. The one count worth reading closely. | 1 | 0 |
| Share from government registers | 80% | 89% |
| Share the vendor cannot edit | 100% | 100% |
| Public practitioner threadsReflects community size as much as product behaviour. | 1 | 0 |
| Most recent entry | Jul 17, 2026 | Jul 17, 2026 |
| Sources last re-queried | Jul 17, 2026 | Jul 17, 2026 |
Where each record comes from
The registers and platforms behind each column, with the body that operates each one. A record resting on government registers carries different weight from one resting on the vendor's own documentation, which is why this is shown per vendor rather than merged.
Splunk
| Source | Operated by | Classification | Items | Latest |
|---|---|---|---|---|
| European Vulnerability Database | ENISA, European Union | Authoritative | 40 | Jul 15, 2026 |
| CERT-Bund security advisories | BSI, Federal Republic of Germany | Authoritative | 28 | Jul 16, 2026 |
| Known Exploited Vulnerabilities catalogue | CISA, United States | Authoritative | 1 | Jun 18, 2026 |
| Engineering discussions | Hacker News, public threads | Independent | 14 | Jun 16, 2026 |
| Analyst, review and reference sources | Recognised analysts, review marketplaces and technology press | Independent | 3 | Jul 17, 2026 |
Palo Alto XSIAM
| Source | Operated by | Classification | Items | Latest |
|---|---|---|---|---|
| CERT-Bund security advisories | BSI, Federal Republic of Germany | Authoritative | 25 | May 15, 2026 |
| Analyst, review and reference sources | Recognised analysts, review marketplaces and technology press | Independent | 3 | Jul 17, 2026 |
Documented vulnerabilities
Only entries tied to a product of the named vendor by a structural signal are listed: an advisory reference on the vendor's own domain, the vendor as the assigning authority, or the affected product list naming it. Entries that merely mention a vendor in passing are excluded from both columns.
Splunk
- CVE-2026-20253criticalCVSS 9.8Known exploitedJun 18, 2026
Splunk Enterprise Missing Authentication for Critical Function Vulnerability
- WID-SEC-2026-2370highCVSS 8.3Jul 16, 2026
Affected products: Splunk Splunk Enterprise
- WID-SEC-2026-1877highCVSS 9.8Jun 15, 2026
Affected products: Splunk Splunk Enterprise
- WID-SEC-2026-1876lowCVSS 4.3Jun 11, 2026
Affected products: Splunk SOAR
- WID-SEC-2026-1618highCVSS 9.1May 21, 2026
Affected products: Splunk Splunk Enterprise
- WID-SEC-2026-1139mediumCVSS 7.1Apr 16, 2026
Affected products: Splunk Splunk Enterprise
Palo Alto XSIAM
What practitioners report
Public threads naming each product in their own title. Not curated for sentiment, and not counted as a verdict: a loud thread is one team's experience, not a measurement.
Splunk
- Hacker NewsAug 26, 2025Independent
My Failures Onboarding at Splunk
Palo Alto XSIAM
What neither record can tell you
The two lists below are the honest holes in each record. Everything a choice between these two actually turns on sits outside both of them.
Splunk
- A further 39 register entries mention Splunk without naming a product of Splunk as affected. They are excluded rather than counted as vulnerabilities.
- Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
- Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.
Palo Alto XSIAM
- 25 register entries mention Palo Alto XSIAM, but none of them could be attributed to a product of Palo Alto XSIAM. They describe other vendors' software and are not shown here.
- No public practitioner discussion naming Palo Alto XSIAM was found in the indexed threads. Operational experience with this product is not represented in this record.
- Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
- Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.
Whether Splunk is the right choice is not on this page
A record of what is true about a vendor is one half of a decision. The other half is your context: which criteria matter, how heavily each one weighs, what is a hard no, and who has to sign the result off. No public page can know that, and any page that claims to rank vendors for you is guessing at it.
Typical criteria for this category
Needs your case- Log Ingestion Capacity & Cost Modelweight
- Detection Rule Coverageweight
- SOAR / Playbook Automationweight
- Mean Time to Detect (MTTD)weight
- Mean Time to Respond (MTTR)weight
Criteria shown as examples for siem and log analytics. Weighting and fit are properties of your decision, not of the vendor, so they are not published here.
What DecisionOS adds on top of this record
- The vendor scored against your criteria with your weighting, not against a generic ranking
- A dealbreaker check against your hard constraints: data residency, contract terms, existing stack
- A side-by-side view of the alternatives on your shortlist, built from this same evidence pool
- This evidence mapped onto your compliance scope: NIS2, DORA, ISO 27001, SOC 2
- A decision memo your board can read, with the trade-offs and the reasoning on the record
Questions this page answers
Which is better, Splunk or Palo Alto XSIAM?
This page does not answer that, and no public page can. Better exists only relative to a decision: which criteria matter, how heavily each weighs, what counts as a dealbreaker and which systems the product has to live next to. What this page gives you is the evidence on both, 86 items on Splunk and 28 on Palo Alto XSIAM, each with its source, so the judgement rests on the record rather than on marketing.
Does Splunk or Palo Alto XSIAM have more vulnerabilities?
Splunk currently has 29 attributed advisories in this record and Palo Alto XSIAM has 0. That comparison is easy to misread. A vulnerability register records what researchers found and what the vendor disclosed, so a widely deployed product with an active disclosure process accumulates more entries than one nobody audits. A low count can equally mean a small install base or a vendor that publishes little. The two figures are also not measured with equal precision: an advisory only counts here when a register ties it to a named product, and 39 entries naming Splunk and 25 naming Palo Alto XSIAM could not be tied to one. The count worth reading closely is how many entries appear in the CISA catalogue of known exploited vulnerabilities, which is 1 for Splunk and 0 for Palo Alto XSIAM.
How independent is the evidence on Splunk and Palo Alto XSIAM?
100 percent of the Splunk record and 100 percent of the Palo Alto XSIAM record come from sources the vendor does not control: government vulnerability registers, public practitioner threads and a fixed list of recognised analysts and technology press. Material either vendor publishes about itself stays in the record and is labelled as a claim.
What does this comparison of Splunk and Palo Alto XSIAM leave out?
Pricing, contract terms, notice periods, support commitments and the current scope of any certificate. None of those appear in a public register; they come from the vendor and belong in a negotiation record. Fit with your existing stack and your compliance scope is also absent, because it is a property of your organisation rather than of a siem and log analytics product.
Why does nexalign publish this instead of ranking Splunk and Palo Alto XSIAM?
Because a ranking would have to invent the buyer. Every quadrant and score sheet silently assumes a weighting that belongs to someone else's decision. nexalign publishes the record and keeps the weighting where it belongs, in DecisionOS, where it is set by the people who have to defend the outcome.
The full records
Splunk: the full evidence record
86 items from 5 kinds of source
Palo Alto XSIAM: the full evidence record
28 items from 2 kinds of source
Two records do not make a decision
Choosing between Splunk and Palo Alto XSIAM depends on which criteria matter to you, how heavily each one weighs, what your hard constraints are and who has to sign the result off. DecisionOS takes this same evidence pool, scores it against the criteria of your actual decision and produces a memo that holds up in front of a board and an auditor.