The compliance is well executed, and the CDR is evolving, with both progressing well. We use the CloudGuard CNAPP CloudGuard Security Posture Management capabilities. It's good for identifying misconfiguration. You have a a variety of rulesets that you can apply. So you can choose on depending on which on which industry standard that you are following. And you can really adapt it towards your environment, so you can mix and match what you need and really come to a more secure cloud environment. The effectiveness of its cloud security posture management for providing compliance rule sets and security best practices has been good. You can define KPIs in CNAPP. You can say: "this is the percentage that we want to work towards." And you can see your progress and say, "okay, at the beginning of the month, we are we are at 60%. And at the end of the year, we are there 80% compliance." You can do that. And you can really monitor it. The cloud security posture management identify the risks that are the most critical to our business. We can define certain key assets that are your crown jewels. And whenever something hits on these crown jewels, you get a very high score. So you can really fine tune towards protecting your risk based assets in the cloud. It also lowered the amount of time it takes when identifying of the most critical risks. If I would do that manually, it would take me ages. So when I have a fine tuned rule set that I that I apply upon all my workloads, I do have automatic identification of every resource. The time savings are indefinite. The CloudGuard CNAPP visibility into CloudGuard logs for simplifying incident investigation is very good. It can reach CloudGuard VPC flow logs and GoToKey events, and it can also look at Azure activity logs. So you can have multi cloud capability, CDR, and you have different rule sets that are quite good. So far, it's excellent. The CDR helps detect anomalous behavior and respond to threats before they become an issue. We had we had some third party products that were using that was not properly configured. CDR detected this when it was doing certain certain scans. We updated the role towards the policy that that CDR provided, and it really helped. The events went away.
