Security operations

What is Attack Surface Management?

Attack surface management is how you find, monitor and shrink everything an attacker could reach. This plain-language guide covers what your attack surface is, why it keeps growing and how to reduce it.

Key takeaways
  • Attack surface management is the continuous practice of finding, monitoring and reducing every point an attacker could reach.
  • Your attack surface spans internet-facing systems, cloud and SaaS, remote and edge devices, shadow IT, suppliers and identities.
  • Exploited vulnerabilities were the initial access route in 20 percent of breaches in the Verizon 2025 DBIR, up 34 percent on the year before.
  • Edge devices and VPNs jumped from 3 percent to 22 percent of tracked vulnerability exploitation, an almost eightfold rise.
  • Only 54 percent of those edge flaws were fully patched within the year, at a median of 32 days.
  • Third-party involvement in breaches doubled to 30 percent, and ransomware featured in 44 percent of breaches.
  • You cannot defend an asset you do not know you own, so discovery from the outside in comes first.
  • CISA requires US federal civilian agencies to run automated asset discovery every 7 days and vulnerability enumeration every 14 days.
  • NIS2 Article 21, DORA Article 8 and ISO 27001 Annex A 5.9 all require you to identify and manage your assets, with the NIS2 board accountable under Article 20.
  • Reduce the surface by keeping one live inventory, closing needless exposure, adding MFA, patching the edge fast and covering suppliers.

Attack Surface Management Defined in Plain Terms

Attack surface management is the continuous practice of finding, monitoring and reducing every point where an attacker could try to enter your systems, move through them or take data out. Your attack surface is the full set of those exposed points, spread across on-premises systems, cloud services, remote access and the suppliers connected to you.

The idea comes straight from how attackers work. The US National Institute of Standards and Technology defines an attack surface as the set of points on the boundary of a system where an attacker can try to enter, cause an effect or extract data. Every internet-facing server, login page, API and forgotten test box is one of those points.

This matters more each year because exposed assets have become the way in. In the Verizon 2025 Data Breach Investigations Report, exploitation of vulnerabilities was the initial access route in 20 percent of breaches, up 34 percent on the year before. Most of those assets were reachable long before anyone attacked them.

Why Your Attack Surface Keeps Growing

A modern attack surface grows on its own. Every new cloud account, SaaS subscription, API, remote laptop and acquired company adds assets that face outward and most appear faster than security teams hear about them.

Why Your Attack Surface Keeps Growing

Cloud platforms let a developer stand up a public database or storage bucket in minutes often with no central review. Remote and hybrid work push the boundary into home networks and personal devices. Software now runs on other software so every integration opens another public endpoint that has to be found and secured.

Each change is small and reasonable on its own. Together they open a steady gap between what you actually run and what you think you run and that gap is where attackers live.

Types of Attack Surface

Your attack surface is not one thing. It is several layers and each needs finding and watching in a different way.

  • Internet-facing systems: Web servers, login portals, email and public IP ranges that anyone online can reach and probe.
  • Cloud and SaaS assets: Storage buckets, databases, containers and third-party apps, often spun up outside central control.
  • Remote access and edge devices: VPN gateways, firewalls and appliances that sit at the perimeter and are exposed by design.
  • Shadow IT and forgotten assets: Old subdomains, test environments and tools nobody decommissioned or logged.
  • Supply-chain connections: Suppliers, managed services and software with a path into your data or network.
  • Human and identity surface: Accounts, credentials and access rights that phishing or a leaked password can turn into a way in.

Two disciplines map these from different angles. External attack surface management or EASM, looks from the outside in and discovers the internet-facing assets an attacker would find first. Cyber asset attack surface management, or CAASM, works from the inside out and pulls cloud, device and identity data into one deduplicated inventory. Both terms were coined by the analyst firm Gartner and are now standard vocabulary.

The Business Cost of Unmanaged Exposure

An unmanaged attack surface has a measurable cost and the Verizon 2025 Data Breach Investigations Report puts numbers on it. Exploitation of vulnerabilities was the initial access route in 20 percent of breaches, a 34 percent rise on the previous year.

