Developers Own Code Security: Fix Flaws Before Exploitation
Code security for software engineers
Resources
Resources & Recommendations
Books
- "The Pragmatic Engineer Deep Dives" - This resource was mentioned for more details on security engineering, implying it contains in-depth information on the topic.
People Mentioned
- Johannes Doss (VP of Code Security at Sonar) - A security expert for 20 years who shared insights on code security, application security, and the impact of AI on the field.
Organizations & Institutions
- Sonar - Johannes Doss's current company, where he is VP of Code Security. Sonar scans billions of lines of code daily to identify security issues.
- MITRE - Runs the CVE (Common Vulnerability Enumeration) list, a database for documenting known vulnerabilities.
- Stack Overflow - Mentioned in the context of a survey where only 3% of developers trusted AI-generated code.
- OWASP (Open Worldwide Application Security Project) - Their "OWASP Top 10" is a standard awareness document for developers and web application security.
Websites & Online Resources
- CVE List (Common Vulnerability Enumeration) - A database for documenting known vulnerabilities, run by MITRE.
- GitHub - Mentioned as a common target for attackers who crawl public repositories to steal secrets.
- NPM (Node Package Manager) - Referenced in the context of packages being poisoned and dependency security issues in the Node.js ecosystem.
- Maven Central - Mentioned alongside NPM as a repository for packages that could be targeted by attackers using "slop squatting" techniques.
Other Resources
- Sasser Worm - A specific computer worm from 20 years ago that infected Johannes Doss's computer and sparked his interest in cybersecurity.