Rethinking Endpoint Strategy: Inside IGEL’s Preventive Security Model

In Episode 103 of IGEL Weekly, host Andy Whiteside and Chris Feeney dive deep into what it means to truly rethink endpoint strategy in 2025. Using James Millington’s recent blog as a guide, they explore IGEL’s Preventive Security Model — a lightweight, adaptive, and policy-aligned approach that moves beyond the bloated, reactive stacks of the past.

From Zero Trust architecture and business continuity planning to repurposing hardware for sustainability and simplifying mergers and acquisitions, Andy and Chris share how IGEL unifies hardware, applications, and security into a failsafe foundation for any organization. Whether you’re managing thousands of endpoints or just a few dozen, this conversation reveals why it’s time to break from the status quo and design for a secure, flexible, and future-ready digital workspace.

Transcript

WEBVTT

1
00:00:02.790 --> 00:00:10.690
Andy Whiteside: Hello, everyone! Welcome to Episode 103 of Igel weekly. I'm your host today, Andy Whiteside. I got Chris Feeney with me. Chris. How's things going.

2
00:00:11.420 --> 00:00:18.288
Chris Feeney: It's going. Well, man, it has been a fast start to the year, and I'm excited about

3
00:00:18.820 --> 00:00:24.510
Chris Feeney: just getting back and talking through all things, Igel again. So look forward to our conversation today.

4
00:00:24.860 --> 00:00:40.399
Andy Whiteside: I know we're going to talk about endpoint strategy with Igel, and that's probably the most top of mind thing for you. But what other than the topic for today. What's the most active conversations you're having, as it relates to Igel these days.

5
00:00:41.740 --> 00:01:05.259
Chris Feeney: Great question. So there's been a lot of talk which we'll speak about on 0 trust as multiple industries. Government has got a mandate to get to that. So and then you see this bleed over into areas like healthcare or retail. I mean, really kind of any industry manufacturing critical industries

6
00:01:05.260 --> 00:01:30.559
Chris Feeney: along with that. There's been a great set of conversations around the business continuity offering that we've put out there. We've got some exciting things that we've 1st of all announced it now and next back in Miami. And then we can talk about these in upcoming podcasts. But we last week launched the 1st piece of that

7
00:01:30.880 --> 00:01:44.149
Chris Feeney: in the ideal, managed Hypervisor. And then we've got our dual boot one that's coming scheduled before the end of this month. Hopefully, that happens before Labor Day. We're currently on target. We've got a lot of exciting

8
00:01:44.380 --> 00:01:50.599
Chris Feeney: things happening there. And and it's just bleeding into additional use cases. And so between

9
00:01:50.920 --> 00:02:04.439
Chris Feeney: a running us in production from a 0 trust perspective or okay, if something happens, I can switch over in a Dr. Scenario that we've got a lot of things happening in in terms of that today. So

10
00:02:05.034 --> 00:02:10.870
Chris Feeney: and it's opening up more and more use cases as we start talking to customers. So.

11
00:02:10.870 --> 00:02:11.440
Andy Whiteside: Yeah.

12
00:02:11.700 --> 00:02:18.180
Andy Whiteside: yeah, I'm I agree. I see customers coming with Igel use cases more and more which has to be exciting for you guys.

13
00:02:18.780 --> 00:02:20.610
Chris Feeney: Yeah, very much. So

14
00:02:21.650 --> 00:02:46.049
Andy Whiteside: So the blog for today, rethinking endpoint strategy with Ijo. I think that's kind of going to touch on what we were just discussing a little bit by James Millington, and this is from June 12th of this year, 2025. I'm just going to read the little intro here for decades. Endpoint strategies have been built on the assumption that compromise is inevitable. Layering tools, endless agents, endless agents, and sprawling recovery workflows

15
00:02:46.220 --> 00:03:14.520
Andy Whiteside: have centered around designing for compromised Failover monitor detect remediate a simple phrase that dramatically belies BALI. ES. The reality belies the reality of that process. By the way, Igel believes it's time to break that cycle. Chris, is this all coming back to the idea that windows is amazing and powerful. But there's problems with it.

16
00:03:15.270 --> 00:03:20.199
Chris Feeney: Absolutely. I think I mean, this is about a month

17
00:03:20.807 --> 00:03:26.039
Chris Feeney: go or so, you know, which last week, a week, a week, a week or 2 ago

18
00:03:26.220 --> 00:03:42.199
Chris Feeney: was the one year anniversary of, you know, a a major incident that occurred. You know, that realized how vulnerable, even in a protected scenario that these devices can be. Agel has been around, for, you know, 20 plus years built

19
00:03:42.730 --> 00:03:48.229
Chris Feeney: on the idea that you can run in an untrusted environment, you know, because of our approach.

20
00:03:49.030 --> 00:03:53.970
Chris Feeney: And so just sort of just kind of contrasting with, you know, this

21
00:03:54.190 --> 00:04:05.789
Chris Feeney: multiple layers of protection for an operating system that's been out there for, you know, 30 plus years. And you know there's there's what's interesting is

22
00:04:06.350 --> 00:04:11.430
Chris Feeney: Microsoft's now announced a feature to remove some of the bloat.

