Home / Security monitoring / Attack surface monitoring

Attack surface monitoring for small business

You cannot defend what you do not know is online. Attack surface monitoring finds every domain, server, login page and open port your business exposes, checks them for known vulnerabilities and flags changes. The part scanners skip is deciding what matters. That is done by a person, and it is what turns a report into fixes.

What your attack surface is

Your attack surface is every way into your business that someone on the internet can try. Your website is one. So are the subdomain you made for a test two years ago, the staff login page, the old server a contractor set up, and the cloud storage bucket nobody remembers.

It changes without anyone deciding to change it. A new plugin, a new SaaS tool or a DNS record left behind each add something. Attack surface monitoring means finding these things continuously, not once.

What is scanned

We start with discovery, then check each asset we find.

Discovery of domains, subdomains and servers

Public records, certificate transparency logs and DNS show what exists under your names, including things you forgot.

Open ports and services

Which doors are open to the internet, and whether they should be. A database or admin panel reachable from anywhere is a common finding.

Known vulnerabilities

Software versions are matched against published flaws. This is vulnerability scanning, and it feeds patch management.

Certificates, headers and misconfiguration

Expired or weak TLS certificates, missing security headers and risky settings.

Leaked credentials

Staff email addresses and passwords that show up in breach data or on the dark web, so they can be rotated early.

Vulnerability scanning is not a penetration test

A scanner finds known problems quickly and cheaply. A penetration test finds the ones that need a human to chain together. They answer different questions. Monitoring keeps the first one current between tests, and a test checks the depth now and then.

If a customer or regulator asks for a penetration test, a scan report does not replace it. If they ask whether you watch your exposure all year, a test does not replace the scan.

What a human adds to the scanner output

Scanners are loud. A typical report lists dozens of findings, many of them low risk, duplicated or false positives. A small business without a security team cannot sort that, so the report gets filed and nothing happens.

Our analysts read the output first. They remove noise, rank what is left by how reachable and damaging it is, and say what to do in plain language. The scanner score alone does not decide priority. A medium finding on your login page can matter more than a high one on a server that nothing connects to.

Then comes follow-through: the right person gets a clear task, the fix is checked, and the finding closes with a date. That closed loop is what an auditor wants to see.

From findings to patch management and evidence

Patch management is the habit of fixing known flaws in a sensible order and showing you did. Monitoring supplies the list and the proof. After a few months you hold a history: when each issue appeared, when it was triaged, when it was fixed.

That history supports GDPR Article 32, which expects regular testing of your measures. It also supports NIS2 readiness, which expects vulnerability handling you can document. It does not make you compliant on its own, and we do not claim that. Your lawyer decides what applies to you.

What external monitoring does not see

Watching from the outside shows what an attacker sees. It does not see inside your office network, on staff laptops or in your cloud admin consoles. Endpoint protection, security awareness training and internal audits cover those. Be wary of any provider that implies one scan covers everything.

For the broader picture see security monitoring for small business.

Common questions

What is attack surface monitoring?

It is the continuous discovery and checking of everything your business exposes to the internet: domains, subdomains, servers, open ports, login pages and certificates. It spots new or changed exposure before an attacker does.

Is vulnerability scanning the same as a penetration test?

No. A scan checks systems against known weaknesses and runs often. A penetration test is a person actively trying to break in, usually once or twice a year, and goes deeper on a narrower scope.

How often should a small business scan for vulnerabilities?

Continuously for exposure changes, and at least weekly for known-vulnerability checks is a common choice. New flaws are published every day, so a scan from last quarter says little about today.

Do you need access to my systems?

External monitoring works from the outside, using your domain names and public information. Active scanning is limited to assets you have authorised.