Will the CRA Break Open Source in IoT — or Make It Stronger?
summary
The CRA makes manufacturers liable for every piece of code and forces them to support products for their entire lifecycle, including finding fixing and sharing vulnerability patches upstream, which reshapes product design and supplier relationships. About 74% of the world codebase is open source and 94% of products include OSS so dependency visibility and supply chain mapping become mandatory work not optional. A neutral working group of 56 members is building best practices and engagement routes to translate due diligence into executable processes.
AI-written summary · about
chapters (7)
- 0:00CRA impact on open source and IoT
- 1:03Manufacturers' new responsibilities
- 3:55IoT cybersecurity challenges
- 5:59Transforming IoT with open source
- 9:10CRA compliance advantages
- 9:52Regulatory compliance relationships
- 12:23CRA readiness key takeaways
related talks
14mThe CRA: an Open Source Sustainability law?
42mPanel Discussion: The Impact of the CRA on the Open Source Ecosystem
42mCopyleft and the EU CRA
42mThe Impact of Copyleft on the EU CRA
54mThe CRA, Where Are We Six Months After Its Approval
27mBeyond Open Source Risks With the CRA and NIS2
42mMaking EU CRA (Cyber Resilience Act) simplified and non-scary for OSS contributors
34mHow Community Collaboration is Fixing the Future of Tech Regulation