Name: Agile SASE: The Fast Path to Modernize Remote Access and DNS Filtering
Uploaded: 2026-09-23T06:16:15.564Z
Duration: 48 min 12 s
Description: Agile SASE: The Fast Path to Modernize Remote Access and DNS Filtering

Transcript for "Agile SASE: The Fast Path to Modernize Remote Access and DNS Filtering": Okay. Hello, everyone, and welcome to today's webinar on Agile SASE, the fast path to modernization. We are excited to have you all with us. My name is Vinay, and I will be helping support today's live session. In this exclusive webinar, our expert speaker will explore how to get your modernization product projects back on track with a unified SaaS platform that other providers promised but couldn't build. But before we begin the session, a little bit of housekeeping. On the top right corner of the screen, you will see the live chat option that you can use to interact with your fellow attendees. In the dots section that is located next to the live chat, we have attached a document on evolving your SaaSy architecture and a white paper on streamlining cloud connectivity that is relevant to today's session. On the extreme right, you will also find the q and a box. As we progress through this webinar, I encourage you to leave all your questions in that q and a box. 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, Abhishek Gupta, senior solutions engineer at Cloudflarem. Hey, Abhishek. Hey. Hi, Vinay. Can you hear me? Yes. All good. Okay. Please take. it away. Hey. Thank you so much, Vinay, for the warm introduction, and, thank you everyone for joining the session. I'm looking forward to speaking to all of you, and please feel free to drop a chat if in case you have any questions or if you want me to deep dive on any specific aspect. Just feel free to feel free to drop a note on the chat, and I'll be more than happy to take that up. So yeah. Thank you, everyone. Welcome welcome, to this webinar, and thank you for joining. And my name is Abhishek, and I'm an enterprise solutions engineer at Cloudflare. So today, we'll look at practical ways to modernize security and networking to an agile SaaSy approach. Right? So we'll focus on two common starting points. The first one is modernizing remote access. You and, the second one is using DNS filter for web protections. Right? The goal is not to suggest a disruptive all at once transformation. Instead, we'll show how organizations can start with one focused use case, prove value, and expand over time. Right? So the title captures the main idea for today. Right? SaaS modernization does not have to be a multiyear transformation before you see value. Right? So we'll focus on remote access and DNS filtering because they are practical starting points for many organizations that we have been talking to. They can address immediate security and operational challenges while creating momentum for a broader zero trust and SASE strategy. By the end, I want you to take away three things. Right? First is how to choose a starting point. Second is how to migrate without unnecessary disruption. And the third one is how to build towards a broader platform, over time. Right? So we look into these aspects, throughout this webinar. Before we begin, let's understand where everyone is starting from. Right? So on the right top corner next to the chat, you would see a poll question still. Please feel free to drop your response, and, then we can get started from here. So please select the option that, best describes your organization from just learning about SASE through to having SASE fully deployed. This this to be honest, there's no rank or wrong answer. Right? Some organizations are still defining their first use case while others are actively expanding an existing deployment. Right? Okay. While the poll is running, one observation from our customer's conversation is that many organizations are still planning. Right? Piloting or stabilizing their first use cases. The important question is not whether you have completed the full SaaS journey, but it is about where you can create the most value or next. Right? So, yeah, we'll look into that in today's session. Okay. I hope you all have submitted the poll. Alright. Yeah. Moving on from here. So what are the fundamental challenges that we're seeing with the legacy architecture? Right? So the fundamental challenge is that legacy architectures are difficult to remove. Users are working from more locations, applications are moving to the cloud, and AI is introducing new types of risk and activity. But many organizations are still operating with security and networking models built around fixed offices, network boundaries, or with security and network models built around, hub and spoke our infrastructure. Right? So point solutions may solve individual problems, but over time, they can create gaps in visibility and control. So noting we eventually ends up managing more policies, more consoles, more integrations, and more infrastructure. Right? The result is a difficult trade off. Organizations need to move faster, but complexity makes every chain slower and riskier. The promise of SASE is to convert security and networking on a single cloud platform. It is supposed to be simpler, more cost efficient, and more secured. But first generation SaaS providers are struggling to deliver on that promise. Right? They delivered a patchwork of proxies and complex policies, essentially becoming new technical debt. Our goal is to simplify security and modernize connectivity. Proflin one is the unified platform that other providers promised but couldn't build. We eliminate the friction of legacy setups by providing one control plane, one data plane, and one infrastructure layer. Our second mover advantage and the organic innovation has followed us to focus on building SASE the right way from the ground up. End to end visibility for every traffic flow, then consistency for all ramps up ramp on on ramps and predictions, and finally, support the customers on a global scale, right, to support distributed enterprises. So before we get started or move before we move further, I wanted to understand how many of you have access to the CloudFlare dashboard, and if you have played around the dashboard, if you would have maybe tried onboarding few users on your zero trust tenant. Maybe if you can have a show of hands in the chat, please, and then we can move from here. Okay. Anna, I see, she has explored the dashboard. That's good to know. Okay. Yeah. I I would, yeah, I would recommend, everyone to probably explore the dashboard. Right? The good part is you can sign up on the CloudFlare dashboard for free. You can set up a test tenant, and you can explore enabling certain features. Right? Test it out, lot of these functionalities that I've been speaking about. Right? And then you can share the feedback with us. If you want to explore any new use cases, we'll be more than happy to help you onboard onto our journey. Okay. So SaaS is a large scale architectural shift. Right? So it can be challenging to know what to prioritize. Based on our experiences with customers, we recommend organizations focus on five strategic areas, which is listed here. Right? The first one, it adds unique value. For example, stopping email email phishing attacks will always be on top of your mind. Right? AI security is one of the hottest topic in the industry, and adopting a coffee shop networking approach is a great way to reduce hardware and simplify connectivity. Today, we are going to focus on the first two that is modernizing remote access, and the second one is DNS filtering for web protection. So let let's let's again get a poll question. You should be able to see on the right hand side of your chat window, just next to the chat, you would see a poll question popping up there. So probably you can fill your responses there. With SaaSy use case, is your organization most likely to prioritize in the next twelve months? So please feel free to drop your response here, and then we'll move on to the next section. So it could be modernizing remote access or replacing your VPN, or maybe it could be securing contractor access, or if someone has bring your own devices, those kind of use cases, we can look into that as well. Okay. I can see responses trickling in. So I think most of you have opted for the first one and, second one as well, securing contact as being your own devices and for privileged users. Okay. Yeah. That's good to know. We can move into the next section. Remote access and DNS filtering are two of the most common starting points. Right? So let's look first at how organizations are modernizing remote access. So modernizing remote access is often a foundational step in a zero trust journey. Right? So traditional VPNs generally provide network level access that can create a broad trust relationship and may be difficult to manage for contractors or unmanaged devices or privileged users. Right? And organizations going through acquisition, especially m and a. With zero trust network access, access can be evaluated using identity. Right? We can integrate with your existing identity providers. We we can give you based on device context, you can create policies. Based based on applications, you can segregate policies. And so rather than relying completely on network location, you can look into these specific filters. And based on that, you can predict your applications. Right? So this allows our magicians to provide simple, secure access to specific internal resources instead of placing users broadly on the network. The customer examples on this slide show different forms of value. Right? The first one is faster VPN replacement or support for large distributed workforces for delivery hero. And the third one is ability to secure applications across multiple integrations. Right? The the practical message is to start with the defined user group or use case, measure the outcome, and then extend the same access model to additional applications and users. DNS filtering is another practical starting point because it can deliver value without requiring every application to change first. Right? And the good part is it can also be done without having you to install any agents on your laptop. Right? So this is one of the most common use cases that we have seen across, across our customers' conversation. Right? They wanna start with, you know, blocking unnecessary access or unauthorized access to certain websites, that users in any eventually should not have access to. So this is one of the most common use cases we have seen. Right? It provides an early control point for blocking dangerous or inappropriate destinations and applying consistent web predictions across users and locations. Right? The key requirements are straightforward deployment, reliable performance, centralized policy management, global enforcement, and automation, variable required. Right? The examples on this slide show the scale and range of the use case, right, including hybrid workers or predictive DNS and distributed environments such as airline connectivity. Right? You would have you all have would have access to Wi Fi, right, on the Internet on on the two point. So these are some of the use cases for the DNS filtering. Right? So DNS filtering can be a quick win, but it is also more than a stand alone control. Right? It provides visibility into where users are connecting and creates a foundation for expanding into broader zero trust and workspace security use cases. Okay. Let's get into a poll question now before we move on to the next section. So, yeah, please feel free to drop your response in the poll. So security projects, right, are often easy to describe than to execute. So which of these challenges is most relevant to your organizations? Is it defining the migration plan or securing budget or an internal support or, all of these are common concerns. Right? A clear migration plan reduces uncertainty. So please feel free to submit your response. And, there are also additional resources that are available through the webinar platform, and the session will be as Vina mentioned, it will be recorded for later viewing. Okay. I can see responses now. Okay. I can see some responses. So risk of disrupting end users and ongoing operations, that's a very valid challenge. And valid concern, difficulty defining a clear migration plan. Okay. We'll look into that. We have two customer use cases that we want to cover during the webinar, so we'll look into that. Alright. Yeah. Thank you for submitting the response. Let's move on to the next one. So I wanted to share some recommendations with you to get started with. Right? Where do you start? Because it sometimes it gets very confusing for customers to know the starting point. Right? When especially when they're planning this kind of migration work. So let me now move from the reasons for modernization to the practical migration process. Right? A successful engagement starts with discovery, planning, and design. First, clarify the business objectives, timeline, priority use cases, and success metrics. Right? Then understand the existing technical environment, including identities, right, or the devices or the applications that you wanna protect traffic flows, policies, and dependencies. Right? For the initial migration, a lift and shift approach is often the safest part. Right? You don't want to you don't want to segregate the policies in the first place. You just might get that as it is, and then you work or or figure out on fine tuning these security rules or removing certain, you know, obsolete, rulesets or policies. So that comes in the later pass. Right? So for the initial migration, a lift and the shift shift approach is often the safest part. Recreate the functionality that is already working before before introducing too many new capabilities. Right? Once the deployment is stable, the organization can optimize the security pusher and introduce additional policies and controls. When designing the pilot, I recommend focusing on two measures. Right? Time to value and risk reduction. How quickly can the organization get the new capabilities working, and how can it deploy without disrupting users or ongoing operations. Okay. Let's look into some of these recommendations. Right? So I have split that into four categories here, starting from timeline and planning to architecture discovery to migration planning and execution, and finally, the optimization side. Once you're done with the migration and everything, how do you optimize your existing policies? Do you need those policies, on those policies in the first place? Because over the time, you know, there could be lot of obsolete, policies that is not even required in the first place. Right? So that comes in the optimization phase at the end. The most important point on this slide is that migration is a program, not just a product deployment. Right? First, align the teams involved. This usually includes networking, security, identity, endpoint, application owners, or surveyed service desk or your chain management policies. Right? If those teams are not aligned early, technical issues often become organizational blockers later. Right? The next step is architectural discovery. Understand the current applications, identity providers, right, or your device populations or your user groups, right, your traffic flows, your policy exceptions, and dependencies on existing WAN or security infrastructure. For the initial migration, I recommend a one to one lift and ship ship, approach. So recreate the functionality as it as it is that users already depend on before introducing too many new capabilities. So this reduces disruption and gives them and gives the team a stable baseline. Right? Then migrating phases start with a representative pilot that in that could include probably the types of users, devices, applications, and locations you expect to support in production. Right? The two metrics I would use from the beginning are time to value and risk reduction. Time to value, like, how quickly can we get the new capabilities working? Risk reduction means how can we deploy without disrupting users or ongoing operations. Once the deployment is stable, the organizations can introduce more advanced policies, automations, and zero trust controls. Right? So a lot of our customers are leveraging Terraform, to do this deployment because it gets a lot easy for them to have a, you know, backup Terraform available policies available. They can just, you know, work on changing few things, and you can deploy it with these on the Terraform through Terraform policies itself. Right? So you don't have to plus the dashboard at all. So the good part is all the functionalities that you see on the dashboard are available through Terraform policies as well. Right? And if if you want to integrate that with your existing CICD pipeline, you should be able to do that with these. Right? And the final part is enablement. Right? Technically, successful deployment still creates risk if the customer does not know how to operate it after the project ends. Right? So let's make this approach concrete with the customer example. Right? I wanted to, walk you through some of the customer references, right, that you've worked with recently, And we wanted to show you the use cases that we've worked on, the timeline, that we have worked on against which we have designed this whole project. So we'll look into all those aspects to you when we discuss the customer reference. So, yeah, let's move on to the next section. Yeah. So first, I wanted to cover one customer example. So it's a global manufacturer with operations across more than 70 countries, more than 45,000 users and 300 locations. So you can imagine the scale at which we operated for this for this customer. Right? The challenge was not simply replacing one product. Growth and acquisitions had created a complex environment with multiple legacy access and web security controls. Right? As I mentioned earlier, when you get started with these kind of migrations, right, the most important thing is there could be a lot of legacy policies, legacy applications that would not be required. That should not be required ideally. Right? But, yeah, you have to first review your entire setup, understand those applications, and then you can start with the safest one. Right? So that's the approach we recommend to our customers. So what I want you to notice is that the organization did not attempt a single cutover. Right? The first step was planning and architecture design. The team then piloted zero plus access with the defined user population before expanding. Right? So maybe you can start with a user group. Maybe some you can pick, an operations team, or maybe you can pick a developer team to get started with, see what sort of access they need to have, what sort of application they need to access day in and day out, what sort of security controls they need to have. So you can define all of that. You can put that in a single policy, and then you can get started from there. Right? The next phase focused on migrating web security policies and validating full tunnel cut connectivity. Right? Only after the new deployment was stable did the organization begin decommissioning the legacy components. Right? The you can see the slide shows separate work streams for VPN replacement, web security, DNS filtering, and network modernization. Right? So these were sequenced so that each stage could be the could be tested before the next one expanded. Right? So for an organization, with acquisitions, this is a very practical pattern, right, that we have seen. So you can start with a business unit, subsidiary, or define user population where there's a clear owner and a strong technical champion. The goal of the first phase is not to solve every security problem. Right? It is to establish a reliable foundation and prove that the migration can be executed safely. The timeline shown here are also important. Right? So large migrations, as you all know, takes time. Right? But a phased approach allows the organization to create value along the way rather than waiting for the entire program to finish. The key lesson here is that modernization is easier to manage when it is treated as a sequence of controlled decisions, right, rather than one large replacement project. Audience in the okay. So, yeah, if if you are approaching a similar migration, right, which area would you prioritize first? Is it the VPN population, or is it the web security policies or a specific, acquired business unit? So you can feel free to drop a comment in the chat, and then we can transition to the next one. So we'll look into how this whole thing works, right, how you can do this kind of deployment for your own organization. So we'll cover that in the next section. So, yeah, feel free to drop a note. Or if you if you want to highlight any concern that you would have noticed while doing some of these migrations, right, or, if you want to know the kind of approach or phased approach that you should take, we can certainly discuss that. Okay. We'll move on to the next one. This visual shows the distribution of customers' endpoints across Cloudflare data centers. Right? The important point is that the user population is distributed across countries, locations, networks, and working environments. Right? So security policies, therefore, needs to follow the user and remain consistent across the footprint. Now this is also where architecture and user experience comes together. Right? If users are forced through distant hubs, right, or inconsistent security controls, performance and operation complexity becomes problems. Right? A globally distributed model like CloudHealthcare helps provide a more consistent access path and a more consistent security posture. During the architecture discovery, I would map three things carefully. Right? The first one is where users and endpoints are located. The second is which applications and networks they need to reach. And the third one would be where traffic currently enters the security architecture. So that mapping helps identify hairpinning or inconsistency policy enforcement. Right? Legacy dependencies and the locations that should be included in the pilot. The goal is not simply to move traffic to a different location. The goal is to create a consistent policy model that works for users wherever they are. Okay. Let's move on to the next one. I quickly wanted to touch base upon the next customer reference. So that's a leading hotel brand. It's a global hospitality organization with thousands of properties and highly distributed workforce and contractual population. Right? The organization was consolidating remote access and web security across 20,000 users and 38 contractor organizations. So you can imagine the scale, right, and the complexities that was involved in this migration project. The important point is that the project started small, right, as as we covered in the previous sections as well. We don't have to do full fledged migration from day one. Right? So you can plan it in phases. The team begin with the solution design, then a pilot for approximately 20,000 users. So what we did is instead of focusing on the whole of 20,000 users, we started with 2,000 users in the first place. Right? 20% of the overall users that we had. So followed by a broader rollout rollout. Right? That sequencing gave the organization a way to test the user experiences, integrations, and operational model before expanding globally. The product also shows why pilot should include realistic conditions, right, and not just focus on POC or certain test cases. Right? So hospitality's users and contractors may connect from hotels, airports, airplanes, and other environments where captive portals or device posture and connectivity conditions can vary. Right? Now this this is where the whole design gets a little tricky. A pilot should therefore test more than the standard office scenario. It should include the edge cases, right, that could create disruption during production rollout. The overall project progressed over up approximately fourteen months, and the legacy access and web security components were retired only after the replacement capabilities had been validated end to end. So the lesson that we learned from this customer migration is that starting small does not mean thinking small. Right? A well designed pilot can become the foundation for a large scale deployment like this. So this is what we've learned, from this customer migration. Right? Okay. No. I quickly wanted to touch base upon the best practices. Right? We looked into the recommendations earlier, and now I want to tell you, like, some of the best practices that we need need to keep in mind, especially when when we are architecting this kind of migration. Right? Or when we are thinking of, replacing our existing secure solution style. Right? Deployment can be technically successful and still struggle if the organization does not establish the right operating model. Right? There are usually three stages of operational maturity that we've seen. The first is manual operation, where teams manage policies and changes directly through the dashboard. The second is semi automated operation where teams use APIs or scripts for repeatable tasks, or it could be a Terrahome script also, such as importing indicators of compromise or integrating with other security systems. Right? The third is a more fully automated model using Terraform and CICD. Right? This can improve chain management, auditing, and repeatability repeatability. Right? And that's the trend we have been seeing across the industry. The operating model also needs to reflect the organization security requirements. Right? So, like, some applications may use application based access policies, while other environments may require broader segmentation or different transition patterns from the legacy VPN model. The organization model matters just as much as the technical model. Right? Networking or IT teams may manage connectors and connectivity, while security teams may manage access and gateway policies. Endpoint teams may manage client deployment and device pusher. So the best approach is to define these roles early rather than allowing responsibilities to remain unclear. A project manager or maybe a professional services can also help coordinate priorities between teams and keep the different work streams moving together. So finally, the professional services should transition the customer to steady state with the right documentation and enablement. That is equally important. Right? We don't want to leave behind any technical debt for for the teams. So that includes high level design documents as build configuration records, or it could be Terraform code or templates. It could be API scripts or workshops, knowledge transfer, and any sort of troubleshooting guides that you would have created during the migration journey. Customers should not remain dependent on the implementation team. That is, again, very important. Right? The goal is to leave them with the knowledge and tools to operate and expand the platform independently. So with that operating foundation in place, organizations can continue expanding the SaaS journey. So, yeah, if if you are planning a similar journey or if if you have, encountered any any hiccups during the migration, just just let us know, and we can help you start, with this journey together. And we can help you with the right process and approach that that we recommend to our customers, especially when they're planning to monetize their SaaS journey or, they want to replace their existing or security stack that that they would have with their organization. Okay. So today, we primarily focused on modernizing remote access and DNS filtering. But what does the but, the road beyond that looks I mean, beyond that, we want to cover few more use cases. Right? So longer term, we see and recommend customers follow a journey like, this. Right? So across three phases and individual steps, you can see the details here. The top row in white are steps focused on consolidating infrastructure and tooling. And the bottom row in orange, so our steps focused on restoring visibility and controls across users, devices, and applications. Right? Each phase incorporates one of the use cases we discovered earlier, right, just on a wider scale and time horizon. So the phase one that is modernizing remote access by adopting zero trust network access, We talked about this a lot today. And in phase two, we looked into modernizing workspace security with a unified platform. So deploying DNS filtering is one part of this, but here we see our mentions go even further. For example, they want to deploy email security, right, or enforce AI usage controls and guardrails. That that's the hot topic that we've been seeing across all car customers' conversation of late. Right? And phase three is modernizing networking and security for single vendor SaaS. Right? This includes, adopting coffee shop networking to simplify end user experiences and produce hardware. Right? Within each phase, organizations progressively extend more granular visibility and controls across more environments. So that's what we have been seeing. So, yeah, we have split that into multiple phases. So in phase phase one, ideally, you should start with, modernizing your infrastructure and, the DNS filtering use cases, and then you can go on beyond that with phase two and phase three. Right? So with that, I wanted to wrap up this session and move on towards the end of this, session. So, yeah, ultimately, the exact order of operations is up to you. Right? With our breadth of our with the breadth of our portfolio, right, CloudFlare is in a unique position that customers choose us to start a variety of different modernization product projects. Right? If you want to go deeper, we recommend our SaaSy reference architecture that has also shared in the chat. So this includes technical steps and best practices as you progress towards the zero zero trust journey. Right? Or you can also talk to our team about many of the different ways to get started, including architecture workshops. If you're interested in that, we can certainly do that discussion. Or if you want to do a test, right, if you wanna do a test, right, workshop, so we give you a lab setup wherein you can you we can work with you, and we can help you onboard your users or maybe if you want to test on certain application access. And we have a lot of use cases covered through these test drive workshops that we plan regularly. So you can probably attend the next one, and we can walk you through the overall use cases and the lab setups. Right? Or if you want to do a POC trial, we can certainly do that. So it's all about the order requirements and the use cases that you wanna cover. Right? So, yeah, thank you so much for tuning in, and we really appreciate your attention. Right? So with this, I'll let's move on to the q and a. And if you have any questions, please feel free to drop that in the chat, and I can take it over from there. So, yeah, Gautam says, can we have the recording of the session? Yes, Gautam. Certainly, we'll be sharing the recording with with all the attendees shortly in the next forty eight hours. We'll share the links also. Yep. We can certainly do that. Can you define the Kunal says, can you define the free part of the trial? How many users are for how long, which features, etcetera? So so, Kunal, you can certainly do that. So by default, you'll get 50 free seats, with zero trust plan. So if you want to test certain use cases, you can certainly try that out, or you can drop us a note, and we'll be more than happy to have a discussion with you and understand your use cases so that we can assist you in the best manner possible. Very interesting. Airline, Kunal also says that it's an interesting airline use case with Starling any publicly available information on this. Sure, Kunal. Let me see, what information we can share, and then we can get back to you on this. So we certainly have lot more details around those use cases. So, yeah, we'll share with you the details. Do mainline China have data center and backbone network connectivity to other country globally? Yeah. Yeah. Yeah. Certainly. We can work on that. So we do have quite a few customers who have this similar use case, so we can certainly address that. So, yeah, we we we'll get in touch with you, and we can we'll share the solutions that we have for that. So even if you have a user's email in China and they want to have a global connectivity, we can certainly do that. And, yeah, thanks, Dene, for sharing my details. So if you have any questions, I'll be more than happy to assist you after the session also, during the late after this webinar. So please feel free to drop a note here. Okay. There are a few more questions coming in. Just allow me a minute. Let me quickly check that. Where does end user traffic terminate in the same screen? Sitting at the same screen. Sitting at the used here. Yeah. That's right, Tony. So we use the same global network. So that's the beauty of our network. Right? So every services that we have runs across every data centers, every service across our platform. Right? So if you have users accessing trying to access, the application from, let's say, Singapore or from a location in EMEA, they they'll get connected to the nearest colo of CloudHealth within the same region. Can we also select the data center, or is it it's it's an anycast network, Tony, but if you want to have any dedicated egress IP, so we can certainly do that. So we can provision a static IP for for certain use cases. Let's say if you want the traffic to egress from certain set of static IPs, we can do that. We can provision that for you. So that's that's there's an add on solution for that. So you can certainly control that. Oh, okay. Anna says for zedDNA use case, if I have non web protocol servers such as RDP, FTP, Can Cloudflare help verify these protocols? So I need to so I did not install my own converter like go Gokomole. Right? So for RDP, yes, Cloudflare access supports browser based RDP, so users do not need an RDP client. Right? So you run Cloudflare d. That's a connector that we use on the RDP server or nearby host and publish it through Cloudflare tunnel, right, and predict it with access policies. So your users connect to a browser and still authenticate with their Windows credentials. Right? For FTP, not in the same way, I would say. Cloudflare can secure FTP as a non HTTP TCP application, but it does not natively convert FTP into a browser browser based, interface. You would still need an FTP client for that. Okay. Let me take few more questions. And Okay. Just bear with me, team. I'm going through the questions at the moment. Okay. I can see Kelvin's query. How does CloudHealth optimize performance for maritime applications such as ERP, cargo tracking, and vessel management systems? Do you have same use case for shipping or logistics? So, yes, the same architecture applies to shipping and logistics as well. So CloudFlare can connect vessels, ports, offices, and cloud environments through CloudFlare WAN, while Zero Trust provides control access to ERP, cargo tracking, and vessel management systems. Right? So DNS and web filtering prod predict crew and operational users while, our performance feature like Argo Smartplotting can improve performance for public web applications and APIs. So CloudFlare cannot remove the inherent latency or bandwidth limits of satellite connectivity, but it can avoid unnecessary back black back hauling to a central data center and provide consistent security and visibility across the maritime environment. So, yeah, that that was a good question, Kelvin. Thanks for bringing that up. Yeah. So we still have some time, Teams, so please feel free to drop a note if you have any questions. And, yeah, even after the webinar, you can just let us know, and we'll be more than happy to cover that. Hey, Abhishek. I see there are, two more questions in the q and a. So if you go on the left panel and click the q and a icon, you will see the questions I've highlighted are still unanswered. Okay. Just a minute. Let me quickly check that. Yeah. Thanks. Thanks. Thanks, Pune, for sharing. Let me quickly check that. Oh, okay. The base is how to have POC. So the base, yeah, we can certainly do that. So you can just drop me a note, and I'll connect you with the with the team, and we can get started with the POC. Right? So we want to first understand your use cases, like, as in how many users you have, what are the features you want to test out. So we can do all of that, or or you we can probably invite you to our test drive workshops that we do frequently. So wherein you can have a lab setup ready, and we'll walk you through all the use cases so we can discuss more about your specific use cases that you would like us to cover during this workshop. For customers located in Thailand okay. Campbell says for customers located in Thailand, do users currently connect to the Singapore gateway or pop? So, Kamal, yeah, we we have our edge pops in most of the regions. Right? So even for Thailand, we do have a pop there. So most likely, it will get connected to one of the pops in Thailand that we have. Right? So if in case there are some network issues or latencies, then it might get routed to the nearby pops like Singapore or Malaysia. But in most of the cases, it should get mapped to one of the pops in within the same region as Thailand. Okay. I see one more question here. Can we select from Tony? I think can we select the data center or okay. I think I covered that. But, yeah, by default, it is anycastoni. So traffic is sent to the CloudTrail location selected by Internet routing. Generally, the closest or the best performing location is served to an end user. Right? So we can still influence routing inside CloudFlare using band traffic steering, right, or regional controls or specific on prem solution. But we typically do not pin users to one individual edge data center against because of, again, because of resiliency reasons. Right? Okay. So please provide the dashboard link registration. Yep. I think link registration. So I think Vina has shared that in the chat, so that's done. Okay. Alright. Outlaw can help to secure. Okay. I see one more question from Saurabh. How CloudFlare help to secure email? Yeah. We do have an email security solution, Saurabh. Right? So if you could elaborate more, like, it depends, like, what you're using. Right? Is are you using Microsoft three sixty five or using Google Workspace? What sort of security solution you're using? We certainly provide email security solutions both, in in different ways. So if if you let's say, if you want to have if you want your existing emails, solution as it is and you want Procter to act as an add on, we can do that. So Procter emails security protects email before it even reaches the inbox. Right? So it can detect phishing, malware, spam, DC sort of an attack. Right? Business email compromise and vendor email compromise using context analysis, right, and threat intelligence on attacker infrastructure. So it can be deployed as I mentioned. Right? It can be deployed both in line, by changing the MX record, or we we can integrate that with your existing Microsoft three sixty five or Google Workspace through APIs. Right? So for Microsoft three sixty five, CloudFlare can also apply outbound DLP policies, right, to warn users or block sensitive emails before they are sent. So, yep, we we can do we can do that. And, yeah, if if you need more details around that, Saurabh, so we can have a discussion around that, you can just drop me a note and the use case that you want to test out, and we'll take it forward from there. Okay. Yeah. So it can be done. Alright. Any more questions, team? Okay. Alright. Thank you so much. Thank you everyone for your time. Really appreciate it. Yeah. As been as mentioned earlier, so you have my email ID. If you want to explore any more use cases with us, you can certainly drop me an email, and I'll take it forward from there. If you want to do a POC or if you what we can do is you can also sign up for our next test drive workshop. If you want to do a hands on session with us with our specialists, we can do that as well. So thank you again for your time. Yeah. Over to you, Vinay. Hey, Abhishek. Yep. Thank you. Thank you. Thank you, Abhishek, for hosting this insightful session. I'm sure all the attendees enjoyed this webinar as much as I did. Lots of interesting question, lots of interesting, comments, to share with you. 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 all found today's session relevant and valuable. We look forward to seeing you at our upcoming webinars. If you have any further questions, please drop them in the q and a box. And you also have Abhishek's, email ID so he can take them right away. Thank you all. Have a good day. Bye. Yep. Thank you, everyone. Bye.