Writing safe and secure code
summary
Code used in roughly six billion instances focuses on reproducible practices: strict compiler warnings, fix-every-warning policy, heavy CI that runs about 50 builds per pull request and thousands of tests consuming ~25 CPU hours per commit, and fault-injection that simulates every malloc/open failure. Tooling includes Valgrind, clang sanitizers, clang-tidy, LGTM and OSS-Fuzz, fuzzing that initially found about four security bugs, plus code review, assertions, extensive unit/integration tests and rapid fixes for discovered issues.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:26How to write safe code
- 4:30Review
- 6:47Testing
- 10:13Build times
- 11:30Tools
- 13:30USSFast
- 14:50Policies
- 16:03Costs
- 16:38Fixing flaws
- 17:07Bad things will happen
- 17:58Conclusion
related talks
29mSecuring C code that seems to work just fine
50mSecure development with C++ - Lessons and techniques
59mHardening Your Code
01h 03m“Secure Coding Best Practices: Your First Line Is The Last Line Of Defense (2 of 2)”
01h 01mSoftware Security
23mSecure Code, Safe Future: Mastering Security in Critical Software Development
48mSecure C++ Programming
40mIs Your Code Secure?: Automatic Security Analysis Tools and Systems