Two paths through the same incident.
Without the Doppelgänger
- 1
Weeks before
The host announces by email that an old PHP version will be switched off. The email gets lost in the inbox.
- 2
Cut-off date
An old plugin stops working, and the website shows an error.
- 3
3 days later
A customer calls.
With the Doppelgänger
- 1
In advance
The Doppelgänger runs on the new PHP version ahead of time. Incompatible plugins show up there and are replaced before the host switches over.
- 2
Immediately
If the website goes down, uptime monitoring raises the alarm immediately.
I meet automated attacks with automated defense: updates go out quickly and regularly, but only after a test on an exact copy of the website.
What the incident costs.
More case studies
The checkout that is only broken sometimes
For three weeks, not a single purchase on invoice went through in the store for wholesale customers. The main store worked perfectly.
The agency was on the server
For a promotion, an outside agency changed files directly on the server. With the next update, the promotion was gone.
Nobody did it
After a new feature went in, the product search found nothing anymore. Nobody knew who had changed what.
A typical course of events, assembled from real incidents. Figures are example calculations based on the stated assumptions.