40 vendors · 11 sourced fields · A to Z
Attack surface management platform or standalone specialist
Read 18 Nov 2026: 23 of 40 vendors sell attack surface management as part of a larger platform, and 17 do not at that level (8 are partial, 9 show no larger suite). The published facts differ in a few places, such as free trials and ticketing. This guide shows where, and which questions follow from the difference.
How the directory draws the line
A vendor counts as a platform suite when its own pages show the attack surface product sold as part of a larger security platform from the same company, such as endpoint, cloud, SIEM or vulnerability management. Partial cases are kept apart.
On 18 Nov 2026, 23 vendors meet that rule at 'yes', 8 are partial and 9 show no larger suite. The table below shows each vendor's entry.
| Part of a larger security platform | Vendors | Names, A to Z |
|---|---|---|
| Yes | 23 | Bitsight, Check Point, Cortex Xpanse, CrowdStrike, Cyble, Darktrace, Edgescan, Group-IB, ImmuniWeb, Intruder, Mandiant (Google Cloud), NetSPI, Pentera, Qualys, Rapid7, Recorded Future, Securin, SOCRadar, Strobes Security, Tenable, Trend Micro, Wiz, ZeroFox |
| Partial | 8 | Censys, Coalition, Halo Security, Microsoft Defender EASM, Outpost24, Searchlight Cyber, Sprocket Security, UpGuard |
| None found | 9 | Aftra, Attaxion, CyCognito, Detectify, FullHunt, Hadrian, IONIX, RedHunt Labs, watchTowr |
What platform pages say
Tenable's pricing page lists attack surface management in the same package as vulnerability management, web application security and OT security. Wiz says its platform connects code, cloud and runtime, and that attack surface management sits within it. Qualys sells the product as part of its Enterprise TruRisk Platform.
Microsoft says Defender for Cloud uses Defender EASM for outside-in scans, with the integration included in the Defender Cloud Security Posture Management plan. Microsoft also says that after a 30-day trial, customers are charged by billable assets as a separate line on the Azure invoice.
What specialist pages say
CyCognito says it is an external exposure management platform and that enterprises question the tradeoffs of broad platforms. That is a vendor's view, and it is a sales position. Hadrian, IONIX, Attaxion, Aftra, FullHunt, RedHunt Labs and watchTowr also show no larger suite on their pages.
The ledger shows that these specialists name their ticketing, SIEM or SOAR links on the product pages, as IONIX does with Splunk, Azure Sentinel, Cortex XSOAR, Jira and ServiceNow. Guide 8 lists what each vendor names.
Aftra's pricing page lists an internal vulnerability scanning add-on and PCI scans through an integrated Approved Scanning Vendor platform, so a stand-alone product can still carry paid extras.
Where the counts differ
These are the counts of 'yes' in each group, from the ledger.
- Ticketing integration: 20 of 23 platform vendors, 13 of 17 others.
- Free tier or free trial: 8 of 23 platform vendors, 10 of 17 others.
- Published price: 2 of 23 platform vendors, 6 of 17 others.
- Subsidiary discovery: 8 of 23 platform vendors, 9 of 17 others.
- Dangling DNS or abandoned assets: 2 of 23 platform vendors, 8 of 17 others.
- An MSP or MSSP offer: 11 of 23 platform vendors, 12 of 17 others.
Cases in between
Several vendors do not fit either side. Outpost24 sells an Exposure Management Platform and also sells EASM as its own product. The Cortex Xpanse documentation says Xpanse remains a separate product line, while the XSIAM documentation describes ASM as an add-on module. Censys sells ASM as one product of the Censys Platform, which also covers triage, investigation and threat hunting.
For these, the question is not which side they fall on. It is which package and price your contract would cover.
What the counts do not show
Counts of 'yes' say what a vendor's pages describe. They do not say how the product behaves, how many customers use it, or how a bundle is priced. A platform vendor may publish less about one module because the module is a small part of a long product list.
A group with a higher count on one field is not a better group. A buyer who already runs a vendor's endpoint or cloud product may get value from a module that shares its console. A buyer without one may prefer a product that ships on its own. Both are reasons to ask, and neither is a finding.
Questions that follow from the difference
- If the product is a module: does it need a license for the parent platform, and is the module sold alone?
- If it is a stand-alone product: which of your existing tools does it connect to, by named integration?
- Which team owns the findings, and which ticket queue do they land in?
- Is there a free trial of the module or only of the suite?
Sources
- crowdstrike.com
- tenable.com
- wiz.io
- qualys.com
- learn.microsoft.com
- cycognito.com
- hadrian.io
- ionix.io
- attaxion.com
- aftra.io
- web.archive.org
- cortex-docs.paloaltonetworks.com
- censys.com
- rapid7.com
Previous guide Attack surface management tools: build a shortlist from published factsNext guide Attack surface management solutions for MSPs and MSSPs
Last reviewed . Report a correction: editor@attacksurfacemanagementvendors.com.