23
00:04:11.550 --> 00:04:14.910
Chris Feeney: meaning some of the things like Xbox or whatever.

24
00:04:15.120 --> 00:04:18.290
Chris Feeney: and like. And so our approach has always been.

25
00:04:18.500 --> 00:04:21.349
Chris Feeney: I like to say, why even start with bloat at all.

26
00:04:21.630 --> 00:04:25.500
Chris Feeney: And so just getting people to rethink this whole idea

27
00:04:25.970 --> 00:04:39.500
Chris Feeney: with regard to endpoint strategy. And I think what what I love about it is in many, many meetings and conversations I've had with you is you walk in, and you? One of the 1st things you bring up is, what's your endpoint strategy, and very often you get blank stares, you know.

28
00:04:40.010 --> 00:04:52.020
Andy Whiteside: Yeah. So the endpoint strategy is typically the same, more or less as it was 2030 years ago. Nothing's nothing's changed. And and I agree with what James is talking. By the way, the word belies is to give a a

29
00:04:52.720 --> 00:05:01.509
Andy Whiteside: false sense, or not not reality. The of the process. By the way. So look, it's

30
00:05:02.460 --> 00:05:15.499
Andy Whiteside: we have just been status quo, ish. We've got better tools, and they're more real time than ever. But throwing windows on endpoint and saying, That's your digital workspace, has just been the answer for.

31
00:05:15.790 --> 00:05:18.584
Andy Whiteside: Well, gosh, I'm 40 years now.

32
00:05:19.260 --> 00:05:34.209
Andy Whiteside: And for customers that are in the enterprise or not even the enterprise. But in in the work world they don't have to function this way. There are alternatives that are very functional and practical and end user friendly. And Igel is one of the answers there.

33
00:05:34.490 --> 00:05:59.290
Andy Whiteside: James has a little video, not a video, but a little cartoon here says it's got a dog standing next to a coffee cup, or sitting next to Coffee Cup with, says Monitor, detect, or mediate, and he's surrounded by flames and just sitting there. And the caption says, this is fine, it's not fine, and it's just a matter of time before it bites us all again. In fact, it's biting people all the time every day, whether they realize it or not.

34
00:06:00.200 --> 00:06:12.349
Chris Feeney: 100%. I mean, this is a famous, I mean, many people have already seen this cartoon before the house is burning down, and you're drinking coffee, like, everything's okay. And this is essentially the world we've lived in for many.

35
00:06:12.530 --> 00:06:29.760
Chris Feeney: for many, many decades at this point. And so people often ask, Well, what's your biggest competitor? Well, it's interesting, because Microsoft is actually quite a good partner of ours. But I always say it's the status quo. This is always the way we've done it.

36
00:06:29.790 --> 00:06:48.210
Chris Feeney: and you know, even back to our former. CEO, Jed, I mean the whole idea of disrupting that disrupting Euc. We had that as a tag for a while, and it's still relevant getting people to realize that there is a shift occurring as we've talked about that sort of

37
00:06:48.320 --> 00:07:17.540
Chris Feeney: at the end of the day. Why do I need a windows? OS, it's mainly because the applications that have been written for that and many of those becoming webified, available through other means. Primarily a browser, you know, kind of uncoupling from the necessary need of a windows. OS. Now that that will we call it the long tail of windows. There's a lot of apps that will be that way for a while, especially if they started on Prem. But anything cloud-based.

38
00:07:17.670 --> 00:07:23.909
Chris Feeney: you know, from the get go can often be done. Everything is done via Browser, and that gives you a lot of options.

39
00:07:24.411 --> 00:07:33.319
Chris Feeney: So that kind of leads into sort of where we're going in this particular blog. Later, down in the in the write up here.

40
00:07:33.320 --> 00:07:38.999
Andy Whiteside: So the statement after the cartoon is, this needs to be the error of designing for a failsafe.

41
00:07:40.220 --> 00:08:05.629
Andy Whiteside: and I'll add to that designing for a cell failsafe, but still focusing on end user experience and security, which would be part of both of those part of the failsafe but it doesn't have to be, doesn't have to be windows on the endpoint. And like you, said Microsoft, is a big partner of Igel these days, because I think they realize more than ever that solving that problem in a delivered format versus a deployed format is the Enterprise way to handle it.

42
00:08:07.030 --> 00:08:20.759
Chris Feeney: Absolutely, and then at scale, too. I mean, even you look at some of the stuff that came out during that incident. You know Scott, Manchester, who runs that Avd. And cloud PC. Practice there, Microsoft.

43
00:08:21.010 --> 00:08:41.000
Chris Feeney: He touted several times the ability to rapidly recover because you had options in the cloud for your windows, desktops. Whether it was a rapid restore of a snapshot, or whatever Igel on the endpoint not having been compromised at all, still up and running.

44
00:08:41.059 --> 00:08:53.509
Chris Feeney: You know it can easily get you to that. Or if you happen to have a device that does go down, you can switch out with our Ud pocket, for example, and boot to that environment. So

45
00:08:53.910 --> 00:08:58.559
Chris Feeney: but for that being said, you know, we kind of look at us like, hey?

