Skip to main content
Regulaxy
עברית
Protect

One patch, many CVEs, many hosts.

You cannot schedule a vulnerability. You can schedule a patch. Regulaxy folds the list into the unit the work is actually done in.

Get a demo
The artifact

A schedulable patch group

The problem

A CVE list is not a work list.

The feed arrives at one row per vulnerability per host. The same patch repeats across dozens of rows, the same host repeats across dozens of patches, and the person who has to book one night is looking at a thousand rows with no order in them.

Figure — folding a scan matrix into one patch

What it looks like

One row per patch

Carrying the CVEs it closes, the highest CVSS among them, the affected host count and the system names. From there you go to a window.
How it works
  1. 01

    Ingest

    A daily file from the SOC — CSV, JSON or Excel. Columns are resolved by header name, and where the name is unfamiliar, by the value itself: a CVE id, a severity label, a hostname.

  2. 02

    Fold

    Rows sharing a CVE id are merged: hosts unioned, the highest CVSS kept, the worst severity kept, and distinct patch references joined and logged.

  3. 03

    Group by patch

    The register is presented by patch: which CVEs it closes, how many hosts, and which business systems those hosts belong to.

  4. 04

    Schedule

    From a patch row you open the scheduling wizard with its hosts already selected. All that is left to decide is the night.

What it connects to

Any source that can write a file. No API required and no outbound access needed.

  • SOC feeds (CSV / JSON / Excel)
  • Vulnerability scanners
  • WSUS target groups
  • Manual entry
Related capabilities

Show us your worst window.

Bring the one that keeps slipping. Thirty minutes, your estate, no slides.

Get a demo