Closing the Endpoint Gap: Business Continuity and IGEL’s Dual-Boot Solution

In this episode of IGEL Weekly, Andy Whiteside sits down with Chris Feeney from IGEL’s Office of the CTO to explore a critical, often overlooked element of disaster recovery—endpoint resilience. They unpack how IGEL is addressing business continuity challenges with innovative solutions like IGEL Dual Boot and USB Recovery, enabling organizations to recover in minutes rather than days.

Chris shares insights into the growing importance of securing endpoints amid rising ransomware threats and operational disruptions like the recent CrowdStrike incident. The conversation dives into:

• Why most organizations fail to plan for endpoint-level recovery
• How IGEL’s dual-boot architecture bridges the gap between prevention and recovery
• Real-world examples of minimizing downtime during breaches and outages
• The future of endpoint strategy as SaaS, browsers, and cloud PCs reshape IT infrastructure

Tune in to learn how IGEL is redefining endpoint continuity and setting a new standard for security and business resilience.

Transcript

WEBVTT

1
00:00:02.460 --> 00:00:19.299
Andy Whiteside: Hello, everyone. Welcome to episode 104 of IGEL Weekly. I'm your host, Andy Whiteside. I'm joined again by Chris Feeney from IGEL. Chris, I'm gonna be totally honest, I think your role has changed multiple times in the last couple weeks, and, you know, without going too long on it, what's, what is the current Chris Feeney role?

2
00:00:19.690 --> 00:00:26.489
Chris Feeney: Great question. So, for the last year and a half-ish,

3
00:00:26.760 --> 00:00:35.229
Chris Feeney: It's been focused on vertical solutions, and part of that spent time with our product marketing team, but as,

4
00:00:35.370 --> 00:00:52.599
Chris Feeney: We've experienced some growth and stuff like that. There's been a need, in the Office of the CTO for, for focusing on, sort of, kind of where I bring my, attention to solutioning, essentially, and obviously working with partners like you to bring that, and so…

5
00:00:52.600 --> 00:00:57.940
Chris Feeney: I'm now in the office of the CTO, working under, and supporting both

6
00:00:58.020 --> 00:01:08.210
Chris Feeney: Jason McFair, our healthcare field CTO, and John Walsh are, critical industries, non-healthcare, for the most part, field CTO, so…

7
00:01:08.410 --> 00:01:15.629
Chris Feeney: But focus on solutioning, vertical solutions specifically, so that is what my role is right now.

8
00:01:16.170 --> 00:01:17.169
Chris Feeney: In a nutshell.

9
00:01:17.170 --> 00:01:33.160
Andy Whiteside: I know that's, got potential for us as a big IGEL partner and a big ServiceNow partner. I know you're helping us maybe bring those two technologies together with, maybe some back-end integration or some integrations that we publish out on the ServiceNow store, so I appreciate that. Anything we can do to get that going.

10
00:01:33.450 --> 00:01:45.340
Chris Feeney: Yeah, absolutely. Now that we know who to figure that out, we'll continue that conversation that started a couple years ago when you guys got Fred going, and congrats on all the success you've had with that.

11
00:01:45.340 --> 00:01:54.330
Chris Feeney: a little note on, sort of, that thing. Yeah, for me, my journey is now I'm in my 8th year at IGEL, and as I've gotten through into different roles, I…

12
00:01:54.330 --> 00:02:03.039
Chris Feeney: One of my favorite parts of my time here has been working with the channel partners, understanding their business, who they work with, but more specifically.

13
00:02:03.180 --> 00:02:20.090
Chris Feeney: as our messaging has evolved, and our solutions have evolved, it's become more apparent to me that it's iGel Plus every single time, whether that's hardware, whether that's a software, whether that's a Better Together, whatever it might be.

14
00:02:20.090 --> 00:02:24.669
Chris Feeney: But what customers are looking for, and partners are looking for a solution, and…

15
00:02:24.710 --> 00:02:31.879
Chris Feeney: Our topic today is a solution that we've come up with. Looking forward to, talking about this, because it's,

16
00:02:32.110 --> 00:02:37.499
Chris Feeney: An overlooked… Problem that, we hope to address.

17
00:02:37.680 --> 00:02:48.050
Andy Whiteside: Yeah, a solution, or what I call a platform a lot of times. I, I do a lot of conversations around Citrix, Omnissa, I learn parallels, as it relates to IGEL. If you take one of those,

18
00:02:48.050 --> 00:02:51.259
Andy Whiteside: One of those pieces, and add it to the…

19
00:02:51.260 --> 00:03:15.070
Andy Whiteside: Linux IGEL platform or operating systems you guys have, you combine the two of those things together, it could just be a browser. It could just be a regular old Chrome browser, island browser would be even better. Now you've got what I call a solution that's made up of an operating system platform and a very applicable application piece, well, multiple or single application piece, and you've really come up with a solution that, in many, many cases in the business world.

