1
00:00:04,480 --> 00:00:06,560
Hello everyone, welcome back to 
the next episode of Streaming 

2
00:00:06,560 --> 00:00:07,720
Time Sports. 
My name is Chris Stone. 

3
00:00:07,720 --> 00:00:10,040
I'm the community lead, joined 
as always by our CEO, Nick 

4
00:00:10,040 --> 00:00:11,840
Beecham. 
Today we're also joined by a 

5
00:00:11,840 --> 00:00:15,720
guest, Olga Kornyenko, who is 
the CEO and Co founder of Easy 

6
00:00:15,720 --> 00:00:17,840
DRM. 
And just before we got on stage,

7
00:00:17,840 --> 00:00:19,840
I'm always trying to figure out 
how I'm going to open things up.

8
00:00:20,160 --> 00:00:22,680
And Olga, you mentioned you 
spent the weekend building some 

9
00:00:22,680 --> 00:00:25,960
IKEA furniture, which 
conveniently Nick is currently 

10
00:00:25,960 --> 00:00:28,440
in the home of IKEA. 
So Olga, I'm going to get to 

11
00:00:28,440 --> 00:00:30,560
your experience over the 
weekend, but Nick, I want to 

12
00:00:30,560 --> 00:00:35,320
know how much of your interior 
design furniture in your house 

13
00:00:35,320 --> 00:00:37,440
in Sweden has come from IKEA? 
Well. 

14
00:00:38,000 --> 00:00:41,320
Well, firstly, I'm also in the 
region of small land, which is 

15
00:00:41,320 --> 00:00:44,360
actually where IKEA was actually
found is not only the country 

16
00:00:44,360 --> 00:00:48,880
but also the region and not far 
away from where I live, I'd say.

17
00:00:48,920 --> 00:00:52,360
So we're renting at the moment 
and we worked out that pretty 

18
00:00:52,360 --> 00:00:58,360
much the entire house, from 
kitchens to bathrooms to a good 

19
00:00:58,360 --> 00:01:01,360
chunk of the furniture is 
basically all from IKEA. 

20
00:01:01,360 --> 00:01:03,120
So I think it's one of those 
things that when someone's 

21
00:01:03,120 --> 00:01:05,160
deciding they want to rent a 
place out, although renting's 

22
00:01:05,160 --> 00:01:08,280
not that popular or common over 
here in comparison to some other

23
00:01:08,280 --> 00:01:11,080
countries, that they've only 
just spent a few hours walking 

24
00:01:11,080 --> 00:01:15,080
around that maze of a store and 
didn't walk out until they 

25
00:01:15,080 --> 00:01:19,160
basically bought the the 
proverbial house full of full of

26
00:01:19,160 --> 00:01:21,920
stuff for it. 
So yeah, you can even see it's 

27
00:01:21,920 --> 00:01:23,560
very easy to find things when 
they break though, because you 

28
00:01:23,560 --> 00:01:25,960
just go on and look at them. 
So at least if you know where to

29
00:01:25,960 --> 00:01:28,960
look, it makes a big difference 
because there is some unique 

30
00:01:28,960 --> 00:01:31,840
things like it can be a little 
bit like Apple sometimes where 

31
00:01:31,840 --> 00:01:35,280
there's certain fittings and 
things that only really work 

32
00:01:35,280 --> 00:01:37,280
with IKEA stuff. 
So it's good to know where to 

33
00:01:37,280 --> 00:01:40,960
where to go. 
But it is still very much a a 

34
00:01:41,000 --> 00:01:44,240
destination here as well as it 
is pretty much anywhere in the 

35
00:01:44,240 --> 00:01:46,720
world these days. 
And and how did you do 

36
00:01:46,880 --> 00:01:48,920
constructing years old? 
Because I'll be honest, in my 

37
00:01:48,920 --> 00:01:51,600
household, I'm not the one that 
build things. 

38
00:01:51,600 --> 00:01:54,760
I do all the cooking, my wife 
does all the DIY, so she's the 

39
00:01:54,760 --> 00:01:56,280
handyman. 
She does everything. 

40
00:01:56,520 --> 00:01:59,280
I certainly couldn't do it even 
with their step by step 

41
00:01:59,280 --> 00:02:01,840
instructions. 
Were you able to build whatever 

42
00:02:01,960 --> 00:02:04,000
piece of equipment or furniture 
you're building? 

43
00:02:04,640 --> 00:02:09,759
So I grew up playing Legos and 
Erector sets and like I grew up 

44
00:02:09,759 --> 00:02:14,280
in Russia and former Soviet 
Union and I had the metal 

45
00:02:14,400 --> 00:02:17,800
erector sets that if you didn't 
quite properly connect them 

46
00:02:17,800 --> 00:02:20,520
together correctly, they pinched
your skin and all sorts of other

47
00:02:20,520 --> 00:02:22,680
things. 
Love it, love it. 

48
00:02:22,680 --> 00:02:26,280
For me, IKEA is like Legos but 
for adults. 

49
00:02:27,000 --> 00:02:30,640
You let me go and I will put 
like I do that for fun. 

50
00:02:30,640 --> 00:02:35,160
As set as it sounds for me, 
putting together a kitchen pole 

51
00:02:35,360 --> 00:02:38,640
closet system, off I go. 
Love it. 

52
00:02:39,480 --> 00:02:41,640
Well, my hand's been slapped a 
few times when I've tried to 

53
00:02:41,640 --> 00:02:43,960
when we have bought some stuff 
from IKEA and I'm like, can I 

54
00:02:44,600 --> 00:02:48,000
maybe I can give that a go And I
get quickly get told that go 

55
00:02:48,200 --> 00:02:50,640
back away from the IKEA 
furniture. 

56
00:02:50,720 --> 00:02:53,680
It's mine. 
So I've learned the hard way to 

57
00:02:53,680 --> 00:02:56,840
stay back in the and let it 
magically appear the next day. 

58
00:02:56,840 --> 00:02:58,840
Yeah. 
For me it's as I said, it's 

59
00:02:58,840 --> 00:03:01,360
absolute fun. 
Yeah, well, a little bit of lore

60
00:03:01,360 --> 00:03:04,320
about me not streaming related. 
I remember I was about 5 years 

61
00:03:04,320 --> 00:03:07,440
old, big basketball fan. 
My father's in the garage. 

62
00:03:07,440 --> 00:03:11,080
He built his own race car, and 
he asked me to come change the 

63
00:03:11,080 --> 00:03:13,960
oil while I was shooting hoops. 
And I remember I accidentally 

64
00:03:13,960 --> 00:03:15,160
dropped the wrench in the used 
oil. 

65
00:03:15,160 --> 00:03:17,280
And then my dad was like, just 
go back to shooting hoops, like,

66
00:03:17,280 --> 00:03:19,320
you're never back aloud. 
And my dad swears this never 

67
00:03:19,320 --> 00:03:21,160
happens. 
But I'm like Dad, it's a memory 

68
00:03:21,520 --> 00:03:24,400
I've remembered 30 years onward.
So basically I blame my lack of 

69
00:03:24,400 --> 00:03:27,560
engineering skills on the fact 
that as a 5 year old I dropped 

70
00:03:27,560 --> 00:03:30,320
the wrench and my dad was just 
like we've like even though he's

71
00:03:30,320 --> 00:03:32,160
a mechanical engineer can fix 
anything. 

72
00:03:32,440 --> 00:03:34,240
I possess none of those skills. 
I. 

73
00:03:34,760 --> 00:03:38,520
Said it's never too late. 
You can start with IKEA and see 

74
00:03:38,520 --> 00:03:41,000
where that takes you. 
We can, we can. 

75
00:03:41,000 --> 00:03:43,240
Well, Speaking of building 
things, we're going to talk a 

76
00:03:43,240 --> 00:03:46,160
little bit around maybe one of 
the most important bits when it 

77
00:03:46,160 --> 00:03:48,640
comes to construction, 
constructing your streaming 

78
00:03:48,640 --> 00:03:50,000
platform, your streaming 
service. 

79
00:03:50,280 --> 00:03:53,680
In one of the areas this came up
on our pre conversation is it 

80
00:03:53,680 --> 00:03:56,400
recently feels like content 
protection is a larger part of 

81
00:03:56,400 --> 00:03:59,600
the conversation than it has 
been in the past, partly because

82
00:03:59,600 --> 00:04:02,760
of how expensive rights are and 
maximising, you know, your 

83
00:04:02,760 --> 00:04:04,920
revenue streams from them. 
Or we look at things on the 

84
00:04:04,920 --> 00:04:08,400
other side, like the falling out
between the zone and Laguna in 

85
00:04:08,400 --> 00:04:10,520
France. 
One of the supported, one of the

86
00:04:10,520 --> 00:04:13,520
reasons was a piracy is so 
rampant in the in the 

87
00:04:13,520 --> 00:04:15,480
marketplace that the zone 
couldn't drive enough 

88
00:04:15,480 --> 00:04:17,720
subscriptions. 
And it just seems anecdotally, 

89
00:04:17,720 --> 00:04:20,079
the more and more I go on the 
LinkedIn, the more I'm hearing 

90
00:04:20,360 --> 00:04:23,480
about content security being a 
major point of emphasis for 

91
00:04:23,480 --> 00:04:25,840
people in the space. 
And that's one of the things 

92
00:04:25,840 --> 00:04:27,040
that we're going to talk about 
today. 

93
00:04:27,040 --> 00:04:29,640
And you know, as we're recording
this, there's the breaking news 

94
00:04:29,640 --> 00:04:31,840
that, you know, UFC is now 
signed. 

95
00:04:31,880 --> 00:04:37,320
AI believe it's a $7.7 billion 
deal with CBS and Paramount 

96
00:04:37,320 --> 00:04:39,120
Plus. 
So I'm sure Paramount Plus 

97
00:04:39,120 --> 00:04:41,760
taking on those sets of rights 
will very much be looking at how

98
00:04:41,760 --> 00:04:43,880
they protect those. 
Because as we know, combat 

99
00:04:43,880 --> 00:04:48,000
sports has always been a big 
victim of piracy, given the fact

100
00:04:48,000 --> 00:04:50,720
that some fights could be less 
than a minute long. 

101
00:04:50,720 --> 00:04:53,280
And you better be pretty good 
about protecting your content. 

102
00:04:53,520 --> 00:04:56,680
So it just needs to be a content
or a topic that's continue to 

103
00:04:56,680 --> 00:04:59,040
come up more and more. 
So Olga, we're we're hopefully 

104
00:04:59,040 --> 00:05:02,040
going to learn more about this 
space and sort of where it needs

105
00:05:02,040 --> 00:05:05,440
to fit within the streaming. 
Your build, your setup is also 

106
00:05:05,480 --> 00:05:08,120
how do you maximise the revenue 
from protecting your content? 

107
00:05:08,120 --> 00:05:10,160
So that's really what we're 
going to talk about today and 

108
00:05:10,160 --> 00:05:12,720
hopefully gain some more 
insights from you on this 

