Revolutionizing Automotive Software: DevSecOps, Functional Safety, and Open Source Sy...
summary
Claims that embedding Continuous Verification and Validation into a DevSecOps pipeline makes automotive software both certifiable and faster to deliver, demonstrated by mapping verification/validation activities onto lifecycle phases and using open source CI/CD tools (GitLab/GitHub Actions, Docker, Kubernetes, SonarQube, Aqua) to automate scans, dependency checks and audit artifacts. Notes the scale — about 80 million lines and software as 50% of vehicle cost by 2030 — and shows building per-ECU pipelines and a cloud digital replica for incremental certification and faster feedback.
AI-written summary · about
chapters (11)
- 0:00Automotive software revolution
- 2:29Software defined vehicles
- 7:23Safety and security challenges
- 10:35Verification and validation
- 15:28Architecture for safety and security
- 20:26DevSecOps and open source
- 25:25Open source security risks
- 27:54Certified ECU pipelines
- 30:47Agile verification validation
- 36:46Continuous verification workflow
- 39:11Q&A
related talks
40mSoftware Supply Chain for the SDV Future — Logistics, Cybersecurity and Compliance
11mBuilding the Software-Defined Vehicle
48mDesigning a Secure Software Development Lifecycle with DevOps
22mA Healthier Software Development Life Cycle with DevOps
19mSecuring the future of mobility: Automotive threat modeling
43mSecuring Software-Defined Vehicles: From Threat Awareness To Holistic Cybersecur...
30mThe 3 Ways of DevSecOps – Making Shift Happen
42mIndustrial DevOps, Applying DevOps to Cyber-Physical Safety-Critical Systems