Name: Rocket Announces Security-First Terminal Emulation
Uploaded: 2025-07-01T15:30:43.958Z
Duration: 45 min
Description: Rocket Announces Security-First Terminal Emulation

Transcript for "Rocket Announces Security-First Terminal Emulation": Hello, everyone. Thank you all for being here today. We are gonna give everyone, I think, a a couple minutes to filter in. Just, I know it's it's hard coming from one meeting to another, so we will give a couple minutes before we kick off the session. But welcome. Happy happy everyone could be here. I am Evan Tackett, the solution marketer for Rocket. I look after the terminal emulation products, and I have our principal product managers, Kris Lall and, Barbara Ballard here with me. So we are very excited to be here. I am really looking forward to this session. So we will give, I think everyone another minute, and then we'll kick things off. I don't know where everyone is located. I'm in Columbus, Ohio, and it is a gloomy rainy day here. But I can't complain because we've had a lot of hot hot days this summer. Someone says Naples. They're from Naples. Looks like. I'm in Seattle. Finally summertime here. Oh, happy Canada Day. Hello, Matthew. How are you? Good to see you on. Alright. We are two after. So I think I will go ahead and kick things off. As I was saying, I am Evan Tackett, the solution marketer here at Rocket. I look after our terminal emulation products, the heritage products, as well as all of our new exciting, secure host access, developments. So I am really excited about this session. I am joined here with, Barbara Ballard and Kris Lall, the principal product managers for Secure Host Access and all of our terminal emulation products. So I will go ahead and get into a little bit of housekeeping here. We will be recording today's session, just so everyone knows. We have had a lot of people register, but, if people couldn't make it, we wanna make sure we're sharing the the link with anyone who couldn't be here, anyone who who may need the session. So we will be recording, and if you have questions, if you wanna chat, I think everyone's found the chat. But, if you if you have questions, please send them along in the q and a tab, and I will keep an eye on it and make sure that we raise them to Chris and Barbara to get question questions answered. But please, keep an eye out for, a a survey that'll come up at the end of the session. I think we'll try to do that right around the q and a session at the end. So please keep an eye out for that. We would really appreciate your feedback. But moving forward into the agenda for today, we are going through the introductions, but we will kind of talk about, Reflection Desktop in a nutshell, what, the space has looked like for Reflection, the the state of the product, and what what we have coming forward, the state of the market, what's changed for terminal emulation, where, Rocket sees, cease development, and what, modernization without disruption, what that means here at at Rocket, and talk to you a little bit about Secure Host Access. So, with that, I think I will go ahead and hand things off to Kris Lall. Thanks very much, Evan. Good day, everybody. So reflection we're really here to talk about Secure Host Access and Reflection Desktop. This will make, more sense as we get further into the conversation here, but Reflection Desktop is the basis for, you know, one of the components that we talk about in the Secure Host Access solution. A lot of you have used reflection and know that it's been providing reliable terminal emulation for a very long time and going back to the nineteen eighties and started out connecting to, HP 3,000 systems, you know, via terminal emulation for, the HP 3,000, which was, the 700 slash ninety eight ninety six terminal type. I like to call it the most popular terminal emulation solution on the market. It's it's, got a very large customer base. We consolidated a few different terminal emulator functionalities feature capabilities into reflection desktop over the years. So, you know, extra, Roomba, and, Reflection Desktop. A lot of the capabilities, are similar between those because we've we've added those capabilities into Reflection Desktop. Lot of innovation, you know, has gone into reflection desktop that you wouldn't normally see in a terminal emulator. For example, redaction of sensitive data. So you can actually hide data on green screens, which is a pretty neat capability. Kinda came about because of the PCI DSS regulatory requirement. There's a whole bunch of automation capabilities built into reflection desktop just by default. So Visual Basic for application support, that's the same Visual Basic for applications. The VBA support that you'll find in any of the Microsoft Office products. There's a dot net API. So if you're a c sharp or other type of dot net developer, there's an, application programming interface available for you. We also have a a programming language called EML express macro language that's available to, you know, to business oriented users that don't necessarily have a lot of programming experience. So kinda something for everybody in the automation, development space. We also have the in reflection desktop, the ability to run just about any type of macro. So it can be a competitive macro. I can mention a few that can run PCOM macros, IBM personal communications, terminal emulator macros, Hummingbird, host explorer, basic macros, reflection extra, and and a a bunch of other types of macros. And then it has, you know, modern look and feel. So ribbons, tabs, integration with Office, plus plus UI modernization capabilities, very modern terminal emulator and and, again, serves as the basis for the secure host access desktop, tier of secure host access. So while Reflection Desktop has been a key innovation leader in the terminal emulation space, there's still a lot more innovation to be done. And now my colleague Barbara Ballard will share why mainframes and other host systems are increasingly at risks from threats. Oh, sure. Put me on the spot, Kris. Okay. Well, Kris is right. In today's environment, IT systems of record are more at risk than they've ever been before. I mean, just look at the news. And that system of record includes the mainframe. In today's hyper connected world, the mainframe remains critical yet vulnerable. Users often connect directly to the mainframe application using just a terminal emulator. Terminal emulators have been around forever. Many of those users still rely on outdated login authentication, just an eight character case insensitive password. This one sufficient approach is now a glaring security risk. According to some statistics from IBM, the stakes are pretty high. The average global cost of a data breach in 2024 was just short of $5,000,000. That's a 10% increase year over year. That's the largest bump we've seen since the pandemic. IBM states that 90% of credit card transactions occur on the mainframe, and that's in addition to storing vast amounts of PII, personally identifiable information. In 2024, 46% of the breaches exposed customers' personally identifiable information, PII, and 43% compromised intellectual property. Another alarming statistics for me is that in 2024, there was a seventy one percent increase in cyberattacks using stolen credentials. IBM reports that 40% of the security incidents targeted application level vulnerabilities. An application level attack is a cyber attack that specifically targets vulnerabilities within a software application. It aims to exploit its code or its functionality to gain access to disrupt its operations and to steal sensitive data. It often does this by select I'm sorry, by sending malicious input or manipulating the application logic rather than attacking the underlying network infrastructure. And finally, another statistic that I'd like to share is or mention is that the insider threat now costs approximately $5,000,000 per breach, more than any other attack. So with these new threats, including AI powered pushing password cracking tools, it makes breaches easier than ever. Organizations have to adopt some modern security best practices to safeguard their mainframe and keep operations secure. Okay. Like, that was a way to start it off. Right? But it's true. If you just read the magazines today, the, information out there on the Internet, it's really alarming, and I can't even keep up with it. More articles are coming out every day. Alright. So I let's change it up a little bit. Talk about me. I came to Rocket Software Software about a year ago with the acquisition of the connectivity products and its people from OpenText. OpenText was previously Micro Focus, and before that, it was Attachment. And I must say, I'm really glad to be here at Rocket Software, and I hope you are too. I've had thirty years of experience in terminal emulation and including the last decade where I really spent as a product, principal product manager, and my focus has evolved helping organizations integrate that terminal emulator into modern rapidly evolving security ecosystem, giving you that ability to protect the host. Rocket Software is a customer focused organization. And if you're in the audience, you came over based on your use of reflection desktop or other host access products, I think you'll find that change brings significant benefits to you and long term value. Rocket software provides a unique and a powerful proposition. Our tagline is modernization without disruption. We meet our customers wherever they are in the modernization journey. For me, that includes the security journey, and I hope that you would agree with me that security is a continuous journey. It will likely never be completed, and instead, we must continually improve our cybersecurity posture and adapt to the new evolving threats. And as part of that mission, Rocket Software invested in a new solution that will allow organizations to leverage their enterprise IAM, identity access and management, to add another layer of security that protects the mainframe. So your corporate credentials. Let's dig into that a little bit. Oh, sorry. Before we do, this is the whole stack of what Rocket offers. Right? In each layer of mainframe, we partner with customers to address every layer. Right? From all the way from the top to the bottom. And what we're really talking about today is the terminal emulator and that perimeter layer, that internal network layer. Right? Whether they're coming from outside or they're inside, it's that protection at the network layer. It's where the access to the mainframe is first established regardless if it's internal or external. Alright. Oh, sorry, Kris. I'm gonna turn it back over to you, and then I'll come back and talk about Securus Access. Thank you, Barbara. So yeah. So, we recently sent out this email notification regarding Secure Host Access, so, hopefully, you received it. And if you didn't, I guess if you joined today, you probably did. But if you didn't, be sure and let us know, and and we'll make sure to get you on the list. But, basically, it's really talking about how Secure Host Access is a security first terminal emulator that enables you to integrate green screen access with your existing IAM solution, to achieve, you know, defend more defense in-depth or true defense in-depth. Rocket's really the only one, you know, doing this right now. I also wanna mention and and I mentioned this before, you know, Reflection Desktop provides the basis for the secure host access solution, that there's, we're gonna talk about in just a minute here how there's three tiers and, and and this is really the, the basic tier, the the pro tier. So, basically, you've seen where we are today with reflection, you know, where we're going with Secure Host Access. With Secure Host Access, we're taking the next step and fitting the terminal emulator into your enterprise security ecosystem. And now Barbara's gonna share share more details regarding the driving forces behind the Secure Host Access solution. Thanks, Kris. So you're absolutely right. Secure Host Access is a security first approach at terminal emulation. Right? So we've been in the game of terminal emulation for well, I won't date myself. A long time. Now what we're doing is moving that terminal emulator into the same IT security infrastructure that you use in order to protect all your other high value targets. It allows you to add those layers of defense. So between an end user and then the valuable host application and or data that they're getting to. It can integrate with your IAM so that end users are authenticated via your enterprise credentials, and they're authorized via your enterprise user directory. And I'm gonna give you I'm gonna give you, a a demo of this. So I know some of this is a little bit hard to imagine. And they do all of that before they get a connection to the mainframe. And what's more is if they can't get through those hurdles, if they fail their authentication or or they aren't authorized, then they don't get that connection to your mainframe. That's really important. And as I already described, this ecosystem for security is rapidly changing, and it includes new mandates and new policies that organizations need to comply with. I mean, I I can go on all day long and talk about all of them. Right? But, some of the ones that we have on the screen are are, PCI DSS. Right? So that turned on March 31, that turned from a best practice to a mandated multifactor authentication. For an example, New York state in The US has a state financial, services mandate, and they're calling out multifactor authentication. We're hearing that HIPAA is gonna call out. It hasn't yet, but but odds are it's going to call out, pretty quickly. And and this is all just based on the attacks that are happening. It's it's it's a proven layer of defense in-depth, multifactor is, in order to, you know, thwart those bad guys from getting to your system. I mean, if you just think about, how they get in today, they steal or buy a username and a password, and so then they can access the system and and and that's pretty easy to get anymore with phishing scams and all those kind of things. But if you up that to, more factors to something that you know, something that you have, or something that you are with biometrics, then it's a lot harder to get into that system. So that's why multifactor is really the game changer here. And most of you, because of the, industry that you're in, probably use multifactor in your organization. And we're gonna talk a little bit about multifactor versus single sign on, so that's that's another conversation. I'll get to that in a minute. But but you're already using that in the, enterprise. And to do multifactor on the mainframe, that would mean a mainframe resident, application. Just one more thing. And so many customers are looking for ways to use what they already have to either provide that, requirement for multifactor authentication or they're just adding a, layer of defense. And when you can do single sign on with multifactor, it really makes a a really sweet story, and that's what we've been working on for the last year. So so as I described, the ecosystem, for security is changing, and that includes the new mandates and the new policies that you have to comply with. So now we're gonna kinda take a look at exactly how that product works. And and the other thing I wanna say, because I know, one of my favorite customers is on the phone. You're all my favorite customers. But but one in particular uses host access for the cloud. That was also a, it was a all those companies, Attachment, OpenText, blah blah blah. It is also the DNA for, this product. It is the DNA for the web client. So just wanted to mention that as well. And and the other thing because I I just wanna be careful and make sure that I'm I'm letting you know what's going on, why, and and, and what's behind it. If you have a web based emulator today, you know, the ones in the reflection family were reflection for the web or or host access for the cloud or any other web based emulator. Oftentimes, that's pretty easy to, integrate into your corporate IAM because it's web based, and and there's tools out there for incorporating web based tools. But what we've done here is done the same thing for the thick client emulator, and that isn't done by anybody else. Not today anyway. I'm sure my competitors will be catching up, but that is something that's unique to Rocket. And what we did, was we we took our conversations with existing customers who had a need to make sure that it was all run through the corporate IAM, and we worked with them. We've been working with them for the last ten years. That's how this, solution was born. So, so, anyway, I just wanted to follow-up on that just a little bit. Okay. Sorry. I'm gonna make my screen a little bit bigger so I can see things a little bit better. So this is this is Rocket Software secure host access. This is really the market texture diagram, that is on here. So, and, again, it was based on years of work that we did with customers, both in the, US federal world as well as the commercial world. What it really all kicked off was back in 2013, and I I you probably all heard me tell the story about just tell it really quick. Back in 2013, there was an OPM breach. That was really important because that was the first time we all had that moment, that usernames and passwords were being used by people that we didn't know to get into systems of record and expose personally identifiable information. That was just, like, one of the first. I call it a slap in the face. And so that's when some of the regulations started changing. Right then, The US federal mandates, they didn't come out and say multifactor because it wasn't really a thing back there. Maybe it was, but it certainly was hard to do, and it certainly wasn't something well thought out yet. But what did happen was they all went to mandates that said no more usernames and passwords. And so this was, we have a lot of US federal customers and so they came to us and said, what do we do? How do we replace usernames and password? So that's really how this was born, and it's just really evolved over the years. And I will tell you, I have customers that either have this rolled out today, this very solution, or, are are in the middle of rolling it out. And as we do this, things are changing. So I again, I have a very large federal government customer. They have always been doing, sorry, smart card authentication. Right? Two that's two factor because they have the card and they know the PIN, but now they're, enrolling in a new, program pushed out by the federal government. It's called ICAM, one identity, and so they had to change it up and they had to pivot and move to either SAML or OIDC, and this product allowed them to do that. So so we do try to stay ahead of the game, and we do try to adapt in whatever technology you have in your organization. So that's pretty important. So alright. So back to the solution. This is it. So you'll see a thick client or a thin client over there on your left and a host on your right, and our solution is in the middle. I I shouldn't say that because we actually own the thick client and the thin as well. But, you're used to using a terminal emulator. You're used to connecting to our host. It is that mid tier server that is new for you. So so what we do here is we make sure that they can clear your corporate identity. What does that mean to you? That could mean SAML, o I d c, LDAP, smart cards, Kerberos. You you can be using a multifactor, some of the vendors that I and I and I'm not trying to exclude anybody. So if I don't say yours, don't don't feel offended. There's so many. But like ping, any federated identities. It's all about how you connect to that, and that's done by specification. So o o I d c or o author or SAML. And so we really do connect. I'm a product management person, not a salesperson, not a marketing person, so I'm not gonna tell you a 100%. But I haven't seen one yet that we haven't been able to connect to. So I'm certainly gonna say in the high nineties. But there could be one out there that I'm not aware of yet that we can't connect to via specifications. But what we do is we allow that integration so that when your terminal emulator is launched, it then is challenged by that corporate identity. Right? Once they clear that, then we go through one more thing because I will challenge you. I don't think everybody in your organization should be getting to the mainframe. So how do you throttle that? Well, the way we've throttled it in the past is by can they if they don't have a login, then they can't get in. If they don't, if they don't if they can't use a password, then they don't get in or a passcode or or what have you. But, really, we can we can do better there. So we can incorporate into your user directory. And if they're not authorized in your user directory where you authorize access to all your other high value targets in the organization, then they don't connect to the host. So that's really kind of the secret sauce here. Now I know you're asking yourself, well, gee, if I'm sticking a server in the middle there, that means that, I'm gonna have performance hit. That's not true. Don't think of that server as something in the middle. Think of it as an integration point because we don't your thirty two seventy data does not travel, through that, connection to the IAM. It's just a integration point. It defers off to the IAM. All your IAM rules apply. K? So it just differs off when the IAM comes back to us and says, yep. They're good to go. Then we move forward, but it we don't throttle things. Sorry. Lot to cover here. I wanna cover one more thing. So sent this this so that security is a journey. Whenever we talk about multifactor, we're asking somebody to sign in with more than one factor. You're immediately thinking popping more authentications up in front of your end users, and that could be problematic because if end users have to jump through more hoops, they are not, they're not productive. So we have this concept of, sorry, multifactor authentication or strong authentication, with more than one factor and single sign on. So, we also incorporate that. So today in your environment, you likely only authenticate once in, excuse me, in a given period of time. Because the next time you need to get to a a resource, your IAM uses single sign on. So what I mean by that is you'll carry around a little token with you. I know I'm not talking technically, but that's really what happens. You carry around a little token with you, and when you go to authenticate to the next thing, you pass your token and it says, oh, you're valid because your token is still it hasn't expired and you've authenticated, we'll let you in the door. That's what single sign on with strong authentication means, and we honor that. So what does that mean to you? That means that when a user connects to their mainframe, they will not necessarily, depending on your IAM, be prompted for more authentication. We also have some secret sauce on the back end, and this is what will probably be different for you. Some of you may use this technology today. We've we've had it out there for a little while. It's gotten much better, but it's also now almost unique, if you will, in the market is we also offer single sign on for the mainframe or other hosted, platform in your background. It's for 100, Unisys and BT boxes and all that kind of stuff. What this allows us to do is we have a mapping to your end users out in the, enterprise, and we map them to your end user on the I'm gonna talk mainframe here because it's the easiest, and it's a great example. On the in rack f, for example, or ACF two or top secret. We have a mapping, and we integrate with a component on the mainframe. The two that are top of mind for me are zMFA and DCAS. We integrate with those, and that is the authenticating authority on the main frame. When we come in, we say, hey. This is, you know, Bob from the enterprise, and he's, Smith on the mainframe. He's authenticated in your enterprise. Will you allow him to, authenticate to the mainframe? And the mainframe looks and cuts him a one time time limited code, and we pass that along to the user, and the end user logs in with that code. So I'm gonna I'm gonna repeat that because it's really important. One time, time limited. So think about that versus your eight character case insensitive password. Much stronger. The authority here is the mainframe. So one time, it can only be used one time. It's time limited, and, of course, the more you can do on the mainframe, the shorter that time window should be. Right? Because the more the more privilege you have, the stronger your authentication and authorization needs to be. But then we allow you to automatically sign in. So, so now I'm gonna show you a demo that actually shows you what I'm talking about. Okay. So, Evan, sorry. Yeah. Move me along there. Okay. But before I show you a demo, I wanna talk you through it because what I'm gonna show you is something that doesn't happen, and that can be really hard. So so I'm gonna move screens around here so that I can see what I'm doing. So this is the way terminal emulation works today. So you will have a terminal emulator on your left hand side. I hope it's one of mine. You had your host on the right hand side. All you need to do here is supply a IP address and a port. I'm hoping you're using some encryption, and you land at the mainframe login screen. That's what terminal emulation is today. So that's what needs to change. Go ahead and move on. We enter the secure host access server that has, sorry, integration with your IAM. So in this case, we would you would open that same terminal emulator, and this is the demo I'm gonna show you, and it is it is configured to connect to the server. The server's configured to talk to IAM. So what happens is, our server runs down and says, hey. Barbara trying to log in. Is Barbara authenticated? And, and so this is where authentication the IAM has the rules, and they say, nope. Barbara hasn't authenticated. He does not he's not carrying around a token. Prompt him. So then we prompt Barbara. He clears his IAM, which could be LDAP Kerberos, you know, you know, whatever you got in the house. Once he does that, then it comes back to the mid tier, then it goes back to the IAM, and the IAM goes back to the server and the serve our server. And this server goes off to the user directory and says, okay. So Barbara is authenticated. Is he authorized? Is he in, rather on his own or in a group, authorized to access the mainframe? We get return of yes or no. If it is yes, then we connect him to the mainframe. If it is no, then the connection stops and he goes no farther. Okay. So we can make that stronger. That could be very strong authentication on your front end. So, I say very strong because, you know, it could be two factor. It doesn't multi factor is could be three or more. So it's just but it really is about strong authentication. Right? I mean I mean, Dora right now is calling out strong authentication. They don't really necessarily call out MFA. They may. Right? They may step it up. Everybody's stepping it up. But right now, they're calling out strong authentication. So, you know, there's a lot of strong authentication out there, but an eight character case insensitive password isn't strong authentication. So we can make that front end as strong as it gets. And that, again, it is all about your IAM. So let's let's take that security journey and let's think about strong authentication. You could maybe you just maybe you don't care about the user experience, which is valid because security is more important. You could challenge your users every time for strong authentication, for MFA, for example. Now that could be exhausting to your users, and I'm sure you're gonna get some pushback. But it's a valid choice because of security. So so that's what I mean is that we wanna make sure that all of those terminal emulators run through that strong authentication that you already have set up based on your rules. So we can make that stronger on the front end by having that a strong authentication tool like multifactor. Okay. One more slide. Secret sauce here, and that's where we add in the single sign on. So if Evan had not clicked and I didn't have that circle in between the server and the mainframe on the right hand side, then what would have happened, and I'm gonna show you this, you would have landed at the rack f or ACF two or top secret login screen. You would have logged in, and that's how you would have gotten to your application on the main frame. But that really, again, remember some I'm not saying all of you, but some still use, like, eight character case insensitive password. And one, not strong enough. Two, doesn't mean mandates. So we can make that better. We can that's where we add the secret sauce where we integrate with the component, and we can make this a one time time limited token instead of your username and sorry. Your yeah. Your username and and and that, not so good password. Alright. So now we're gonna do a demo. Now remember I told you demos are what's not gonna happen. This first demo is really just somebody launching the thick client emulator and connecting to the host so that you see how things work. So here they are. They've landed at the rack f screen. They're gonna type in what application they wanna go to. They're gonna supply their username. Now they're gonna type in their password. You'll see that's really short. And here they are logging in. It goes through its motions, and it lands them at the application that they chose to go to. So that is how terminal emulation works today. You can think about that yourself, and that's probably how it's working for you in some form or fashion. Now let's look at secure host access and how that same login would work. Okay. So here we go. So this is and we have I've configured this in not single sign on mode for you on the front end because I want you to see it. So I launched the emulator, and now it's being intercepted because it's configured that way. It's being intercepted by your corporate IAM. I do not have single sign on token in my pocket because I wanted you to see this. I was challenged by my Okta. That's what we use here at Rocket. I was challenged for my two factors. One of them is my normal password that I use every day to log in to Windows, and the other is the code that I have in my Okta app. I happen to get it on my cell phone. So I get that I get that code. I enter it in, and now Okta is verifying that I am who I say they am. Under the covers, it's gonna run back and make sure that I'm authorized to connect to the mainframe, and I am. And now you're gonna see this fly by because it is what doesn't happen. Now I'm at the same application. I can't even talk fast enough to tell you what happened. So what happened there was once I cleared Okta, then the server my server, the host access server, took over and it worked with rack f on the back end. This host is configured with z m f a, and it worked. And and the user has already been authenticated, and, ZMFA said, yep. I will let this person in and I will let them in via, a one time time limited token. So so that is how we use stronger security and have that user experience. It's still a good experience, but still very, very strong authentication. So okay. Not sure even what the next slide is. Okay. And I think I'm turning over to secrets. Yay. Okay. I'll get you some coffee. Thanks, Barbara. You betcha. That's great. So yeah. So let's use the next two slides here to talk about the Secure Host Access solution. So, really, this is kind of a really high level look here. There's it's a single solution with three tiers. So as you go to the right, and we'll we'll talk about each one. So there's the pro tier. And as you go to the right, you add more functionality, more capabilities. So the pro tier is really about the desktop terminal emulation and its basic security features like TLS 1.3. When you move to the enterprise tier, you're talking about the desktop terminal emulator and some of the central management capabilities that, you know, go along with that. So central management of your desktop terminal emulation estate. And once you have that capability, once you have the central management in place, then you have the ability to integrate with an IAM solution, an identity and access management solution. You have the ability to do multi factor authentication and then, also, you know, single sign on in those situations as well. So, again, moving to the right, you've got the pro tier, the enterprise tier, and now there's the anywhere tier. And that includes everything that is in the pro and enterprise tiers. So you get the desktop terminal emulator. You get, the central management of the, desktop terminal emulator. But now you're adding the web based zero footprint terminal emulator. So you can access your host systems from any, any browser, any HTML five browser. And you can use a single dashboard, a single console to manage, both your thick and thin clients, your desktop and web emulators. Again, that's kind of the high level look at the the single sing secure host access solution and the three tiers, pro, enterprise, and anywhere. So if we look at this a lit in a little bit more detailed manner, go to the next slide, please, Evan, then, this is kinda really, you know, going to the next level of detail here, if you will. So, again, the pro tier, it's a feature rich desktop terminal emulator. That's the reason why I talked about Reflection Desktop at the beginning because Reflection Desktop is the DNA for the Secure Host Access Pro level, that that desktop emulator, which includes some of the things I mentioned previously and some things I didn't mention previously. So I mentioned VBA macro support, kinda modernized UI, integration with Office. I mentioned all that stuff. I didn't mention, you know, TLS 1.3 so much and the fifth, you know, the fifth validation, which is a US FedGov standard. The, latest SSH encryption, smart authentication, I think Barbara mentioned that, for HSPD 12 as well as FedRAMP, standards require that. And then moving on to the, the host access secure host access enterprise tier, you get things and and, again, we've kind of emphasized these things like, integration with your IAM, the ability to enable multi multi factor authentication to authorize access to your, you know, valuable host systems. Really, at this year, we're talking about enabling your thick client emulator, which is which is what most of your users, you know, have been using too up to this point because it's you know, we've had thick client web based, desktop based terminal emulators for, you know, thirty years now, if you will. You can lock down the emulator via, LDAP groups. You can, you know, seamlessly update security settings, from a central standard sorry, central point. So using the, central management capabilities there again. So if you wanna move your, end user state from TLS 1.1 or 1.2 to TLS 1.3 because that's the new standard for the mainframe, you can make that happen, at the, the enterprise tier with that central management capability. And then, again, looking at the the anywhere tier, which adds the, web based capability, so it has the desktop terminal emulator included. It has the central management capability. Okay. Now you've also got the web based capability. And and how powerful is that being able to go to any web based, inner you know, interface, any browser, basically, on your phone, your tablets, your Windows desktop, your Mac desktop, whatever, Firebird browser, and then being able to access your host systems, from a browser. And, of course, you're going to integrate, some of the security capabilities we've talked about here to make sure that only those folks that should have access to your host systems are getting access through that interface. So a lot of power, a lot of capabilities in the secure host access solution. And I think now I will, open it up and turn it over to Evan and open it up for questions. Yeah. I I haven't seen questions come through in the chat. It I think you you must have wowed everyone here. That was very well done, Kris and Barbara. But if you do have questions, please feel free to to pass them along in the q and a tab. And I believe everyone here should see the the the short survey come through. We would really love your your feedback there. But I think we'll we'll give everyone a a minute to complete the survey and and pass along questions that that they have. And I think most of you know how to reach out to someone at Rocket. There is an ask the expert button if you have no other way of getting contact or or or, you know, don't maybe know your sales rep, and most of you know me. So, anyway, please don't hesitate. I mean, questions are gonna come up after the fact, things that make you, you know, think of things in a different way. And please don't hesitate to reach out. This is this is what we do for a living. This is what we love. And and you're in a good place with Rocket, so we wanna make sure that all your questions get answered. And there's a lot to this solution. While we make it seem simple, we there's a lot we haven't discussed about managing, you know, your thick and thin emulators, locking them down. I mean, there's just there's a lot going on. So, and and it's a great tool. We just we just can't talk at you for three hours to go over the entire product. So, so we're coming at this really from a, you know, security perspective and just getting you to kinda understand the difference between what you have today and what you could have with Securus Access. So That's right. Yeah. And I And we're trying to get the word out. So we we mentioned previously, we've got that, you know, the email we sent, to notify you all of the, change and of some of the changes and then, of course, the of the secure host access solution. We're launching it and so forth. Just wanna make sure that everybody is, getting you know, receiving those notifications. And if they're not, be sure and let us know or your, or your sales folks that you work with directly so we can make sure everybody's getting getting the message out there. Maybe you have a colleague that should also be receiving this information. Let's make sure we have everybody on that list that that needs to be, you know, knowing about the, changes here as well as the Secure Host Access solution. That's right. Valid point because there's more emails that are gonna start coming out, and there's actually more webinars coming to talk a little bit about how do you get from the product that you're using today to secure host access, and we wanna be helpful with that. And we wanna kinda we wanna help you understand what that means in the beginning, and and partner with you until we get you upgraded. So That's right. And, we we also have a host access forum on the the Rocket website, which is another great place where you can find all of the, events that we're hosting and anything that's available. So, I would I would definitely recommend that you follow the forum. We will also have the the recording for this webinar there if if you want to pass it along to to anyone else. Kris, I see you were late joining. No problem at all. We as I mentioned, we recorded the session today, so you will also get the recording and you can you can take a look. But, quickly, we, talked about, the the reflection desktop space today and where I think a lot of our, our customers are now, what's the the state of terminal emulation and the industry really looks like as far as, cybersecurity goes, and why, Rocket is taking the steps to to move to a a, security first terminal emulator like Secure Host Access in the future. So, hopefully, that is a a decent overview, and, I I would love to to have you watch the the recording. But if if you do have, any colleagues that should get it, feel free to pass along the recording. Yeah. Okay. I haven't seen other questions come through, so maybe we are are good for the session. So, again, thank you all for being here today. Really appreciate the attendance. We are really excited about the the journey that we're on, and we're excited to be on this with you guys. So, if there are questions, if there are anything that you need, as Barbara mentioned, you can reach us on the the the experts, link on the website. You will receive the the recording. We are always here to help. Thank you all so much. Have a good day. Have a great day. Day, everybody.