20
00:03:15.200 --> 00:03:18.310
Andy Whiteside: can just totally make windows on the endpoints.

21
00:03:18.310 --> 00:03:35.479
Andy Whiteside: irrelevant, and sometimes, and you're actually doing it right now, I think, you're using Windows 365, I believe, to run the recording for this podcast, so, and I assume you're using an Agile device, which I know you are, IGEL device to talk to a, Windows, where it belongs in the cloud PC,

22
00:03:35.480 --> 00:03:45.009
Andy Whiteside: And you combine those two together, you know, an application running on a platform, talking to a back-end system like Windows 365, and now you have a solution

23
00:03:45.010 --> 00:04:02.359
Andy Whiteside: That, you know, what we're going to talk about here applies to, as well as lots of other enterprise class capabilities that you're bringing to the mix. So the blog today is Closing the Endpoint Gap in Business Continuity and Disaster Recovery, by James Millington from September of this year. Just to kind of tee this up.

24
00:04:02.460 --> 00:04:08.759
Andy Whiteside: Lots of organizations have been bit by the under, under-thinking

25
00:04:08.860 --> 00:04:13.889
Andy Whiteside: or not planning ahead. Okay, I get we need business con… we need disaster recovery.

26
00:04:14.030 --> 00:04:27.609
Andy Whiteside: In our data center, we need business continuity in our data center. Oh, but what happens, which is the common thing now, when the endpoint side of the equation gets, attacked, or broken, or what have you? It could just be, you know, a bad keyboard.

27
00:04:27.610 --> 00:04:34.629
Andy Whiteside: It could be a bad, bad, file structure on the operating system that causes it not to work.

28
00:04:34.700 --> 00:04:42.979
Andy Whiteside: what happens when that endpoint no longer functions? And that's what IGEL's addressing here, and we're going to cover it in today's… in today's blog that James put out in September.

29
00:04:43.910 --> 00:04:44.769
Andy Whiteside: So let's.

30
00:04:44.770 --> 00:04:45.760
Chris Feeney: Yeah, definitely.

31
00:04:45.760 --> 00:04:47.319
Andy Whiteside: Let me just start by asking this, Chris.

32
00:04:47.540 --> 00:04:53.330
Andy Whiteside: and I kind of teed it up here a little bit, but in general, what's the number one reason

33
00:04:53.480 --> 00:04:59.079
Andy Whiteside: Why you think people don't plan for business continuity at the endpoint.

34
00:05:00.610 --> 00:05:02.850
Chris Feeney: I think everything…

35
00:05:03.150 --> 00:05:19.610
Chris Feeney: You know, as there's been some consolidation with the data, the data center, you know, obviously, you know, you've got, that's where you're, generally speaking, accessing stuff, and so there's been a tremendous amount of focus, even going back 20-plus years, right, where

36
00:05:19.610 --> 00:05:39.680
Chris Feeney: started hearing some of these, vendors offer hosted data centers, right? And you started seeing customers go with either that as a backup option, maybe a hot standby, warm standby, cold standby, whatever it was, but just something where they had the ability to switch over to it. But rarely did you hear a conversation around.

37
00:05:39.680 --> 00:05:44.840
Chris Feeney: you know, what about the devices being used? And, granted.

38
00:05:44.940 --> 00:05:54.399
Chris Feeney: We weren't dealing with ransomware and malware to the extent that we see almost every single day, like we are today in our interconnected world.

39
00:05:54.400 --> 00:06:11.580
Chris Feeney: And so, where… where it's come up is you've got all… and plus, now we got the rise of the cloud in certain industries, so when I came to IGEL 8 years ago, for example, I was still thinking, when is healthcare going to begin to, embrace the cloud?

40
00:06:11.580 --> 00:06:29.090
Chris Feeney: when is the Fed government, you know, beginning to do that, right, in the world of end-user computing? And a lot's changed in that particular period of time, as so has the efforts of those nefarious actors trying to compromise the endpoint devices. And so, I think

41
00:06:29.150 --> 00:06:36.170
Chris Feeney: There's been a tremendous amount of, well, let's make sure our data and everything is restored, but then they think, well.

42
00:06:36.650 --> 00:06:42.820
Chris Feeney: you know, we talk about all the time, what are we using to get to that? And that's where I think there's been this…

43
00:06:43.110 --> 00:06:44.020
Chris Feeney: Oh.

44
00:06:44.150 --> 00:06:52.510
Chris Feeney: well, what do you guys have ideas for? I don't know, you know, and so we were uncovering that this is often the overlooked problem.

45
00:06:52.890 --> 00:06:54.580
Chris Feeney: This endpoint gap.

46
00:06:55.140 --> 00:07:00.100
Andy Whiteside: Chris, I agree with that. At the same time, if my argument would be, in the beginning.

