1
00:00:00,000 --> 00:00:04,850
Before we really dive in today, just a quick word about the supporter who helps

2
00:00:04,850 --> 00:00:05,680
make this possible.

3
00:00:05,680 --> 00:00:09,520
SafeServer. They're dedicated to hosting software like the kind we're discussing

4
00:00:09,520 --> 00:00:09,600
and

5
00:00:09,600 --> 00:00:18,560
supporting your digital transformation. You can find out more at www.feserver.de.

6
00:00:18,560 --> 00:00:24,090
Okay, so let's unpack this. We're looking at something today that's, well, it's

7
00:00:24,090 --> 00:00:24,320
really

8
00:00:24,320 --> 00:00:29,270
changing how we think about using computers, especially when security is a big deal.

9
00:00:29,270 --> 00:00:29,520
Imagine

10
00:00:29,520 --> 00:00:34,390
this, what if your desktop or even just your web browser wasn't actually running on

11
00:00:34,390 --> 00:00:34,960
your physical

12
00:00:34,960 --> 00:00:39,440
computer? Exactly. Instead, it's running somewhere else securely and just streamed

13
00:00:39,440 --> 00:00:40,000
to you. We're

14
00:00:40,000 --> 00:00:43,910
talking about Ketham workspaces and this idea of container streaming. Right, so you

15
00:00:43,910 --> 00:00:44,560
open a browser

16
00:00:44,560 --> 00:00:48,690
tab and boom, there's your secure environment. That's the core idea. And for anyone

17
00:00:48,690 --> 00:00:49,200
listening

18
00:00:49,200 --> 00:00:52,880
who's curious about secure remote access but maybe finds the tech talk a bit much,

19
00:00:52,880 --> 00:00:53,600
things like zero

20
00:00:53,600 --> 00:00:57,760
trust or containerized desktop infrastructure, our mission today is pretty simple.

21
00:00:57,760 --> 00:00:58,480
We're translating

22
00:00:58,480 --> 00:01:02,430
it, right? Making it clear. Exactly. We want to give you a clear, practical

23
00:01:02,430 --> 00:01:03,520
understanding of what

24
00:01:03,520 --> 00:01:07,720
this means and why it matters. It's sort of a shortcut into this next wave of

25
00:01:07,720 --> 00:01:08,720
remote computing.

26
00:01:08,720 --> 00:01:13,360
And the big takeaway really seems to be this. Whether it's a browser, an app, or a

27
00:01:13,360 --> 00:01:14,560
full desktop,

28
00:01:14,560 --> 00:01:18,350
it gets streamed to whatever device you have, wherever you are. Your laptop, your

29
00:01:18,350 --> 00:01:18,800
tablet.

30
00:01:18,800 --> 00:01:23,440
It almost doesn't matter for security. That's the promise. The device becomes less

31
00:01:23,440 --> 00:01:24,160
important than the

32
00:01:24,160 --> 00:01:28,880
secure access itself. Okay, let's dig into the basics then. We've heard of VDI

33
00:01:28,880 --> 00:01:29,760
virtual desktop

34
00:01:29,760 --> 00:01:35,920
infrastructure for years, but the material we looked at really emphasizes that Chasm

35
00:01:35,920 --> 00:01:36,160
uses

36
00:01:36,160 --> 00:01:42,600
something different. A workspace streaming platform based on containerized desktop

37
00:01:42,600 --> 00:01:43,360
infrastructure or

38
00:01:43,360 --> 00:01:47,920
CDI. Why is that difference so important? Well, think of it like this. Old VDI was

39
00:01:47,920 --> 00:01:48,400
maybe like

40
00:01:48,400 --> 00:01:52,610
needing a whole separate car for every single trip you take. Each user needed a

41
00:01:52,610 --> 00:01:53,280
full copy of

42
00:01:53,280 --> 00:01:57,110
the operating system, like Windows. Super heavy, resource intensive. Right, I

43
00:01:57,110 --> 00:01:58,000
remember those being

44
00:01:58,000 --> 00:02:02,610
slow to start up. Exactly. CDI though uses Linux containers. It's much more

45
00:02:02,610 --> 00:02:03,840
efficient. Think more

46
00:02:03,840 --> 00:02:07,770
like a modern hybrid car using a shared engine efficiently. So everyone's using the

