40 vendors · 11 sourced fields · A to Z
Attack surface management tools: build a shortlist from published facts
Read 18 Nov 2026: you can cut 40 attack surface management vendors to a short demo list in an afternoon by choosing three or four of the 11 published fields, filtering on them, and reading the gaps. A field counts only where a vendor's own page shows it. This guide gives the steps and the counts.
Decide what you already know
Before you filter, write down four facts about your own estate: whether you own subsidiaries or recent acquisitions, whether you will supply a domain list or want discovery from a company name, which ticketing system your teams use, and whether you need a partner to run the product for you. These decide most of the filters below.
Keep the list to three or four. Each extra requirement shrinks the list, and the 11 fields do not vary separately.
The 11 fields and how many vendors meet each
Every vendor in the directory is read against the same 11 fields. A vendor meets a field only when its own pages show it at the level 'yes'. Partial and none-found are kept apart. These are the counts of 'yes' across the 40 vendors, read on 18 Nov 2026.
- Subsidiaries, brands or acquired companies: 17 of 40
- Discovery from a company name or one domain: 15 of 40
- Third-party hosted assets: 19 of 40
- Validation of exposures: 18 of 40
- Remediation beyond a report: 31 of 40
- Ticketing integration: 33 of 40
- Dangling DNS or abandoned assets: 10 of 40
- A published price: 8 of 40
- A free tier or free trial: 18 of 40
- Sold as part of a larger platform: 23 of 40
- An MSP or MSSP offer: 23 of 40
| Field | What it records | Yes | Partial | None found |
|---|---|---|---|---|
| Subsidiaries | The vendor's pages describe discovery of assets of subsidiaries, brands or acquired companies | 17 | 9 | 14 |
| Seedless start | The vendor's pages describe discovery that starts from a company name or a single domain, without a supplied asset list | 15 | 16 | 9 |
| Third-party assets | The vendor's pages describe discovery of assets hosted by third parties (SaaS, CDN, hosting providers, supply chain) | 19 | 14 | 7 |
| Dangling DNS | The vendor's pages describe detection of dangling DNS, subdomain takeover risk or abandoned assets | 10 | 10 | 20 |
| Validation | The vendor's pages describe validating exposures (active safe checks or exploitation proof), not only listing assets or version matches | 18 | 15 | 7 |
| Remediation | The vendor's pages describe a remediation feature beyond a report: fix guidance per finding, ticket creation, or an action that closes or protects the exposure | 31 | 8 | 1 |
| Ticketing | The vendor's published integrations include a ticketing system (Jira, ServiceNow or similar) | 33 | 3 | 4 |
| Part of a platform | The ASM product is sold as part of a larger security platform from the same company (endpoint, cloud, SIEM or vulnerability management) | 23 | 8 | 9 |
| MSP offering | The vendor's pages describe an MSP, MSSP or partner multi-tenant offering | 23 | 13 | 4 |
| Price published | A price is published on the vendor's own pages | 8 | 6 | 26 |
| Free tier or trial | A free tier or a free trial is offered on the vendor's own pages | 18 | 6 | 16 |
Filter, then check the overlap
Filters stack quickly. 8 vendors meet all three of subsidiaries, validation and remediation: Cortex Xpanse, CyCognito, Hadrian, IONIX, Qualys, Securin, Strobes and watchTowr. 27 meet both ticketing and remediation. 17 vendors do not meet the platform field at 'yes', which is the closest the ledger gets to a stand-alone product.
Use the ledger table to apply your filters. Sort by the field you care about most, then look at who is left.
Read the gaps as dates, not as verdicts
A cell reads none found on 18 Nov 2026 when the pages checked do not show the feature. That is a statement about the pages, not about the product. A vendor may offer a feature that its public pages never mention.
Each gap names the pages that were checked. For example, the Pentera ledger entry says no discovery of subsidiaries, brands or acquired companies was found after checking the Pentera Surface page and the data sheet. Take that list of pages into your demo and ask the vendor to show the feature.
Check the source and its date
Every fact carries a source URL and a read date. Open two or three for the vendors you keep. Look for the quote, the page type (product page, documentation, press release, archived copy), and whether the vendor says it or a third party does.
Archived pages are marked. Outpost24's EASM page was read from an archived copy dated 6 Oct 2026, and the entry says so.
What the fields leave out
The fields do not measure accuracy, coverage, speed or support. A vendor that meets a field describes the feature; it does not show how well it works. Test those in a proof of value with your own domains, and write the pass mark down before the trial starts.
Ticketing is a good example. 33 of 40 vendors name a ticketing system, so the field separates few vendors. How findings arrive in your tickets, and how duplicates are handled, is something only a trial shows.
Cut to three or four and plan the demos
19 vendors publish a price or offer a free tier or trial, so you can try them without a sales call. The rest need a conversation first.
Pick the vendors that meet your filters, add one that does not, and ask each the same questions. Guide 11 lists questions that follow from what vendor pages say and omit.
- Hour 1: write your four facts and pick the fields.
- Hour 2: filter the ledger table and note the vendors left.
- Hour 3: open sources for each and write down the gaps.
- Hour 4: send each remaining vendor the same short list of questions.
Sources
- strobes.co
- hadrian.io
- cycognito.com
- slcyber.io
- aftra.io
- ionix.io
- pentera.io
- rapid7.com
- web.archive.org
- attaxion.com
Previous guide Attack surface management companies: who sells whatNext guide Attack surface management platform or standalone specialist
Last reviewed . Report a correction: editor@attacksurfacemanagementvendors.com.