How the finder works
The finder is a points table. Six answers add points to six tool types, the highest total wins, and a fixed order settles ties. It never looks at vendors.
What it scores, and what it never scores
It scores tool types against your answers. It does not score, rank or weight any vendor. Once a type is chosen, the results page lists every vendor whose own material documents that type, alphabetically, then the ones with partial claims, alphabetically.
"Documented" and "partial" come from each vendor's research record. Documented means the vendor's own pages describe the capability as a product or module. Partial means the claim is narrower: a beta, a module that covers part of the job, or a capability described only in passing. The record for each vendor explains which, and the vendor note shows it.
Why these six questions
Each question separates two or more types that buyers confuse. Question 1 splits control testing from path finding. Question 3, agents, splits most breach and attack simulation from automated pentesting. Question 4 is the one buyers skip: a platform nobody runs is wasted money, which is why "no dedicated team" adds the most points of any answer to managed services.
Questions 2, 5 and 6 add smaller weights. Where your estate runs, how often you test and how you buy all matter, but none of them should override what you need to prove.
Every rule
Each answer adds points to one or more tool types. Nothing else feeds the result: no vendor data, no cookies, no history.
| Q | Question | Answer | Points added |
|---|---|---|---|
| 1 | What do you need to prove? | Our controls block and detect attacks | breach and attack simulation +3, adversarial exposure validation +1 |
| 1 | What do you need to prove? | Exploitable attack paths exist, or do not | automated pentesting +2, attack path analysis +2 |
| 1 | What do you need to prove? | Both | adversarial exposure validation +3, exposure management platforms +2 |
| 2 | Where does the estate you will test run? | On-premises | breach and attack simulation +1, automated pentesting +1 |
| 2 | Where does the estate you will test run? | Cloud | attack path analysis +2, exposure management platforms +1 |
| 2 | Where does the estate you will test run? | Hybrid | adversarial exposure validation +1, exposure management platforms +1 |
| 3 | Can you install agents on endpoints? | Yes | breach and attack simulation +2, adversarial exposure validation +1 |
| 3 | Can you install agents on endpoints? | No | automated pentesting +2, attack path analysis +2, exposure management platforms +1 |
| 3 | Can you install agents on endpoints? | On some hosts | adversarial exposure validation +1, managed validation services +1 |
| 4 | Who will run the tests? | An in-house red team | adversarial exposure validation +2, automated pentesting +1 |
| 4 | Who will run the tests? | The SOC only | breach and attack simulation +2, attack path analysis +1 |
| 4 | Who will run the tests? | No dedicated team | managed validation services +4, automated pentesting +1 |
| 5 | How often do you need to test? | Once | automated pentesting +1, managed validation services +2 |
| 5 | How often do you need to test? | Quarterly | automated pentesting +1, attack path analysis +1, breach and attack simulation +1 |
| 5 | How often do you need to test? | Continuously | exposure management platforms +2, adversarial exposure validation +1, breach and attack simulation +1 |
| 6 | What does your budget process need? | A published price | breach and attack simulation +1, automated pentesting +1 |
| 6 | What does your budget process need? | A quote is fine | exposure management platforms +1, managed validation services +1 |
Ties
When two types end level, the finder takes the one that comes first in this order: adversarial exposure validation, breach and attack simulation, automated pentesting, attack path analysis, exposure management platforms, managed validation services. Adversarial exposure validation comes first because it is the broadest type and the least likely to send a buyer down a narrow path by accident.
A worked example
A buyer answers: both; hybrid; some hosts; in-house red team; continuously; a quote is fine. Adversarial exposure validation collects 3, 1, 1, 2 and 1, a total of 8. Exposure management collects 2, 1, 2 and 1, a total of 6. Managed validation collects 1 and 1. The finder sends that buyer to adversarial exposure validation.
Limits of a six-question tool
It cannot see your estate, your budget figure or your existing contracts. Treat the result as the type to pilot first, not a decision. If two types finish within a point of each other, read both results pages before you book a demo.
The weights were set by the finder desk from how each type is described in vendor material and in Gartner's public category definitions. They will change if the category does, and every change will be listed on the corrections page with a date.
What the page records
Nothing. The answers live in the address bar of the results page and nowhere else. The site uses cookieless Vercel Web Analytics for page counts; see the privacy note.