Secure Code, Safe Future: Mastering Security in Critical Software Development
summary
C and C++ code in critical systems still produces classic, exploitable bugs — examples include Heartbleed (66% of sites affected, 500,000 unpatched months later), Cloudbleed (≈3,500 customers, ~4.8M credentials), and remote vehicle RCEs — so the talk shows concrete fixes: adopt Conan package manager to standardize dependencies, publish SBOM (SPDX/CycloneDX) for continuous SCA, apply MISRA rules and static analysis, use IDE Snyk plugins and AI-assisted fixes, and follow concrete demos that find and patch buffer overflows, memory leaks and unsafe API usage.
AI-written summary · about
chapters (8)
- 0:00Introduction to C/C++ security
- 2:35Challenges in legacy languages
- 4:34Common vulnerabilities and fixes
- 9:15Real-world security impact
- 12:16Standards and best practices
- 17:22Package management with Conan
- 20:21Resources and final thoughts
- 21:39Q&A and concluding remarks
related talks
01h 01mSoftware Security
01h 24mCode Red: Navigating the Minefield of Security Programming Blunders
14mEmbedded C and C++: A Security Perspective
01h 03m“Secure Coding Best Practices: Your First Line Is The Last Line Of Defense (2 of 2)”
45mBuilding Secure Software: Practical Strategies for Developers
01h 26mEmbracing an Adversarial Mindset for C++ Security
01h 06mSecurity Beyond Memory Safety - Using Modern C++ to Avoid Vulnerabilities by Design
48mSecure C++ Programming