The problem

Security engineers reviewing code, running scanners, triaging findings, and still drowning with the volume. That has been the reality of AppSec in most orgs for as long as I can remember. Automation was our answer to that problem back then.

Now the pace has shifted again. Developers are generating hundreds of lines of code in minutes and the traditional AppSec playbook of manual reviews, scheduled scans, and remediation workflows is going to hit its limits even for the best orgs out there. The tools and processes that security teams have spent years building are becoming less relevant because the underlying assumptions are changing.

What this session is not about

We will not be debating the merits of AI-generated code. AI written code is already mainstream and is everywhere. That is the starting point, not the discussion.

What we are here to figure out

This is about what security engineers are actually doing, or trying to do, to effectively secure environments where the SDLC looks very different from what it did two years ago. This is still an uncharted territory and the goal is to find out what is working for people, what is not, and what the new challenges ahead look like.

Who should attend

If you are a security engineer who has witnessed this shift or someone who is still figuring out how to respond, this session will be your opportunity to learn from your peers.

Why now

I am seeing this shift happen in real time and I would much rather get ahead of it than watch security become an afterthought yet again

Register here — April 11, Bangalore.

AppSec in the age of Agentic Software Development

{{ gettext('Draft') }}