40 vendors · 11 sourced fields · A to Z
Attack surface management vendor picks by published rule
10 picks, each a published rule over the 11 fields, list every attack surface management vendor that meets the rule, A to Z. A field counts only when the vendor's own pages support it at level yes. The rules were fixed on 18 Nov 2026, before any fact was collected, and the lists use.
| Pick | Rule | Vendors that meet it |
|---|---|---|
| Discovery through to a fix | A vendor is listed when every one of these fields is at level yes: subsidiaries (the vendor's pages describe discovery of assets of subsidiaries, brands or acquired companies); validation (the vendor's pages describe validating exposures (active safe checks or exploitation proof), not only listing assets or version matches); 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). | 8 of 40 |
| Companies with subsidiaries or acquisitions | A vendor is listed when every one of these fields is at level yes: subsidiaries (the vendor's pages describe discovery of assets of subsidiaries, brands or acquired companies); seedless start (the vendor's pages describe discovery that starts from a company name or a single domain, without a supplied asset list). | 8 of 40 |
| Teams that want findings proven, not listed | A vendor is listed when this field is at level yes: validation (the vendor's pages describe validating exposures (active safe checks or exploitation proof), not only listing assets or version matches). | 18 of 40 |
| Dangling DNS and abandoned assets | A vendor is listed when this field is at level yes: dangling dns (the vendor's pages describe detection of dangling DNS, subdomain takeover risk or abandoned assets). | 10 of 40 |
| Start without a sales call | A vendor is listed when at least one of these fields is at level yes: price published (A price is published on the vendor's own pages); free tier or trial (A free tier or a free trial is offered on the vendor's own pages). | 19 of 40 |
| Buyers who want ASM from a platform they already run | A vendor is listed when this field is at level yes: 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 of 40 |
| Buyers who want a standalone ASM specialist | A vendor is listed when none of these fields is at level yes: 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)). | 17 of 40 |
| Teams that route findings into tickets | A vendor is listed when every one of these fields is at level yes: ticketing (the vendor's published integrations include a ticketing system (Jira, ServiceNow or similar)); 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). | 27 of 40 |
| MSPs and MSSPs | A vendor is listed when this field is at level yes: msp offering (the vendor's pages describe an MSP, MSSP or partner multi-tenant offering). | 23 of 40 |
| Assets hosted by third parties | A vendor is listed when this field is at level yes: third-party assets (the vendor's pages describe discovery of assets hosted by third parties (SaaS, CDN, hosting providers, supply chain)). | 19 of 40 |
How a pick list is computed
Each list is computed from the fields at build time. A field counts only at level yes; partial and none found do not count. A rule of "all" needs every named field at yes, "any" needs at least one, and "none" needs that no named field is at yes. Changing a rule is a change to the published data file, not to this site's code.
Last reviewed . Report a correction: editor@attacksurfacemanagementvendors.com.