Video: Office Hours: Cloud Web 'Ask Me Anything' | Duration: 5400s | Summary: Office Hours: Cloud Web 'Ask Me Anything'
Transcript for "Office Hours: Cloud Web 'Ask Me Anything'":
Alright. Here we go. Alright. Welcome everybody, and thank you for joining, today's Forestvine office hours. Today's topic is web security cloud, ask me anything. And today, joined by Herve, who's the product manager our product manager for, Web Security Cloud. Hello, Herve. Hi, folks. And also from our tech support team, we have two subject matter experts, Freddie and, Sharaf, tech support engineers. Thank you guys for joining us today. Hello. Hello, all. Yeah. Hello, everyone. And my name is Mark Lambert. I am a senior program manager in the customer success team here at Forcepoint. So a couple of quick notes before we get started. So I know I said this is an ask me anything session, which it is. But we did put together a very brief slide deck. It's available under docs. You should see chat, docs, and q and a on your screen. If you click on docs, click on the link there, you'll get a immediate access to a PDF of today's slides. We do have a lot of new folks joining the call, so we wanna, provide some useful information on background and and reference material related to Web Security Cloud. Also, Herve will, take a few moments to talk about road map from a product perspective, you know, where where cloud, cloud web is is heading in the future. And then we'll transition to taking your questions. You will receive an email tomorrow with a link to watch the playback of today's sessions. You can go ahead and enter your questions at any time in the q and a tab. And thanks to those of you who did take the time to submit a question when you registered, do appreciate that. We have a few that we're gonna go through first, and then we'll pivot to, any questions that you all submit live. And lastly, I'll push out a survey near the end of the call. Just a couple of questions. We do appreciate any and all feedback that you have for us, on today's session, on the program in general. If you have suggestions for any future topics, we'd love to hear about it. Okay. So with that, the Cyber Institute. So a couple of, quick notes on, training. So I'm highlighting three areas here, types of of training that are available. The micro learning collections, you see these little tiles on that screenshot. If you click on any of those, it'll give you a deeper level of of information on the specific topic. That could be links to videos. It could be links to, you know, quick how to guides. A lot of useful information within that microlearning collection. In the middle, self paced elearning courses. Both of these, by the way, are available for free. The micro learning and the self paced e learning courses. So take advantage of those if you haven't already. Really valuable and free resources. And third, there are instructor led courses that are available, to get full administrator certification. So the links are right here on the slide. And the way to get to the FCI, if you're not already aware, is through the Forcepoint customer hub. If you don't already have an account, the the link is right here. Go ahead and register and get yourself an account. And, you'll see I've highlighted the training. The top center of the of the hub is where you'll access the Forcepoint Cyber Institute. I'm not gonna read everything on here. It's pretty self explanatory. Couple things I will point out though, office hours link. We're in the process of standing up a whole new hub for office hours. So that's where you're gonna get, advanced notice of future sessions that are coming up as well as we're gonna host an archive of all past recordings, since the new year for office hours. That hopefully, in the next couple of weeks, that's gonna go live. Watch out for that, but the link is there on the customer hub. And, let's see. The last one I'm gonna talk about is the communities groups. So right from the customer hub, get access to the community group. This is an example I have for DLP, but I've highlighted in red the, the web security. This is super useful. We have Forcepoint subject matter experts, customers, and partners all actively engaged, asking questions, seeking advice. We do hear that, customers can get their questions answered and resolved without ever having to open a case. So it's super useful. Do take advantage of the community group. And lastly for me, reference material. Here, the full documentation landing page and also the one, two, three, four, five links in the bottom, you know, from a tech support point of view, an answer to some of the most frequent questions that come in and cases that get raised. These are some really useful knowledge base articles and reference materials, related specifically to cloud web. So, again, download the PDF under docs and get access to all of these links. Okay. Now I'm gonna get out of the way. I'm I'm a turn it over to Erve, who's gonna spend a few minutes talking to you about, road map, and then we'll get into answering your questions. K. Erve, I'll go to the next slide, and you can take it away. Yep. Sure. And this first slide actually is just to, briefly review what we, recently released, since the start of the year. Right? So, again, there was more stuff last year, that Dawn I'm not gonna cover, excuse me, on. But, essentially, in February release, we had support for old traffic, as part of a dedicated IP offering, that was, that was launched, some improvements around the scheme user management. And, I think most of the, folks who kind of, connected to portal recently also noticed the, update on our password, policy, right, which essentially, brings support for pass freezes or longer passwords as well as longer duration, including custom durations. And that was, I think one of great point of feedback, from our, admin teams as part of surveys and all those sort of elements there. Right? So just to let you know that, when you provide feedback, we can listen and try to act on this. Again, it might take a little bit longer than you think, but, we we do, we do listen. Right? We also brought some additional logic, for the IP address entries, and as part of the proxy connection. So, again, all that part is the the regular connection policies. And then in April, most of you also noticed right through at the Forcepoint Estate, the update, to data security cloud, which we use as an opportunity to update a little bit our login flow flow, as well as, kind of the the the branding, essentially, the the login page and those sort of, other elements as well. In terms of reporting, minor updates regarding filtering source. These are valuables, again, when you use the transaction viewer or the report builder, so those options are available to you. There was also kind of new search, being, published, for updates and consumptions. Both, I think I'm pulling them on the same time, but, for single end user single sign on as well as the, what we call the manual middle or the essentially the, SSL decryption, search. Right? So, there's timelines. There's been tech alerts, around those search updates, which is the the sort of up in around April, and they're gonna, manifest themselves a little bit later, right, at least for the, money in the middle of SSL decryption. In June, we're also again, typically, we do break down, right, between fixes and security updates and, feature updates. So, on the earlier February and April, I only covered about some of the main points that are typically more around the the features. But, yeah, in June, just to zoom in a little bit, couple of fixes. One that was regarding, what's called a, a CFG deadlock. So that's when users are being moved from one policy to, another. And in some rare occurrence, this was kind of, creating a deadlock situation. So that fix for that has been published. Same as well for, when there's conflict between Deer Sync and the SCIM. So that has been also, published. And then, also on kind of a back end enablement, for a higher number of bypasses regarding, f one e endpoints, for, again, with you two endpoints, executable bypasses. Right? In terms of security updates, just again, just to name one example, going deeper on the cross scripting on block pages, further on the preventions there. So some more steps were done. And then, just to draw your attention in terms of feature, for customers who are today either using the Forcepoint one, platform or also using the CASB, from, from Forcepoint, we essentially brought a compatibility between the two agents. Right? The smart agent, the SCA, and the Forcepoint one e, and also a, proxy connect, right, which is what PSEP, sort of stands for. So that, customer who are using the true products, can use those two agents side by side, and then, essentially, the traffic, for managed application gets tiered, towards the SEA and for all the classic web traffic, again, funneling through f one, f one e. Right? So that's kind of, what we've done, recently. And now if we take kind of a a sneak peek about, what we're working on right now and as well as the things that we wanna bring later, into, into release. Mark, if you don't mind going to the next slide. So, again, I typically break that down. And I think for some of you who've done the joined us on earlier, ask me anything, or I've kind of seen both my presentation either from myself or from my colleague. We tend to break it down between kind of a now, next, kind of a later type of phase. And, again, this is sort of gonna give you a sense of, roughly, the items that we, that we wanna cover and, and that you we expect to either, see sooner or later depending on whether they're on the now next and later. Right? So, an example there is the, work that we've done around the resource centers. Today, the resource center has a certain look and feel. It's also been supported, by, by, by another provider. So we've done some architectural changes, to enable, the support of that, new resource center. So I think that's something that's gonna be announced, very soon and that we expect to come, to you also very soon. There will be a tech alert, to, to inform you about the change. But, essentially, the resource center will be updated, from your end. It would be mostly cosmetic update. Right? So, for example, you can drag and drop, the resource center in different places. The icons are kind of a change and, and and those kind of elements. Right? So just stay tuned. We sort of expect that to make that available towards the end of the month. We also have, what's called the early access. So early access are kind of programs, where we, essentially work with, early engagement, customers. But just typically after those early access are concluded, we then, after ingesting the feedback, release, those, those features. Right? So we've done a good chunk of work, I would say, around the API and the, API essentially for custom categories. Right? So the typical use case, and that's what's put in brackets. URL ingest is, if you have a custom block list and that your SOC team wants to add, for example, new domains or IPs, that need to be blocked. Right? So in today, you can do that in the UI. You can do that by entering directly. You can also, import or, export through CSV, and we know bringing essentially API, right, to, to do those same steps, which helps towards, automation and so forth. Okay? So just, again, stay tuned for that one. As I mentioned, this is available for early access. If there are some of you interested in the audience, please do reach out, to, your Forcepoint contact or maybe leave your, information, either there in the chat or or essentially try to let me know, but we'll, we'd be a, more than happy to work with you and expose, those, those APIs. Right? And there will be an HGA, later January available, later, later in the year or in the next, sort of, coming months or so. Right? Policy propagation, that one is interesting. It comes with, two elements. One was, is the work that's been done on the background to kind of make essentially policy to propagate, faster, across different proxies. We also wanna show you, in the UI when you update and save a policy, how soon and how fast is the policy spreading, throughout all the different, proxies and clusters available in our data centers. Right? So, again, I think that that one has been, asked, and would be, quite popular. This is a great, addition, right, for web administrators, to know when the change has been fully propagated in addition to just, you know, use the filtering test and then, constantly check the policy. Right? We also some more enhancements coming out on the reporting. As I mentioned, we had recently updates around some of the filters. We're going a bit further. We are gonna bring essentially the endpoint versions and the endpoint type, available and as well, not mentioning here, but just to let you know, also enhancements around the view of if you're using dedicated IP, whether traffic was forwarded to dedicated IP, yes or no. And, also, for customers who don't use dedicated IP or use dedicated IP, the view of the egress IP out of the data center, on the on the transaction view or under report builder as well. Right? In terms of integration and support, we should be able to release soon, what's called the federated identity. But if, again, if you're consuming more than one product from Forcepoint, it's the ability to kind of synchronize your identity either through, AD sync or scheme or all those other methods and define it at the platform as well and having those information sort of, like, cascade down across Forcepoint products. Right? There's also some work happening regarding the cloud DLP integration. Right now, after uploading the JSON, if you do create a new category or delete, a new, an existing custom categories, so there's kind of a manual export and imports, export out of the cloud web, interface and then import either in FSM or in cloud DLP. And we are on a essentially automate, those so you wouldn't have to export imports, and it will all be done, on a on a background. To draw also your attention, I'm probably not gonna drain these too much, but we're constantly working on infrastructure and service. So that's what the, essentially, the work stream around proximalization and dese modernization are kind of mentioned here. So, again, like the lines around software, OS updates, security enhancements are kind of constantly happening. Right? I I kind of have them on the next, because they're they're always sort of happening. But just to kind of draw your attention to that, there's some work that we wanna do around what's called blacklisting controls. So, this has to do about either, the usage of, certain security categories, right, such as, malware or other destination that tend or even, honeypots. Again, they come as default as being, blocked, but, of course, the policies can be updated. The issue there is that, of course, when, some users are allowed, to access, honeypots or those kind of elements, it sort of has a downstream impact, to all of our customers, because it's essentially kind of a tarnish, right, the IP reputation. So we wanna bring controls, there in place, for that. Right? So which is essentially ultimately a good thing, for all all of our customers. So that's essentially what's kind of, expected to kind of, in in in the near in near sort of, medium term and the work that we are tackling on, right now. And as we look into, you know, further things that we wanna do, on the kind of the next phase and say the the the later phase is a little bit more beyond, we sort of expect towards the end of the year, or maybe the start of next year, but, to release a new web category, around crypto, cryptocurrencies, and etcetera. And sort of a segment out of the use case, right, between the, what do we call call essentially the, the decentralized finance, right, the the whole, financial aspect of the cryptocurrency, and the miner and the infrastructures. Right? So this way, you have finer controls around your use cases. And if you're using custom categories, then you would be able to then use Forcepoint categories, as a as a default. So more further work done around reporting and SIEM SIEM integration. Some of the things we wanna do is essentially bring, what's called the audit logs. The audit logs are more kind of a track not necessarily tracking, but, kind of highlighting the steps and the change that were done from, admins on the policies and other elements in the portal. And, we want to bring that up, into, the SIEM exports along the logs. Right? Another adjacent kind of work around this is the support for additional format, like CEF and, JSON. Right? So that's on the, SIEM reporting and as well as the web category. And then for follow-up from the API after work done around the custom category, we wanna go further and let you manage, the, essentially, the various bypasses, through API. Right? So they take different flavor, whether it's, SSL encryptions, authentication, all those kind of elements. But, essentially, most likely break down into different phases and use cases, but to get the management of those API sorry, of those bypasses drawn through APIs. Right? Further integration and support, we do expect also further enhancements on the shadow IT, or cloud application database. That's also kind of a work that is, that is, ongoing, but, you know, stay tuned for more there. Some more work happening, in the future there. We also wanna work on the, better tighter integration, with our CASB inline solution. As I mentioned, we just released, recently the compatibility between the two agents. Now the question has become, if I still wanna use just one agent and f one e, how can I work around that? And the CASB inline through f one e, what's also come sometime called, like, the process chaining, would be helping, that use case and allow you to have just one single endpoint and manager, can speak in line, through that, through that same funnel. Right? RBI dedicated as an action, I think is also, one integration element that I think has been quite popular from a feature request, that we want also to, target. Right? In terms of proxy, again, more IPs, so better reputation and all that throughout, but, add additional egress IP for vPops. HTTP two supports as well. Right? So bringing the native support for HTTP two, is important. It's part of the modernization, and, that's something that it it's it's gonna take a a bit of a time on our end, but that we, want to, to to work on in the in the kind of the medium futures. Right? We're also contemplating, stay tuned on those fronts, right, on the DC modernization, to add, additional also point of presence. Again, most likely, an additional one in India, an additional one in The Kingdom Of Saudi Arabia, etcetera. Right? So, again, those are more on the infrastructure side. More details to be shared, but just to kind of, put those sort of, points across. Right? Block by destination, SSL decryption for custom categories, at least the controls, right, to bring those controls back. Device push to control, which is, again, more of a kind of a, CASB type of use case, but then we wanna fold in closer to web, while current URL blocking. So this one is, you know, again, to go deeper, into the kind of a block use case and have, actually parity with some of the on prem functionality, which allow you essentially to, based on the kind of the URL elements, to kind of either do keyword, match or etcetera, and, to decide and unblocking or allowing or those additional policy controls. Stay tuned as well. Mobile agent, something quite exciting as well, that, that the team is, working on. So, mobile in the sense of, you know, Android and iOS, agents. I know sometimes, mobile also refers right to, mobile users or roaming users or etcetera. Right? So this one specifically, is, for an agent, for, again, support of the web traffic for, you know, Android and, iOS or Mac users. Right? Platform RBAC, for the modernization on the on the user interface and the front end of the tech stack and tighter platform integration as well as for their CASB line, strategies. Right? I'll I'll sort of, probably leave it at that. I think at this stage, you probably have managed to kind of read faster than than me, talking through it. So, I hope, this preview, of the road map of the things that we're working on, was useful. Again, the usual caveats, right, that those things are always kind of subject to review and change. And by the way, if you do have, strong opinions on certain elements that are either missing or that you see to accelerate faster, etcetera, again, do do reach out. Right? If you do have a a Forcepoint customer success manager, do ask them about these. Again, as a product manager, I'm always keen to hear from customers and, you know, what are use case that are important to you and and and so on and so forth. Right? So, while this is the statement of what the things we are, again, working on right now and that we plan on tagging next, If there are certain events that, you know, you you feel are either missing from there or that you like to see accelerate further, again, to to reach out. Right? We're we're we're sort of here for that. So and I think I'll, stop on this part, that has a bit more of a road map y, element of the call. And, yeah, turn it over to you and, you know, questions you might have. Fantastic. Thanks, Herve. We we typically do get a a fair bulk of the questions are related to more forward looking things. Customers are always interested in what's coming next. So, hope you all found this, valuable. I know I learned a lot. So really yeah. Thanks, everybody. We want more. We want more product managers on these calls to share, what's what's coming. So thank you. Let's go to the q and a portion now. So, again, anyone out there, if you have questions, you can enter them in the q and a, panel. We'll hit, we only had a few actually this time, but four questions, I think. Yeah. Four that were submitted early that we'll go through. But again, enter any questions you do have in the q and a panel. First one, how to allow the most recent Google Earth version to access the Internet bypassing authentication? Who wants to take that one? Yeah. My I had a look at this question, and I'll I'll answer it. So, we already have an, KB article for it, but that that is a bit old. Here is the KB article which I'm sharing. So, I took a look at this the latest version of Google Earth. The user agent, what we see here, it is, similar to the previous, the older version. So if you are seeing the authentication prompt for this specific application, you you you can define it, define the user agent in a wild card mode. Instead of specifying the full, user agent name, you can specify the Google Earth and with the wild card entry and bypass the authentication for all the destination. So there there might be, a new version of the Google Earth might be having, different URLs or new URLs added to their application. So instead of, specifying the each URL, you can, create an, authentication rule based on the user agent wild card. That might help. But, you need to or, when you look at the, authentication rule authentication bypass rule, that will only apply to the, only apply to an, request coming from the proxy location or the non location. So, then only the authentication by first tool works. But we don't have that much, context here, what is the deployment or how is how they are accessing. So, if the endpoint is installed, I I just tried this, Google Earth provision in the in my lab. When the endpoint is installed, endpoint is able to insert the headers in the Google Google Earth connect request, and it is able to authenticate well. So, if it is specifically for a, machine without the agent, I I suggest you to add an, authentication bypass rule for the user agent and, for all destination you can select. That is the, option you can try. And if it still doesn't work, you can reach out to the, technical support. Team will be able to assist you. Yeah. Alright. Perfect. Thank you. Thanks for dropping that link, into the chat. Super helpful. Yeah. Yeah. And also, I would like to add, one more thing. So I have seen, if some application, doesn't work, customers or the users, have a tendency to add this application directly to the application, endpoint application bypass. So if you add that application bypass, then endpoint will not be able to add the headers to the outgoing request. So in that case, we see the authentication prompt coming for that specific application. So please make sure that, Google Earth TXTs are not added to the application bypass if you are using the endpoint install machines. Yeah. So, yeah, that's for that question. Alright. Great. Thanks. Number two is quick decryption plan. I understand that decryption on the firewall may be difficult due to user roaming, but from a technical perspective, I don't see such a problem with explicit proxy where the user will always connect to web security cloud. Yep. So, the protocol is not currently supported by the the Forcepoint cloud proxy, and we have a, article which explains the, workarounds. I have shared it in the chat. You can look for it. So it uses the, UDP protocol, using the UDP protocol. So, for that to sell inspection, we we require the for the first of all, the traffic is not using the proxy, based on the current, design, or, it it can only send the TCP protocols to the proxy, HTTP, HTTPS, and FTP. So, the, in such cases, you'll have to block it on the firewall or the, if you're using the IPsec, you'll have to, block it on the on your redirecting firewall. And, the protocol will be, fail off, fail over to the HTTPS connection in that case. So that is the solution. And there are also an option to block it on the browser level. There are flags available to, disable so it can switch to the HTTPS connection. Yeah. Okay. Thanks. The next one, and I won't read the whole thing out here. But number three, is there a plan to decrypt WebSocket instead of auto tunnel? Right. I'll answer that one. So, unfortunately, WebSockets are currently not supported for scanning or a cell decryption through web security cloud proxies. It need to be tunneled, actually, as, as rightly mentioned in the in the question itself. Yeah. The WebSocket traffic that is entered, it should need to be, tunneled. You can either do an SSL bypass, or you can enable the option to auto tunnel all the WebSocket traffic. I had a conversation with Harvey earlier, regarding the road map, regarding whether we have plans to support that socket, decryption. Herve said that, you know, we have the plan, but that is later in this year or early next year. Yeah. So and then that, pet sockets are not supported. We have to either rely on SSL decryption bypass or we should do auto tunneling. Yeah. Just to zoom in a little bit on this one. Right? So I think you would have seen that on the on the later, sort of the section of a road map there. At my end, I also would say, right, the challenge with WebSocket is that each different application it's it's not, like, standardized like HTTP or or others, right, which is one of the reason, that auto tunnels essentially allow it, to work. Right? Because otherwise it's causing problems, because each application sent to kind of, either communicate in in different ways. Right? So my maybe questions to the person who wrote that question is is are there specific application, right, that you are interested into decrypting, that are currently using WebSocket. Right? And then which which kind of type of, sort of, class that they that they need or or or or apply. Right? I would again, at at my end, I think I would try to break that down into, sort of the different use cases or families. Right? There are certain application that use WebSocket, that are essentially more about the communication, like, say, Teams type of chat or channels or etcetera. Right? Is that something that you're interested? Some are doing other elements. Right? So, again, WebSocket has good things going for it, but it's at least, for me, would be useful to understand from your perspective which type of, you know, application you want, to decrypt and then, inspect. Right? I have also copied a KB article that explains about the supportability of WebSockets. It pasted it is pasted in the chat. Okay. And the last of the early submission questions. What policies are put into place to safeguard users from any malicious attacks? K. I will, answer the question. Let me first share my screen, so that let's see. Make sense of what I'm talking here. So I hope you are all able to see my screen. So this is the, cloud web security, portal. In the web pages, you can go to policies, and you can select the policy. Inside the policy, go for web categories. Under web categories, you can see all, the threat seeker, web categories. The cat categories managed, the first point, threat seeker. These are the list of categories. In here, there is a category called security. There are few subcategories, in this category as well. So these, categories are actively managed by Forcepoint. Our ThreatSeeker technology is scanning, billions of URLs every day to see if there is, any, threats that's developing. And if if we see that there is a particular URL that is, that was saved yesterday but have got some malicious content. We then re categorize them to one of these security categories. So all all you need to do is to make sure the security category and it's all the subcategories are blocked in the policy to make sure, any malicious content is blocked for the user. Yep. Alright. Terrific. Thank you. And but, I mean, they they also add, plenty of additional layers. Right? You can also, you know, again, around either five blocking. There's also some add ons around sandboxing or etcetera. Right? AV scans. All again, Freddie touched on, one of the core aspects, but there's definitely, multiple layers there. Right? So, and I don't know if we have the person who asked this question, here on the audience, but would be nice just to, you know, again, understand was that, you know, was there any specific area there, right, that you were worried or or is that, you know, generic sort of approach, suffice. Right? And and same by the way, folks, if there's any questions here on the, on the audience, please, don't be shy. Yeah. I was just gonna say this is this is rare where we have no questions that have come in, with really, really quiet bunch today in the audience. Just make sure this is working properly. Can someone pop a test question in the q and a? Just make sure that it's working. But, yeah, if anyone has any questions at all for our panel, for Herve, Freddie, or Shround, this is your chance. We've gone through, what few slides we have. We've gone through the early submission questions. I'm getting concerned now that this isn't working properly if folks can't enter any questions. Let's see. I am going to I'm looking for a couple of friendlies out there. Eric, if you're out there, I see you. And they're oh, there we go. Mohammed, thank you. At least we know it's working. A very few application controller available in the dashboard. More comment than a question. And maybe I'll, take that up. So there's also, I don't know if you looked, but on the cloud apps. Right? So, essentially, the a lot of the core of that use case, right, is on the essentially, block or allow, type of application. If you want so, typically, the market answer, right, for the fine grain control applications, is CASB. Right? So if you don't have a CASB application or if you're interested, I would encourage you to, to reach out to, to a Forcepoint contact there. As a further element, right, what specifically what specific application are more of interest to you. Right? And, again, we do have, CASB inline as well as CASB API available, as as as integration, sort of, points there. And we do want essentially to fold them further, in in UI and all those different elements, as part of a a web security offering. But that's, you know, that's that's the element there. Right? And, yeah, I'll ask you a question as well from, Jason. We mentioned that the cloud is a subscription certificate, expiring soon. So yes. So that's back on the comment I made, right, about the new certificates who have been made available and published. You would have seen a tick alert around that. And the approach for the SSL decryption is that essentially we recommend to download both the old and the new certificates, right, which should be, on the same on the same sort of location and sort of, push that onto your, end user, endpoints. Right? Meaning that, they will have those two certs, available at the same time, and then, there wouldn't be any sort of, impact or timeline to coordinate, very tightly, regarding the expiry. Right? Because if you download the certificate that we published into the portal and push that to your end users, by essentially implicitly trusting those old and the new certificates, the the the timing of the switch, would not have any impact. Right? And I think sometimes there's a follow on questions about, okay. Well, now there's, like, is there a problem that the older certificate is still trusted? No. Again, it's, you you can keep it there probably as as long as you sort of, see fit. This is kind of, more of a cosmetic, but there's no, there's no sort of, impact, impact there. Right? Okay. We had two others from Christopher. Any progress on test database not being used for Neo connectivity? So I forgot to mention this point. So that's part also of the reporting. So right now, some customers using, Neo or certain versions of Neo, etcetera, right, might see when they go on their transaction viewer of the traffic, right, a bunch of hits. Again, this website, test database webcents.com, these are gonna be essentially, removed, from, the transaction and the reports, builder, giving you kind of a a cleaner view and allowing you to, to focus. I I don't have the exact timeline, for when this will be available, but I expect that to come in a in a kind of, I would say, short term, right, within the kind of the, next two to three months. I know some work, on that was already done. It's the the release vehicle. Right? That's I'm I'm still not super crisp on, so I don't wanna lead you on. But, yes, there there is progress being made, and this will result in, all of those kind of, hits, visibility, and and, you know, presence in the logs, to essentially, be, be removed. Right? So, I think those are kind of the two questions there. Let's see. Two minutes of are there any bandwidth limits for users using Web Security Cloud? So they are, I would say, SLAs. I'm trying to remember on the exact number on the on the actual, bandwidth or the, the type of information. Sorry. The the the amount of, you know, sort of transaction or etcetera. I know these are on our, solution writers. I'm I'm trying to bring the exact number to mind, but I'm I'm blanking out a little bit in there. So, yes, there is, but I would say there are definitely very fair. Last time we did a comparison against competition, we were, again, I think, allocating, more more bandwidth, than our typical, typical, competitor. Right? And then there's a separate point I think. I don't know if that's the one you were alluding to, Bartosz, but regarding the tunnel and the tunnel bandwidth, we do have a default, limit. If you feel or need, higher limits or etcetera, some of those limits can be increased. I would just welcome you to, reach out through support and your customer success manager there. Right? If, again, if there's the tunnel element and the bandwidth, that worries you, compared to what you have and where you want to go, there are possibilities to increase it. And then if it's the bandwidth for limits for users and, you know, like, let's say you contracted for 500 users and wonder, you know, am I sort of falling short or etcetera? As, again, I'm really trying to get that number, calling up. I I I I don't, but I can tell you, yes, there is bandwidth, but it's it's it's it's it's fairly generous, last time we compared against competition. Right? So I think the, IPsec tunnel bandwidth is 200, Mbps by default. Yeah. As Harv said, it can be, it can be It can be. You you support increase. Right? Again, those are kind of typically done at the kind of a, commercial kind of a conversation levels. We also wanna make sure, right, that the the load is sort of being spread and etcetera. So there there's definitely, some, some elements, that goes into that. But, again, if there's a need, do reach out and let us know. Right? And and and we'll we'll get back to you. I still think I'm seeing another question from Mohammed about, simple way to add custom block page rather than hosting it. That one so, again, maybe I'm sort of missing the mark, but if you do use the cloud, version there, right, you have the ability to create quite large number amounts of, custom block pages, there. Right? And then then, you know, serve a different block page based on the categories and customize the the content, the look and feel, same as the logo. Right? You don't have to stick with the four point logo. You can upload your own logo, etcetera. We also, and that was last year, but released a a custom, block page presented to, user on the certificate error. Right? But we do support, custom block pages for a variety of scenario. You do not necessarily have to host it as, again, you you could you could host these. There are also kind of a library of preset, icons or etcetera if you wanna play around. This is a bit of a, what you see is what you get, type of editor. You can also go a bit more advanced into the HTML mode. Right? So, I'm I'm I'm hoping I kind of, answer your questions there, Mohammed. But, you know, from my perspective, you you don't have to host it. Right? It's just a possibility, but, you know, you don't, you you don't have that. Okay. And how about Sorry for confusion on the on the on the tunnel bits. But yeah. So if you're interested in the by the tunnel side, just know. Right? It's available, and then, extract. So anyway, glad glad you get you get the answer. And, yeah, thanks. I think you were Freddy was gonna walk us through, right, the the the block pages. Right? Yeah. Yeah. Yeah. So these are the various block pages that you can host through the first point. Yep. Okay. Any more questions? We've got 15 left, for in in our time today. Last call. Any other questions? I am going to take this opportunity then to push out, our brief survey. Again, as I said at the top, if if you wouldn't mind, we do appreciate any feedback that, you all have for us. We do read every response. Let's see some programming notes. We're running a DLP, ask me anything, actually, tonight for our APAC audience, morning, India time. We have for any DLP customers, any DLP endpoint customers that may be on the call, where next week we're having a session, for manifest v three. The latest and greatest, what's happening, with deprecation of manifest v two, moving on to manifest v three. So we're gonna have a session, next Tuesday. Invitation should be going out for that as early as tomorrow. I think it's a bit late in the cycle to get them out, admittedly, but invitations are going out very soon for manifest v three, office hours next week. We will be coming back with a network security, asking anything in the next month or two. I'm stalling for time here if anybody has any of the last questions they wanna pop in. And and I kinda just, by the way, add one more, element, because now I remember it. It took me a while to kind of go into my, my sort of, mental notes. But, so on the bandwidth elements, right, again, I think if you calculate, I think the number that we have on the SLA, was indicated, you know, sort of, like, per user, per month, or etcetera. But, again, roughly, you can, I think, approximate the six gig, right, of data, per month, per user of web traffic, processed, right, which, again, is is sort of a part of there? Alright. Great. A new question just popped in. Any best practices and guidelines for web security deployments? Broad question, but what do you say on that? Yeah. It's sort of, it's sort of interesting. I think it's, probably more thinking about, instead of trying to go deeply, I think I think the going deeply into the use case fine grain elements of, what about this, what about that is more to really set your policy around the things that you absolutely don't want, right, and sort of have your default web policy set around there. Right? So any users and etcetera, you wanna make sure that you you you set the bar, right, to whatever you're sort of comfortable. So, not necessarily in a too probably restricted fashion. Again, I know some customers prefer to go on the, and this is maybe more coming from either on prem or firewall or some of the others elements of going to do categories and then block everything and use custom categories or kind of, special lists for only the things that you allow. Again, from my perspective, that that's probably not the most efficient. Again, it's probably to set your blocks around the sync that you're really worried about, and then you can fine tune or add different type of policies based on users and groups and etcetera, but sort of, set that kind of a a default bar, right, about really, the the things that you worry about instead of just go block everything and only allow a very kind of a narrow set of case. Again, I I respect. Right? It depends on industries and and I would say company cultures and those kind of elements. But, typically, you you'd have both an easier time on on the monitoring and the setting up of the policy and overall user interaction as well, by by sort of, going that way, than trying to go, restrict, restrict, restrict and only allows through exceptions. Again, it's easy for me to say it's also depending on your industry and your, you know, kind of your your company sort of guidelines or or structure, but I think that could be a I think that could be a good one, right, to think about what are the things I wanna, you know, protect the most or, you know, I am worried about the most. Right? And then then it's kind of a start drawing there. I don't know, Freddie or Charles, if there's some elements there that you'd like to raise as kind of a maybe best practice or etcetera, certain things that you might see maybe raising, our cases or questions where you you you know? I've just pasted a link, a KB article on how to get started, with CSC. This is was more basically not about deploying. I mean, it's about, you know, how to get the licensing done and how to get, get this ball rolling if you are starting from the scratch. And I think also in the earlier slide we presented with all the reference material links, so well, let me stop the share here. And, Fred, if you can stop sharing there you go. Now, you guys tell me if you agree, but the documentation landing page, like, the very first link installation guides, configuration management, probably a ton of useful information, right in there. Alright. Let's see. I can't answer that one. Is it possible to automatically disable proxy cloud in f one e e if the user goes to headquarter and that that has force on prem proxy environment? Good question. Yeah. And, yeah, the and the answer to that is, is yes. So there's way to do that. So tipi sorry. My mind was going into, DCP. That that's typically kind of, for users going to Direct Connect. Right? And the Direct Connect endpoint use kind of like a a disposition service. So there's ways, right, to kind of, configure your beacon, to essentially, make the Direct Connect endpoint, going essentially off when you're going into, an on prem, type of elements. For the proxy, again, I'm I'm I'm a little bit blanking on the exact method, but there are also some further work. Again, we haven't covered this, but there's a there's a whole also host of work that is happening on the endpoint and, endpoint road map specifically. Right? And there's some work that we want to do as well on essentially bringing kind of, the location awareness. Right? That to to to essentially make those type of use case, easier or addressing them kind of a more seamless or, even more tweakable, kind of fashion. Right? For for proxy if if this question is for proxy connect endpoint and of if our intention is to not route the traffic to a proxy, the the option that we currently have is, if if you go to a filtered location and if you go to that first particular office IP, you can mark that office IP as transparent proxy. So if if if you mark that, then when the user is or when the PCEP is in the office, PCEP is going to get a PAC file that has direct statements. So, technically, the traffic from the browser will not go to any proxy. Instead, it will go direct. Okay. Thanks, Greg. Yeah. I think, I want to add one more thing. So if it is for the full cloud, solution cloud web solution, there are some, flags available during on the, if the pack file. If we, disable the pack file download in the on premise, then there are options. Override options can be added to, change it to the auto detect settings. But I'm I'm I'm worried if we can send it explicitly to the on premise proxy, but if you probably, you can use the transparent proxy method. It's like if if the PAC file cloud proxy PAC file download is failed, then, it would actually the this flag will, set it to auto detect settings. So it can either identify that the blue tag or transparent, proxy method can be used in such cases to direct, around the traffic to the on premise. Alright. Thank you. Yeah. Yeah. I think probably you can try this, I got a article. There is an auto override mode options while deploying the endpoint, proxy connect endpoint, so, probably we can use it. Oh, that's great. Thank you. Alright. Any last questions? Oh, no. Christopher, as soon as I said it, there you are. Is there a way to configure or suppress or reboot pop up for OTA Neo upgrades? Yeah. That We don't have, we don't have at the moment because, at the, the latest new endpoints have elements of DLP in it. So, system restart is required to complete the, upgrade. But I'm not sure if this is planned for something in the future. Herve, maybe Herve can help us. Yeah. I yeah. And this is where it was kind of pointing to the endpoints or endpoint road map or I think, Mark, right, keeping on us there, I think there are some session that have been scheduled around that. I think the keyword you wanna look for is something called silent update. And and and again, right, I'm I'm I'm a little bit, removed from those exact details or or or or the when or etcetera. But, you know, they they I would say there's definitely road map elements there. I would also mention that, you know, a lot of the work today, right, on the endpoint side is focused on, you know, f one e or sometimes the f one e next gen. Right? So, may always still kind of, you know, being worked on, but sort of, new features or those kind of elements tend to be a little bit more, well, tend to be more focused on the, f one e, agents there. Right? So, I apologize for not giving you, details there. Unfortunately, I was a bit, you know, cut away from the from the exact details. I also don't wanna mislead you. Right? But, you know, there's definitely elements around, yeah, silent updates or the configuration and those flags kind of there. And, I know my colleagues on the endpoint side will be working on those. Yeah. I was just saying in in your defense, you are not the endpoint product manager. And and we we look. We do recognize, the need to come back and have a dedicated session around endpoint. We typically get a lot of questions in in the various product sessions, whether it's DLP or web security cloud, you know, you name it. There are end endpoint implications. So, yeah, it's kind of on pardon the pun. It's on our road map. Future office hours sessions is to have a session dedicated just to, to endpoint. Closest we have right now, as I said, next week is one for DLP endpoint customers, around manifest p three support. Okay. We are three minutes to go on our clock here. Any last questions? Going once, going twice. Do hope you found value in today's session. These AMA sessions are are popular. Right? We don't dedicate the the hour to a specific topic. Just take any questions that you have. Hopefully, you do appreciate that and, and gonna get some value out of these sessions. I did push out the survey. Thanks for any feedback. Any last questions? Last call. Alright. We're gonna cut it here then. Thank you all for joining. Do appreciate it. And, we'll see you on the next Forcepoint office hours. I'm gonna leave the stage and, we're gonna close out the call. Thanks, everybody. Appreciate your time. Thank you very much, everyone. How are you doing? Bye.