109
00:05:12,720 --> 00:05:14,000
particular topic. 
And Nick, I don't know if 

110
00:05:14,000 --> 00:05:16,040
there's anything else you want 
to frame this or if I've gone on

111
00:05:16,040 --> 00:05:18,840
the long enough soliloquy before
we go and jump into it. 

112
00:05:19,520 --> 00:05:20,400
Yeah. 
Look, I think you've covered it 

113
00:05:20,400 --> 00:05:21,680
pretty well. 
I think there's a load of 

114
00:05:21,680 --> 00:05:25,360
aspects to this topic that we've
not had a chance to to cover. 

115
00:05:25,360 --> 00:05:29,280
And particularly as you've seen 
sports properties and 

116
00:05:29,280 --> 00:05:32,040
broadcasters looking at more 
ways of distributing content 

117
00:05:32,040 --> 00:05:35,200
rather than just single, single 
channel approaches. 

118
00:05:35,200 --> 00:05:37,760
These days, it's even more 
important than ever to know 

119
00:05:37,800 --> 00:05:40,280
where and how your contents 
being accessed and distributed 

120
00:05:40,600 --> 00:05:42,160
and protected. 
Otherwise, you're probably 

121
00:05:42,160 --> 00:05:47,040
leaving a lot of a lot of 
opportunity, a lot of revenue on

122
00:05:47,040 --> 00:05:51,000
the table and having a very 
leaky ecosystem that is not 

123
00:05:51,000 --> 00:05:55,800
going to when we see profits and
and profitability of streaming 

124
00:05:55,800 --> 00:06:00,200
being such a key part of 
everyone's challenge in a, in 

125
00:06:00,200 --> 00:06:03,400
this space right now, there's 
one way you can, one thing you 

126
00:06:03,400 --> 00:06:06,200
can really focus on the can help
that tangibly and that's what 

127
00:06:06,200 --> 00:06:07,920
hopefully we're going to get a 
little bit more about today. 

128
00:06:08,080 --> 00:06:12,160
Well, we always look at security
as a strategy. 

129
00:06:12,320 --> 00:06:16,160
It can be a, oh, you know, let 
me slap this on at the end kind 

130
00:06:16,160 --> 00:06:18,920
of a conversation though. 
The way we build our system. 

131
00:06:18,920 --> 00:06:20,520
If you've really had to do that,
you can. 

132
00:06:20,840 --> 00:06:23,560
But in the grand scheme of 
things, your approach to 

133
00:06:23,560 --> 00:06:28,960
security has to be a strategy, 
ideally glass to glass, but that

134
00:06:28,960 --> 00:06:34,560
doesn't mean that the moment you
decide to just do security, you 

135
00:06:34,560 --> 00:06:38,360
have to do everything. 
Basically, we as EZDRM started 

136
00:06:38,640 --> 00:06:41,120
over 20 years ago doing 
specifically DRM. 

137
00:06:41,880 --> 00:06:45,520
When we first launched, we 
decided to take the approach of 

138
00:06:45,520 --> 00:06:52,280
let's do DRM in the easiest way 
to handle it, where we have AAPI

139
00:06:52,360 --> 00:06:56,400
for encryption, encrypting 
content and an API for playback.

140
00:06:56,400 --> 00:06:58,320
And we leave everything else 
behind the scenes. 

141
00:06:58,720 --> 00:07:01,160
And we've been doing it 
successfully for, as I said, 

142
00:07:01,160 --> 00:07:04,240
almost 20 years. 
And that's where usually people 

143
00:07:04,240 --> 00:07:06,840
start. 
I kind of equate DRM to the lock

144
00:07:06,840 --> 00:07:09,080
on the front door. 
You don't want to put the 

145
00:07:09,080 --> 00:07:14,040
cheapest lock on the front door.
You don't want to go by the 

146
00:07:14,040 --> 00:07:16,360
price because at the end of the 
day, the cheapest lock on the 

147
00:07:16,360 --> 00:07:19,120
front door of your own house is 
probably not the greatest idea 

148
00:07:19,120 --> 00:07:21,680
in the world. 
But the lock on the front door, 

149
00:07:21,680 --> 00:07:25,120
if we start take it to the 
security of, you know, our 

150
00:07:25,120 --> 00:07:28,120
homes, kind of a perspective, 
that's not the only thing. 

151
00:07:28,120 --> 00:07:32,240
We need a camera that looks to 
see who's coming and going and 

152
00:07:32,240 --> 00:07:35,040
various other parts of it and so
on and so forth. 

153
00:07:36,000 --> 00:07:39,640
So recently we've been looking 
at various other aspects of 

154
00:07:39,640 --> 00:07:42,640
security as well, adding on to 
the DRM bits. 

155
00:07:43,120 --> 00:07:47,240
But yes, there is a lot of it. 
And you can just pick a point 

156
00:07:47,400 --> 00:07:52,720
and start there and grow on 
slowly but carefully and 

157
00:07:52,720 --> 00:07:56,320
without, you know, rushing into 
a crazy expensive solution. 

158
00:07:56,600 --> 00:08:01,080
Because at the end of the day, 
our experience is that a lot of 

159
00:08:01,080 --> 00:08:06,440
people, like people understand 
that there is piracy, but 

160
00:08:06,760 --> 00:08:09,880
sometimes it's kind of hard to 
put a finger on how much it is, 

161
00:08:10,480 --> 00:08:14,120
what percentage it is. 
And also sometimes people look 

162
00:08:14,120 --> 00:08:16,920
at security just as an expense, 
which is something else that I 

163
00:08:16,920 --> 00:08:19,880
think the mind is shifting and 
people are seeing that their 

164
00:08:19,880 --> 00:08:23,080
content is popping up on all 
this other in other places. 

165
00:08:23,080 --> 00:08:28,800
I mean, piracy sites and all 
these other sites where the 

166
00:08:28,800 --> 00:08:32,679
pirates don't really need to 
worry about hosting content and 

167
00:08:32,679 --> 00:08:35,480
coding content, packaging 
content, getting the rights. 

168
00:08:35,480 --> 00:08:40,360
They just take it. 
And DRM itself and by itself 

169
00:08:40,360 --> 00:08:45,200
cannot, cannot withstand the 
onslaught of pirates. 

170
00:08:45,200 --> 00:08:48,000
And now I'm guessing AI helping 
hack into all sorts of things 

171
00:08:48,000 --> 00:08:51,440
and whatnot. 
So additional other things are 

172
00:08:51,440 --> 00:08:54,760
coming into play, and we've seen
contracts ask for more than just

173
00:08:55,000 --> 00:08:57,200
DRM. 
I will say I love the analogy 

174
00:08:57,200 --> 00:08:59,720
and maybe I've just not paid no 
one's ever, at least I've not 

175
00:08:59,720 --> 00:09:01,040
personally heard the house 
analogy. 

176
00:09:01,040 --> 00:09:03,480
And to your point, like there's 
multiple ways, you know, we hear

177
00:09:03,480 --> 00:09:05,560
people talking about all these 
different things, you know, 

178
00:09:06,440 --> 00:09:08,800
water marking, password, all 
these different things. 

179
00:09:08,800 --> 00:09:11,400
I love that analogy there. 
Maybe specifically, though, 

180
00:09:11,400 --> 00:09:15,640
where does the DRM sit within 
that space, in terms of where it

181
00:09:15,640 --> 00:09:19,760
sits within that overall process
or that overall protection that 

182
00:09:19,760 --> 00:09:21,280
you're going to build around 
your property? 

183
00:09:21,280 --> 00:09:26,240
So DRM is like your, if we're 
going to stick to the house, 

184
00:09:26,920 --> 00:09:30,480
it's the lock on the front door 
or in your regular, you know, we

185
00:09:30,480 --> 00:09:33,400
can all, we've all logged into 
bank accounts or whatever. 

186
00:09:33,600 --> 00:09:39,360
It's your username and password.
And based off of that, you know 

187
00:09:39,360 --> 00:09:44,000
that DRM in the grand scheme of 
things, DRM is a technology that

188
00:09:44,000 --> 00:09:45,720
says how you can use the 
content. 

189
00:09:46,040 --> 00:09:50,080
Can you play it? 
For how long can you cast it? 

190
00:09:50,400 --> 00:09:54,160
Can you like, can you have a 
like if I'm watching it on my 

191
00:09:54,160 --> 00:09:56,520
computer, can I have a monitor 
attached to it? 

192
00:09:56,520 --> 00:10:00,440
And so on and so forth. 
And DRM in and of itself 

193
00:10:00,440 --> 00:10:03,600
controls just that. 
The encryption that happens 

194
00:10:03,760 --> 00:10:07,760
you're in the DRM process is a 
vessel, if you will, to get the 

195
00:10:07,760 --> 00:10:14,080
right sound to the content. 
Usually in the workflow it 

196
00:10:14,080 --> 00:10:16,680
happens around encoding, 
packaging. 

197
00:10:17,280 --> 00:10:20,560
That's the first part where 
content is prepared and then the

198
00:10:20,560 --> 00:10:23,760
second part of it, like we've 
all probably dealt with, when 

199
00:10:23,760 --> 00:10:28,600
you press play as an end user, a
licence is delivered to the end 

200
00:10:28,600 --> 00:10:31,280
user and that is the second 
piece of it where you get to 

201
00:10:31,280 --> 00:10:35,160
view the licence. 
There's also a common 

202
00:10:35,160 --> 00:10:38,200
misconception when people say my
content is decrypted, the 

203
00:10:38,200 --> 00:10:39,880
content is actually never 
decrypted. 

204
00:10:40,200 --> 00:10:43,040
It is unlocked. 
Going back to my front door 

205
00:10:43,040 --> 00:10:46,760
example, when you walk into a 
house or hotel room, you open 

206
00:10:46,760 --> 00:10:49,480
the door with a key or key card.
You never physically RIP the 

207
00:10:49,480 --> 00:10:52,440
lock off the door. 
Kind of sort of the same logic 

208
00:10:52,440 --> 00:10:56,400
with DRM, You know that you have
access to go into this specific 

209
00:10:56,400 --> 00:10:59,920
spaces, but you, you know, don't
take the lock off the door. 

210
00:11:01,080 --> 00:11:04,760
And as a company we're also 
working on other things to make 

211
00:11:04,760 --> 00:11:09,400
sure that hacking into DRM, 
harvesting keys and all this 

212
00:11:09,400 --> 00:11:12,320
other stuff is becoming more and
more difficult. 

213
00:11:13,040 --> 00:11:17,240
But in the flow of the process 
it usually on the encoding side 

214
00:11:17,400 --> 00:11:20,000
and pieces on the playback side 
because it is a two-part 

215
00:11:20,000 --> 00:11:23,360
process. 
So Olga, when you describe that 

216
00:11:23,360 --> 00:11:27,600
it makes complete sense or it's 
important and it's necessity. 

217
00:11:27,920 --> 00:11:30,440
So why is it that not everyone 
uses a what? 

218
00:11:30,440 --> 00:11:33,160
What is the benefit of having 
DRM versus not? 

