Security testing often starts with a list of systems to check. A vulnerability scanner works through known IP ranges, while a penetration test follows an agreed scope. Both depend on having a reasonably accurate inventory in the first place.
Attack surface management (ASM) helps identify what’s missing from that list. It looks for internet-facing systems an organisation doesn’t know about, has forgotten to decommission or assumes another team or supplier is managing.
This guide explains what ASM covers, how it differs from vulnerability scanning and penetration testing, how providers discover and prioritise assets, and what to look for when comparing their platforms.
What attack surface management actually is
Attack surface management involves continuously discovering, cataloguing and monitoring assets that attackers could target, along with the weaknesses and exposures associated with them.
Many products described as ASM focus on external attack surface management (EASM). The UK’s National Cyber Security Centre (NCSC) defines this in its buyer’s guide to external attack surface management as identifying, monitoring and reducing vulnerabilities in assets accessible from the internet.
The value is often in finding systems that aren’t on anyone’s radar. A marketing team might commission a campaign microsite that remains online after the campaign ends. A test environment might outlive the project it was created for. An acquisition could bring in infrastructure that hasn’t been added to the central asset register, or a cloud service might have been set up without the usual IT oversight.
EASM can help uncover exposed services that should be internal only, DNS misconfigurations, weaknesses in email security and outdated records pointing to former suppliers or decommissioned services.
These issues don’t necessarily require a sophisticated attacker to find. EASM helps security teams see their internet-facing estate from the outside, where gaps in internal records become much easier to spot.
Defining the scope: external, internal and exposure management
The external attack surface includes internet-facing systems and related assets that can be discovered from outside an organisation. These might include domains, IP addresses, certificates, exposed services, web applications and remote access gateways. EASM tools generally work from the outside in, without needing agents or access to the internal network.
The internal attack surface covers systems and connections accessible from within the organisation’s environment. This includes access available to employees, contractors and third parties, as well as routes an attacker might use after gaining an initial foothold.
Internal assets include endpoints, directory services, applications and the relationships between accounts and systems. Assessing them calls for other tools, such as internal vulnerability scanners, IT asset management software and cyber asset attack surface management (CAASM). CAASM platforms typically bring asset data together through API integrations with existing tools, such as endpoint agents, cloud platforms and directory services.
Exposure management takes a broader view. It brings together findings from areas such as attack surface discovery, vulnerability management, cloud configuration and identity security, then prioritises them according to business impact and tracks remediation through to verification.
ASM is one part of that wider process. An EASM platform can provide useful visibility of internet-facing systems without showing the full picture of internal assets and access relationships.
Vendors don’t always use these terms consistently, so ask exactly what a product covers. The focus here is on external attack surface management.
How ASM differs from vulnerability scanning and penetration testing
These three approaches answer different questions, and each has a role to play.
| Attack surface management | Vulnerability scanning | Penetration testing | |
| Core question | What do we have exposed, and what has changed? | Which known weaknesses exist on the systems we have listed? | Could a skilled tester exploit this scope, and how far could they get? |
| Starting point | Seed information, such as domains and organisation names, expanded outwards | A defined list of targets | An agreed scope, which may include reconnaissance |
| Timing | Continuous, often refreshed daily | Scheduled or regular | A point in time |
| Typical output | An asset inventory with exposures and changes | A list of vulnerabilities on known systems | Evidence of exploitable paths and their impact |
A penetration test may include reconnaissance, but its findings reflect a particular point in time. Scheduled scans also depend on the targets included. Neither is designed primarily to keep an organisation’s asset inventory up to date between engagements.
That’s where ASM comes in. If it discovers an unfamiliar subdomain, for example, the security team can establish ownership and decide whether it should be included in future authorised testing.
It’s also important to understand what an EASM finding actually proves. Some findings are inferred from information such as a software version banner. The NCSC distinguishes this type of indication from vulnerability assessment, which uses carefully designed, harmless payloads to establish whether a weakness is present.
Treat an EASM alert as a lead to investigate, rather than automatic proof that a system is vulnerable. Discovery methods and validation processes vary between providers, which is one reason different tools can return different results for the same organisation.
How external asset discovery works
Providers use different techniques, but a typical discovery process involves six steps.
- Start with known assets. The provider uses information such as registered domains, IP ranges, organisation names and details in digital certificates as starting points.
- Follow technical connections and validate the results. DNS records, TLS certificates, redirects and shared hosting can reveal related assets. However, a connection doesn’t necessarily prove ownership. A single hosting IP, for example, may serve many unrelated organisations. The NCSC recommends validating discoveries or assigning them a confidence score.
- Look beyond the traditional perimeter. Cloud workloads, APIs, remote access services and shadow IT may sit outside the IP ranges the organisation expects to find.
- Consolidate duplicate records. A server may appear under several hostnames, IP addresses and certificates. Linking these records helps avoid reporting the same issue multiple times.
- Establish ownership and confidence. Each asset should have a likely owner, supported by evidence showing why it has been attributed to the organisation.
- Monitor changes. New hosts, newly exposed ports, certificate changes and altered DNS records can indicate that the attack surface is changing.
Finding an unfamiliar asset is only the beginning. Once ownership has been established, the security team needs to decide how serious the exposure is, who is responsible for addressing it and what evidence will confirm that the problem has been fixed.
How exposures get prioritised
When a finding relates to a recognised vulnerability, the Common Vulnerability Scoring System (CVSS) provides a useful starting point. However, it doesn’t tell the whole story.
The CVSS v4.0 specification explains that the base score reflects a vulnerability’s intrinsic characteristics. Organisations should consider this alongside threat information and their own environment when deciding what to address first.
Many EASM findings don’t have a CVSS score. An exposed administrative interface, a dangling DNS record or missing email protections may still create a meaningful risk.
Six factors can help establish priorities:
- Reachability: Is the service genuinely accessible from the internet, or only under specific conditions?
- Asset criticality: What does the asset support? Does it hold sensitive data or provide access to important systems?
- Exploit activity: Is there evidence that the vulnerability is being exploited? This is different from predicting whether exploitation might occur. The Exploit Prediction Scoring System (EPSS) estimates the probability that a published Common Vulnerabilities and Exposures (CVE) entry will be exploited in the next 30 days. It’s a forecast, not evidence of an active attack.
- Threat intelligence: Is there information suggesting attackers are targeting the relevant technology or sector?
- Exposure path: Could the asset provide access to something more valuable, such as an administrative interface or identity service?
- Evidence quality: Has the weakness been confirmed, or is it inferred from information such as a software version?
These factors, combined with clear ownership and an understanding of business impact, provide a more useful basis for comparing providers than the number of assets or alerts they report.
What to evaluate in an attack surface management provider
The NCSC notes that no single EASM product will suit every organisation. Start by deciding what you need to achieve. You might want to uncover unknown assets, monitor subsidiaries and acquisitions, or address specific gaps such as weak email spoofing protection.
Then compare providers across three areas.
Discovery accuracy
- Inventory quality and evidence. A longer list of findings doesn’t necessarily mean better coverage. Ask which data sources the provider uses, how it attributes assets to your organisation and how it communicates confidence in those results.
- Coverage as your estate changes. Consider subsidiaries, different brands, cloud accounts and future acquisitions. Find out how coverage and licensing work as the number of assets grows.
Risk prioritisation
- Validation and supporting evidence. Ask which findings are confirmed and which are inferred. If active vulnerability assessment is available, establish what it involves and what permissions it requires.
- Risk context you can understand and adjust. Exploitation evidence, likelihood and asset criticality should be visible rather than buried in a single opaque score. Check whether you can adjust severity to reflect your organisation’s risk tolerance and record accepted risks.
Operational integration
- Workflow, reporting and integrations. Look for connections to ticketing systems and security information and event management (SIEM) platforms, along with raw data exports and reports for senior stakeholders. Findings should be usable within your existing vulnerability management processes and asset records.
- Refresh frequency and support. Different checks may run at different intervals. Ask how often assets are refreshed, whether you can request additional scans and what onboarding or analyst support is included.
Testing a provider during a trial
A trial gives you a chance to see how a provider performs against your own estate, rather than relying on a feature list or sales demonstration.
Before testing begins, agree the authorised scope in writing, including whether active vulnerability assessment is permitted. Make sure your security operations team knows how to recognise the provider’s scanning traffic, as the NCSC recommends, so it isn’t mistaken for an attack.
Give each shortlisted provider the same limited starting information, such as your main domain and organisation name, and allow discovery to run for an agreed period. Then divide the results into three groups:
- Assets you already knew about. How many known assets within scope did the tool identify? What did it miss?
- Previously unknown assets. Can your team confirm that they belong to the organisation using the evidence supplied? Once validated, these discoveries can provide some of the clearest evidence of a tool’s value.
- Assets attributed to you incorrectly. Infrastructure belonging to another organisation but listed as yours points to a potential validation problem. It can also create unnecessary work, so exclude these assets from further testing.
Finally, fix a genuine finding and check how quickly and clearly the platform registers the change. This helps show whether the tool can support remediation as well as discovery.
Choosing with evidence
Choosing an ASM provider comes down to the visibility it gives your team and how useful that information is in practice. The platform should help you establish which assets belong to your organisation, distinguish meaningful exposures from unreliable findings and check whether remediation has reduced the risk.
If your team is assessing ASM or wider exposure management providers, asset attribution, evidence quality and remediation workflows are useful starting points for supplier discussions.
Cyber Secure Forum brings senior security and IT decision-makers together with cyber security suppliers through pre-arranged individual meetings and seminars.
Qualifying buyers can select the product and service areas they want to review. Attendance is funded for those accepted who commit to the full day and their meeting itinerary. You can check whether you qualify as a buyer.
Frequently asked questions
How is attack surface management different from a vulnerability scan?
A vulnerability scan checks a defined list of systems for known weaknesses. Attack surface management helps establish what belongs on that list by discovering internet-facing assets you may not know about, then monitoring them for exposures and changes.
What is the difference between ASM and EASM?
ASM is the broader discipline of understanding the assets and systems an attacker could target. EASM focuses on assets accessible from the internet.
Does external attack surface scanning create additional risk?
According to the NCSC, using an EASM product doesn’t increase the risk to online services in almost all cases, because internet-facing services are already probed regularly by scanners. Active vulnerability assessment can carry more potential impact, however, so agree the permitted activities and scope with the provider before testing begins.
Do we still need ASM if we already have an asset management tool?
Often, yes. Asset management tools commonly rely on registered assets, agents and integrations, although some also offer discovery capabilities. EASM takes an external view to help identify what those records may miss, such as forgotten domains or services managed by third parties.
Image credit: https://unsplash.com/photos/woman-working-on-computers-in-an-office-4G3vzMnC34M