46
00:08:59.020 --> 00:09:05.839
Chris Feeney: Why design from the get-go, knowing you've got a patch and put all this stuff on it. Just start with a

47
00:09:05.960 --> 00:09:12.519
Chris Feeney: a foundation that's already designed from a high security perspective to prevent a lot of that from the get. Go.

48
00:09:12.520 --> 00:09:13.099
Andy Whiteside: You know.

49
00:09:13.710 --> 00:09:24.340
Andy Whiteside: you know, we're having all these conversations. And this this doesn't address the fact that the future is probably a browser is the operating system of the future.

50
00:09:24.390 --> 00:09:39.149
Andy Whiteside: and the application being delivered as a web, app, or web. Native app is probably the future of a lot of this. It's going to happen where you're going to mitigate the need for windows, either as a delivered solution or as the endpoint solution.

51
00:09:39.150 --> 00:10:04.429
Andy Whiteside: That day is coming. It's just we're in this murky middle for now, and maybe for a very long time, and we've got to figure out how to address it. And that's what Igel is doing. This blog is, it's part of a series. 1, st one is preventive security model which we're going to talk about today. Second, one is preventive security architecture, which we'll talk about next time, and then the 3rd one is adaptive, secure, desktop. It kind of goes back to my mantra of.

52
00:10:04.610 --> 00:10:20.660
Andy Whiteside: you know in it. We do one thing, and that is, we provide access to applications, no matter how they're architected to users with a good user experience. And securely. And this this whole blog series is, gonna talk about the secure aspect of how we do that.

53
00:10:21.580 --> 00:10:23.560
Chris Feeney: Yeah, absolutely, so.

54
00:10:24.180 --> 00:10:46.869
Andy Whiteside: So this one is a preventive security model, and it's got one of the Igel wheels that covers a bunch of different topics that all centers back into the Igel world. Chris, can you kind of walk through the preventive security model of Igel and the Graphic that's on here to help us understand how Igel accomplishes this.

55
00:10:47.320 --> 00:11:09.069
Chris Feeney: So the model is, we call it this unifying framework right? And so by that Klaus, our CEO kind of talked about like the 3 ring circus. So Ijo being in the middle. And if you're at a circus you've got acts going on around, and the 3 ring circus is really focusing on. You know, you're unifying the application access.

56
00:11:09.070 --> 00:11:24.350
Chris Feeney: the hardware strategy, and of course, your security. So if we take, you know, at the very top, the endpoint hardware platforms. Obviously, Igel can repurpose existing devices. So extend the life of those

57
00:11:24.793 --> 00:11:38.990
Chris Feeney: by, you know, could be a number of years. And or you are looking for a net. New user experience. Maybe it's partners with Lenovo, lg, HP. For example, or others

58
00:11:39.080 --> 00:12:03.600
Chris Feeney: where you, they have a specific model that fits your needs, whether it's an all-in-one, a laptop, or an actual, thin, client form factor whatever. And so Ijo gives you that ability to be able to unify those. Even if you don't have a solid endpoint strategy in terms of a vendor, you could take different types of devices that are out there, convert them over. And now you have a

59
00:12:03.730 --> 00:12:09.460
Chris Feeney: a base operating system and a management system that can control all of those types of devices.

60
00:12:09.960 --> 00:12:39.289
Chris Feeney: Now that leads over to obviously applications. Right? What are you getting them to? Is it a virtual desktop? Is it a das offering? Is it just an enterprise, browser or Pwa, or something. And so that's where you can kind of begin unifying that application delivery. You have some scenarios where you might need a full desktop windows to do some work, and then others. You might be able to just work out of a browser all day long whether it's maybe a call center scenario. You just need a headset, a browser.

61
00:12:39.808 --> 00:12:41.679
Chris Feeney: and then, of course.

62
00:12:41.710 --> 00:13:09.640
Chris Feeney: on the security side, you kind of lean over there. Now you look at you know the trust and the access there unifying your identity. Access management, for example, maybe. Hey, you want to integrate with your intra, your octa. Maybe it's Ping or the Verizon and Omnisa with Workspace. One variety, you know, I mean, just hey? And then you've got security around there, or you want to have

63
00:13:09.760 --> 00:13:33.010
Chris Feeney: maybe a tool we are working with Zscaler, for example, and they've got their client connector where you can authenticate to that. Or now we just launched, I believe the Palo alto secure browser. We've also got the island browser. And so there's multiple options there that align some of that security strategy, whether it's internal to the network or when I'm traveling remotely

64
00:13:33.050 --> 00:13:44.710
Chris Feeney: and obviously pulls together. What you're trying to do at the end of the day is is, stay, keep those devices operational and protected from the ransomware or cyber attacks that might occur.

65
00:13:44.860 --> 00:14:11.910
Chris Feeney: So that's sort of what the preventive security model is is kind of unifying all those strategies and then around that and the outside of that circle, various types of projects that we found ourselves part of these days. Windows, 11. Migration upgrading. That's been a big one. Obviously a lot of devices that can't go, maybe can't go to Windows 11 for different reasons on the hardware. We can help idealize those, and then you can deliver that through another means

