Vidimus
Explainer videos NL Start free

VIDIMUS/QUESTIONS/DATABASES AND FOLDERS

After a hack, how do you show that your database was not changed?

Short answerOnly with a starting point from before the incident that lies outside the hacked server: a snapshot with a fingerprint per row or per file, anchored with an external timestamp. After the incident, you recompute the same fingerprints and put them side by side: whatever differs, changed. Without such a starting point, your answer comes from the system that was hacked.

Updated on 29 October 2026 · Oskar Verschoren, Vidimus (VO Initiatives BV, Antwerp)

01 / HOW IT WORKS

How it works.

  1. A snapshot before the incidentfingerprint per row or per file

    You export your database, or choose a folder. Each row and each file gets a fingerprint (SHA-256) on your own computer. Only the fingerprints, the names of tables and columns, and counts go to Vidimus; with the row key, no key values either. For a folder: file names and fingerprints.

  2. One record, anchored outside your servered25519 · rfc 3161 · bitcoin

    The list is signed as one record with the key of your system or device and anchored within five minutes: an external timestamp on the group, our ledger as a hash chain, and Bitcoin via OpenTimestamps. Whoever later gets into your server cannot change that starting point unnoticed.

  3. After the incident: put them side by sidefolder today · database in development

    For a folder, you put the current files next to the snapshot: per file you see what is unchanged, changed, moved or missing. For a database, we are building that comparison now (in development); you can already record the snapshot itself today.

  4. Your customer or insurer verifies it themselvescheck page · evidence bundle

    Your customer or insurer does not have to take your word for it: the check page works without an account, and the evidence bundle with its script can be recomputed even without Vidimus.

02 / RIGHT NOW

What you can do right now.

  • Copy the server's history to another place, as soon as possible. Whoever got into the server could also adjust that history.
  • Take a snapshot of the current state now. It says nothing about the past, but from now on every change stands out to whoever checks.
  • If personal data is involved, check whether you have to report the data breach to the Belgian Data Protection Authority within 72 hours (Art. 33 GDPR). If your organisation falls under NIS2, the CCB (Centre for Cybersecurity Belgium) asks for a first notification within 24 hours for a significant incident.
  • Bring in a specialised company for the forensic investigation. Vidimus does not detect breaches.
03 / LIMITS

What it does not prove.

  • Anything about data that was not anchored before the incident. A snapshot from today proves what your data looks like today, not what it looked like yesterday.
  • What changed between your last snapshot and the incident. The more often you record, the smaller that window. Automatic every night is in development.
  • What was read or stolen. A fingerprint shows whether something changed, not who looked at it.
  • Who changed something, and whether the data was accurate when you recorded it.
  • Protection. Vidimus does not prevent breaches, does not detect them and does not replace a patch, a backup or a security company.
04 / SPECIFICATIONS

Specifications.

database
fingerprint per row, computed on your side · to Vidimus: fingerprints, table and column names, counts · with row key no key values
folder
fingerprint per file · to Vidimus: file names and fingerprints
compare
folder: per file unchanged, changed, moved or missing · database: in development
every night
in development
anchored
within five minutes · RFC 3161 per group · ledger · OpenTimestamps → Bitcoin
retention
ten years per logbook by default, adjustable
counts as
one record per snapshot or folder
price
first 100 records a month free · one snapshot a day fits in easily
05 / QUESTIONS

Frequently asked questions.

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.

Is the server's own history not enough?

It is valuable, but it sits on the same server as the data. Whoever got into that server could also adjust the history. A snapshot anchored outside the server does not depend on that server.

Can it also cover data from before the incident?

Only if that data was already anchored at the time. That is why it is best to start before anything happens: one snapshot a day costs nothing within the first 100 records a month.

Does Vidimus say which rows changed?

For a folder, yes: per file unchanged, changed, moved or missing. For a database, the comparison per row is in development. Vidimus does not say who changed something, and not what the right value was.

How we start: your first logbook today, the first 100 records free.

You create your account in two minutes. No payment details needed. A director identifies your company once with the Belgian eID; then you create your first logbook in a few minutes. Would you rather talk first? Book 15 minutes with the founder.