Date & time

17:00

AI is changing the pace of development in ways that are measurable and real, but speed cuts both ways. Review times are increasing by up to 90% because AI is generating code faster than teams can review it. Fortune 50 companies saw 4x velocity gains alongside 10x more vulnerabilities. And mean time-to-exploit has gone negative, with working exploits now arriving before patches exist.

Every new AI tool your engineers adopt immediately touches your dependencies, your build system, and your pipeline. The surface area grows every sprint. And agentic workflows that pull from public registries don’t distinguish between clean and compromised packages. That’s your platform team’s job to solve, not your developers’.

Every organization has to change its relationship with security matters, in order to remove friction from developers, without increasing risk.

This session brings together engineering leaders to discuss the operational habits that make AI-assisted development structurally safer, including how to:

• Standardize on a secure-by-default foundation, with everyone understanding what ‘secure’ means
• Apply a “built from verified source” standard across containers, libraries, and CI/CD actions, not just one layer
• Make compliance evidence a continuous byproduct of your build process, not a quarterly scramble