001 CTEM: attack paths + real detection

Which attack paths would your detection miss?

Bonanza maps who can reach your crown jewels and ranks every path by whether your own monitoring would see it. Read-only.

Deterministic engine, ranked remediation and what-if testing. Now working with design partners.

002 The problem

A path can be open and invisible at the same time.

Security teams keep two views of risk. One maps how an attacker could get in. Another tunes what the SOC detects. Almost nobody checks whether the two agree.

Red team view: attack paths

What an attacker could reach, based on network topology, identities and privileges.

Attack-path tools, penetration testing

Blue team view: detections

What is detected right now, based on logs, detection rules and incident response.

Detection rules, log sources
  • Which attack paths would our SOC actually see?
  • Which paths are not defended?
  • How critical is that exposure?
Your environment as a box. The attack-path circle and the detection circle slide together, but even overlapping they leave a blind spot and a part of the environment no one checks. YOUR ENVIRONMENT ATTACK PATHS DETECTION BLIND SPOT SEEN NOISE NO ONE LOOKS HERE

Two separate views. Watch them move together, then tap any area.

003 From the CISO's chair

More alerts. More rules. Still no answer to "what would we miss?"

The board asks whether you are covered. The SOC is buried in alerts and tuning. Adding rules adds noise; it does not tell you which attack paths no one would see.

59%

of security leaders say they have too many alerts.

Industry survey, 2025 (2,058 leaders)
73%

name false positives as their top detection challenge.

SANS 2025 Detection and Response Report
13%

of SIEM detection rules are broken and will never fire.

Industry SIEM detection report, 2025
14%

of simulated attacks raised an alert, though 54% were logged.

Industry simulation report, 2025 (160M+ simulations)

Bonanza turns the pile into an order: which paths are invisible, which single fix closes the most of them, and which logs you pay for that no rule uses.

004 What you get

See it. Prioritize it. Fix it.

See

Every attack path to your crown jewels, and which steps your SOC would and would not detect.

Prioritize

The invisible paths rise to the top, so the team works on the gaps that matter, not the loudest alerts.

Take action

Fixes ranked by how many invisible steps each closes, tested as a what-if before anything changes.

All on one map, drawn the way the product draws it

  • Users and identities
  • Groups and roles
  • Computers and servers
  • Domains and trusts
  • Containers
  • Entry points
  • Crown jewels

005 How it works

From connection to fixed blind spots in four steps.

TopologyAttack pathsDetectionFixes
  1. 01

    Build the environment graph

    Load your directory export: users, groups, computers, permissions and trust relationships.

  2. 02

    Load detection data

    Load your detection rules and a list of the log events you actually collect.

  3. 03

    Analyze every attack path

    Check each step against your detection rules and classify it, so the paths you cannot see rise to the top. No attacks are run.

  4. 04

    Fix and re-check

    See the fixes ranked by how many invisible steps each one closes: a detection rule, a log source or a cut hop. Try a fix on the map first, then re-check once it is live.

007 Design partners

Help us test Bonanza on a real environment.

We are looking for a small group of security teams. It is free during the pilot.

  • You connect a read-only source; we show you the blind paths we find.
  • Your feedback shapes what we build next.
  • A short conversation first, no obligation.

Opens your email app with a message to the founders. We use what you send only to reply to you.

Rona Oran, PhD · product and algorithms · MIT, NASA science missions Tal Poremba · product and go-to-market · cybersecurity product leadership Meet the founders →