Transcript for "Embracing quantum-ready security: Preparing for tomorrow's encryption standards": Hello, all, and welcome to today's webinar. My my name is Vinay, and I will be helping support today's live session. Before we begin the session, a little bit of housekeeping. On the top right corner of your screen, you will see the live chat option that you can use to interact with your fellow attendees. We have also attached an ebook on modernizing security for AI and an upcoming webinar on securing connectivity in the docs section that is next to the live chat. On the extreme right, you will also find the q and a box. We encourage you to leave all your questions in that q and a box as we progress through this webinar. We'll make sure to address all your questions towards the end of this presentation. A quick reminder, this session is being recorded, and we will share the recording with you within forty eight hours. Now please join me in welcoming today's speaker, Volker Rath, field CISO at Cloudflare. Hi, Volker. Hello. Thank you very much. And hello, lovely people. Thank you very much for joining this, webinar. We. do really appreciate that you find the time. We know that subject like post quantum readiness, post quantum computers is a bit of a dry subject, but it is an important subject. And we want to help you with webinars like these to understand the problem. Let's talk about plain English about, this, quite complicated subject and demystify some of the things about quantum computing and quantum encryption, but first and foremost, give you a glimpse of how you can prepare and get ready for post quantum error. So post quantum is many people call it the new y two k event. Why? At the year 2000, and I used to be a consultant back then doing software quality assurance services for banks. And the banks were back then the only ones who really, prepared well for the, y two k events. Many other organizations didn't. And so, yet at November 1999, many organizations had, were becoming quite nervous and were relieved to see that everything was working the next day. We have a new y two k event, which is the post quantum era, and this is the time where, cryptographically relevant quantum computers will become available mainstream. Why is this relevant? Well, these computers will change the cryptography as we know it, because they are able to crack some of these things, which we will dive into a little bit later. So we don't know what the new year will be, if it will be 2030, 2028, 2040. All we know is that progress is happening fast, and the topic post quantum readiness is becoming a more and more important topic, especially for organizations who deal with sensitive data. But let's dive first into the problem. What are we talking about here? What is the problem? The Internet was not developed with security, trust, privacy protection performance in place. And, you know, we joined the CloudFlare webinar, and our slogan is we wanna help building a better Internet. We come to that later. But we didn't have that better Internet, for a long time, and so the Internet was not, built with these things in mind. So the industry had to bolt on security and privacy to establish trust, trusted communications. In order to build trust in the Internet, you need to have three components. The first one are digital signatures or certificates. They help you to tell somebody who you are so that the other party can trust you. The second one is a key exchange where you, agree on a certain key that you use later for encryption. So think about you wanna share a safe or a vault with a friend. First of all, you need to make sure that your friend is really your friend. After that, you agree to a key. Maybe you have two copies, and then you use the same key to, open the vault and close the vault. Let's look a little bit into how RSA encryption works and where the problem lies. So first of all, RSA is an encryption algorithm that is used for digital signatures and, encrypting data. It is pretty much a mathematical algorithm that creates two types of key, a public key and a private key, and we know this today as public key encryption. And I am unfortunately, the slides are breaking up here. I'm sorry for that. Let me let us dive a bit a bit deeper into this. So what RSA does, it takes two prime numbers and multiplies these two prime numbers. And after a little bit of additional math, it comes up with two key pairs. And you see here the key pair one is fifty five and three, which would be the public key, and the key pair two with fifty five and twenty seven. Using these two keys, RSL, RSA will use these keys to encrypt to, to encrypt data, using the public key and decrypt data using the private key. The problem here is that the math problem is very hard to solve for today's computers. They take hundreds, thousands, and sometimes even ten thousands of years depending on the key length. But for quantum computers, it will take potentially only a couple of minutes. We don't have these quantum computers yet, but we it is quite foreseeable that we will reach capabilities like that in the close future. So why is it vulnerable? So RSA and, other cryptography standard like ECDSA, which is an elliptic cryptography standard, are, standards used for data in transit. That means, we use them for HTTPS, for example, which is the majority of our Internet, and we use it for TLS 1.2. AES is an encryption another encryption standard, that uses a symmetric key. So use the same key for both direction. And the good news to to of today is that these keys and these encryption standards are safe, from, quantum computers. So our focus is, fully on data in transit. I think that's important to know when it comes to our, quantum ready strategy and what we what actions we have to take to become quantum ready. How does TLS work? There are many documents written about TLS and how it works, and they're quite technical. But I think if we kind of, have a little bit of an, conversation with a friend, it becomes quite clear, how it actually how this handshake works. So a person says, hey. I'm using TLS one zero two, and I'm using also RSA. Can we have a chat? And the other person says, yeah. I'm using I'm speaking the same language. We can have a chat. Okay. So I just downloaded your certificate, and everything looks fine. And, can we just talk? And so I know that you are really you. And the other side says, yes. I also checked your certificate, and I think we can trust each other now. And we're using the same language. And then both sides start to talk. Starting to talk in the Internet means, in a secure way, means that we're that we're agreeing on a key in this initial key, exchange, and we are communicating at an encrypted level both using the same key. What is the problem? So as we said before, these keys can be broken in the future, and there's an algorithm for those who like math and science. It's called the Shor's algorithm that is specifically designed to break this multiplication of two prime numbers, and quantum computers will be perfectly suited to, use Shor's algorithm to decrypt cryptography. Both modes, RSA and also Diffie Hellman results in a, in a shared secret. There's a difference between RSA and Diffie Hellman. RSA is not forward secret, and this is why it's used less in, encryption protocols. Forward secret means that if I crack the key in the future, can I decrypt communication of the past? So RSA is not forward secret. That means any, communication today that is encrypted with RSA, which is today considered safe, could be recorded. And in the future, when quantum computers become available, they can decipher this, conversation. So why is this for why is this important, and why is this, relevant for me? Because even if I can be attacked in the future in quantum computers already, the question is, do people really record all of my traffic today, wait another five or even ten years, to decrypt it? So while this is technically feasible, from a risk perspective, the likelihood seems quite low. Well, that may be the case, but think about you have, secret plans of critical infrastructure or you have patents of complex, goods like fighter jets, for example. This kind of data is valid and needs to be kept secret for a longer period of time, and they're absolutely, valid targets for, record now and decrypt later attacks. So why are we need to be, why sorry. Why do we need to upgrade now? First and foremost, upgrading infrastructure is hard. The RSA and the, ECDSA standard are used everywhere. And this will be it would be a huge undertaking to upgrade all components in the Internet and in your infrastructure. So we need to start now simply from an operational logistical perspective. NIST provided guidance, around the readiness, and NIST suggests that, these standards that we just discussed must be depreciated by 2030 and disallowed by 2035. After NIST, announced this statement, all of US government followed, the Australian government followed, and more and more regulators like the in the EU and also in Asia Pacific followed this type of guidance, and it's the commonly accepted timeline for post quantum readiness. So we talked about this harvest now, decrypt later, and we talked about sensitive data, that is valuable over a long period of times. That, is potentially happening now. The bad news is that we don't know if it happens because if a threat actor records data now or harvest data now to may be decrypted later, you would not see that. It is very hard to detect just a simple recording of communication, and therefore, it's very hard to, protect yourself against this kind of attacks today. But there's also the big unknown. There is a lot of money globally invested in quantum computers, and, progress is happening very fast. But what happens if one party or one nation state or even threat actors are the first ones to build a quantum computer that can be used to crack all of these encryption standards. And this party will not tell the world that they are have access to this kind of computer. So this would give that particular party an unparalleled advantage to launch cyberattacks globally. So while we will roughly know when quantum computers will become ready in the future because this is quite openly, discussed, we will not know if a rogue actor in the market will have it earlier and, starting to explore these attacks. The big question is now, how do I become post quantum ready? In order to become post quantum ready, I need to upgrade my encryption algorithms and therefore also the keys. The new mechanism or the new, standard is called MLKEM, and we need to upgrade all of our infrastructure like, network appliances and and proxies, for example. There was the question comes up, up quite often. Do I need to have quantum computers, or do I need to have technology that uses quantum mechanics, for this new kind of capabilities? And the answer is no. There are two options. You can cryptographically save or, or exchange Sorry. There are two options to exchange keys, that are safe from quantum computers. One is to use quantum effects, and you may have heard that as soon as you try to, observe a quantum, a qubit, it will change its state. So, you can use that effect to detect if something has been modified, and that gives you, an ability to check if there is a man in the middle using physics. But this would be too hard, but it was required that everyone has, access to infrastructure of that very high level of sophistication, and this is most likely be not very cheap. So the industry developed a new mathematical algorithm that we can use instead, and the good news is here that we can upgrade existing infrastructure using these algorithms. The new standard, that is quantum proof or quantum computer cracking proof is called TLS one dot three, and it uses just new, crypto ciphers. We don't need any specific hardware, or software for that. It's just a new algorithm that we need to deploy, and new key change, mechanisms. So we quantum the quantum wake up call is, I would say, we heard more and more about the quantum wake up call, I would say, from beginning of last year. Before that, quantum computers, news about the development of quantum computers appeared in the press quite regularly, but it was more kind of an in research, and development kind of process, not really ready for, public consumption. This changed, last year and especially this year. We go a little bit into that in the next slide. But we now can have access to quantum computers. You cannot buy them right now, but you can have access through an API that allows you to program, a quantum chip. So what's the latest? And I was wondering where are we right now. And when you open the press, there's a lot of talks about Qubits and and and other very technical terms. So I found this statement from Google quite interesting because it gives us kind of an idea as nonexperts of where we are right now. So if there is a common standard test benchmark that is used, to test quantum computers and their capability to compute specific algorithms. And it needs to be said that quantum computers today are even the existing ones are not a replacement for normal computers. So they're specifically designed to solve specific problems. So today, you could not even, in theory, put a quantum quantum chip into your notebook and have a thousand times quicker notebook. We are not there yet. But for this specific benchmark, and this benchmark also uses mathematical problems that are also relevant to crack cryptography, and achieved a specific task in five minutes, that the fastest supercomputer so we need to keep in mind this is the year 2025. The fastest supercomputers of the world are insanely fast. More than ten septillion years would need then, would need ten to the power of twenty five years to solve the same problem. As I said, it is unlikely that the first commercially available quantum computers will be that quick. This is a benchmark for a particular kind of solving a mathematical problem that is very well designed for quantum chips. So what's the what's the landscape today? So we need to deploy, we need to be become ready to the kind of risks that are increasing with every year, and we need to deploy new standards. We need to, and, deploy technology that allows our infrastructure to talk TLS one dot three using an LKEM algorithms, in order to become quantum safe. And we also need in the future to upgrade our ability to provide cryptographically safe digital signatures. Interestingly enough, we have TLS one dot three today, but we don't have the signatures. We have people employed who actually work in the, in the working group to, develop, signature algorithms that are quantum safe. So this is something that will come very soon, but we are not there yet. There's a lot of confusion about post quantum readiness and post quantum encryption. I just wanna talk, through some of them. So the first of all, as as we said, there are two different things we need to upgrade. One is the key agreement and the key exchange because after we exchange the key, we are changing to symmetric key encrypt to symmetric encryption, and symmetric encryption is considered safe today. So the only, part of the trust chain we need to change is the key agreement and the certificates. In terms of key agreement, we have technology that doesn't require specific hardware, to allow us to implement TLS one dot three, and the post quantum ready certificates is a thing that is coming potentially very soon. We don't need to upgrade symmetric crypto. What does this mean in layman's terms? Symmetric crypto is used to encrypt your hard drive, to encrypt your cloud storage. Everything that we consider a data addressed that uses standards like AS, for example, and even AS, a 128, specifically about 256 are considered secure today. We we don't need specific hardware for post quantum key distribution even there is a lot of documents out there in the Internet that talk about using quantum effects to do, quantum key distribution, which would be which is very cool and from a scientific perspective, very, very interesting, but it's not required to become post quantum ready. And very important, and this is, a statement from our CEO, It's very important that we as an industry work on standards and not products. Because this is a new problem and this is a huge problem we need to solve, it opens up opportunities to sell more products, which is fair enough. But it is very important that we everyone in the Internet, from, private people to, you know, organizations who have much more buying power have the same have access to the same level of security to communicate securely over the Internet. Trust building trust should not be depending, on on, people's ability to buy products. So it's probably we are five years away from the NIST recommendation, and but that is not much time. So it's now the 2025. Your slide is a few months old, So we can probably say it's now four years to meet in this recommendation, and that is not much time considering that the standards like RSA are used everywhere, and upgrading infrastructure at scale has always been a very challenging task. So we need to start now, and we need to develop our post quantum, strategy. How can we accelerate this journey? So the easiest way to become post quantum ready is, to put your infrastructure, so your origin service or even your entire site, behind CloudFlare. Why? Because we started the journey years ago, and we can now say that all of Cloudflare is upgraded to TLS one dot three. That means from the onramps and from the entry, points so you see here a web server, for example, if you serve the Internet and you connect to a website that is behind Cloudflare, So the traffic entering the Cloudflare network from entering the Cloudflare network will use TLS one dot three, and the origin server even does not need to be updated. So the on ramp capabilities like our CloudFlare daemon that connects the origin server to the CloudFlare network is also supporting TLS one dot three. This is was an this was an example if a user, or somebody Internet serves your origin server and then accesses the website. The second example here, is a zero trust network ex example where entire sites or your endpoints, using our WARP agent are connected to the, Cloudflare network. In this case, the entire chain from your endpoint over the Internet or the Cloudflare network to the Orange Hood server or your entire sites will be using TLS one dot three and will be safe from post quantum attacks. You're probably wondering what does this mean, in terms of the endpoint. Well, endpoints need to be ready as well. We come to that in a couple of minutes. So everything in the Internet, especially when we talk about cloud, has a particular shared responsibility model. And let us talk one minute about that because it is important to understand what's your responsibility and what's your response our responsibility to help you be with, post quantum readiness. So our entire environment uses TLS one zero three. We deployed everywhere the more the latest encryption algorithm. We are, upgrading our products. We are updating our products, for example, all the tunnels and all the proxies and everything in between, and we also upgraded our, secure key management capabilities. What remains in your responsibility, for example, is the browser. Not every browser today supports TLS one dot three, while all major browser companies have a roadmap to support this very, very soon. As far as I know, Safari is a little bit behind, but this will be probably solved within the next couple of months. You also need to place your origin server behind CloudFlare, to ensure that the entire communication chain is covered by by CloudFlare. And, you if you want to ensure that you have an end to end, post quantum readiness, you need to deploy a warp agent on your computers to allow zero trust network access, or you need to establish tunnels between your site and the Cloudflare network. So if you would like to know, is my current connection post quantum proof? That's actually very easy to check. So we have this, website where you can check if your current connection is post quantum proof, and it will tell you which part of the connection is, is ready and, which part is not. Very nice, check to, stay on top of the of the readiness progress. And another one which is quite interesting is, you don't know if you search a website like example.com or helloworld.com, you would like to know, am I using the latest encryption algorithm? Has my browser established a tls1.2 connection to this particular site or a tls1.3 connection to this particular site? So on Chrome, you use, you open up the developer tools, and in the developer tools, you find a security tab. And as you see here, the security tab will tell you what kind of connection it has established and it will show you that it uses TLS one dot three, which is the, and what specific algorithm, it uses to, provide the secure key exchange. So in this case, the, standard x two fifty five blah blah blah is used, and you see in that name, MLKEM. That is a clear indicator that the latest, cost quantum ready algorithms are used for the secure key exchange. And once the key is exchanged, the further communication is then encrypted with an AS 128 bit key for symmetric encryption, which is also considered post quantum safe. So in this case and I opened up a, a website from Cloudflare. I can make sure that my entire connection is safe. For those who don't know Cloudflare, a lot, so Cloudflare is primarily a, a network. So we want to help build a better Internet. We can't fix the Internet because it's a network of networks, so we build our own Internet. And we have we operate today one of the biggest networks in the world. And, 335, sites in the world, built this global network, including 35 sites in China. So what does this mean? We these 335 sites means that we have a presence at this site with, with systems and hardware building this global network. This global network interconnects with over 15, I think, even now 16,000 other networks in the world. What this means for our customer is that this network is light speed fast and provides ultra low latency for customers. In a 180 of these sites, we also have now, Nvidia chips that allows you to execute code anywhere in the world and even in, do AI inference in, a 180 sites in the world. What does this mean for our customers? If you build a website called hello world, and it uses a little bit of AI by generating a, providing a chat, an AI chat, or generating images using AI, you don't deploy this in a particular region. You just tell Cloudflare, here is my hello world program and domain. Please run it on planet Earth. If somebody from Canada, for example, launches or accesses your website, we will make sure that the code, including the inference, is happening in Canada. And even if you deploy that website initially from your hometown in, for example, Sydney, we will execute that code very, very close to your customers, which allows you to provide them with exceptional user experience and low latency. You see here an overview about the size of Cloudflare, and this gives you a glimpse about the size, of the network. Our aim is, to, provide ultra low latency, availability, high throughput in in that network. And security products, as you know, maybe know Cloudflare as a web provider or as a CDN. Security products are more or less a feature of this network, and we now have a whole bunch of application security, network security, zero trust network access, SASE features, that can be used using that network, and also now a developer platform that allows you, like in my last example, allows you to execute codes, on a global scale. Because a lot of our customers are free tier customers and a lot of webs a lot of websites today run on Cloudflare, and a lot of users are protected, because they put themselves behind Cloudflare using our work agent, for example. This resulted in the fact that today more than 20% of all sites of the Internet are behind the Cloudflare network. Cloudflare has always been the leader in post quantum readiness. And as I said, we started years ago to make sure that the entire Cloudflare network is post quantum ready. And we have today trillions of daily requests, that, of that perform key exchange on the Cloudflare network. So you can imagine what kind of infrastructure is required, to support this. Worldwide, we're currently seeing 35 going probably close north to the 40% of all traffic is, post quantum ready. And there's an interesting story behind this. So there's a website called Science of Triviality, and this person actually looked into the numbers. So we roughly have 30 to 40% of all Internet traffic is post quantum ready, but this person figured out that more than 30% of that traffic is all behind Cloudflare with a huge, gap towards the second player. So we can proudly say that CloudFlare is clearly the leader in post quantity quantum readiness. It's maybe or not only because we have 20% of the sites are behind CloudFlare, but also on the ease. After you onboarded to CloudFlare, there's more or less not much less to do for you to become cross quantum ready. And that's it for today. I saw on the right side, a couple of questions. Maybe we pick a few questions. Winnie, if you can help me pick a good question. Yep. Volker, so I think we have two questions. The first one says, does Logitech see any value in using QKT? QKD, quantum Yeah. I so what's don't know. Maybe I'll ask the person to Xiyeong Lee. Contribution, If you can elaborate on what do you mean by q k. most likely. Yep. So there distribution. there are two parts. Yeah. Yeah. So so if they could if I understand the question right, the question is, should I use, hardware that uses, quantum, effects, to secure this, the quant the key distribution using quantum effects, or can I rely on the, on the mathematical solution that does not require any specific hardware? And by the way, the hardware would only work with fiber. It wouldn't work over copper. This is simply something to do that we're dealing with physics when we talk about quantum. The answer is not necessarily no, because the world would never become post quantum ready if we would rely on on on specific hardware to achieve, quantum safe key distribution. So, that's why the, MPLM standard has been developed. And, the mathematical problem behind that, is considered today safe for the quantum computers that we envision will come up in the future. I know this is a lot of ifs and whatevers. The 100%, secure of methods would be using quantum effects, but that would require a lot of hardware. But if the math does the same gives us the same outcome, then I would always say use the math, which means just upgrade to a TLS one dot three, and you should be on the safe side, until we are not anymore. And then I guess we will have a new, standard by then. Alright. I hope that answers question. The next question from. I'm sorry if I'm pronouncing your name incorrectly. But, they are asking, should we need to increase the encryption AES two fifty six to be AES five twelve as practically in term of safety and performance impact for data at best? Yeah. That is a very good question. So, I'm not a mathematician. Everything I heard so far doing my research, said that a s even 128 is considered safe for now. So that tells me doubling that gives us, an exponentially it's not a linear. It's an exponentially better protection. And I would consider, a s two five six secure enough today. To be future proof, more security doesn't hurt, 100%, but it always comes with drawbacks or everything is a a trade off. So better encryption is always a trade off because more computation is required to decrypt data. That means, we are we require more energy, but we are also introducing latency. So higher more keys or more cryptographic longer cryptographic keys consume more CPU. That means if I access data, a lot of data that is encrypted, I, increase the latency to access my data. So everything is a trade off. You know? If you can if if you have for archive data, for example, I would always use the highest key because, ideally, I never, try to decrypt that data. And even if I want to decrypt a backup data, it doesn't really matter, if it takes a little bit longer. But for data that is constantly accessed, like on a hard drive or an s three bucket or whatever, you need really need to think about, how, how strong you want to encrypt. You wanna be on the safe side, but you don't wanna overshoot to reduce cost and, achieve acceptable latency. Alright. Maybe Moving on. in this future, Sorry. quantum computer changed that game, but we are not there yet. Hope that answered that question. Volker, the next question asks from so this question is from. I'm sorry if I'm pronouncing the name incorrectly. How soon TLS 1.3 can be settled to be the standard? TLS one dot three. The question is what is settled to be the standard? So TLS one zero three is the new standard. The question is how quick organizations upgrade. Right? So, TLS one zero three using specific cryptographic algorithms that we handed on today is the new standard, is considered to be secure. That's what we use in Cloudflare, and that's also what's used with the other hyperscaler. The the entire conversation is about, upgrading to TLS 1.3. When you talk about, browsers, are browsers post quantum ready? The question is only do they support TLS one dot three. And we are the like in TLS 1.2, you have options. You have options what kind of cryptographic standards you use under the umbrella of TLS 1.3. Like, you can use, in TLS 1.2, you can use Diffie Hellman, or you can use RSA to perform specific tasks in that, communication encryption. And the same thing will happen in TLS 1.3. But more important is TLS 1.3 is is flexible in this regard that if a new cryptographic standard comes in, it will be able to support it, and and it will be also, mandatory for one dot three, which is not for one dot two, that the standard is, forward safe. So that once you collect now and decrypt later, will not be an option. Thanks, Volker, for that insightful answer. Evan asked, are we able to view who's accessing our websites using ML AEM on the Cloudplay dashboard? Yeah. Yeah. On the Cloudflare dashboard, that is a good question which I, on top of my head, cannot answer. And and I'm happy, you know, if we can, if you can contact us, my email address will be available. I'm happy to answer that. So the, what method is used is part of the TLS key exchange. So that's not necessarily happened on your web server. So you may not know, but you see I mean, we see this definitely on radar. I'm sure you can see it somewhere on the on the dashboard, but I I cannot answer this question on top of my head. Sorry. It shouldn't be too hard. It shouldn't be too hard, but, ultimately, it leaves traces. You will say, okay. What kind of communication has been established with the with Cloudflare itself? And you can and I know that on top of my head, you have the choice. So there is the if you want to do the right thing and you are what for example, you are behind Cloudflare and you are accepting so you are ready to use TLS one dot three, but your visitor is using a legacy browser version, and the browser, is negotiating to TLS one dot two. So everything at the beginning, if TLS one dot two or or three is used, is an outcome of the initial negotiation. And the negotiation, depends on two things. First of all, who is limited to what kind of standard. So if the browser can only speak TLS one dot two, then you can only negotiate on the level of TLS one dot two and establish a connection on that level. The second part is what is your policy? And this is something you can configure, certainly, in Cloudflare. This is, I'm not too sure about the visibility. You certainly have to control, that you say, okay. For I am TLS one dot three ready, clients can talk to me in TLS one dot three, but I do allow that legacy clients are allowed to connect to my website. Right? So when we're getting closer to, a time where quantum computers are commercially avail will become commercially available, you can then change the policy and say, okay. I only allow negotiate, TLS one dot three. And you can potentially even make a kind of a risk based approach. You can allow legacy standards for your public websites where security is not a big concern because only public data is served on that website, but you enforce TLS one dot three as soon as the communication gets private and sensitive data is involved. For example, a bank may allow tls one dot two to to go on the home page, but enforces TLS one dot three on the home banking website. Alright, Volker. I don't think we have any more questions. If there are any more questions, please feel free to drop them in the q and a box. Okay. There's another one that is coming right now. How many love, that so many questions come in. Thank you. how many percentage in USA to adopt CloudPath for PQC? I don't have the answer on top of my head how many in The US. I don't have that. I I have the number that, 20% of the global Internet is behind CloudFlare, and that is, of course, a mix between, paid customer and free customers. I don't have on top of Maheta, numbers in The US. My gut feel is that the, that it is on more than 20%, but I don't have the numbers. I'm sorry. Yes, Salida. Alright. I think that was the last of it. If there are any more questions, we are still here. Please feel free to drop them in the q and a box. If not, please make sure to also check out the doc section next to the chat on the top right corner. We have attached an upcoming webinar link, and, also, there is an ebook about modernizing security in the AI era. That would be very relevant to today's webinar topic. So maybe we can wait another minute to check if there are more questions from the audience, Volker, and then we can close it. Yeah. Alright. And, while we wait, let me just thank you, Volker, for hosting this insightful session. I'm sure all the attendees were as engaged as I was throughout the presentation. And on that note, I would also like to thank all the attendees for joining today's session and interacting with us live. Hope you found today's session relevant and valuable. We look forward to seeing you at the upcoming webinar. Like I already mentioned, the registration link is attached in the doc section on the top right corner. If you have any further questions, we are still here. We are waiting. Please drop them in the q and a box, and Volker will take them right away. Thank you. Thank you very much. Much appreciated. Bye bye. Bye bye.