Pragmatic Approaches To Building Secure Software
summary
Panelists lay out concrete tradeoffs and controls: competing priorities and uneven security expertise leave thousands of scanner alerts and dependency issues on backlogs; teams adopt a restrictive Content Security Policy to make XSS impractical, run SAST and software composition analysis for third‑party libraries, and keep an inventory to track patches. Prioritize by likelihood and impact in a risk register, add focused manual exploratory tests for business logic, and treat responsibility as shared while watching API attacks rise toward ~30% and phishing/ransomware automation increase.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:19Key challenges in secure software
- 12:16Security controls early
- 17:56Responsibility for security
- 25:02Regulation in software security
- 30:00Security testing approaches
- 36:03Security scanning tools
- 41:45Prioritizing risks and vulnerabilities
- 44:38Emerging threats and attacks
related talks
27mSecurity: The Thing That Everyone...
51mSecurity & Privacy in Digital First Businesses (Panel)
44mApplication Security: Everything we know is wrong
38mPrioritizing Trust While Creating Applications
40mDesign Approaches for Security Automation
44mSecurity Practices Useful in Agile Development
01h 04mShifting Security Everywhere
45mShifting from Syntax to Secure Software Development Processes