A family business runs three delicatessens in Lille. Its refrigeration supplier monitors the cold rooms over the internet, its tills take card payments, and its loyalty scheme holds 4,000 customer email addresses. Nobody in the business thinks of the cold rooms as computers.

The October attacks on shop refrigeration

Reuters reported on 20 November 2026 that a UK cybersecurity operation had fixed a flaw in the operating systems of commercial fridges and freezers. The October hack in France forced stores to throw away millions of euros' worth of food.

On 4 November ENISA, the European Commission, Europol's cybercrime centre, the EU CSIRTs Network and EU-CyCLONe issued a joint statement on incidents in refrigeration systems across the EU since 11 October. It told organisations to "take immediate action to mitigate exposure in the affected systems" and to follow their national CSIRT's advisories. It reminded them of the reporting duties under NIS2 and the Cyber Resilience Act.

The Commission itself was hit this autumn. Its spokesperson confirmed that an attack first detected on 22 October was carried out with AI tools; several applications were taken down for a time and most are restored, the Associated Press reported on 19 November.

The maker's duties and the shop's duties

The maker of a connected product carries the Cyber Resilience Act. Since 11 September 2026 a manufacturer that learns of an actively exploited vulnerability must send an early warning within 24 hours, a notification within 72 hours and a final report no later than 14 days after a fix is available (Article 14(2) of Regulation (EU) 2024/2847). A severe incident takes the same two first steps, then a final report within one month of the notification (Article 14(4)).

The shop carries its own duties. Personal data in its systems needs technical and organisational measures appropriate to the risk (GDPR Article 32(1)). A personal data breach goes to the supervisory authority without undue delay and, where feasible, within 72 hours of the business becoming aware of it, unless the breach is unlikely to result in a risk to people (Article 33(1)). A cold room outage that touches no personal data is not a personal data breach. A loyalty list read by a stranger is.

A business that is an essential or important entity under NIS2 owes an early warning within 24 hours of becoming aware of a significant incident, a notification within 72 hours and a final report within one month of that notification (Article 23(4) of Directive (EU) 2022/2555). Whether a business is one depends on its sector, its size and the national law that transposes the directive.

In the United Kingdom the same 72 hour rule sits in UK GDPR Article 33, which since 30 September 2026 names the Information Commission as the body that receives the report. The Cyber Security and Resilience (Network and Information Systems) Bill would add a 24 hour initial report and a fuller report after 72 hours for regulated organisations, and would bring medium and large managed service providers and data centres into scope. The Commons was listed to consider the Lords amendments on 24 November 2026, and the Bill had not received Royal Assent when this article was written.

337 incidents in a year, and fewer continuity plans

The National Cyber Security Centre handled 337 incidents that needed its support between 1 September 2025 and 31 August 2026, 80 of them nationally significant, according to its Annual Review published on 3 November. Its State of the Cyber Nation report, published the same day, judged AI-powered malware highly likely to be used in a ransomware attack on Britain's critical national infrastructure by 2028.

Preparation is falling behind. The government's Cyber Security Breaches Survey 2025/2026 found that 44 per cent of small businesses, those with 10 to 49 employees, had business continuity plans that address cyber security, down from 53 per cent a year earlier. Cyber incidents reported to the Financial Conduct Authority reached 38 in October 2026, the second-highest month in five years, Reuters reported on 19 November.

The file the delicatessens keep

The law asks a small shop for measures appropriate to the risk (GDPR Article 32(1)) and a record of every personal data breach, its effects and the action taken (Article 33(5)). For the Lille business, a practical file holds a list of every device a supplier reaches over the internet, the supplier's contact for security notices, the date each device was last updated, the name of the person who decides whether an incident is a personal data breach, and the 72 hour clock written down before anyone needs it.

NIS2 entities carry a longer list, set out in Article 21(2): risk analysis, incident handling, business continuity and backup management, supply chain security, cyber hygiene and training, access control and asset management, and multi-factor authentication, among others.

UK businesses starting from nothing have help this winter. The government's Cyber Essentials First Step Fund, announced on 3 November 2026 with £2.4 million of funding, gives eligible micro, small and medium-sized UK businesses that have not been certified in the last four years a 75 per cent discount on a new Cyber Essentials certification. It runs until March 2027 or until the funding runs out.

Toolkits for these laws and for Cyber Essentials

ComplianceSME publishes agent toolkits for the GDPR (A-001), NIS2 (A-003), the Cyber Resilience Act (A-006), the Data (Use and Access) Act 2025 (A-011) and Cyber Essentials (A-021), each built from the text it covers. Each toolkit interviews the person who holds the duty against the law as written and records where the business stands. When a regulator, an insurer or a customer asks after an incident, the answer already sits in the business's own dedicated Claude account. The toolkits run through the ComplianceSME connector in Claude.

The free assessment shows which of these reach a business of a given size and sector.

ComplianceSME research articles are available for republication in full, free of charge, with attribution. Requests to toolkit@compliancesme.com.

Every claim and its source