Keynote: Evolution of Open Source for Safe Usage in Critical Systems
summary
Open source components require machine-readable evidence for safety and security: prototypes generate SBOMs and provenance metadata from CI, map CVEs to safety profiles, and attach attestations that travel with binaries. Work shows concrete integrations with Linux Xen Yocto Zephyr, kernel provenance patches, Xen isolation knobs, Yocto buildinfo hooks and Zephyr safety manifests. Demos produce automated reports and a reproducible build chain that flags unsafe versions before deployment.
AI-written summary · about
related talks
05mKeynote: Evolution of Open Source for Safe Usage in Critical Systems
40mBOF: Open Source Projects in Safety Critical Applications
32mDeveloping Open Source for Safety and Security
08mKeynote: Security of the Open Source Supply Chain, a Call to Action
34mOpen Source in Safety Critical Applications: the Next Frontier
22mKeynote: Bringing Greater Trust and Security by Design to the Open Source Ecosys...
44mNavigating Open Source and Open Standards for Better Cybersecurity
16mKeynote: Back to Security Basics: Evaluating, Consuming, and Contributing Open Source Software
