Attack Surface Analysis
How your organisation looks from outside, set down with evidence
We set down how your organisation looks to an attacker from outside, as a list of assets backed by evidence.
We find assets visible from outside, such as domains, IP addresses, and servers and admin pages open to the internet, and look at when each appeared and how it has changed.
What of ours is open to the internet, and is any of it unknown to us?
We tell you which assets were missing from your list, and what to close first, with the evidence.
Expert reviewed
When it fits
- You worry about assets you don't know of
When you wonder whether servers or domains you don't know about are open to the internet, we start by setting out everything we can see open today.
- Your organisation or systems have changed a lot
After a merger or acquisition, a move to the cloud, or a service being redesigned or shut down, your asset list and what is really open to the internet easily drift apart.
- Many teams and suppliers open new assets
Campaign sites, test servers and other assets set up by many teams and suppliers have piled up, and some no longer have a clear owner.
- Before setting the scope of testing
Setting down what can be seen from outside before you commission vulnerability assessment or penetration testing means less is left out of scope.
The SAFE SQUARE approach
Following the links
Starting from the domains you give us, we follow the connections all the way to assets that were never on your list.
Ownership, on evidence
An analyst checks the evidence that each candidate is yours; where the evidence is thin, the asset goes into a separate ‘ownership to confirm’ group.
Seen over time
For each asset we record when it was first seen and what has changed, so you can see what opened when, and what was never closed.
What we look at
Every organisation shows a different face to the internet; below are things we often look at.
Names and addresses
- Domains and subdomains
- IP addresses and ranges
- Names in TLS certificates (the domains a server certificate carries)
- Addresses tied to cloud services
What is open to the internet
- Websites and services
- Login and admin screens
- Remote access points
- APIs and file storage open to the internet
Ownership and change
- Assets whose owner is not confirmed
- Assets missing from your asset list
- Assets still open after they fell out of use
- Assets that appeared or disappeared, and their history
How it runs
Set the targets
Based on the organisation and brands to look at and the assets you already know of, we settle the scope and how it will run.
Gather and link
We gather external observations and link them through their relationships and history to draw up the assets that may be yours.
Confirm ownership
Analysts review the evidence that each candidate is yours, and separate confirmed assets from those whose ownership still needs checking and those that are not yours.
Report
We explain the asset list and its evidence and the priorities for action based on the likely impact, and hand over the items for your staff to check.
A one-off assessment is the usual form; if you often open new domains and services, monitoring that checks for changes at a set interval is added. Which form it takes is decided with you. See the three ways to run it
What you receive
Assets found, with evidence
For each asset found from outside, the evidence that it is yours, when it was first seen and what has changed.
Assets whose ownership needs confirming
Assets that look like yours but lack evidence, gathered separately so your staff can check them.
Priorities for action
Based on the likely impact, what to close or add to your asset list first.
A baseline for next time
This result is kept as a baseline, so the next assessment or monitoring round can compare what has changed.
Whether an asset found has a vulnerability, or can actually be exploited, can be checked next in Vulnerability Assessment & Penetration Testing (VAPT).
Four assets missing from the asset list
Scope: two company domains and one affiliate
| Asset | Finding | Evidence and action |
|---|---|---|
| A subdomain for an event | Confirmed as yours | The same name appears in your certificate, and it has stayed open since the campaign ended two years ago. Close it first. |
| An admin page on an old domain | Confirmed as yours | A login page is still up on the domain you replaced three years ago. Close it, or add it to your list. |
| A test server in the cloud | Ownership to confirm | Its name matches one of your services, but it sits in a supplier's account and the records do not show it is yours. Your staff need to confirm. |
| An online shop with a similar name | Not yours | The name is similar, but it is registered to someone else and runs on different infrastructure: another company's asset. Taken off the list. |
- What to do first
- Close the event subdomain and the admin page on the old domain, and ask the supplier who owns the test server and what it is for. This list is kept as the baseline for next time.