219
00:11:33,240 --> 00:11:37,960
You know, I think part of it 
might be some more of an older 

220
00:11:37,960 --> 00:11:43,880
thinking of it's an expense I've
had, I've also had people 

221
00:11:43,880 --> 00:11:47,960
contact us and say, hey, we're 
trying to set this up, but we've

222
00:11:47,960 --> 00:11:50,480
been trying to get this set up 
for a couple months now and it 

223
00:11:50,480 --> 00:11:52,320
doesn't seem to work with a 
different vendor. 

224
00:11:54,320 --> 00:11:57,920
We built our system in a way 
that we have a very 

225
00:11:57,920 --> 00:12:04,040
straightforward process and then
we partner with everybody and we

226
00:12:04,040 --> 00:12:06,080
don't try to do everything 
ourselves. 

227
00:12:06,080 --> 00:12:09,120
We have encoding packaging 
partners, we have player 

228
00:12:09,120 --> 00:12:13,840
partners and we make sure that 
we have integrations already pre

229
00:12:13,840 --> 00:12:15,840
done with them in order to get 
going. 

230
00:12:16,480 --> 00:12:21,480
We have a very transparent price
and we want people to understand

231
00:12:23,360 --> 00:12:26,240
what is happening, how it's 
happening, what the parts are 

232
00:12:26,240 --> 00:12:27,640
that are involved in the 
process. 

233
00:12:28,000 --> 00:12:32,600
And I have seen cases where 
that's not the situation. 

234
00:12:33,160 --> 00:12:36,680
I've had people be like, oh, 
this is how it works. 

235
00:12:36,680 --> 00:12:40,280
We didn't understand because 
there was no proper 

236
00:12:40,280 --> 00:12:44,120
documentation or whatever, or 
the price was so high we just 

237
00:12:44,480 --> 00:12:47,640
couldn't, or whatever the 
situation may be. 

238
00:12:48,160 --> 00:12:50,440
And sometimes it's just another 
thing to think about and you 

239
00:12:50,440 --> 00:12:52,640
just don't want to and you think
you need to build it. 

240
00:12:52,640 --> 00:12:56,360
So, you know, conversations on 
build versus buy come into play 

241
00:12:56,360 --> 00:12:59,120
there as well. 
So just take that question a bit

242
00:12:59,120 --> 00:13:01,280
of a sort of a step further. 
Obviously, the, the typical 

243
00:13:01,280 --> 00:13:03,720
workflow, you've got the 
ingestion, the encoding, then 

244
00:13:03,720 --> 00:13:05,560
the packaging and encryption 
going on. 

245
00:13:05,560 --> 00:13:09,800
Then then, you know, things get 
sent to the, the, the storage 

246
00:13:09,840 --> 00:13:11,920
out there where, wherever it's 
stored and then it comes back 

247
00:13:11,920 --> 00:13:14,200
and there's, there's an 
acceptance of access to the 

248
00:13:14,200 --> 00:13:16,680
platform. 
That's kind of how how from what

249
00:13:16,680 --> 00:13:20,200
I understand the process and 
flow to work, like just what 

250
00:13:20,520 --> 00:13:23,760
what happens if they don't have 
ADRM there? 

251
00:13:23,760 --> 00:13:27,200
What what happens instead is 
that basic just the encryption 

252
00:13:27,200 --> 00:13:31,120
is is non next to non existent 
and that's why it's it's a 

253
00:13:31,120 --> 00:13:34,040
problem from a security 
perspective or how does that 

254
00:13:34,040 --> 00:13:36,760
happen if someone's not using it
currently? 

255
00:13:36,800 --> 00:13:39,520
Well, there's no DRM that the 
content is in the clear. 

256
00:13:39,880 --> 00:13:42,560
What it that's what it's called 
and it's not encrypted and not 

257
00:13:42,560 --> 00:13:46,120
protected. 
I've had people say, well, I had

258
00:13:46,120 --> 00:13:49,000
a very long conversation with 
somebody doing fast channels who

259
00:13:49,000 --> 00:13:52,680
told me they don't need to do 
DRM on fast channels because 

260
00:13:52,680 --> 00:13:56,120
it's ad supported. 
OK, you, but you're still 

261
00:13:56,120 --> 00:13:59,280
licencing this content and 
you're still playing this 

262
00:13:59,280 --> 00:14:01,880
content. 
So what's to stop, you know, a 

263
00:14:01,880 --> 00:14:05,080
completely different site from 
just taking it from you and 

264
00:14:05,080 --> 00:14:07,600
running their own ads or doing 
something else. 

265
00:14:07,880 --> 00:14:11,400
But realistically, I mean, 
people try to do tokenization, 

266
00:14:11,400 --> 00:14:16,800
people try to do your URL 
obfuscation and various other 

267
00:14:16,800 --> 00:14:19,640
things, but at the end of the 
day, the content itself is in 

268
00:14:19,640 --> 00:14:25,680
the clear and absolutely nothing
stops me from recording, just 

269
00:14:25,880 --> 00:14:29,880
screen grabbing the content. 
At the end of the day, there is 

270
00:14:29,880 --> 00:14:33,040
no technology in the world that 
would prevent me from putting a 

271
00:14:33,040 --> 00:14:37,240
phone in front of or a very good
camera in front of my TV and 

272
00:14:37,360 --> 00:14:40,320
recording it that way. 
It's nothing that stops you 

273
00:14:40,320 --> 00:14:43,000
right now. 
Watermarking can help you track 

274
00:14:43,000 --> 00:14:47,840
it down afterwards, but I think 
it all depends on what the 

275
00:14:48,560 --> 00:14:51,640
company is trying to achieve. 
But if there's no DRM, it's 

276
00:14:51,760 --> 00:14:54,400
going to be the same as watching
this podcast after we're done. 

277
00:14:54,800 --> 00:14:55,920
It's just going to be in the 
clear. 

278
00:14:56,120 --> 00:14:58,560
Well, I think that's one of the 
the challenges when we talk 

279
00:14:58,560 --> 00:15:01,640
about content security is 
there's some people out there 

280
00:15:01,640 --> 00:15:07,720
that rightly or wrongly will go 
with wrongly say it's a badge of

281
00:15:07,720 --> 00:15:09,520
honour. 
If someone wants to pirate my 

282
00:15:09,520 --> 00:15:13,160
content, you know, that they can
understand why an NFL or Premier

283
00:15:13,160 --> 00:15:14,720
League would want to protect 
their content. 

284
00:15:14,920 --> 00:15:16,480
But there's some people out 
there that are like, hey, I 

285
00:15:16,480 --> 00:15:20,200
would love for people to even 
know we exist and would love for

286
00:15:20,200 --> 00:15:22,200
them to. 
If someone pirated our content, 

287
00:15:22,200 --> 00:15:25,240
that means we finally made it. 
But you know, you've sort of 

288
00:15:25,240 --> 00:15:28,200
explained a little bit, but like
in terms of the mentality of 

289
00:15:28,200 --> 00:15:30,360
changing people to understand 
that this isn't something that 

290
00:15:30,360 --> 00:15:34,240
is just a problem for the big, 
the big whales in the ocean. 

291
00:15:34,240 --> 00:15:36,560
It's also something that goes 
down to the lower ends of the 

292
00:15:36,560 --> 00:15:40,640
ecosystem, sort of where there's
misconceptions about that idea 

293
00:15:40,640 --> 00:15:42,960
that just because I don't sit at
a certain level that I don't 

294
00:15:42,960 --> 00:15:45,120
need to be focusing on. 
This is a problem for me. 

295
00:15:45,200 --> 00:15:49,320
From my perspective, you are 
still paying to produce this 

296
00:15:49,320 --> 00:15:52,000
content. 
You have the infrastructure to, 

297
00:15:52,840 --> 00:15:56,880
you know, package it, encoded 
stream it. 

298
00:15:56,880 --> 00:16:00,160
You're paying for bandwidth, 
you're paying for, you know, 

299
00:16:00,400 --> 00:16:02,160
maybe you're doing your own 
player development, you're 

300
00:16:02,160 --> 00:16:05,480
playing paying everybody to get 
this content out there. 

301
00:16:05,680 --> 00:16:10,720
And sure, absolutely, I know 
that for a while there were 

302
00:16:10,720 --> 00:16:16,360
companies that were using piracy
as a a marketing tool, but that 

303
00:16:16,360 --> 00:16:19,240
only goes so far. 
If all of your content is stolen

304
00:16:19,240 --> 00:16:21,680
and you're not making money off 
of it or you're not getting any 

305
00:16:21,680 --> 00:16:25,000
return on investment. 
As my Co founder says, we're all

306
00:16:25,000 --> 00:16:29,360
a.com, nota.org, right? 
And in order for us to continue 

307
00:16:29,360 --> 00:16:32,440
producing content, we need to be
making money on it. 

308
00:16:32,960 --> 00:16:38,440
So I think and Chris to your 
point, I think a lot of the 

309
00:16:39,280 --> 00:16:43,320
conversation like that goes to, 
I think it's very expensive to 

310
00:16:43,560 --> 00:16:46,200
GRM protect for somebody who is 
small. 

311
00:16:46,760 --> 00:16:50,480
And I then for the to those 
people, I'd say do some research

312
00:16:50,480 --> 00:16:54,640
because prices for DRM are not 
what they used to be 10/15/20 

313
00:16:54,640 --> 00:16:57,480
years ago. 
I'm not saying it's a race to 

314
00:16:57,480 --> 00:17:01,000
the bottom, but the prices are 
very reasonable. 

315
00:17:01,000 --> 00:17:04,520
And we and just like other 
companies or a good amount of 

316
00:17:04,520 --> 00:17:08,800
companies do it based on usage. 
So if this month you had 1000 

317
00:17:08,800 --> 00:17:12,880
views and next month you had 
10,000 views and then 100,000 

318
00:17:12,880 --> 00:17:17,240
and I'm back to 1000, you pay 
per usage and that becomes 

319
00:17:17,240 --> 00:17:20,560
manageable and makes people feel
uncomfortable. 

320
00:17:20,800 --> 00:17:24,079
And you mentioned you guys have 
been around for over 20 years 

321
00:17:24,079 --> 00:17:26,280
now. 
You know, in terms of the 

322
00:17:26,280 --> 00:17:30,840
evolution, we are transitioning 
to a more streaming heavy world.

323
00:17:31,200 --> 00:17:34,480
How have you seen the 
development of content security 

324
00:17:34,480 --> 00:17:38,080
going from a world that was 
largely linear broadcast to now 

325
00:17:38,360 --> 00:17:41,840
there's more streaming, is that,
you know, compared to linear, is

326
00:17:41,840 --> 00:17:44,400
it more complicated, less 
complicated, or just completely 

327
00:17:44,400 --> 00:17:46,360
set of different problems? 
You know, how have you seen just

328
00:17:46,360 --> 00:17:49,720
the evolution of content 
security over that period of 

329
00:17:49,720 --> 00:17:52,600
time, particularly as we're 
transitioning basically from 1 

