CRA & PLD Liability rules and Software Freedom
summary
European rules create a mandatory C-label on software tied to the Cyber Resilience Act, Product Liability Directive and a paused AI liability file, after about three years of debate. Individual developers get a clear individual-developer exemption while firms that significantly financially benefit must act as manufacturers and obtain labels; foundations and communities can register as stewards to assist. Market surveillance authorities enforce compliance and implementation details, including what counts as a substantial modification, are set to be defined over the next two years.
AI-written summary · about
chapters (6)
- 0:00Introduction to liability rules
- 1:50Cyber Resilience Act overview
- 3:14Open source and commercial activity debate
- 7:08Manufacturers vs stewards roles
- 9:36Implementation and enforcement plans
- 13:33Q&A session
related talks
23mDigital Products in Europe in the Face of the Cyber Resilience Act (CRA)
39mAll your code belongs to Policy Makers, Politicians and the Law
25mSecure or Sorry: Your software is now a European Product
39mFrom Policy Enthusiast to Legislators' Contact Point
33mImplementing the EU Cyber Resilience Act (CRA)
15mKeynote: Cutting Through the Fog: Clarifying CRA Compliance in Cloud Native
45mWhy EU Policy Making matters to everyone in the Open Source Ecosystem
32mThe EU Cybersecurity Resilience Act (CRA) - Boring, Scary or Exciting?