“Secure Coding Best Practices: Your First Line Is The Last Line Of Defense (2 of 2)”
summary
Static analyzers like CppCheck and Clang‑Tidy catch correctness issues but miss many security flaws; security scanners such as Coverity, Sonar, PVS Studio reduce risk but give false positives. Dynamic tools and fuzzers — OSS‑Fuzz, libFuzzer, AFL — find runtime and protocol bugs but require stable interfaces. Penetration tools like Metasploit, Nmap expose real attack paths. A demonstrated Dirty COW exploit uses an mmap+madvise race to alter /etc/passwd and achieves root, proving design and threat modeling (STRIDE, trust boundaries) are decisive.
AI-written summary · about
chapters (17)
- 0:00Introduction to hacking
- 1:01Planning and intention
- 2:20Static analysis tools
- 5:07Dynamic analysis tools
- 6:16Fuzz testing techniques
- 8:50Penetration testing
- 11:58Threat hunting fundamentals
- 13:14The cyber kill chain
- 18:56Project aurora case study
- 20:28Threat modeling process
- 23:41Analyzing trust boundaries
- 29:41Security best practices
- 34:59Logging and auditing
- 37:25Code review and legacy code
- 45:36Dirty cow vulnerability
- 52:23Final security takeaways
- 58:57Q&A and conclusion
related talks
23mSecure Code, Safe Future: Mastering Security in Critical Software Development
44mAn intro to improving the security of your code with free analysis tools
01h 26mEmbracing an Adversarial Mindset for C++ Security
29m“The Current State of (free) Static Analysis"
45mEradicating Vulnerability Classes by Shelving SAST and Embracing Secure Defaults and Invariants
22mWriting safe and secure code
45mFinding Vulnerabilities through Static Analysis and Scripting
17mTools & training for more secure software