47
00:02:07,770 --> 00:02:08,480
same core

48
00:02:08,480 --> 00:02:13,070
engine, the Linux kernel, but they get their own isolated space. Precisely. You

49
00:02:13,070 --> 00:02:14,000
share the underlying

50
00:02:14,000 --> 00:02:19,510
kernel, which saves a ton of resources, compute, memory, disk space, and this leads

51
00:02:19,510 --> 00:02:20,960
to two huge

52
00:02:20,960 --> 00:02:26,400
advantages. Speed and efficiency. We're talking desktops booting up in seconds,

53
00:02:26,400 --> 00:02:27,280
literally seconds.

54
00:02:27,280 --> 00:02:32,420
Not minutes like the old VDI. No way. And that efficiency, that speed, is what

55
00:02:32,420 --> 00:02:33,440
makes it practical

56
00:02:33,440 --> 00:02:37,440
for these workspaces to be, well, disposable. You can create one instantly and

57
00:02:37,440 --> 00:02:39,040
destroy it just as fast.

58
00:02:39,040 --> 00:02:42,960
And that disposable aspect is key for the security side, which I definitely want to

59
00:02:42,960 --> 00:02:43,760
get into.

60
00:02:43,760 --> 00:02:48,080
But hang on a sec. If I'm streaming a whole desktop through a browser tab,

61
00:02:48,080 --> 00:02:52,320
I'm thinking about lag. You know, is it going to feel sluggish compared to my local

62
00:02:52,320 --> 00:02:52,880
machine?

63
00:02:52,880 --> 00:02:54,720
Yeah. Especially with graphics or video?

64
00:02:54,720 --> 00:02:57,440
That's a fair question. And with older tech, maybe.

65
00:02:57,440 --> 00:03:01,520
But Chasm uses their own open source tech called ChasmVNC. It's not your grandpa's

66
00:03:01,520 --> 00:03:02,080
VNC.

67
00:03:02,080 --> 00:03:03,440
Okay. So what's different about it?

68
00:03:03,440 --> 00:03:07,120
It's specifically built for this job, streaming securely and efficiently to a web

69
00:03:07,120 --> 00:03:07,920
browser.

70
00:03:07,920 --> 00:03:12,390
It uses modern web protocols to send just the visual output, the pixels, to your

71
00:03:12,390 --> 00:03:13,280
browser tab.

72
00:03:13,920 --> 00:03:18,730
The result is remarkably smooth, low latency, and feels surprisingly close to

73
00:03:18,730 --> 00:03:19,360
native,

74
00:03:19,360 --> 00:03:20,960
even for demanding apps.

75
00:03:20,960 --> 00:03:24,080
Got it. So the tech is there to make the experience good.

76
00:03:24,080 --> 00:03:26,960
And it's not just a small experiment, is it?

77
00:03:26,960 --> 00:03:32,160
The source mentioned over 100 million polls on Docker Hub. That sounds like a lot.

78
00:03:32,160 --> 00:03:35,360
It is. That kind of number shows serious adoption.

79
00:03:35,360 --> 00:03:39,240
It means hundreds of organizations, big ones, trust this approach. It's not just

80
00:03:39,240 --> 00:03:39,760
theory.

81
00:03:39,760 --> 00:03:44,290
It's verified enterprise-grade technology. It proves the container model works

82
00:03:44,290 --> 00:03:45,360
reliably at scale.

83
00:03:45,360 --> 00:03:48,560
Which you'd need if you're spinning up and carrying down potentially thousands of

84
00:03:48,560 --> 00:03:48,800
these

85
00:03:48,800 --> 00:03:49,840
sessions constantly.

86
00:03:49,840 --> 00:03:53,440
Absolutely. That reliability and scale are crucial for making this whole

87
00:03:53,440 --> 00:03:55,520
disposable model work seamlessly.

88
00:03:55,520 --> 00:04:00,560
Okay. So speed, efficiency, scalability. Check. Now, let's talk security.

89
00:04:00,560 --> 00:04:02,880
This seems to be where things get really interesting.

90
00:04:02,880 --> 00:04:05,600
The core idea mentioned is browser isolation.

91
00:04:05,600 --> 00:04:09,280
How does that fit into this zero trust idea we hear so much about?