330
00:17:52,600 --> 00:17:55,240
medium to another? 
It's definitely a transition. 

331
00:17:55,320 --> 00:17:59,480
And for on the content security 
side, I mean, if we go back 20 

332
00:17:59,480 --> 00:18:03,360
years, we have, we had 
technologies 20 years ago that 

333
00:18:03,360 --> 00:18:07,160
don't exist anymore. 
A lot of standardisation came 

334
00:18:07,160 --> 00:18:11,480
into play also, which makes it 
so much easier for content 

335
00:18:11,480 --> 00:18:15,080
rights holders to actually DRM 
protect content and just secure 

336
00:18:15,080 --> 00:18:19,960
content in general. 
The more and more we get into 

337
00:18:19,960 --> 00:18:21,880
the world of streaming, I don't 
know if there's going to be a 

338
00:18:21,880 --> 00:18:25,120
point where we're all going to 
say there's just way too much 

339
00:18:25,120 --> 00:18:27,360
content out there and I can't 
watch it. 

340
00:18:27,360 --> 00:18:31,920
And IRC drops, I don't know. 
We can all hope because they're 

341
00:18:31,920 --> 00:18:34,520
just way too much stuff, but I 
seriously doubt it. 

342
00:18:34,840 --> 00:18:40,600
And I think just like us, a lot 
more of the security vendors are

343
00:18:40,600 --> 00:18:43,480
talking more and more about what
content protection is. 

344
00:18:43,680 --> 00:18:48,640
Studios are mandating it. 
And as we shift into the world 

345
00:18:48,640 --> 00:18:54,400
of streaming, not only is it 
important to have secure 

346
00:18:54,400 --> 00:18:57,880
content, but also know where 
your content is coming from. 

347
00:18:58,960 --> 00:19:03,280
Because knowing that the content
you're watching is truly Disney 

348
00:19:03,600 --> 00:19:08,720
or truly NFL, and the scores 
you're watching and potentially 

349
00:19:08,720 --> 00:19:12,560
betting on have not been changed
and nothing's been modified with

350
00:19:12,560 --> 00:19:14,920
the stream becomes more and more
important. 

351
00:19:14,920 --> 00:19:19,960
Because then there's less 
concern about manipulating, I 

352
00:19:19,960 --> 00:19:22,600
don't know, the game 
manipulating content and so on 

353
00:19:22,600 --> 00:19:24,320
and so forth. 
Oh God, I was just wondering the

354
00:19:25,880 --> 00:19:28,000
when you've talked, you 
mentioned earlier about the fact

355
00:19:28,000 --> 00:19:32,120
that there's even when AD when a
request is made, when someone's 

356
00:19:32,120 --> 00:19:34,760
trying to log in or access it. 
There's even things like the 

357
00:19:34,880 --> 00:19:39,480
screen, like recording of the, 
the of the experience. 

358
00:19:39,480 --> 00:19:42,320
There is also the casting on the
screen that you help 

359
00:19:42,320 --> 00:19:44,480
authenticate. 
Can you just give us a, a 

360
00:19:44,480 --> 00:19:47,880
snapshot of what are some of 
those things that might be a 

361
00:19:47,880 --> 00:19:51,800
typical within the the ecosystem
there that might have to be 

362
00:19:51,800 --> 00:19:54,520
authenticated that some that 
your clients are using? 

363
00:19:54,640 --> 00:19:59,040
So in a world of DRM, most DRM 
technologies have a certain set 

364
00:19:59,040 --> 00:20:03,040
of rules, and those rules depend
on technology. 

365
00:20:03,200 --> 00:20:06,360
But in the grand scheme of 
things, it is whether or not the

366
00:20:06,360 --> 00:20:10,400
content can actually be played. 
If it is in the browser, it's 

367
00:20:10,400 --> 00:20:14,080
just one play and that's it. 
If it's on a mobile app, you can

368
00:20:14,080 --> 00:20:17,080
have content that can be played 
for a period of time. 

369
00:20:17,320 --> 00:20:20,960
So think your. 
I don't know, Netflix, Hulu, 

370
00:20:20,960 --> 00:20:23,680
pick your poison. 
You can buy a movie and watch it

371
00:20:23,680 --> 00:20:29,640
for 2448 hours, right? 
And then you, as the 

372
00:20:29,640 --> 00:20:33,480
technologies allow you to 
control things like can you 

373
00:20:33,480 --> 00:20:39,640
cast, can you prevent unsafe 
monitors on analogue connections

374
00:20:40,080 --> 00:20:44,160
and so on and so forth. 
Those are the most popular ones,

375
00:20:44,720 --> 00:20:49,880
but at least in the world of 
like movies and so on, those are

376
00:20:49,880 --> 00:20:52,320
also the kind of things that are
dictated by rights holders. 

377
00:20:53,000 --> 00:20:56,800
So when people go out and sign a
contract for the rights for 

378
00:20:57,760 --> 00:21:01,800
streaming a movie, they say you 
can do this, you can do this, 

379
00:21:01,800 --> 00:21:03,560
you can do this, but you cannot 
do that. 

380
00:21:04,040 --> 00:21:07,840
They can specify that for a 
specific, like for SD content 

381
00:21:07,840 --> 00:21:10,760
you can do this, but for HD 
content you can't. 

382
00:21:11,000 --> 00:21:15,040
You have to specify different 
encryption keys for different 

383
00:21:15,040 --> 00:21:18,600
types of resolutions and so on 
and so forth. 

384
00:21:19,240 --> 00:21:22,640
And there is. 
And if people are not sure what 

385
00:21:22,640 --> 00:21:26,320
they can do, they can always ask
their preferred vendor. 

386
00:21:26,600 --> 00:21:30,480
I would say us, but I don't want
to be presumptuous, but they can

387
00:21:30,480 --> 00:21:33,320
always ask us. 
We're very much open to saying, 

388
00:21:33,320 --> 00:21:35,480
hey, here's what you, what are 
you trying to achieve? 

389
00:21:36,080 --> 00:21:39,120
And based on what you're trying 
to achieve, you should do this. 

390
00:21:39,120 --> 00:21:41,840
You can do this, and you might 
want to think about doing that, 

391
00:21:42,760 --> 00:21:45,600
but a lot of it is dictated by a
the way the technologies are 

392
00:21:45,600 --> 00:21:48,200
built. 
And it's play ready from 

393
00:21:48,200 --> 00:21:53,520
Microsoft wide vying from Google
and Fairplay from Apple and also

394
00:21:53,520 --> 00:21:56,760
what the studios recommend or I 
don't know if in the sports 

395
00:21:56,760 --> 00:21:59,960
world, actually don't know if in
the sports world, if rights 

396
00:21:59,960 --> 00:22:03,120
holders control what you can and
cannot do to that grandeur 

397
00:22:03,120 --> 00:22:05,280
already. 
I think it's a it's case by case

398
00:22:05,280 --> 00:22:08,680
in a lot of instances on how how
big those contracts can be 

399
00:22:09,080 --> 00:22:11,920
depending on some of the 
companies you might talk about. 

400
00:22:11,920 --> 00:22:13,960
I think what's interesting 
hearing you talk about that Olga

401
00:22:13,960 --> 00:22:18,880
is that it sounds like therefore
that when you we hear the 

402
00:22:18,880 --> 00:22:22,840
discussion, have a discussion 
are right in sports about what 

403
00:22:22,840 --> 00:22:28,000
warrants requesting someone to 
pay a subscription for versus 

404
00:22:28,000 --> 00:22:30,880
just making things for free. 
One of the aspects of that can 

405
00:22:30,880 --> 00:22:34,760
be the quality of the content, 
whether it could be a multiview,

406
00:22:34,760 --> 00:22:37,240
whether it could be high 
definition or 4K, etcetera, 

407
00:22:37,840 --> 00:22:41,440
whether it could be casting to 
bigger screens and so forth. 

408
00:22:41,720 --> 00:22:45,920
Those layers I think are an 
interesting area where there are

409
00:22:45,920 --> 00:22:48,680
some major platforms doing that 
in sports. 

410
00:22:48,680 --> 00:22:52,040
I can think of a couple, but I 
think for the the for some 

411
00:22:52,040 --> 00:22:55,560
sports properties that maybe 
they worry about other features,

412
00:22:55,560 --> 00:22:58,160
maybe like access to different 
types of pieces of content, 

413
00:22:58,160 --> 00:23:01,280
which is, is I put an important 
part of the product mix. 

414
00:23:01,760 --> 00:23:05,200
But I don't think they often 
think about the those aspects, 

415
00:23:05,200 --> 00:23:07,840
the technological aspects to 
improve the actual user 

416
00:23:07,840 --> 00:23:11,920
experience and maximising the 
value of the of what they buying

417
00:23:12,320 --> 00:23:16,160
to buying is another way to add 
a perhaps another product layer 

418
00:23:16,600 --> 00:23:20,000
to it rather simply rather than 
I think I could imagine some 

419
00:23:20,000 --> 00:23:21,640
people might find that really 
difficult to get their heads 

420
00:23:21,640 --> 00:23:25,760
around if they were launching as
a product for a decent sized 

421
00:23:25,760 --> 00:23:28,840
audience. 
What is that key differentiator 

422
00:23:28,840 --> 00:23:31,680
they can offer in a more premium
solution to the base model? 

423
00:23:31,840 --> 00:23:34,880
Well, and also I think the other
part of it is, I mean, they're 

424
00:23:34,880 --> 00:23:38,160
in the world of mobile devices. 
How many phones are there, 

425
00:23:38,160 --> 00:23:41,680
right? 
Even if on the Apple side it's 

426
00:23:41,680 --> 00:23:45,560
probably easier, but still on 
the Android side, how many 

427
00:23:45,560 --> 00:23:49,240
variations of Android is out 
there? 

428
00:23:49,480 --> 00:23:53,720
So kind of keeping it more 
generalised and I going 

429
00:23:53,720 --> 00:23:56,880
completely off the deep end of, 
you know, I'm going to make it 

430
00:23:56,880 --> 00:23:59,960
this for this phone, this for 
this device, this for the like, 

431
00:23:59,960 --> 00:24:03,480
it becomes unruly. 
But having a certain basic set 

432
00:24:03,480 --> 00:24:08,320
of features can probably 
differentiate a service, 

433
00:24:08,320 --> 00:24:11,600
especially whether or not you 
can cast off your phone because 

434
00:24:11,600 --> 00:24:14,800
that all of a sudden creates 
more of a lean back watch the 

435
00:24:14,800 --> 00:24:18,560
game or a race or what have you 
on your TV at home with your 

436
00:24:18,560 --> 00:24:21,000
family. 
And it creates a more of a 

437
00:24:21,040 --> 00:24:25,120
different experience. 
But I But for that, This is why 

438
00:24:25,120 --> 00:24:28,680
you go to a security specialist.
We do this. 

439
00:24:28,680 --> 00:24:31,400
This is what we, you know, 
sleep, eat and breathe. 

440
00:24:31,400 --> 00:24:34,720
And we can make recommendations 
and tell you that this would 

