Transcript for "Forcepoint Office Hours | Next-Gen Firewall 'Ask Me Anything' | DEC 2025": Hi, everyone. Thank you for joining. I appreciate everyone who hopped on a little bit early. We're gonna give it just a minute here, and then we'll go ahead and get started with today's four scoring office hours. Alright. Alright. Thank you all for joining. Give it about another fifteen seconds here, and we will go ahead and get started. Alright. Let's go ahead and dive in. We have a packed session for you today. But before we get started, as a reminder, the presentation is available for download. As you have as we go through the presentation and you come up with questions, please feel free to go ahead and drop those into the q and a. You do not need to wait till the end of the session to do that. And about ten minutes or so, as we start to wind down, I will send out a post call survey. We do review and read every single response that we receive, and we are working on our plans for 2026. So please let us know in the comments if there's anything that you'd like to see as we go into the next year. And as always, you will receive an email tomorrow with a link to watch the playback. Alright. We have three presenters today. We have Klaus, our principal product manager for network security, Lorenzo, our senior customer success architect on our CS organization, and Yako, our director of research and development with engineering. And I'm gonna go ahead and turn it over to Klaus. Okay. Thank you. Good afternoon. Good morning from my side. I'm a product manager for the Nextiva Firewall. So, we we are are having a beautiful day today. So we are having seven dot four version released today, and I will go quickly through what we have there. So these these were, this release is not the long long term supported release. It's a feature release. It has some, very interesting features. Can you, share the slides? Yeah. Sure. One more. There. Okay. So we have a very interesting features there. Some of them are, directly customer requests, like like the, application portal. You remember we used to have a SSL VPN portal. We renamed that as an application portal. We had couple of interesting customer cases who were looking at, how to access, through the firewall corporate resources. And, application portal or the old SSL VPN portal. It it worked quite well with the web traffic, like HTTP and HTTPS, but it didn't work very well with, like, SSH, remote desktop, or VNC. So, we created a a kind of hybrid model there where you enter the application portal, and then you have a Qualcomm all open source after it. And it helps us to do the SSH, RDP, and VNC, And and then we have, access from the application portal to it. We also, in the same, kind of setup, we also, brought in the SAML authentication in that portal so that when you enter the portal, you can, do the SAML authentication. And as part of that SAML authentication, we previously didn't support email addresses as a username, So using the at mark or at character, at the like, you use it in a email address, so now it's allowed. And, also, we brought up something that you can, do the authentication without LDAP. So we, we handle that a little bit differently. And all that is a kind of one bigger feature that allows us to use the application portal and and one more thing we added there so that, if you have a your normal VPN client, it uses SSL, you can use that same application portal, go into the SAML authentication, and then click a button, and it automatically uses those same authentication tokens for the VPN client. So then you it automatically opens a VPN client. It's a kind of, I don't know, kind of workaround so that you can have SAML for the VPN client access as well. Then we also prod the local support for URL categorization. There were a couple of companies who didn't want to send any URLs to the threat seeker in a cloud. So, in order to solve that problem, we brought the threat seeker database directly in the firewall engine. So now you can make those queries locally. You still need the URL, license because it's basically same function, but instead of a cloud, you're using now local database in in the firewall itself. In some cases, it might provide you a little bit faster responses for the URL categorization. Then other big thing we had is the explicit proxy with the Windows authentication and, browser based authentication support. So we we used to have a lot of sidewinder customers to proxy firewall customers. So it's really good for those kind of customers who don't have default route out of the network, and they need to use proxy or something similar, explicit proxy to get out of the network. So we provide that. It's it's it doesn't have as many features as our other Forcepoint web proxy product, but, it normally has enough features for, that kind of customers who were using Sidewinder earlier. Then we also finalized our QUIC and HCD v three, protocol support. So now we can support them, the QUIC and HTTP much better. So the new faster protocols for web browsing. We also did some remote access advancement. So the VPN client that we have out there, it on a TLS side, it had slower downloads, so we implemented DTLS. So it's using UDP for the data transfer. So it's a faster way to do TLS than the TCP, TCP kind of, TLS what we had before. And then appliances, I actually cover here. So we have one new small appliance, 130. It will replace the 120 appliance that we had before. This one is faster, and it also has eight ports. Two of them are SFP ports. So if you want to want to connect it to the fiber network, one gig fiber network, you can use those two SFP ports for that or if you want everything to be copper, so you just put copper transceivers in there. We are going to bring the WL, so Wi Fi and and the five g version, early next, maybe q two next year, and then that will replace the other 120 w l models, that we have currently. Then, we are also bringing a new 2,300 series. It will replace the 2,200 series appliances that we have currently. So, there's three appliances on this series, twenty three zero one, five, and ten. So, originally, we we were planning to release this in q one next year, but there were a couple of customer cases which we, thought that, okay. Let's bring the third twenty three zero five and twenty three ten already available at the end of this year. So they are already available, and the twenty three zero one will come sometime in q one next year. It's a good, good product line. And and compared to all 2,200 series, it had one module slot, and this has two. So it can give you a little bit more port density if you need it. We also brought the four port 25 gig module, earlier this year, so you can have a lot of 25 gig ports in this model as well. Let's see. Then we had, okay, road map. So here on the left hand side, you have the the road map for what we have no. Kind of Yesterday, it was what we have currently. But currently, we have the the seven dot four is the green in the middle, and then the blue on the right hand side is, what is coming, I I think, about mid twenty twenty six. And, I have to see screen is really small. Can I get it any bigger here? Let me do it. So move it to another screen so I get it a little bit bigger. So, we, we have the CTNA solution. So, or or let me go that way. The seven dot four that we just released, we were supposed to have SMC as a service GA around this time. We have postponed that a little bit, to sometime for the next year. We are, we have the high availability, scripts available for Oracle Cloud, AWS, and Azure. We have that application portal, SAML, that I explained earlier, and HTTPthree and QUIC, and threat secret database, and then those new appliances. And then if we go to the next year, we are scaling up the SMC as a service, so that the current one could handle maybe ten, twenty engines. So we continue to work and, scale it bigger so that it could handle maybe 100, 200 engines. And then the CTNA solution, so, we are working with the, our existing VPN client. So you know that we have endpoint context, agent, and VPN client, they are currently separate. So there's a plan to combine them together and and then have a kind of CTNA solution. This application portal is part of that solution like a clientless CTNA, and then with the client CTNA would come that combination of ECA and VPN client. We are working on some of the advanced security add ons, like, if if we want to quarantine some files and stuff like that. We're also working heavily on the AI, and I don't talk much about that because Jaco has couple of slides about that. So he will tell about that. We are also working with the quantum resistant crypto. We already have something to protect you against, quantum computers, but sometime next year, we are actually adding those, like negotiation algorithms that are, quantum crypto resistant or quantum resistant crypto. And and then, also, we have the 20 o one o twenty three zero one appliance, for the 2,300 series. And then we also working to get some kind of rocket appliance for OT environments or or or, installed in, vehicles like in a trains or or places where they might get some moisture or water and vibration. K. And here is the the appliance line. So you know the 60 series has the 60 n 61. That's faster than the old 60 series. We still keep the n 60 l there. So, n 60 as itself will go end of sales, but, 60 l, so LTE version will stay there. 130 series will replace the 120 series at some point. Currently, we have the plain version available, and then three fifty series stays there. 1,200 series stays there. 2,200 series will change to 2,300 series. We have some government customers who need government certifications, so we will keep some of the twenty two zero five and twenty two tens available for them. And then 3,400 series is still there and, but will be replaced at some point with the 3,500 series. And we are working in the sometime next year also for the maybe even higher model for the 3,500 series and also 400 gigabit interface cards for for those customers who have 400 gigabit, core network. That's all from my side. I'll give it next to Jaco. Go ahead. Good. I found the mic button. So good. Hello, everyone, and welcome. So, yeah, I'm Yakima. I'm the director of engineering here. I lead the network security engineering. And today, I'll be showing you, a sneak peek of what we're working on in the front of AI. So as everyone, is is certainly aware, the the AI technologies have have, taken major leaps forward. And, we are also looking at what, what would be the best use cases for our product to to utilize AI and and and bring value to our customers. So, today, I'll show you a couple of, brief demos, from my team, and then, explain slightly the, the, the technical technical background, what what you'll be seeing there. So, without further ado, I'll now try to get the screen shared for the first demo. Good. So the first demo will be about, about log analysis. Let's put it to roll. So, we have introduced a new tab to the, to where you have the filters for logs, where you can, insert queries in a natural language to to browse your, browse the the logs that you have there now, this, it browses the logs through the through the back end and also provides a a brief analysis of those those logs And, as you can see here, it's remembering the context of your queries with it. So you can make, you can drill down and and, go further with your with your queries. The the documentation of the product, is also included, into the, into the LLM data as as, as a rack, server rack, database on the background. So, you can also make curious, about how to use the the product I've seen here. You can ask, questions on how to configure the PBK, for example, here. So this is basically, these are basically the the first steps on on a longer journey to to extend these features, and the the, the target will, of course, will be to to be able to create elements and and configuration changes as well. As of now, this is, what we're developing right now is is that it will be able to to to work as as an assistant for you and and kind of, ease the use of the use of the product. So that's the that's the first demo. Then, let's have a look at the second one. There. Good. So on top of the log browsing and the analysis, we also, are working on, on a policy analysis tool. So, basically, in the policy view, you have the same option to to open the AI pane and then, do a queries about the the policy you have in place. So this is implemented, currently in two phases. So there is a first analysis that's done per log, or per policy, policy row, and then, that analysis is per row is then inserted into the LLM just, because the the policy itself is not something that the LLM is able to read, and digest. We'll need to do, initial digest done by code, and then we provide that as, as data for the for the, for the AI. So here, we made two questions, how to improve the security posture of this policy, and then, made further further questions about about how to do certain things here on this demo related to the logging options. So as said, these are under development, and, we're for of course, interested to hear feedback about, what do you you think would be the the, most, most usable, features here for your workflow. Then, we can shift back to the presentation. So then, briefly about the technical side, how this works. So we are utilizing, MCP, server here on the back on the on the back end here to to to implement the queries against the logging back end so, the when the user makes queries to the to the, to the SMC about, what logs we want to see then, after that the MCP client discusses with the MCP server and the LLM to basically generate, a log query that then can be provided to the to the logging back end. So it it translates that human human, formatted, log query into something that our actual logging back end can understand and we can execute. And then the logging back end is able to to to come back, with a reply, and that's then formatted analyzed and formatted to the to the user. The MCP allows us to abstract away the LLM so that we we are able to test different LLM, LLMs. Obviously, on our side, we we prioritize locally run LLMs because, many of our customers, understandably don't want any of the information to leak from their network. So so we, our priority is to is to be able to, to run the whole thing at, at the customer environment. And here, you can see a a brief example of what what the log query looks like. So so here on the left, we we can see that the user has made a query, by natural language to ask about the SSH connections. That is then translated by the, MCP and the LLM into something that the logging back end can understand. So it's, that that dissertation formatted, query generated by the LLM, and then that is then formatted, forwarded to the to the logging back end. It is able to understand this, machine readable query, and then the logging back end replies with the actual log entries that we see on the right. That's a technical background of of how it works. Good. And, happy to answer any any questions about this. Just put them on the chat or on the on the q and a. Thank you. I'll I'll forward it to to Lorenzo then. Thanks. Thanks, Jaco. Yeah. Yeah. I'm, customer Lorenzo Gantelmik as a customer success architect, in customer success business unit. Today, I'm gonna present you this proposal to test the SMC UI. Next slide, please. From the previous office hours, I share with you the fact that we are leading some initiative internally. And from those initiative, there are interesting trends that I used to, spot. And, specifically from the material assessment, I've been spotted some related to some testing situation done by the customer. Next slide, please. One of the main trend is that, I noticed that really few customers have adopted preproduction environment. So I I found occasion to to refresh a bit the relevance to test, any change in the preproduction before going to production environment. I would like also to highlight that the preproduction should be closer to the production setup and, at least cover, with a doc tests the the critical business use cases. Right? The the validation is, should be done by due diligence at UKL, which are two principles that are part of the security domain and also the professional board. And, also, I would like would like to highlight that the change itself should be assessed, you know, in terms of criticality, rollback feasibility, especially when the rollback is not possible, the extra care is needed. Contextualizing this within our solution, there is one of the most critical changes are usually the upgrades of the products. Right? And, specifically, the SMC upgrade is a critical operation. Sometimes, it may not be possible to downgrade to to the previous version, especially if you, let's say, start to apply changes in production. While it may be possible, for example, for the next generation firewall components. So it is critical to put extra gear in this operation and avoid blind SMC upgrades. Right? Because, there may be strong impacts in for the business, operations, and productivity as well. Even if the issue from your perspective may be minor. Right? Consideration is that even if the product goes through the high quality assurance process, Since each customer has his own unique workflow, how it operates, it is strongly recommended to lead this, SMC UI testing. Okay? Ideally, with the production like data. So within this context, I encourage initiating this kind of SMC UI testing by proposing a generic procedure via SMC demo mode installation. We'll see the benefit later on. And, that this has to be a complimentary step to the ad hoc preproduction validation that any customer should do. At this procedure, the Tangoe Pro boss can be introduced in the change control process. Next slide, please. So this procedure consists of installing the SMCDMO mode. We'll see later on step by step. And later on importing the backup in the in the virtual machine. The goal is to have an isolated framework or VM where you can lead the the test you want in a kind of sandbox. And, the purpose is to enable you to to have, either the option to test the remote when needed and also get closer to the production testing with after the import. And, once you set up this environment, it would be also easy to share with, within your technical team before upgrading, you can do the testing as needed. Next slide, please. So the the proposal approach, at refresh is, is not that replace the preproduction testing. It's rather a complimentary way to test the UI. It is, in fact, an enabler, this approach, to to access a minimal environment where you can spot quickly differences between the target release that you are testing with respect to, the the production layout of the UI. You can validate UI fixes on the same dataset where you reported the the data the the the problem. You can validate also with this procedure the health of your backup. Sometimes there are backup that were not tested. The one the import was triggered. The backup was basically compromised in a chief work. No? So it's good practice to test periodically also the the import of the backup. No. Previous slide. Sorry. Then you can test also all the, object opening, editing, and saving, including the critical policies engines. You can manipulate objects there. You can also, as I said before, the, test, the layout, how it looks like in the most recent versions, such as the new one, like seven zero four for curiosity and whatever. You can also test, the some features that Jako mentioned. So it's a way to have this kind of secret sandbox where you could potentially also test some API integration. I shared there some references how to start the getting started with API and also, some references about how to test the scripts because, indeed, it is critical to test also API integration because the execution of this script may have strong impacts in the production if not validated before. And also, with this tool, you can, for example, based on the production data imported, also assess in advances there are potential bugs that may impact you if you would have upgraded. Okay? So it's very meaningful. The over go overall goal then, as I mentioned, is to decreasing the chance of having measure issue after, SMC upgrade in terms of, SMC UI usability and productivity, and increase the chances that SMC upgrade success criteria are met. Success criteria may be related to the simple testing of this with this framework, but should expand to overall success criteria bound to the production testing, integration testing, and so on. Okay? So, overall, for this kind of testing, I would be also available to to share knowledge, with enterprise customers. And for any issue, you can, just report, the problem to our support. Next slide, please. So now we see in this appendix, all the procedures step by step, procedure one, and then we also have quick overview on the procedure two. Next slide. So for step one and two, the the goal is to define a virtual machine that could match the hardware specification. It's a sure way when you will trigger some testing or display some, some UI elements, the time of response will be, the same of the, the the one that you have in in production, basically. The download of the binaries can be done from our customer hub, and the targeted version can be selected based on your requirements. You know? And you should consider also the release notes about the which which kind of version is supported for the migration. Next slide, please. So, the the goal is to launch the demo mode standard installation. You will end up the the installation and then soon quickly, you will be able to access, an environment, where there there are there will be some, emulated engine. Okay? Fake engine. But the the UI itself is operational, and, you can perform even some policy refresh on, on this environment. Next slide, please. After this operation, then the recommendation is to create a starting point taking a snapshot of the VM. And from there, you can revert to this point whenever you want to do this kind of testing where there are also some fake log servers, log entries generated, and to explore all the integration of the services. Instead, if you want to focus on the management, let's say, UI, we can restart the machine and then import the production backup. We can place it in a temporary file folder. And, later on, we apply some tuning, after stopping the the services and reflecting the memory assigned to the production management services. Next slide, please. So, in order to have an isolated environment, then recommendation is to disconnect the virtual cable for this solution. Then there are other, other visor that allow you to do it anyway, this kind of disconnection. And you can start then to import the big app. Next slide, please. Of course, before starting the services, I recommend to confirm the isolation of the the host from networking perspective and take, also VM snapshot to reutilize the the the this kind of setup in case you decide to roll back, to the other scenarios. Okay? So once you restart, next slide, you will be able to to connect, local host. And then next slide, You could basically access them, the the UI as it is in the newer version, for example, and see how it is, the the UI behaving, if there are problems to display the UI, and so on. So you could really benefit of this kind of procedure, which is generic for any, any version of the SMC. Next slide, please. Beyond the procedure one that I mentioned you, there is a procedure two that allow you just to install directly the SMC demo starting from demo backup. That, basically, would skip the possibility to access the the the mode environment standard environment. With this, you just install the the the software, the MoMoD with the by restoring directly the the the production data that you need to test. So, between the two approach, the the first one is more modular and allow you to get more flexibility. This one is more direct and and, anyway, variable. Next slide. I guess it's done. Perfect. Okay. That's it. If you have any question, I will be happy to follow-up, Thank you, and, Lorenzo. And thank you, Klaus, and Yako. as well. Let's go ahead and go into our early submission questions. We've had a really active chat and q and a today. So thank you guys so much for getting in there and asking your questions. I think some of these are a little, very much the same, so we might have the similar answers that are in the chat as well. But starting with the first one, is there a plan to have a cloud based SMC instead of maintaining a VM, for this purpose? Looking at other folks who are using a web based interface to manage their console. Yeah. So, I can answer that one. As you know, we we, used to have the fat Java client, but there there is the there is a possibility to have a web page, GUI as well using the the kind of the web server that's in the SMC. We have also plans for the SMC as a service so that the Forcepoint will host the SMC in a cloud, and you as a customer would be using it. We haven't g a'd that yet. We are still working on it. We are working on the scalability of that thing. So once that is done, we will probably announce it as a product. So it's in the works, in the finalizing finalizing phases. But, yes, we are still planning to keep the Cello client, for now. I don't know. Jaco, do you have any any, other answers that Justin is asking that, you are still planning to keep the Java client? Yeah. We are, yes. We are planning to keep the Java client. Yes. And, internally in engineering, we are looking at options to, to, to implement, a UI that would be, React or some some web technology based. That's something we are investigating the best methods to to implement such, such. But, of course, it's a big effort to do that. Yeah. And and, Jennifer, one more. Tara pointed out that, I should clarify that currently in the seven dot four, we don't have SAML support for the VPN client. So VPN client itself doesn't have SAML support. The only way you can have some kind of SAML support for the VPN client is use the application portal and do the SAML authentication there, then you have a button there that click that use the VPN client. That's the way it works with the seven dot four. We have plans to do it, so that you can just run the VPN client and have a SAML authentication for that, but it's not yet ready in a seven dot four. Okay. Next question. Thanks, Klaus. I mean, that seems to be a consistent question as well. So we have one here on the screen. I think I saw a couple come in as well. So the second question here is about the new secure access client, which includes ECA and VPN components. So what will that look like when it includes both of those components? And they're asking about the licensing, so it will be licensed separately. And then will secure access client be further enhanced with verification, for example, of a specific process registry key or an AD Entra ID affiliation? Yeah. I can take the first part, the licensing. So currently, the VPN client and endpoint context agents are license free. We are still considering, should we make the license? There, we we tested the pricing with couple of customers, and they said that $10 per user might be good price for the client. We are looking into it. We we haven't decided on that yet. So if you want to give your feedback, please let it come in. So, there is a possibility that we we license it. Currently, it's not licensed. And and the rest of the questions, Jaco, can you take those? So, yeah, the the, the plan is to integrate, to have the, the capabilities that are currently under any ECA on the VPN client, integrated. To accelerate the release of this combined client, we may come out initially with some, with a version that doesn't have all the ECA functionalities, but, but the the plan is to have them there eventually. There is, the the ECA itself, that that client is planned to have the, the machine on authentication capability, both for Windows and Mac so that you can do the, you can allocate that the machine belongs to the to the company. ECA actually, has that currently already since, the distribution method of the certificate is through the AD. So the administrator, it won't, ECA won't function without having a certificate that, belongs to the to the organization. Okay. Alright. So we've already covered XAML authentication. We're gonna skip down one here. So why is change management in the SMC and GFW not separated between changes in current configuration and automatic daily force point updates? They would like to have those updates on, and at the same time manage, where'd it go? And the same, some user made changes managed. Yeah. Could you wanna explain why the SMC doesn't allow that? I'm trying to understand the question. Just a second. I'm. a bit slow. I I I can try from my side. So if I understand correctly, that's the the reason is that the SAPC doesn't have a version handling for the policies. In order to do that kind of, that we allow, like, dynamic update to be refreshed separately from the policy up, refreshing or allow some admins to refresh part of the policy and stuff. That's currently not something we can do. Is that correct, Jako? Yes. I would need to go back and get a bit more detailed answer from my team. So so yeah. Yeah. Yeah. It's recommended to open a feature request then, in case when there's a gap, and then we can assess it. Yeah. There there are, there are several pizza requests around this topic. Alright. So going on to number five, if a hardware is coming end of life, will it stop working before you've had a chance to replace it? And if it if it doesn't stop working, will you still be able to push policies? Yeah. There are different, okay. This is appliances real appliance related. So, once the, once the appliance comes at the end of life, we will limit the, operating or the the version of the firewall that it can run. Like, for example, I just today added three three zero five appliance that it can only run seven dot three, LTS version. It cannot be upgraded to seven dot four. So that kind of restrictions will come when the appliance goes end of life. Also, we officially, we don't support it anymore, so we recommend that you actually actually upgrade. Before the end of life, you start thinking about hardware refresh. So our current thinking is that the hardware should be refreshed every five years if you have possibility. There are some exceptions, like, for government where they might have a longer, time requirements. But dynamic updates will cease. So once it goes to the end of life and we don't support it anymore, you do not get the dynamic, updates anymore. Some cases, it might stop policy pushes as well. You can keep running the existing policy that you have, but you can't make any changes anymore. Okay. So I recommend that, do a little bit of planning before the appliances go to the end of life. Okay. And then the last question, which I believe I also saw in our Q and A as well, is around integrating any new features from Sidewinder platform such as the new SSM proxies. So we we did integrate some of the SSM so Sidewinder proxies, to our firewall, and they are there. We haven't implemented any new, new proxies, but we have the new explicit proxy functionality. So it kind of brings you a little bit more. Jako, do you have more details on that? No. Not from my side. No. Yeah. Okay. We we so the kind of short answer is that, no, we haven't brought any more Sidewinder proxies into the firewall, but you might find the explicit proxy function that we currently brought to the seven dot four release. They might Okay. Alright. We've got about twelve minutes left. I am gonna go ahead and push out this survey before we dive into the open q and a anyway. questions. Again, we do receive and review all of those submissions. So if there's anything that you're looking for for 2026, please feel free to comment that on the survey as well. Let me jump back here to the Q and A. Let's see. Okay. So a couple let's see. I think we might have already covered this one, Klaus, but just in case, when is the planned release date of the VPN client with SAML support for Windows and macOS? Yeah. Of course. Do you have that? so, we are targeting next year for, for that. That's, we are combining the ACA. So it's a it's a bit bigger effort, but that's the, that's the plan. The team is currently working on it or starting work on it after the we are getting this seven zero four now out. Awesome. Alright. And I think, Klaus, this one might be for you. When will the SMC as a service be available to purchase? Sometimes next year. I can't sorry. What cannot very like? be more specific, but we are working on, scaling scaling it up a little bit before we release it. Sure. Alright. And let's see. This one is a little bit more of a technical question, but I have added all network applications, some known protocols for free VPNs, but there's still more and more. So what is the best practice in those situations? Daryl, can you take that one? Yeah. I think, like, I I suggested using the URL to your proxy for that, but I'm not sure if that will be enough for, perhaps it would be a better for this. We could check with, our, ex ops team. But the recommendation would be for for this, VPN services. It's it was. very, very difficult to hear you, Tara. You were, breaking up. okay. I'll reply write an answer. Thank you. Thank you, Thank. you. Alright. And I think you guys have been very active in the chat as well. So I think we've gotten all of the ones in our q and a so far, but please feel free to keep the questions come in. I do think we've got all the ones in the chat as well. Okay. Alright. So I think we are caught up, but please feel free to keep your questions coming. So about ten more minutes before the session is over for today. Alright. Right. So we'll give it just another minute here, and we can go ahead and end the session just a couple minutes early if there's no other questions. Here's one coming in. I'm gonna go and push it over to the q and a, but I will ask it live. Can you share any information regarding certificate based authentication for iOS devices? Yeah. I got that. It's probably for. you. We we we probably need to this needs a bit more digest then. Dave, if you don't mind to open a support ticket or something, and, we can, continue from there. Alright. Give it just another minute. Again, thank you all for joining. If you haven't taken your survey yet, definitely recommend, like I said, I do read those responses. I do share those with Klaus and the product management team. And we are again looking for what what we're gonna do in 2026. We're building off that road map now, so this will help us. Alright. So if there's nothing else coming in, again, really appreciate everyone for joining today. Hope you have a wonderful rest of your twenty twenty five, and we will see you in 2026. Thank you all. Thank you. Fine. Bye. Thanks. Bye. Alright, guys. I will do here. Bye.