The pressure has moved to the perimeter. Edge devices and VPNs made up 22 percent of the vulnerability exploitation Verizon tracked, up from 3 percent the year before, an almost eightfold increase. Only 54 percent of those edge flaws were fully patched over the year and the median time to do it was 32 days.

The surface you do not own counts too. Third-party involvement in breaches doubled to 30 percent and ransomware appeared in 44 percent of breaches. An exposed supplier or a single unpatched appliance is often the cheapest route in, so attackers take it.

Real-World Cases

MOVEit and the Exposed File Transfer App (2023)

In May 2023 the Cl0p ransomware group began mass-exploiting a critical flaw in Progress MOVEit Transfer, a file-transfer application many organisations expose to the internet. The vulnerability, CVE-2023-34362, carried a CVSS score of 9.8 and allowed SQL injection into the app.

Attack Surface Management Real-World Cases

Progress patched it within days but the window was enough. CISA and the FBI reported that the group compromised more than 3,000 US organisations and over 8,000 worldwide, many through a single supplier that ran MOVEit on their behalf. Knowing the app was internet-facing and retiring or isolating it was the difference.

Ivanti Connect Secure and the Perimeter Appliance (2024)

In January 2024 CISA issued its first emergency directive of the year over two chained vulnerabilities in Ivanti Connect Secure, a VPN appliance that sits on the network edge. CVE-2023-46805 allowed an authentication bypass and CVE-2024-21887 allowed command injection and together they were being mass-exploited.

The directive did two things at once. It told agencies to apply Ivanti’s mitigation immediately because no patch was yet available and it required them to report a complete inventory of every affected appliance to CISA within about a week. You cannot mitigate or account for a device you have not found which is why a full inventory sits at the heart of the response. Before you can fix an exposed device you have to know you have it.

Miljödata and the Supplier Surface (2025)

In August 2025 attackers hit Miljödata, a Swedish supplier of HR and work-environment software used by around 80 percent of the country’s municipalities. Swedish authorities confirmed the ransomware attack disrupted services at 164 municipalities and four regions and the data was later published when a ransom was refused.

More than 2.2 million people had personal records exposed including sick-leave and rehabilitation details. Not one of those municipalities was breached directly. Their exposure ran through a supplier they depended on which is exactly the part of the attack surface that inventories tend to miss.

Attack Surface Management and Compliance

Knowing and controlling your assets is no longer just good practice. Several regimes now require it and Swedish organisations sit under more than one.

NIS2 and Cybersäkerhetslagen put asset awareness into law. NIS2 is implemented in Sweden as Cybersäkerhetslagen (SFS 2025:1506), in force from 15 January 2026. Article 21 requires risk analysis and security measures that assume you know what you run and covers supply-chain security and Article 20 makes senior management personally accountable. Our NIS2 guide sets out the full duties.

DORA is explicit about it. The Digital Operational Resilience Act, Regulation (EU) 2022/2554, applies to financial entities and is supervised in Sweden by Finansinspektionen. Its Article 8 requires firms to identify, classify and document all ICT-supported functions, information assets and their dependencies and to review that map at least yearly. See our DORA guide.

ISO/IEC 27001 starts from the same place. Its 2022 revision opens Annex A control 5.9 with an inventory of information and associated assets, each with an owner and adds controls for vulnerability and configuration management. Our ISO 27001 guide covers the certification path.

How to Find Your Hidden Attack Surface

You cannot manage what you have not found so attack surface management starts with discovery from the outside in, the same way an attacker would map you.

  • Certificate transparency and passive DNS: Public logs of issued certificates and historical DNS records reveal subdomains and hosts you may have forgotten.
  • Internet-wide scanning: Services that continuously scan the public internet show which of your IP addresses and ports are open and what is running on them.
  • Cloud and account enumeration: Querying your own cloud provider APIs surfaces storage, databases and services that never went through central review.
  • Leaked credential and code searches: Public code repositories and breach data expose keys, tokens and logins that widen the surface.

