Two paths through the same incident.
Without the Doppelgänger
- 1
Weeks 1 to 3
A break-in goes unnoticed, and every backup saves the back door along with everything else.
- 2
Discovery
Every available backup is already infected. Restoring means rebuilding.
With the Doppelgänger
- 1
Always
The code is under version control, and every version stays retrievable.
- 2
First night
The nightly file comparison reports the break-in, not three weeks later.
- 3
Every night
An independent backup of your live website, database and files, encrypted and in Germany, going back up to six months, in addition to your host’s backup.
An update alone is not enough: for almost half of all WordPress vulnerabilities there is no patch yet when they are published. That is why nightly monitoring is part of it.
What the incident costs.
More case studies
The big update without a rehearsal
The Shopware major update ran on Sunday. On Monday the store accepted no payments.
A week of casino ads
For a week the website redirected its visitors to casino sites. It was a customer who noticed.
Friday evening, “Update all”
One click on “Update all”, and after that the website showed nothing but “There has been a critical error.”
A typical course of events, assembled from real incidents. Figures are example calculations based on the stated assumptions.