66
00:14:11.950 --> 00:14:30.289
Chris Feeney: business, continuity, disaster, recovery. We talked a little bit about that. With some of the options we offer there mergers, acquisitions. I know you probably as long as you've been around probably had customers where something like that occurred, and you're kind of unifying those companies together, or

67
00:14:30.600 --> 00:15:00.439
Chris Feeney: they've got contractors that need to access corporate resources. And then, of course, you've got the manageability, or you've got sustainability efforts. You're trying to check some boxes off with a green initiative whatever. There's a lot of these things that are happening. And then, of course, finally, total cost of ownership optimization. That's probably the bigger one, so that in a nutshell kind of pieces together what we call the preventative security model.

68
00:15:02.240 --> 00:15:03.999
Andy Whiteside: And and, Chris, all this

69
00:15:05.200 --> 00:15:25.640
Andy Whiteside: kind of leads back to the functionality being just as good or better in a world where we're in a in a connected world where this endpoint device that has a preventive security model can access what it needs to. And it's you know, a real time, fast experience, and secure at the same time.

70
00:15:26.080 --> 00:15:29.634
Chris Feeney: Yeah 100% and so what's interesting is

71
00:15:30.617 --> 00:15:58.559
Chris Feeney: we've actually internally began to deploying Igel corporate wide. And so we've done some analysis internally of all of our use cases. And so you'll we'll have options for virtual desktop, whether it's azure vd. Or cloud. PC, for example. Obviously a corporate browser. So we'll have some options there

72
00:15:58.610 --> 00:16:13.160
Chris Feeney: and then for those that might need what we just launched. The Igel managed Hypervisor, a virtual windows. 11, for example, that's corporate in tuned and everything. But you can run it locally if your endpoint can support it. For example, hardware, wise, which which most of them

73
00:16:13.390 --> 00:16:26.680
Chris Feeney: that they issue can. So we kind of have all those options available. And so we're going to be running this full time. So we're transitioning over to that right now. There's a portion of the company that are doing it. We're now just so, you know.

74
00:16:26.790 --> 00:16:35.090
Chris Feeney: we're we're over. I think we just went over 500 people globally. I don't know. The number is. So we're we're growing rather quickly. So.

75
00:16:35.270 --> 00:16:37.649
Andy Whiteside: Yeah. All as a company, over 500 people.

76
00:16:38.280 --> 00:16:41.867
Chris Feeney: That's my understanding. Yeah, so it's

77
00:16:42.380 --> 00:17:06.679
Andy Whiteside: My last comment was about the endpoint has shifted so much. Our strategy. Enterprise computing has moved, workloads have left the endpoint Sas Das and enterprise, browsers and Vdi. I threw that one in there now carry the weight of productivity users. Wrong devices are fluid, data must stay protected without relying on where it is physically lives. That goes back to my previous comment. I mean, it was one thing when things needed to be client server applications.

78
00:17:06.680 --> 00:17:15.390
Andy Whiteside: and the client did its execution. But the data and things came from the back end, or the entire data was encapsulated within the client

79
00:17:15.430 --> 00:17:36.239
Andy Whiteside: in enterprise, computing and in in work computing these days most of the time. That's not the case, and when it is, it can be virtualized through some, you know, desktop or app publishing solution. There's 1, 2, 3, 4 bullets here where Igel is talking through how the preventative security model provides framework that connects to these things. Can you walk through those.

80
00:17:36.890 --> 00:17:46.059
Chris Feeney: Yeah. So on the application front. That's a great point. I'm just thinking about it. Right? So we we've been tethered to data on the endpoint, you know.

81
00:17:46.320 --> 00:18:06.319
Chris Feeney: and getting used to, and I think for the younger generation, I would say, for folks like us or Gen. X. Or whatever we're kind of used to this idea, where everything, you know is sort of local. That was a model that we went to. We kind of pushed it away from the as 400 s. To the end. By our own personal computer.

82
00:18:06.420 --> 00:18:25.469
Chris Feeney: along comes this new digital Internet connected world. And that data doesn't have to be there on the endpoint. And so just I mean, I'm sitting here looking at my desk right? I've got my main laptop. I've got an ipad an iphone. I've got another Igel laptop here, and I could use any one of them to work.

83
00:18:25.570 --> 00:18:28.729
Chris Feeney: and I won't lose productivity. I can get up.

84
00:18:28.740 --> 00:18:57.439
Chris Feeney: go, run an errand, take a zoom call teams, call email, and my data is still there. I could even attach stuff or send links, or whatever all, just from my phone or my ipad or something, and I won't lose that because I don't have my windows laptop. That's the world that we live in today. And so when you extrapolate that to like all right? Well, if the data is not needed on the endpoint, and certainly for security reasons, is a great reason why you don't want to have it on the endpoint.

85
00:18:58.004 --> 00:19:14.779
Chris Feeney: Then it just sort of gives you more flexibility. Well, how do I deliver this to the user. I remember a couple of years ago, I think your kickoffs hard to believe is probably 2, 3 years ago, but your kickoff was in Nashville, and I said, I'm going to deliver this presentation from the browser, that's it.

