 Right, so yeah, I'm Eric Carter and someone here in the middle, someone yell Baba Booey. That's something I always wanted to have happen. I'm going to talk a little bit about modernizing real world secure DevOps practices. What does this mean? Well, here's a picture of you all, right? You've got all these different job roles and suddenly in your life and your world, you're being asked to be security people, right? Maybe that wasn't what you woke up expecting to be, but we need to do that individuals in the companies that we work for and the different jobs that we have. So how do you move in that direction? Well, clearly, we're starting to see people who once identified as DevOps people now are being identified as DevSecOps people, practicing what I'm calling the art of secure DevOps that is integrating security with everything that we normally would have done as a DevOps person. And we have worked with as an example with Red Hat on a customer who has credit cards in the cloud. So Red Hat OpenShift on AWS, on Azure, on-prem, in Google and needed a way to protect that stuff. And all they cared about early on was just doing monitoring. So is it working? Is it healthy? But then they were asked to take care of everything else with that. And this is world pay. We have a great case study and we've done webinars with them. But think about that. Anytime you're dealing with somebody's financial information, there's this level of seriousness that all of us get into. And so pairing with Red Hat, with SysDig, we were able to solve their problems. How did we do that? And so this is going to speak to the concepts of becoming more aligned and modernizing your DevOps practices. One is to secure the build. How many people are scanning in your registries? Probably most of you have, yeah, how about in the CI CD pipeline? Sometimes we're plugging in there. Sometimes we're not. Shift left. We're tired of hearing about it, but it's like, do security early and often, right? So securing the build pipeline, detecting and responding to threats when I'm in production. And SysDig is known in part for Falco, which is an open source project. We don't own it. It's all part of the CNCF, but this is really a part of what it does is to try and sniff out who's doing what in my running containers, in my running environment. Monitoring, of course, you can't see what's going on if you're not monitoring it. And that's another important piece is to understand how are things going? Is it healthy? Is it not? And now, because so many of us are running these things in the public cloud, we also need to understand, am I set up correctly? Are my configurations on AWS such that I'm protected? Do I have buckets out there that are open to the public with all that credit card information in it? You want to be able to see that. So all of these become part of that modernization of your DevOps practices. And what do these all have in common? There's a level of visibility that you need. Visibility to see what's going on in your container, in your cloud, in your Kubernetes control plane, and so on, right? And so this is really who SysDig is. It's all about providing, yes, we're on the deep end of the pool, providing you deep visibility so that you can understand and be successful at implementing security across the different workflows. We have a couple of solutions, SysDig Cura, SysDig Monitor. A lot of it built on open source projects that you may already know and love. Falco, Prometheus, open source SysDig, and Promethia, Cloud Custodian as well, which is a new to the mix. Even Opa now, by the way. So that's what SysDig is at the end of the day. Red Hat, SysDig, and I just wanted to see if somebody would notice the squirrel, right? Confidently run containers could raise in cloud. Look, if you're ever worried, you have an oh shit moment and you really wanna make sure that you know what's going on in your environment. Between Red Hat and SysDig, I think we can be very helpful to you. So that's all I have. Thank you everyone for sticking around.