47
00:07:00.200 --> 00:07:02.220
Andy Whiteside: The bad guys attacked the data center?

48
00:07:02.290 --> 00:07:22.090
Andy Whiteside: We've got those things somewhat resilient at this point. Now they're attacking the endpoint, and so, organizations are now, now starting to realize that's where they've got to move their strategy to not only the data center, data centers, more than likely, but also the endpoint, and as much as we want to talk about thinking we're being strategic, we're really just chasing the ball.

49
00:07:22.820 --> 00:07:32.579
Chris Feeney: That's a great point, true. I think, as people have realized the, benefits of, you know, the security around having

50
00:07:32.610 --> 00:07:51.639
Chris Feeney: a cloud, or hybrid cloud, or whatever you want, ability to rapidly restore, you know, virtualization technologies that can help you, you know, snapshot things and recover quickly, whereas a lot of the security tools shifted, and a lot of them is on the endpoint. We talk about this all the time.

51
00:07:51.640 --> 00:07:56.129
Chris Feeney: And, but… but you still deal with…

52
00:07:56.540 --> 00:08:08.509
Chris Feeney: physical devices that may have a problem, not just being attacked from a software perspective, but what if the hard drive happens to go, or something else, right? And so that's where, you know.

53
00:08:08.860 --> 00:08:16.829
Chris Feeney: is it a matter of a bunch of replacement devices waiting in the wings, or… or something else, right? And so, we're saying…

54
00:08:16.830 --> 00:08:21.569
Andy Whiteside: You mean, you mean to run down to Best Buy and buy all the Chromebooks or Windows PCs doesn't work?

55
00:08:21.950 --> 00:08:40.089
Chris Feeney: Yeah, it's a great point, right? What if there's 12 others that are doing the same thing, you know, or there was a fire sale, a back-to-school sale, and nobody has anything left, you know? Is that really what you're going to hope your strategy on? Is that there'll be some spare devices waiting in the wings?

56
00:08:40.090 --> 00:08:47.350
Andy Whiteside: Well, and then also just factor in that most of these stores have kind of just-in-time inventory anyway. They don't keep a hundred of whatever it is on the shelf anymore.

57
00:08:47.740 --> 00:09:03.529
Chris Feeney: Yeah, and I mean, honestly, for the stuff that you guys have been doing over the years with, you know, taking older devices, I mean, I've seen it many, many times that we're going on site with customers, seeing, you know, these back rooms where we're setting things up, and they've got

58
00:09:03.530 --> 00:09:14.010
Chris Feeney: piles on piles of devices that are destined, generally speaking, for the dumpster, right? And they could be perfectly reused, or ready to go, or what have you.

59
00:09:14.010 --> 00:09:24.809
Chris Feeney: And they just… that wasn't how they were thinking. And so there's, there's opportunity to continue to extend the life of these devices, whether they are

60
00:09:24.810 --> 00:09:34.329
Chris Feeney: Your backup options in case something happens, or you do it more strategically, like, like we're saying here with our… with our new solution that we're gonna talk about.

61
00:09:35.240 --> 00:09:50.420
Andy Whiteside: Let's, let's talk about the solutions. Solutions, plural. It's really double-clicking on one of them. There is one more section here from the… in the blog that James wrote, it's called, Why Recovery Takes So Long. It says, IBM did a study, 76% of organizations that recover from breach

62
00:09:50.420 --> 00:10:05.429
Andy Whiteside: took more than 100 days to fully recover. 26% needed over 150 days, while just 2% managed to get their recovery down to 50 days. That's a lot of lost productivity, a lot of lost business opportunity.

63
00:10:05.430 --> 00:10:20.170
Andy Whiteside: and, quite frankly, a lot of money. You know, I talk to your CEO, Klaus, all the time, and he's like, look, the security guys know this is a problem, and they're willing to spend money to fix this. You know, I'm not sure, what… I know there's all types of people who listen to this podcast.

64
00:10:20.170 --> 00:10:29.890
Andy Whiteside: My overarching message here when it comes to security and being able to recover in less than a handful of days, hopefully within hours in this case, this is well worth the money.

65
00:10:30.540 --> 00:10:44.509
Chris Feeney: Yeah. Well, taste in point, right? What do we see, not necessarily a breach, but more of an update outage is what we refer to it, and we're talking, obviously, about the CrowdStrike incident, right, where a trusted

66
00:10:44.510 --> 00:10:50.909
Chris Feeney: a trusted vendor pushed out an update that unfortunately had a very bad impact. It…

67
00:10:50.910 --> 00:11:01.410
Chris Feeney: required physically touching devices, every single one of them that was impacted at the physical layer. In the data center, same sort of thing, right? And so.

68
00:11:01.410 --> 00:11:15.750
Chris Feeney: A lot's changed in the last year, as Microsoft has made some changes to try to address something like that. But still, how much time did it take a lot of these organizations that didn't have the manpower to go out and rapidly recover these devices? So these numbers are… are…

