Security as the New Functional Requirement
recording made private on YouTubehttps://youtu.be/djaHoFf9vKg
summary
Argues that security must be a measurable nonfunctional requirement and gives concrete checks: no stacktraces to users, filter out MongoDB strings, and protect against OWASP Top Ten risks like SQL injection and components with known vulnerabilities (risk 9). Recommends tools and practices: firewalls/UTM like CISCO ASA, SIEM, static analysis, architecture-first design, a vulnerability-response policy with clear SLA and prioritization, coding standards, and maintaining agility so patches actually get applied.
AI-written summary · about
related talks
23mSecurity Doesn't Have To Be a Nightmare
43mSecurity By Design
34mMastering Security Requirements Engineering
38mPrioritizing Trust While Creating Applications
29mGraphQL Security Best Practices and Hardening
47mThe Only Reason Security Really Matters for DevOps
50mAdapting First Order Security Principles to Newer Architectural Trends
33mInterview with