 All right. So I'm here with Sid this afternoon to talk about the financial services regulatory compliance issue. I wanted to hear how Sid is talking about it with customers and prospects at events and we're recording it so that we can use it with sales and for sales enablement and potentially with customers as well. Yep. This is the page. I made the first start of this and then you helped to make it better. It's great that it's better because it really resonates. A lot of customers ask like, hey, kid lab, I know you're very focused on developers are you also we're in the compliant industry. So can we also use it? And the answer is yes. And a lot of people do, including most of the regulators are using get lab to stay compliant. And we understand exactly what kind of regulations you're talking about. These are the ones that are relevant to you. And probably one of the biggest things that companies do is segregation of these. This means that no single person should be able to abuse the system, like wire money to their own account or have some really malicious code out in production. So get lab helps with that with things like protected branches, merge request approvals and protect permission, which means that even the people in the team cannot undo the branch protection on the admin scans. And then two person access controls will be a future feature that could really help them as well. They also love the security that we provide. I think that the how get lab helps isn't mapping one to one to some of these rules, role based access controls and revocation of accounts. We have that, but it's not this feature. So I think we should do a bit better here of listening what we do. Some of this is already here under auditing. But they are very happy to hear that we have many of the security technologies they're looking at. Sometimes they already have vendors for this for static application security testing and dynamic. Many times those vendors give them a solution, but it's super hard to integrate into their pipeline. So that's where get lab comes in. Get lab makes the adoption by developers much, much easier because it's a part of get lab. And we took special care so that we don't break anybody's work stream. For example, many vendors, when there's a vulnerable dependency, they just break the build and prevent you from releasing to production. It sounds like a good thing, but it's actually a bad thing. For example, you can have dependency in production. It might become vulnerable just because of vulnerability is discovered. So now your production contains the vulnerability. Your new code contains the vulnerability. Deploying it won't make anything worse. And there might be like a big outage through some work you introduced. And now you can't solve that, even though you're not making any security thing worse. So that's not the way to do it. The way to do it is to start early. So in get lab, as soon as you push code, we start scanning that code and we give you visibility. A month from now, in November 22nd, we'll release a security dashboard that gets CSO and other people visibility and what's out there. And you can agree on a security budget with the teams that work in the company. They have to respond quickly to things that become vulnerable. If they're not showing that they can do that, you could, for example, restrict them and say, hey, from now on, everything you ship has to fix the security issue until you're back to a normal cadence. The auditing, really important that no information gets lost. We were pretty good there. Change management, automated deploys, et cetera. The license management to make sure you don't do any code that's not compliant. So that's all resonating. I think what we should talk about as well is auto remediation. Auto remediation is something we'll launch next year and it's an integrated cycle. If you work at a company that doesn't have auto remediation, when there's a dependency that is widely used, for example, take Heartbleed last year, vulnerability is detected, now you got to fix all the applications that use it. So you come in on Monday morning and then suddenly you have 100 applications you should fix. With auto remediation, GitLab fixes all those applications and that we can do because we know what's vulnerable. The source code isn't GitLab. Fix that, deploy it, and monitor whether the fix is causing any problems and if needed, refer to it and create an issue. Results, you come in in the morning, you have only one issue instead of 100, only the application where there was a problem with the service level objectives after the fix. Another thing we should probably look into is requirements management. It's really important that you can link anything you've changed to something you wanted to achieve and of everything you wanted to achieve to be compliant, you're sure that that is tested. I think it's a big benefit that we do monitoring integrated with GitLab. So you're not deploying into a black hole that helps with the meantime to resolution that's becoming increasingly more important. It's not that you're never going to have any problems, but that if you have a problem you can respond soon and the regulators are catching up to that. GitLab's also coming out with incident management next year that should be good, that will help you reduce your meantime to resolution and keep everyone on the same page and communicate effectively. So those are some of the things that I think are helpful. Okay, thank you Sid. I appreciate you sharing your pitch basically. Do you get a lot of questions around how it might differ for a financial services firm versus healthcare or anything like that? Yeah, I think we should have the same thing we do here. We should have something for healthcare. I think there's a lot in common, there's a lot we can reduce, but I think people want to know that hey, I want to see tax from HIPAA, how it relates to me and I think our current HIPAA tax is not good enough. GitLab HIPAA, it's better than it was a while ago. No, I understand it needs some more, but it needs some work. Okay, well should we explain to anybody watching the video that it's almost Halloween? It's almost Halloween and it's a Friday afternoon. Okay, well thank you Sid, appreciate your time and as always if people have questions around security they can always reach out to me, Cindy Blake. Thanks for letting me do my pitch and thanks for improving it so much. That's great, thank you. Have a great afternoon. You too. Bye.