92
00:04:09,280 --> 00:04:13,680
Right. Zero trust basically means don't trust anything by default.

93
00:04:13,680 --> 00:04:18,480
Verify everything. Browser isolation is a perfect example of that in action.

94
00:04:18,480 --> 00:04:20,320
Let's say your computer is your house, right?

95
00:04:20,320 --> 00:04:21,040
Okay, yeah.

96
00:04:21,040 --> 00:04:24,480
Normally when you browse the web, especially clicking unknown links or

97
00:04:24,480 --> 00:04:28,000
downloading files, you're potentially inviting threats into your house.

98
00:04:28,000 --> 00:04:30,720
Malware, ransomware.

99
00:04:30,720 --> 00:04:32,080
You're letting them through the front door.

100
00:04:32,080 --> 00:04:35,200
Exactly. Browser isolation puts a stop to that.

101
00:04:35,200 --> 00:04:39,840
The actual browsing, all the risky stuff, rendering webpages, running scripts,

102
00:04:39,840 --> 00:04:43,840
handling potentially malicious content happens outside your house.

103
00:04:43,840 --> 00:04:47,600
It happens remotely inside one of the secure disposable containers.

104
00:04:47,600 --> 00:04:52,640
So the container is like a detached secure shed where the risky stuff happens.

105
00:04:52,640 --> 00:04:53,600
That's a great way to put it.

106
00:04:53,600 --> 00:04:56,960
The container acts as that zero trust secure web intermediary.

107
00:04:56,960 --> 00:04:59,200
All that comes back to your actual computer, your house,

108
00:04:59,200 --> 00:05:03,200
is a safe stream of pixels showing you what's happening in the shed.

109
00:05:03,200 --> 00:05:05,440
The threat never gets near your local machine.

110
00:05:05,440 --> 00:05:08,240
So I click on ransomware, it executes in that container.

111
00:05:08,240 --> 00:05:11,520
Which is running on a server somewhere else, completely isolated.

112
00:05:11,520 --> 00:05:15,130
And then when you're done, the container is destroyed, taking the ransomware with

113
00:05:15,130 --> 00:05:15,280
it.

114
00:05:15,280 --> 00:05:17,520
Your laptop, your phone, your tablet,

115
00:05:17,520 --> 00:05:20,720
they're completely removed from the attack surface for that web activity.

116
00:05:20,720 --> 00:05:24,320
And the source mentioned this is coupled with controls for data loss prevention.

117
00:05:24,320 --> 00:05:25,600
Yes, absolutely.

118
00:05:25,600 --> 00:05:27,520
It's not just about stopping threats coming in.

119
00:05:27,520 --> 00:05:29,760
It's also about controlling data going out.

120
00:05:29,760 --> 00:05:34,760
You can set very specific rules about what users can copy, paste, download, or

121
00:05:34,760 --> 00:05:35,360
upload

122
00:05:35,360 --> 00:05:38,240
between the remote session and their local device.

123
00:05:38,240 --> 00:05:40,960
That leads us to the Chasm Cloud Browser.

124
00:05:40,960 --> 00:05:45,280
This sounds like browser isolation offered as a service you can just sign up for.

125
00:05:45,280 --> 00:05:48,800
The idea of a truly disposable browser is fascinating.

126
00:05:48,800 --> 00:05:51,360
What does that really mean for a user day to day?

127
00:05:51,360 --> 00:05:55,280
It's like having a magic reset button for your online identity and security

128
00:05:55,280 --> 00:05:56,480
for every single session.

129
00:05:56,480 --> 00:05:58,160
Every time you close that browser tab,

130
00:05:58,160 --> 00:06:01,760
the entire container environment it was running in is completely wiped.

131
00:06:01,760 --> 00:06:02,960
Poof. Gone.

132
00:06:02,960 --> 00:06:04,880
So no leftover malware?

133
00:06:04,880 --> 00:06:10,480
None. No tracking cookies, no browser history lingering, no cached files,

134
00:06:10,480 --> 00:06:15,520
no session fingerprints that websites use to track you across visits.

135
00:06:15,520 --> 00:06:17,680
Every single time you start a new session,

136
00:06:17,680 --> 00:06:22,240
it's like using a brand new, perfectly clean, fully patched browser