441
00:24:34,720 --> 00:24:38,080
work or yeah, this might be a 
bit tricky. 

442
00:24:38,080 --> 00:24:40,240
Or because of the fact that 
you're trying to cast to 

443
00:24:40,240 --> 00:24:42,280
whatever, you know, set of 
televisions. 

444
00:24:42,560 --> 00:24:44,600
Not all of them support it. 
Yeah, the example that that 

445
00:24:44,600 --> 00:24:48,560
comes to mind, Chris, that I'm 
not sure how they approached it,

446
00:24:48,560 --> 00:24:53,560
but I remember when the NFL 
launched their mobile only like 

447
00:24:53,560 --> 00:24:56,360
plus offering. 
And one of the things that stuck

448
00:24:56,360 --> 00:24:58,040
to me as well as also bedding 
rights. 

449
00:24:58,040 --> 00:25:00,760
You see a lot of bedding 
companies that will buy certain 

450
00:25:00,760 --> 00:25:02,360
sets of rights right across the 
world. 

451
00:25:02,760 --> 00:25:05,800
Is that what how do they make 
sure that that stuff's not being

452
00:25:05,800 --> 00:25:07,720
used in other ways? 
Because otherwise it's just 

453
00:25:07,720 --> 00:25:11,640
opening up the floodgates for, 
you know, someone basically 

454
00:25:12,280 --> 00:25:15,280
buying a bedding, A bedding, 
accessing it free through 

455
00:25:15,280 --> 00:25:19,400
bedding platforms and then just 
casting it onto their their 

456
00:25:19,400 --> 00:25:20,680
devices. 
So I don't know. 

457
00:25:21,000 --> 00:25:22,520
It's just something that I 
thought that with the NFL 

458
00:25:22,520 --> 00:25:25,880
example, I had always had that 
curiosity that, well, can people

459
00:25:25,880 --> 00:25:30,000
just be be casting it to their 
biggest screen in the house? 

460
00:25:30,000 --> 00:25:32,760
And I don't know what they did 
in in to mitigate that, but I 

461
00:25:32,760 --> 00:25:34,680
would have expected they'd have 
to have considered that quite 

462
00:25:34,680 --> 00:25:37,000
heavily. 
Well some betting companies do 

463
00:25:37,000 --> 00:25:39,120
use DRM on all of their content 
as well. 

464
00:25:40,920 --> 00:25:43,080
Talking get again from 
experience from a customer of 

465
00:25:43,080 --> 00:25:46,000
ours. 
They do stream betting for 

466
00:25:46,120 --> 00:25:51,040
football and American football. 
Sorry, forgot about the audience

467
00:25:51,040 --> 00:25:54,000
for a second. 
And they do use DRM on 

468
00:25:54,000 --> 00:25:56,240
everything. 
So I couldn't tell you what 

469
00:25:56,240 --> 00:25:58,640
specific rules they're setting, 
if they're controlling the 

470
00:25:58,640 --> 00:26:00,960
casting or not. 
But that was definitely a 

471
00:26:00,960 --> 00:26:04,240
requirement from the NFL, that 
if you're betting on content, 

472
00:26:04,520 --> 00:26:07,560
you need to be able to control 
all of that well. 

473
00:26:07,560 --> 00:26:10,960
And also, if we're getting into 
betting and just in general, 

474
00:26:10,960 --> 00:26:15,200
watching content, knowing that 
the score is right and correct 

475
00:26:15,200 --> 00:26:19,080
and knowing that nobody's 
modifying, this is also becoming

476
00:26:19,080 --> 00:26:23,120
more and more of a conversation 
in the world that we sit in. 

477
00:26:23,600 --> 00:26:26,880
And to that end, there's a 
technology out there called, 

478
00:26:27,720 --> 00:26:29,720
well, not a technology. 
It's a set of standards called 

479
00:26:29,720 --> 00:26:33,640
C2 PA, which stands for 
Coalition for Content Provenance

480
00:26:33,640 --> 00:26:38,320
and Authenticity. 
And in the grand scheme of plain

481
00:26:38,320 --> 00:26:42,280
English things, that means 
knowing where your content comes

482
00:26:42,280 --> 00:26:45,600
from. 
Is it specifically from NFL or 

483
00:26:45,600 --> 00:26:50,560
is it from Joe Bob at, you know,
my NFL basement.com? 

484
00:26:51,000 --> 00:26:56,440
And also knowing that since the 
NFL published it, it has not 

485
00:26:56,440 --> 00:27:00,400
been modified. 
So C2 PA attempts to answer 

486
00:27:00,400 --> 00:27:03,680
those two questions. 
So then as a user, when you are 

487
00:27:03,680 --> 00:27:07,040
watching a game, if you're 
watching you're paying for a 

488
00:27:07,040 --> 00:27:10,720
game, especially if you're 
travelling, you know exactly 

489
00:27:10,720 --> 00:27:12,240
what you're getting, you know 
that it's correct. 

490
00:27:12,320 --> 00:27:15,920
I will say if, if the goal was 
to educate today, I'll, you 

491
00:27:15,920 --> 00:27:18,120
know, I'll put my hands up in 
the air if anyone's watching the

492
00:27:18,120 --> 00:27:21,160
video. 
I, I knew there are things like,

493
00:27:21,160 --> 00:27:23,800
you know, for example, I can go 
on my phone and I can on my 

494
00:27:23,800 --> 00:27:25,920
Chromecast. 
I can connect YouTube, can't 

495
00:27:25,920 --> 00:27:29,400
connect Apple TV to it. 
I didn't realise that was 

496
00:27:29,400 --> 00:27:31,640
specifically because of DRMS. 
So there we go. 

497
00:27:31,640 --> 00:27:33,760
I at least now know I can walk 
away. 

498
00:27:33,760 --> 00:27:36,920
The next time I try to cast 
something to my TV, I'll be like

499
00:27:37,040 --> 00:27:40,680
gosh darn you DRMS. 
So at least now I know what. 

500
00:27:40,680 --> 00:27:43,960
That is, don't blame them. 
We're just no, no, no, no, no. 

501
00:27:44,000 --> 00:27:45,440
We're just the messenger. 
Yeah, yeah. 

502
00:27:45,440 --> 00:27:48,560
Not easy DRM specifically, but 
just that is the set of 

503
00:27:48,560 --> 00:27:51,280
technologies. 
With which that's the decision, 

504
00:27:51,280 --> 00:27:53,320
Chris, That's the decision, 
yeah. 

505
00:27:53,320 --> 00:27:55,720
Yeah, that's the. 
Decision of who owns the rights.

506
00:27:56,240 --> 00:27:59,560
Yeah, like I said, I I'm not 
saying the person, the strategy 

507
00:27:59,560 --> 00:28:02,560
behind it, they all have their 
own strategies for which why 

508
00:28:02,560 --> 00:28:05,680
they've limited those things. 
But I've learned that it's the 

509
00:28:05,680 --> 00:28:10,240
DRM, just the tool that may 
limit or be the gatekeeper for 

510
00:28:10,240 --> 00:28:13,720
how you can access that content.
Is that correct if I phrase that

511
00:28:13,720 --> 00:28:15,640
correctly? 
Yeah, basically as part of the 

512
00:28:15,640 --> 00:28:18,560
rule set, one of them is allow 
casting, yes or no. 

513
00:28:19,240 --> 00:28:21,800
And if you don't allow casting, 
you don't allow casting. 

514
00:28:21,800 --> 00:28:24,240
And if the answer is yes, then 
go crazy. 

515
00:28:24,720 --> 00:28:28,360
The Olga, the this, the the idea
of that. 

516
00:28:28,480 --> 00:28:30,840
You're able to also see if 
anything's been altered. 

517
00:28:30,840 --> 00:28:32,760
I think it's a really 
interesting concept when you 

518
00:28:32,760 --> 00:28:35,760
talk about C2 PA, because 
obviously with AI coming as a 

519
00:28:35,800 --> 00:28:39,800
more and more hot topic and the 
pace of the ability to alter 

520
00:28:39,800 --> 00:28:43,720
content being so rampant these 
days, that could become a real 

521
00:28:43,720 --> 00:28:47,680
issue for live and non live. 
I think content in the sports 

522
00:28:47,680 --> 00:28:50,960
space you from from I can think 
of a bunch of, you know, 

523
00:28:51,000 --> 00:28:53,840
examples of that, but non live 
could definitely be a big 

524
00:28:53,840 --> 00:28:56,640
problem for content that's being
produced across different 

525
00:28:56,640 --> 00:28:58,560
channels distributed globally, 
etcetera. 

526
00:28:58,920 --> 00:29:03,040
And even if you think Chris on 
on the live perspective for 

527
00:29:03,640 --> 00:29:08,040
things like this might be 
getting a step ahead of myself. 

528
00:29:08,040 --> 00:29:10,800
But the, the technology that 
we've seen through a few 

529
00:29:10,800 --> 00:29:15,480
different companies that allows 
different ads so virtually on 

530
00:29:15,720 --> 00:29:20,120
overlaid on the, on the signage 
in the billboards, the football 

531
00:29:20,120 --> 00:29:22,320
matches and the like. 
Think about where it could get 

532
00:29:22,320 --> 00:29:25,120
to is that that could be 
tampered with. 

533
00:29:26,040 --> 00:29:29,280
So if you're, if you steal those
rights, then you could be 

534
00:29:29,520 --> 00:29:31,440
overlaying your own stuff over 
the top of it, which I don't 

535
00:29:31,520 --> 00:29:34,200
want to give any, any, any 
people any ideas. 

536
00:29:34,200 --> 00:29:37,280
But there's one way to back. 
Maybe I can maybe play some, 

537
00:29:37,280 --> 00:29:40,440
make some pretty big damage. 
Well, and that goes back to 

538
00:29:40,480 --> 00:29:44,320
whether or not the content is 
DRM protected and that goes back

539
00:29:44,320 --> 00:29:47,760
to whether or not CTPA is on 
your content. 

540
00:29:48,200 --> 00:29:51,280
You CTP is coming more and more 
into play. 

541
00:29:51,280 --> 00:29:54,960
You see it on LinkedIn when in 
the corner of a image, there's 

542
00:29:54,960 --> 00:29:59,400
like a little circle like thing 
that says CR. 

543
00:30:00,280 --> 00:30:02,720
And then basically it means that
this piece of content, 

544
00:30:02,720 --> 00:30:06,280
specifically a photo or video 
has credentials and you can 

545
00:30:06,280 --> 00:30:09,760
click on that and see who owns 
the rights who posted it. 

546
00:30:10,200 --> 00:30:12,680
Right now there's a lot of 
conversation about tagging 

547
00:30:12,680 --> 00:30:17,240
content that is AI generated, 
but we've also been working and 

548
00:30:17,240 --> 00:30:22,240
will be releasing and a product 
shortly that allows you to sign 

549
00:30:22,240 --> 00:30:25,080
your live content. 
Like if you are streaming a 

