HomeBlog › Threat Lab
True story from the field

How I Built a Vulnerability Scanner That Never Trips the Alarm

Updated 2026-07-18 · 8 min read · by Mihai Bătrîneanu
How I Built a Vulnerability Scanner That Never Trips the Alarm

The vulnerability scanners everyone reaches for have two habits that make them useless to the clients who need them most: they demand the IP addresses and subnets no client wants to hand over, and they bury the real findings under huge annexes of standard, theoretical recommendations nobody can implement. These are not my complaints alone — they are field realities in businesses all over the world. I watched OpenVAS and Nuclei fail real clients this way for years: inflexible, rudimentary, and, on a hardened network, promptly blocked. So I built the opposite — a scanner that needs no input at all. It discovers the network itself, inventories every asset, evaluates the services, and only then runs the real assessment, delivering a report a client can actually act on rather than file away. And because real client networks are defended, it also had to learn to move like a cat: evaluate the prey, step softly, and never trip a single alert. This is how it was born.

ContentsThe tools everyone uses — and why they fail real clients
The loud scanner finds nothing
Why turning up the stealth also fails
The cat: evaluate the prey, then move
Discovery without asking — the scanner maps the network itself
A report you can act on, not file away
Frequently asked questions

The tools everyone uses — and why they fail real clients

The scanner was born from frustration, not ambition — and from a frustration anyone who runs assessments anywhere in the world will recognize. The standard vulnerability tools, OpenVAS and Nuclei and their kind, are built for a world that does not match how real engagements work. OpenVAS is inflexible and rudimentary; Nuclei is narrow and, as a standalone client deliverable, close to useless. But the deeper failure is not the engine — it is what they demand and what they produce.

They demand that you feed them the targets: the IP addresses, the subnets, the map of the network. And here is the reality no one who has done this work will dispute — no client wants to hand you that. The very information the tool needs in order to start is the information the client is most reluctant to give. Then, when the scan finally runs, out comes a huge annex of boilerplate findings and standard, theoretical recommendations: pages of generic advice, hard to implement, tuned to no one's actual environment. The client is left holding a doorstop, not a plan. That double failure — it needs what clients will not give, and it produces what clients cannot use — is what made a different kind of scanner necessary.

The loud scanner finds nothing

Picture the assignment: an authorized vulnerability assessment of a network that had just been through a serious incident and locked itself down hard. A next-generation firewall in front of everything, tuned by people who had been burned and now suspected even the harmless. The job was to find the organization's real exposures before an attacker did — the standard defensive exercise, with full authorization, on the client's own network.

So I did what every instinct says to do: a thorough scan. Many ports, solid probing, all the checks. And the network simply closed on me. The firewall watched the pattern of my probes, recognized it for what it was, and shut the door — connections dropped, sessions killed. Two hours in, I had nothing. Not a partial map, not a list of services. Nothing. The lesson landed at once and it has never left me: on a defended network, force does not get you in. It gets you noticed, and then it gets you cut off. The thorough scan and the blind scan turned out to be the same scan.

Why turning up the stealth also fails

The obvious fix is to reach for the scanner's stealth mode — smaller probes, longer delays, the paranoid settings. It is the natural second guess, and on a modern network it fails for its own reasons. Two of them.

First, naive stealth is still a pattern. Exotic, fragmented, deliberately odd traffic does not look innocent to a next-generation firewall — it looks exactly like someone trying not to be seen, which is its own bright red flag. You did not become invisible; you announced that you were hiding. Second, and more practically, cranking the delays up can make a scan stall forever. Push the back-off high enough against a filtered host that never answers, and the scanner sits there waiting on silence — a reply that will never come — until the whole run hangs and dies without producing a result. Too loud gets you blocked. Too weird gets you flagged. Too slow gets you nowhere. The answer was not on the dial between fast and stealthy at all.

The cat: evaluate the prey, then move

The answer came from watching how a predator that actually catches things behaves. A cat does not sprint at its prey the instant it sees it. It stops. It reads the situation — distance, cover, whether the prey is alert. It moves in soft, measured steps, pausing between them, and it commits to the pounce only when it is certain the move will not be detected. Force is the last thing it uses, and only once.

That is exactly what the scanner had to become. Not loud, not exotic — ordinary. Traffic that looks like the normal life of the network, not like a tool. It touches only the handful of things that actually reveal exposure — the doors that matter, the services an attacker would truly care about — instead of hammering everything. It paces itself and reads resistance: when the network pushes back, it eases off before it trips anything, rather than pushing harder. And — the detail that took real pain to learn — its patience is capped. It will wait, but never forever; the moment waiting stops paying off it moves on, so it never stalls into that dead hang. Evaluate, step, pause, read, commit only when it is safe. A predator with patience, not a battering ram.

Discovery without asking — the scanner maps the network itself

The first requirement wrote itself from the client problem: the scanner must need nothing to start. No IP list, no subnet map, no questionnaire — because that is the very thing clients will not give you. It has to arrive on the network and understand the place on its own.