137
00:06:22,240 --> 00:06:24,080
that has never touched the internet before.

138
00:06:24,080 --> 00:06:27,120
You don't have to worry about clearing your cache or history

139
00:06:27,120 --> 00:06:28,960
because it's automatically obliterated.

140
00:06:28,960 --> 00:06:32,240
Exactly. Ultimate digital hygiene, automatically enforced.

141
00:06:32,240 --> 00:06:35,120
Okay. The source material brought up a really specific use case.

142
00:06:35,120 --> 00:06:40,960
OSINT Open Source Intelligence and something called Managed Attribution.

143
00:06:40,960 --> 00:06:45,040
That sounds pretty advanced. Why would researchers need that capability?

144
00:06:45,040 --> 00:06:45,920
Well, think about it.

145
00:06:45,920 --> 00:06:48,960
If you're an investigator, maybe a journalist or intelligence analyst

146
00:06:48,960 --> 00:06:53,600
looking into sensitive topics or say tracking threat actors online,

147
00:06:53,600 --> 00:06:58,160
you absolutely cannot have your research activities traced back to you or your

148
00:06:58,160 --> 00:06:58,880
organization.

149
00:06:58,880 --> 00:07:01,440
Because that could tick them off or reveal who's investigating them.

150
00:07:01,440 --> 00:07:05,600
Precisely. It could compromise the entire investigation or even put people at risk.

151
00:07:05,600 --> 00:07:07,840
Managed Attribution is designed to prevent that.

152
00:07:07,840 --> 00:07:10,720
How does it work then? How does it hide the origin?

153
00:07:10,720 --> 00:07:14,160
It ensures that all the technical details of your browsing session,

154
00:07:14,160 --> 00:07:18,400
the IP address your traffic seems to come from, the unique fingerprint of your

155
00:07:18,400 --> 00:07:19,040
browser,

156
00:07:19,040 --> 00:07:23,680
even the timing signals, all appear to originate from a generic anonymous location

157
00:07:23,680 --> 00:07:24,240
in the public

158
00:07:24,240 --> 00:07:28,480
cloud, often somewhere geographically distant. So it looks like the search is

159
00:07:28,480 --> 00:07:28,960
coming from

160
00:07:28,960 --> 00:07:33,440
some random cloud server, not my office. Correct. And because that container

161
00:07:33,440 --> 00:07:33,680
running

162
00:07:33,680 --> 00:07:38,240
the browser is instantly destroyed after the session, there's no persistent link,

163
00:07:38,240 --> 00:07:42,550
no trail connecting that specific activity back to the actual user or their

164
00:07:42,550 --> 00:07:43,600
organization.

165
00:07:43,600 --> 00:07:47,760
It provides anonymity and security through that instant digital amnesia.

166
00:07:47,760 --> 00:07:52,320
Okay, that makes sense for high security stuff. Let's pivot now to maybe more

167
00:07:52,320 --> 00:07:53,280
everyday business

168
00:07:53,280 --> 00:07:58,060
use and compliance. How does this container streaming translate into practical

169
00:07:58,060 --> 00:07:58,560
tools for

170
00:07:58,560 --> 00:08:02,800
remote work? This is where we get into desktop as a service, or DES. Instead of

171
00:08:02,800 --> 00:08:03,600
managing physical

172
00:08:03,600 --> 00:08:08,260
laptops for everyone, organizations can provide cloud desktops on demand. Users get

173
00:08:08,260 --> 00:08:08,960
access to a

174
00:08:08,960 --> 00:08:13,680
full desktop environment, Windows, Linux, maybe even Mac OS within seconds, just by

175
00:08:13,680 --> 00:08:14,080
opening the

176
00:08:14,080 --> 00:08:18,640
browser. And it's scalable. Easy to add or remove users. Infinitely scalable,

177
00:08:18,640 --> 00:08:19,760
essentially. And

178
00:08:19,760 --> 00:08:23,480
because it's streamed, the user experience is consistent whether they're using a

179
00:08:23,480 --> 00:08:24,160
low-powered

180
00:08:24,160 --> 00:08:28,770
Chromebook or a high-end workstation. Their secure work environment lives in the

181
00:08:28,770 --> 00:08:29,200
cloud,