69
00:11:15.750 --> 00:11:23.939
Chris Feeney: And that was, you know, again, that wasn't a ransomware scenario like we've seen, or malware, where you have to…

70
00:11:23.940 --> 00:11:40.989
Chris Feeney: you know, investigate, or with cyber security and, you know, figure out how bad it really is. It's Cybersecurity Month right now, and so one of the things that I was looking at that recently occurred over in Europe was.

71
00:11:41.180 --> 00:11:55.639
Chris Feeney: A third-party vendor had a tool that was being used in respect to airports, and there was a breach there, and it worked its way down to the endpoint. Presumably, those endpoints were running Windows.

72
00:11:55.640 --> 00:11:57.809
Chris Feeney: And about a thousand of them

73
00:11:57.810 --> 00:12:17.940
Chris Feeney: for example, at Heathrow, were impacted, taken down, and that's where the users were just accessing to do things like, you know, bag checks, you know, checking in, you know, going into the gate, all that type of stuff. And so, who knows how long it's going to take to recover those devices, but these numbers are not unheard of.

74
00:12:18.790 --> 00:12:25.539
Andy Whiteside: It's happening every day. It may not be another update outage like we saw before, but it is literally happening every day.

75
00:12:25.730 --> 00:12:42.489
Andy Whiteside: every industry across the world. The easy one to find is, like, you just described, kind of the airport, and that's the airport signage. That's a great example. I don't walk into an airport without seeing some sign down, because it's got some kind of, you know, blue screen of death, or some update in progress, yeah.

76
00:12:42.490 --> 00:12:44.340
Chris Feeney: Yeah, I, saw one…

77
00:12:44.340 --> 00:12:44.890
Andy Whiteside: bills.

78
00:12:45.130 --> 00:12:54.320
Chris Feeney: Yeah, totally. You see it in hotels, I've seen it just in the last month. I've had several locations I've been to where

79
00:12:54.400 --> 00:13:07.090
Chris Feeney: There was some digital signage up, and it had, you know, something regarding windows, or had… it was a boot that required somebody to physically touch, to… to get it to boot correctly, or whatever it might be.

80
00:13:07.710 --> 00:13:23.990
Andy Whiteside: Yeah, I stay in Marriott's a lot, and most of the Marriott's I go in now. There's a large percentage of them, the hotel kiosk down in the lobby is sitting on some screen where somebody has to hit the button to tell it to accept the favorites or accept some of the default things, and it just boots back into that over and over and over again.

81
00:13:24.160 --> 00:13:28.349
Andy Whiteside: And nobody even notices. It's just become so mainstream to expect that.

82
00:13:28.660 --> 00:13:34.289
Andy Whiteside: Let's talk about the next section here. It says, IGEL's, unique answer, fast.

83
00:13:34.380 --> 00:13:53.060
Andy Whiteside: secure endpoint recovery, and James breaks it down into 3 different options, or 3 different categories here. The first is this new thing, which I think we want to focus on probably the most, which I'm super excited about. I haven't had a chance to put it on my primary laptop yet, but I can't wait to, and that is the IGEL Dual Boot Recovery Option. Chris, you want to explain that one?

84
00:13:53.210 --> 00:14:03.480
Chris Feeney: Yeah, so the concept of having, on the same hard drive, the same endpoint device, the ability to boot to more than one operating system is not new.

85
00:14:03.580 --> 00:14:08.839
Chris Feeney: And so, what we've done is, you know, understanding

86
00:14:09.010 --> 00:14:14.539
Chris Feeney: what's happening, right? We have customers that, obviously, you know, we've tried to…

87
00:14:14.700 --> 00:14:20.999
Chris Feeney: You know, push very hard that, hey, for the preventive security architecture model that we've had since day one.

88
00:14:21.000 --> 00:14:37.480
Chris Feeney: it would be very wise of you to run IGEL in production, but there's a lot of companies that are not yet ready to go there, for different reasons. So, if that's the case, we're saying you're… it's not a matter of if, but when, and so, if you have a device running Windows,

89
00:14:37.760 --> 00:14:46.340
Chris Feeney: you know, generally speaking, there's probably space on the hard drive that can be leveraged, and so we can install IGEL, a different version of IGELOS,

90
00:14:46.440 --> 00:15:01.050
Chris Feeney: that will be installed right alongside Windows in a partition, and we have a KB article that talks about, you know, how large that partition will end up being, whatever. But it's there in the scenario where

91
00:15:01.240 --> 00:15:05.459
Chris Feeney: You know, hey, We got hit by ransomware, we got hit by something, right?

92
00:15:05.830 --> 00:15:20.420
Chris Feeney: there's an outage, and so we have to switch over. And so, what happens is, you know, you go to reboot, and you get a boot menu. The default is Windows, and so you would switch to Agile Dual Boot.

