Two paths through the same incident.
Without the Doppelgänger
- 1
Friday, 6 pm
14 updates are waiting in the dashboard. One click, and the page builder does not get along with the new theme version. The website is a blank white page.
- 2
Weekend
The agency cannot be reached. Inquiries through the contact form go nowhere.
- 3
Monday
Emergency call-out, troubleshooting, rolling back individual plugins by hand.
With the Doppelgänger
- 1
On the copy
The updates run on the exact copy first. The error shows up there, and the live website is not touched.
- 2
When everything works
Nothing is published until everything works.
Extra cost: none.
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 listens in
For weeks, card details were skimmed at checkout. It was the bank that reported it.
The full disk
For two days the store took no orders. The disk was full, and nobody noticed.
The host switches PHP versions
The host raised the PHP version. For three days the home page looked empty.
A typical course of events, assembled from real incidents. Figures are example calculations based on the stated assumptions.