Name: Rocket Customer Webinar: Rumba Lifecycle
Uploaded: 2025-10-22T18:01:29.603Z
Duration: 57 min 48 s
Description: Rocket Customer Webinar: Rumba Lifecycle

Transcript for "Rocket Customer Webinar: Rumba Lifecycle": Hello, everyone, and welcome to our session today. I am Evan Tackett. I'm the solution marketing organization here at Rocket, and I have the pleasure of looking after Secure Host Access and all of our various terminal emulators. And it's it's really an exciting time to be here. We're doing a lot of really cool stuff, and, I'm excited to be talking to you about it. But, I am joined today by our principal product managers, Chris Wall and, Barbara Ballard. So, I think I'll just use some housekeeping quick and then hand things off. We really want this to be a very conversational session, very open, and if you have questions along the way, feel free to send them along. I'll keep an eye on the q and a panel in the chat, and I can raise questions to Chris and Barbara along the way. And if not, that's okay. We can get to that at the end, or you will also see a, an email address that goes direct to Chris and Barbara to to get questions if you don't wanna send them along in the session. So you will see that in a few slides. But I think for now, I'm gonna hand things off to Chris. Sounds good, Evan. Thank you, and thanks everyone for joining today. Welcome to our webinar on Rumba Plus desktop and our new offering, Secure Host Access. Let's go to the agenda and quickly discuss what we're gonna go over today. So, gonna give some history on kinda how we got here. Kind of an interesting thirty year look at the terminal emulation space and, you know, how we got to Rocket. We'll look at what the path forward looks like. It's very exciting, with the Secure Host Access solution, which hopefully you've got an announcement in email from, Rocket, on. And then, we'll talk a bit about the product life cycle because folks obviously won't understand how they're gonna be supported going forward, with with both the legacy products and and the new, Secure Host Access solution. We'll talk a bit about our commitment, you know, to you during this process. And then, of course, we'll handle questions as they come up during the presentation and towards the end. With that, let's start with a, disclaimer. We also have to start with the the legal stuff. Right, Evan? So, basically, what we're telling you today, is true as best that we know it is as it exists today. Things will probably change in the future a bit, and, you just need to be aware of that. That's really the message we wanna give here. Just a little disclaimer. If you, you know, wanna read all these, words, feel free to watch the recording and and maybe pause it because you probably need to. But, yeah, just a quick disclaimer on that. Thanks, Evan. Alright. Let's talk about our history, and I like our little, we sometimes call this, the ant farm because of all the little, tunnels that go from every direction that it appears to be. But this is really a representation of our, you know, the Rocket corporate journey as it exists today. So if you look at all the different, you know, tubes here, the at the end of them are the heritage companies that kind of fed have fed products into Rocket. So there's OpenText and Micro Focus and Attachment and NetManage and and, WRQ and, of course, WAL Data for those of you that use the Roomba product. This is a product that came about, you know, in the nineteen eighties and is still relevant today. And you can see through all the acquisitions, well, data NetManage, Micro Focus NetManage, and then coming together, you know, with OpenText, and then finally, Rocket Software Software last year. So quite a corporate journey. It probably, you know, is similar if you were to draw out your company's corporate journey. Probably be something like this as well with a lot of different companies coming together, a lot of different products and so forth. And this this is just kinda where we came from, and it's good to understand the history. And then, you know, now we're gonna talk about where we're going. And as we do that, I'm gonna hand it over to Barbara to talk about the wonderful values. Yes. So as a Roomba customer, you've been through quite the journey, and now you are now with Rocket Software. And this is not, I just this is a heartfelt message for me. Right? Because I I've been through that journey with you. I was part of Micro Focus. Before that, I was with AttachMate, and and then Micro Focus went to OpenText, and and now you're with Rocket Software. And, what we just really wanted to articulate here, as our customer, you are in a very good place. Rocket Software is a really cool company that values their customers, values the customer's input. They are customer focused, which is actually why we're introducing this new product. And I just I just want you to know from me that you're in a good spot. Probably a better spot than you've been in years as an emulation customer, using Rumba. So so I want you to know that. You're you're gonna see, some things in this presentation where we're talking about the future. But the cool thing about Rocket is that there this is not a required change. This is not we're not forcing you to go here. We think there's huge value in what we're offering you, but we also get the changes hard. And I think that's what's different about Rocket is we really do understand our customers, and we don't dictate what our customers do or use or those kind of things. What we're hoping to do is provide value, in this journey that we're going on and that you'll come with us. But the most important part is that, we're okay if you don't wanna go on the journey with us. So, so that's where this is coming from. And I I would also say as an employee, Rocket, is a really good place for the employees. So Chris and I have been around this for a long, long time, and everybody now from employees to customers really are in a good spot. So Rocket's a great company to work for. They really value your your input. So, so now let's talk about the future, Chris. Sounds good. Oh, and maybe that's me that's gonna talk about that future. That's well, at least you know it's not recorded. Right? Because we're just Chris and I are just doing these all the time. So alright. So the journey we're about to take you on, the reason why we're doing everything that we're doing in this new product is really because of the state of security and compliance today. I mean, it is just it's just amazing if you if you and I'm sure you do listen to all the news. Right? Well, not we're not talking about the all the news. I'm talking about cybersecurity news. Right? It is just every week, something new is happening. And not only is it something new, it is big things happening. It is different things happening that were happening six years ago. I mean, a great example is just it was just I was out on vacation last week and, and while I was out, a very large, not customer, but a very large organization. I don't name names. But they were attacked by a state sponsored bad actor. That's just that is different than where we were before. We used to worry about some bad guy getting our username and a password and coming in and, and absconding with our personally identifiable information. Well, now it's people that are paid, to come after you to get your personally identifiable information. So it's it's just it's just a different world. And then when you think about what AI has to do with that and how AI is gonna influence the cybersecurity landscape, it's even scarier. So, the good news from an emulation standpoint is we've been thinking about this for a long time. I I actually have my last ten to twelve years has been concentrated on how do we take that emulator and bring it into the enterprise security world. Right? How do we protect the host that you're logging into by more means than just what you have on the host itself? And that's what we're gonna talk about with Secure Host Access. So, but one thing I wanna call out so these are lots of lots of different, statistics. But the one thing that you should know is that regardless of who's coming after you from a bad actor perspective, they are using usernames and passwords to do that. Whether they attack you to get them, whether they buy those off the dark web, or the latest trend is that you hired them and you gave them credentials. So so it's just this what we're trying to help you do as a mainframe organization is add more layers of defense between who is logging into the mainframe or other back end host and the back end host itself. So so I hope that helps a little bit. But it's really based on all of these, statistics that are in front of you. Right? I mean, it's just the the it's just changed a lot. The other thing I will also call out is that, 40% of the incidents in 2024 were application level attacks. Right? So that's where a bad guy gets in and they go after the underlying applications, not necessarily, you know, going after your data. They go aft and the reason why that's important to you is because they could go and detect it. It can last a lot longer than you would think it would, so they have a lot more access to a lot more things. So and you have to protect against that application level attack. So so, anyway, that's enough about statistics. That is the state of security, and and, honestly, it's only escalated over the last ten years. But that is why we're introducing secure host access to the market. So let's go ahead and change the slide, and then we'll talk a little bit about oh, no. We won't. So, Chris, sorry. Again, we're not recorded, so I'm gonna pass it back to you so you could talk a little bit about the tiers in this application, and then we'll kinda talk about how it fits into a an organization. Sounds good, Barbara. Thank you. And that's great background. And everything you just said is why we created this, secure host access, security first terminal emulation solution. Right? So we've got, if you if you think about RumblePlus desktop, that's really like the first tier. Right? The the pro tier is the desktop terminal emulator. Right? And it's got the basic security features, TLS 1.3, you know, FIPS validation, you know, maybe SSH encryption as well, maybe some other security capabilities. Right? Locking down menus and toolbars and so forth so users can only access certain, functionalities within the program. So that's that's the pro tier. What we're moving toward is more security focused capabilities, and so the second tier is called enterprise. And and enterprise really allows you to take that desktop terminal emulation and add modern security to it. So identity and access management integration, which once you have the integration with your I IAM solution, then you can enable functionality like multi factor authentication, single sign on. You can centrally manage your, terminal emulation estate. Right? You can manage your RAMBA desktops or your Shaw desktops. That's the concept. And then with the anywhere tiers, you move to the right here, you're getting that all that functionality I just mentioned, plus you're getting the web based client, the thin client. And you're getting capabilities like being able to manage your entire terminal emulation estate from single dashboard interface and administrator would do that. And And you're gonna have users that are casual users of the mainframe or other types of host systems. You're gonna have users that are power users and they're gonna have different needs. Some some are gonna use the thick client, some thin. You're gonna have new regulatory mandates that say you have to implement and protect data no matter where it lives and this is the type of solution and these, you know, what's available in these tiers, if you will, of secure host access is what is going to enable your organization to adhere to those regulatory mandates. And with that, I'll turn it back over to you, Barbara, to talk about some of that. Alright. So, this product does a lot, and we only have an hour. I could I could spend three or four hours just talking to you about all the stuff that's in here that you don't have today. But we don't have that kind of time, and that's not what you're here for. So I'm gonna highlight really two points, that is really the the hot topic or secret sauce, if you will, about this application. So, so the first thing on the left hand column, excuse me, is our ability to integrate your enterprise IAM in this path between your between a end user trying to log in to the mainframe and actually logging in. And So what do I mean by that? So, think about how you log in to Windows today and other applications in your organization. That's traditionally done through, you know, a a SAML login. I mean, today, the, you know, the words you might be hearing is intra ID, through Windows Hello, through, various forms of authentication. And in the enterprise, most organizations, and I hope it's true for all of yours, but most customers are using two factor or multifactor authentication. Why? Because it's absolutely more secure than a username and password. Two, because you have so many applications to log in to, and your cybersecurity team in your organization is trying to protect all the assets. But that's not the case on the mainframe. So we'll talk about that in a little bit. Right? So so that is our secret sauce is we're able to tap into what you already have and leverage your IAM to add a layer of defense between the person logging in or the bad person logging in and the login itself, the the green screen application. The other side of this slide is really what, Chris was talking about is we're in this a period of time where mandates are being updated and new ones are coming out. So some examples of that is, from a from an upgraded perspective, PCI DSS. Right? We've all been living with PCI DSS for years and years and years, and they and they oftentimes update it. And they say, you know, these are the best practices. Right? You should be using redaction. You should be using encryption. You should really be using multifactor authentication. Well, the world changed on, March 31 of this very year, and that's because version four came out and didn't say you should anymore. They said you have to. They have to or you're not in compliance with that regulatory policy. And there's a lot more coming out than just PCI DSS, but that's an example of one we've been living why, but they we've been living with, but they've changed the rules. Gone from best practices to mandates. Now there's also new ones coming out. New York State has a regulation requiring multifactor authentication. That's the NYCRR 500. That came out. It came out last year, and there is a, there is a period of time in that regulatory requirement that depending on your use case in there. But the the end of that period of time is 11/01/2025. So, and that's, like, next week. So that's when it becomes a mandate. There is no period of time anymore. You're not in compliance if you don't have multifactor, and you're doing business with the state of New York. So state of New York financial services. US Federal has been requiring this for a long time. That's how I got in this game. If you if you think about about it was about twelve, thirteen years ago. It was called the OPM breach. That was one of the first ones that where a near dwell got a username and a password. They logged into a system, and they got stuff that they shouldn't have got. It was personally identifiable information. It was my information. I'm a vet, and and it really irritated me as a consumer. Right? And what happened then over the next year, we had our large US federal government customers coming to us and saying, look. You know, we now we we have to secure all the systems, and that includes, the mainframe. And it's hard to put multifactor on the mainframe. And even if it's not hard, it's different than the one I got out there in the enterprise. So what do we do? And that's that was really, how we got to secure host access. But the other thing that was a game changer for them is that's when it was called HSPD 12 came out. That was a mandate that said no more usernames and passwords. That's all it said was no more usernames and passwords. Didn't say what to use, but it said no more usernames and passwords. Well, now twelve years later, we've got The US, cybersecurity mandates that say, you need to use multifactor authentication if you're doing business with the US federal government. You need to use encryption. You need to use redaction. So, so the things are changing, and they're not gonna get any easier going forward. So this is this product is trying to help you from both a best practices standpoint and leveraging what you already have, which is your IAM, and dealing with the mandates that are coming in in what I call a tsunami, requiring multifactor authentication, which you likely already use in your enterprise. So so that's really where we're focused. Oh, last thing I'll say about this slide, kind of an interesting fun fact. When we first started down this road and we first started talking about this product, we actually got in front of a customer, and we were talking about it. And and I'm gonna show you a a a little architecture diagram in a bit, but we showed them the architecture diagram. But we also, actually demoed the product and how it worked and all the integration end to end, all the way from the end user logging into green screen all the way to single sign on at the host. And a person at this company said, oh, my gracious. This is phishing resistant, passwordless, secure access to my host applications. Why haven't you told me about this before? Why didn't I know? And that, that was actually directed at IBM because we were part of the IBM conversation. But I took that pretty seriously. And so since then, that was a little over a year ago. Since then, we really have been talking about it a lot. You might have seen some of our webinars out there. We've been doing share webinars. We've been doing webinars on other platforms, and we're trying to get in front of customers because that is exactly true. It is phishing resistant, passwordless, secure access to your host applications, and you need that. So, so I just wanna let you know where that information came from. It was not a marketing phrase that came up. It actually came from one of you, the customers that I service. So alright. Let's go look at the market texture diagram. So this is what it looks like. And I'm I'm talking to you as my Roomba customers so that you kinda understand what the value is that you would get by moving into this. So as a Roomba plus desktop customer, you have an emulator sitting over there on that left hand column. And like Chris alluded, that's really what the pro tier is all about. It's a thick client, and and and Rumba looks a lot like, what that thick client looks like. It's actually based on, a product that, was called reflection desktop, but very, very feature rich, which Rumba is as well. A lot of the features you have in Rumba are in, in this thick client. So, so you have the thick client, but you also, in this product, also get a zero footprint client. So that's kind of important too because I think a lot of my customers are looking at how do I give access without installing something on the desktop. You know, a lot of people like to use web based apps because that's kind of the new thing. And, so they'd rather have that than a Windows based application. So you you have that as well in this product. It is HTML. So that's an important consideration because there's no requirements for you to install something at the desktop. But the secret sauce comes in the middle of this, diagram. So that is where the secure host access server sits. So as I said on the last slide, we allow you to integrate this server into your IAM. So what does that mean? That means when I launch my emulator, rather that is thick or thin, I have to go through my IAM to be successful as an end user. So so let's talk about that from an authentication perspective. That means I need to be able to authenticate however you authenticate today in your organization. So think I mean, you could the vendors, you know, there's so many vendors out there. Ping, Okta, Duo. There's just so many. But it's really specification based, and that's important because that means we can feed into any vendor. Right? And I say any. I gotta be careful. I'm not a salesperson. I'm a product manager, and there's always that slim chance that you could come to me and tell me you have an IAM that I don't feed into. But I haven't had that yet, so so let's have the conversation. But what that means is that as I launch my emulator, I will be challenged for authentication in your IAM. So that two factor authentication, for example, or that even more than two factors. However you authenticate to your other apps in the organization, that's how you would authenticate for your, emulation. Now I so I'm let me go one more step, and then I'm gonna come back to that. Then the next step, because that's not only what happens in an enterprise, you also need to be authorized to get to that application. And what I mean by that is we're gonna go look into your user directory and make sure that you, as end user Bob, actually require access to the mainframe because most people most organizations, not everybody in the organization needs or has, you know, a a role that requires access to the mainframe. So so now going back just a bit, you've authenticated and you've been authorized in your organization's IAM, and then and only then will you be allowed to connect to the mainframe. Now the one thing I wanna because it's always worrisome. Right? Oh my gosh. I'm now gonna, you know, make this user jump through more hoops. If you use a single sign on technology out there in your enterprise, we abide by that. So we're we're we're deferring off to your IAM. If your IAM says you're good, then then we trust your IAM. That's what it's there for. So so what I mean by that is a lot of companies, including Rocket, use a single sign on type of technology. Think OIDC, SAML, Kerberos, to where I log in once and then for a duration of time set by your organization, I don't have to authenticate again to log in. And so we honor that. So it doesn't mean that we're gonna be prompting every end user that launches their emulator to authenticate because they likely already authenticated either to Windows or to another application. So I just wanna put that out there. So that's the front end of the secret sauce, but I got back end secret sauce too. So most organizations that I talked to today are doing, authentication to the mainframe via a username and a password. And, by the way, when I say mainframe, in this conversation, I'm talking about the z o s mainframe. But, really, we we connect to a lot of mainframes, and I can do this, on any back end host. So it just the, you know, the components might change, but but it's available for any host. So it's 400, Unisys box, all of that stuff. So, so so what would happen is when I launch my emulator, I land at a mainframe login screen, and I'm supplying my authentication on the mainframe. That could be a username and a password. Oftentimes, it is. I will say we got lots of customers out there that are looking for MFA options on the mainframe. Valid. But what we can do from a secure access standpoint is we can actually make that login stronger if they are using a password and easier on the end user and the administrators if, if they're using a password. And so the reason why I say that is we can have a single sign on experience to your mainframe. So what that looks like is our server is, connected in a secure way. We have a relationship with a component sitting on the mainframe. The one we advise the most is zMFA, sold by IBM, but there's other ways to do this as well. We have a secure relationship there. And so what we do based on that secure relationship because nobody should be logging in with that mainframe unless the mainframe knows about it and authorizes it. But we map the enterprise ID. So my bob at Rocket to my rack f ID or a c f two or top secret, which may be, Ballard, you know, at whatever. We map those two. And so what that looks like is I log in with my enterprise ID, and on behalf of that login, once I'm successful there, instead of logging into the mainframe between these two servers, I will have a onetime time limited code that is passed back to the end user in an automated fashion that allows me to log in. More secure than a password, not reliant on the password. So think about how many password resets you do. Not reliant on a password anymore. The end user doesn't have to remember it, oh, or write it down. So way better. So that is the other piece of our secret sauce. And, again, this is why I told you I could talk about this stuff for hours and hours, but Evan kinda controls me and only lets me talk for a few minutes. So these are the highlights that you would be getting in Secure Host Access if you adopted this solution. Right? So this is what you would get in addition to what your thick client gives you today in Rumba. So with that, I think I am passing it back. Am I oh, yeah. Pass it over to me. Address. Okay. Yeah. Thanks, Barbara. Keeping track. I And then Barbara Barbara and I are both old timers, and we we still use a s 400 to describe the IBM I system. Right? Or no. No. That's good. All good. The I series. Right? We've been through many changes on that side with regards to marketing, and I still because I'm from the nineteen eighties. Right? I'm I'm I don't call it a system 36 or 38, but I call I typically call it an AS 400 just like you. So, yeah, thanks for that background and marketing. Sorry. Sorry. Sorry. Yeah. ISeries. Yeah. Right. That's another way to say it. So no organization likes to, you know, make change and do upgrades of software and so forth, and you've got a lot of applications deployed, and we recognize that. And so we're trying to make it as simple as possible to move to the new Secure Host Access solution. It's a relatively straightforward upgrade to Secure Host Access desktop from Rumba Plus desktop. K? So the the Shaw desktop client can run Rumba user configurations, sessions. So if you've got an existing, you know, mainframe, s 400, I series, IBM I session, VTSSH session. You you know, Shaw will open those up, the run ones from Rumba, and run those and connect to, you know, host systems. You don't need to make any changes. You just need to open up the file within the Shaw desktop application. And same with macros. And that's illustrated here on the screen. Right? I've got a screenshot here. This is a screenshot of Secure Host Desk Access Desktop, and all the different types of, different terminal emulators, macros that you can run from within Secure Host Access desktop. And you can see I've highlighted in this purple box, a Rumba macro, and then there's a bunch of other types there that, secure host access can run out of the box. There's no conversion necessary. Right? You open the macro and the automation runs. It's kind of a, cool capability. Makes it much easier, you know, to move from, Rumba plus desktop to secure host access. So the the some aspects of the upgrade experience are very seamless and others require some manual tasks and to use, you know, printers printer sessions as an example. So we talked about terminal sessions before. Those Those are the ones that open. You can connect to host systems, you know, without making any changes. And then there's printer sessions, which we don't migrate today within Secure Host Access, and we could potentially. And what I mean by printer sessions is like a thirty two eighty seven, printer emulation, you know, mainframe based printer session that you've created in Rumba that won't necessarily be openable by secure host access and then, you know, connect to, the host system and and connect to printer session. So there's some things that are outstanding. I think we cover today probably, you know, the core things, the core functionalities that you use within the product. We probably cover 60 to 80% depending on, you know, which things you're using within, Rumba. We cover those things in Secure Host Access, desktop, and, with more to come. Actually, we're working on a few other things. We just released service pack three. So, Rumba Plus desktop 10 dot two service pack three was released this week. In case you, haven't received the email notification yet, that is coming soon, and it will show you how to, it will, inform you how to download, Rumba 10 dot two service pack three, from our download system, which is called Rocket customer community or RCC. So be on the lookout for that. And then, some notable dip notable differences, you know, with regards to kind of the look and feel of the product When at the time that you move from Roomba to Secure Host Access, you're gonna notice, you know, obviously, the company name is different. So we've done some rebranding. It's you know, we're Rocket Software now. The product name is different, obviously, and then, hopefully, you like the color purple. Because that's gonna seem a little more purple than you used to see. But, and you can change the colors if you need to, but, the default color is gonna be purple. So those are some of these things you're gonna, you know, experience. Just inform you know, good to know, as you move, Rumba to Secure Host Access desktop. I think the other thing and we're gonna cover this a little bit later. You know, we're gonna this is kind of a journey for all of us. Right? I think we mentioned that at the beginning a little bit, and, you you know, we're gonna be here for you, and and we're here to answer your questions. And we know it's gonna take some time to go through this process, and and, you know, we're we'll go through it together. Again, we're gonna talk about this a little more during the product life cycle section, which is, I believe, next, Evan. I believe it is. Yep. And then Barbara gets gets to go again. Yeah. Oh, k. Screens are moving around. Okay. So you are here most likely because we just sent you an email, on October 7, and that was to inform you that Rumba desktop will be going into what we're calling a mature status. Now this was not to alarm you. This was not to scare you. This was not so that you thought, oh my goodness. They're gonna end up, like, my product. That is not what this is about. This allows so if you think about what Rocket has today, we are a merger and acquisition of many, many, many, many customers who all had emulation for years before Rumba came over to it. They had been doing, you know, Passport and all of these other emulators. So there are actually 17 emulators that reside under the Rocket company. So that's a lot. And we and this maturity is happening to all of those emulators. And what it allows Rocket to do is focus our innovation development, the, you know, the the go forward looking, all the things we're gonna do that make the product better for you as our customer. We're gonna focus that development in Rocket secure host access. And and that's important because we can't do that 17 times. That's really one of the foundations of why we're making that move. So maturity is happening. You will see on the screen and in your email that we give you a year's notice that that's happening. But here's what I want you to know, is it's not end of life. That is not at all what we're saying here. What we're saying is we're not gonna do major new features and functionality in Rumba desktop. You will continue to get, annual releases. We've got your back when we're talking about bugs and security patches. You wouldn't have to wait, for a year to get a security patch. Right? We're on that. We're actively making sure that you get what you need. But the innovation part, the new features, the enhancements, those will be going into, SecureOS access, and they will not be going into Rumba starting, October 2026. So I just don't want you to think that, oh my gosh. You know, you're forcing me to go to this other emulator. We're not. If Rumba does what you needed to do today and you're not looking for innovation, then you can continue using Rumba. I believe, personally, being around for this long that really secures to access has a lot of, features and functionality that you're gonna wanna participate in. Understanding the the cybersecurity climate and the compliance, the mandate compliance climate that we're living in. But this we're not pushing in there. This is not a you have to upgrade. So, we just think the journey will present enough value. So what I want you to know from Chris and I as PMs is we're not end of life in this product. We're not walking away from it. As Chris said, we're delivering service pack three this month. The plan will be to deliver a service pack like release annually. But, of course, if there's something that comes up some devastating bug or a new OS comes out that, you know, Rumba doesn't work on, you know, and and what I mean I don't mean, like, new OS, like, something whole wholly new, but but more like, Windows 11 maybe has an update or Windows 12 comes out. Chris keeps track all that stuff. But we we expect you to be able to keep using our product. So we we'll have those and then and then, and then security patches. So but the plan will be for an annual release, and then we'll handle anything that is, that is, you know, require something out of that band. We'll handle that as well. So so that's what I want you to know from Chris and I is that the product's not end of life thing. It's go forward. We're still we still got your back. And we really believe that within a couple of years, most of you will have upgraded to Securys access. So, so, but but we don't want you to think that that is, that you have you have to do that because we're telling you to. So we think there's value there. Alright. I think I'm passing it back to you, mister Law. Sounds good. Thanks, Barbara. So yeah. So we've been working on a product life cycle that makes just makes sense. So you we've got a bunch of terminal emulators, and then we've got the new secure host access launched. We wanna make sure folks understand, you know, how they're supported, what the support looks like going forward under Rocket. The first thing to note, we've been working on this for quite some time, and, you know, basically, we were looking to, you know, publish a product life cycle. We didn't have, really any, template to follow when we got to Rocket because, you know, different teams were using different product life cycle policies. And so, it took us a while to get these published, so that's why I put an exclamation point on this bullet is that it took us a long time to, you know, coordinate with various teams and so forth. We finally got that published. It's been up for three or four weeks now. That is a public facing, product life cycle website, web page. There's multiple pages, actually. And you can search on the product of choice. In in our case here, it's gonna be Rumble Plus desktop and see the different versions and what the, you know, future looks like for them. So the the life cycle policies are new and improved. They're improved in many ways. I mean, we just there's just no way that you can, you know, fall out of support and not be able to call tech support and not be able to get resources online to help you. You got you know, the policies are published. They're easy to understand. There's a there's a team that, you know, can help you anytime and then the tech support, customer support team. We provide frequent communications whether it's via email or the forum or the, what we call the docs portal. It's the documentation portal, docs.rocketsoftware.com, has all, new information. So, for example, you know, the we just released this this Rumba service pack SP three and the read me file, the new docs and so forth. They're they've been updated and are available on the docs portal. So some of the, you know, PLCs, the product life cycle policies were not, consistent or made public under Rocket. So, and and across all host terminal emulators. And so now we've got a consistent policy. First, there's the emulators that can go into maturity, which we talked about, and Barbara talked about that being October for Rumba. And then as customers move to Secure Host Access, it's a very well laid out multi phased product life cycle policy that starts with the standard support general availability, which gives you full support for any product release for years one to three. And then after years, you know, after year three, then we move into the product version, moves into limited support for years four and five, and then beyond that, year six plus. There's restricted restricted support. So some services, you know, go away with each as as the product version moves into each phase, but, you know, you'll notice that there's a lot of great services for a very long time for every version that we release of the Secure Host Access solution, so you should be very well supported. So with that, let's talk a bit more about, you know, our commitment as as you're moving, you know, over the next couple years from Rumba to Secure Host Access. So I'll cover the first couple of bullets and then Barbara will take over. So, I think Barbara illustrated and talked about this really well. You know, Reflection is or sorry. Reflection. Now there are, emulator that we have under our portfolio. The Rumba product will continue to be supported. That's just, you know, straight fact. You I'm sure you've experienced that. You call support, you know, you go online, you find the information you need. You need a bug fixed, you know, you get your fixes, so forth. You can move at your own pace to Secure Host Access. Right? Like Barbara said, every year we're doing this this cadence of, you know, updates to service pack. We just released s p three. And then we're gonna support you through your your and our modernization journey. A lot of this stuff is new to us as well. Barbara went over kind of what's going on in the, security world in general, and we're responding to that by bringing secure host access to the market really to address all those things. And and all the enterprise customers we work with doesn't matter what vertical, horizontal, whatever they're in, finance, manufacturing, you know, insurance, the, whatever, retail, they all are having to adhere to these, you know, regulatory mandates, multifactor authentication, protect the data wherever it lives. And so, you know, it just makes sense for us to release a secure host this secure host access solution to the market to help you, you know, protect your your host assets. And, Barbara, I'll let you go with the next ones. And Secure Us Access will provide you an innovative road map. So what do I mean by that? So when you think about more things in security land, a a great example is, you know, we have been kinda moving through this, process for the last, I don't know, five, ten years where we went from SSL to TLS and TLS one dot o, then 1 dot one, then 1. Two. Now we're at 1.three. 1.4 is gonna be common. Right? And we will keep up with that. That will be in your secure host access innovative road map. That's an example. There's other things that we're thinking about doing, with secure host access, and we'd love your input. So, I'm having customer meetings a lot, and I'm thinking I'm thinking about what else can we do to make this, you know, a a product that you could depend on from a security point of view. So, so it does have an innovative road map. The other thing I will mention, for you is is, you know, I think you've been kind of on this path for getting an annual release. So Securus to Access will actually have a quarterly release. They'll they'll do a big splashy, release every couple of years, but quarterly, we will be re releasing stuff. And so what that offers you is the ability to partake in it from DevOps perspective. Right? So if you wanna if you're constantly keeping up on the latest so that you have the latest in security vulnerabilities, you'll have that ability to do that with Securys access. So, so that's the other thing for me that I I think about when I think about an innovative road map. The product life cycle is better than it's ever been. Right? Rocket's a customer focused, company, and so they want you to have a good product life cycle. And that also lends into those quarterly releases that should you move to Securus access. And then I think, you know, I think maybe maybe even more importantly as part of Rocket is we get that there's still some work to do. Right? And, you know, I, I recently had a a conversation. Chris and I were both involved in a conversation on product life cycle. Right? We work months and months and months to get this thing, and and and then now we need to make some changes because we weren't necessarily articulating everything you needed to see because we were a little bit clue too close to the the forest, if you will. We we can always improve what we do. So, the the difference being at Rocket is we actually wanna hear from you. Right? And we want you to tell us what we what you don't like and what you like. So because we want to adapt. Can we fix everything that you don't like? I don't know. That's you know, bring it to me and we'll see. But the fact is is that we wanna listen and and generally speaking, you know, and I think Chris would agree with this, is if you have a concern, you're not the only one. Right? I got another customer out there that maybe not talking to me be with the same concern. So we do wanna hear from you, and and I don't mean that lightly. There's an email address on this page, and I think we're gonna have it on the next page as well. Write that down. This is how you get to Chris and I. The only reason why it doesn't say Chris and Barbara on there is because, otherwise, you'd only get one of us. We are behind this this, inbox, if you will. Evan's there as well, but this is really intentional for you as a customer to get to product management. But, you know, Chris and I do our best, to respond right away. If you don't get a response, send it again and say, look. How come I didn't get a response? We're we're humans, but our intention here is to work with you and get you what you need and answer any questions you might have. We could bring in your sales rep. Some of you might not even know who your sales rep is. That happens from time to time. We're here to help. So whatever it is, we'll let you know if you gotta be talking to somebody else. But Chris and I will be answering those emails. So, okay. So I think I think we're about to wrap up. Yep. Okay. Alright. Yeah. That's right. Nicely done, Chris and Barbara. Honestly, I think that was a great session. I I haven't seen questions come through, but I know that you're both in a lot of conversations, around, Secure Host Access and the other emulators. Are there questions that come up regularly that you think this this audience, you know, should should hear? I think one thing that came up when I was listening to Barbara talk about the regulatory mandate. So there's this new New York, regulatory mandate, Barbara, and NYCRR 500, whatever it is. And I think I think an important question is, does it just apply to companies in New York? Oh, great question. And, actually, I thought about something else that I didn't talk about, so I'll get that in a minute. To answer your question, it has to do with anybody doing business with New York. So it is not that you reside in New York. It is the fact that you in fact, I talked to a very large insurance company not very long ago who does business with New York and has to comply with this mandate. So it is anybody doing business with the state of New York in a financial services type of fashion. That is who that but the other thing, then I'm gonna expand a little bit here is because you re kind of put something in my head. You will not see a regulatory mandate that calls out the mainframe. And the reason why is because these mandates don't care where the data is. It is what the data is, and that could be credit card information or more likely it's categorized as personally identifiable information, which is a very big term. Right? I mean, a person identifiable information can be, as specific as your Social Security number if you live in The US, but can also be as vague as your phone number or address. It is information that can be connected to your identity or a person's identity, and that's why it has to be protected because that's what these near dwells want. The more pieces of information that they can tie to a identity, the more likely they can be to take over that identity. So that is why it is what it is. So, you know, you're not oh, I just gotta protect Social Security numbers, you know, or tax ID numbers or for whatever country you live in. It is way more than that. It is there's not even a real good definition for personally identifiable information other than any information that causes that person to be identified. So it's very loose. Think health care, an, you know, an insurance ID. Anything that connects back to that person, you have to protect. So And that's a great point, Barbara. Call out where it is. They don't care. Yeah. And that's a great point. Now there was a customer we were talking to the other day, and they said, we were having a meeting to dis to discuss the definition of PII. Like, what qualifies as personally identifiable information? There's all kinds of new data being created. Right? And it may not even be defined as, you know, personal PII or not. And so, that's another thing I think that organizations are struggling with and and as such, even more important, right, to protect to be able to protect old data and new data, whatever data gets created. The other question that often comes up, Barbara so my background is more desktop. Your more recent background, Barbara, has been more web. And I think Indeed. When folks have used web emulators in the past, they've been 20% of the functionality you get in the thick client is in the web client. Right? How would you quantify today, like, what what customers would get from, a web client perspective from a functionality point of view? So that's a great question. So, you know, thin's thin. Right? And that's important because it is it is not thick. It is not the same as your desktop emulator. So the goal is really to make it, you know, I I it's hard for me to put a percentage on it, but I would say in the 70 to 80% of the functionality. Where you have to have a desktop into, desktop emulator is really about the business logic that you wrap around that. Or maybe from a developer person who needs to have, you know, the ability to program in a VBA macro. Right? It's JavaScript in the web based product. So so think about those kind of things. But the other thing that's really important is you think about when you think about security, which is all I think about anymore, is the browser has a sandbox around it. So you cannot do certain things. You cannot go directly to a device. You cannot, you know, talk to a printer, for example. You can't interrogate the hard drive because the browser has its own security. And now I just was recently on a conversation this week that there are new browser platforms coming out there. These are centrally managed browsers that actually lock that down even farther to where you can't copy and paste. But the Yeah. What I'm trying to get across here is there is there are things that even if we wanted from an emulation perspective to allow you to do in a browser, we wouldn't be able to do that because of the browser security. So so we do have to abide by that. The one other thing I wanna mention, Chris, while we're talking about the difference between, installed on the desktop and and the, the most of the newer web based emulators, including Securys access, are, no dependencies on the desktop. So no Java, no active x, no plugins required in the browsers. But the other thing that's kinda cool with our product is it is it is HTML from the end user's browser to our server, that middle box on that market texture diagram. And the reason why that's important is because that means thirty two seventy traffic or, fifty two fifty traffic, whatever kind of host you're on, does not leave your organization. So you can share a mainframe connection with somebody outside of your organization and the traffic, the thirty two seventy traffic doesn't leave your organization. So that is that's really important. That's great. And we got a couple of things in the q and a. So I don't wanna because you Yeah. Yeah. Dave David, I see your question about the, the maturity announcement on October 7. That would have gone to it would have been an email that went out. It would have gone to the same email that received the the notification about this webinar. So, I don't I don't know if you received this or if a, coworker sent it your way, but, you were they should have received that notification. And if not, I I can get it to you too, if you wanna let me know in the chat or I'm happy to to share it, you know, of anyways. Yeah. Or I mean, he can just email that Rocket that Rocket Software because because we can get it to you that way, David, because because we want you to have what you need. Yeah. That's right. Go ahead. You're oh, go ahead. Sorry. No. No. No. Go ahead. I was just gonna move on to, the other question. And you're a little bit more familiar with the specific versions of Rumba. Right. Our current version is 10 dot two and service tech three is coming up this week. Right. Yep. And they're asking me when we officially supported, yeah. When we officially supported Windows 11? They're saying it's incompatible with Windows 11 based on a case that they opened, which is which is, I just don't when did we that seems like that's seems like that wouldn't be true. I don't think 10 dot one is all that old, but I could be wrong too. So Yeah. We'd have to look at, Yeah. So let's do this then because we don't we don't so give you if and I don't know how to pronounce your name, so I'm gonna say Daratha. I I love that name. If you would just email us at that Rocket, rocket software dot com because I don't have your email address, shoot us an email in there. Chris and I will look into it, and we'll get back to you when we officially supported it. Now you may be even if it's officially supported, you may be having some form of an an error that doesn't have to do with that, and you still need to work with support. But but we just wanna make sure you know when we officially supported, Windows 11. So that would be great. Yeah. Great. And then Evan, you responded back to David, so we'll get that taken care of. Okay. So Good. Okay. Yeah. I I think that's all the questions that we've received. So, if if there's nothing else, we can go and wrap up. But if you have other questions after the fact, please please reach out to this Rocket. Oh, I do see one more question. In your earlier diagram, it wasn't clear to me if I am was in reference to security group or security technology component. That would refer to your identity and access management, the, the tools and and best practices in your, environment. Right. And the enterprise. Right. Yep. And then part two, does your production work with both mainframe, e s m, rack f, ACF two? Yes. Rack f ACF top secret. Yep. Yeah. Does your product work? Oh, yeah. Sorry. We can yeah. And we do. So absolutely. We be because we just we, we're not at that level. You you have your product. So rack f or ACFT, for example, they would be configured to work with that component that we work with. So then rack f, for example, is still all in charge of who's getting in and and if they should get in. So we don't disrupt that at all. Our our goal here is just to make all of this easier not to take it over. So, so we don't disrupt the authentication and authorization on the mainframe. We work with it to allow you a single sign on experience for your end users. So I hope that helps a little bit. And, again, if you you know, we can always have a one on one discussion too. So just pop an email into that thing and, you know, if I need help because I'm just a product manager, so I don't necessarily always but I got a developer that could joins me in a lot of my calls. We got SCs that'll join us. So, and then and then if you want a salesperson involved, we can get that too. So Yep. Perfect. That's good. Well, if there's if there's anything else, the the email address here, rocket connectivity at Rocket Software dot com, that'll get to us. But, otherwise, thank you all so much for attending today. I think this this was a great session. Chris, Barbara, thank you both. You bet. Thanks everybody for joining. Yep. Thanks for your time today.