Some exposure is visible if you look. Forgotten subdomains still resolving, development and test systems reachable from the internet, admin panels open to the public and cloud storage left world-readable are all common findings on a first scan.

The hard truth is that this work is never finished. The surface changes every time someone ships a service or opens an account so a one-off audit goes stale within weeks. CISA’s binding operational directive sets a pace worth borrowing. It requires US federal civilian agencies to run automated asset discovery every 7 days rather than once a quarter or once a year.

How to Reduce Your Attack Surface

Once you can see your attack surface, the goal is to make it smaller and keep it that way. The steps below are ordered and the first one is non-negotiable.

How to Reduce Your Attack Surface
  • Build one authoritative inventory: Keep a single, continuously updated record of every asset, who owns it and whether it faces the internet.
  • Discover from the outside in: Scan your own perimeter regularly so you find exposed assets before an attacker does.
  • Reduce what is exposed: Decommission dead systems, close unnecessary ports, take test environments off the public internet and put multi-factor authentication on every remote and admin login.
  • Prioritise by real risk: Rank fixes using the CISA Known Exploited Vulnerabilities catalogue and exploit-prediction scoring rather than severity alone.
  • Patch the edge fast: Treat internet-facing appliances and VPNs as urgent and measure how long they stay unpatched.
  • Extend it to suppliers: Track which third parties connect to you and hold them to the same standard.
  • Watch for change: Monitor continuously so new exposure is caught as it appears.

Reducing exposure connects directly to fixing the flaws you find which is the job of vulnerability management. Start with the inventory. Everything else depends on knowing what you have.

Myths & Facts

Myth

Attack surface management is just another word for an asset inventory.

Our firewall covers the attack surface.

We are too small to have an attack surface worth mapping.

An annual scan is enough.

No regulation actually requires this.

Supplier security is the supplier's problem.

Fact

An inventory is a static list. Attack surface management is continuous discovery, monitoring and reduction of exposure from the attacker's side, including assets no inventory ever recorded.

A firewall protects assets you already know about. It does nothing for the forgotten subdomain, the public cloud bucket or the exposed supplier, which are where breaches actually start.

Attackers scan the whole internet indiscriminately. The MOVEit and Ivanti campaigns hit any exposed instance they found, regardless of the organisation's size.

The surface changes every time someone ships a service or opens an account. CISA requires US federal civilian agencies to run automated asset discovery every 7 days for this reason.

NIS2 Article 21, DORA Article 8 and ISO 27001 Annex A 5.9 all require you to identify and manage your assets, and NIS2 Article 20 makes the board personally accountable.

Verizon found third-party involvement in 30 percent of breaches in 2025. The Miljödata attack exposed more than 2.2 million people through a supplier, not through the municipalities themselves.

Test Yourself

Four real-world scenarios, then six knowledge questions. See how prepared you would be under pressure.

Scenario Simulation

  1. A first external scan of your company turns up a login page on an old subdomain nobody remembers setting up.

    What is the right first move?

    • Ignore it, since no team owns it
    • Add it to your inventory, then assess and decommission or secure it
    • Assume the firewall covers it
  2. Your organisation runs a file-transfer application exposed to the internet, and news breaks of a critical vulnerability being mass-exploited.

    What does attack surface management tell you to prioritise?

    • Wait for the next quarterly patch cycle
    • Patch or isolate the internet-facing app immediately
    • Focus on internal workstations first
  3. A national authority orders urgent action on a widely used VPN appliance, and the first instruction is to report every affected device you run.

    Why does the inventory come before the patch?

    • Because patching is optional
    • Because you cannot fix or account for devices you have not identified
    • Because inventories satisfy auditors and nothing more
  4. A supplier that holds your HR data is hit by ransomware, though your own systems are untouched.

    How should this shape your attack surface management?

    • It is the supplier's problem, not yours
    • Include suppliers and their access in your attack surface and hold them to your standard
    • Nothing, since your own network was not breached

