On 20 August, the Swedish government submitted a legislative proposal for a new Product Liability Act implementing EU Directive 2024/2853. The act extends the product definition to include standalone software and digital manufacturing files. Damage from lost or corrupted data becomes compensable. Open source developed outside commercial activity is exempt. The act is proposed to enter into force on 9 December 2026.
Novudom Weekly – Week 35, 2026
This week shows that responsibility for digital risk is being written into more laws than the Cybersecurity Act alone. Product liability will soon cover standalone software, the EU e-evidence regulation places new demands on cloud and hosting providers, and the ECB gives banks a clear deadline. Meanwhile, the attacks on Norway and Boston Scientific remind us that operational resilience is not a theoretical question.
Product Liability Act extends to standalone software
Organisations that develop, sell, or provide software will face strict liability just like physical product manufacturers. Map out now which of your digital products and services are covered and ensure your product safety processes include software.
ECB demands action plan against AI-driven cyber threats by 31 October
ECB Banking Supervision sent a letter on 7 July to all significant institutions requiring a concrete action plan against AI-enhanced cyber threats. The plan must identify measures, allocate resources, assign responsibilities, and set timelines. The ECB emphasises that AI does not create new risk categories but amplifies the speed and scale of known threats. DORA remains the binding framework.
Banks and financial institutions under ECB supervision have 63 days. The plan should build on existing cyber risk strategy and be delivered to the respective Joint Supervisory Team. Short-term priorities are the attack surface of internet-exposed assets, patch management, and AI-assisted detection. Long-term requirements include zero trust, legacy technology phase-out, and tested crisis plans.
Massive DDoS knocked out Norway’s national digital services for three days
On 24 August, the Norwegian Digitalisation Agency’s (Digdir) infrastructure was hit by the largest DDoS attack in its history. ID-porten, used by 4.5 million Norwegians to access healthcare, pharmacies, and government services, went down. Digdir described the attack as two to three times larger than previous ones. A pro-Russian hacker group claimed responsibility. It was the third time since June that Digdir’s services were attacked.
Shared digital infrastructure is efficient but creates a single point that can knock out entire societal functions. Review your own exposure to shared platforms and test your contingency plan for the scenario where a shared service becomes unavailable for several days.
Boston Scientific confirms cyberattack halting global medical device supply chain
On 25 August, medical device company Boston Scientific identified a cyberattack that disabled operational systems and business applications globally. The company was unable to process or deliver customer orders. Employees at the Cork, Ireland manufacturing facility were sent home. The share price fell six per cent. Analysts estimate it could take up to three weeks before normal operations are restored. The company reported the incident to the SEC via an 8-K filing.
Medical device supply chains are critical infrastructure in practice. Healthcare organisations should verify backup supplies and contractual terms with critical product suppliers now. Ask your key suppliers what recovery time they plan for.
EU e-evidence regulation in force since 18 August
Regulation (EU) 2023/1543 on electronic evidence is now in force. Judicial authorities in one EU country can request electronic evidence directly from service providers in other EU countries, without going through the country where the provider is established. A European production order must be answered within ten days. In urgent cases, a response is required within eight hours. Cloud, hosting, and communication providers must have designated a permanent contact point within the EU. Fines of up to two per cent of global annual turnover can be imposed for late or incomplete handling.
Organisations providing cloud services, hosting, or communication platforms within the EU must have a designated contact point and a process for handling production orders. Verify that you can identify and produce requested data within eight hours if urgency is invoked.
Three Copilot vulnerabilities turn AI assistant into exfiltration channel
Varonis Threat Labs has reported three separate vulnerabilities in Microsoft 365 Copilot during 2026. Reprompt bypassed safeguards by asking the same question twice. SearchLeak turned Copilot Enterprise into a covert exfiltration channel with a single click. CoSnitch, the latest, exploited the AI assistant’s own reasoning process. Microsoft has patched all three. Varonis calls the method meta-hacking, where the attacker manipulates the AI’s decision logic rather than attacking the code.
AI assistants have access to the same data as the user and can be manipulated to collect and forward it. Review which AI tools have access to sensitive data in your environment and apply the principle of least privilege to AI connections as well. Governing what the AI is allowed to do with the data it sees is as important as traditional access management.
CERT-SE warns of ChainDrop, self-replicating npm worm
CERT-SE warned on 5 August about ChainDrop, a self-replicating worm in the npm ecosystem. Within four hours it infected 452 packages with a combined approximately two billion downloads per month. The worm stole secrets and was controlled via the Ethereum blockchain, making takedown difficult. Microsoft Security Blog confirmed the analysis’s technical conclusions.
The software supply chain remains one of the most undervalued risk surfaces. Inventory which open source packages your development organisation uses and ensure dependency management has automated controls that react to compromised packages. Patching alone is not enough; you need to know what is in your dependency tree.
Weekly reflection
Three of this week’s seven stories are about liability being written into law or supervisory requirements, not about technology. Product liability for software, an obligation to produce data within eight hours, and the ECB’s 31 October deadline all share the same common denominator. They assume the organisation already has control over its digital environment. That control is not an IT question. It depends on whether management has a current picture of the systems, services, and dependencies the business actually rests on.