93
00:15:20.520 --> 00:15:23.960
Chris Feeney: And, that will become the new default.

94
00:15:24.190 --> 00:15:36.890
Chris Feeney: And, for obvious reasons, if the Windows partition needs to be investigated or preserved or whatever, you don't want that to come up again and re-compromise, whatever like that, so IGEL will become the new…

95
00:15:37.210 --> 00:15:43.580
Chris Feeney: default boot, right alongside on the same hardware. So.

96
00:15:43.580 --> 00:15:56.220
Andy Whiteside: So, Chris, you said… I want to challenge something real quick, you said default boot, so it becomes one of the options. Can you actually make it the default, where the operating system just loads up in from the bootloader to IGEL by default, and Windows becomes the secondary option?

97
00:15:56.610 --> 00:16:13.849
Chris Feeney: Yeah, let me think about this. So, if from, like, hey, I want this to be Agile to be my primary for production all the time, versus the dual boot, which is designed for recovery, essentially, I think technically you probably can, but it's primarily designed so that

98
00:16:13.850 --> 00:16:19.059
Chris Feeney: Windows already on the endpoint, we go to install IGEL, we won't become the default OS

99
00:16:19.060 --> 00:16:26.270
Chris Feeney: Presumably Windows is still fine until it isn't. But once you select the dual boot option in the recovery scenario.

100
00:16:26.370 --> 00:16:38.669
Chris Feeney: Yeah, the presumption is Windows has been compromised for some reason, whatever it might be, and we need to go to dual boot into IGEL, and we become the default from that point on until you decide to switch it or whatever.

101
00:16:38.670 --> 00:16:50.719
Andy Whiteside: Okay, that's interesting. Yeah, I can't wait to play with it, and I just had this thing running through my head. Okay, what if I made IGEL my default, and I used it for a month, and then I said, oh, let's move back to Windows today, then I'd have to sit there and get all the updates and madness.

102
00:16:50.720 --> 00:17:10.549
Chris Feeney: Yeah, and this is a great point, because for those that are familiar with IGEL, right, I mean, we repurpose devices, and so we, you know, our primary mode, which is why this is a separate install file, essentially, is we are going to replace Windows on the entire disk drive. So, if you just pull down our normal

103
00:17:10.569 --> 00:17:12.710
Chris Feeney: OS, Creator.

104
00:17:12.819 --> 00:17:28.429
Chris Feeney: tool, or decide to push it out through SCCM. Our default scenario for years and years has been to replace Windows on the endpoint, you know, so we install, we're gonna blow whatever's there away, and put IGEL on the entire disk drive, or whatever.

105
00:17:28.430 --> 00:17:48.070
Chris Feeney: This is a different solution. It's not going to replace Windows on the endpoint. It's going to set up IGEL in a separate partition, so you have this capability in case something happens. It still takes the same license, the IGEL license, and then the idea is that you would have it for, you know.

106
00:17:48.080 --> 00:17:55.369
Chris Feeney: 45 days, 90 days, whatever is needed there to recover until you need to go back to Windows, or…

107
00:17:55.560 --> 00:18:01.170
Chris Feeney: Maybe you decide IGEL's the thing we need all over, and you decide you want to go production.

108
00:18:04.440 --> 00:18:14.009
Andy Whiteside: I think you're gonna see some of that happening, or at least, at a minimum, people are gonna buy it for business continuity, and then they're gonna realize, hey, I like this, I have… there's benefits of this to me, and then all of a sudden.

109
00:18:14.300 --> 00:18:22.099
Andy Whiteside: they start to consider IGEL as their primary platform for the endpoint, versus just a, you know, a backup option.

110
00:18:22.600 --> 00:18:39.710
Chris Feeney: Yeah, so, for the second one we're going to talk about here in a second, I'm literally doing that right now. It's not… it's… I'm, on my LG Gram, I've got Windows and Ubuntu Linux in a dual-boot scenario, and then I just use my iJoD Pocket.

111
00:18:40.030 --> 00:18:54.679
Chris Feeney: To boot to iJoe, and then I've got it set up with multi-monitors like I would if it's just like my Windows laptop to my left here. I could plug that in, and I get the same multi-monitor experience. I'm doing today's call via Zoom through my cloud PC.

112
00:18:54.680 --> 00:19:02.370
Chris Feeney: I could also, if Microsoft infrastructure is down, I could just fire up the Zoom local app, and we could have the same conversation.

113
00:19:03.160 --> 00:19:18.069
Andy Whiteside: And Chris, I want to also challenge something you said just now, just on the point of clarity. You are using your Windows desktop in the cloud, doesn't matter which cloud, in this case it's Azure, and you're using an IGEL endpoint operating system running at the moment, sounds like off a USB key.

114
00:19:18.070 --> 00:19:27.019
Andy Whiteside: And you're doing this magical thing, which has come so far and is so reliable these days, which is you're offloading, in this case, the Zoom session for the unified communications piece.