86
00:19:15.520 --> 00:19:38.079
Chris Feeney: And so I fired up my Lg Gram and connected to your team's call and just pulled up a browser with Powerpoint and delivered it. It worked fine. It was totally fine. So and user experience didn't suffer the slides, you know work just as if it was Powerpoint on windows. So I think there's been a multiple angle here, right? And then, of course.

87
00:19:38.350 --> 00:19:59.719
Chris Feeney: the rise of progressive web apps. That's a new one, right where, you know, I just get an icon. It looks like an app. And it's really just in our case, like a chromium based browser that gives you. I was looking at an article yesterday, you know, if I want to look up Google Maps, you know, which is, I use that quite frequently, especially when I'm traveling, or something. Want to see what's going on around me, or looking.

88
00:19:59.910 --> 00:20:05.420
Chris Feeney: That could be a progressive web app on the endpoint. But there's no data there for the user. So.

89
00:20:05.780 --> 00:20:11.350
Andy Whiteside: So that's progressive web app is like a browser based, delivered app. But it looks and feels native to the endpoint.

90
00:20:11.350 --> 00:20:21.099
Chris Feeney: Exactly and it's man you. You look at an icon you launch, and it looks like it's a locally built app, and it's just running off a web framework. So

91
00:20:21.943 --> 00:20:36.029
Chris Feeney: so I, Joe, gives you all this flexibility. So right before this call I was on a call with a customer, and we were discussing sort of their production and healthcare strategy. And then what what would happen if they need to switch to their Dr. Site

92
00:20:36.190 --> 00:21:05.059
Chris Feeney: and the phase one was, just let's bring up an island browser, for example, which I know you guys use internally and then switch over to an Avd. Once they kind of got through the outage, or whatever or or make it flexible. They could do that if they need to. All still running Igel. And so it gives them that flexibility so they could take. If there is is a device that has to run windows for some reason they could switch it to Igel.

93
00:21:05.410 --> 00:21:13.349
Chris Feeney: migrate over, have access for a period of time, and then maybe switch it over to actual production. True productivity.

94
00:21:15.530 --> 00:21:18.950
Chris Feeney: Let's see the other bullet points in your 0 trust strategy. We talked about that.

95
00:21:19.836 --> 00:21:39.119
Chris Feeney: That's I mean the mantra there is, I mean, unlike, you know, Reagan kind of said it, you know. Trust, but verify. 0. Trust is no trust, always verify. And so you're in this model where you know it's it's not a it's it's not a product, and there's no one product that gives you all of what this

96
00:21:39.360 --> 00:21:41.210
Chris Feeney: architecture is about.

97
00:21:42.093 --> 00:21:51.979
Chris Feeney: But there are certain sort of pillars that kind of fall into various categories, whether it's on the endpoint or user level data level, that type of thing.

98
00:21:52.786 --> 00:21:57.040
Chris Feeney: And so it covers. Sorry. Go ahead. You have a question.

99
00:21:57.040 --> 00:22:16.930
Andy Whiteside: Well, I was going to come in the in the paragraph here. It says, you know, it's not one product. Trust is in a product. It's a 0 trust is from you. Don't buy 0 trust from a single company. But I will argue that when you start with something secure, like Igel, you are starting from a point of 0 trust and limited attack vector.

100
00:22:17.200 --> 00:22:23.819
Chris Feeney: 100%. That's we preach about that a lot because a lot of the stuff that's built around this model

101
00:22:24.660 --> 00:22:28.129
Chris Feeney: was for the status quo world when it comes to endpoints.

102
00:22:28.230 --> 00:22:33.549
Chris Feeney: And we talked about that earlier, there's a lot of products that were built to protect

103
00:22:33.560 --> 00:22:51.990
Chris Feeney: and provide some of these capabilities, and when we find ourselves going into conversations where we begin to kind of place ourselves on the endpoint, they naturally bring up a mapping to a 0 trust requirement or whatever. And they realize that wow, Ijo kind of eliminates these things already

104
00:22:52.000 --> 00:23:19.169
Chris Feeney: because of our architecture, the model that we've built from the ground up. And then you kind of layer in your, as I mentioned earlier. Okay, well, can I layer in an identity access management platform? Sure, you can set up an Igel device. So you log in to get to the Igel desktop as your identity, whether it's your corporate user account or active Directory or your Mfa. You have that option.

105
00:23:19.410 --> 00:23:36.409
Chris Feeney: If all you're doing is logging into a browser, you can make island, for example, or edge or something, you know. So it points to an idp. You authenticate again to get to your stuff here at Igel. If I go to office.com. I'm always going to have to go, Mfa.

106
00:23:36.830 --> 00:23:45.119
Chris Feeney: If I go to my Abd or Cloud, PC. I'm always going to go through that process every single time, regardless of where I'm coming from. So it never sort of

107
00:23:45.510 --> 00:23:50.090
Chris Feeney: gives me flexibility there. And that's fine. I mean, that's that's the.

108
00:23:50.200 --> 00:24:00.399
Chris Feeney: you know, conditional access piece that they've put in place. If I do travel to a country that is not my regular. Then I yeah, I have to put either request an access

