Vidimus
Explainer videos NL Start free

VIDIMUS/AFTER A BREACH

The patch is installed. What changed in your data?

On 21 October 2026, PHP released an urgent patch for two vulnerabilities, together called "php2shell". With them, an attacker could run their own code on the web server without a password. Amazon already saw a first attack on 17 October, four days before the patch. Patching closes the door. It does not say what happened inside.

Monday, after the patch. Your IT partner asks: "Can we show that the invoices and consignment notes in the database are still the same as last week?" The history is on the same server. The backup comes from the same system. Nobody can say for certain.

01 / FIRST THIS

What you do now, even without Vidimus.

  • Patch every server running PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or higher. Ask your hosting provider: webshops, portals and old internal applications often run on PHP too.
  • Check the server's history from 17 October onwards: unknown files, new administrators, strange outgoing connections.
  • Replace passwords and keys that were on those servers, such as database and API keys.
  • Report it. If you fall under NIS2, you make a first notification to the CCB (Centre for Cybersecurity Belgium) within 24 hours. If personal data leaked, you report it to the Belgian Data Protection Authority within 72 hours.
02 / THE QUESTION THAT REMAINS

Why nobody can say what changed.

A

The history is on the same server

Whoever can run code on the server can also adjust the history. So it proves nothing about what the attacker did.

B

The backup comes from the same system

A backup shows how things were. It does not prove that it stayed unchanged itself, nor when a change happened.

C

Your customer has to believe you

After a breach, a customer or insurer asks: how do you know this is still the same as before the breach? Your answer comes from the system that was hacked.

03 / NEXT TIME

A snapshot outside your system.

01 · today

A first snapshot

You export your database or a folder. Each row and each file gets a fingerprint on your side. For a database, only fingerprints, the names of tables and columns, and counts go to Vidimus; with the row key, no key values either. For a folder, it is the fingerprints and the file names. Vidimus anchors them within a few minutes, with a timestamp from an independent service.

one record for the whole export
02 · in development

Automatic every night

The same export runs by itself every night. That way you have a fixed starting point for every day.

03 · in development

Comparing after an incident

You put the current export next to the snapshot from before the incident. Per row or file you see: unchanged, changed or new since that day. Your customer or insurer can recompute it themselves, without an account.

Vidimus does not prevent breaches and does not replace a patch, a backup or a security company. The proof only covers data that was anchored before the incident.

04 / QUESTIONS

FAQ.

Was Vidimus itself affected by php2shell?

No. Vidimus does not run PHP. The site is on GitHub Pages, the service runs on Python.

Do we have to upload our database to Vidimus?

No. The fingerprints are computed on your side. For a database, Vidimus only receives fingerprints, the names of tables and columns, and counts; with the row key, no key values either. For a folder, it receives the fingerprints and the file names. Not the content itself.

Can it also cover data from before the incident?

Only if that data was already anchored at the time. A snapshot from today proves what your data looks like today, and that it stayed unchanged after that. That is why it is best to start now.

What does it cost?

One snapshot a day is one record a day. That fits easily within the first 100 records a month, which are free.

Start today: your first snapshot is free.

You create your account in two minutes. No payment details needed. A director identifies your company once with the Belgian eID. Then you record your first snapshot. If you are a hosting provider or IT partner, we will look together at how you can offer it to all your customers.