Cyber defence & recovery ยท Briefing

Your security dashboard raised an alert. Who got the call?

An alert can reach the right person and still go unhandled. The test of a handover is whether someone takes responsibility for the next action within the time the service needs.

Worked example, not a client case study. Consider a parts distributor that relies on its dispatch system for Saturday collections. The technology lead and the support provider agree in writing to follow a harmless, vendor-supported test alert from one authorised device. If the primary responder does not acknowledge it within ten minutes of delivery, the backup must be notified and take ownership within five more minutes.

Follow the alert past the dashboard

At 08:05 the dashboard records the alert. At 08:06 the service desk opens a ticket and the notification service records delivery to the duty analyst. The analyst has agreed to withhold acknowledgement for the exercise. At 08:22 the ticket is still assigned to the primary responder. The backup, who is on the supplier rota, confirms that no notification reached them.

The test shows detection, ticket creation, and delivery to the primary responder. It does not show human acknowledgement or working backup cover. A delivery receipt is evidence that a notification arrived, not that someone read it or took responsibility.

Decide what you can rely on

The service owner records a failed Saturday handover. The provider checks the routing against the current rota. Until a retest passes, the technology lead and provider agree a temporary manual escalation and confirm who will answer it. In the retest, the backup must receive the alert, acknowledge it, and name the next step. No device is isolated, and no live records are changed.

Start with one service and one shift. Ask who gets the first notification, who takes over if it goes unanswered, and which record would show that the handover happened. Repeat the check when the rota or provider changes.