550
00:30:25,080 --> 00:30:31,960
game, you can sign it on the fly
and you can also sign VOD or if 

551
00:30:31,960 --> 00:30:35,760
it's just in time packaging, you
can sign all of your content and

552
00:30:35,760 --> 00:30:39,400
have it be out there. 
And then as you're watching this

553
00:30:39,400 --> 00:30:43,320
piece of content and something's
been modified, you will be able 

554
00:30:43,320 --> 00:30:47,960
to see on the like the play line
where the the way we're doing it

555
00:30:47,960 --> 00:30:50,760
is like if the play line is 
green or blue or whatever. 

556
00:30:50,760 --> 00:30:53,280
And again, you see the content 
kind of rolling through and all 

557
00:30:53,280 --> 00:30:57,440
of a sudden it turns to red and 
it says the the sections here 

558
00:30:57,440 --> 00:31:00,320
have been modified. 
Completely up to you if you want

559
00:31:00,320 --> 00:31:03,200
to trust them. 
And this way, you know that 

560
00:31:03,200 --> 00:31:05,480
somebody might have tampered 
with what is that you're 

561
00:31:05,480 --> 00:31:09,400
watching. 
We can do DRM with C2 PA. 

562
00:31:10,360 --> 00:31:12,680
We can do them separately. 
Depending on what you're trying 

563
00:31:12,680 --> 00:31:17,160
to achieve in the world of news 
or maybe re recaps or whatever, 

564
00:31:17,160 --> 00:31:20,840
he may not want to do DRM. 
But you definitely want to know 

565
00:31:20,840 --> 00:31:25,280
that if you're talking about 
scores or what have you, that 

566
00:31:25,280 --> 00:31:27,160
that has not been altered. 
It's. 

567
00:31:27,320 --> 00:31:28,920
Very interesting. 
I think to your point, Nick, I 

568
00:31:28,920 --> 00:31:31,680
mean, I think I saw something 
the other day where Amazon's 

569
00:31:31,680 --> 00:31:35,640
looking at investing in the AI 
of Netflix, where they're going 

570
00:31:35,640 --> 00:31:41,160
to allow people to basically 
alter original IP to create 

571
00:31:41,160 --> 00:31:44,280
their own content, which I think
is just mind boggling that 

572
00:31:44,280 --> 00:31:46,760
someone like Disney would allow 
Amazon to go do that. 

573
00:31:46,760 --> 00:31:50,000
But like, I, I, it does seem 
like that particular instance 

574
00:31:50,000 --> 00:31:53,080
you raised there, Nick, is only 
going to become potentially more

575
00:31:53,080 --> 00:31:56,800
prevalent as AI becomes more 
powerful from a generative 

576
00:31:57,080 --> 00:31:59,400
perspective and what it's 
already able to do some of the 

577
00:31:59,400 --> 00:32:02,560
deep fakes, you know, Oh gosh, 
that it, that's a can of worms 

578
00:32:02,560 --> 00:32:04,880
right there. 
Well, and, and from that 

579
00:32:04,880 --> 00:32:08,720
perspective, I can also see the 
provenance information be used 

580
00:32:08,720 --> 00:32:12,480
as AI. 
Don't know you cannot combine 

581
00:32:12,960 --> 00:32:20,240
NFL and I don't know NBA 
content, you cannot physically 

582
00:32:20,240 --> 00:32:24,840
combine those 22 properties for 
whatever legal reasons. 

583
00:32:25,200 --> 00:32:29,560
So if we know that this is NFL 
and this is NBA, then AI would 

584
00:32:29,560 --> 00:32:33,680
not be able to do that because 
whatever, that's what it's been 

585
00:32:33,680 --> 00:32:35,960
told. 
I'm using that as a rough 

586
00:32:35,960 --> 00:32:39,720
example, but I can see that that
provenance information could 

587
00:32:40,080 --> 00:32:43,920
further down the line be used to
control what AI can and cannot 

588
00:32:43,920 --> 00:32:47,240
do as well. 
So basically DRM kind of acts as

589
00:32:47,240 --> 00:32:50,960
like The Who can watch, but the 
CDPA is kind of where and if 

590
00:32:50,960 --> 00:32:56,000
it's authentic and and tracks 
its use, so to speak. 

591
00:32:56,040 --> 00:32:57,160
Is that how you would describe 
it? 

592
00:32:57,680 --> 00:32:59,720
I wouldn't call it tracks its 
use. 

593
00:33:00,160 --> 00:33:02,600
I would just say that you know 
what you're looking at. 

594
00:33:02,920 --> 00:33:07,520
I mean the most perfect case for
C2 PA is news and knowing that 

595
00:33:07,520 --> 00:33:11,320
the leader of a country said 
this but they didn't say that or

596
00:33:11,320 --> 00:33:14,640
you know whatever the events are
happening and being shown on TV,

597
00:33:14,640 --> 00:33:18,480
it's actually happening now and 
not footage from 7 years ago and

598
00:33:18,480 --> 00:33:20,520
another piece of the world and 
so on. 

599
00:33:21,800 --> 00:33:27,600
As far as tracking what you are 
doing, that comes into the 

600
00:33:27,600 --> 00:33:30,920
reason how we got to this 
podcast in the 1st place is the 

601
00:33:30,920 --> 00:33:34,200
technology that I won the pitch 
with that the pitch off and is 

602
00:33:34,520 --> 00:33:37,320
Pro Madrid. 
We are also working on a 

603
00:33:37,320 --> 00:33:40,400
solution announced it shortly 
called North Star. 

604
00:33:40,720 --> 00:33:42,720
Actually when I pitched it, we 
didn't have a name for it. 

605
00:33:43,040 --> 00:33:45,200
It is not, it does not have a 
name North Star. 

606
00:33:46,120 --> 00:33:51,120
And the idea behind that 
solution is that using the C2 PA

607
00:33:51,240 --> 00:33:56,840
signing algorithm, you can sign 
content at the edge or as the 

608
00:33:56,840 --> 00:33:59,280
content is moving through the 
CDN. 

609
00:33:59,280 --> 00:34:03,560
If you really wanted to go that 
deep, you can sign that content 

610
00:34:03,840 --> 00:34:08,440
and when somebody plays it back,
you can get that signature back.

611
00:34:09,239 --> 00:34:14,440
And you can see that a piece of 
content that was delivered from 

612
00:34:15,120 --> 00:34:17,719
New York is playing in 
Singapore. 

613
00:34:18,520 --> 00:34:23,280
The question becomes why? 
Because if it is a tiny small 

614
00:34:23,280 --> 00:34:26,000
company, yeah, maybe they have 
one location and they're serving

615
00:34:26,000 --> 00:34:27,480
it from New York and it goes 
everywhere. 

616
00:34:27,840 --> 00:34:31,520
But if it's a large sports 
property, they have 

617
00:34:31,520 --> 00:34:35,080
relationships with CDNS, they 
have content everywhere. 

618
00:34:35,440 --> 00:34:38,040
Content that's is in New York 
should not be streaming to 

619
00:34:38,040 --> 00:34:41,520
Singapore. 
So that it becomes a whole other

620
00:34:41,800 --> 00:34:43,520
conversation of what do you do 
with that. 

621
00:34:44,199 --> 00:34:49,360
And the way we structured our 
solution is then the sports 

622
00:34:49,360 --> 00:34:52,760
property can say, well, I'm 
going to let them watch it. 

623
00:34:53,080 --> 00:34:56,440
Let's see what they're watching.
Or, you know, we need to give 

624
00:34:56,440 --> 00:35:00,360
them ads every 3 minutes and 
make this a very miserable 

625
00:35:00,360 --> 00:35:04,480
experience. 
Or just no, we don't want to 

626
00:35:04,480 --> 00:35:06,440
waste their bandwidth on it. 
And we're just going to kill it.

627
00:35:07,240 --> 00:35:10,840
And it gives people, sports and 
rights holders the ability to 

628
00:35:10,840 --> 00:35:15,080
say, I'm just going to decide 
what I'm going to do with this 

629
00:35:15,080 --> 00:35:18,000
person. 
But I'm also, but also it gives 

630
00:35:18,000 --> 00:35:20,720
you access and your visibility 
into what people are doing. 

631
00:35:20,720 --> 00:35:24,280
Like why is this one game 
getting pirated all of a sudden 

632
00:35:24,600 --> 00:35:27,200
to Singapore? 
Maybe we should keep in mind 

633
00:35:27,200 --> 00:35:32,400
that we need to stream it there 
legally or things like that, but

634
00:35:32,400 --> 00:35:36,560
that's the that's the tracking 
part of it is the other product 

635
00:35:36,560 --> 00:35:39,080
that we're currently working on.
Well, what I will say, Olga, is 

636
00:35:39,080 --> 00:35:41,280
you're you're already a 
podcasting expert because I was 

637
00:35:41,280 --> 00:35:43,680
going to bring up the fact that 
you were joining us today 

638
00:35:43,680 --> 00:35:46,160
because of your success in the 
pitching Power Hour and I was 

639
00:35:46,160 --> 00:35:47,960
going to transition into North 
Star. 

640
00:35:47,960 --> 00:35:48,920
So you've already done it for 
me. 

641
00:35:48,920 --> 00:35:50,800
So you're you're already a a 
pro. 

642
00:35:50,800 --> 00:35:53,880
You're learning quickly. 
You know, you, you just take my 

643
00:35:53,880 --> 00:35:57,240
job. 
So yeah, it's like that. 

644
00:35:57,240 --> 00:35:59,240
And also, I think that's part of
the one of the reasons we were 

645
00:35:59,240 --> 00:36:01,920
going to talk about it was the 
fact that this is something that

646
00:36:01,960 --> 00:36:03,280
you know, with our pitching 
power hour. 

647
00:36:03,280 --> 00:36:05,600
For those that don't know, if 
you're listening to stream talk 

648
00:36:05,600 --> 00:36:07,840
sports podcast, you're probably 
aware that we host events 

649
00:36:07,840 --> 00:36:10,280
because you've either been to an
event or you've heard Nick and I

650
00:36:10,280 --> 00:36:12,120
talk about our events. 
One of the things we've done to 

651
00:36:12,120 --> 00:36:16,200
try to change up and diversify 
the content so it's not just 

652
00:36:16,200 --> 00:36:19,560
listening to three blokes on a 
stage kind of all pat each other

653
00:36:19,560 --> 00:36:21,960
in the back is we've introduced 
this pitching power Hour and 

654
00:36:21,960 --> 00:36:24,240
it's quite literally you're 
going to give a 5 minute 

655
00:36:24,440 --> 00:36:27,880
elevator pitch in your product. 
And we have different members of

656
00:36:27,880 --> 00:36:31,560
our Sports Pro Media Awards 
judges there to to go through 

657
00:36:31,560 --> 00:36:33,440
listen to it and vote. 
And you know, so this is 

658
00:36:33,440 --> 00:36:35,400
something that was validated by 
those judges. 

659
00:36:35,400 --> 00:36:40,440
This isn't something, you know, 
that, yeah, you're just here to 

