Two AI engines, two different security vendors, 72.7% of the time.
Twenty buyer-intent questions — the ones a security lead actually types — put three times each to ChatGPT and Perplexity on one day. On the eleven where both platforms were consistent with themselves, the two named a different leading vendor on eight. They shared a median 3.8% of their sources. All twenty questions are published below, including the nine excluded from the headline rate and the two predictions registered beforehand that came out wrong.
Which engine your buyer asks decides whether you are named.
This is not a ranking problem with two scores. It is two channels that share 3.8% of their sources and disagree about who leads nearly three times in four. A vendor optimizing for “AI visibility” as one thing is optimizing for an average of two populations that barely overlap.
The measurement
| What was measured | Result | Base |
|---|---|---|
| Disagreement rate, where both platforms were internally consistent | 72.7% | 8 of 11 questions |
| Cross-platform citation overlap | 3.8% | median across questions |
| ChatGPT citation stability across three identical calls | 17.2% | median |
| Perplexity citation stability across three identical calls | 100.0% | all 20 questions |
| ChatGPT named a different leader across identical calls | 40% | 8 of 20 questions |
| Perplexity named a different leader across identical calls | 10% | 2 of 20 questions |
The three agreements are the tell. Identity and access management, container security and threat intelligence — the three categories with one obvious canonical answer. Everywhere a category had genuine competition, the two platforms picked different winners.
All twenty questions, including the nine that did not count
Nine questions are excluded from the 72.7% because one or both platforms contradicted itself across three identical calls. That guard was set before retrieval, and instability is never reported as disagreement. They are published here anyway, because a reader cannot check a rate whose exclusions are invisible.
| Category | ChatGPT named | Perplexity named | Counted as |
|---|---|---|---|
| SIEM, small team | Splunk | Rapid7 | disagree |
| Zero trust network access | Cloudflare | Zscaler | disagree |
| Cloud security posture management | Palo Alto | Wiz | disagree |
| Identity and access management | Okta | Okta | agree |
| Email security | Proofpoint | Check Point | disagree |
| Managed detection and response | ESET | CrowdStrike | disagree |
| Security awareness training | KnowBe4 | Hoxhunt | disagree |
| Attack surface management | ORDR | Palo Alto | disagree |
| Container security | Trivy | Trivy | agree |
| Third party risk | Riskonnect | Vanta | disagree |
| Threat intelligence | Recorded Future | Recorded Future | agree |
| Endpoint detection and response | Seceon, then SentinelOne, then CrowdStrike | — | excluded — unstable |
| Vulnerability management | contradicted itself | — | excluded — unstable |
| Data loss prevention | contradicted itself | — | excluded — unstable |
| Penetration testing | Rapid7, then nobody, then CrowdStrike | Declined both times: “there is no single best provider” | excluded — unstable |
| Secure access service edge | contradicted itself | — | excluded — unstable |
| Privileged access management | contradicted itself | Keeper, then Delinea | excluded — unstable |
| Security orchestration and response | contradicted itself | — | excluded — unstable |
| Backup and ransomware recovery | contradicted itself | — | excluded — unstable |
| API security | — | Salt Security, then Akamai | excluded — unstable |
Penetration testing is the honest row. Perplexity declined to name a leader both times, with the same reasoning each time — there is no single best provider. ChatGPT named Rapid7, then nobody, then CrowdStrike. The platform that refused to answer gave the better answer.
What was registered, and what it cost me
Four predictions with bands, written before any retrieval. Two came out wrong and one of them fired a falsifier I had written specifically to kill my own hypothesis.
| # | Registered | Band | Result |
|---|---|---|---|
| P1 | Disagreement rate lands between 30% and 60% | Likely | 72.7% — above the band |
| P2 | Citation overlap is higher than entertainment’s 12.5–16.7% | Likely | 3.8% median — the falsifier fired |
| P3 | ChatGPT citation stability under 70% | Very likely | 17.2% median |
| P4 | Perplexity citation stability above 90% | Likely | 100.0% on all twenty |
The P2 falsifier read: P2 dies if citation overlap is at or below 16.7%. That result would mean the corpus split is a property of how these platforms retrieve, not of thin coverage in entertainment — a stronger and more general finding than the one I am predicting.
It came in at 3.8%. I expected the dense commercial corpus of a B2B category to pull the platforms together. It pushed them three to four times further apart than entertainment did. The prediction was wrong in the direction of a stronger result, which is the only kind of wrong worth having.
What the engines were actually reading
| ChatGPT | Perplexity | |
|---|---|---|
| Rows citing a paid newswire | 7 rows, 4 questions | 0 |
| Rows citing a foreign-language reseller, listing or store | 11 domains | none |
| Rows citing nothing at all | 11 | 0 |
| Domains cited per row | 0 to 9 | 7 to 10, never empty |
On best EDR platform for a mid-size company, ChatGPT’s first answer led with Seceon, sourced to Seceon’s own press release on a paid newswire — a company growth announcement, syndicated, surfaced as the top recommendation to a buyer. These were the nine domains behind it:
prnewswire.com · logpresso.store · saas.imitsu.jp · licenzesoftware.it · connect.xdr.security.cisco.com · spotsaas.com · saasworthy.com · insidecyber.ai · securityboulevard.com
A paid newswire, a vendor’s online store, a Japanese SaaS listing, an Italian software-licensing reseller, two SaaS directories and one security publication. Perplexity’s five, identical on both calls:
acronis.com · cynet.com · huntress.com · paloaltonetworks.com · securityboulevard.com
A US buyer asking ChatGPT which security product to buy is being answered, in part, from Japanese and Italian software reseller listings. That is also the mechanism behind the 17.2% stability: a long tail of thin directory pages gives it a different draw every time.
Review databases, not trade press
Six source types were registered before retrieval as the ones a model would reach for. Four hit and two did not, and the two that missed are the pure security trade titles.
| Registered source | Appeared in | Outcome |
|---|---|---|
| G2 | 14 rows | hit |
| Gartner | 9 rows | hit |
| CSO Online | 2 rows | hit |
| TrustRadius | 1 row | hit |
| Dark Reading | 0 rows | never cited |
| BleepingComputer | 0 rows | never cited |
The registered set appeared on 11 of 20 questions, 26 marker hits in total. Models answering buyer questions reach for review and comparison sites, which are commercially maintained and structured for exactly this query shape, and skip editorial trade press, which is organized around news rather than selection. G2 is not accessible consumer press — it is a buying-decision database, and that is why it is there.
A correction, kept on the page. I first wrote that this confirmed a pattern carried forward from three earlier passes, and published that before running the check. It did not confirm it; the real pattern is narrower and more useful. The check took one command. The standing rule that came out of it: a registered source marker is scored against the pack, never against the prior.
What this supports, and what it does not
Supported: in cybersecurity, on buyer-intent questions, the two platforms usually name different leaders and almost never cite the same sources. A parallel entertainment measurement was the weaker version of this same result, which means it is not an artifact of one category.
Not supported: which platform is right. Nothing here measures accuracy. Perplexity is more stable and better sourced; that is consistency and provenance, not correctness.
What a vendor can act on: the engines read review and comparison databases and do not read the security trade press. If being named matters to your pipeline, that is where the asymmetry is — and it is two separate problems, not one, because the two engines share 3.8% of their sources.
What this study cannot tell you
- Nothing here measures which platform is right. Perplexity is more stable and better sourced. That is consistency and provenance, not correctness, and this study does not establish that either engine names the better product.
- Platform-default budget-tier models — gpt-4.1-mini and sonar. Buyers are usually served the flagship. Nobody in this category is measuring the flagship either, and this study does not close that gap.
- One row of 100 was lost to a 30.1-second timeout on the third container security call. That question is one of the three agreements and rests on two calls rather than three. Had the missing call named something else, the disagreement rate would be 80% rather than 72.7%, so the published figure is the conservative one. It was not re-run, because the stopping rule said one pass.
- Nine of twenty questions are excluded from the headline rate, because one or both platforms contradicted itself across identical calls. Those are reported as instability and never as disagreement. That guard was set before retrieval, and all nine are published in the table above rather than dropped.
- One pass, one day, one location. October 19, 2026. A platform that retrieves differently on a different day will answer differently, and this estate has already measured ChatGPT’s own instability varying fourfold within a single day.
- Twenty questions is not the category. They were chosen as buyer-intent questions across common security budget lines, not sampled from anything.
How this page changes
A standing study, not an article. Corrections are published in place and dated, never applied quietly.
| Measurement | Cadence |
|---|---|
| All twenty questions, both platforms | Quarterly |
| Registered source markers | Every re-run |
| Excluded questions and the reason for each | Every re-run, republished in full |
| Date | What changed |
|---|---|
| 2026-10-25 | Published from the pass of 2026-10-19. The source-marker reading in the section above was corrected on the day of the pass, before publication, and the correction is kept on the page rather than removed. |
This study is re-run quarterly, and the next reading will differ from this one.
Sound Decisions carries each re-run and each correction, with the registered question written before the data is pulled.
Subscribe to Sound Decisions