The French blood service, Établissement français du sang (EFS), has confirmed a cybersecurity incident involving a supplier that affected cold-room monitoring and control systems at three of its sites, with monitoring, intervention and preventive transfers helping to protect continuity. No blood-product loss or health impact was reported. EFS statement
The contained outcome makes this a useful example for businesses to consider, particularly where the equipment supporting daily operations sits across the responsibilities of IT, facilities and external suppliers. Each team may understand its own part of the environment, while practical questions about who receives an alarm, who can restrict a supplier’s access and who decides how operations should continue can remain less clear until an incident brings those responsibilities together.
For regulated businesses, including the finance and insurance organizations we work with, the connection is relevant even where refrigeration has no role in their operations. Cooling, power, building access and environmental monitoring can all support the facilities that business services depend on, and the ability to recover an application has limited value if the equipment or location needed to run it is unavailable.
The following are practical recommendations for reviewing those dependencies, rather than claims about the cause of the EFS incident or the specific controls it had in place.
Understanding who owns the response
A useful starting point is to take a critical business service and work through the physical equipment, monitoring systems and supplier relationships needed to keep it operating, then identify who is responsible when one of those dependencies becomes unreliable. This should include the people who can assess the equipment locally, the team that manages its connectivity and the person authorized to make a decision that may interrupt service.
The difficulty can arise when responsibility is described too broadly. An agreement that says a supplier maintains the equipment does not necessarily explain who responds when its remote service is unavailable, whether the customer can continue operating locally or how an incident will be escalated outside normal working hours. Those details need to be understood by the people expected to act, rather than left for them to work out while an alarm is active.
An inventory is useful when it records how the equipment supports the business and how it is operated, alongside the usual model, location and maintenance information. For a critical installation, that could mean knowing which external connections are required, what happens if they are lost, who can inspect the equipment and which procedures are available without access to the supplier’s systems.
Reviewing access and monitoring together
Supplier access is one area worth reviewing, without assuming it was the route involved in this incident. Organizations should understand which equipment an external party can reach, what work that access permits and how it can be suspended through an approved procedure if the supplier reports a security problem. Where remote access is necessary, it should be limited to the work required and supported by records that allow the customer to establish what happened.
The isolation procedure needs the same operational attention as the access itself, since disconnecting equipment without understanding its behavior could create another problem. Facilities staff, IT teams and the supplier should establish what safe local operation looks like, which functions would be lost and who has the authority to make that decision under the conditions described in the response plan.
Monitoring deserves a similarly practical review. An alarm has to reach somebody who can assess it and arrange an intervention, including when the usual monitoring platform or supplier connection is unavailable. Where the consequences justify it, organizations should consider an independent means of checking the physical condition being monitored, so that a reassuring dashboard is not the only information available to the response team.
Testing whether the business can continue
Continuity procedures become more useful when they describe actions that can actually be carried out with the people, equipment and capacity available. If a plan depends on moving an operation, transferring materials or switching to a backup installation, the organization needs to establish whether the receiving location is suitable, whether enough capacity is available and how long the change would take.
A joint exercise can expose these gaps without requiring a live disruption. IT, facilities, operations and the supplier can work through a scenario in which remote monitoring becomes unreliable or supplier access must be suspended, checking how an alert would be assessed, who would attend the site and what evidence would support a decision to continue operating. Any physical test should be planned around the equipment’s safety requirements and the business’s operating constraints.
The same exercise should cover the return to normal operation, including who confirms that the equipment is behaving correctly and what checks are required before supplier connectivity is restored. Recovering a connection is one step in that process, while confirming that the supported business service can operate safely and reliably may involve several teams.
For Ahead, the relevance is in bringing these dependencies into the same conversation as the technology they support. Businesses put considerable effort into protecting applications and data, and that work is strengthened when the physical environment, supplier arrangements and operating procedures are understood with the same care. A clear view of how those parts work together gives the people responding to an incident a better chance of making informed decisions while there is still time to contain its impact.