109
00:24:00.590 --> 00:24:05.369
Chris Feeney: thing. So, hey, I'm I'm in. I'm in a conference somewhere in the world, or whatever, and

110
00:24:05.630 --> 00:24:09.920
Chris Feeney: you know it has to be made aware of it, so they will grant me that condition.

111
00:24:10.040 --> 00:24:14.110
Chris Feeney: So we have those things in place, and then the last 2

112
00:24:14.320 --> 00:24:31.749
Chris Feeney: I know, near and dear to you is the sustainability of it, equipment, right? Extending those life refreshing devices. And you know, giving them more time. Right? I mean, I see that in a number of things right? I went to buy some new shoes right? I'm a runner, and

113
00:24:31.860 --> 00:24:52.830
Chris Feeney: before I left there was a place where you can donate your old shoes if they're still in good working order or something. And so there's this concept to continue to give some life to that. And so when it's staggering, if you go to the dump to throw things away. The electronics section. Just amazing how much stuff you see there.

114
00:24:52.830 --> 00:24:53.400
Andy Whiteside: Come!

115
00:24:53.850 --> 00:25:02.379
Chris Feeney: That's probably still usable. Frankly, that just gets tossed and recycled somehow, some way.

116
00:25:02.690 --> 00:25:06.840
Chris Feeney: So. And then finally, the operational flexibility

117
00:25:07.550 --> 00:25:09.010
Andy Whiteside: I think, Chris, what you just said is interesting.

118
00:25:09.540 --> 00:25:37.729
Andy Whiteside: It's not this reuse. The hardware is reusable at least components of it, if not all of it. It's just the the industry has honestly created this motion that that Microsoft and and the PC. Makers have had for years, which is, you always need something new and better and more powerful because the legacy model needed the power to execute. I think a lot of the electronics industry is that way. And Pcs have been that way. And that's kind of the model you guys are breaking.

119
00:25:38.510 --> 00:25:44.320
Chris Feeney: Yeah. And you think about that. Now you hear? Like, I've been to several conferences in the last few months.

120
00:25:44.500 --> 00:25:47.419
Chris Feeney: and I look around, who's there? What are they promoting?

121
00:25:48.260 --> 00:25:52.900
Chris Feeney: And we're seeing more of the Aipc stuff out there now

122
00:25:53.170 --> 00:25:57.759
Chris Feeney: with the Npus, those new processors.

123
00:25:57.960 --> 00:26:02.670
Chris Feeney: And I think, as I began to look into that

124
00:26:02.830 --> 00:26:08.360
Chris Feeney: it was really like, All right. Well, are there applications that are going to truly be able to take advantage of that?

125
00:26:08.880 --> 00:26:11.940
Chris Feeney: Add that the you know. So

126
00:26:12.743 --> 00:26:17.970
Chris Feeney: again just promoting the status quo and the endpoint. But yet a net new.

127
00:26:18.330 --> 00:26:24.290
Chris Feeney: you know, hardware component. And and so I think we're starting to see some of that. And we're just saying.

128
00:26:24.560 --> 00:26:32.749
Chris Feeney: Hey, you might want to, you know. Give some thought to that. Now there's arguments for maybe running those workloads on the endpoint, not in the cloud.

129
00:26:33.210 --> 00:26:38.309
Chris Feeney: you know, and that's we're not going to debate that today. But but again, we're just sort of

130
00:26:38.840 --> 00:26:47.150
Chris Feeney: the whole title is just rethinking your entire strategy. And what I like about working with you guys is that you go in there and you help them understand that.

131
00:26:47.330 --> 00:26:48.340
Chris Feeney: You know

132
00:26:48.690 --> 00:27:00.400
Chris Feeney: end of the day. You're about delivering a digital workspace. Your endpoint has to be considered in that, and a lot of people seem to. Sometimes they forget about that. They don't really think about it from the beginning. So.

133
00:27:00.830 --> 00:27:20.600
Andy Whiteside: They either forget about it or they assume it's the end, all be all which is really what's happened all these years it's been the point of the point of the digital workspace and the actual execution the last bullet here is operational flexibility. You talked about mergers, acquisition onboarding folks. That's where this really is. A game changer.

134
00:27:21.295 --> 00:27:33.749
Chris Feeney: So, so we were talking this recent with a customer. Right? If you have devices that are coming online in in the network, and they're able to communicate directly to ums our management system.

135
00:27:34.519 --> 00:27:46.670
Chris Feeney: You can do what's called a 0 touch deployment, you know. You can literally, you can push the Igel OS components down to a windows machine. Convert it.

136
00:27:46.850 --> 00:27:48.990
Chris Feeney: It comes up, registers.

137
00:27:49.130 --> 00:28:07.609
Chris Feeney: and you never physically touch the machine, and you can get it all configured and switched over. You can also ship a device to a user and say simple instructions. You're going to boot it up. You're going to go through some clicks. Get it on your home network, or whatever you're going to come to a screen type in your corporate email address.

138
00:28:07.920 --> 00:28:18.650
Chris Feeney: And you're going to get walked through, and it's going to register, and then from there you can configure it gets configured and moved into essentially the right bucket, if you will.

