Name: Rocket Customer Webinar: Rocket® Terminal Emulator Desktop Lifecycle
Uploaded: 2026-02-17T19:31:02.629Z
Duration: 56 min 40 s
Description: Rocket Customer Webinar: Rocket® Terminal Emulator Desktop Lifecycle

Transcript for "Rocket Customer Webinar: Rocket® Terminal Emulator Desktop Lifecycle": Hello, and welcome, everyone. I'm so glad you all could be here today. I am Evan Tackett, in solution marketing. I look after secure host access and RT, all the emulators here at Rocket. I'm joined by my product product managers, Barbara Ballard and Chris Law. I am really excited about this session. We have so much exciting stuff happening in this space and a lot that that impacts your products. So I think I think everyone will be will be excited to hear what we have to say. So glad you can be here. I think to kick things off, I'll do a little bit of housekeeping. First, we we just want this to be really an informative and engaging session. So if you have questions about what we're covering, feel free to drop them into the the q and a, the chat. I'll keep an eye on those windows and we can can take questions as they come in. That way they're relevant to to what we're covering. If there's anything that you don't wanna ask in the session, we do have a email address that goes straight to Chris and Barbara, and we can take questions that way too. So we we want to help and answer as many questions as possible. So please, please reach out. We're we're here to help. But now I will go ahead and hand things off to Chris and Barbara to walk us through. Awesome. Thanks, Evan. This is Chris Law. And just a quick agenda review here. So we're gonna look at some of our history, historical background, you know, where we came from, how we got here, what the path forward looks like in the terminal emulation host access market, how we're gonna be supporting folks, you know, with product life cycle for the various products that are are moving to the product that we're talking about today, which is secure host access, you know, what our support commitment is to you. And then, yes, we'll be taking questions as Evan said, as we get through this or go through this and at the end. Alright. So this is the non exciting part, Evan, where you get to do the disclaimer. Basically, we're gonna, you know, tell you a bunch of information today as far as we know as of today that it's accurate. We're gonna do our best to, you know, be transparent and share accurate information with you. But some things change, and so, you know, things will happen in the future that might change our direction or so forth. But for the most part, what we're talking about today is should be accurate and helpful to you. If you wanna review this full disclaimer, you know, after the webinar, we'll be recording this. And and then you can read that whole exciting statement there. Alright. So let's move on to the historical background. So I like to show this chart because it's been kind of an interesting journey that we've been on over the past, you know, twenty to thirty years in the, host access market. And for, you know, Rocket Software in particular, you can kinda pick your product tier and see what path, you know, you've you've been on. In in the case here where we talk about Rocket Terminal Emulator, there's a company called Siegel Software, you know, that began was incorporated back in the nineties and then was acquired by Rocket. They had a product called BlueZone and and that eventually became, you know, RocketTE desktop, which is what we're talking about here today. I think if you look at, you know, any corporate journey probably for the companies, you know, you work for, you'd probably know, you could put together a similar map, if you will, of all the interesting twists and turns there have been in the history, you know, with mergers and acquisitions and so forth. And and so I do like this this, you know, graphic because it really does kinda show where we came from. And there's a lot more to come, so we're excited to share that with you today. Alright. So now I'm gonna turn it over to Barbara, and she's gonna talk about our values and our missions and and mission and so forth. Thanks Barbara. You bet. Thanks for the introduction there, Chris. So yes, welcome to all of you and thanks for spending some time with us today. So I came over much as Chris did in the it was called the AMC divestiture, divestiture, which really means that Chris and I came over via a with a portion at the time. It was a portion of OpenText, but looking at that slide that Chris shared, Chris and I came over via a lot of different companies. But the good news is we're at Rocket Software and that, my friend, is a good place to be. I say that from heartfelt communication to you, my customers. The reason why is because of the values that Rocket shares. Know you know this because you're a Rocket customer, but I will tell you that we're helping probably 16 different groups of customers that have had various emulators, the ones that Chris showed on his slide, understand our path forward and that's what we're here to talk to you about today. Many of those customers haven't had the experience at Rocket. Chris and I are somewhat new to it. Right? That acquisition happened a couple years ago. But it's a great company to work for, both as an employee and as a vendor to its customers. They have real purpose in everything that they do and everything is really customer focused. I hope you'll find that today. Is never something that a customer wants to hear about the product that they have invested in may not be the go forward flagship product. What I will tell you when Rocket does that, it does it in a way that shows you the vision of where we're going. I'm hoping you're gonna see some goodness in that vision because there's a lot of it there for you. But also that if you choose not to go on that journey with us, we'll still support you. That again, we'll be talking about that today in much of this presentation. And we do all of that through our values, which is empathy, humanity, trust, love. And sometimes that may sound a little squishy, right? And I get it. It's a little awkward, but you know what? I thought it was too when I first heard them. I will tell you as a Rocket employee, it isn't squishy and it isn't awkward because that really is what Rocket's all about. So I hope you'll see that through the presentation today. I hope you'll listen carefully because we think we've got a great journey for you to join us on going forward. And at the end of the day, at the end of this presentation, you're gonna get an email address. I think Evan referenced that, and that's where you get to Chris and I personally one on one. Right? It it's an email address, but it's just so that both Chris and I can share it. So we wanna hear from you. We want to know what you're thinking about and we want to know how we can help going forward. Think I'm going to continue, right? We're going to talk about that journey and we're going to talk about it right now. The one thing I will tell you is that I believe that much of this journey we're going to share with you over the next ten-fifteen minutes is really partly why Rocket Software made the investment into this portfolio of products. We are taking what you know as a terminal emulator and we are now developing that terminal emulator into a security solution. So that's what we're here to talk about today is where we're going and why we're going there so that you can understand our journey. About fifteen years ago, somewhere in that range, I've been with, well, Rocket over 30, I used to do terminal emulation for my business and about fifteen years ago I changed my focus. So I changed my focus in the previous companies looking at the terminal emulator and understanding the security state at the time and how we could take that terminal emulator and put it into today's security ecosystem of the organizations that have mainframes. Sounds like a lot of marketing words in there, but really what happened was back in thirteen years ago, we had the OPM breach. That was one of the first breaches that kind of came out, slapped us a little bit in the face and said holy cow, bad guys are out there using compromised credentials to get to data that you don't want them to get to. It's really as simple as that. And here we are. Oh, by the way, that was a personal thing for me because OPM is the Office of Personal Management. I'm a vet. Information was leaked. I got notified. So when my large federal government customer came to me because they used my terminal emulator at the time and said, what are we gonna do? Because now we have HSPD 12. I can't remember. Homeland Security personnel directive, something to that effect, telling this organization no more usernames and passwords for all the right reasons, by the way. Didn't really tell them what to do, but told them they can't use usernames and passwords anymore. In that, they came to me and said, well, that's cool. In the enterprise, I use a CAC and a PIV card. That's a smart card for the federal government. But what am I gonna do for my mainframe? And that's where this product was born. So so I just wanted to mention that. But now look at the statistics on the screen. I you know, I'm not a statistics person. I'm not out there to try to fear you into thinking you need to go on the journey, but that center one is what concerns me greatly. So here we are. That OPM breach was thirteen, fourteen years ago, and here we are, and we're still seeing a 71% increase year over year of the attacks that used usernames and passwords. So stolen compromised credentials. Still that bad guy getting a username and a password and getting the data he shouldn't get to. That's what we're here to talk about. What Rocket Software is introducing will help you, my terminal emulation customer, my RocketTE desktop customer, put more layers of defense in-depth between what that bad actor is out there in the enterprise that wants the data and the mainframe that it sits on. So let's take a look and see how we do that. Oh, sorry, Chris. I'm gonna turn it over to you. Yeah. Kinda talk about the solution. Sorry about that. Yep. Yeah. At least they know we're not recorded. Right? Because sometimes I sound like that because I just get on my soapbox and can't get off. So yeah. Sorry, We'll. get to your other over to you. a minute. Thank you, Yeah. Barbara. I was on a roll there. you were on a roll. You'll be on another roll in just a minute. I would. So so what we're bringing to market is a security first terminal emulation solution, and we're calling it the product secure host access. Alright? So there's three tiers. And the first tier is called pro. And this is really where you see your desktop terminal emulation. Right? The Windows native, and you get basic security features, TLS, you know, one dot three SSH, some data redaction, other capabilities. The second tier is called enterprise, and that's where you can manage kind of from a central location, your desktop terminal emulator. You also get some of the things that Barbara's been talking about with regards to, you know, advanced security. But for mainframe, n a s 400. So things like identity and access management integration, multifactor authentication, single sign on. So after you, authenticate to the host, you can actually, sign on automatically sign on to your, host application as well. So that's the enterprise tier. And then the third tier we talk about is anywhere. And anywhere includes everything we've talked about previously. So desktop terminal emulation, central management, and some of the security authentication capabilities, auto sign on. But we add that to the what we call the thin client or the zero footprint client, which is also known as the web client. So you can effectively manage your entire host access estate from a single dashboard or a single console. So your administrators might have, you know, multiple administrators. And you may have thousands of users, and you're able to centrally manage their sessions or configurations, what they have access to, and so forth from that central location. So those are the three tiers of the Rocket software secure host access solution. And that's kind of our go forward strategy product for the for the terminal emulation host access space. Alright. So let's turn it back over to Barbara and go into more detail here, please. Alright, Get on another roll. you can tell I'm passionate about my product. Let's dig in a little bit to those three tiers. Because I'm held to time on this webinar because I can talk about this stuff all day long. I really want to do is concentrate on the sweet spots. There's a lot to this solution, But what I want to concentrate here on is you, my RocketTE desktop customer, and what this offers to you. So when you think about security, When you're logging on to a mainframe and I'm gonna talk about mainframe here just because if I can stay on one one host type, it helps me. But we do this for all of them. So it's not just ZOS. We also do it for I series. We do it for VT connections to a a Unix Linux box. We actually connected Unisys mainframes. We connect the airline GDSs, but I'm just gonna kinda drill down on a one host because it's easier for me. So when you think about that host, that ZOS for example, It has its own IAM. Think RACF or ACF two or Top Secret. That's what your user logs into in their terminal emulation session. But you have another IAM out there in the enterprise. Think what you log into for all your other access to applications in your enterprise. That is what you're you know as your enterprise IAM. Right? Think and I'm gonna throw some names out here, but it's never limited. Think Ping Identity or or Okta, Intra ID. I mean, there's just so many of them out there. But that's what you log in to the Windows world or other applications in your enterprise. And then when you're using terminal emulation, you landed a mainframe screen and you log into RACF, the ACF two top secret. Well, here's the sweet spot of Secure Host Access is we can integrate into that enterprise IAM to leverage another point here for authentication. That's really important because, honestly, many of you may not want to admit to this, but many of you still use an eight character case insensitive password on the mainframe. And that is really just the fact that we've done mainframe security as security by obscurity. It's back there in the back office. Nobody can get to it. Even if they could, they wouldn't know what to do. But we're living in this new world. Right? So so the first sweet spot here is we can integrate with your IAM on the front end. And I'm gonna show you a little diagram here so you'll understand that. So then you can keep your host application access as secure as access to any other application in the enterprise. That's really important. The other side of this equation here, the right side, is this tsunami of regulatory compliance that we're going through right now. I just I will just tell you, I've been doing this for, I don't know, twelve, thirteen, fourteen years. I have never seen this many changes in the regulatory compliance space as I am seeing right now. In fact, we're gonna have to go update the the darn slide. Right? Because that's how much it's going. So so the things on the slide, though, that have recently changed. So DORA came out. Right? That certainly requires multifactor. That's for my European colleagues and when, you know, not just European, but mostly European. NYCRR 500. So that is the New York State regulation that says if you're gonna do business with New York State Financial Services, gotta do it through multifactor authentication. US Federal. Right? They went beyond HSPD 12 and saying you gotta use something other than a username and a password. Now they've come out and said you have to use multifactor authentication. And there's more coming. Right? So we're seeing new mandates come in. Almost every country has them, and most of the states in The US are starting to adopt them. There's at least five out there, probably a few more since the last time I checked. We're hearing HIPAA is gonna go that direction by before 2026 is over. So lots of changes and lots of new regulations. What do they have in common? Multi factor authentication. Why are they doing it? Because they need to make sure that that bad actor out there can't use compromised credentials to get the valuable data. You'll notice I chose my words carefully. These regulations don't care where your data is. They don't care if it's on a system in your enterprise or a system like a mainframe. They require you use multi factor authentication to safeguard that information. We're talking about PII, personally identifiable information. Talking about credit card information. Anything that is sensitive data, need to be protecting with multi factor authentication. I'm going to talk about one more thing here before I move on. The threat of what's coming in the future is pretty scary. When you think about some of the new things that have just come up recently, this new threat of fake workers where they have laptop farms. They're decking them out to make sure that they can look like they're somebody you want to hire. It's extraordinary that these things are happening. What I'm really in fear of and it may have helped them a little bit here but it's what AI is going to do, right? What AI is doing today. A great example is AI is going to make some of those factors a little more scary. Think facial recognition. Look at all those fake things that are out there on the internet where people are posing as somebody else. It's really not their face, but yet if you're using facial recognition. So it's just We're going to get really bogged down here the next couple of years. I see a lot of goodness coming in sight because AI is going to make the threat actors way better at their job and I think they're honestly going to introduce a whole bunch of new ones. We're going to go under this new threat that we've never seen before, it is going to really ramp up. Really, the answer is multifactor authentication across the board to all access to all sensitive data, and then you're gonna have to pay attention to the factors that you're using in that. So just my two bits. So alright. Let's talk a little bit about what the solution looks like. So on the thick sorry. On that left hand column you'll see terminal emulation. Today for you that is RocketTE desktop. This is the secure host access desktop client or the web client. The desktop client is much like RocketTE terminal emulator, but it's different. Right? So so we'll dig into that a little bit because we get changes hard. The web client is a zero footprint client. And that's, of course, if you bought the top tier that Chris was talking about. The secret sauce here is that middle server. And this middle server applies to both thick and thin. It'll serve up your thin client, but it will also allow that integration into IAM. And so what do I mean by that? And, again, I'm gonna go back to adding the fair the sorry. Layers of defense in-depth. What I mean by that is when I launch my emulator today, all I have to do is supply an IP address, a port, hopefully I'm using some encryption, and boom. There I am. I'm at that log on screen to my mainframe, whether that is RACF, ACF two, or top secret. Tomorrow, by adopting Secure Host Access, there would be a couple of additional steps there. One, you would be authenticated by your corporate IAM to know that you are a known, well known, authenticated user of the enterprise before you can get to your host mainframe. Now why is that important? Because if you can't clear that, you're not going to connect. So I'm not letting you get to that screen that you can supply that eight character password if you cannot authenticate via your corporate IAM. Again, think Okta, Ping, Enter ID. Whatever it is you're using, we'd probably integrate with it. Another step is we need to make sure you're authorized. I think if you think about your mainframe access from a secure standpoint, then not everybody in the organization should be able to get to the mainframe. So we're gonna look in your user directory or now we support claims based authorization through SAML or OIDC to make sure you're allowed to connect to the mainframe. So that is just two layers that I have added there. Authentication via your IAM and authorization via your corporate user directory. If you cannot clear those two, then we will stop you in your tracks and you will not connect to the mainframe. So that is really important. Not only we're gonna allow the good guys in, but we're gonna stop the bad guys from getting in. Gets better than that. This product offers you also single sign on to the mainframe. We do this for any host but again I'm just trying to do Z because I need to do one. But we do it for all of them. We can have a trusted relationship with a component sitting on the mainframe. In this case it would be the ZMFA by IBM, and we can have a trusted relationship with that. It's obviously of great value to you because it is doing multifactor on the main frame, so much better than the username and password. But we can do it in a single sign on way, and what that allows is a mapping of their enterprise ID, the user's enterprise ID, and the RACFID, top secret or ACF two. Then we go to ZMFA on the mainframe and we say, Look, Bob wants to log in. Is he allowed? And ZMFA will say, yep, he's allowed. Here's his one time time limited token and Bob will automatically log in. So the complete story here of this journey is I launch so if I am a RocketTE desktop customer today, I launch a client, I will launch a, sorry, a desktop session and I connect to the mainframe. With Securos Access, I launch that same desktop session, I go through my IAM out there in the enterprise. I go through my user directory out there in the enterprise. I've cleared both of those. I'm allowed. I then map my user ID in the enterprise to my user ID on the mainframe, and I get a one time time limited token, and now I'm logged in. That could have been a very seamless login depending on if you have single sign on out of the enterprise. The user may not have been prompted for any credentials at all, but it would have been way more secure because we have cleared so many layers of defense in-depth and it's all integrated to support single sign on. That is just this little tiny bit of Secure Host Access. We do a lot more than that, but Evan keeps my time limited. That is the secret sauce, friends. That's why we're bringing this to market. In a world where the threats are using compromised credentials, this no longer depends on credentials that can be compromised and allows you to integrate with sources that you already have in your organization to make sure that you're adding layers of defense in-depth to mainframe access. Awesome. Okay. Thanks, Barbara. That's very helpful. overview of the secure host access solution. And now let's talk a little bit about, the thick client, the native windows client, and the and the upgrade, you know, to the secure host access desktop client. And so what you see on the right here is a screenshot of secure host access desktop. It's part of the pro offering, the pro tier offering, and all all of the tiers include the desktop client. And what you see here is a screenshot of the ability to run competitive macros, if you will, or macros from basically any terminal, you know, common terminal emulator, popular terminal emulator out there. So we're trying to make the you know, we you looked at the we went over the corporate journey a bit earlier. You saw all the different companies, legacy companies that have been part of the merger acquisition journey and history for Rocket Software. All of those, you know, thick client terminal emulators had their own proprietary, maybe, you know, macro languages. They supported some supported visual basic for applications. Some have a dot net API. But what you wanna be able to do in a lot of cases, organizations wanna be able to preserve those automations as they as they move forward to, you know, the next version or the next solution they're gonna use. In the case of secure host access desktop here, you can reuse, you know, kind of your macros as is without making any changes to them. You can run them as is. And so you can see on the very bottom here of this screenshot, it says RocketTE macro. So you can take a RocketTE desktop macro and run it in the secure host access, desktop client. So that's one way that we're making the upgrade to secure host access, you know, more straightforward, trying to make it as seamless as possible. The product really is built on the latest security capabilities. Right? So whether you're talking really thick client or thin client, you get the latest in security. And for the thick client specifically, the native Windows client, you're getting things like TLS 1.3 and SSH, latest SSH support. And there's a whole bunch of stuff that goes into the encryption. Right? There's elliptic curve, cryptography. There's different ciphers and key exchanges and so forth. All the latest is being supported in the secure host access desktop client. There's a capability. I think you've you've maybe heard of data redaction or heard it called something else. But that is, I think, available in RTE desktop as well. And it's a very valuable feature being able to, take a mainframe application and if there's sensitive data on the screen being able to, you know, hide that data. Right? So, maybe you mask that data, credit card numbers, you know, Social Security numbers, national ID numbers, telephone numbers, names, and so forth. And you can you can configure that in such a way that only certain people could can see certain information. Right? So you have different roles in your organization. Maybe there's a manager who should be able to see a full Social Security number or a a credit card number. And then there's somebody else in the organization who should only see the last four digits of a Social Security number or national ID number. And that's where data redaction and the ability to assign it to different roles is a very powerful capability, and is supported in secure host access desktop. Talked about automation a little bit. So, you know, what you see on the right here in the screenshot is really about the macros, the basic macros, and so forth. But there's also visual basic for application automations. There's also Halaupi high level language application program interface, which is a standard from way back when that IBM established for automation against the mainframe. That's supported as well in in, you know, secure host desktop. And then there's all the macro compatibility I've been talking about here. The desktop client, again, this is an a really powerful feature that you can actually just open your sessions. So you've created a bunch of sessions or files over time that, you know, your RTE desktop users can use to connect to to a certain host with. Well, you can take the secure host access desktop client and say file open and then navigate to some directory that has your automations in it or your automations and your sessions in it. And just run those sessions as is, and they'll connect to the the mainframe or s 400, whatever cut type of system you're connecting to, run the mac most macros as we say here, and then, also support for, you know, custom toolbars and menus. And this is kind of a journey. Right? So we're trying to make this process as seamless as as possible for you, this, you know, this upgrade migration to secure host access. So over time, we're adding more and more capabilities to make that upgrade easier. So a lot of work being done in that area. We wanna make it as easy as possible for you. We wanna give you the best, you know, solution with the most security capabilities on the market. Alright. With that, let's, move to upgrade guidance. I'm gonna pass it back over to you, Barbara. Before I start going down the screen, I think what you're trying to say there as well, Chris, is that this is a comparable emulator to you. We get that it's not exactly the same, but what we want you to know is that you're not going to lose functionality important. And we're trying to make it as easy as we can from our perspective in order for you to upgrade so you can run your things, your sessions, macros, and stuff in place. So so with that said, you know, our Chris and I and and even Evan too, our suggestion is that you start looking at Secure Host Access so that you can make the plan. Right? We wanna hear from you. So so if we have a evaluation copy today. We can hook you up with your salesperson, your account executive, if you don't know who that they are. If you do know who they are, feel free to reach out. We do make account changes every year so it's a possibility it's changed, but go ahead and start there. Then start making a plan. We're going to talk a little bit about the life cycle here in a little bit and that's the other reason why we want you to start making a plan. And let us know how we can help you. This is that email I talked about earlier. Write it down, take a picture, it'll also be in the deck that you get after the show, after the presentation. Reach out to us. It's big not inbox there that 500 people maintain. It's Chris and I. We do our best to respond right away. If for some reason you don't get a response, email us again because that is our plan. But we both travel and we got a lot going on, so there's a very slim chance that we might not respond in a timely manner. Keep hitting us up because it's just Chris and I there. We want to know how we can help you. K? That's really important. Even, like, for example, you don't know who your sales rep is. Just email us at that inbox. We'll figure out who it is, and we'll hook you up with a conversation. So we want you to start looking at this sooner than later for your perspective and so that you know what's going to be available to you as well as ours. I think you're doing PLC, Barbara, Am. I? Okay. I am. Okay. Yeah. So, again, we're not recorded. So yeah. I coulda hit on this on the last side. So What we're doing after the AMC divestiture, it's been a couple of years, we have lots of emulators out there and this is the plan for all of those emulators. I don't want you to feel like you're being treated differently than everybody else because you're not. This is for all the emulators. The timing is a bit different. Right? But we want to focus our innovation on Secure Host Access. That's why we're talking to you today so that you understand where we're going. We're hoping you're going to see some value in that and you want to go with us. You probably received an email in January 2026 around the middle of the month somewhere to tell you that Rocket eDesktop is going into what we're calling a mature status. Now you may not have read through it or you may feel like there's gray area. Here's what I want you to know heartfelt again based on values it does not mean end of life. It does not mean that Rocket Software is stepping away from this product. Not at all. It is about innovation. What we would like to do is we would like to put all of our development resources for innovation into this new Secure Host Access product rather than all of the various emulators that Rocket had, that Rocket had through acquisition, that that AMC had. And there was plenty of them if you go back to that original history slide that Chris was showing. With that said, we get it. First of all, even if you do like the journey and you wanna go along with this, migration takes a while. We have your back. We will do bug fixes, and we will do security patches after it goes into maturity. So that's important. Right? Think if you had a sudden a vulnerability in SSL, for example. We've got you. We will give you a fix for that. So we're not walking away from the product. We just want to channel our innovation on the new secure host access. That's where we're going to be doing new features. Great example, if you come to me and you say, Barbara, TLS 1.4 is now out there and it's going to come at some point in time. I want that for RTE desktop, I'm gonna probably say no, because we're gonna put that into secure host access. So this is why if you go back, we want you to start taking a look at secure host access now to be able to start planning so that those are not tough conversations for you. Again, it's going to go into mature status in January 2027. That's a little bit less than a year from now, so you got lots of time to plan. And even then, once it does do that, you will still get bug fixes and security fixes. We don't want you to no panic here. No need. Could be, although I don't quite understand the use case, there could be a reason why you wouldn't wanna move to SecureWorks Access. And with that said, we will continue to support you from a bug fix and security fix for for the for as long as we need to to make sure that we do the right thing because that's who Rocket is. So okay. So, Chris, now I think I'm turning it back over to you. Yes. You are. Thank you. So, yeah, with regards to product life cycle, you know, Barbara and I have worked on, product life cycles for software products for years and years under different organizations. When we got to Rocket, there really wasn't a consistent set of policies for all products. You have mainframe products, you know, Windows products, so forth. So it didn't really fit into that that kind of the standard template you do for all products for a product life cycle. So we we worked as a team and and and basically built, you know, new product life cycle policies kind of from the ground up based on our experience, and they're available now. So you can go to one of the links available to the product life cycle. It's around here somewhere. But it's it's on the Rocket website. They're new and improved, and they're easy to access and understand. We provide, you know, frequent communications. We're actually gonna do kinda two point o version of the product life cycle update. So we published a version of the product life cycle a couple of months ago, I I don't know, September October time frame. And then we got some feedback from customers and and are making changes to that right now. Those should be published soon to get into more detail. Some customers had customers that had questions that hadn't been answered by the one point o version of the PLC. So we're gonna get that get that updated in the next couple of weeks here. So we, you know, we provide frequent communications via various channels if you weren't aware of these. Excuse me. So you've got the emails that come out. We talked about, you know, getting getting customers informed by sending out the secure host access notification emails. We now have the forum. This is kinda new. So you can check out the forum on the Rocket website, and we'll be there's an area specifically for secure host access. And, you know, we're gonna be giving and posting information there for customers about new releases and product life cycle updates and all sorts of stuff. Don't forget about the doc documentation portal Has all the documentation, the like in electronic form that comes with the product, but it's just nice to be able to have it at, you know, accessible obviously on the on the web. And then we also have the Rocket customer community, is the RCC platform, which is where you get downloads your product downloads and so forth. There's also quite a bit of good product information available on RCC as well. So like I said, you know, we're working on product life cycle, improving it all the time. We just wanna make it, you know, easy for you to look at a product life cycle for your specific product and be able to say, okay. Now I know how to plan my future upgrade to, you know, secure host access or whatever journey you end up going on. I've got a quick example at the bottom here. You know, we we put this little graphic here that says, you know, the product goes general availability. It's gonna be fully supported for, you know, three years. Full support means tech support, a dev support, you know, bug fixes, new enhancements, so forth in the in the GA phase. And then it goes in a limited support for a couple years and then restricted support for a couple years after that. All this these terms and so forth, limited support, restricted support are defined, you know, on the product life cycle page and so forth and and we can share that link with you as well. And again, always evolving, always improving. So if you have, you know, major questions about the life cycle we can either answer answer those or we can make changes to life cycle to to make things more clear if they are not to you. Alright. So we've kind of been talking about some of our commitment to you already but let's let's summarize what our commitment is to our customer base. So we're continuing to you know, we're launching secure host access. It's a great solution, security first solution, and, you know, really is where the market needs to go going forward. All the regulatory mandates that Barbara talked about and so forth. So, you know, secure host access is the go forward solution. RocketTE desktop is going to continue to be supported. We talked about, you know, bug fixes and and security patches and so forth. Those are continue to be delivered. You can move at your own pace to secure host access. Right? One year, five years, whatever. We're gonna we're gonna support you and be there with you. We'll be there, you know, to support you through our kind of our and your modernization journey as we move. And and we think there's it's gonna be compelling, you know, reason there are gonna be compelling reasons to move to to Securos Access because they're just there's just so many, you know, things happening in the market, which Barbara covered very well and in detail where you're gonna need a a solution that can really protect your host assets. Right? All the data that you keep on your host systems that's mission critical. Then, Barbara, I think you're gonna Sure, help us. Yeah. go in here. So, Keep going. Secure Host Access provides the innovation roadmap that you may be looking for, that you probably are looking for. That's the other reason why we're suggesting you get on this journey with us. The product life cycle policies are new we've already made improvements, but I think one of the things that's important is from a RocketTE desktop perspective, I don't think we ever published what product life cycles really what our policies were and how we're going to help you as a customer. We do that now and we also do that for Securos Access. This is kind of a vague statement. There's still some work to do. What does that mean? Well, there's always work to do. We can always improve. I come from an agile background, and we're always looking at make improvement. The couple of areas there that I see is one, of course, with the product life cycle, we're already making improvements there because we've had some feedback, and we're going to adapt to that feedback. But the other thing I think that is fair to you is, let's if you can take a look, you know, earlier with the move from RocketTE desktop to Secure Host Access, we have work to do there on the migration. We don't support every macro macro type right now. We want your feedback. Right? So do we are you using those kind of macros that we don't bring over? Is there another way that we can bring them over? That's an example of what we have to do. Maybe for some reason, the way you use RTE desktop is not well understood by Rocket Software, and there's something there that we're missing. We want to help you, so we need to know about that. So we're opening doors, same email address. Tell us what you like and what you don't like. You can be honest. We got thick skin. We wanna have the conversation with you. We know change is not easy. We know swapping out a terminal emulator isn't easy. But quite frankly, we feel like there's enough value in this journey that you're going to want to come with us. You're not migrating off the mainframe tomorrow. You're going to use your terminal emulator for a long time to come. And that terminal emulator needs to be secure. So so that's why we're doing this. That's why we're having these conversations with all of our customers. So don't hesitate to use, that email address. It'll get to Chris and I. And I think that's probably it for presentation mode and I think we're gonna open it up for Q and A. I'll start. I'll. start with one, Chris. question. Thanks, Evan. So we talk about secure host access anywhere. And a lot of customers, when they hear thick clients, web clients, I think traditionally think about, you know, Java being involved in the web client. What is what how is Java involved in this solution, if at. all? Yep. So great question. And we do get a lot of customers that ask that because Java was the way you would use a web based emulator for many years, but it is not the case with Secure Host Access. The Secure Host Access is a zero footprint emulator, and the sweet spot about that is it can run-in any modern browser, and it is HTML from the server to the browser. So why do I say that? Because I'm always thinking about security, and the closer you set that Secure Host Access server to your mainframe, the shorter distance the thirty two seventy traffic will move. And and more importantly, the thirty two seventy traffic or fifty two fifty or whatever host you're supporting doesn't leave the server. It's HTML that leaves the server. So that from a security perspective, that's great because you're not seeing that data stream on the wire. No dependencies, Java included, any modern browser, really no desktop dependencies at all. Great. And then there's this question about regulatory mandates. So you said something about it doesn't really matter where the data lives anymore. I think in the old days, you know, five years ago, the mainframe was kind of exempted in a lot of cases even though, you know, mission critical data is on the mainframe. So you talked a little bit about a couple of regulations, but can you be a little more specific with regards to maybe HIPAA or p PCI DSS or the New York the new New York regulatory mandate that talks about, you know, specifically protecting data no matter where it lives. Yeah. So I think we all believed that the mainframe was okay to be exempt because it was inside of the firewall. So it was nobody accessed it from out in the Internet. And so I think it was our own perception that the mainframe wasn't subject to those requirements. And at the end of the day, it really isn't true. The requirements are the requirements, and it doesn't care where your data lives. Don't think we've talked about it, I'm pretty sure IBM states that 90% of credit card transactions take place on that mainframe. Well, right there it says that all of these regulatory compliance that we're seeing with the big ones are requiring multi factor and PCI DSS. If you have credit card information on the mainframe, you're subject to that. These regulatory mandates do not care where the data is. They care what type of data and this is sensitive data. For me, there's three categories of sensitive data. Two that are generic and one that is more owned by the organization. Owned The by the organization is like your IP, your own intellectual property. And of course you're going to want to safeguard that. But the regulatory compliance really talks about sensitive data and that is either personally identifiable information or credit card data. Quite truthfully, there's not a real good definition, if you will, on personally identifiable information because it's anything that could hook to an identity. So, you know, while you might think, you know, your ZIP code shouldn't be personally identifiable information, it is one of the ways that you say, yep. That's my credit card. Right? So that's your ZIP code is becoming more and more important and it is hooking you into the personally identifiable space. So so it's about sensitive data regardless of where it resides. So it doesn't matter. It doesn't dictate, oh, if it's in a Oracle database or if it's on a mainframe or if it's it doesn't care. It's. wherever the information that you're safeguarding is, including a mainframe. Yeah. And I think that's an interesting shift, you know, in our market with, regards to mainframe and the shift is in perception. I. think it's always been that way from a regulatory standpoint, but I think we, as people involved in mainframe organizations, had to change our perspective because you know, and for all the right reasons. Right? We are extending our mainframe out to new areas. That's what modernization is all about. Yeah. But we have to protect that information at all costs. Yeah. No. Great points. Thank you. And then this other question that comes up so frequently because when you show you the network topology of secure host access. Right? So you you're gonna implement the solution that that has a server kind of in the middle for that helps with the negotiation of credentials and so forth in the IAM and then do multifactor and single sign on automated sign on to the host. Well, customers, some of the first questions they have are things like, okay. Can we do cloud? Can we do high availability? Right? What what is the capability that this server has? So can you go into any details about that. that, That's a great question. access server? I think we think about high availability differently from a desktop perspective than we do from a server perspective. Remember, even though it feels like it's a new product, it's really not. It's been out there for over ten years and we've got a lot of very large organizations that have already got it deployed. We have three deployment models. We can deploy on prem, we can deploy in the cloud, it does have high availability all over the place. We deliver a software appliance that you can just put in any VM infrastructure and it's supported there. That's the easy button, if you will, right? Because it's kind of simple to deploy. A lot of my customers don't really want that because what we ask you to be careful there is we don't want you putting more software in there because we're the software in that virtual appliance. So and we'd have to ask you to remove that software if we went to troubleshooting. So a lot of customers like the bring your own Linux. If Linux scares you, don't worry about it. It's just getting it onto the OS, then we all have a graphical user interface from then on. I I have a lot of testimonials from a lot of my Windows customers that that really scared the daylights out of, and now, and they've got it deployed and they're very comfortable with it. In fact, one of them said to me the other day, I'm not going back. Not going back. And then the third option, which is fairly new, is we so inside of our Black Box, inside of our product, it is containers that come with orchestration. So what we now offer is our containers that you can deploy in your own orchestration tool. Think Kubernetes. While I thought that would only be of interest to a couple of you, wow. Lots of people are really interested in that. From a high availability, we're going to have to have a conversation because we need to understand what high availability means to you. Is that across servers? Is that across geographical locations? Is that across data centers? Is that across zones in the cloud, for example? But we can deploy amongst all of that. The licensing here is pretty simple. It is named user or concurrent user. It does not limit you on how many servers you can deploy. So we have we have customers that have very large deployment either in the cloud or on prem via multiple geos, and we can support it all. And and in the end, if there's a business disruption due due to a server going down, they can get back up and running very quickly. Oh, it's really cool because it's scalable inside. So, actually, by Bing containers and orchestration, it will detect that a server went down and bring another one up. So so there's lots of ways to implement the solution that absolutely will protect you from having a user disruption. The other thing that's kinda cool is on a on a desktop, you launch a session, and and you are completely separate from the guy next to you launching sessions. When you're using Secure Host Access in a web environment, we can change the server on the back end and all you do is disconnect and reconnect, you're on another server and you didn't even know it. So so it really does make for business continuity when when you got lots of end users in a situation where they have to stay connected. Very powerful, sounds like. And then way, sorry, yeah. one more thing, is. you can use both. Right? It doesn't limit you. If you're on anywhere, you can use both the thin and the thick. We're not limiting you. It's by the user, but that user can use one or the other or both because it's the user that has the license. That's important too. Think COVID Yeah. where we all had emulators installed on our desktops and we all moved home and I didn't have my emulator anymore because I wasn't on a laptop. My workstation stayed in my office until they figured out how to get them all home. So. I could have launched it via a web based emulator. So so disaster recovery is a great way to think about SecureWorks Access Anywhere. And and that's a great segue to really the final question which is can you really manage your thick and thin host access estate from a is it from a single console or do you have to have two consoles or, it is from one console and somebody out there might say, what the heck is he talking about? So where I try to draw your thoughts are if you have a thin based emulator, right, you're managing that from a console. You're so you're setting up the sessions. Is it TLS? Is it, you know, what host does it go to? Blah blah blah. You can do the same thing for thick. That's what's really cool about this solution is you can manage both thick and thin from the same console. And here's the other cool thing is remember when we changed? Remember when we had to go from SSL, maybe the earlier versions of TLS to the. later versions? If. you were on a thick client, that meant you had to go out there and change every session. We can do that from the administrative console one time, and the end user will just pick that change up the next time they come in. Wow. What a benefit. So, yeah, there's a lot to unpack here, which is kinda why we're asking people to take an early look. Awesome. Think, that's all the questions, Evan. yeah. No, this has been great. Thank you so much, Chris and Barbara. Really, really helpful. Everyone who was here to attend, thank you all for being here. As they mentioned, we will make sure that everyone gets the recording and the deck that was shared so you have those to reference later. If there are questions, please reach out. The email address is here on screen. Yep. So please, we're here to help. We wanna make sure we make this very beneficial for everyone. So if there are questions, please reach out. Otherwise, we'll we'll hopefully hear from you soon. So thank you all for being here. Thanks for your. time today.