Blog
Attack surface management

Attack surface management vs vulnerability management

James Harrison
Author
James Harrison
Senior Content Writer

Key Points

Attack surface management (ASM) and vulnerability management (VM) are often confused, and while they overlap, they’re not the same. The main difference between attack surface management and vulnerability management is in their scope: vulnerability management checks a list of known assets, while attack surface management assumes you have unknown assets and so begins with discovery. Let’s look at both in more detail.

What is vulnerability management?

Vulnerability management is, at the simplest level, the use of automated tools to identify, prioritize and report on security issues and vulnerabilities in your digital infrastructure.  

Vulnerability management uses automated scanners to run regular, scheduled scans on assets within a known IP range to detect established and new vulnerabilities, so you can apply patches, remove vulnerabilities or mitigate any potential risks. These vulnerabilities tend to use a risk score or scale – such as CVSS (Common Vulnerability Scoring System) – and risk calculations.  

Vulnerability scanners often have many thousands of automated checks at their disposal, and by probing and gathering information about your systems, they can identify security gaps which could be used by attackers to steal sensitive information, gain unauthorized access to your systems, or disrupt your business. Armed with this knowledge, you can protect your organization and prevent potential attacks.

What does vulnerability scanning check for?

Most vulnerability scanners offer a list of security issues that the scanner checks for. This can be a good way to help you decide which scanner is right for you. Here are some broad classes of vulnerability which a modern vulnerability scanner should be able to check for:

  • Vulnerable software: this class of vulnerabilities is the biggest category, as it includes checks for known weaknesses in all kinds of 3rd party software and hardware. These are weaknesses discovered by security researchers in certain versions of a particular technology.  
  • Web application vulnerabilities: there’s a wide range of weaknesses which could be used to gain unauthorized access to information, compromise the web server or attack web application users such as SQL injection, cross-site scripting and directory traversal weaknesses.
  • Mistakes and misconfigurations: these include identifying software which has been incorrectly configured, common mistakes, and best practices which aren’t being followed.
  • Encryption weaknesses: a wide range of weaknesses in the encryption configurations used to protect data in transit between your users and servers can be identified by vulnerability scanners. These should include checks for weaknesses in SSL/TLS implementations, such as use of weak encryption ciphers, weak encryption protocols, SSL certificate misconfigurations, and use of unencrypted services such as FTP.
  • Information disclosure: this class of checks report on areas where your systems are reporting information to end-users which should remain private.

Not all vulnerability scanners check for all of these, and the number and quality of checks vary too. Some scanners are focused on one particular class of vulnerabilities - for example, web application vulnerabilities. A web application focused scanner wouldn’t necessarily check for infrastructure-level flaws, such as known vulnerabilities in the web server in use.

If you’re only using one scanner, it’s worth making sure it can handle all of the above, so there aren’t any gaps in your coverage. You can learn more about vulnerability scanning for Windows and Linux specifically in our dedicated guides.

What is the vulnerability management process?

  1. Performing a vulnerability scan
  2. Assessing your vulnerability risk
  3. Prioritizing and fixing vulnerabilities
  4. Monitoring continuously  

Read our guide on how to build a vulnerability management program for more detail.

What is attack surface management?

The main difference between vulnerability management and attack surface management is the scope. Attack surface management (ASM) includes asset discovery – helping you to find all your digital assets and services and then reducing or minimizing their exposure to prevent hackers exploiting them.

With ASM, all known or unknown assets (on-premises, cloud, subsidiary, third-party, or partner environments) are detected from the attacker’s perspective from outside the organization. If you don’t know what you’ve got, how can you protect it?  

Take the example of an admin interface like cPanel or a firewall administration page – these may be secure against all known current attacks today, but a vulnerability could be discovered tomorrow – when it becomes a significant risk. If you monitor and reduce your attack surface, regardless of vulnerabilities, you become harder to attack.

So, a significant part of attack surface management is reducing exposure to possible future vulnerabilities by removing unnecessary services and assets from the internet. But to do this, first you need to know what’s there.

What is the attack surface management process?

  1. Discover and map all your digital assets
  2. Ensure visibility and create a record of what exists
  3. Run a vulnerability scan to identify any weaknesses
  4. Automate so everyone who creates infrastructure can do so securely
  5. Continuously monitor as new infrastructure and services are spun up  
Intruder's Attack Surface view shows you what's exposed to the internet

How does attack surface management differ from vulnerability management?

Vulnerability management is the process of identifying and prioritizing vulnerabilities in your IT infrastructure and applications. Attack surface management goes a step further by identifying and analyzing your attack surface – all the devices, entry points and exposed services that an attacker could potentially use to gain access to your systems or data.  

We've also explored the difference between attack surface management and exposure management.

Can you combine Attack Surface Management and Vulnerability Management?

While ASM and VM may have different scopes and objectives, they’re not mutually exclusive. Used in combination, they create a much more holistic, robust and comprehensive cyber security posture. By identifying your assets and vulnerabilities, you can prioritize your security efforts and allocate resources more effectively – which will help you reduce the likelihood of a successful attack and any potential impact.

How Intruder can help with ASM and VM

Ultimately, you want to leave no stone unturned when it comes to cyber security. Modern VM and ASM solutions like Intruder can detect vulnerabilities affecting your organization. It gives you greater visibility and control over your attack surface, monitors network changes and SSL/TLS certificate expiry dates, helps you stay on top of your cloud infrastructure, and you only pay for active targets. Start a free trial to get started with vulnerability management or get in touch with us to learn more about ASM.

Get our free

Ultimate Guide to Vulnerability Scanning

Learn everything you need to get started with vulnerability scanning and how to get the most out of your chosen product with our free PDF guide.

Sign up for your free 14-day trial

7 days free trial