A secure application architecture not only prevents vulnerabilities in the initial release but also reduces the frequency of security issues being introduced into subsequent release candidates. Early OWASP Top 10 lists included buffer overflows as one of the most common vulnerabilities, but with the rise of type safe languages those vulnerabilities became less common. Other security issues like Cross Site Request Forgery are less common in microservice architectures and have fallen off the top 10 list as well which begs the question: By choosing certain languages, frameworks, and application runtimes can an app be designed from the beginning to have fewer recurring vulnerabilities?
This session explores secure application design to reduce common vulnerabilities in the context of a Docker/Kubernetes based application.
- How spending more time on secure design reduces likelihood of recurring vulnerabilities
- Importance of choosing technology stack for a secure by default mitigation strategy
- Role of API Gateway and WAF in quickly resolving vulnerabilities
- How Kubernetes/Docker provides OOTB security controls for preventing DoS and Data Exfil
Technical Level: High