Hello and welcome to today's webcast, improved security for your Sterling managed file transfer sweet with secure proxy and sees my name is Canal Martha and I'll be your host today. Before we start, let me answer a few common questions with these brief announcements. The women are is being recorded and you will receive an email about the recording in the next 48 hours. If you don't want to wait that long, you can use the same link you use to log in today or visit the managed file transfer group of the Sterling supply chain user community. You may ask the question at anytime during this left us to submit your questions, please click on the Q&A icon at the bottom of the screen and we will. We will answer your questions at the end. Next slide. It was because I will be discussing forward looking ideas and material. IBM statements regarding its plans, directions, and intent are subject to change or withdrawal without notice and at IBM's sole discretion information mentioned above regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be corporated into any contract. Now let me go ahead and introduce our speaker for the day with chocolate. BJ's and offering manager for IBM Spanish file transfer offerings where he's responsible for IBM Sterling secure proxy ansi solutions. He also overseas tactical and strategic vision for hybrid cloud or Sterling be collaboration portfolio. Try to his current role. He has successfully led the technology solutions in the procurement supply chain, an aftermarket domain. You can certify IT software product manager and has a master's degree in engineering and technology from Intern Institute of Technology in Delhi, India. Back in Virginia and over you. OK, thank you for that introduction. Great to be here talking about picture proxy or newly is and pretty much excited to share the details around that. But before we get into those details, let's let's take a look at why managed file transfer matters to us and then matters to you right? And why is it important to have the robust solutions and mechanisms to conduct the same? So some stats here and probably some of it you may have seen it, or you may be already aware of, but really important to know. And this is again based on the service conducted by some of. The well known analyst like McKinsey and company once in Bonn, IDC and so forth. It's kind of a consolidation of consolidated view of those insights here. So we we have seen in recent years almost 55% of internal and external system integrations accomplished wire files and that tells us that it's. Pretty important to have a secure and robust solution around the file transfer mechanisms, because a lot depends on the company's operations based on the file file transfer activities that goes in almost 20% of an enterprise workloads have now moved to the cloud, and that's pretty important. I'm going to talk about it a little more detailed, but that really tells us how enterprises are shifting their deployments of how they are modernizing. Other deployments in order to get the operational efficiencies or really make an impact on the savings and as well as on the bottom line right? About 88% of organizations they are right now challenge to move big quickly and efficiently, and it also tells us. How what's the significance of the faster file transfer management solution in place to really be able to address that as as the data volumes, the file sizes keep and growing day by day and like being able to effectively manage those transfers is really crucial. And last but not least, our thoughts are important to understand is how the security incidents globally are impacting. Impacting the enterprises these days, so about 3.92 million of is is the global average cost per data breach incident foreign enterprise. So looking at that number, it's pretty significant, not even mention about the brand reputation that gets impacted with any of the security incidents. So All in all, what I'm saying here is again, moving data efficiently or the Internet is very critical component for success of any businesses today and security has been the key concerns with. Every enterprise, regardless of the industry that they operate in. If you look at just one example on the financial services side, financial services, and especially the regulated industry is they have been experiencing the highest volume of security incidents in last couple of years. And like I said, the cost of data breaches is close to 25% higher in in in this sector as well, so those are really sensitive industries. But like I said, it's all across the enterprise and it's really crucial to protect your brand reputation by implementing a very robust security mechanisms for you will be to be exchanges and the file transfer operations. This is where I be installing secure proxy comes into picture figure proxy is DH security solution for IBM Sterling. Be Toby and managed file transfer offerings. It provides market leading MSP solutions like connect direct 4.2 points, secure file transfer, file gateway for hub and spoke, model of distribution and B to B integration solutions like Sterling Integrator which is for orchestration of the business processes and communication. Uh, the partner engagement manager, etc. And more than 2/3 of the top banks globally used these solutions with thousands of customers overall. Thicker proxy here acts like a shield to protect the interactions and operations within these solutions. While your enterprise enterprises deal with external world for all your business exchanges. A quick primer. About second proxy, it's it's basically a demilitarized DMV based application proxy that protects your organizacional file transfer from the public Internet. It does it by enforcing tighter controls that include trading partner authentication, multifactor authentication, session breaks, and all of this happens before the file before the transfer. Even even end enters your ever enters your trusted zone. It incorporates firewall navigation best practices, an SSL session, brakes to keep network and data transactional secure. It basically increases the perimeter security for an enterprise data movement infrastructure by shielding the trusted zone from the external attacks. Again, it does it by preventing the direct communication or direct contact between the partners and the internal servers with regards to the file exchanges. It also consolidate and simplifies the security management. By providing central centralized authentication of partners and being able to integrate with existing security infrastructure like your single sign-on mechanism, thereby reducing the total cost of ownership. And finally it makes you easier to meet your stricter security policies are requirements, be able to help with your audience supporting this demand dates and government regulations like like HIPAA, Sox and PCI for the financial industry. So basically a secret proxy is a critical element in protecting your enterprise and it's brand. It basically enhances security to help reduce the risk to the enterprise. Like I said, bye-bye utilizing the best practices and protecting against an unauthorized access. I also helps you with the data vulnerability and support your audit and regulatory requirements and all by by helping also to reduce your costs and not only administrative but as. Also, the infrastructure costs and the cost to recover from a security incidents right? Not to mention about the fines and audits that comes along with any incident security incident that happens right? And ultimately it increases your speed up on voting, trading partners and or faster revenue recognition. So that's top line impact as well. So basically it it helps you leverage the Internet to lower the file transfer costs and close your file transfer community. So that that in mind today I'm going to talk about some of the key features and capabilities that we have implemented in our latest 601 release for thicker proxy and sees and also explain how it provides an advanced protection for their enterprise file exchange is that are operating on the IBM Sterling MFT solution. I don't hear ago we made available 6 to really something I think in by veil of Jan Jan 31st we made this release. And this really is, uh, is pretty important. So I wanted to give a recap of the four key features that we implemented in 6.0 and then extending the conversation to talk about 601 release that we did a couple of weeks back. There's talking briefly about there not really spending too much time on this, but first of all, the single sign-on. So this was around the expansion of our SSO support capability. We are now including support for external identity providers or the Federation services providers like like shibboleth, Microsoft Active Directory or acquired entity Federation and probably 50 others which are based off the Saml 2 dotto specification. So any single sign on providers supporting sample to specification. We could put that to use here. Basically helps you to authenticate your users using the corporate portal and users may not have to log in again while accessing the IMF the system. We also implemented an enhancement around which we call it as proactive security. It's basically the blacklisting. There's a key problem that we're addressing here to block the suspicious users and or or even they could be a probing users to make an authentication attempt and unusual cases. These atoms would fail. However, there is still a risk that if such authentications are not filtered before hand, they could still find their way into the systems by multiple tries over a period of time or or at the least load the authentication server by making hundreds of failed atoms annual. Probably be struggling to find out more details on those those atoms within a pile of log file that gets generated switch. It also has a performance side to that. So basically setting up the rules and blocking the users of front by ability by being given the ability to blacklist the IPS, IP patterns, user ID or user ID pattern so that they don't even make an authentication Atom. The Turkey announcement is around the high ability we delivered in six. Daughter was around high support for high available deployments where the Sterling external authentication server, which is short form that sees is, is part of the overall viterbi or MFT deployments, right majority of our customers use that component for advanced authentication. We have been supporting high available deployments for the secret proxy or all, but there was one in failover scenario with the tokens from the seed server never got synchronized with. Another if one server goes down and we fixed that in $6 so that you have even more robust support for high available scenarios. And finally we delivered about 14 to 15 arrest apcs rest API. So this this announcement is again on the side of the house where the authorized client applications can interact with these server seamlessly, right? So different rest APIs that have been exposed to which can be used by any kind of application to perform the basic crud operations, create or read, update and delete the Seas configuration, objects, objects, objects such as session, SSL info, trust or authentication, certificate validation and so forth. So these are all documented on the knowledge center, so we can we can kind of look at it. So basically we are with the benefits that we're we're trying to bring up with this is. To be able to access the Seas object once you get the pizza optics seamlessly and give more. Improve flexibility in configuring those objects, which is kind of becoming a more frequently. So we continue some of those and we'll see what's new in 601. So now I'm going to talk about our very recent release, so we continue in adding functionality to 601, which is now available. We made 601 available in January of 31st of this year, and I like, let's let's look at some of the changes. I'll talk about it one by one and go a little deeper this time. So first of all, we are providing the secure proxy certified containers to support the open hybrid and multi cloud use cases. Which can be managed by enterprise ready container management platform like open shift. So take your proxy joins. Its sibling offerings like connect direct integrator file gateway ideas which are already available in as a certified container today for enterprises who are shifting to the modern deployments, we are providing an advanced and robust container image that runs on let out open ship container platform. This little I mean as not only independence sticker proxy, but as a part of the whole deployment it will. As a part of the whole modern deployment based off control based on containers, it will it will give you capabilities to manage the application lifestyle lifecycle. Central Ian seamlessly and it really provide you a very powerful means to leverage multi cloud and hybrid cloud deployment scenarios. So to make it simple, is it when I talk about when I say simplification of the deployment process, it it really includes the steps right from getting an image into an environment to installing a monitoring regularly for the new updates? Are performing upgrades and rollbacks as needed to solve all of those steps? Are will be simplified with this kind of deployment an and our containers that we are providing here affect your first of all monitored for performance and have all the auditability features built in. So that the deployment related activities can be tracked centrali to ensure smooth and consistent functioning of your business downstream critical processes. One of the benefits and. Kind of shifted the next shuttle to talk a little bit more is is. It so this actually. The picture of this depicts the 35 containers as a whole and secure proxies are part of it, which is. Supported and qualified on Red Hat Openshift platform and one of the biggest benefit that we get here is to be able to support multiple cloud environments and multiple platforms so that there is a flexibility to switch or migrate between different cloud providers spanning from on premises to local cloud, private, cloud, public, dedicated. So all form the cloud as well as even like within public cloud. Look at AWS as you are so. With with openshift we're enabling support for all those multiple clouds as well as hybrid cloud kind of deployments where you can still keep some of the workloads running on prices and shift some of those lighter workloads or or non sensitive workloads to the cloud. So that's what we're enabling and I'll talk about the key value proposition of why we are investing in certifying are solutions and secure proxy is the latest one, but we have already implemented that with the other way to be an MST solutions by IBM and will continue to. Kind of least 30 five qualify with the newer platforms and so forth, but the key benefits the key value propositions you'll be getting in order to address your high volume file exchanges growing complexities in the businesses, cost pressures and so that's, uh, that's the reason to address this. So first of all, these certificates drive flexibility with my ability to deploy applications in your preferred cloud environment. Like I mentioned in all forms of the cloud. Secondly, it will. Provide your operations team with scalable, secure an enterprise grade applications platform with the very unified container and cloud management capabilities. Pearly to bring the cost down by building by giving an ability to build new integrations, all the shared infrastructure right along with other applications on the same platform. The whole back end integration can become seamless. If you are have intentions to deploy cloud packs with IBM cloud fax will have an easy button to connect to the cloud pack an envy. You will be evolving or build up time to provide that Seamless connectivity to various cloud packs that IBM provides today. And finally, it also like we adapting Redhead Technologies. It gives you an opportunity to adopt the open source technologies with confidence, right? They have their own benefits and several vendors to choose from. So that gives you an level of interoperability, interoperability. So that was a bit dump on on the cloud enablement side and still highlighting secret prostheses supported as a containerized deployment. They go along with well with our beta be collapse solutions. So at this time will take a little bit of pause. I want to run a quick survey here too. Just bring your attention back and get some feedback on this. Since we have on this topic so you have two on your screen. Choose one of the options and the question is about to understand your intentions in shifting to the containerized world of categorized deployment. You're already There you are. You have your introduction in one way or the other. You are. Exploring the options you are. Building the containers or getting a containers and it's in development or test environment currently. Third option is you don't. You're not doing anything right now, but you definitely have an intention to get this to next 12 months. Active conversations are going on in your in your internal teams. Excuse me, and finally you're thinking about it, but probably it's it's a future we don't see it happening in next 12 months. Up Spell polyester, probably few seconds. By the time you choose your answer and hit the submit button. And then we can see the results on my next screen. Alright, so let's see if you have. That's good. So what we're seeing here is and kind of similar to what I'm expecting here, and we have just out of out with the new container certified container. So I think I've not expect anything in production right now. But there are some border cases where customers are chosen to go to containerized path by building their own containers, but it doesn't seem like in this case, so we have almost like 36% in Devon text, currently very encouraging story. And this is what we are seeing that trend across, like majority of customer so actively working towards that. That I found with the next 12 month and year and completely understand it's it's not a decision that has that's made by an individual product or solution or a tool like it's and it white enterprise wide solutions. So. So yeah, so that's that's a good trend within within the group that we have today. Thank you for taking time to submit that stairway. Alright, let's shift gears to think so one I think it was the main topic and getting to the other enhancements apart from the containerized. Solution that we are providing 601 so the second announcement that we are providing in 601 is our beginning of wireless scanning capability and I don't really need to stress somehow why it is important and an why are we investing in this space. So what we have done is. Well, let me talk about the virus scanning solution approach. So just given background on how we implemented it. So first of all we are giving an ability within sequel proxy. To scan the incoming file. Uh. Incoming file in in the DM BMV subnetwork. You and the scanning can be. It configured, it's an optional it. It won't be enabled by default, so you can choose to put the scanning place using secure proxy or you have to just opt out and you continue doing it the way you are doing it. So it is a director level. It is optional. It can be configured. Secondly, the whole interaction happens in the scanning is supported, so and I cap protocol right and that will follow the RFC 3507 so any scanning engines that support the eye care protocol. Is you you can you can use that to kind of. Connect to this functionality and get the in flight virus scanning done up in incoming file. Now what we have done here is the way we have built in built it in here is we have given some basic. Security configurations and some advanced configuration right? So the basic security configuration, basic and security configurations involve setting of all your host and port for IBM secure proxy and being able to securely connect. With establishing the connections with the scanning engine, right? So we're putting that SSL mechanism in place so that the files can be routed to the scanning engine and we get the scan before sending it to the the whole back end node or getting into the trusted so right. The important thing to understand here is. Scanning is is. I'm kind of an expensive process in terms of depends on what you're sending it to scan so it's a smaller few KB file. It will be quick, right? And those are the smallest smaller sized files are the ones that are most vulnerable for four. In fact, getting infected right? The larger the media files usually have not. So majority of our customers. Well, well, we're designing this. We told us that 95% of the chances of having scans is all all smaller files in KBS. Sometimes not more than probably 50 ambilight is probably the higher limit, so we're given that configuration for customers to to for users to set that up to filter it down of what you want to scan, you want to scan files below, say, 20 MV. You want to scan only certain types of files you want to limit the retries because sometimes the scanning engine is busy, or sometimes you don't really getting stuck. If that happens, you just want to resolve the files to the back end and not really get it scanned. So this is your really playing with the performance was the thing, I mean the the the capability kind of a trade off right? And that's why we would want you to kind of set that limit based on whatever underlying infrastructure that you are using, right? If you can't, if your ability to scan larger files you can go. You can definitely do that. And if you want to keep some of the files because they are large because there's certain file type, you can directly read out to the back end nodes so there won't be any time consumed and then right before even before sending the files to the scanning engine, they can route it back and those when it gets routed back it actually you can. Suffix them with a different file name so that you know that these files are not scared, and then you can implement another mechanism to get. That's fine, scans with interested phone, right? So the influence you have full control on the inside of the dynamic scanning capability that we're giving here. In case the fight is infected and this cancer failed, the secret proxy will immediately terminate the session and it is logged so that the sender will know what's happening in the file was not sent. We can decide if you want to let them know on the reason, but but basically he will get to know that the file was not signed. An and definitely there will be logged for that all or trace of information is there. So this is the high level representation of the architecture here. Now, one caveat here, in our first released, because right in the beginning I said This is the beginning of our antivirus scanning capability. So this is a phased approach. We are going to implement and deliver it pretty quickly rather announcing this capability. So in the first release in 601 we are supporting all the files with only SFTP protocol. It doesn't show it clearly on this graphic, but in 601 you'll have the. This is limited to FTP protocol with all the configurations that I just mentioned, including ability to to rename the file. If you don't. If you want to skip it or if it if it does not fit the criteria that you're set in advance configuration. Going forward will have I'll quickly fast for one shot and then come back again on that so quickly. Want to talk about the phases so immediate? Next target is covering HTTP and the Connector HTTP HTTPS in the correct correct protocol. Uh, and then there are certain additional things that we want to do like like today we support data loss protection. Sorry. Today we do not have the data loss protection support. So that is something that will be doing it in the face. Three in the phase two will start expanding to the more protocols and also giving an additional advanced capability to route the unscanned file to different nodes than the default back end node right? We also have qualified tested this. With the McAfee and will expand or qualifications to other scanning in just going forward. But again, like I said, This is based on the nightcap standard, so if it works for one it should technically work for several of the scanning Indians out there which primarily support I can. OK, so in interest of time will not go this entirely, but you get an idea of this is something that will be implementing in phases. I'll I'll do. This is also a capability scenario chart which talks about what happens in different scenarios. For example, if there are any errors within an ICAP server scanning engine itself. So you deploy semantic and semantic scanning engine, have some errors and the response in the request times out, then we'll kind of send the file. Without an option to send the file to a quarantine server going forward right now, you can decide if you want to send it by renaming it as unscanned or to the back end standard back end node, or you just want to terminate so you can. You can have that option, but going forward will also we had the ability to send it to a current time zone that you define within the trusted zone. If yeah, so some of the scenarios. I think I already covered if the file exceeds the maximum file size limit, then what happens then we have an option to directly sent to a standard outbound node and in future will send it to a separate outbound node, probably a corentine outbound on again. If the file fails with the scanning engine, or if it's if the audit log gets generated, the file will not be sent. The first rate zone. So yeah, we're protected right there. And in the prefixing of the file, so this is this table kind of highlights what I already said on my earlier screen, and again, just to. Just to state it again will be implementing in a very short term from now. Will have expanded support for expanded protocols and will be still some protocols that will be adding in the long term and will be focusing on advanced capabilities like data loss protection going forward. OK, so we did talk about the two then I'm let me talk about the IP validation so I packed in the beginning in their last released. Like I said, we we implemented the blacklisting capabilities. This is kind of an extension to that feature, so we have. We are giving A2 new user exits pre and post authentication exist exits foresees which will allow you to use make use of the third party IP validation services which can. Dynamically. I'll find out if the IPS originating from the right sources or not, so there are several providers out there. They have this reputation database to kind of make that and then they maintain. It's pretty accurate. Probably every hour or every 24 hours. So one example is IP that those are coming. If you want to block an IPS that are coming from the sanctions countries, write an those information. Pretty pretty dynamic that keeps on changing over a period of time pretty quickly, so those external services are the one trusted sources that you can. Connect to it using those user exits. And be able to check their IP IPS dynamically before establishing that connection and and start sending the file server or start receiving the file server so those user exits and this has gone from a couple of customers and then asked for several. Others will be definitely helpful if you want to implement that advanced protection. And finally, around input monitoring, the 4th announcement that you see. So it's a small announcement but yet significant. So for customers who are using Control Center solution for monitoring, the diploid for monitoring the instances. So we already have been given monitoring secure proxy instance. The health of the profits running up and down. We also included sees disturbing external authentication server to the list, so you can also monitor the seeds health in the Control Center monitoring dashboard. That's that's fine. Smaller but really significant announcement so that you can really ensure that everything is fine dining and ensure your availability in that time of the solutions. So with that, let me run another poll here. So this is this is focused more on secure proxy and like I said will will be continue working on the. Uh, cause enhancing those features. Like I said, why does scanning is one area where will start expanding the protocols support. We also have an intent beginning 2022. To invest, enhance the monitoring, reporting and alerting capabilities in secret proxy. Leveraging the Control Center modules right start sending more logs over it, and build more capabilities around reporting to be able to monitor report on the file transfer activities that that kind of happen through secure proxy and also being able to alert, for example, the virus scanning alert. Good mechanism, so it should be for love all those events. And enable them to Control Center monitor. So that's the 2nd. A choice we have is a thing that's important, crucial. You could choose that. It's basically asking you what are the areas we would like to see announcements sooner than later, right? And we're going to address all of these, or a bit of time. The third one here, since we are on this page, it's about modernizing the web user interface. We have those swing UI. Right now we want to bring everything to web user interface. Uh, and modernize it the way we started doing it with Control Center monitor and Control Center director will have a consistent and very easy to use interface for your ID admin for MFT admins. And finally we have continued images right now, but there's this. We cannot do a lot on that. We can keep qualifying new platforms. We can add more capabilities into the container images to better support the hybrid cloud story. So you had to pick one of it, which you think is most important that we need to invest in. Near future. And don't forget to take some input on. OK, Alright so those are out, so I think that. The the response here is. Roughly 30% would want to keep continuing investing in antivirus capabilities expand to the protocols to have full coverage. Yes, that's our intent. Monitoring reporting is looks like is is a is the top choice here. Yes, for that. Thanks for that input. That really helps. And of course we would need to improve the web user interface for ease of use. Great thank you for that response is it helps. All right, so we're coming to an end here for just to summarize. Started off with by highlighting why security is important. Then again, nobody would deny it. It's definitely the most important requirement for RV to be an transactions as well as the file exchanges. I be installing thicker proxy provides best breed of security solutions for the entire bee to be an empty portfolio, and our 6.4 series of release when we shipped it from the 3.4 releases to 6.0 you have seen pretty significant investment. We have been improving it. We will continue to invest and provide the capabilities that give you more reliability and security for your enterprise. File exchange is. So I would encourage you to upgrade to the latest version and take advantage of the key capabilities here. If you want to find more information, you'll have the product page starting point. Of course, the documentation captured all the details on the new enhancements and also encouraged to join the beta be client communicator. Let's go now, will talk about giving a quick one minute primer on how to join client community and you have this links to the 60. An announcement to get a summary of all the new changes that we are bringing in the 601. Of course, don't forget to submit any new ideas on the announcements in our ideas portal. The link is embedded here and also subscribe to my notifications. Therefore, in the support portal so that you will get notified on any new. Really, there's 6 packs or I fix a security packs will be notified immediately through email if you subscribe to those links. With that I will handle a hand it over to canal and Meanwhile I'll take a look at the QH section. Why don't you just being born? Thank you so much. You can turn on for the Q&A. Perfect uhm, so just before a quick announcement on now you know you can actually submit your questions if you have any. At this point you can click on the Q&A icon at the bottom of the screen type of questions in the question box and just hit the submit button. Will try to get to as many questions as we can in the time that we have left. If you enjoyed this content and want to make sure that you don't miss similar future content, P state takes literally just three minutes to join the online Sterling community. We have group so we do integration, file transfer, managed file transfer and order management practitioners. Uh, and there's you know, there's actually a link in the community in your resources. You can actually just use that link to quickly join the community today. With that, let me see if uh on the Q&A. Yeah, so just let me start. Couple of questions and I think yeah, we we have a couple of minutes to take them. So the first question I see is on which version of Control Center is mandated to have the monitoring of fees. So yeah, so that's a good question. I mean we have we are supporting 612. We have qualified the Seas connection with six 1 two so six Control Center monitor 61 two onwards is supported just as a heads up will also be coming up later in this quarter. Under 613 release of Control Center and that will also be supported, so it's it's a good question. OK. The other question I'm falls in here. Is around will secure proxy an be to be other 35 containers run only on Red Hat openshift container platform? Another question so. When we say certified containers, it's mainly focused on qualifying, certifying with the Kubernetes standards, and apologies I missed calling that out, so that enables you to make use of any Cuban 80s platform. For example, if you are migrating to a WS and you want to use amazons given 80 service because you can do that and deploy the same container container, certified containers provided from us, you don't have to really build your own containers. Right, there's a lot of investment in the in building it out, and of course in supporting it as well. We strongly recommend open ship container platform for all the reasons that I mentioned. To give you an agility to shift to the clouds don't really have locked in yourself to one particular cloud or one particular technology so that open ship container platform really liberates you from getting locked in into the one technology and also allows you bunch of capabilities connect to open source technologies. An really give you an enterprise level capability to manage the deployment across your enterprise, not only. Just one part of the solution, so we have qualifying certifying. We're tying closely with Openshift. But to answer the question. If you are an organization, have decided to to to to adopt. Non openshift platform, largely majority of them. We fill out all Cuban. It is based so it'll it'll still work. We may not fully support that platform because of course we are not qualified for that. But we'll we'll have full support on the container images that we provide. OK, one question. I think I covered this already. What are the wireless scanning engines supported for figure proxy to scan the incoming file? So pretty much majority of the scanning engines out there support ICAP protocol. So any scanning engine that supports I cap would be used to as a scan as you're scanning engine and connect it to the second proxy for system to have that in flight or dynamic. Scanning. So with that I think we're right about the time I get there. Feel free to add more questions and then we can get back offline responding to those so canal. Do you want to make any closing commands? I really appreciate your time today. The recording will be available. I see you. Thank you, thank you so much for J. Uh, it's just another reminder, but if you found the webcast insightful, please take a couple of minutes to join the PDP collaboration community. This will ensure that you don't miss any great future sessions that we do. Thank you for participating at this point in the set pass and have a great day. Thank you so much everyone.
Securing the data exchange with your partner ecosystem is critical and many organizations rely on Sterling Secure Proxy to achieve this. We are introducing some advanced capabilities with Sterling Secure Proxy 6.0.1 to make these data exchanges even more secure.
Join our solution experts to explore how new tools in this release can help you:
Improve protection against external threats via virus and malware scanning capabilities at the edge
Support for Hybrid Cloud deployments with certified containers that runs on Red Hat OpenShift
Ensure high availability by being able to track the status of smooth running of SEAS servers through IBM Sterling Control Center Monitor
Increase security with advanced IP address monitoring and validation with ability to connect to third-party sources and deny trusted zone access to suspect connections
You can get your questions answered by our solution experts and learn more about how Sterling Secure Proxy is evolving to help keep your data exchanges more secure.