Building Secure Software: Practical Strategies for Developers
summary
Attack surface is expanding with AI and low‑code tools and developers must harden pipelines now: 1.8M breaches traced to broken access control and 100% of tested apps had issues, exploit creation drops from ~7–14 days to under 2 days, and regulators force supply‑chain proofs—SBOMs verified from Dec 2027. Practical steps: generate and store SBOMs, add SLSA and CI/CD plus continuous monitoring, sandbox AI coding (dev containers or NixOS/Nix-based VMs), avoid homegrown access control, and prioritize logging, alerts and incident playbooks.
AI-written summary · about
chapters (16)
- 0:00Secure software development intro
- 2:23Panelist introductions
- 4:07Top security concerns
- 9:10Security in agile workflows
- 13:50AI tools security risks
- 18:06Speed vs security
- 20:38Q&A on SQL injection
- 23:28Cyber Resilient Act & supply chain
- 27:50AI agents in security
- 30:39Immediate developer steps
- 36:26Security mistakes to avoid
- 37:47Developer’s security role
- 39:09Understanding SBOMs
- 40:13Secure dev resources
- 43:21Trusting trust & long-term security
- 44:44Closing remarks
related talks
25mYour Software Supply Chain is Only as Secure as its Weakest Link- 25mYour Software Supply Chain is Only as Secure as its Weakest Link
46mApplication security from start to finish
41mManaging the Risk of Software Supply Chain Attacks
44mKeeping Your Software Supply Chain Healthy
49mPanel: From Code to Defense: Why Developers Are the New Security Leaders
46mAre Developers the New Front Line of Security?
23mSecure Code, Safe Future: Mastering Security in Critical Software Development