Attack Surface Management is expanding beyond traditional external asset discovery. Organizations now face exposure across cloud environments, identities, APIs, third parties, and AI-enabled systems, and ASM platforms are being asked to cover far more than internet-facing assets.
In this webinar, we present key findings from the latest edition of the KuppingerCole Leadership Compass for Attack Surface Management. The session examines market developments, emerging capabilities, technology trends, and the positioning of the participating vendors, with particular attention to how the market is addressing new attack surface areas.
Osman Celik will present the key findings from the third edition of the Leadership Compass for Attack Surface Management and share his analyst perspective on how the market is developing. He will cover the capabilities assessed across 36 vendors, emerging areas, and the use of generative and agentic AI in ASM platforms, and outline what organizations should consider when evaluating solutions.
Who Should Attend
This webinar is designed for CISOs, security architects, security operations leaders, vulnerability and exposure management teams, security engineers, risk professionals, and IT decision-makers evaluating or reviewing Attack Surface Management solutions
Hi, everyone. Welcome to our webinar today. My name is Osman Celik. I'm a Research Analyst at KuppingerCole, and today I'll be sharing with you my insights and findings from my latest Leadership Compass on Attack Surface Management. Before we start with the webinar, I remind you a couple of rules about today's webinar.
So, you'll be muted, so your participation with the voice is not really possible, but make sure to use the menu on the right-hand side to interact with me and send your questions and answer our polls. Feel free to use the menu on the right-hand side and send me your questions, and there is no need to worry about the slide deck. It will be recorded, and then at the end of the presentation, you'll have access to it. We start with the first poll question. Does your organization have an ASM solution in place today?
Yes, actively deployed, or you're in evaluation proof-of-concept phase, or no? Today's agenda will cover my ASM findings and the market overview, kind of what you should expect from ASM solutions, the subcategories of it, and then I will share with you guys my evaluation and research criteria, how I conducted my research. It was a research covering 36 vendors in over 150 pages, so it was a very detailed one, and at the end, when we have time, we will have a Q&A session.
All right, let's start with the buyer side of the story, so why do they need an ASM solution, or what makes them acquire an ASM solution, and it most of the time starts from the incomplete visibility over their entire attack surface, and it starts with your assets. That's the backbone of the attack surface management. You have to have an eye on your assets, your digital, your physical, your human, your identities, your applications, your AI tools, so all of them you can think about. This is actually the separate attack surfaces that are subject to the attack surfaces.
AI, identity, and API risks are on the rise compared to last year, especially AI and identity are the new focus for most vendors compared to last year, and just a small reminder, by the way, I've been working on the market over four years, and this is my third edition of the series.
Also, we see lots of solutions investing in that area as well, and as always, we have the sophisticated attack vectors that are mostly powered by AI, as you can imagine, so AI is used as a defensive and offensive tool in cybersecurity, and in this part, of course, we are in the into help companies comply with the regulations, and for these purposes, we see lots of control groups are implemented to the policies, and they're automatically trying to highlight if you are complying with certain framework standard or regulation.
This is very popular use case for SM solutions, and for most of the companies out there, you have so many alerts, so many findings, so many false positives, but you don't know which one to begin with, and you don't know why it is relevant to you. That's why I would say you have so many findings, but too little context, and you have lots of people involved in your remediation workflows, and it's fragmented.
It's another problem, and for the larger organizations out there, you most of the time work with your suppliers and their suppliers, so it's not only limited to the third parties, but you're also dependent on end parties nowadays. It goes beyond third parties, fourth and fifth parties, etc., so you also would like to keep an eye on the supply chain attacks, and lastly, in some cases, your solution is simply using a legacy solution that is not competent.
It's not advanced enough to deal with the sophisticated attack vectors that we are dealing today, and so how does an ASM solution work, and why do you need it? So here, I would like to make a distinction and explain to you guys these four subcategories of attack surface management. This solution, this problem, is persistent, by the way. I hope that I can manage it until the end, and on top of that, I'm sick. I'm sorry.
So to begin with CASM solutions, these are the first generation of attack surface management solutions, and they focus on the internal tools, and they most of the time integrate with your asset management solutions or CMDBs, and they also provide some sort of vulnerability scanner capabilities. If not, then they integrate with the third-party solutions. Second category is EASM. That's like the second generation of ASM.
In most cases, we see that the vendors are kind of accumulated in this market, so the most vendors are coming from EASM background as a side note, and these solutions are focusing on your digital assets, and they are probably the most common ASM solutions you can find on the market. It just begins with a simple seed discovery. You provide them your URL, and then they find your domains and subdomains and other dependent digital assets that are belonging to your company. The other one is DRP solutions. Here we go a bit specialized.
The DRP solutions are focusing on the social aspect, the brand aspect of your company, your brand, so they provide the dark deep web monitoring solutions and also social media analysis. TPRM solutions are focusing on the supply chain security, which I discussed in the previous slide, and why do we need it? Because then the attack surface is expanding.
That's very obvious, and if you think about some other solutions like network-specific, endpoint-specific, or web application-specific solutions, they're only targeting one aspect or one environment or one system, but when it comes to attack surface management, the coverage of or the meaning of attack surface is very broad, and it is expanding from your network to endpoints to your IoT, in some cases, OT devices, your endpoints, your AI tools, your identity and access management tools, so attack surface management solutions coverage are pretty broad, and the attack surface that the organizations are trying to address is also getting larger and larger every year, and you want to understand what is targeting you, why you might be on the risk, and what is relevant to you, and attack surface management solutions are actually designed to show you what is the most relevant and what is the most critical threat out there to address first.
All right, so I was explaining you guys why you need an attack surface management solution, and then we basically talked about attack surfaces are being expanded, and as an organization, you need to figure out what is most relevant and most critical to fix first. And another reason that you need an ASM solution is because it is impossible now to just focus on your organization without seeing what's going on in your third-party and party dependencies.
We can call this also supply chain security, and the attack surface management solutions are also helping you remediate the critical threats and risks quicker, and also as an emerging capability, now most ASM solutions are helping you with your compliance and also your audit processes.
All right, so here I actually would like to mention a couple of the capabilities here that might be maybe interesting to talk about, but before I categorize them in nice to have, must have, and innovative capabilities, I would say that everything you see here is actually going around NIST's framework, and most of them, maybe except the new pillar, govern, I think that most of you are familiar with the NIST's framework. Discovery, assessment, prioritization, and remediation, these four steps are basically the workflows that most, in 95 percent of the time, ASM solutions are dealing with.
So you can think like this, so the first step is to discover, and then the second step is to assess what is relevant from your discovery and monitoring activities, and then you prioritize what is relevant to your organization, and what might be a problem for the future, and then as the last step, remediation, you try to either fix it through an ASM solution or through an integrated solution, and finally you verify if the fix applied worked for you, and all the capabilities you see are actually helping you complete this step.
So if you begin from the discovery identification, or like the misconfiguration discovery, or shadow IT detection, or certificate discovery, these are all related to, so Sandy, I'm explaining now briefly, as I said, the governing part is not really a subject of, or the main focus of ASM solutions, but the discovery part, we could say that anything you see here in the core capabilities and the other capabilities are subject to discovery part. Let's talk about, for example, real-time vulnerability and risk analysis.
So this is part of assessment, and then CTI, for example, not everything you have in your CTI feed is relevant to you, right? Let's say that there is a threat actor, or there's a campaign, and then this is not hitting your industry, but then everyone is talking about it.
Why should you be interested, or spending time, and then your hours, and also your business capacity that is actually not relevant to you, just because there's a assessment process, and in most cases, you have a control and awareness of what assets you have, which assets do you have, and correlated with the CTI, then you go on to the prioritization part, and then here, there are catalog risk scores, like CVSS scores, or the these are the so-called catalog risk scores that actually, most of them, most of the time, tied to a CVE, and then you see there what are the likelihood, and how much you should be alerted, but on top of that, if your ASM solution is actually providing these advanced capabilities, in some cases, they have their advanced risk scoring mechanisms that are also bringing you the contextual information, also like the relevancy scores, and also some other risk scoring mechanisms that are proprietary to them, and then that helps you actually get a more meaningful data from this, all those risk scores, and then once you know what is the most relevant to your organization, then you start alerting the stakeholders, the relevant departments, and also the users, and when it comes to remediation, you either have an ASM solution that is actually trying to remediate the issue, or assisting you to integrate with a solution that would actually do the actual remediation, let it be SIEM, or SOAR, and or any other SOC solution, right, and nowadays, we see the emergence of the AI SOC solutions, so in most cases, I think the larger organizations are more tend to work with the fragmented tools, but some ASM solutions should be enough for dealing with the remediation as a standalone solution as well.
I'll explain, I get back to your question at the end, Abhishek, and so additional capabilities and innovative capabilities, I'm not going to go over them, but I explain you this way, so additional capabilities are actually the capabilities that we identify in the market when we see a repetitive pattern. What is it? So we have 36 vendors in this research, and the innovative capabilities are like, in most cases, I compare what's changing from last year, and if there is a pattern in vendors, if they're investing in a new functionality, for example, shadow AI detection.
When I started working on an ASM report back in 2022, it was only shadow IT, but now AI is in our life, and half of the vendors I work with, approximately, are now providing also shadow AI detection, so this is an innovative capability, but why not data encryption or DLP, for example, or bridge and attack simulation, because not every ASM vendor is only offering an ASM solution. For example, I work with vendors that are providing either separately licensed or included in their ASM license, automated pen testing.
This was the case until last year, and now, this year, we have agentic pen testing solutions. Either they work with a token credit base, or this comes with the standard package, so what you can do is, you can actually go through the discovery, assessment, prioritization, remediation, and verification process on a certain environment.
You have your red teams, your blue teams, and the solution is actually kind of trying to simulate an attack in a sandbox, in a controlled environment, so depending on the use cases, these kind of additional capabilities are also helpful to support the ASM activities. That's why they are called ASM additional capabilities, but not core, and for the innovative capabilities, a couple of more notes.
I think that this part is very subject to very quick and dynamic changes, because it is very difficult to keep an eye on what is changing in the market, and also, most vendors are not really sharing their roadmap capabilities with anyone, because these are not to be disclosed. They are most of the time confidential, and it's just what I grasp from the market, and for that, you need to really keep an eye on the market for over a couple of years to see what is changing.
For example, when I was talking about innovation last year, I was not talking about MCP servers, for example, because this was not even existing last year, or if it was existing, it was not subject to ASM tools. All right, so we have our second poll question now. Please try to answer using the menu in the right hand side. Which of these workflows are you more likely to automate in your cybersecurity operations?
Discovery, risk prioritization, remediation, or other? Please mention in the chat, we can discuss it. If you have any questions around it, if you have any concerns around it, if the time allows, I'll also try to give my feedback on that. I'm sorry.
So, I will briefly highlight the key findings. You will see here, one, two, three, four, five, six, seven, eight, nine, 10, 11, 12. 12 key findings I have here, but these are not limited to all these 12 findings. If you are interested in more of them, more specific key findings, please read the report, either through our website, if you are our subscriber, or through the vendors that are licensing this for free. I think it will be also very easy to go and find it with the Google search.
If you just Google Copenhager Coal 2026 ASM report, you will see the vendors who licensed this report, and then there you can go and find and read all the key findings and my market analysis as well. These are the analysis that are vendor agnostic and not relevant to any vendor. It's just my observation. What has changed in one year?
So, a couple of them I will mention here. The most important part, I believe, here is the identity and API attack surface discovery and also AI as an attack surface.
Also, the implementation of AI is now creating problems for attack surface management. So, it's a new attack surface.
As I said, AI is used as a defensive and also offensive technology today in cybersecurity. So, in one hand, we have the GNI or AI agents to actually automate and also help our life easier with the cybersecurity tools, also get some insights and summaries and some reporting activities quicker. But on the other side, it's creating another attack surface to protect. For example, if you are working with the MCP-based integrations, then you also have to keep an eye on them. And then for that, you also need to have an ASM solution that can monitor the AI assets.
Remediation capabilities are central to effective ASM and are consistently cited as the top customer priority. Yes, at the end of the day, customers are concerned the most about if this ASM tool is helping me remediate or mitigate this issue I have, or is it doing the right job with an ITSM or SIEM or SOAR solution. A couple of new findings here, like the GNI, for example, was used by many vendors in 2025, and this year it has become a standard, for example. And what is new in the field of AI is agentic AI.
We see so many vendors are including agentic workflows in this discovery, assessment, prioritization, and remediation workflows. It's really difficult to make an estimation here, but I would say most of them are utilized around discovery and remediation. Like in the beginning and at the end of this workflow.
All right, and I think the last but not least, I should mention that the vendor messaging is shifting toward the protection of crown jewel assets, sensitive data, and business critical services. One of the reasons that vendors are actually giving this message is because I think that when ASM emerged, I think that people thought that this was a complementary solution to their existing cybersecurity system or stack. And nowadays, I think that some organizations are now using the ASM as their standalone solutions against cyber attacks.
And here, the message is like, I am dealing with your most important sensitive data, your assets. So with ASM only, you can address and protect your most significant services or assets. This was my observation.
All right, we have the last poll question before we move on to my research methodology and story, basically. Where does your organization have the least visibility in your attack surface? Internet-facing assets and cloud services, APIs and SaaS applications, identities, credentials, and access relationships, and lastly, AI applications and agents. So from here on, I will explain to you guys a bit about what an LC is and also how we actually conduct this leadership compass research.
Leadership compasses are our flagship reports, and they are the most detailed reports that we provide to the people, as Kupinger call, as a cybersecurity industry analyst company. And what we do is basically, in a nutshell, we identify a market, and then later on, the vendors operating there. And as analysts, we are trying to pick the vendors that could be a good fit to our research criteria for a specific market. In our case, in today's case, it's attack surface management.
But it could be also another topic like identity and access management, or network security, or endpoint security, or cloud security, etc. And then we create a questionnaire that is trying to get answers around some corporate information and also some solution-specific information. And these questionnaires are actually not short. In most cases, they are over 500 questions, and we try to get the most out of these questions, and we hope that the vendors answer most of them. And most of the time, they do a good job.
If they do not answer enough, then we alert them and then tell them with this kind of... If they lack some information, then it will be reflected in their ratings badly. So they most of the time provide us most of the time. We set up a one-hour-long briefing call with every participating vendor. In that call, we also have a small chitchat around their product. They show me with the slide deck most of the time and share their roadmaps. And we spend most of our time in that one hour analyzing their solution on a demo, a live demo most of the time.
And I tell them, please navigate through the menus and show me your dashboards, your tabs, and then a typical user journey. This is what we try to see. And then based on this two information, the questionnaire and the briefings, we analyze the solutions. And then after we analyze every vendor, we try to come up with a market analysis, try to understand the trends, what is changing in the market. And then when the first draft is ready, we send this report to the vendors to make sure that everything is valid and everything is accurate. And then they send us their feedback.
They either say everything is good or they say that we need to change a couple of things. And if they have an issue that they want to talk to me about, then they book a short fact check call with me. And then after this period, we make sure that every party is providing me the changes they request with a proof. And as long as they do that, we are happy to change our opinion. We make mistakes also, as everyone else. So once everything is corrected, and once we believe that the report is ready, we publish it.
And this is the process for every LC we are writing, not only limited to tech service management. So you see evaluation criteria spider chart here. And security, deployment, interoperability, and usability are actually standard to every LC we are conducting. But from asset discovery to artificial intelligence, what are they?
Asset discovery, vulnerability monitoring, cyber threat intelligence, risk prioritization, digital risk protection, third-party risk monitoring, remediation and reporting, and artificial intelligence are specific criterias for a tech service management that I have determined. And I rate the vendors based on these categories. And then for every vendor, by the way, the name of the vendor is not mentioned here, but this is actually from the LC. So this is an actual vendor's rating. So you see there how they score in different categories, and then how well they perform in these categories.
I will skip through quickly the explanation of these dimensions. If you're interested, please go and download my slide deck and take a look at it. If you have any question, please ask me. But you will see the explanation for every spider chart category we have here.
And again, quickly going through the vendors participated in this year. First of all, I would like to thank you all these vendors participating here. The reason is because this is the third edition we have written. And in the first two editions, we have, again, a good number of participants. It was around 20 vendors for both versions. But this year, we had 36 vendors. So it was actually a good success for us.
And also, I think I believe vendors also benefited from this participation number, because at the end of the day, they actually have seen themselves against a larger vendor pool. And it was probably more accurate than the first two editions, considering that we have covered as much as players in the market. So you see the participation vendors here. If you are curious about any of them, go check out their website. And these 36 vendors that I've shown you in the map, and you will see them in one big chart altogether.
Again, don't worry. Regardless of their ranking, their status in the overall leadership chart, which we will see in soon in the later slide, they're actually qualified to my research. That means that they at least provide the basic level or the standard core capabilities that we expect from a tech surface management solution. So I would suggest checking any of these vendors, because I don't know which size of company you have, which resources you have. So I think that you can find solution based on your needs among these 36 vendors.
And if there was a vendor that is not good enough to provide a tech surface management solution that I see it is capable enough, then I would not invite them to my research. And if I did, I would alert them in the middle of my rating process. And I will tell them that unfortunately, you are actually not in the desired level. So everyone here you see is actually beyond a certain threshold. So you can keep that in mind. And these are the other vendors that we have either invited or could not get in touch. But we know that they exist. And they are in this market.
Most of them also provide very solid solutions, but they are not rated in this leadership compass. With some of them, I worked in the last years, by the way. If you are familiar with KupingerCole's ASM report, you will see some familiar names also here. As you might already know, at KupingerCole, we provide four leadership charts. And the first three of them are product and innovation leadership and the market leadership. And this year, we provided the market leadership with the bubble sizes for a more fair representation.
And combination of product and innovation leadership, we identified the overall leadership. And in the coming slide, I will show you the overall leadership. I think it's the most interesting part of my research. I think most of the people are only interested actually in that part. And I will show you guys the overall leaders and also the challenges. And also some only product leaders and only innovation leaders. If this is not big enough, please zoom in. I cannot really do it, I think.
But here is the vendors you see in the top right corner highlighted with the red color are the overall leaders and the remaining are challengers. And also you see some vendors highlighted with the gray, darker gray. Threat Energy Security was only innovation leader, not a product leader. And Reclaim Security and Certified Cyber was a product leader, but not an innovation leader.
The other vendors here, ReliQuest, Qualys, Armis from ServiceNow, Axonius, Ionix, BitSight, GroupIV, SiteCognito, Kela, CTM2, 360, Vicarious, JupiterOne, 4Seed, Sockradar, SciFirma, Zafran Security and HivePro and Axonius were both innovation and product leader, therefore an overall leader in the market. And for the market leadership, please pay attention to the bubble size. As we are not a financial analyst company, it's not fair to try to make a super accurate estimation on their market leadership.
And I think that as a cybersecurity industry analyst company, we most of the time do not receive the necessary information to make concrete judgments. And it's, I think, more fair to judge them with the bubble sizes.
All right, so this was the research I conducted. And if you have any questions, let me know. I think the time did not really allow us to go through everything. And I was trying to answer some of the questions that Sandy and Abhishek asked, at least. And I will see you guys in the next webinar. And please contact me through the QR code. And you have my email here. Please let me know if you have any questions. And I wish you guys have a good day and a good evening. Bye-bye.
See All Locations
See All Locations