 Good morning. We are living in interesting times. Think about that. Just 15, even 10 years ago, we would have imagined that a large part of the world software would be running in containers. We would be all using sophisticated CICD pipelines that our software would be organized in microservices and scheduled by software like Kubernetes or other orchestrators, that deploying our software in the cloud would be the rule and not the exception. So, definitely interesting times, but we are at a security conference and from the security point of view, if you think about that, the challenges that we are required to deal with to solve are largely the same. Find and fix vulnerabilities in our software, manage configuration and permissions. This is particularly critical when our software is deployed in the cloud and essentially everybody has remote access to our infrastructures. Meet compliance, which is a moving target, every country, every continent has constantly changing rules from this point of view. And of course, detect and respond to threads. So, when we look at the security landscape from the perspective of cloud native, we can see two trends. The first one is towards shift left, right? And this is driven by the increased usage of CICD security, by the fact that we are centralizing our artifact, our software, the dependencies in repositories where we can then validate and check for vulnerabilities better. The second trend is a trend toward the right, toward runtime security. And this one is driven by the increasing complexity, by the orchestration, by the fact that, you know, microservice-based infrastructures that are running on Kubernetes are maybe easier to operate, but it's hard to actually figure out what's happening at runtime. And when we think about these two trends, the one toward the left and the one toward the right, typically in the context of cloud native security, we tend to think about the one toward the left first, right? It's natural, it fits very well the model. It's also easier if you want. I shouldn't say easier in the context of security, but you know what I mean. I'm here to argue a little bit for the shift to the right and the fact that it's equally important. In particular, you know, runtime security is key to detect attacks, block zero day events, prevent drift, and many other things. I like this quote from the Cloud Security podcast. Detection and response is all about solving the security problems that the rest of the security organization has been unable to solve. You can have fantastic supply chain security. You can have great vulnerability management. But in the end, the bugs stop where your applications are running in your production environment. So without great visibility, without granular ability to see what's happening, you have a gap. You have a big gap. Fortunately, the Cloud Native Computing Foundation is a tool that can help you with this. It's name is Falco. I'm one of the Falco contributors. And I like to describe Falco as the security camera for your Cloud Native infrastructure. Falco is traditionally based on EBPF instrumentation and can see what every single process does in each of your containers and hosts. But in time, the community has extended it to support, for example, cloud logs. So you're able to tell when one of your users logs in your AWS environment without multi-effect authentication. Or we embedded it in GitHub, so you're able to tell when somebody commits in one of your repositories a password or a secret or something like that. In general, Falco is a great community that can help you get started and also solve advanced problems that you might have with the tool. As I was saying before, typically shift left is what we worry first, and that's totally natural. But I argue that understanding what's happening at runtime is not only equally important, but highly complementary. And a key component of a truly well-designed security strategy for Cloud Native. So think about it today and go take a look at Falco. Thank you very much.