115
00:19:27.070 --> 00:19:30.329
Andy Whiteside: And it just kind of works these days if you've got

116
00:19:30.740 --> 00:19:31.960
Andy Whiteside: Have you got things done correctly.

117
00:19:32.890 --> 00:19:50.260
Chris Feeney: Yeah, and, I tested it yesterday, I've got 3 monitors here, and I wanted to present and make sure that, hey, if I'm sharing my third monitor, whatever, is it working as expected? You know, from an audio-video thing, the video cam's working just fine,

118
00:19:50.310 --> 00:20:01.910
Chris Feeney: I've got a headset plugged in here, I can hear you just fine, so, lots come a long way, and even internally within IGEL, we're doing what's called IGEL on iGel, so we have

119
00:20:02.060 --> 00:20:12.589
Chris Feeney: IGL laptops issued out, and you have the option of using a, you know, cloud PC or web apps, whatever you need, as well as some local apps.

120
00:20:14.640 --> 00:20:28.730
Andy Whiteside: Yeah, and I mentioned browsers a while ago, Island Browser, and several others, including Chrome and Mozilla Firefox in your world, that when the world becomes mostly, if not exclusively, SaaS-based applications, this

121
00:20:28.820 --> 00:20:40.410
Andy Whiteside: conversation around the endpoint resiliency is going to be where the future, where the focus is, I believe, because the back-end stuff is going to be so distributed and so, so,

122
00:20:41.290 --> 00:20:42.390
Andy Whiteside: impenetrable…

123
00:20:42.510 --> 00:20:48.500
Andy Whiteside: Maybe not the right word, but so resilient, that this endpoint piece is going to be where the focus will have to be at that point.

124
00:20:49.290 --> 00:21:07.729
Chris Feeney: Yeah, no, we've talked about it many times. At the end of the day, what is it easier to get to? Their workspace. And a lot of these apps, if I'm building something from the ground up, it's gonna be browser-based to start. And I, you know, IGEL, as currently going on our, IGEL on tour. You were at the one in New York, I was one in Boston.

125
00:21:07.790 --> 00:21:22.950
Chris Feeney: We've got a few others that are out there. There's one in Sydney, Australia, going on. I've had a chance to speak, you know, speak at those. Island presented for me recently in front of my presentation. I'm very impressed with, obviously, what they've been able to do.

126
00:21:23.040 --> 00:21:38.520
Chris Feeney: They keep adding more and more capabilities into that browser, and we were talking about, you know, truly, I mean, getting to a point where everything I need to do and function is delivered from a browser, and what's better than a secure browser that can be managed?

127
00:21:38.790 --> 00:21:53.169
Chris Feeney: And, and even… what's interesting is, maybe I shouldn't say this, but they're being able to deliver published applications, so forgive me if, Island, if I spilled the beans on that, but you got some really cool stuff.

128
00:21:53.370 --> 00:21:57.719
Chris Feeney: That, very excited to see here for customers to take into account.

129
00:21:59.360 --> 00:22:00.700
Andy Whiteside: And that's…

130
00:22:01.170 --> 00:22:07.769
Andy Whiteside: Probably true, Chris. We'll just leave it at that for the moment. But it's absolutely something I believe they're working on.

131
00:22:09.160 --> 00:22:12.870
Chris Feeney: well then, I probably should not… I've said that, but .

132
00:22:12.870 --> 00:22:13.310
Andy Whiteside: I think.

133
00:22:13.310 --> 00:22:13.950
Chris Feeney: What we got?

134
00:22:13.950 --> 00:22:14.770
Andy Whiteside: That's fine. I think we're.

135
00:22:14.770 --> 00:22:15.610
Chris Feeney: You said it's fine.

136
00:22:15.610 --> 00:22:32.860
Andy Whiteside: I think it's, I think it's commonly known that they know that's, one of the last frontiers for making the browser the answer to all things application on the endpoints, is getting access to those, legacy… legacy x86 apps, which, my favorite topic in that one is Windows, is a legacy x86 app.

137
00:22:33.080 --> 00:22:35.609
Andy Whiteside: And I will, I will debate anybody on that.

138
00:22:35.940 --> 00:22:51.039
Chris Feeney: One last thing on the USB boot, real quickly. So, when a customer buys the dual boot or the business continuity solution, you will get the dual boot and the option for the USB boot, in case, for example, the hard drive does die.

139
00:22:51.040 --> 00:22:58.750
Chris Feeney: and you can't dual boot, you could still take the option of going to, the IGL USB key.

140
00:23:00.130 --> 00:23:14.629
Chris Feeney: Obviously, you know, managing that, sitting there in an envelope on the back of the… whatever it is, you know, but that is an option you will get. It's included, you just need to, you know, do you want those devices or not when you purchase the disaster recovery solution, so…

