Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
An attack surface is the sum of every point where an attacker could try to enter or extract data from your organisation—systems, applications, cloud services, people, and physical sites.

What Is an Attack Surface?
An attack surface is the total of all the points where an unauthorised person could try to get into a system, or get data out of it. It includes internet-facing servers and applications, cloud accounts, remote access gateways, employee laptops, third-party integrations, the people who can be tricked into helping, and the buildings that house your equipment. The larger and less understood your attack surface is, the more chances an attacker has of finding one weak point.
It is worth separating the attack surface from the attack vector. The surface is where you can be attacked; the vector is how a particular attack gets in—phishing, a stolen password, or an unpatched vulnerability.
The assets you manage well are rarely the problem. Trouble comes from the ones that fall outside normal processes:
Cloud adoption, remote working, and mergers each add exposure faster than most inventories can track. Every new SaaS integration grants another set of OAuth permissions; every acquisition brings a network nobody on your team has assessed. Edge devices are a particular concern: VPN concentrators, firewalls, and file transfer appliances are internet-facing by design, and attackers move quickly once a flaw is published, as the Citrix Bleed vulnerability (CVE-2023-4966) showed in late 2023.
In late May 2023, the Cl0p ransomware group began mass-exploiting a zero-day SQL injection flaw in Progress Software’s MOVEit Transfer product, tracked as CVE-2023-34362. In the UK, the payroll provider Zellis was among the victims, and staff data belonging to several of its clients—including the BBC, British Airways, and Boots—was exposed. For many affected organisations, the file transfer server was not something they ran themselves; it sat on a supplier’s attack surface that had quietly become part of theirs.
External attack surface management (EASM) treats your organisation the way an attacker would: starting from domain names and IP ranges, it uses certificate transparency logs, DNS enumeration, and internet-wide scan data from services such as Shodan and Censys to find everything publicly reachable, then fingerprints the services found. Internally, the equivalent is a complete asset inventory backed by network discovery and endpoint management data. The first two CIS Critical Security Controls—inventory of enterprise assets and of software—exist for exactly this reason.
| Question | Typical evidence |
|---|---|
| What do we expose to the internet? | EASM results, firewall rules, DNS zone review |
| Which of those systems are vulnerable? | Authenticated vulnerability scans, patch status |
| Who can access what? | Identity reviews, privileged account audits |
| Which suppliers hold our data? | Third-party risk register, contract reviews |
Because the surface changes weekly, a one-off review goes stale quickly. Our continuous vulnerability scanning services keep your external exposure under regular watch, so new assets and new weaknesses are flagged as they appear.
The attack surface is the full set of places where you could be attacked: systems, applications, people, and premises. An attack vector is the specific route or method an attacker uses to get in, such as a phishing email or exploiting an unpatched VPN appliance. Reducing the surface removes opportunities; closing vectors blocks particular techniques.
Start from what an attacker can see. Search certificate transparency logs for your domains, enumerate subdomains, review internet scan data from services such as Shodan, and check cloud billing records and expense claims for unregistered services. Compare the results against your official inventory; every unexplained asset needs an owner or should be shut down.
It usually changes it rather than simply increasing it. You hand some physical and infrastructure risk to the provider, but gain new exposure through identity, misconfigured storage, management consoles, and APIs. Many cloud incidents stem from configuration mistakes rather than provider flaws, so posture monitoring and strict identity controls matter more than in a traditional data centre.
External exposure should be monitored continuously or at least weekly, because new services, certificates, and vulnerabilities appear constantly. A deeper review, including internal assets, suppliers, and social engineering exposure, is sensible once a year and after major changes such as an acquisition, a cloud migration, or the launch of a new customer-facing platform.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.