182
00:08:29,200 --> 00:08:34,480
accessible from anywhere. That flexibility sounds great. But what about a really

183
00:08:34,480 --> 00:08:34,880
common

184
00:08:34,880 --> 00:08:38,880
headache for IT legacy applications? Yeah. You know, that one critical piece of

185
00:08:38,880 --> 00:08:39,760
software that

186
00:08:39,760 --> 00:08:44,480
only runs on an old version of Java or maybe uses Adobe Flash. Oh yeah, the bane of

187
00:08:44,480 --> 00:08:45,120
many IT

188
00:08:45,120 --> 00:08:49,200
departments. They can't update the operating system because it breaks the app, but

189
00:08:49,200 --> 00:08:50,000
running the old

190
00:08:50,000 --> 00:08:54,320
stuff is a massive security risk. Right. So how does this help? This is where app

191
00:08:54,320 --> 00:08:55,200
streaming becomes

192
00:08:55,200 --> 00:09:00,560
a lifesaver. Chasm allows organizations to host those legacy applications, Flash,

193
00:09:00,560 --> 00:09:01,200
old Java,

194
00:09:01,200 --> 00:09:06,070
whatever it is, inside one of these secure, isolated containers. So the risky old

195
00:09:06,070 --> 00:09:06,720
app runs

196
00:09:06,720 --> 00:09:10,820
remotely in its own little sandbox. Exactly. The user accesses it through their

197
00:09:10,820 --> 00:09:11,840
browser, just like

198
00:09:11,840 --> 00:09:16,160
any other web app. It works, they can do their job, but the application itself,

199
00:09:16,160 --> 00:09:17,040
with all its potential

200
00:09:17,040 --> 00:09:21,310
vulnerabilities, never gets installed on their local machine. It stays contained.

201
00:09:21,310 --> 00:09:21,680
The risk is

202
00:09:21,680 --> 00:09:26,580
quarantined, basically, and when they close the tab, the container and the risk

203
00:09:26,580 --> 00:09:27,520
disappears.

204
00:09:27,520 --> 00:09:33,140
No installation, no local maintenance burden, and the security hole is plugged. It's

205
00:09:33,140 --> 00:09:34,160
a fantastic way

206
00:09:34,160 --> 00:09:38,890
to handle technical debt and keep essential but outdated systems running safely.

207
00:09:38,890 --> 00:09:39,280
Let's bring in

208
00:09:39,280 --> 00:09:42,990
those examples from the source material to make it real. There was a realtor

209
00:09:42,990 --> 00:09:44,160
mentioned. Why would

210
00:09:44,160 --> 00:09:49,870
a realtor need this? Seems like an everyday job. Well, think about Diane, the realtor.

211
00:09:49,870 --> 00:09:50,240
Her job

212
00:09:50,240 --> 00:09:54,620
involves constantly visiting unfamiliar websites from clients, opening documents

213
00:09:54,620 --> 00:09:55,680
attached to emails

214
00:09:55,680 --> 00:09:59,390
from unknown senders, checking various webmail accounts. Okay, yeah, lots of

215
00:09:59,390 --> 00:10:00,400
potential phishing

216
00:10:00,400 --> 00:10:05,510
links and dodgy attachments there. Right. So she used a Chasm cloud desktop. All

217
00:10:05,510 --> 00:10:06,160
that potentially

218
00:10:06,160 --> 00:10:10,320
risky activity happened in the disposable cloud environment. If she clicked a bad

219
00:10:10,320 --> 00:10:11,040
link or opened

220
00:10:11,040 --> 00:10:15,030
a malicious PDF, it hit the container, not her personal computer where she keeps

221
00:10:15,030 --> 00:10:15,920
client info and

222
00:10:15,920 --> 00:10:19,480
financials. Peace of mind. Makes sense. And then there was the cybersecurity

223
00:10:19,480 --> 00:10:20,400
principle using it

224
00:10:20,400 --> 00:10:24,650
for threat intelligence. That ties back to the OSINT and managed attribution we

225
00:10:24,650 --> 00:10:25,520
discussed.

226
00:10:25,520 --> 00:10:30,010
Exactly. It perfectly illustrates that high-end security use case hunting for

227
00:10:30,010 --> 00:10:30,960
threats online,

