A developer’s guide to making security reviews suck less
In many companies, security reviews suck. You’ve spent weeks or months grinding on a new feature and you’re finally ready to push to production, only to have a security review at the eleventh hour spark chaos. A security engineer raises a concern that might be valid or might be a total misunderstanding, but either way, it leads to urgent meetings, escalations, and complicated Go/No-Go decisions.
In this talk, we will dive into how to navigate these reviews without the drama. As an AppSec Director, I will help you understand exactly what security teams are looking for and why. I’ll show you anticipate their concerns and requirements so you aren’t surprised by scope creep right before code complete. We will explore how to effectively engage your security team, what specific information they need from you, and how to speak their language so you can accurately address concerns and get to the heart of their requirements.
By the end of this session, you will have a straightforward strategy to streamline your next security review and build a more collaborative relationship with your security partners. You will walk away with the tools to reduce the friction that leads to pre-launch panic, helping your team ship with significantly fewer headaches.