Video: Assessing your API Risk | Duration: 2528s | Summary: Assessing your API Risk | Chapters: Welcome & Introduction (8.72s), Session Agenda Overview (145.46s), Understanding REST APIs (290.785s), API Security Landscape (473.26s), API Security Infrastructure (607.875s), API Shield Capabilities (749.045s), API Discovery & Labeling (868.27s), API Schema Validation (1054.255s), Authentication Methods (1313.005s), Security Posture Management (1471.51s), Q&A and Closing (1762.435s), Q&A Session (1868.35s), Closing Remarks (2374.23s), Closing Remarks (2473.11s)
Transcript for "Assessing your API Risk": Hello, everyone, and welcome to today's webinar. My name is Vinay, and I will be helping support today's live session. We are excited to have you all join us. In this exclusive session, our expert speaker will explore how to fortify your API ecosystem, powering innovation without compromising resilience. But before we begin the webinar, a little bit of housekeeping. On the top right corner of your screen, we will see the live chat option that you can use to interact with your fellow attendees. In the doc section that is located next to the live chat, we have attached, API guided tour link and two ebooks on API security. On the extreme right, you will also find the q and a box. We encourage all of you to leave your questions in that q and a box as we progress through this webinar. We'll make sure to address all the questions towards the end of this presentation. A quick reminder, this session is being recorded, and we will share the recording with all of you within forty eight hours. Now please join me in welcoming today's speaker, Michael Snowden, senior solutions engineer at Cloudflare. Hey. How's it going? Thanks for the introduction, Vinay. My name is Mike Snowden. I'm one of the solutions engineers based over here in Sydney. As you can probably tell by by accent, I sound very Australian. That's because I come from the very Australian city originally of Washington DC, but I moved over from there over to here, back in around 2019. And, well, yeah, here I am. So, give me one second here. Let me start sharing my screen, and let's just get on with it. You know? So, you know, just, just, I guess, maybe a few more housekeeping housekeeping items. You know, nothing too crazy. Again, you know, as Renee said, session is being recorded. If you got any questions, drop them in the q and a box. Closed captionings, they will be made available a little bit later on. And if you have any other technical questions, you know, just, again, drop them to the q and a, or go here to gold Goldcast for help in case you have some coworkers that are just having difficulty difficulty trying to view the stream. Now, yeah, let's start talking about APIs, risk, and, you know, API shield. This is gonna be the agenda for today. You know, I'm just gonna just take a a brief moment to kinda talk about what APIs are. I do understand that, you know, not everybody that's joining today's session is a technical person, but I am hoping that, you know, my very quick one to two minute explanation can hopefully shed a little bit of light on, you know, what the stuff is. We'll talk about the current landscape of APIs and the API security. We'll talk about API Shield and, API Shield capabilities. I'll give you a quick walk through of the product. I had originally planned on trying to do kind of a live demonstration today, but, like, just due to work pressures and scheduling, things like that, yeah, my my lab environment was just not able to get set up in time for today's session. But I am still able to walk you through the, through the product. And then finally, we'll talk about, you know, an API risk assessment offer, that, you know, we can make it that we can make available for you. So this way, if you're kind of lost on what to do, just know, you know, over here at CloudFlare, you know, we're we're not jerks about things. You can come to us and ask for help, and we can help, help you with, some kind of, you know, basic API assessment. Now, I do understand that, you know, today, we do, we do have it on the schedule that we're gonna be here for an hour. But, realistically, I think an hour for any kind of webinar is way too long. I am gonna try and condense all of this so this way we can hopefully have half of that amount amount of time. So this way you can take this information, do something useful with it, and probably most importantly, just kinda go live your life because lord knows you got better things to do than just stare at your computer screen all day. Now let's get into what APIs are. Just kinda quick, just by quick, round of, you know, hands or messages in in in the chat here very quick. It's okay. Don't be shy. How many of you in the chat right now feel like you're relatively comfortable with what APIs are? Or do you feel like maybe you you kinda know what they are? You know, you you work with them, but, you know, it's just one of those more nebulous things. Yeah. Okay. I wanna assume thumbs up means you understand what they are. But for those who are a little bit shy, this is just kind of a quick this is my quick layman's explanation for what an API is. Now APIs can take on many different shapes, forms, and sizes. It can be written APIs can be written in so many different languages. There's so many different modes in which you can communicate with APIs. But at least with CloudFlare and for today's discussion with eight with, API Shield, the types of the APIs that we're generally talking about are things called rest APIs. And if you have no idea what an API is, I got a quick little explanation right down here. API is for application programming interface, and it's basically something that that exists that allows two programs, two applications to be able to talk to each other. If you go online, you do a quick Google search, or you ask AI, you'll hear a lot of these explanations, you know, being explained to the terms of, like, a formalized contract, you know, public interfaces versus private interfaces. But the way that I like to kind of explain to, to people, you know, what an API is, like, specifically a REST API, is maybe just through a very quick simple example. So just imagine this. Imagine that you're on a web page. You need to go through and you need to register a new user account on some website. Doesn't really matter. It could be a new Gmail account. It could be a new account, at your, you know, at, at your at your local bank. Doesn't really matter. If you go to their website and you try to register for account, most websites will follow this pattern, which is when you go when you go to the website, your client, AKA the web browser, will navigate to, you know, the home page for that website, and the application is basically the web page that gets loaded up inside of your browser. When you try to register for a new account, your browser will basically and I'm not joking here. It'll quite literally submit an HTTP request, you know, the same type of request that your browser normally sends when you click on links and you try to navigate to different web pages. Except in this case, this HTTP request that gets sent out is is highly structured. It's a little bit special, and it basically contains, some additional JSON data in it. So this way, the server that receives the HTTP request knows what your intent is, which in this case is to register for a new user account. After the after the server has processed the request, it sends an API response back, which basically is just JSON data with a little bit of a status code in there that says, hey. Your registration was successful. Now this is just one example of an API that, that can be called, but you have APIs that can basically do anything under the sun depending on how you've programmed it. You can have APIs that just simply help you with retrieving information, like maybe weather and forecast data or analytics data. And you also have other types of APIs that helps you with, you know, performing actions on whatever target web application that you're interacting with. So the world of APIs is wide and varied, which is the reason why, you know, we're talking about APIs so much in this in this day and age. The reason being is because right now, there's been an explosion of APIs. You know? Ever since, you know, AI came onto the scene, we already knew that we had a problem with APIs in the industry where, you know, developers weren't doing a very good job documenting the APIs that they were developing. So then we had a shadow API problem. But But within the past couple of years, that those issues have exploded by by over four times because we have a lot of AI generated code that's creating undocumented APIs. And now the security landscape is also pretty uneven, you know, because we have a combination of human coded and AI coded, API endpoints. We have no real strong guarantees that, you know, input is being validated. We have no idea whether our security controls are being implemented on those endpoints. And then, also, this represents a consolidated risk, again, mainly due to the involvement of AI in the software development space. So, this next part right here, this is just meant to kinda give you kind of a, like, a like, a quick high level snapshot of, like, I think probably the top three things to be aware of when it comes to, you know, API abuse, API security. And I understand it says 2025 here. Bear with me. This information is still relevant today. Specifically, you have issues like denial of service. You also have account, account takeover problems where you basically have, you know, automated attack tools, trying to perform, you know, account account stuffing attacks and credential guessing. And, also, you have forms and analytics for the things that your business relies on order to make informed business decisions. Ascent essentially overnight becoming very muddy because, again, a a AI is on the scenes. You have a lot of AI powered, attack tools now these days, scraping websites, stuffing forms with with fake and bogus data, which is just polluting polluting the analytics data that your businesses rely on. So, how much, you know, how much operational infrastructure relies on APIs? That's the other thing that, you know, often kinda gets overlooked. It's, you know, it's often the case that, you know, some people are thinking like, okay. You wanna know what? I've just got, like, maybe a fun little blog here. You know? But, like, I think people really underestimate just how pervasive web service APIs are now in this day and age. Like, you really can't run a modern web application without it, which is the reason why things like Cloudflare and API Shield are so important. The reason being is because we can insert ourselves as a proxy layer in between the clients and your origin servers such that every single request that comes in goes through goes through CloudFlare, where we can try and help you with doing things like discovering shadow APIs, performing posh posture management, determining whether or not you have adequate security controls and protections on your APIs. And when you are lacking, we can help to bolt on and add on, an additional layer of security that you didn't have previously. Things, by introducing things like schema validation, JWT validation, and other things. And then finally, it's not just enough to validate the requests that are coming from the clients to your API servers, but it's equally as important that we validate the responses that are coming from your API servers from origin back to client. The reason being is because sometimes those responses could potentially contain a sensitive piece of information that you really don't wanna have it being disclosed. And over here, you know, this is just another quick diagram here just to kind of real just to really give you an idea here of what it is that we're really doing here. We're because we're really inspecting and scrutinizing every single request. So this way, we can help you with situations like bad actors doing bad things, good users doing good things and allowing that traffic through, or even something a little bit more nuanced where, you know, you have legitimate users that are, doing something incorrectly, and you just wanna make sure that certain business logic with your with your application is being followed. So this way, we don't have unexpected runtime errors or potentially, having issues that cause our analytics data become more polluted. So let's talk about, API Shield's capabilities. This slide right here, there's gonna be a lot of text. There's gonna be a lot of things that I'm gonna throw up onto here. But generally speaking, the API Shield capabilities, that are offered from CloudFlare generally fall into, like, one of three buckets. Okay? So we'll have capabilities that help you with discovering and managing your APIs. We have capabilities that help you with runtime protection and finally posture management. I'm just gonna stop here for a brief moment because this is actually a very useful, this is gonna be a very useful slide here for a lot of you that are viewing the stream right now. I'm just gonna pause for a moment, and I would recommend that you take a quick little screenshot of this particular slide right now. So this way, if you have, if you have, you know, any questions a little bit later on with, you know, what any of these capabilities are or you want to you didn't know about one of these capabilities, which is most likely this situation, this will just be a quick and easy to go to cheat sheet to to know and reference very quick what is that API shield can do for you in terms of security. Okay. Now so, I'm gonna assume that everybody has taken a, taken the screenshot right now at this point. So let's get into actually going through and doing a quick product walk through. Okay? Again, I wanna apologize to those in the audience. I had originally planned for a bit of a live demo. That would have been really fun, but it just wasn't in the cards today. So what I have for you are basically kind of a a series of quick, snapshots from our from the from the CloudFlare dashboard, where we have API shield situated just to give you a a real good taste of what it is that you can expect to see when you start trying to protect your web service APIs with Cloudflare. Now, this is essentially one one of the first things that you will see when you come o when you come over into Cloudflare. If you have onboarded your zone into Cloudflare and we're you've turned on cloud you've you've gone, orange cloud on on your zone, and we're providing things like, web app you know, web application firewall security, rate limiting, and other things like that. You'll also have, access to API Shield and its, API discovery capabilities. So this is something where once you let, once you let your zone run on CloudFlare, run through CloudFlare for a certain period of time, API Shield is able to detect and take note of all the web service API endpoints, the API URLs, that are being invoked. And then from there, you know, we're able to help you I'm hoping, at least, we'll help you discover APIs that you didn't know about. Okay? There you go. And, when it comes to, when when it comes to, after the discovery, we then give you the capability of adding, add adding, some tags to those API endpoints. So this way, you can manage them and start creating rules around what you want to happen with those API endpoints. The way that works is, generally speaking, that you work on labels. Now we have Cloudflare provided labels, which we, that we have, as part of the platform, and that will automatically apply to various API endpoints provided that certain conditions are met. But you, as a customer, you also have the capability of creating your own labels, which is a really powerful feature. And the reason for that is because when you go through and, eventually start creating your own custom rules for how you want CloudFlare to be handling the security of various API endpoints. Being able to apply those rules based on based on the labels is probably gonna be the easy easiest thing that you can do. So I guess as an example here, you know, if you have a class of APIs that are all related to user account management, you can apply a, you know, a user, a a user, user data user data tag to all of those related related API endpoints. So this way, you can maybe require, you know, additional JWT token validation or certain kinds of, you know, rate limiting where, you know, those APIs can only be called an x number of times over over, over over a certain time frame or anything else that you want. Plus on top of that, if you start trying to, export, export, information out from CloudFlare using our publicly accessible web service APIs for your own analytics purposes, the labels provide a really powerful attribute that you can generate dashboards and analytics from as well. And for, you know, dashboarding, we provide a rich set of dashboards. This is basically kinda what you're seeing here. You'll be able to see things if you take a look at the, graph on the left, things like, you know, authentication, error rates, the number of requests that have come in, and also error rates as well. So, you know, if we're getting, you know, 400, 500, error status codes from, you know, from origin back over the client, you'll be able to get a near real time visibility into all that data. When it comes to trying to make sure that we're providing proper input validation, if you have not done that properly, server side, such as, you know, just making sure that if you're if, you know, you're accepting updates to a user's profile information. Alright? And if you give the capability for a user to change their age, then you probably wanna make sure that, you know, the data that you're getting back for that one specific little field is, in fact, a number, a digit, you know, rather than a string of characters. So with schema validation, what you can do here is this. You can basically provide to CloudFlare the a p API definition file. Usually, for most people, they'll have something like a swagger definition file or an open API spec file of some kind. Typically, these are either typically, these are in JSON and sometimes YAML format as well. So if you have that, awesome. But if not, that's that's that's totally fine. There's other things that we that we can do to help you out. But if you have that schema file, all you need to do is click on the schema settings. And then from over there, you'll be able to upload your, schema files in into Cloudflare. And then after you do that, you're basically telling Cloudflare ahead of time, hey. These are all of the a p these are all the APIs that should exist, Cloudflare. And for each one of these APIs, they accept a certain number of they accept a certain set of parameters, and each of these parameters is a specific data type here. I would like for you to help enforce that. So if at any point there is a client request where the where the data being passed through that API doesn't match that shape correctly, we can do one of a couple things. You know, we can block the request. We can allow it to go through anyways, or we can allow it to go through, with with logging. Okay? Another really powerful capability that we have with Cloudflare is also something called sequence analysis. Okay? So let's just say that, you know, there, that there is a certain, you know, sequence of operations that you ex that you expect to be happening. Okay? Sequence analysis allows allows you to to go in and see what are the most popular sequences that Cloudflare has taken notice of. So on any one so on the sequence analysis, tab of API Shield, you can see essentially, you know, the top, you know, the top 40. I think it's yeah. It's actually still top 40 now at this point. The of the most commonly seen sequences that CloudFlare is taking notice of, You'll see the starting URL path. And once you've clicked on any one of these, API endpoints here, we'll show you, some additional metadata such as what other API endpoints end up getting called, in sequence after that initial API call. We'll provide you with a correlation score. We'll tell you when it's last observed, how many endpoints are involved, you know, a bunch of really useful things. And this is this is a really, really powerful auditing tool for a lot of security organizations just to make sure that, you know, nothing really weird is happening. And when it comes to sequence mitigation, this is something I kinda mentioned a little bit earlier on. But if you're noticing that a certain sequence of API calls is not being followed, again, you know, we can help with with enforcing that. So this way, if things happen out of order, we can block it, we can log it, or we can allow it to go through. And, you know, all this is just kinda built into the dashboard. Now, after that, we can also, help you out with, situations where, again, if you didn't bolt on this type of security ahead of time, that's fine. If you need for Cloudflare to help you with authentication, okay, we do have support for adding on mutual, mutual TLS based authentication to your API after the fact in case you didn't, build this out in your in your in your origin ahead of time. K? So nothing really too fancy or mystical to say here. Basically, you know, you provide us, you provide we help you with, you know, create creating a certificate. Then after that, you can, you can oops. Sorry. You can you can trust that certificate on both sides, and then bada bing bada boom. You'll have a situation where every single, every single HTTP request that's coming in now from trusted clients is going is going through a, is going through an SSL connection that's been validated and authenticated using mTLS. And, for situations where, again, you're you're you're you're deal you're dealing with many many, many clients. This is something that's that's very popular, you know, with, with, you know, with multi tier web applications. So where you have your database back end, you have an API API layer, and then you have a independent client front end. Clients submitting JWTs for performing eight, API requests directly from, you know, a web page basically is very popular. And if you just want to make sure that, CloudFlare is also validating and performing the JWT token validation at the edge, so this way you can save a little bit of on compute resources down at the origin, we can do that as well. Typically, all you would really need to do is just to, you know, provide for us, you know, the public key the public key search for your, for for your origin. So this way so this way we're able to sorry. The private key, actually, for the downstream origin. So this way, we are able to, decode you know, decrypt the JWTs that are coming in for the validation process to complete successfully. Alright. And, you know, like with everything else in CloudFlare, everything is logged. You have access to logs. Alright. So, let's talk about security posture management here next. Okay? So with the posture management, all of this is powered using CloudFlare's, you know, industry leading dashboard capabilities and and analytics. So what I mean by that here is this. If you have a CloudFlare account, if you're going through and you you're proxying all of your client traffic client user traffic through CloudFlare, this is gonna look very, very familiar, and it's gonna make a lot of sense. Long story short, posture manage posture management to me, it means, Lisa, I'm getting live near real time data and analytics and feedback into the user into user and client traffic that is passing, through CloudFlare and ultimately down to my origin. So this way, I can make informed decisions as to what I need to be doing at that exact moment. The vast majority of times for most of you, that's it's there's gonna be a lot of nothing that you're doing. But you can think of Cloudflare as being that insurance policy that that you pulled out ahead of time, where you put us at the front door for all that traffic. So this way, when there are things like DDoS attacks, when there are, SQL injection vulnerabilities, being being launched against your website, CloudFlare is there at the at the very edge to block that type of traffic before, before it ever hits your origin. And if in the unlikely event, things are still getting through. Having the, you know, having to analyze that live analytics data on hand in real time, gives you the capability of making informed decisions for what you might wanna do, which for a lot of our customers is you is usually, you know, creating new new rules on the fly to, to address real time threats. Now, some other things that we can do here is, you know, again, this is still related to to posture management, but we can check this as we're watching and monitoring the client traffic, that is, that's coming through CloudFlare. We can take, take note of what type of we can take note of what type of authentication, is, is being leveraged here. So, you know, if we're seeing that, you know, you're you're having open authentication or you're not using certain authentication headers, we'll let you know about that. If we see that there is sensitive data being returned by the origin down to the client, things like credit card numbers, maybe patient health care information, things along those lines, again, will alert you. We'll even tag the API endpoints that we've, taken note of that is divulging that information. Something else that's still a really, really hot topic today, and I'm I'm surprised that this is still still an issue, is broken object level authorization. You know? And long long story short, this is kind of the way this is a simplified example for, how I explain, bolas to customers. You know, imagine you are running a photo like like a photography business or something else like that. Okay? And with your photography business, you know, you do online previews for, you know, for the pictures that, you know, that you've taken for your clients. And, you know, you've got clients that have, you know, paid for, you know, some of their photos, but not for everything. But once but you have a problem with your website, which is once you have an authenticated user on the website and they're looking through their photos, you forgot to secure you forgot to secure the, the URL path that goes back to the Amazon s three bucket where you're actually holding all of the unwatermarked photos, the high definition stuff, regardless of whether or not, you know, the customers have paid for some of those photos or not. Alright? So being able to access URLs and paths on a target website or web application without proper authorization is basically what BOLA is. And, again, you know, this is still a problem that we have today, and, you know, in in some cases, it can be forgiven. So, again, during our analysis, we'll take we'll we'll we leverage a heavy amount of AI machine learning here to help us with this analysis, that we ultimately present back down to you. And when we do see stuff, again, we flag things, we label things appropriately. So this way, you you can take appropriate actions. Alright. So that is, the kind of end of the walk through, and we are coming up to three twenty nine now at this point. I do really wanna stress here just, like, what it is that we're really dealing with. There are a ton of APIs out there in the there are a ton of APIs out there right now, more than what people can really imagine or or comprehend. Right now, it's just web service APIs. Going forward, in the future, we'll see more and more, MCP servers. Those aren't web service APIs, but they they are still APIs nonetheless, for your AI for your AI agents. And we really need to be doing a better job in the industry of, you know, being able to of having better security controls, visibility, and posture management over these types of things. So, if you need help with any of these types of things, if you need some advice, if you need, you know, if you need stronger assurances, our doors are always open for everybody here that's, on on the call right now. So I guess with that, again, just thank you very much. Here's a quick, QR code where you can, you know, come over to us, get a free API set free API risk assessment. We can help you with, you know, discovery with, trying to rate the risks and help to create an action plan over what to do about those, insecure shadow APIs or and anything else in between. So with that, I do wanna open up the floor right now for a bit of q and a, and I apologize if there have been questions being dropped. I haven't been monitoring. But, what I'll I'll just start from the top working my way down. So the first question is coming from, from mister Winston. What it what's a shadow API? And you said it's an API running without without you knowing. And you are correct. That is exactly what it is. No more, no less. It's basically an API that's running that is not documented, that's not accounted for. No more, no less. Are there any other questions on the chat? So I do have I do I do have a bit of a question here for some of the people on the chat, and I I do wanna get a little bit involvement here. How many how many of you are concerned about, API security in the context of the MCP servers or API security in the context of, you know, your existing, you know, restful web service APIs? Do you know just, you know, put your vote in the chat just by saying, like, either MCP or or a rest, r e s t, just to let me know where your concern is. And while I'm waiting for some responses in chat, let's see here. I have one question that came in. Is it possible to implement with Cloudflare business plan? Short answer, yes. It is possible. Another question that came in says, mobile API, mobile apps and APIs. So I'm gonna assume here your question is whether or not CloudFlare can provide API security for the APIs that mobile applications use. If that is your question, then the answer is yes. The reason being is because the vast majority of mobile apps that are running on your phone, iOS and Android, when they do communicate with some back end service, it is typically these days, either gonna be REST or GraphQL, API endpoints. Less so with GraphQL. Graph is kind of fading in popularity, but, you know, REST APIs are still very, very heavy in popularity. And I do I am noticing an an increase in the number of mobile apps that are actually using gRPC as well. Yeah. Can I use endpoint management as a gateway, for my internal apps? Consider I have 15 services. Usually, I have an in house gateway. Can I replace that with this? How should the routing be managed? Okay. So I wanna I wanna say if you are talking about the if you're if you're talking about 15 services for things that are running inside for, like, you know, like, an, like, an internal API that's kind of used with with within an office, and these are not publicly accessible to the Internet, you I would say API Shield is actually probably a bad fit for this for for that particular use case. Okay? But if these internal services are publicly exposed, alright, it it it meaning, you can access these services over the public Internet. Okay? Generally speaking, what you would do is, you would you would update your, you would need to have, like, some kind of domain, assigned to the public IP address of your gateway. Okay? And then then then from there, you can basically onboard that zone, that domain name into Cloudflare. So this way, all the all the eight, HTTP requests going to your API that's to your API that's sitting behind that domain name is going through CloudFlare, and you can, you know, get the benefit of, you know, all of the security stuff that I've been talking about today. You know, things like, you know, API shield, even our advanced rate limiting and our web application firewall as well. If you have if you have internal app if you have internal apps that you want to make publicly available, but you you you don't have the ability to modify your gateway to, you know, kind of to do the, you know, to do the port forwarding and things like that. We do have another, we do have another thing, available. It's kind of a product that you can use with CloudFlare called CloudFlare d, and I'll just drop that into the chat. Alright. Using this, you can basically create a reverse tunnel from your internal network out to Cloudflare as a way of exposing those internal services without having to do any modification on your gateway. K. Alright. And last question is what shadow API okay. Yeah. And I've already answered the shadow API question. Okay. So, I'm just gonna give it another moment here in case there are any other questions. There was literally no feedback from anybody on which type of, you know, API security that you're that you're really most concerned about here, but that's okay. I know that there's a silent majority amongst you. Now, at this point right now, I think I am going to wrap up the session. If there are let's see here. One second here. I think I am going to wrap up the session. I don't see any other questions coming in either. Oh, you asked another question. Okay. Let's see here. Okay. So, you are using CloudFlare zero trust access, service keys with a mobile app to access API protected by zero trust. Is it recommended, or is there a better alternative? Let me read let me read your question again. I'm gonna say, Siva, it it it depends on your it depends on what your goals are. So if your goals are to ensure that only, you know, approved people are communicating with that API, then, yes, the current approach that you have right now is is a recommended approach. Okay? The reason being is because, you know, cloud CloudFlare zero trust or CloudFlare one, now as as we're as we're calling it, it base it basically is filtering out the rest of the public Internet. So this way, only approved authenticated people, entities are able to communicate with, with your internal services. Okay? Now if if you're in a situation where you do need to open up a an internal service to, to the broader Internet, you will want to use a different pattern. You'll probably wanna use port forwarding, or you probably wanna use, you know, our our our CloudFlare d service to expose in internally facing applications to the, you know, to the public Internet, you know, things like that. So I would probably need to understand a little bit more on what your goals and objectives are. But, again, if you do wanna make sure that it only the the internal apps are only accessible by, you know, you know, by approved employees and things like that, then your current approach is is is the good pattern is the recommended pattern. Okay. So, Siva, our I'm gonna recommend this. You know my you know my first name and my last name. I'm gonna drop my email here in the chat. Flick me out a message. We'll we'll need to kinda go into some of the settings here in your account here. So this way, I can provide you with some some better advice. So one second here. There you go. Okay. Are there any other questions? Nothing in chat? Nothing in QA. Going once. Going twice. And with that, ladies and gentlemen oh, there's another one. Okay. Okay. And I guess with that, ladies and gentlemen, thank you very much for joining us today. I hope you got something useful out of today's session. If you have any questions, my email is in the chat. Don't free, you know, don't feel shy. Don't hesitate to reach out if you have any questions. And I guess with that, I will close things out or pass things back over to Vinay if there if you have any final words before we fully shut things off. But with that, thank you very much, and you have a great rest of your day, everyone. Cheers. Hey, Michael. Thank you so much. Thank you, Michael, for hosting this session. I'm sure all the attendees enjoyed the chat as much as I did. With all the questions coming in, I could tell that, you know, they were all locked in. And with that, I would also like to thank all the attendees for joining today's session and interacting with us live. Hope you found the session relevant and and valuable as well. We look forward to seeing you at the upcoming webinars. And like Michael mentioned, if you have any further questions, please, you know, feel free to contact Michael directly. He has, dropped his email ID on chat. You can reach out to him anytime you want with, any other questions you might have after the session ends. Thank you so much. You have a good day. See you later. Bye.