How to Get Involved with CRA Standardization
summary
The Cyber Resiliency Act is an EU product regulation covering software and hardware (not services) and it spawns about 35 standards—three horizontal and 30+ verticals—each product-focused and risk-based. Vertical drafts define core functionality, map use cases to risk levels (example net L0-L3), and attach concrete requirements such as static source code analysis for memory errors unless isolated (L0). Harmonized standards give a legal presumption of conformity. Drafts are on ETSI Labs, public comment rounds open soon, and small grants via CyberStand and ESO delegate routes fund technical contributors.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker background
- 1:47What is the Cyber Resiliency Act
- 3:30CRA impact on open source projects
- 6:03Standardization process explained
- 8:50Vertical standards structure
- 11:37How to get involved in standardization
- 13:00Q&A session
related talks
42mMaking EU CRA (Cyber Resilience Act) Simplified and Non-scary for OSS Contributors
33mImplementing the EU Cyber Resilience Act (CRA)
34mHow Community Collaboration is Fixing the Future of Tech Regulation
01h 09mIntroduction to CRA Attestations and Workshop Read-outs
42mPanel Discussion: The Impact of the CRA on the Open Source Ecosystem
46mLinux Foundation Initiatives Supporting the Implementation of the EU Cyber Resilience Act
42mMaking EU CRA (Cyber Resilience Act) simplified and non-scary for OSS contributors
15mKeynote: Cutting Through the Fog: Clarifying CRA Compliance in Cloud Native