139
00:28:18.830 --> 00:28:35.529
Chris Feeney: And that user's up and running in just a matter of minutes. Certainly during A. M. And A. If you take over an organization, and the next day. You want to switch them over to your corporate stuff, you know. We can do that by converting the devices or the Ud. Pocket, plug it in.

140
00:28:35.530 --> 00:28:52.719
Chris Feeney: pre-configured or not. And now you're operating from the net new company environment. And then the old stuff is either taken care of down the road or whatever. So the point is, you have flexibility, and you can adapt based on that, and don't have to

141
00:28:52.750 --> 00:29:03.989
Chris Feeney: worry about. You know things such as joining those devices to a domain and doing the trust. None of that really is needed. If you want to put Igel in the endpoint.

142
00:29:06.451 --> 00:29:18.199
Andy Whiteside: Chris, the next section talks about, you know, being the force multiplier for the preventive security model across the different partners you guys have in the segment. Can we talk through these? These 4 different pieces here.

143
00:29:18.410 --> 00:29:43.589
Chris Feeney: Yeah, kinda it's a great point. So I mentioned earlier about our our partners in the hardware sector. Right? Igel doesn't build hardware anymore. We just focus on the software. And so we've got leading oems out there that have amazing hardware in my purview here. I've got Dell, although not one of our official partners. But I've got a dell device I've repurposed. I've got HP, I've got Lenovo. I've got lg variety of different platforms.

144
00:29:43.590 --> 00:30:05.500
Chris Feeney: All can run and have been checked off the list to run the Igel OS, and then we've got a longer list that beyond the ones that have gone through official testing or whatever. There's a large number of devices out there that are x 86, 60, four-bit compatible, and we can repurpose those just as easily.

145
00:30:05.520 --> 00:30:31.670
Chris Feeney: and then sort of bleeding into. Okay. Well, now, I've established OS on the endpoint of choice or choices. Now, any corporate user is going to be tied to some kind of identity. And so we've got strong partnerships with one I've mentioned before. Whether it's intra omnisa, one workspace, one imprivada octoping all providing integrated sso and Mfa functionality.

146
00:30:32.087 --> 00:30:49.809
Chris Feeney: And then, and so that delivers, you know, various types of integrations with those whether everything is like for Microsoft, for example, we have the intune app so you could take an Igel device, put the intune app on it, register it officially with your intune instance.

147
00:30:50.030 --> 00:31:06.660
Chris Feeney: It doesn't mean you're replacing ums to manage it just means, hey? That device is now a known entity, and when I go to access Edge or Avd, or whatever I know that that device is known and trusted and and then the user is able to authenticate. So it's just another layer

148
00:31:07.320 --> 00:31:30.400
Chris Feeney: on the security side. We announced a lot of this starting, I think, late last year. But we've got customers where they use like the Zscalar. They just take a browser and go through the Zscaler portal. I'll call it that. And so there's no Zscaler client connector running. But we are working with Zscaler now to build that for their

149
00:31:30.470 --> 00:31:46.349
Chris Feeney: I'm going to get it wrong, their private Internet access or Pia. And then there's another one, too. But again, all of that is based on identity. So the the layer above that you identify yourself, and then Zscaler can route traffic or give you access to resources based on your identity.

150
00:31:46.900 --> 00:31:57.840
Chris Feeney: Palo Alto. We just released the prism browser. I think it's available in the Igel app portal now secure browser, very similar to island.

151
00:31:58.080 --> 00:32:25.200
Chris Feeney: and then partner with companies like Netsco for for enforcement with secure service edge, sassy type stuff. And so these are where things are going. And then, of course, you have a lot of stuff you plug into the device or need to use the peripheral support. Whether it's headsets, video webcams across all these different industries, speech mics, smart cards.

152
00:32:25.500 --> 00:32:33.300
Chris Feeney: document scanners, signature pads. I mean all this stuff that you would use whenever I walk into some office dental office.

153
00:32:33.817 --> 00:32:36.850
Chris Feeney: Retail whatever I look at what's plugged in, and

154
00:32:37.140 --> 00:32:51.969
Chris Feeney: and those common devices are what we're talking about. So we kind of help weave all that together with our partnership, whether it's a actual technical integration, there's an app or something that's weaving it together, or if it's more of a better together story.

155
00:32:52.120 --> 00:32:58.040
Chris Feeney: a good example of that would be Nerdio. We don't have a technical integration, but they save money

156
00:32:58.350 --> 00:33:06.440
Chris Feeney: managing your costs in azure. We save you a ton of money on the endpoint management costs and operational pieces.

157
00:33:06.440 --> 00:33:07.080
Andy Whiteside: Right?

158
00:33:08.760 --> 00:33:12.589
Andy Whiteside: Yeah, it goes. You know, goes back to the idea that this is.

159
00:33:12.920 --> 00:33:33.520
Andy Whiteside: it's all got to come together. If we're going to replace this beautiful magical windows, endpoint, workload and replace it with a delivered windows or delivered application scenario. We've got to have our lessened attack vector together, which Igel does out of the gate. But all this other stuff the pieces of the