228
00:10:30,960 --> 00:10:35,440
anonymously and safely, knowing that the malware they might encounter is completely

229
00:10:35,440 --> 00:10:36,160
isolated and

230
00:10:36,160 --> 00:10:40,000
disposable. It really shows the range, doesn't it? From protecting a realtor,

231
00:10:40,000 --> 00:10:41,200
opening emails,

232
00:10:41,200 --> 00:10:44,880
to securing an advanced threat hunter. It does. The core principle of secure,

233
00:10:44,880 --> 00:10:49,040
disposable, streamed environments applies across the board. Okay. One more critical

234
00:10:49,040 --> 00:10:49,440
area for

235
00:10:49,440 --> 00:10:56,270
businesses. Compliance. Dealing with regulations like SOC 2, NIST, HIPAA, ISO. It's

236
00:10:56,270 --> 00:10:58,160
complex. Yeah.

237
00:10:58,160 --> 00:11:01,840
How does a platform like this help? It helps significantly. A major part of

238
00:11:01,840 --> 00:11:02,560
compliance is

239
00:11:02,560 --> 00:11:06,700
controlling where sensitive data lives and who can access it and how. Because Chasm

240
00:11:06,700 --> 00:11:07,120
keeps the

241
00:11:07,120 --> 00:11:11,160
applications and data within the organization's controlled infrastructure, it never

242
00:11:11,160 --> 00:11:11,680
actually

243
00:11:11,680 --> 00:11:15,510
resides on the user's potentially insecure personal device. It simplifies things

244
00:11:15,510 --> 00:11:16,400
dramatically.

245
00:11:16,400 --> 00:11:21,630
So the data doesn't leak out onto unmanaged laptops? Correct. It acts as a secure

246
00:11:21,630 --> 00:11:22,160
gateway

247
00:11:22,160 --> 00:11:26,240
to corporate resources. You access what you need through the secure stream, but the

248
00:11:26,240 --> 00:11:27,040
data itself

249
00:11:27,040 --> 00:11:31,880
stays put. This reduces the need for traditional VPNs, which can have their own

250
00:11:31,880 --> 00:11:33,040
vulnerabilities,

251
00:11:33,040 --> 00:11:37,280
and it makes demonstrating control for audits much easier. You're minimizing the

252
00:11:37,280 --> 00:11:37,920
data leakage

253
00:11:37,920 --> 00:11:42,260
risk right at the point of access. We've covered a lot of ground. The tech, the

254
00:11:42,260 --> 00:11:42,960
security, the

255
00:11:42,960 --> 00:11:46,790
applications. Something else that stood out for the material was the platform's

256
00:11:46,790 --> 00:11:47,440
flexibility and

257
00:11:47,440 --> 00:11:53,710
openness. They offer a community edition. They do. Yes. It's free for individuals,

258
00:11:53,710 --> 00:11:54,800
home lab users,

259
00:11:54,800 --> 00:11:59,130
nonprofits, testing. It shows a commitment to not just being a closed off

260
00:11:59,130 --> 00:12:00,240
enterprise product. They

261
00:12:00,240 --> 00:12:03,810
want people tinkering and building. And for developers who want to build on it.

262
00:12:03,810 --> 00:12:04,000
There's a

263
00:12:04,000 --> 00:12:08,140
developer API. If you want to integrate this streaming capability into your own

264
00:12:08,140 --> 00:12:08,560
custom

265
00:12:08,560 --> 00:12:13,130
applications, the tools are there. The source also mentioned specific tools for

266
00:12:13,130 --> 00:12:13,840
deployment,

267
00:12:13,840 --> 00:12:19,760
Ansible, and Terraform. Now, why should someone who isn't an IT pro care about

268
00:12:19,760 --> 00:12:20,880
those names? Well,

269
00:12:20,880 --> 00:12:26,800
those names signal that this platform is built for the real world of modern IT. Ansible

270
00:12:26,800 --> 00:12:27,600
and Terraform

271
00:12:27,600 --> 00:12:32,480
are the standard ways large organizations automate deploying and managing software,

272
00:12:32,480 --> 00:12:36,400
whether it's on their own servers or in the cloud. So it means Chasm can be rolled

273
00:12:36,400 --> 00:12:37,280
out quickly,

