Compliance

This is the Compliance demo. Every visitor shares this company, and it resets every night.

What you change here, everyone sees until the next reset. Email, payments, and the AI models are switched off.

Start your own trial
  • EU GDPR (2016)
  • ISO 27001:2022
  • NIS2
  • NIS2 Netherlands (Cbw, 2026)

Nothing found that matches the search criteria.

Start your own trial
SV
Sam de Vries
sam.devries@tidewell-it.example

Edit INC-006

Cancel
Description
Loading...

Summary

An update of the monitoring agent was pushed to customer workstations in the early morning. Within the hour the first customers called in: workstations restarted again and again before anyone could sign in.

Impact

Availability only. About one hundred and twenty workstations at nine customers were caught in a reboot loop, and the staff concerned could not work until their machine was fixed. No data was lost or exposed.

Response

The service desk linked the calls to the update within twenty minutes. The engineers stopped the rollout, withdrew the update from the deployment console, and published a fix for machines already affected. By the end of the day the previous version was back on every workstation, and the last stubborn machines were repaired by hand on site.

Notifications

Every affected customer got a call from their account owner and a written follow-up. A status message was shown on the service desk page during the incident.

Root cause

The new agent version conflicted with a disk encryption driver used on one model of workstation. The update went to all customers at once, without a trial group.

Lessons learned

Updates of the agent now go out in waves, starting with our own workstations and one friendly customer. A wave only continues when a day has passed without new tickets.

    Comments on this Incident (0)

    Add comment

    Loading...

      Are you sure?

      This action cannot be reverted.

      Leave this page?

      Your changes on this form are not saved. If you leave, they are lost.