660
00:36:40,440 --> 00:36:41,680
talk about. 
It is something that everyone 

661
00:36:41,680 --> 00:36:44,720
else agrees it's important, 
which I think maybe validates 

662
00:36:44,720 --> 00:36:47,960
the whole thing about the whole 
world of content protection is 

663
00:36:47,960 --> 00:36:50,560
something that more people are 
seeing value and being able to 

664
00:36:50,560 --> 00:36:51,760
track. 
That's hopefully through that 

665
00:36:51,760 --> 00:36:54,280
process. 
And just now that North Star 

666
00:36:54,280 --> 00:36:57,280
officially has a name, you know,
again, like I said, there's 

667
00:36:57,280 --> 00:37:00,960
there's a sign of people looking
more for this kind of stuff 

668
00:37:00,960 --> 00:37:03,440
because some of the solutions 
within that pitching power are 

669
00:37:03,440 --> 00:37:05,520
our are not necessarily content 
security. 

670
00:37:05,520 --> 00:37:07,440
And you know, I've mentioned 
this to Nick before. 

671
00:37:07,680 --> 00:37:10,080
It feels like we used to kind of
have to drag people at our 

672
00:37:10,080 --> 00:37:13,440
events to go to the piracy 
sessions where I think something

673
00:37:13,440 --> 00:37:16,000
like this validates. 
There does seem to be a shifting

674
00:37:16,000 --> 00:37:19,120
of attitudes towards how 
important this actually is for 

675
00:37:19,120 --> 00:37:21,480
people across the landscape. 
We did. 

676
00:37:21,480 --> 00:37:24,440
I did notice that a number of 
people popped when I was 

677
00:37:24,440 --> 00:37:27,040
pitching. 
A number of people popped in and

678
00:37:27,040 --> 00:37:30,720
then I think as I was done, 
which by the way is a very nerve

679
00:37:30,720 --> 00:37:34,280
wracking experience because 
being able to stick a product 

680
00:37:34,680 --> 00:37:38,640
into a 5 minute presentation and
then obviously the judges said 

681
00:37:38,640 --> 00:37:42,280
criteria of, you know, you have 
to cover this, this, this, this 

682
00:37:42,280 --> 00:37:44,040
and this and make it all look 
seamless. 

683
00:37:44,320 --> 00:37:48,680
It is actually not an easy feat,
but I did see people come in, 

684
00:37:48,680 --> 00:37:51,560
listen to my presentation, and 
as I was coming off the stage, 

685
00:37:51,920 --> 00:37:54,800
get up and walk. 
So it was very interesting to 

686
00:37:54,800 --> 00:37:59,280
see that security is becoming 
more and more prevalent and more

687
00:37:59,280 --> 00:38:03,400
and more of a conversation. 
And I think also people are 

688
00:38:03,400 --> 00:38:06,400
trying to figure out how we as 
security vendors are solving 

689
00:38:06,400 --> 00:38:10,680
problems because one of the 
problems that is still out there

690
00:38:10,720 --> 00:38:15,360
that nobody has solved yet is 
the question of key rotation. 

691
00:38:16,560 --> 00:38:19,320
At the moment. 
Often times studios think that 

692
00:38:19,320 --> 00:38:24,880
if you rotate keys out X amount 
of times during the broadcast of

693
00:38:24,880 --> 00:38:28,080
a game, it makes it more secure.
Realistically, of course it 

694
00:38:28,080 --> 00:38:32,440
does, because even if the 
content is pirated, the moment 

695
00:38:32,440 --> 00:38:37,120
the key rotates, the content 
stops playing and then the 

696
00:38:37,120 --> 00:38:39,520
pirate now has to go out and 
figure out how to get the next 

697
00:38:39,520 --> 00:38:41,320
set of keys and so on and so 
forth. 

698
00:38:42,440 --> 00:38:47,880
And that works gloriously if you
have a small game when there's, 

699
00:38:47,880 --> 00:38:51,520
I don't know, 10,000 people are 
watching it because at the end 

700
00:38:51,520 --> 00:38:55,400
of the day, moment that key 
rotates, all those 10,000 people

701
00:38:55,400 --> 00:38:57,920
need to get a new licence. 
That very split second. 

702
00:38:59,640 --> 00:39:03,760
It doesn't really work for an 
NFL size games when you have 

703
00:39:03,760 --> 00:39:07,960
millions of people needing to 
get a licence in the one exact 

704
00:39:07,960 --> 00:39:12,240
second where the key rotates and
you don't want to have a, I'm 

705
00:39:12,240 --> 00:39:14,560
going to call it an ugly 
experience where the screen 

706
00:39:14,560 --> 00:39:17,760
stutters or there's a, you know,
blank time or whatever. 

707
00:39:18,560 --> 00:39:23,480
So even though studios do like 
the idea of key rotation hasn't 

708
00:39:23,480 --> 00:39:26,800
really been a very prevalent 
solution specifically for that. 

709
00:39:27,520 --> 00:39:32,240
So we're also trying to address 
that situation as well. 

710
00:39:33,120 --> 00:39:38,360
And we're also releasing another
product that would allow us to I

711
00:39:38,360 --> 00:39:42,360
don't want to say split, I want 
to say split, but that's not not

712
00:39:42,360 --> 00:39:46,520
the correct word. 
Maybe duplicate encryption on 

713
00:39:46,520 --> 00:39:51,880
content, because at the end of 
the day, DRM is very good at 

714
00:39:51,880 --> 00:39:53,960
rights. 
It knows exactly how to handle 

715
00:39:53,960 --> 00:39:57,160
rights and knows how to control 
things and who gets to view 

716
00:39:57,160 --> 00:40:00,280
stuff and not. 
But in it's not an encryption 

717
00:40:00,520 --> 00:40:03,000
device. 
It does encryption to get its 

718
00:40:03,000 --> 00:40:05,640
rights across, but it's not very
good at encryption. 

719
00:40:06,640 --> 00:40:10,800
In today's world, if you contact
somebody like Akamai and get one

720
00:40:10,800 --> 00:40:15,160
of their edge servers. 
On Leno, you can run encryption 

721
00:40:15,160 --> 00:40:19,000
algorithms and do all sorts of 
things way better, way more 

722
00:40:19,000 --> 00:40:22,080
economical and with way better 
levels of encryption. 

723
00:40:22,960 --> 00:40:25,280
So another product we're 
announcing, which is kind of 

724
00:40:25,280 --> 00:40:29,880
crazy because we're currently 
working on three new products is

725
00:40:29,880 --> 00:40:34,400
what we call a precision 
envelope key management, which 

726
00:40:34,400 --> 00:40:38,440
would allow people specifically,
we think it applies a lot more 

727
00:40:38,440 --> 00:40:42,760
to live content, but it would 
allow rights holders to 

728
00:40:43,120 --> 00:40:45,360
literally double encrypt 
content. 

729
00:40:46,120 --> 00:40:50,760
And you can control the keys and
the encryption from outside of 

730
00:40:50,760 --> 00:40:53,520
DRM. 
And you can control it from, as 

731
00:40:53,560 --> 00:40:56,560
I mentioned, an Edge server from
Lenode or something along those 

732
00:40:56,560 --> 00:41:01,240
lines, where now in order for 
the hackers to get to the DRM 

733
00:41:01,240 --> 00:41:03,760
content, they first have to 
break to the first layer of 

734
00:41:03,760 --> 00:41:08,760
encryption and then get to the, 
the, the keys and then get the 

735
00:41:08,760 --> 00:41:11,120
content. 
So at the very least, we're 

736
00:41:11,120 --> 00:41:14,960
hoping it's going to make, you 
know, piracy life just a smidge 

737
00:41:14,960 --> 00:41:18,200
harder. 
But also, if you are double 

738
00:41:18,200 --> 00:41:23,240
encrypting the content, you are 
looking at the fact that in a 

739
00:41:23,240 --> 00:41:27,400
regular situation, you can see 
all the DRM headers kind of go 

740
00:41:27,400 --> 00:41:31,240
across the wire, the, you know, 
web traffic, if you will. 

741
00:41:31,640 --> 00:41:36,280
And you can sniff them out with,
you know, Http://sniffer type 

742
00:41:36,280 --> 00:41:40,360
applications, You don't see them
anymore where the double 

743
00:41:40,360 --> 00:41:47,080
encryption situation, you don't 
see web DRM headers, you don't 

744
00:41:47,080 --> 00:41:49,320
see any of that conversation 
going on. 

745
00:41:49,320 --> 00:41:53,040
So it becomes a more secure 
solution to begin with. 

746
00:41:53,560 --> 00:41:58,000
And we've tested it in a very 
drastic environment when we 

747
00:41:58,000 --> 00:42:03,880
encrypt every single segment and
there's no delay, we are at sub 

748
00:42:03,880 --> 00:42:08,120
200 milliseconds of being able 
to deliver the solution. 

749
00:42:08,360 --> 00:42:10,600
We're currently testing it. 
We're we're going to test it 

750
00:42:10,600 --> 00:42:12,920
with a broader audience and 
we're going to work with a 

751
00:42:12,920 --> 00:42:17,280
company who's going to try to 
beat it and see how far we get 

752
00:42:17,280 --> 00:42:20,520
with that with testing it to 
make sure there is absolutely no

753
00:42:20,520 --> 00:42:25,000
delay, but adding. 
But we're hoping that adding the

754
00:42:25,000 --> 00:42:30,960
secondary level of encryption 
allows us not only to answer the

755
00:42:31,000 --> 00:42:34,480
more of a secure question, but 
also allow us to get more 

756
00:42:34,480 --> 00:42:36,960
precise with encryption in 
general. 

757
00:42:37,560 --> 00:42:41,520
Where I can give Nick one set of
keys and Chris a different set 

758
00:42:41,520 --> 00:42:43,760
of keys. 
So if hackers are trying to work

759
00:42:43,760 --> 00:42:48,680
together, they would have to 
hack into, if they, even if they

760
00:42:48,680 --> 00:42:51,520
hack into Nick's content, they 
don't get into Chris's. 

761
00:42:52,680 --> 00:42:55,960
And we can do that on a person 
basis that becomes a bit unruly.

762
00:42:56,800 --> 00:43:00,080
We can do it on a geographical 
level in the US and you know, 

763
00:43:00,080 --> 00:43:04,160
New Jersey gets one set of keys,
New York gets another, New York 

764
00:43:04,160 --> 00:43:07,560
City versus I'm in Yonkers and 
so on and so forth. 

765
00:43:07,800 --> 00:43:10,480
And we can get very creative as 
to what we can do. 

766
00:43:10,680 --> 00:43:13,360
Yeah, I think Nick's raised this
a couple times we've had this 

767
00:43:13,360 --> 00:43:14,600
conversation. 
It's going to be really 

768
00:43:14,600 --> 00:43:16,920
difficult to stop piracy, but 
what can you do to make it 

769
00:43:17,280 --> 00:43:20,480
really freaking annoying? 
And I think that's sort of The 