So it begins by listening. A live network is already talking — devices announce themselves, traffic reveals the shape of the place — and a great deal about the topology and the live hosts can be learned purely by observing, without sending a single packet of your own. Zero injection, zero footprint, nothing for a firewall to catch, because nothing has been done yet. From that, the scanner draws the map, then inventories every asset it can see — the real estate as it actually exists, including the machines the client forgot they had — evaluates the services each one exposes, and only then runs the real vulnerability assessment, aimed at what is genuinely there. Discover, map, inventory, evaluate, then assess — and never once ask the client for the answer key.

A report you can act on, not file away

The adaptive scan flowed straight through the network that had blocked everything else. It mapped the estate, inventoried the assets, surfaced the real weaknesses the organization genuinely needed to fix — and the defenders never saw a thing. Not one alert fired. But mapping a hardened network quietly is only half the job. The other half is the part the standard tools get most wrong: what the client actually receives.

Not a huge annex of boilerplate findings and theoretical advice, but a detailed, personalized report tied to the client's real network — recommendations that can genuinely be implemented, prioritized by what matters to them rather than by a generic severity score that knows nothing about their business, and correlated with the attacks their SOC actually sees. That is the difference between a scan that generates paperwork and a scan that reduces risk. It is exactly what CYBER3 Global Scan was built to be: autonomous discovery with zero client input, an adaptive engine that maps a hardened network without tripping a single alert, and a report that tells you what to fix and why it matters to you. Not unstoppable because it is loud — unstoppable because it is patient, and because it hands you something you can actually use.

A scan loud enough to get blocked is a scan that sees nothing.
CYBER3 Global Scan is adaptive by design — it studies the target, moves in measured steps, and maps your real exposure without tripping a single alert. Autonomous discovery, vulnerability assessment, and MATCH of alerts to weaknesses, with verified authorization.
Explore CYBER3 Global Scan →
🛡️ Try CYBER3.AI free
AI security copilot + Global Scan of your own network. 700 free credits on sign-up — no card, no strings.
Start free →
About the author: Mihai Bătrîneanu
Founder of CYBER3.AI and a 30-year veteran of internet infrastructure. In 1994 he founded PC-NET, the first Internet Service Provider in Eastern Europe, and built Romania's first e-mail, ADSL broadband and VoIP services. He now builds CYBER3.AI — a sovereign Security LLM and autonomous Security Operations Center.

Frequently asked questions

Does CYBER3 Global Scan need the client to provide IP addresses or subnets?

No. Traditional scanners like OpenVAS require you to feed them the targets — the IPs and subnets — which is exactly the information clients are most reluctant to share. CYBER3 Global Scan needs no input to start: it discovers the live network on its own, builds the map, inventories every asset, evaluates the services, and only then runs the assessment. Autonomous discovery first, with verified authorization, and no target list handed over by the client.

How is CYBER3 Global Scan different from OpenVAS or Nuclei?

Three ways. It needs no target list — it discovers the network and inventories assets autonomously, instead of demanding the IPs and subnets clients will not give. It is adaptive rather than aggressive, so it maps a hardened network without being blocked or tripping alerts, where those tools get cut off. And it delivers a personalized, actionable report tied to the client's real environment and correlated with observed attacks — not a huge annex of standard, theoretical recommendations that are hard to implement.

What is adaptive vulnerability scanning?

Adaptive vulnerability scanning is a method where the scanner evaluates the target and adjusts its behavior in real time instead of running a fixed, aggressive sweep. It looks like ordinary network traffic, focuses only on the services that actually reveal exposure, paces itself and eases off when the network pushes back, and caps its own delays so it never stalls. The goal is to map real weaknesses on a defended network without triggering the firewall or IPS — which a loud, static scan cannot do.

Why do aggressive vulnerability scans get blocked on hardened networks?

Because a next-generation firewall or IPS recognizes the pattern. A thorough scan hits many ports quickly and probes hard, which is exactly the signature these systems are tuned to detect and cut off. On a hardened network the aggressive scan is spotted within minutes, its sessions are dropped, and it returns little or nothing. Force does not defeat a modern defense — it announces itself to it.

Is stealth mode better than a fast scan?

Not on its own. Naive stealth — tiny fragmented probes and very long delays — creates its own problems. Deliberately odd traffic looks like someone trying to hide, which a next-generation firewall flags in its own right, and extreme delays can make a scan hang forever against filtered hosts that never respond. The effective approach is neither loud nor exotic: ordinary-looking, focused, self-pacing traffic that reads resistance and backs off, with passive discovery done first.

Can an authorized vulnerability scan avoid triggering alerts?

Yes — when it is adaptive rather than aggressive. On an authorized assessment, a scanner that behaves like normal network traffic, targets only the services that matter, listens passively before probing, and paces itself to the network's tolerance can map exposure without tripping the defender's sensors. That is valuable for defenders precisely because it shows what a patient real attacker could learn, and it does so without disrupting production systems.

What makes CYBER3 Global Scan different from a normal scanner?

CYBER3 Global Scan is adaptive by design. Instead of a fixed aggressive sweep it begins with passive, zero-footprint discovery, then probes surgically and quietly — focused on real exposure, self-pacing, capped so it never stalls — so it maps a hardened network without tripping alerts. It then correlates the weaknesses it finds with the attacks a SOC actually observes (the MATCH), turning a scan into prioritized, defensible action. All of it runs only with verified authorization.

Protejează-ți telefonul — CYBER3, gratuit pe Google Play
Instalează