141
00:23:14.760 --> 00:23:15.699
Andy Whiteside: That's interesting, though.

142
00:23:16.540 --> 00:23:18.140
Andy Whiteside: It really is.

143
00:23:18.340 --> 00:23:30.019
Andy Whiteside: Okay, last of the bullets here, the numbers, enterprise-grade security, by design, IGEL OS is read-only, modular, and tamper resistant. I love the word resistant there, you're not willing to

144
00:23:30.660 --> 00:23:39.229
Andy Whiteside: From a, covering your, you know, basis perspective, not willing to say, 100%, impenetrable, but it's pretty damn close.

145
00:23:39.310 --> 00:23:52.899
Andy Whiteside: And way more… more resistant than, you know, your typical Linux non-read-only operating system, your Apple, Mac, or your Google, or Windows in this case. It's intentionally secure.

146
00:23:52.900 --> 00:24:01.160
Andy Whiteside: So the device remains in good state while booted, and reboots back to that same good state. Anything to add on the enterprise-grade security comment there, Chris?

147
00:24:01.550 --> 00:24:12.570
Chris Feeney: Well, it's just, you know, re-emphasizing everything we've talked about, on this podcast and elsewhere, that, you know, it's the same immutable operating system that's booting up here.

148
00:24:12.570 --> 00:24:30.429
Chris Feeney: With the same preventive security architecture model, such as, you know, users aren't going to be able to tamper with the configuration settings. This assumes, obviously, you've locked things down and you're controlling all those capabilities, which you would normally do in production. They're not going to be able to download applications.

149
00:24:30.480 --> 00:24:43.399
Chris Feeney: Everything that you need that device to do, you have 100% complete control over that. And if something were to happen, it's just… just reboot it. Generally speaking, it's fine. You know, it's gonna come right back up.

150
00:24:43.400 --> 00:25:05.070
Chris Feeney: Like it was before. But what we're finding is, okay, if I'm going to be operating in a downtime somewhat scenario, am I getting to… what am I getting to? IGEL gives you all those options, right? I need to get to VDI, my backup VDI, or DAS, or, I just need a browser to get to Office, or whatever, so we can communicate with customers.

151
00:25:05.200 --> 00:25:20.369
Chris Feeney: take emails, or help desk call, whatever it is, right? And so IGEL gives you that flexibility, or you incorporate from a solution perspective, hey, Island's gonna be part of this, or whatever, you know, and you piece all those things together, now you have a solid solution.

152
00:25:20.820 --> 00:25:21.370
Andy Whiteside: Yeah.

153
00:25:21.570 --> 00:25:29.420
Andy Whiteside: Chris, I don't know if you can see what I'm doing on the screen, but I did a net stat on my Windows computer that I'm using for this. I'd love to see, like, a net stat, similar type thing on your IGEL unit.

154
00:25:29.680 --> 00:25:43.040
Andy Whiteside: you know, it's not just Windows. We spend a lot of time talking about Windows. It's not necessarily just Windows that's the blessing and the curse here. It's all those applications that either come on Windows or have been loaded

155
00:25:43.040 --> 00:25:50.739
Andy Whiteside: you know, after months and months and months of use on that Windows computer, it's not just a Windows might be our problem scenario on the endpoint, it's a…

156
00:25:50.740 --> 00:26:03.930
Andy Whiteside: a holistic platform of what's on top of Windows that could be the concern in the security model, and from an Agile perspective, we just limit it to what's appropriate, and you can't add more stuff to it, unless it's systematically done, therefore the problem doesn't exist.

157
00:26:04.580 --> 00:26:22.399
Chris Feeney: Yeah, and I, you know, I'll say this till I'm dead in my grave, for example. When I came to IGEL, I sold right into Federal. The very first thing I experienced selling into that market was, hey, we're gonna scan your operating system, first and foremost. I mean, we are a federal government entity, whatever, and so, go ahead.

158
00:26:22.760 --> 00:26:37.720
Chris Feeney: every single time they're scanning, just like you were saying, hey, what ports are open? I mean, they come back and they're like, we're not finding much here at all, and you know, they ask us, can we actually get into the device? I'm like, well, we don't allow for that by default, and…

159
00:26:37.720 --> 00:26:50.680
Chris Feeney: So, but we already had a limited capability, so if you have a bad actor scanning the network, looking for devices, they're gonna see, you know, very little when it comes to IGEL. They're like, I don't know what that is, and move on.

160
00:26:50.690 --> 00:26:56.930
Chris Feeney: It's very difficult to try to even break in because of the security posture, let alone

161
00:26:56.930 --> 00:27:13.740
Chris Feeney: allowing the user to modify or make changes that might open up a capability. Now, to your point, we have a top-notch security team that is always keeping their eyes open for, hey, is there anything out there that might impact us at the OS level or within an application, whatever, and so we…

162
00:27:13.740 --> 00:27:16.240
Chris Feeney: Stay on top of those regularly.