274
00:12:37,280 --> 00:12:42,400
reliably, automatically, at scale. Exactly. It's about infrastructure as code.

275
00:12:42,400 --> 00:12:44,000
Repeatable,

276
00:12:44,000 --> 00:12:49,590
consistent deployments, fewer errors, faster scaling. It shows it's designed to

277
00:12:49,590 --> 00:12:50,080
integrate

278
00:12:50,080 --> 00:12:55,090
smoothly into existing enterprise workflows, whether on-premise or multi-cloud. And

279
00:12:55,090 --> 00:12:55,280
they

280
00:12:55,280 --> 00:12:59,830
provide ready-made workspace images too, right? Like pre-built browsers and desktops.

281
00:12:59,830 --> 00:13:00,160
Yes,

282
00:13:00,160 --> 00:13:04,320
a whole library of them, plus extensive documentation. The goal seems to be making

283
00:13:04,320 --> 00:13:07,840
it accessible, whether you're just starting and need a secure browser quickly, or

284
00:13:07,840 --> 00:13:08,320
you're

285
00:13:08,320 --> 00:13:12,640
a large enterprise planning a complex deployment. That modularity and flexibility

286
00:13:12,640 --> 00:13:13,360
seems key to

287
00:13:13,360 --> 00:13:17,040
serving such different needs. Definitely. It has to be adaptable. Okay, so let's

288
00:13:17,040 --> 00:13:17,520
try and pull

289
00:13:17,520 --> 00:13:21,520
this all together. We've gone on quite a journey from just thinking about software

290
00:13:21,520 --> 00:13:22,000
on our own

291
00:13:22,000 --> 00:13:26,080
computers. What's the big picture here? At the end of the day, the real power of

292
00:13:26,080 --> 00:13:26,640
something like

293
00:13:26,640 --> 00:13:31,620
Chasm Workspaces is its ability to securely isolate and stream whatever digital

294
00:13:31,620 --> 00:13:32,800
tool you need,

295
00:13:32,800 --> 00:13:37,810
a browser, a specific app, even a full desktop, by making that environment

296
00:13:37,810 --> 00:13:38,800
containerized,

297
00:13:38,800 --> 00:13:42,400
disposable, and delivered through a zero trust stream. It makes your actual

298
00:13:42,400 --> 00:13:43,040
physical device,

299
00:13:43,040 --> 00:13:47,700
your laptop or phone, almost irrelevant from a security standpoint for that task.

300
00:13:47,700 --> 00:13:48,480
Exactly.

301
00:13:48,480 --> 00:13:53,230
The risk stays contained in the cloud in that ephemeral session, and then it just

302
00:13:53,230 --> 00:13:53,920
evaporates.

303
00:13:53,920 --> 00:13:57,690
It fundamentally shifts to where the security boundary lies. So here's a thought to

304
00:13:57,690 --> 00:13:58,080
leave you

305
00:13:58,080 --> 00:14:02,210
with. If your browser effectively becomes the universal application, and every

306
00:14:02,210 --> 00:14:03,040
session you run

307
00:14:03,040 --> 00:14:07,480
inside it can be completely disposable, secure, maybe even untraceable, what's the

308
00:14:07,480 --> 00:14:08,240
most valuable

309
00:14:08,240 --> 00:14:12,040
piece of tech you actually own? Is it the physical device in your hands, or is it

310
00:14:12,040 --> 00:14:12,800
just the key,

311
00:14:12,800 --> 00:14:16,960
the access method, that lets you into these secure cloud environments? Something to

312
00:14:16,960 --> 00:14:17,600
think about for

313
00:14:17,600 --> 00:14:23,130
sure. The value shifts from the endpoint to the secure access. Indeed. And once

314
00:14:23,130 --> 00:14:24,080
again, a big thank

315
00:14:24,080 --> 00:14:26,630
you to our supporters, Save Server, for helping us bring you this deep dive.

316
00:14:26,630 --> 00:14:27,520
Remember, they handle

317
00:14:27,520 --> 00:14:31,760
hosting for software like this and support digital transformation. Check them out

318
00:14:31,760 --> 00:14:32,320
at www.safeservr.ed.

319
00:14:32,320 --> 00:14:39,840
Join us next time as we explore another piece of technology shaping our future.