770
00:43:20,480 --> 00:43:22,640
thing is like, you know, you may
not be able to stop it all the 

771
00:43:22,640 --> 00:43:27,160
way, but can you make it 
annoying enough that it it it 

772
00:43:27,160 --> 00:43:28,880
really ruins the experience? 
I think that's the thing about 

773
00:43:28,880 --> 00:43:31,520
live sports, right, is probably 
more than any other piece of 

774
00:43:31,520 --> 00:43:34,720
content, being on time is so 
important. 

775
00:43:34,720 --> 00:43:37,920
So can you make it annoying 
enough that it ruins the 

776
00:43:37,920 --> 00:43:39,600
experience? 
You know, I think we always use 

777
00:43:39,600 --> 00:43:42,840
the example if you're saddened 
two opposite rooms and the 

778
00:43:42,840 --> 00:43:44,760
person that's pirating it is a 
minute behind. 

779
00:43:44,760 --> 00:43:46,800
Like can you make that 
experience real enough that it's

780
00:43:46,800 --> 00:43:48,280
just difficult? 
And I think to your point, the 

781
00:43:48,640 --> 00:43:51,800
the degree with which you can 
manipulate the keys to just make

782
00:43:51,800 --> 00:43:54,520
it annoying enough. 
Like that's I think probably a 

783
00:43:54,520 --> 00:43:58,520
more realistic goal than cutting
out piracy, you know, from the 

784
00:43:58,520 --> 00:44:01,720
root, I guess, in terms of being
able to successfully take it off

785
00:44:01,720 --> 00:44:03,640
the air. 
Well, I mean, the grand scheme 

786
00:44:03,640 --> 00:44:08,360
of things, if you take the the 
four things that we're currently

787
00:44:08,360 --> 00:44:12,480
working on, including our 
original DRMS solution, you're 

788
00:44:12,480 --> 00:44:16,160
looking at a piece of content 
that is DRM protected, which 

789
00:44:16,160 --> 00:44:20,880
means that you know that only 
Nick who paid for this content 

790
00:44:20,880 --> 00:44:24,720
is actually is going to watch it
and he can cast it, but he can't

791
00:44:24,720 --> 00:44:27,040
attach a monitor to it or 
something along those lines. 

792
00:44:27,360 --> 00:44:30,320
We know that this is authentic 
NFL content. 

793
00:44:31,280 --> 00:44:35,120
And then we know that it is 
extra encrypted. 

794
00:44:35,160 --> 00:44:38,680
And we know that Nick is 
watching it in Sweden while 

795
00:44:38,680 --> 00:44:42,120
sitting next to an IKEA shop, 
IKEA store. 

796
00:44:42,400 --> 00:44:44,560
And we know that nobody else is 
watching it. 

797
00:44:44,960 --> 00:44:50,560
And if all of a sudden Nick's 
credentials or Nick's, I don't 

798
00:44:50,560 --> 00:44:53,760
know, CDN tokens and whatnot are
going to start popping up all 

799
00:44:53,760 --> 00:44:56,400
over the place, we know that 
Nick is actively pirating this 

800
00:44:56,400 --> 00:44:57,840
content. 
So we can take it. 

801
00:44:57,840 --> 00:45:01,120
Away from Nick and from 
everybody else he's pirating it 

802
00:45:01,120 --> 00:45:04,880
with. 
And what we are trying to grow 

803
00:45:04,880 --> 00:45:09,360
into, and we think we're going 
to be very successful at it, is 

804
00:45:09,640 --> 00:45:14,120
to actually create a glass to 
glass solution where we know 

805
00:45:14,120 --> 00:45:16,560
that this is properly licenced 
content. 

806
00:45:16,560 --> 00:45:19,960
We know where it's coming from 
and we know where it's being 

807
00:45:19,960 --> 00:45:23,440
played back from. 
And it allows our customers, 

808
00:45:23,440 --> 00:45:26,960
rights holders a lot more 
control and flexibility over 

809
00:45:26,960 --> 00:45:28,840
what they're doing with their 
content. 

810
00:45:29,640 --> 00:45:31,400
That's the goal. 
That's what we're trying to 

811
00:45:31,400 --> 00:45:34,920
achieve right now. 
And since we're recording as 

812
00:45:35,320 --> 00:45:38,480
right before September, do you 
want to stop and see us at IVC? 

813
00:45:38,480 --> 00:45:41,000
We would love to see you. 
Yeah, well, Olga, I, I'm just 

814
00:45:41,000 --> 00:45:42,600
looking at the clock. 
There were some other questions 

815
00:45:42,600 --> 00:45:44,120
I wanted to ask, but just 
conscious, you know, we're 

816
00:45:44,120 --> 00:45:46,240
running low on time. 
But I do want to say genuinely, 

817
00:45:46,440 --> 00:45:48,800
you know, Nick and I said in in 
the meeting just before here, 

818
00:45:48,800 --> 00:45:52,520
we're hoping what we could do is
people walk away and understand 

819
00:45:52,520 --> 00:45:56,240
what ADRM is and where it, it 
fits into the whole protection 

820
00:45:56,240 --> 00:45:57,840
space. 
Like I said, maybe I'm the one 

821
00:45:57,840 --> 00:46:00,560
that needs to learn more given 
how much given I've been at 

822
00:46:00,560 --> 00:46:03,200
sports pro for six years, been 
to sports pro Madrid now is the 

823
00:46:03,200 --> 00:46:05,080
sport for media Summit long 
enough? 

824
00:46:05,080 --> 00:46:07,760
I should have known this, but 
like I've walked away at least 

825
00:46:07,760 --> 00:46:11,080
the better understanding of what
are the tools that I sometimes 

826
00:46:11,080 --> 00:46:13,120
encounter. 
You know, I I basically tell 

827
00:46:13,120 --> 00:46:15,440
people what I do work as I learn
how the sausage is made. 

828
00:46:15,640 --> 00:46:18,080
I now know a little bit more 
about the content security 

829
00:46:18,080 --> 00:46:21,400
sausage and I can say that's the
DRM that they're using that's 

830
00:46:21,400 --> 00:46:23,720
preventing me to do this. 
So I've walked away from this 

831
00:46:23,720 --> 00:46:27,360
conversation having learned more
about where a company like Easy 

832
00:46:27,360 --> 00:46:29,400
DRM fits within the, the 
security space. 

833
00:46:29,400 --> 00:46:32,240
So I I appreciate you being able
to talk it and put it in 

834
00:46:32,240 --> 00:46:34,120
layman's turn for someone like 
myself. 

835
00:46:34,880 --> 00:46:37,880
See, I think the big part that I
want to, you know, kind of 

836
00:46:38,440 --> 00:46:41,360
continue your thought is I don't
think you're expected to know 

837
00:46:41,360 --> 00:46:44,320
about DRM. 
We are expected to know about 

838
00:46:44,320 --> 00:46:46,240
DRM. 
And I think the biggest point I 

839
00:46:46,240 --> 00:46:49,640
would like to get across is if 
people want to know what it is, 

840
00:46:49,720 --> 00:46:52,560
reach out. 
If you want to know what a 

841
00:46:52,560 --> 00:46:55,400
licence is and how that works, 
reach out, say hi. 

842
00:46:55,800 --> 00:46:59,680
Because we as a company, we 
would love to have people 

843
00:46:59,680 --> 00:47:02,040
understand it. 
And if somebody doesn't 

844
00:47:02,040 --> 00:47:04,680
understand how DRM works and 
they would just rather not deal 

845
00:47:04,680 --> 00:47:07,320
with it, schedule 1/2 an hour 
call. 

846
00:47:07,320 --> 00:47:09,560
We'll go through it with you. 
We'll answer your questions, 

847
00:47:09,560 --> 00:47:12,840
we'll explain things and at the 
very least you'll have a better 

848
00:47:12,840 --> 00:47:16,080
understanding of what it is. 
That's kind of like, you know, 

849
00:47:16,600 --> 00:47:20,440
the name Easy DRM. 
We try to stick to the easy part

850
00:47:20,440 --> 00:47:25,960
of it and make sure that even if
somebody doesn't end up becoming

851
00:47:25,960 --> 00:47:29,480
a customer, at least they 
understand what is going on and 

852
00:47:29,480 --> 00:47:31,920
why things are happening the way
they are and they're more 

853
00:47:31,920 --> 00:47:34,600
comfortable with the solution. 
Why they wouldn't become a 

854
00:47:34,600 --> 00:47:39,400
customer, I don't know, but at 
the end of the day we are all 

855
00:47:39,400 --> 00:47:42,120
about making sure that you 
understand what the technology 

856
00:47:42,120 --> 00:47:44,680
that you're working with is, and
we don't want to make it a 

857
00:47:44,680 --> 00:47:47,800
black, scary, expensive box of 
unknown stuff. 

858
00:47:47,960 --> 00:47:49,080
Brilliant. 
Well, like I said, I really 

859
00:47:49,080 --> 00:47:52,080
appreciate you coming on and 
talking us through that today, 

860
00:47:52,080 --> 00:47:54,160
Olga. 
Of course it was fun. 

861
00:47:54,200 --> 00:47:55,400
Thanks so much, Olga, that was 
great. 

862
00:47:55,400 --> 00:47:58,040
I'd have to say that just 
anecdotally, firstly, I'm not 

863
00:47:58,040 --> 00:48:00,720
pirating anything here for those
wondering based on Chris is an 

864
00:48:00,720 --> 00:48:02,800
example. 
But from the conversations I've 

865
00:48:02,800 --> 00:48:07,040
had recently, protection and 
security of content, it is 

866
00:48:07,040 --> 00:48:13,560
becoming a bigger and bigger 
concern having huge impact. 

867
00:48:13,560 --> 00:48:17,080
And it does feel like the 
industry is a little bit lost 

868
00:48:17,080 --> 00:48:21,520
and I'm talking at sea level and
down as well at what to do with 

869
00:48:21,520 --> 00:48:23,760
this. 
So Olga, thank you for giving us

870
00:48:23,760 --> 00:48:27,280
a bit of insight into what are 
some of the levers of the 

871
00:48:27,280 --> 00:48:28,640
toolbox. 
So I think we've used a few 

872
00:48:28,640 --> 00:48:31,680
metaphors today, Reggie, called 
sausages to can doors. 

873
00:48:31,680 --> 00:48:34,280
But I think it's been really 
helpful to get a bit more 

874
00:48:34,280 --> 00:48:37,080
clarity on where particularly 
DRM sits because I know a few 

875
00:48:37,080 --> 00:48:40,240
people have different levels of 
understanding and haven't needed

876
00:48:40,240 --> 00:48:42,520
to really understand or didn't 
really understand the need, 

877
00:48:42,720 --> 00:48:44,720
didn't understand the need to 
know. 

878
00:48:44,720 --> 00:48:47,040
And now hopefully we've given a 
little bit more insight. 

879
00:48:47,040 --> 00:48:49,080
So thanks very much for that. 
Absolutely, anytime. 

880
00:48:49,840 --> 00:48:51,560
Thank you very much for having 
me, it's been fun.