163
00:27:17.420 --> 00:27:32.490
Andy Whiteside: So, Chris, we're probably out of time at this point. I want to hit the last two sections here, why this matters. Going back to some numbers from the IBM study, 86% of organizations suffering operational downtime, lost productivity, all adds up to, let's see,

164
00:27:33.510 --> 00:27:43.579
Andy Whiteside: for average… 4.4 million in average daily costs when a data breach happens, over 10.22 million in the U.S. alone.

165
00:27:43.760 --> 00:27:45.260
Andy Whiteside: Trying to make this number.

166
00:27:45.880 --> 00:27:57.979
Andy Whiteside: A lot of money. A lot of money goes out the window when something bad happens. Again, it might not be an attack. It might just be, you know, somebody pushed out something that just took things down. It was supposed to help, and it actually hurt.

167
00:27:58.000 --> 00:28:13.970
Andy Whiteside: Let's go to this last section, and just kind of wrap this up. The title of this section from James is, A New Standard for Endpoint Resiliency and BCDR. Can you kind of help, explain how IGEL is looking at this through a different lens than everybody else has all these years?

168
00:28:14.310 --> 00:28:26.900
Chris Feeney: Yeah, so as we talked about earlier at the beginning of the podcast, there's been a lot of effort and strategies and plans built around, you know, accessing your backup site, your data backup site, that type of thing, whatever.

169
00:28:26.900 --> 00:28:33.159
Andy Whiteside: And not so much thinking about what do we do about the endpoints. And so, IJL was saying, we have.

170
00:28:33.320 --> 00:28:37.340
Chris Feeney: A solution for that. Use the same devices.

171
00:28:37.470 --> 00:28:55.319
Chris Feeney: and bring those devices back up in minutes versus days, or whatever, you know, and you have options, whether you want to do the dual boot, or the USB boot, or flat out take another device and plug it in and bring it online with just IGEL on it overall. You have all those options, and then…

172
00:28:55.550 --> 00:29:07.870
Chris Feeney: at the end of the day, what are you trying to get to? And you can know for sure that, hey, when I come to access those applications or data from a IGEL device, we know it's built on a top-notch security solution.

173
00:29:07.870 --> 00:29:20.789
Chris Feeney: From the ground up, and I'm going to have less there. So our point is, bring that endpoint strategy into full focus with, considering IGEL and our ability to get you up and running in minutes.

174
00:29:21.680 --> 00:29:33.829
Andy Whiteside: And doing that, and using the Agile solution, which is a great first step, which takes almost no effort to implement this, and very low-cost way to do it.

175
00:29:33.930 --> 00:29:39.049
Andy Whiteside: It just seems like you guys are connecting a dot for people that they didn't even, in many cases, realize need to be connected.

176
00:29:40.090 --> 00:29:57.680
Chris Feeney: Yeah, and as you've talked with Klaus, our CEO, and Jeff Mitchell, for example, what we're finding is that when it comes to these scenarios, there's an entire organization within an organization, you know, focusing on cyber insurance, recovery, whatever like that.

177
00:29:57.680 --> 00:30:08.209
Chris Feeney: And so, they're looking for solutions, and it's not necessarily, you know, the IT team, but that's a group within it that, hey, you know, this is something you can consider.

178
00:30:08.250 --> 00:30:12.620
Chris Feeney: Here's what we're saying. We have a solid solution for you.

179
00:30:12.620 --> 00:30:31.049
Andy Whiteside: Yeah. I bet every CISO out there is aware of this problem, and if they're not, the minute you kind of talk through this, they immediately see it as a problem, and it leads to a very easy conversation to have on the security side of the house, in addition to the end-user compute, PC, data center.

180
00:30:31.390 --> 00:30:50.179
Andy Whiteside: end-user compute team that we've been talking to all these years that see the problem, but it wasn't their charter to fix it. Now it's a joint effort to fix it, and you guys are providing a way to do that. I'm going to read this last paragraph from James, it really does sum it up. In an era where breaches and outages are inevitable, they will happen, they're going to happen, resilience is measured not just in whether you can recover.

181
00:30:50.290 --> 00:31:00.250
Andy Whiteside: Most people can somehow get recovered over a period of time, it's how fast you can recover, and that's what you guys are really solving here. And we're talking, you know, minutes at this point, not days or months.

182
00:31:00.570 --> 00:31:01.320
Andy Whiteside: For longer.

183
00:31:02.820 --> 00:31:05.070
Chris Feeney: 100%. That's really what it is.

184
00:31:05.700 --> 00:31:08.560
Andy Whiteside: Chris, I appreciate the time, and I look forward to the next conversation.

185
00:31:08.770 --> 00:31:10.440
Chris Feeney: Certainly. Always a pleasure, Andy.

186
00:31:10.440 --> 00:31:11.740
Andy Whiteside: Alright, thank you. Have a good day.