160
00:33:33.740 --> 00:33:39.229
Andy Whiteside: community have to come together and still work. And you guys have done a great job onboarding partners to do that.

161
00:33:40.060 --> 00:33:48.490
Chris Feeney: Yeah, my my role. Now in vertical solutions, I'm looking at it at where all these things come together across the different verticals we sell into. So

162
00:33:48.700 --> 00:34:06.780
Chris Feeney: you know, we we have solid delivery solutions in in healthcare retail, for example, financial services with some options right? Depending on what the customer's back end might be, or whatever. And so but at the end of the day we talk about it.

163
00:34:06.880 --> 00:34:20.740
Chris Feeney: It has to be great user experience, and users need to accept that and and then obviously be able to be productive. And so but but it has to start with the foundation. So we always lead with security

164
00:34:21.000 --> 00:34:30.709
Chris Feeney: as the baseline, and then build on top of that the management capabilities, the partnerships, and then, of course, leading to what is the outcome.

165
00:34:31.100 --> 00:34:33.290
Chris Feeney: Well, the outcome might be

166
00:34:33.300 --> 00:35:03.190
Chris Feeney: a business continuity scenario, a fast recovery, you know. Scenario M and a acceleration. We talked about that windows, 11 readiness shifting to windows in the cloud, the sustainability, and of course, the 0 trust piece piecing all those things together. And so the point we're making here is that Igel, as your endpoint strategy from the get go can can help you with all of these different areas across multiple different industries.

167
00:35:03.190 --> 00:35:20.050
Andy Whiteside: Yeah, Chris, it's been. It's been interesting to me to watch. We just picked up a client with about 25 users. They're part of a much, much larger enterprise company, but they're completely hands off and managed by themselves, and they deliver for the entire company 25 virtual desktops, all persistent

168
00:35:20.060 --> 00:35:40.430
Andy Whiteside: to Igel endpoints, and it's been interesting to watch a small company with enterprise needs attack this and do it successfully with a delivered compute model and a very much secure but in user enabled endpoint. Like Igel, it's it's been interesting to watch them accomplish this without

169
00:35:40.570 --> 00:35:45.230
Andy Whiteside: the the scalable needs that some of the larger companies we deal with work that have.

170
00:35:46.300 --> 00:35:49.719
Chris Feeney: That's a great point. We haven't really talked too much about it. But briefly.

171
00:35:50.444 --> 00:36:02.139
Chris Feeney: switching, we have seen customer by switching to agile on the endpoint. Now the operational cost well, how many people does it take to manage these devices? Do I need, you know, 50 people.

172
00:36:02.580 --> 00:36:15.419
Chris Feeney: you know, to manage 50,000 endpoints, or what? And so we we know we've got customers out there where it's maybe one to 2 people managing tens of thousands of devices. You can get to that type of scale.

173
00:36:16.180 --> 00:36:40.319
Chris Feeney: you know, free up some of those other staff for other type of more strategic projects. But you're not Manning, you know, providing a lot of manpower to manage these devices once you get them set up and configured, and then, obviously, partners like yourself that can provide that capability delivering on projects or in the Msp. World, managing it at the end of the day for the customer soup to nuts.

174
00:36:41.240 --> 00:36:48.259
Andy Whiteside: Yeah, Chris, I think we've wrapped it up here for this part, so I'll I'll read one. James's last

175
00:36:48.430 --> 00:37:11.700
Andy Whiteside: bullets here last paragraphs where traditional endpoint. Stacks are active and bloated or reactive and bloated. Psm. Is lightweight, adaptive, and policy aligned. A failsafe foundation for cloud 1st enterprises. I'm going to change that last piece of cloud 1st companies, right? Because the Enterprise word gets used a lot to talk about the big big boys. And like, I was just pointing out small customer of ours.

176
00:37:11.700 --> 00:37:27.779
Andy Whiteside: 25 users is doing this type of solution, and it's truly enabled them to have a smaller lightweight. Staff mergers and acquisitions can happen. They can grow. They're secure by design. Really, an enterprise class solution for companies of all sizes.

177
00:37:28.300 --> 00:37:30.560
Chris Feeney: Yeah, yeah, that's great to hear.

178
00:37:30.560 --> 00:37:42.329
Andy Whiteside: Next up in this series is preventative security architecture. We'll try to get this one done in the next week or 2 and and get it out and and cover what James covers in that one, and get this content in front of our listeners.

179
00:37:43.080 --> 00:37:45.600
Chris Feeney: Well, always a pleasure, Andy appreciate it.

180
00:37:45.610 --> 00:37:50.200
Andy Whiteside: Chris. Thanks for the time today. And I guess it's Tuesday. So hopefully got a

181
00:37:50.550 --> 00:37:53.550
Andy Whiteside: rest of the week. You can get some stuff done, and

182
00:37:53.850 --> 00:37:55.710
Andy Whiteside: and try to have some fun at the same time.

183
00:37:56.580 --> 00:37:59.129
Chris Feeney: Always we'll try. Take care, man, thank you.

184
00:37:59.130 --> 00:38:00.799
Andy Whiteside: Alright talk again later. Thank you.