Day Zero Confidence

Know if a patch will break production before you deploy it.

Day Zero Confidence tests critical patches on isolated copies of your own servers, then tells you, application by application, whether it's safe to roll out.

Request a pilot See how it works

Example report

November cumulative update, Windows Server 2022

Tested on copies of 11 servers in 4 application groups

Application groupCopies passedVerdict
SQL Server4 of 4Go
Web servers3 of 3Go
File serversOne copy needed a second reboot.2 of 2Caution
Domain controllersNetlogon failed to start on one copy.1 of 2Wait
Roll out to SQL and web first. All test copies deleted.

Every critical patch forces the same bad choice.

Patch now

Close the vulnerability today and hope nothing breaks. When it does, it breaks in production, in front of users.

Wait

Hold for the change window, the test lab and other people's reports on forums. Meanwhile the systems stay exposed for days or weeks.

Test labs drift from production, and pilot groups test on real users. Neither tells you how your own servers will react to this patch.

How it works

Everything happens on temporary copies. Your production servers are never touched.

  1. Copy

    Make isolated, temporary copies of a sample of your real servers from your existing backups or snapshots.

  2. Patch

    Apply the new patch to the copies only.

  3. Check

    Reboot them and run health checks: services start, applications respond, the vulnerability is closed.

  4. Clean up

    Delete every copy automatically, whatever the result.

  5. Answer

    Get a go, caution or wait verdict for each application group, with the evidence behind it.

The Day Zero Confidence dashboard showing a demo run: 7 of 9 systems passed and the verdict is Proceed with Caution.
The dashboard after a demo run. Two of nine copies failed, so the verdict is Proceed with Caution, and each failure is explained below it.

Why it's different

  • Your servers, not someone else's

    Other tools score patches with data from other companies' environments. This tests the patch against copies of yours.

  • No test lab to build

    It works through the backup platform or hypervisor you already run, so there's no second environment to buy or keep in sync.

  • Production is never touched

    The patch only ever goes onto temporary copies, and every copy is deleted at the end of the run, even when a test fails.

Built for Rubrik and Cohesity, and works with Microsoft Hyper-V.

VMware, Commvault and Veeam support is in development.

Try it on your next Patch Tuesday

We're taking a small number of pilot customers. In a pilot, you get:

  • A test of the next critical patch on copies of a sample of your servers
  • A written go, caution or wait report for each application group
  • Setup help and a direct line to the person who built it
Request a pilot info@dayzeroconfidence.com