| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Static application security testing | Developer platform | 0% | 20 of 71 | 36% | 25 | criticized challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Application security posture management | Developer platform | 0% | 68 of 70 | 100% | 1 | under 10 labels · led by Aikido Security at 37% | |
| Dynamic application security testing | Developer platform | 0% | 32 of 58 | 0% | 1 | under 10 labels · led by OWASP ZAP at 29% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| SAST | 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 → 20 of 71 |
| ASPM | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 68 of 70, unchanged |
| DAST | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 32 of 58, 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 | 2 | 0 | 2 |
| GPT-5.4 mini | 0 | 1 | 0 | 0 | 1 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 2 | 2 |
| Perplexity Sonar | 0 | 1 | 1 | 0 | 2 |
| Grok 4.20 | 0 | 1 | 0 | 0 | 1 |
| Mistral Small | 0 | 0 | 1 | 1 | 2 |
| DeepSeek V4 Flash | 0 | 1 | 1 | 0 | 2 |
| Llama 4 Maverick | 0 | 1 | 1 | 0 | 2 |
| Qwen 3.7 Flash | 0 | 1 | 0 | 2 | 3 |
| Kimi K2 | 0 | 1 | 0 | 3 | 4 |
| GLM 4.7 FlashX | 0 | 1 | 1 | 1 | 3 |
| MiniMax M2.5 | 0 | 1 | 0 | 0 | 1 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 1 | 0 | 1 | 2 |
Verbatim evidence the judge attached to positive labels.
“Deep static analysis for binaries/source, customizable rules, on-prem/SaaS. High accuracy in taint tracking but can be slower/resource-heavy” Grok 4.20 · SAST · comparative prompt · alternative
“a comprehensive security solution that covers static analysis, dynamic testing, and software composition analysis” Llama 4 Maverick · DAST · paraphrase prompt · alternative
“Choose Checkmarx or Fortify if: You are a large enterprise with rigorous compliance needs” Qwen 3.7 Flash · SAST · comparative prompt · alternative
“enterprise-grade, long-established SAST, often chosen for large regulated environments” GPT-5.4 mini · SAST · 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.
“Avoid: Traditional enterprise ASPM platforms (Checkmarx, Fortify, Apiiro)” Kimi K2 · ASPM · budget prompt · hard negative
“Fortify is described as heavyweight \u2013 requiring dedicated infrastructure and a team to manage scans and triage.” Muse Glimmer 30B · SAST · negative prompt · soft negative
“Why be cautious: Fortify is widely considered a "heavyweight" tool. It is famous for high false positive rates” GLM 4.7 FlashX · SAST · negative prompt · soft negative
“Requires building/compiling to scan, very slow scans, outdated rules... painful support” Kimi K2 · SAST · negative 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 85 of the 95 answers that named OpenText Fortify and are not a share of its labels.
365 of the 365 domain citations in answers naming OpenText Fortify 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 OpenText Fortify's own pages state, read September 28, 2026: cybersecurity.opentext.com/products/data-security, cybersecurity.opentext.com/products/email-security, cybersecurity.opentext.com/products/endpoint-security, careers.opentext.com/us/en/job/51960/Premium-Support-Engineer-Fortify, careers.opentext.com/us/en/job/52699/Lead-Software-Developer-Fortify-Cloud-development. 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 OpenText Fortify'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 OpenText Fortify, 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 OpenText Fortify by email, built from the raw record of the edition. It shows: