40 vendors · 11 sourced fields · A to Z
Attack surface management software: what vendor pages tell you and what to ask in a demo
Read 18 Nov 2026: all 40 vendors publish a product description and an integrations list, but only 8 publish a price, 13 state no founding year and 5 state no deployment model. 117 of the 440 field cells read none found. This guide lists what pages cover and ten questions for a demo.
What vendor pages usually cover
Every vendor in the directory describes what the product does and lists some integrations, though watchTowr and Group-IB name ticketing or SIEM systems only as categories. Most state how it is delivered. 35 of 40 give a deployment model, usually SaaS and often agentless. Aftra's pricing page says there are no complex agents to install because Aftra focuses on the external footprint. FullHunt says discovery needs no agents or network access.
Partner programs, analyst mentions and case studies are common on larger vendors' sites. Documentation is a better source than a home page where it exists: Microsoft, Palo Alto Networks and Censys publish product documentation that states limits, scan schedules and supported exports in plain terms, and those pages carry more checkable detail than a product page.
What they usually leave out
Only 8 of 40 vendors publish a price. 13 state no founding year. 5 state no deployment model. 38 of 40 vendors have at least one field where the pages checked show nothing, and 117 of 440 cells read none found in all.
Common gaps are about how the product behaves. IONIX has no published discovery frequency or time for a new asset to appear, other than a 12-hour CVE response claim and the word continuous. For watchTowr and CrowdStrike, no page shows the evidence behind an asset attribution or a way to report and correct a false one. For Hadrian, none found on 18 Nov 2026 for a decommission workflow that retires unwanted assets, as opposed to detection of unclaimed subdomains.
How to read vendor numbers
A number on a vendor page is a claim. Qualys claims 30 percent more enterprise assets for its EASM. Darktrace's products page carries the tagline Discover 30-50% more assets. Neither page, as read, gives the baseline: more than what, for which customers. The same goes for 13 attribution components at IONIX or the 316 partner organizations SOCRadar cites, which describe the vendor, not your result.
Frequency claims differ in kind. CyCognito says discovery runs continuously with daily refreshes. Google says scans can run daily, weekly or on demand. Microsoft says some insights are labeled Potential when the scanner detects a service but cannot confirm the version.
Ten questions for a demo
These are questions that follow from the gaps above. They are not a requirements list.
- Start from only our company name or one domain. What does the product find, and how long does it take?
- For three assets you found, show why each belongs to us. What evidence is displayed?
- How do we report a wrong attribution, and how fast is it corrected?
- How often is each asset re-checked, and can we see the date of the last check?
- When a finding is marked validated, what did the check do, and could it affect production?
- After we fix something, how is it retested?
- Show a finding arriving in our ticketing system, with the owner field filled.
- What can we export, and does the API cover everything in the console?
- Where is our data stored, and which entity signs the contract?
- If the vendor is bought, renamed or merged, what happens to our contract and the product?
Before the call
Read the vendor's entry in the directory and open the sources. Write down which fields read none found, and ask about those first. Bring a list of ten assets you know, including one from a subsidiary or an old project, and see whether the product finds them.
Ask each vendor to confirm in writing what the demo showed, and keep the notes with the read date of the pages you used. If you find that a fact here is out of date, tell the editor. The corrections page explains how. A vendor that sends a page that states the fact will get the entry checked against it.
Sources
- aftra.io
- fullhunt.io
- docs.censys.com
- ionix.io
- watchtowr.com
- crowdstrike.com
- hadrian.io
- qualys.com
- darktrace.com
- socradar.io
- cycognito.com
- cloud.google.com
- learn.microsoft.com
- docs.rapid7.com
- pentera.io
- rapid7.com
Previous guide Where threat intelligence and digital risk vendors fit in attack surface managementNext guide Attack surface management companies: who sells what
Last reviewed . Report a correction: editor@attacksurfacemanagementvendors.com.