Managing risk needs to scale as your product grows in popularity and complexity. In traditional software development, security was often treated as a last gating factor at best and post-incident concern at worst. You need to shift your security processes left—in other words, earlier in the development lifecycle. The cost of applying security practices too late can be catastrophic to a company, leading to the loss of customer trust and affecting the bottom line.
Join Jennifer Davis to gain an overview of security tools and practices to adopt, including the CIA triad and why security matters, motivations of attackers, core foundation practices, defense in depth, threat modeling, making choices in your architecture based on operational concern, testing code, coding standards, securing code reviews, handling incidents, and advanced practices such as bug bounty problems, capture the flag, and red team exercises.
Application Security Verification Standard Project
Minimum Viable Response Plan: jhand.co/CreateResponsePlan
CTF with Google
“Fundamentally, if somebody wants
to get in, they’re getting in…accept
that. What we tell clients is:
Number one, you’re in the fight,
whether you thought you were or
not. Number two, you almost
certainly are penetrated.”
Bit Community by Ashley McNamara is licensed under CC BY-NC-SA 4.0
Session page on conference website