Knowledge Test

  1. In the Verizon 2025 DBIR, roughly what share of breaches used exploitation of vulnerabilities as the initial access route?

    • 5 percent
    • 20 percent
    • 50 percent
    • 80 percent

    Verizon reported 20 percent, a 34 percent rise on the previous year.

  2. How did the share of edge devices and VPNs in tracked vulnerability exploitation change in the 2025 DBIR?

    • It fell by half
    • It stayed flat
    • It rose from 3 percent to 22 percent, almost eightfold
    • It reached 90 percent

    Edge and VPN exploitation grew from 3 percent to 22 percent, an almost eightfold increase.

  3. What does external attack surface management (EASM) focus on?

    • Internal HR records
    • Internet-facing assets visible from outside the organisation
    • Employee training schedules
    • Physical building security

    EASM discovers and monitors the internet-facing assets an attacker sees first.

  4. How often does CISA's binding operational directive require US federal civilian agencies to run automated asset discovery?

    • Every 7 days
    • Once a month
    • Once a quarter
    • Once a year

    BOD 23-01 requires asset discovery every 7 days and vulnerability enumeration every 14 days.

  5. Which control opens the ISO/IEC 27001:2022 Annex A asset section?

    • Encryption of all data
    • An inventory of information and associated assets with owners
    • Mandatory penetration testing
    • 24/7 security monitoring

    Annex A 5.9 requires an inventory of information and associated assets, each with an owner.

  6. According to the 2025 DBIR, how did third-party involvement in breaches change?

    • It disappeared
    • It doubled to 30 percent
    • It dropped to 5 percent
    • It was not measured

    Third-party involvement doubled to 30 percent, underlining supplier exposure.

Take It with You

Share the Summary PDF with Your Team

A short distilled brief in PDF: key findings, red flags and action steps.

Download summary PDF

Why Training Matters

Tools discover the attack surface, but people create it. Every account opened, service launched and supplier onboarded adds exposure, so the staff making those decisions need to understand the risk they introduce.

This is also a board-level duty. Under NIS2 Article 20, senior management is personally accountable for cybersecurity risk management, which means asset and exposure awareness has to reach beyond the security team. Regular training keeps that awareness current as the surface changes.

Frequently Asked Questions

What is attack surface management?

Attack surface management is the continuous practice of finding, monitoring and reducing every point where an attacker could reach your systems or data. It covers internet-facing systems, cloud services, remote access, forgotten assets and connected suppliers, and it works from the attacker's point of view rather than from an internal list.

What is the difference between attack surface management and vulnerability management?

Attack surface management finds and reduces every exposed asset, while vulnerability management finds and fixes the specific flaws on assets you already track. Attack surface management answers what do we expose, and vulnerability management answers what is wrong with it. You need both, and the first feeds the second.

What is external attack surface management (EASM)?

External attack surface management, or EASM, discovers and monitors the internet-facing assets an attacker can see from outside your organisation. It maps domains, IP addresses, open ports, cloud services and exposed applications continuously. The term was coined by the analyst firm Gartner and describes the outside-in half of attack surface management.

What is the difference between attack surface management and asset management?

Asset management tracks the devices and software you own for inventory and licensing, usually from the inside. Attack surface management focuses on which of those assets are exposed and reachable by an attacker, and it actively discovers assets that asset management never recorded, such as forgotten subdomains and shadow cloud accounts.

Does NIS2 require attack surface management?

NIS2 does not use the phrase attack surface management, but it requires the underlying work. Article 21 mandates risk analysis and security measures that assume you know your assets, plus supply-chain security, and Article 20 makes senior management personally accountable. In Sweden this applies through Cybersäkerhetslagen, in force since 15 January 2026.

How often should you scan your attack surface?

Scan continuously rather than on a fixed annual schedule, because your attack surface changes whenever a service, account or device is added. As a benchmark, CISA's binding operational directive requires US federal civilian agencies to run automated asset discovery every 7 days and vulnerability enumeration every 14 days.

You Understand the Risk.
Now See Where You Stand.

Book a 30-minute briefing with one of our analysts, or run the free breach check first to find out what attackers already know about your organisation.

Book a 30-Min Briefing
No sales pitch, just a straight assessment

How eBuilder Security Can Help

Awareness is the first layer. These are the services that turn it into measurable protection.