Speaker

What does it really mean to create software that is safe to use in today's world? In this panel discussion, our experts will talk about different security issues that developers face today. They will share their thoughts on these issues, which come from their experience in architecture, data platforms, AI systems, and developer culture.

Maybe you want to learn more about reactive, incident-driven security and move towards a more proactive Secure by Design mindset. When should you start thinking about security when creating software? And how can teams balance speed, innovation, and resilience without slowing delivery?

Have you ever thought about how real-time data streaming is becoming really important in lots of systems? The panel can look at the special security problems of platforms like Apache Kafka. This includes ways to encrypt information, how to control who can access it, how to manage keys, how to monitor it, and what we have learned from data exposure incidents that have actually happened.

As AI and large language models become more common in apps, new risks like prompt injection might also be talked about. What are the practical results of these attacks? How can developers deal with increasing threats while still coming up with new ideas using AI?

As well as technical controls, the panel could also look at the human side of security. What can organisations do to make developers more aware of security issues? Could activities that involve playing games, like capture-the-flag exercises, help change the way people think about security from "security as compliance" to "security as responsibility"?

Get ready for a lively discussion where our speakers share their experiences and the audience can ask questions. If you're designing systems, working with streaming data, integrating AI or strengthening engineering culture, this session is for you.

Most systems aren’t intentionally designed to be insecure… They’re designed to ship.

When time-to-market sets the pace, systems tend to evolve by reacting to incidents: something breaks, we fix it, and move on. Over time, this becomes incident-driven design when systems aren’t shaped early to avoid facing the consequences of pre-installed weaknesses.

This talk focuses on what “Secure by Design” means before code is written. We’ll look at how requirements, planning, and design phases of the SDLC define what can go wrong later, and how small changes at this stage help build security into the design without slowing teams down.

By the end of the talk, you’ll leave with practical advice on how to integrate proactive security into system design.