oolak
Live demo Free 14-day trial →
oolak / Use cases / Urgent vulnerabilities
Urgent vulnerabilities

A critical vulnerability is in the news. Are we affected?

When a new vulnerability hits the headlines, everyone asks the same question at once. oolak answers it with a list of affected systems, their owners and how exposed each one is.

Start a free 14-day trial → See how it works
From a public name to the server behind it, and the problems waiting there.
Today

What usually happens

  • The security team exports scan results and searches them by hand.
  • Nobody is sure which of the affected servers face the internet.
  • Owners are chased by e-mail, and nobody knows when the work is really done.
With oolak

What changes

  • You can answer "are we affected?" the same morning.
  • Internet-facing systems are fixed first.
  • Every fix is confirmed by a scan, not by an e-mail.
With oolak

How it works, step by step

  1. Find what is affected

    Search the vulnerability or ask the AI assistant, and oolak lists every affected asset with its owner.

  2. See the real exposure

    The relationship map shows which of those systems can be reached from the internet.

  3. Scan just those systems

    A workflow asks for approval and launches a targeted scan on the affected hosts only.

  4. Hand it to the owners

    Tickets open automatically for the right teams, with a deadline based on the risk.

  5. Confirm the fix

    When a team reports a fix, a rescan confirms it and the finding closes.

Features

The features behind it

Risk-based prioritisation

Fix the few things that really matter, first.

oolak scores every vulnerability by how likely it is to be exploited, how important the asset is and whether it can be reached from the internet.

Learn more Relationship map

Follow the path from the internet to your data.

oolak links domains, IP addresses, certificates, servers and applications on one map.

Learn more Workflows

Let routine security work run itself.

Build workflows by filling in a form, without writing code.

Learn more Verified closure

Only call it fixed when it is really fixed.

A finding can disappear from a scan because it was fixed, or simply because the server was switched off that day.

Learn more AI assistant

Ask your security data a question, in plain language.

Connect the AI assistant you already use, or a model running inside your own network, and ask things like "which internet-facing servers have critical issues this week?".

Learn more

See oolak on your own data in 14 days.

We install oolak in your environment, connect your tools and show you your real risk picture. You keep everything it finds.

Start a free 14-day trial → Try the live demo
For engineers

Technical details

Which data sources does this use?
Scanner findings from Tenable and other connectors, CISA KEV and FIRST EPSS for exploitation data, the asset inventory for owners and criticality, and the attack surface graph for internet exposure.
Can a webhook start the response?
Yes. A workflow can start from a webhook sent by a threat feed, collect the affected assets, wait for approval and then launch the scan and send notifications.

More problems oolak solves

Shadow IT

Which of our servers has everyone forgotten about?

Bring forgotten test servers, old subdomains and unmanaged hosts to light, and give each one an owner.

See how it works Prioritisation

We have thousands of findings. Where do we start?

Turn an endless list into a short one, ranked by real threat, business importance and internet exposure.

See how it works