WEBVTT

00:00:00.000 --> 00:00:00.318
Nearly

00:00:00.382 --> 00:00:00.638
half

00:00:00.691 --> 00:00:00.797
of

00:00:00.897 --> 00:00:01.197
all

00:00:01.277 --> 00:00:01.677
world

00:00:01.762 --> 00:00:02.867
organisations

00:00:02.947 --> 00:00:03.267
have

00:00:03.327 --> 00:00:03.507
had

00:00:03.587 --> 00:00:03.907
some

00:00:03.987 --> 00:00:04.307
sort

00:00:04.333 --> 00:00:04.385
of

00:00:04.450 --> 00:00:05.100
experience

00:00:05.164 --> 00:00:05.420
with

00:00:05.500 --> 00:00:06.140
problems

00:00:06.220 --> 00:00:06.940
regarding

00:00:07.020 --> 00:00:07.340
data

00:00:07.420 --> 00:00:08.060
security

00:00:08.510 --> 00:00:08.780
And

00:00:08.837 --> 00:00:09.179
indeed

00:00:09.579 --> 00:00:09.739
as

00:00:09.803 --> 00:00:10.059
more

00:00:10.123 --> 00:00:10.379
data

00:00:10.485 --> 00:00:10.697
is

00:00:10.757 --> 00:00:11.177
created

00:00:11.777 --> 00:00:11.897
the

00:00:11.961 --> 00:00:12.217
more

00:00:12.270 --> 00:00:12.376
it

00:00:12.408 --> 00:00:12.536
will

00:00:12.632 --> 00:00:13.016
leak

00:00:13.536 --> 00:00:13.656
the

00:00:13.720 --> 00:00:13.976
more

00:00:14.047 --> 00:00:14.615
security

00:00:14.672 --> 00:00:15.014
audits

00:00:15.046 --> 00:00:15.174
will

00:00:15.254 --> 00:00:15.574
fail

00:00:16.094 --> 00:00:16.214
and

00:00:16.234 --> 00:00:16.294
the

00:00:16.326 --> 00:00:16.454
more

00:00:16.516 --> 00:00:17.012
frequent

00:00:17.072 --> 00:00:17.492
attacks

00:00:17.524 --> 00:00:17.652
will

00:00:17.720 --> 00:00:18.128
become

00:00:18.501 --> 00:00:18.927
It

00:00:19.007 --> 00:00:19.167
is

00:00:19.193 --> 00:00:19.245
an

00:00:19.295 --> 00:00:19.795
inevitable

00:00:19.891 --> 00:00:20.275
part

00:00:20.328 --> 00:00:20.434
of

00:00:20.494 --> 00:00:20.674
any

00:00:20.732 --> 00:00:21.472
technology’s

00:00:21.552 --> 00:00:22.272
lifecycle

00:00:22.372 --> 00:00:22.672
and

00:00:22.692 --> 00:00:22.752
the

00:00:22.845 --> 00:00:23.310
cloud

00:00:23.670 --> 00:00:23.870
which

00:00:23.923 --> 00:00:24.029
is

00:00:24.077 --> 00:00:24.509
currently

00:00:24.575 --> 00:00:24.905
still

00:00:24.945 --> 00:00:25.065
one

00:00:25.091 --> 00:00:25.143
of

00:00:25.183 --> 00:00:25.303
the

00:00:25.367 --> 00:00:25.623
most

00:00:25.714 --> 00:00:26.260
secure

00:00:26.356 --> 00:00:26.740
ways

00:00:26.793 --> 00:00:26.899
of

00:00:26.959 --> 00:00:27.379
storing

00:00:27.419 --> 00:00:27.539
and

00:00:27.610 --> 00:00:28.178
managing

00:00:28.210 --> 00:00:28.338
your

00:00:28.418 --> 00:00:28.738
data

00:00:29.458 --> 00:00:29.618
is

00:00:29.698 --> 00:00:29.858
no

00:00:29.922 --> 00:00:30.498
exception

00:00:30.578 --> 00:00:30.738
to

00:00:30.770 --> 00:00:30.898
this

00:00:30.978 --> 00:00:31.298
rule

00:00:31.554 --> 00:00:32.258
Most

00:00:32.311 --> 00:00:32.417
of

00:00:32.437 --> 00:00:32.497
the

00:00:32.577 --> 00:00:32.897
time

00:00:33.277 --> 00:00:33.457
new

00:00:33.510 --> 00:00:33.934
security

00:00:34.005 --> 00:00:34.573
services

00:00:34.593 --> 00:00:34.653
and

00:00:34.725 --> 00:00:35.373
solutions

00:00:35.473 --> 00:00:35.853
won’t

00:00:35.906 --> 00:00:36.012
be

00:00:36.038 --> 00:00:36.090
of

00:00:36.138 --> 00:00:36.330
much

00:00:36.394 --> 00:00:36.650
help

00:00:36.730 --> 00:00:37.210
either

00:00:37.423 --> 00:00:37.849
as

00:00:37.913 --> 00:00:38.489
generally

00:00:38.937 --> 00:00:39.369
companies

00:00:39.429 --> 00:00:39.689
don’t

00:00:39.760 --> 00:00:40.328
actually

00:00:40.408 --> 00:00:40.728
know

00:00:40.781 --> 00:00:41.046
which

00:00:41.102 --> 00:00:41.606
solutions

00:00:41.654 --> 00:00:41.846
they

00:00:41.891 --> 00:00:42.161
should

00:00:42.217 --> 00:00:42.721
implement

00:00:42.801 --> 00:00:42.961
to

00:00:43.011 --> 00:00:43.361
protect

00:00:43.426 --> 00:00:44.076
themselves

00:00:44.332 --> 00:00:45.036
This

00:00:45.089 --> 00:00:45.195
is

00:00:45.235 --> 00:00:45.355
the

00:00:45.420 --> 00:00:46.070
conclusion

00:00:46.102 --> 00:00:46.230
that

00:00:46.301 --> 00:00:46.869
security

00:00:46.929 --> 00:00:47.349
company

00:00:47.455 --> 00:00:48.227
Thales

00:00:48.323 --> 00:00:48.707
came

00:00:48.840 --> 00:00:49.106
to

00:00:49.239 --> 00:00:49.505
in

00:00:49.531 --> 00:00:49.661
their

00:00:49.718 --> 00:00:50.060
recent

00:00:50.140 --> 00:00:50.540
Cloud

00:00:50.602 --> 00:00:51.098
Security

00:00:51.164 --> 00:00:51.494
Study

00:00:51.699 --> 00:00:52.449
Global

00:00:52.529 --> 00:00:53.089
Edition

00:00:53.742 --> 00:00:54.207
Multi

00:00:54.287 --> 00:00:54.687
cloud

00:00:54.751 --> 00:00:55.327
solutions

00:00:55.367 --> 00:00:55.487
are

00:00:55.593 --> 00:00:55.805
on

00:00:55.825 --> 00:00:55.885
the

00:00:56.045 --> 00:00:56.685
rise

00:00:56.858 --> 00:00:58.043
Alongside

00:00:58.083 --> 00:00:58.203
new

00:00:58.270 --> 00:00:59.074
technologies

00:00:59.114 --> 00:00:59.234
and

00:00:59.289 --> 00:00:59.949
increasingly

00:01:00.013 --> 00:01:00.269
more

00:01:00.349 --> 00:01:00.909
complex

00:01:00.982 --> 00:01:01.858
applications

00:01:02.518 --> 00:01:02.578
the

00:01:02.636 --> 00:01:03.448
implementation

00:01:03.501 --> 00:01:03.607
of

00:01:03.660 --> 00:01:03.925
cloud

00:01:03.990 --> 00:01:04.640
technology

00:01:04.746 --> 00:01:04.958
is

00:01:05.038 --> 00:01:05.358
also

00:01:05.420 --> 00:01:05.916
becoming

00:01:05.964 --> 00:01:06.156
more

00:01:06.222 --> 00:01:06.948
complicated

00:01:07.108 --> 00:01:07.588
and

00:01:07.633 --> 00:01:07.903
simply

00:01:07.958 --> 00:01:08.618
transferring

00:01:08.650 --> 00:01:08.778
your

00:01:08.858 --> 00:01:09.178
data

00:01:09.218 --> 00:01:09.338
and

00:01:09.405 --> 00:01:10.209
applications

00:01:10.262 --> 00:01:10.368
to

00:01:10.388 --> 00:01:10.448
the

00:01:10.541 --> 00:01:11.006
cloud

00:01:11.192 --> 00:01:11.564
is

00:01:11.617 --> 00:01:11.723
no

00:01:11.780 --> 00:01:12.122
longer

00:01:12.202 --> 00:01:12.682
enough

00:01:13.210 --> 00:01:13.562
This

00:01:13.615 --> 00:01:13.721
is

00:01:13.777 --> 00:01:14.281
confirmed

00:01:14.334 --> 00:01:14.440
by

00:01:14.520 --> 00:01:14.840
both

00:01:14.920 --> 00:01:15.560
Thales’

00:01:15.666 --> 00:01:16.196
study

00:01:16.356 --> 00:01:16.676
as

00:01:16.708 --> 00:01:16.836
well

00:01:16.889 --> 00:01:16.995
as

00:01:17.155 --> 00:01:17.635
ADM

00:01:17.701 --> 00:01:18.431
Cloudtech’s

00:01:18.751 --> 00:01:18.911
where

00:01:18.951 --> 00:01:18.991
I

00:01:19.071 --> 00:01:19.391
work

00:01:19.587 --> 00:01:20.747
experience

00:01:20.880 --> 00:01:21.146
as

00:01:21.186 --> 00:01:21.306
the

00:01:21.372 --> 00:01:21.702
cloud

00:01:21.752 --> 00:01:22.252
management

00:01:22.302 --> 00:01:22.652
partner

00:01:22.712 --> 00:01:22.892
for

00:01:22.952 --> 00:01:23.372
various

00:01:23.436 --> 00:01:24.012
companies

00:01:24.072 --> 00:01:24.252
and

00:01:24.302 --> 00:01:24.802
government

00:01:24.888 --> 00:01:25.920
institutions

00:01:26.443 --> 00:01:26.959
implementing

00:01:27.025 --> 00:01:27.355
cloud

00:01:27.411 --> 00:01:27.915
solutions

00:01:27.968 --> 00:01:28.074
in

00:01:28.094 --> 00:01:28.154
the

00:01:28.216 --> 00:01:28.712
simplest

00:01:28.812 --> 00:01:29.112
way

00:01:29.432 --> 00:01:30.152
AKA

00:01:30.338 --> 00:01:30.710
by

00:01:30.765 --> 00:01:31.425
transferring

00:01:31.489 --> 00:01:31.745
data

00:01:31.771 --> 00:01:31.823
to

00:01:31.843 --> 00:01:31.903
the

00:01:32.023 --> 00:01:32.623
cloud

00:01:32.783 --> 00:01:33.263
has

00:01:33.319 --> 00:01:33.823
decreased

00:01:33.903 --> 00:01:34.063
by

00:01:34.116 --> 00:01:34.381
about

00:01:34.477 --> 00:01:34.861
half

00:01:35.421 --> 00:01:35.581
from

00:01:35.661 --> 00:01:36.381
55

00:01:36.807 --> 00:01:36.859
to

00:01:37.019 --> 00:01:37.899
24

00:01:38.051 --> 00:01:38.699
according

00:01:38.725 --> 00:01:38.777
to

00:01:38.857 --> 00:01:39.417
Thales

00:01:39.790 --> 00:01:40.376
In

00:01:40.456 --> 00:01:41.096
contrast

00:01:41.656 --> 00:01:41.896
use

00:01:41.976 --> 00:01:42.136
of

00:01:42.202 --> 00:01:42.532
multi

00:01:42.598 --> 00:01:42.928
cloud

00:01:43.000 --> 00:01:43.648
solutions

00:01:43.728 --> 00:01:43.888
is

00:01:43.941 --> 00:01:44.047
on

00:01:44.067 --> 00:01:44.127
the

00:01:44.207 --> 00:01:44.767
fastest

00:01:44.895 --> 00:01:45.407
rise

00:01:45.951 --> 00:01:46.207
last

00:01:46.271 --> 00:01:46.527
year

00:01:46.972 --> 00:01:47.242
around

00:01:47.402 --> 00:01:48.122
57

00:01:48.575 --> 00:01:48.681
of

00:01:48.741 --> 00:01:48.921
all

00:01:48.977 --> 00:01:49.481
companies

00:01:49.543 --> 00:01:50.039
surveyed

00:01:50.183 --> 00:01:50.759
used

00:01:50.821 --> 00:01:51.317
multiple

00:01:51.557 --> 00:01:52.595
IaaS

00:01:52.665 --> 00:01:53.155
service

00:01:53.219 --> 00:01:53.795
providers

00:01:54.395 --> 00:01:54.515
but

00:01:54.563 --> 00:01:54.755
this

00:01:54.803 --> 00:01:54.995
year

00:01:55.523 --> 00:01:55.715
that

00:01:55.760 --> 00:01:56.030
number

00:01:56.070 --> 00:01:56.190
has

00:01:56.256 --> 00:01:56.586
grown

00:01:56.639 --> 00:01:56.745
to

00:01:56.905 --> 00:01:57.625
72

00:01:58.465 --> 00:01:59.065
The

00:01:59.105 --> 00:01:59.385
biggest

00:01:59.433 --> 00:01:59.625
part

00:01:59.651 --> 00:01:59.703
of

00:01:59.735 --> 00:01:59.863
that

00:01:59.916 --> 00:02:00.340
increase

00:02:00.400 --> 00:02:00.820
belongs

00:02:00.846 --> 00:02:00.898
to

00:02:00.960 --> 00:02:01.766
organisations

00:02:01.798 --> 00:02:01.926
that

00:02:02.026 --> 00:02:02.326
use

00:02:02.379 --> 00:02:02.644
three

00:02:02.724 --> 00:02:02.884
or

00:02:02.980 --> 00:02:03.364
more

00:02:03.724 --> 00:02:04.882
IaaS

00:02:04.942 --> 00:02:05.362
service

00:02:05.450 --> 00:02:06.242
providers

00:02:06.908 --> 00:02:07.038
their

00:02:07.081 --> 00:02:07.511
proportion

00:02:07.567 --> 00:02:08.071
increased

00:02:08.103 --> 00:02:08.231
from

00:02:08.311 --> 00:02:08.631
10

00:02:09.164 --> 00:02:09.430
to

00:02:09.590 --> 00:02:09.910
20

00:02:10.590 --> 00:02:11.190
The

00:02:11.240 --> 00:02:11.740
increasing

00:02:11.805 --> 00:02:12.455
popularity

00:02:12.508 --> 00:02:12.614
of

00:02:12.680 --> 00:02:13.010
multi

00:02:13.076 --> 00:02:13.406
cloud

00:02:13.494 --> 00:02:14.286
solutions

00:02:14.419 --> 00:02:14.685
is

00:02:14.755 --> 00:02:15.245
logical

00:02:15.365 --> 00:02:15.725
and

00:02:15.783 --> 00:02:16.363
completely

00:02:16.419 --> 00:02:16.923
warranted

00:02:17.243 --> 00:02:18.043
First

00:02:18.256 --> 00:02:18.921
using

00:02:18.961 --> 00:02:19.321
different

00:02:19.401 --> 00:02:19.801
cloud

00:02:19.881 --> 00:02:20.521
services

00:02:20.609 --> 00:02:21.401
decreases

00:02:21.441 --> 00:02:21.481
a

00:02:21.541 --> 00:02:22.041
company’s

00:02:22.099 --> 00:02:22.679
dependency

00:02:22.785 --> 00:02:22.997
on

00:02:23.077 --> 00:02:23.317
one

00:02:23.385 --> 00:02:23.793
single

00:02:23.843 --> 00:02:24.193
service

00:02:24.255 --> 00:02:24.751
provider

00:02:25.059 --> 00:02:25.947
second

00:02:26.213 --> 00:02:26.585
it

00:02:26.625 --> 00:02:26.825
gives

00:02:26.865 --> 00:02:26.985
the

00:02:27.035 --> 00:02:27.385
company

00:02:27.449 --> 00:02:27.705
more

00:02:27.785 --> 00:02:28.665
flexibility

00:02:28.851 --> 00:02:29.223
by

00:02:29.271 --> 00:02:29.703
providing

00:02:29.743 --> 00:02:29.863
the

00:02:29.923 --> 00:02:30.583
opportunity

00:02:30.636 --> 00:02:30.742
to

00:02:30.842 --> 00:02:31.142
use

00:02:31.204 --> 00:02:31.700
specific

00:02:31.771 --> 00:02:32.339
services

00:02:32.451 --> 00:02:32.899
from

00:02:32.939 --> 00:02:33.299
different

00:02:33.365 --> 00:02:33.695
cloud

00:02:33.767 --> 00:02:34.415
solutions

00:02:34.855 --> 00:02:34.975
e

00:02:35.055 --> 00:02:35.135
g

00:02:35.295 --> 00:02:36.095
artificial

00:02:36.144 --> 00:02:36.732
intelligence

00:02:36.812 --> 00:02:36.972
or

00:02:37.052 --> 00:02:37.292
big

00:02:37.356 --> 00:02:37.612
data

00:02:37.684 --> 00:02:38.404
processing

00:02:38.684 --> 00:02:39.284
and

00:02:39.350 --> 00:02:39.680
third

00:02:39.906 --> 00:02:40.636
using

00:02:40.702 --> 00:02:41.032
multi

00:02:41.098 --> 00:02:41.428
cloud

00:02:41.492 --> 00:02:42.068
solutions

00:02:42.208 --> 00:02:42.628
can

00:02:42.676 --> 00:02:42.868
help

00:02:42.948 --> 00:02:43.508
isolate

00:02:43.568 --> 00:02:43.748
and

00:02:43.819 --> 00:02:44.387
decrease

00:02:44.407 --> 00:02:44.467
the

00:02:44.547 --> 00:02:45.027
effect

00:02:45.107 --> 00:02:45.267
of

00:02:45.323 --> 00:02:45.827
potential

00:02:45.883 --> 00:02:46.387
incidents

00:02:46.707 --> 00:02:47.187
But

00:02:47.247 --> 00:02:47.667
despite

00:02:47.747 --> 00:02:47.987
all

00:02:48.040 --> 00:02:48.305
these

00:02:48.367 --> 00:02:48.863
positive

00:02:48.953 --> 00:02:49.583
aspects

00:02:49.929 --> 00:02:50.301
we

00:02:50.349 --> 00:02:50.541
must

00:02:50.581 --> 00:02:50.781
still

00:02:50.841 --> 00:02:51.261
account

00:02:51.301 --> 00:02:51.421
for

00:02:51.469 --> 00:02:51.901
potential

00:02:51.994 --> 00:02:52.459
risks

00:02:52.770 --> 00:02:53.978
Security

00:02:54.298 --> 00:02:54.938
security

00:02:55.346 --> 00:02:56.050
security

00:02:56.343 --> 00:02:56.929
By

00:02:56.973 --> 00:02:57.325
trusting

00:02:57.365 --> 00:02:57.485
our

00:02:57.549 --> 00:02:57.805
data

00:02:57.831 --> 00:02:57.883
to

00:02:57.923 --> 00:02:58.043
the

00:02:58.109 --> 00:02:58.439
cloud

00:02:58.939 --> 00:02:58.999
the

00:02:59.063 --> 00:02:59.319
most

00:02:59.369 --> 00:02:59.719
burning

00:02:59.781 --> 00:03:00.277
question

00:03:00.357 --> 00:03:00.517
is

00:03:00.577 --> 00:03:00.757
not

00:03:00.810 --> 00:03:01.075
about

00:03:01.095 --> 00:03:01.155
the

00:03:01.223 --> 00:03:01.631
rented

00:03:01.681 --> 00:03:02.031
storage

00:03:02.151 --> 00:03:02.751
space

00:03:02.911 --> 00:03:03.231
or

00:03:03.284 --> 00:03:03.549
about

00:03:03.602 --> 00:03:04.026
dividing

00:03:04.074 --> 00:03:04.506
potential

00:03:04.586 --> 00:03:04.986
risks

00:03:05.092 --> 00:03:05.304
up

00:03:05.354 --> 00:03:05.704
between

00:03:05.748 --> 00:03:06.100
multiple

00:03:06.160 --> 00:03:06.580
service

00:03:06.644 --> 00:03:07.220
providers

00:03:07.520 --> 00:03:07.940
but

00:03:07.980 --> 00:03:08.180
about

00:03:08.200 --> 00:03:08.260
the

00:03:08.331 --> 00:03:08.899
security

00:03:08.970 --> 00:03:09.538
involved

00:03:09.838 --> 00:03:10.498
The

00:03:10.543 --> 00:03:10.813
golden

00:03:10.877 --> 00:03:11.133
rule

00:03:11.245 --> 00:03:11.693
here

00:03:11.853 --> 00:03:12.173
is

00:03:12.205 --> 00:03:12.333
that

00:03:12.373 --> 00:03:12.493
the

00:03:12.557 --> 00:03:12.813
more

00:03:12.877 --> 00:03:13.133
data

00:03:13.173 --> 00:03:13.293
you

00:03:13.359 --> 00:03:13.689
store

00:03:13.715 --> 00:03:13.767
in

00:03:13.787 --> 00:03:13.847
the

00:03:13.927 --> 00:03:14.327
cloud

00:03:14.847 --> 00:03:14.967
the

00:03:14.999 --> 00:03:15.127
more

00:03:15.191 --> 00:03:15.767
important

00:03:15.838 --> 00:03:16.406
security

00:03:16.496 --> 00:03:17.126
becomes

00:03:17.462 --> 00:03:18.166
This

00:03:18.230 --> 00:03:18.486
rule

00:03:18.592 --> 00:03:18.804
is

00:03:18.852 --> 00:03:19.284
perfectly

00:03:19.352 --> 00:03:20.160
exemplified

00:03:20.213 --> 00:03:20.319
by

00:03:20.399 --> 00:03:21.039
Thales’

00:03:21.119 --> 00:03:21.599
report

00:03:22.199 --> 00:03:22.399
which

00:03:22.439 --> 00:03:22.639
found

00:03:22.671 --> 00:03:22.799
that

00:03:22.879 --> 00:03:23.519
35

00:03:23.945 --> 00:03:23.997
of

00:03:24.059 --> 00:03:24.865
organisations

00:03:24.961 --> 00:03:25.345
have

00:03:25.405 --> 00:03:26.065
experienced

00:03:26.145 --> 00:03:26.465
data

00:03:26.518 --> 00:03:26.783
leaks

00:03:26.815 --> 00:03:26.943
from

00:03:26.963 --> 00:03:27.023
the

00:03:27.129 --> 00:03:27.659
cloud

00:03:27.845 --> 00:03:28.217
or

00:03:28.249 --> 00:03:28.377
have

00:03:28.445 --> 00:03:28.853
failed

00:03:28.893 --> 00:03:29.093
their

00:03:29.173 --> 00:03:29.573
cloud

00:03:29.635 --> 00:03:30.131
resource

00:03:30.222 --> 00:03:30.768
audits

00:03:31.068 --> 00:03:31.728
The

00:03:31.785 --> 00:03:32.127
latter

00:03:32.180 --> 00:03:32.286
is

00:03:32.326 --> 00:03:32.686
certainly

00:03:32.743 --> 00:03:33.085
better

00:03:33.117 --> 00:03:33.245
than

00:03:33.298 --> 00:03:33.404
an

00:03:33.472 --> 00:03:33.880
actual

00:03:33.944 --> 00:03:34.200
data

00:03:34.280 --> 00:03:34.600
leak

00:03:34.786 --> 00:03:35.158
as

00:03:35.184 --> 00:03:35.236
it

00:03:35.289 --> 00:03:35.713
provides

00:03:35.766 --> 00:03:35.872
us

00:03:35.904 --> 00:03:36.032
with

00:03:36.072 --> 00:03:36.192
the

00:03:36.252 --> 00:03:36.912
opportunity

00:03:36.965 --> 00:03:37.071
to

00:03:37.141 --> 00:03:37.631
improve

00:03:37.693 --> 00:03:38.189
existing

00:03:38.277 --> 00:03:39.069
solutions

00:03:39.160 --> 00:03:39.706
before

00:03:39.766 --> 00:03:39.946
any

00:03:40.026 --> 00:03:40.506
actual

00:03:40.574 --> 00:03:40.982
damage

00:03:41.008 --> 00:03:41.060
is

00:03:41.156 --> 00:03:41.540
done

00:03:41.750 --> 00:03:43.050
Prevention

00:03:43.103 --> 00:03:43.209
is

00:03:43.264 --> 00:03:43.924
increasingly

00:03:43.972 --> 00:03:44.164
more

00:03:44.236 --> 00:03:44.884
important

00:03:45.070 --> 00:03:45.442
as

00:03:45.482 --> 00:03:45.602
the

00:03:45.647 --> 00:03:45.917
amount

00:03:45.943 --> 00:03:45.995
of

00:03:46.051 --> 00:03:46.555
sensitive

00:03:46.635 --> 00:03:46.955
data

00:03:47.015 --> 00:03:47.195
and

00:03:47.239 --> 00:03:47.591
critical

00:03:47.652 --> 00:03:48.384
applications

00:03:48.441 --> 00:03:48.783
stored

00:03:48.809 --> 00:03:48.861
in

00:03:48.901 --> 00:03:49.021
the

00:03:49.114 --> 00:03:49.579
cloud

00:03:49.739 --> 00:03:50.059
is

00:03:50.109 --> 00:03:50.459
growing

00:03:50.491 --> 00:03:50.619
with

00:03:50.667 --> 00:03:50.859
each

00:03:50.959 --> 00:03:51.259
day

00:03:52.219 --> 00:03:52.779
85

00:03:53.125 --> 00:03:53.177
of

00:03:53.233 --> 00:03:53.737
companies

00:03:53.797 --> 00:03:53.977
say

00:03:54.009 --> 00:03:54.137
that

00:03:54.190 --> 00:03:54.455
about

00:03:54.495 --> 00:03:54.535
a

00:03:54.601 --> 00:03:54.931
fifth

00:03:54.984 --> 00:03:55.090
of

00:03:55.110 --> 00:03:55.170
the

00:03:55.250 --> 00:03:55.570
data

00:03:55.602 --> 00:03:55.730
they

00:03:55.783 --> 00:03:56.048
store

00:03:56.074 --> 00:03:56.126
in

00:03:56.146 --> 00:03:56.206
the

00:03:56.286 --> 00:03:56.686
cloud

00:03:56.899 --> 00:03:57.325
is

00:03:57.389 --> 00:03:57.965
sensitive

00:03:58.225 --> 00:03:58.765
and

00:03:58.813 --> 00:03:59.005
over

00:03:59.165 --> 00:03:59.485
50

00:03:59.965 --> 00:04:00.205
say

00:04:00.237 --> 00:04:00.365
that

00:04:00.418 --> 00:04:00.524
at

00:04:00.564 --> 00:04:00.764
least

00:04:01.004 --> 00:04:01.324
40

00:04:01.670 --> 00:04:01.722
of

00:04:01.742 --> 00:04:01.802
the

00:04:01.882 --> 00:04:02.202
data

00:04:02.234 --> 00:04:02.362
they

00:04:02.394 --> 00:04:02.522
have

00:04:02.579 --> 00:04:02.921
stored

00:04:02.947 --> 00:04:02.999
in

00:04:03.019 --> 00:04:03.079
the

00:04:03.159 --> 00:04:03.559
cloud

00:04:03.799 --> 00:04:04.279
is

00:04:04.346 --> 00:04:05.150
confidential

00:04:05.896 --> 00:04:06.268
As

00:04:06.288 --> 00:04:06.348
the

00:04:06.393 --> 00:04:06.663
amount

00:04:06.689 --> 00:04:06.741
of

00:04:06.805 --> 00:04:07.381
sensitive

00:04:07.461 --> 00:04:07.781
data

00:04:07.807 --> 00:04:07.859
in

00:04:07.879 --> 00:04:07.939
the

00:04:08.005 --> 00:04:08.335
cloud

00:04:08.395 --> 00:04:08.575
has

00:04:08.641 --> 00:04:08.971
grown

00:04:09.744 --> 00:04:09.850
so

00:04:09.910 --> 00:04:10.090
has

00:04:10.110 --> 00:04:10.170
the

00:04:10.215 --> 00:04:10.485
number

00:04:10.538 --> 00:04:10.644
of

00:04:10.724 --> 00:04:11.284
malware

00:04:11.672 --> 00:04:12.320
ransomware

00:04:12.760 --> 00:04:12.880
and

00:04:12.924 --> 00:04:13.276
phishing

00:04:13.356 --> 00:04:13.916
attacks

00:04:14.188 --> 00:04:14.956
Even

00:04:15.004 --> 00:04:15.196
this

00:04:15.249 --> 00:04:15.514
makes

00:04:15.567 --> 00:04:15.832
sense

00:04:15.885 --> 00:04:15.991
as

00:04:16.031 --> 00:04:16.151
the

00:04:16.211 --> 00:04:16.391
bad

00:04:16.455 --> 00:04:16.711
guys

00:04:16.759 --> 00:04:16.951
tend

00:04:16.977 --> 00:04:17.029
to

00:04:17.082 --> 00:04:17.188
go

00:04:17.214 --> 00:04:17.344
where

00:04:17.364 --> 00:04:17.424
the

00:04:17.477 --> 00:04:17.742
money

00:04:17.822 --> 00:04:17.982
is

00:04:18.142 --> 00:04:18.462
to

00:04:18.542 --> 00:04:18.782
try

00:04:18.802 --> 00:04:18.862
and

00:04:18.922 --> 00:04:19.102
get

00:04:19.142 --> 00:04:19.342
their

00:04:19.395 --> 00:04:19.660
share

00:04:19.713 --> 00:04:19.819
of

00:04:19.872 --> 00:04:19.978
it

00:04:20.258 --> 00:04:20.858
The

00:04:20.906 --> 00:04:21.098
most

00:04:21.146 --> 00:04:21.578
efficient

00:04:21.674 --> 00:04:22.058
ways

00:04:22.084 --> 00:04:22.136
of

00:04:22.198 --> 00:04:22.694
reducing

00:04:22.760 --> 00:04:23.090
cloud

00:04:23.140 --> 00:04:23.490
related

00:04:23.570 --> 00:04:23.970
risks

00:04:24.090 --> 00:04:24.450
are

00:04:24.480 --> 00:04:24.690
thought

00:04:24.743 --> 00:04:24.849
to

00:04:24.902 --> 00:04:25.008
be

00:04:25.048 --> 00:04:25.168
the

00:04:25.218 --> 00:04:25.718
encryption

00:04:25.771 --> 00:04:25.877
of

00:04:25.957 --> 00:04:26.277
data

00:04:26.377 --> 00:04:26.677
and

00:04:26.743 --> 00:04:27.469
connections

00:04:27.789 --> 00:04:28.349
59

00:04:29.508 --> 00:04:29.628
Key

00:04:29.678 --> 00:04:30.178
Management

00:04:30.658 --> 00:04:31.138
52

00:04:31.737 --> 00:04:32.337
and

00:04:32.377 --> 00:04:32.497
the

00:04:32.577 --> 00:04:32.897
Zero

00:04:32.990 --> 00:04:33.455
Trust

00:04:33.517 --> 00:04:34.013
security

00:04:34.079 --> 00:04:34.409
model

00:04:34.777 --> 00:04:35.609
Data

00:04:35.659 --> 00:04:36.159
encryption

00:04:36.219 --> 00:04:36.399
has

00:04:36.444 --> 00:04:36.714
become

00:04:36.762 --> 00:04:36.954
more

00:04:37.024 --> 00:04:37.514
popular

00:04:37.562 --> 00:04:37.754
over

00:04:37.794 --> 00:04:37.914
the

00:04:37.978 --> 00:04:38.234
last

00:04:38.314 --> 00:04:38.634
year

00:04:39.294 --> 00:04:39.354
but

00:04:39.380 --> 00:04:39.510
there

00:04:39.550 --> 00:04:39.670
are

00:04:39.710 --> 00:04:39.910
still

00:04:39.967 --> 00:04:40.309
plenty

00:04:40.335 --> 00:04:40.387
of

00:04:40.449 --> 00:04:41.255
organisations

00:04:41.281 --> 00:04:41.411
where

00:04:41.451 --> 00:04:41.571
the

00:04:41.635 --> 00:04:41.891
data

00:04:41.923 --> 00:04:42.051
they

00:04:42.117 --> 00:04:42.447
store

00:04:42.473 --> 00:04:42.525
in

00:04:42.545 --> 00:04:42.605
the

00:04:42.711 --> 00:04:43.241
cloud

00:04:43.401 --> 00:04:43.721
is

00:04:43.766 --> 00:04:44.036
either

00:04:44.094 --> 00:04:44.674
completely

00:04:44.780 --> 00:04:44.992
or

00:04:45.056 --> 00:04:45.632
partially

00:04:45.738 --> 00:04:46.589
unencrypted

00:04:47.213 --> 00:04:47.469
only

00:04:47.669 --> 00:04:47.869
11

00:04:48.215 --> 00:04:48.267
of

00:04:48.329 --> 00:04:49.135
organisations

00:04:49.175 --> 00:04:49.295
can

00:04:49.355 --> 00:04:49.535
say

00:04:49.567 --> 00:04:49.695
that

00:04:49.748 --> 00:04:49.854
at

00:04:49.920 --> 00:04:50.250
least

00:04:50.410 --> 00:04:51.050
81

00:04:51.476 --> 00:04:51.528
of

00:04:51.554 --> 00:04:51.684
their

00:04:51.780 --> 00:04:52.164
data

00:04:52.270 --> 00:04:52.482
is

00:04:52.546 --> 00:04:53.122
encrypted

00:04:53.362 --> 00:04:54.002
When

00:04:54.062 --> 00:04:54.560
encrypting

00:04:54.656 --> 00:04:55.040
data

00:04:55.546 --> 00:04:55.678
it’s

00:04:55.742 --> 00:04:55.998
also

00:04:56.054 --> 00:04:56.558
important

00:04:56.611 --> 00:04:56.717
to

00:04:56.785 --> 00:04:57.193
ensure

00:04:57.225 --> 00:04:57.353
that

00:04:57.373 --> 00:04:57.433
the

00:04:57.491 --> 00:04:58.071
encryption

00:04:58.128 --> 00:04:58.470
method

00:04:58.582 --> 00:04:59.030
used

00:04:59.140 --> 00:04:59.910
matches

00:04:59.950 --> 00:05:00.070
the

00:05:00.136 --> 00:05:00.862
sensitivity

00:05:00.888 --> 00:05:00.940
of

00:05:00.960 --> 00:05:01.020
the

00:05:01.100 --> 00:05:01.420
data

00:05:01.766 --> 00:05:02.696
Based

00:05:02.749 --> 00:05:02.855
on

00:05:02.895 --> 00:05:03.015
our

00:05:03.080 --> 00:05:03.730
experience

00:05:04.230 --> 00:05:04.290
the

00:05:04.340 --> 00:05:04.690
default

00:05:04.748 --> 00:05:05.328
assumption

00:05:05.408 --> 00:05:05.568
is

00:05:05.600 --> 00:05:05.728
that

00:05:05.828 --> 00:05:06.128
all

00:05:06.192 --> 00:05:06.448
data

00:05:06.501 --> 00:05:06.607
is

00:05:06.663 --> 00:05:07.167
encrypted

00:05:07.220 --> 00:05:07.326
at

00:05:07.438 --> 00:05:07.886
rest

00:05:08.046 --> 00:05:08.366
as

00:05:08.398 --> 00:05:08.526
well

00:05:08.579 --> 00:05:08.685
as

00:05:08.738 --> 00:05:08.844
in

00:05:08.914 --> 00:05:09.404
transit

00:05:09.617 --> 00:05:10.043
in

00:05:10.107 --> 00:05:10.363
both

00:05:10.443 --> 00:05:11.083
external

00:05:11.223 --> 00:05:11.643
and

00:05:11.705 --> 00:05:12.201
internal

00:05:12.281 --> 00:05:12.921
networks

00:05:13.561 --> 00:05:13.881
At

00:05:13.921 --> 00:05:14.041
the

00:05:14.089 --> 00:05:14.281
same

00:05:14.377 --> 00:05:14.761
time

00:05:15.257 --> 00:05:15.321
when

00:05:15.347 --> 00:05:15.399
it

00:05:15.452 --> 00:05:15.717
comes

00:05:15.770 --> 00:05:15.876
to

00:05:15.933 --> 00:05:16.275
highly

00:05:16.331 --> 00:05:16.835
sensitive

00:05:16.915 --> 00:05:17.235
data

00:05:17.821 --> 00:05:17.873
it

00:05:17.926 --> 00:05:18.032
is

00:05:18.072 --> 00:05:18.272
worth

00:05:18.325 --> 00:05:18.908
considering

00:05:18.928 --> 00:05:18.988
the

00:05:19.068 --> 00:05:19.308
new

00:05:19.388 --> 00:05:19.948
options

00:05:19.996 --> 00:05:20.428
available

00:05:20.481 --> 00:05:20.587
in

00:05:20.653 --> 00:05:20.983
cloud

00:05:21.054 --> 00:05:21.622
services

00:05:21.926 --> 00:05:22.502
such

00:05:22.555 --> 00:05:22.661
as

00:05:22.716 --> 00:05:23.376
confidential

00:05:23.432 --> 00:05:23.936
computing

00:05:24.442 --> 00:05:24.572
which

00:05:24.629 --> 00:05:24.971
allows

00:05:25.043 --> 00:05:25.763
processing

00:05:25.869 --> 00:05:26.081
in

00:05:26.201 --> 00:05:26.561
use

00:05:26.633 --> 00:05:27.281
encrypted

00:05:27.361 --> 00:05:27.681
data

00:05:28.027 --> 00:05:28.559
If

00:05:28.579 --> 00:05:28.639
the

00:05:28.696 --> 00:05:29.038
client

00:05:29.091 --> 00:05:29.197
is

00:05:29.261 --> 00:05:29.517
also

00:05:29.570 --> 00:05:29.676
in

00:05:29.721 --> 00:05:29.991
charge

00:05:30.017 --> 00:05:30.069
of

00:05:30.122 --> 00:05:30.546
managing

00:05:30.586 --> 00:05:30.786
their

00:05:30.866 --> 00:05:31.106
own

00:05:31.163 --> 00:05:31.904
cryptographic

00:05:32.016 --> 00:05:32.464
keys

00:05:33.136 --> 00:05:33.264
then

00:05:33.296 --> 00:05:33.424
that

00:05:33.477 --> 00:05:33.742
helps

00:05:33.768 --> 00:05:33.820
to

00:05:33.888 --> 00:05:34.296
ensure

00:05:34.328 --> 00:05:34.456
that

00:05:34.536 --> 00:05:34.856
only

00:05:34.936 --> 00:05:35.256
they

00:05:35.320 --> 00:05:35.576
know

00:05:35.636 --> 00:05:35.816
the

00:05:35.873 --> 00:05:36.215
actual

00:05:36.295 --> 00:05:36.855
content

00:05:36.881 --> 00:05:36.933
of

00:05:36.959 --> 00:05:37.089
their

00:05:37.169 --> 00:05:37.489
data

00:05:37.595 --> 00:05:38.125
being

00:05:38.189 --> 00:05:38.765
processed

00:05:38.818 --> 00:05:38.924
in

00:05:38.944 --> 00:05:39.004
the

00:05:39.097 --> 00:05:39.562
cloud

00:05:39.562 --> 00:05:39.640
The

00:05:39.720 --> 00:05:40.040
Zero

00:05:40.106 --> 00:05:40.436
Trust

00:05:40.502 --> 00:05:40.832
model

00:05:40.912 --> 00:05:41.072
is

00:05:41.122 --> 00:05:41.472
already

00:05:41.525 --> 00:05:41.790
being

00:05:41.870 --> 00:05:42.190
used

00:05:42.270 --> 00:05:42.430
by

00:05:42.510 --> 00:05:42.590
a

00:05:42.656 --> 00:05:42.986
third

00:05:43.546 --> 00:05:44.106
29

00:05:44.612 --> 00:05:44.664
of

00:05:44.726 --> 00:05:45.532
organisations

00:05:46.092 --> 00:05:46.652
27

00:05:47.112 --> 00:05:47.292
are

00:05:47.345 --> 00:05:47.769
planning

00:05:47.822 --> 00:05:47.928
to

00:05:47.976 --> 00:05:48.408
implement

00:05:48.461 --> 00:05:48.567
it

00:05:49.127 --> 00:05:49.687
23

00:05:50.067 --> 00:05:50.247
are

00:05:50.300 --> 00:05:50.724
thinking

00:05:50.764 --> 00:05:50.964
about

00:05:51.013 --> 00:05:51.601
implementing

00:05:51.654 --> 00:05:51.760
it

00:05:52.280 --> 00:05:52.400
and

00:05:52.560 --> 00:05:52.960
20

00:05:53.472 --> 00:05:53.920
have

00:05:54.026 --> 00:05:54.238
no

00:05:54.344 --> 00:05:54.874
plans

00:05:54.934 --> 00:05:55.114
for

00:05:55.180 --> 00:05:55.510
using

00:05:55.590 --> 00:05:55.750
it

00:05:56.230 --> 00:05:56.470
yet

00:05:56.727 --> 00:05:57.503
Compared

00:05:57.556 --> 00:05:57.662
to

00:05:57.726 --> 00:05:57.982
last

00:05:58.014 --> 00:05:58.142
year

00:05:58.275 --> 00:05:58.461
it’s

00:05:58.504 --> 00:05:58.934
definitely

00:05:59.014 --> 00:05:59.094
a

00:05:59.147 --> 00:05:59.571
positive

00:05:59.624 --> 00:06:00.207
development

00:06:00.807 --> 00:06:00.927
but

00:06:00.953 --> 00:06:01.083
about

00:06:01.163 --> 00:06:01.243
a

00:06:01.283 --> 00:06:01.483
fifth

00:06:01.536 --> 00:06:01.642
of

00:06:01.690 --> 00:06:02.122
companies

00:06:02.162 --> 00:06:02.282
who

00:06:02.342 --> 00:06:02.522
use

00:06:02.588 --> 00:06:02.918
cloud

00:06:02.982 --> 00:06:03.558
solutions

00:06:03.658 --> 00:06:03.958
are

00:06:04.011 --> 00:06:04.276
still

00:06:04.326 --> 00:06:04.676
without

00:06:04.736 --> 00:06:04.916
any

00:06:04.996 --> 00:06:05.316
kind

00:06:05.342 --> 00:06:05.394
of

00:06:05.490 --> 00:06:05.874
Zero

00:06:05.954 --> 00:06:06.354
Trust

00:06:06.434 --> 00:06:06.834
model

00:06:07.054 --> 00:06:08.034
Another

00:06:08.078 --> 00:06:08.430
positive

00:06:08.476 --> 00:06:08.982
development

00:06:09.142 --> 00:06:09.462
is

00:06:09.510 --> 00:06:09.702
that

00:06:09.766 --> 00:06:10.022
more

00:06:10.084 --> 00:06:10.890
organisations

00:06:10.922 --> 00:06:11.050
than

00:06:11.114 --> 00:06:11.370
ever

00:06:11.461 --> 00:06:12.007
before

00:06:12.107 --> 00:06:12.407
are

00:06:12.467 --> 00:06:12.806
basing

00:06:12.832 --> 00:06:12.962
their

00:06:13.028 --> 00:06:13.358
cloud

00:06:13.411 --> 00:06:13.835
security

00:06:13.900 --> 00:06:14.550
strategies

00:06:14.630 --> 00:06:15.110
either

00:06:15.182 --> 00:06:15.830
partially

00:06:16.230 --> 00:06:16.870
47

00:06:17.590 --> 00:06:18.070
or

00:06:18.180 --> 00:06:18.950
largely

00:06:19.270 --> 00:06:19.830
34

00:06:20.710 --> 00:06:20.870
on

00:06:20.950 --> 00:06:21.270
Zero

00:06:21.363 --> 00:06:21.828
Trust

00:06:22.468 --> 00:06:22.948
Strong

00:06:23.006 --> 00:06:23.818
authentication

00:06:23.898 --> 00:06:24.058
is

00:06:24.084 --> 00:06:24.136
an

00:06:24.184 --> 00:06:24.616
important

00:06:24.712 --> 00:06:25.096
part

00:06:25.122 --> 00:06:25.174
of

00:06:25.214 --> 00:06:25.334
the

00:06:25.414 --> 00:06:25.734
Zero

00:06:25.814 --> 00:06:26.214
Trust

00:06:26.294 --> 00:06:26.694
model

00:06:26.822 --> 00:06:27.334
with

00:06:27.374 --> 00:06:27.414
a

00:06:27.460 --> 00:06:27.966
development

00:06:28.019 --> 00:06:28.125
in

00:06:28.157 --> 00:06:28.285
that

00:06:28.349 --> 00:06:28.605
area

00:06:28.685 --> 00:06:28.845
as

00:06:28.925 --> 00:06:29.245
well

00:06:29.930 --> 00:06:30.200
nearly

00:06:30.280 --> 00:06:30.600
half

00:06:30.653 --> 00:06:30.759
of

00:06:30.839 --> 00:06:31.079
all

00:06:31.139 --> 00:06:31.799
respondents

00:06:31.927 --> 00:06:32.439
said

00:06:32.455 --> 00:06:32.519
that

00:06:32.572 --> 00:06:32.678
it

00:06:32.731 --> 00:06:32.996
plays

00:06:33.036 --> 00:06:33.076
a

00:06:33.156 --> 00:06:33.396
key

00:06:33.476 --> 00:06:33.796
role

00:06:33.876 --> 00:06:34.036
in

00:06:34.116 --> 00:06:34.436
Zero

00:06:34.516 --> 00:06:34.916
Trust

00:06:35.169 --> 00:06:36.034
Still

00:06:36.540 --> 00:06:36.592
it

00:06:36.632 --> 00:06:36.912
doesn’t

00:06:36.960 --> 00:06:37.152
mean

00:06:37.200 --> 00:06:37.392
that

00:06:37.449 --> 00:06:37.791
modern

00:06:37.844 --> 00:06:38.586
authentication

00:06:38.650 --> 00:06:39.226
solutions

00:06:39.266 --> 00:06:39.626
haven’t

00:06:39.666 --> 00:06:39.946
already

00:06:39.994 --> 00:06:40.186
been

00:06:40.232 --> 00:06:40.738
implemented

00:06:40.791 --> 00:06:40.897
in

00:06:40.917 --> 00:06:40.977
the

00:06:41.057 --> 00:06:41.457
cloud

00:06:41.857 --> 00:06:42.817
Zero

00:06:42.923 --> 00:06:43.453
Trust

00:06:43.510 --> 00:06:43.852
should

00:06:43.868 --> 00:06:43.932
have

00:06:43.964 --> 00:06:44.092
been

00:06:44.150 --> 00:06:44.730
integrated

00:06:44.778 --> 00:06:44.970
into

00:06:45.010 --> 00:06:45.130
the

00:06:45.290 --> 00:06:45.770
DNA

00:06:45.796 --> 00:06:45.848
of

00:06:45.928 --> 00:06:46.168
all

00:06:46.381 --> 00:06:46.807
IT

00:06:46.857 --> 00:06:47.207
related

00:06:47.257 --> 00:06:47.757
activities

00:06:47.877 --> 00:06:47.997
a

00:06:48.061 --> 00:06:48.317
long

00:06:48.381 --> 00:06:48.637
time

00:06:48.737 --> 00:06:49.037
ago

00:06:49.357 --> 00:06:49.837
It

00:06:49.917 --> 00:06:50.077
is

00:06:50.127 --> 00:06:50.477
equally

00:06:50.533 --> 00:06:51.037
important

00:06:51.090 --> 00:06:51.196
in

00:06:51.260 --> 00:06:51.516
both

00:06:51.536 --> 00:06:51.596
the

00:06:51.702 --> 00:06:52.232
cloud

00:06:52.338 --> 00:06:52.550
as

00:06:52.598 --> 00:06:52.790
well

00:06:52.843 --> 00:06:52.949
as

00:06:52.975 --> 00:06:53.027
in

00:06:53.059 --> 00:06:53.187
your

00:06:53.240 --> 00:06:53.664
building

00:06:54.250 --> 00:06:54.302
on

00:06:54.334 --> 00:06:54.462
your

00:06:54.518 --> 00:06:55.102
employees’

00:06:55.182 --> 00:06:55.742
devices

00:06:55.922 --> 00:06:56.222
and

00:06:56.282 --> 00:06:56.462
all

00:06:56.482 --> 00:06:56.542
the

00:06:56.613 --> 00:06:57.181
networks

00:06:57.581 --> 00:06:58.058
including

00:06:58.090 --> 00:06:58.218
your

00:06:58.280 --> 00:06:58.776
internal

00:06:58.836 --> 00:06:59.256
network

00:06:59.768 --> 00:06:59.896
that

00:06:59.912 --> 00:06:59.976
your

00:07:00.040 --> 00:07:00.616
employees

00:07:00.736 --> 00:07:01.096
use

00:07:01.149 --> 00:07:01.255
to

00:07:01.303 --> 00:07:01.495
move

00:07:01.555 --> 00:07:01.975
company

00:07:02.055 --> 00:07:02.375
data

00:07:02.711 --> 00:07:03.415
That

00:07:03.468 --> 00:07:03.574
is

00:07:03.654 --> 00:07:03.894
why

00:07:03.974 --> 00:07:04.294
over

00:07:04.334 --> 00:07:04.374
a

00:07:04.422 --> 00:07:04.614
year

00:07:04.714 --> 00:07:05.014
ago

00:07:05.467 --> 00:07:05.573
we

00:07:05.619 --> 00:07:06.125
implemented

00:07:06.205 --> 00:07:06.285
a

00:07:06.347 --> 00:07:06.843
complete

00:07:06.939 --> 00:07:07.323
Zero

00:07:07.403 --> 00:07:07.803
Trust

00:07:07.869 --> 00:07:08.199
model

00:07:08.385 --> 00:07:08.757
at

00:07:08.957 --> 00:07:09.557
ADM

00:07:09.663 --> 00:07:10.513
Cloudtech

00:07:10.813 --> 00:07:11.473
The

00:07:11.513 --> 00:07:11.713
model

00:07:11.775 --> 00:07:12.271
includes

00:07:12.331 --> 00:07:12.511
our

00:07:12.564 --> 00:07:12.829
whole

00:07:13.015 --> 00:07:13.387
IT

00:07:13.445 --> 00:07:14.257
infrastructure

00:07:14.337 --> 00:07:14.657
with

00:07:14.737 --> 00:07:14.897
no

00:07:14.969 --> 00:07:15.689
exceptions

00:07:15.849 --> 00:07:16.329
and

00:07:16.382 --> 00:07:16.806
provides

00:07:16.886 --> 00:07:17.046
us

00:07:17.078 --> 00:07:17.206
with

00:07:17.246 --> 00:07:17.366
the

00:07:17.414 --> 00:07:17.846
certainty

00:07:17.878 --> 00:07:18.006
that

00:07:18.059 --> 00:07:18.165
in

00:07:18.185 --> 00:07:18.245
the

00:07:18.309 --> 00:07:18.565
case

00:07:18.618 --> 00:07:18.724
of

00:07:18.750 --> 00:07:18.802
an

00:07:18.870 --> 00:07:19.278
attack

00:07:19.978 --> 00:07:20.158
our

00:07:20.238 --> 00:07:20.478
job

00:07:20.531 --> 00:07:20.637
is

00:07:20.717 --> 00:07:20.957
not

00:07:21.010 --> 00:07:21.593
interrupted

00:07:21.646 --> 00:07:21.911
since

00:07:21.951 --> 00:07:22.071
the

00:07:22.124 --> 00:07:22.389
reach

00:07:22.442 --> 00:07:22.548
of

00:07:22.608 --> 00:07:22.788
any

00:07:22.868 --> 00:07:23.348
attack

00:07:23.380 --> 00:07:23.508
will

00:07:23.561 --> 00:07:23.667
be

00:07:23.729 --> 00:07:24.225
strongly

00:07:24.285 --> 00:07:24.705
limited

00:07:25.105 --> 00:07:25.585
In

00:07:25.605 --> 00:07:25.665
the

00:07:25.713 --> 00:07:25.905
name

00:07:25.958 --> 00:07:26.064
of

00:07:26.109 --> 00:07:26.379
better

00:07:26.450 --> 00:07:27.018
security

00:07:27.578 --> 00:07:27.818
all

00:07:27.892 --> 00:07:28.854
organisations

00:07:28.899 --> 00:07:29.169
should

00:07:29.201 --> 00:07:29.329
make

00:07:29.369 --> 00:07:29.569
their

00:07:29.640 --> 00:07:30.208
security

00:07:30.274 --> 00:07:31.084
infrastructures

00:07:31.164 --> 00:07:31.484
more

00:07:31.540 --> 00:07:32.044
efficient

00:07:32.812 --> 00:07:33.244
implement

00:07:33.284 --> 00:07:33.404
the

00:07:33.484 --> 00:07:33.804
Zero

00:07:33.884 --> 00:07:34.284
Trust

00:07:34.350 --> 00:07:34.680
model

00:07:34.820 --> 00:07:35.240
and

00:07:35.308 --> 00:07:35.716
modern

00:07:35.774 --> 00:07:36.586
authentication

00:07:36.658 --> 00:07:37.306
solutions

00:07:37.626 --> 00:07:38.106
and

00:07:38.159 --> 00:07:38.424
train

00:07:38.450 --> 00:07:38.580
their

00:07:38.636 --> 00:07:39.140
employees

00:07:39.193 --> 00:07:39.299
to

00:07:39.352 --> 00:07:39.458
be

00:07:39.522 --> 00:07:39.778
well

00:07:39.858 --> 00:07:40.338
versed

00:07:40.418 --> 00:07:40.578
in

00:07:40.658 --> 00:07:41.298
security

00:07:41.618 --> 00:07:42.258
This

00:07:42.298 --> 00:07:42.658
doesn’t

00:07:42.690 --> 00:07:42.818
come

00:07:42.898 --> 00:07:43.298
cheap

00:07:43.438 --> 00:07:43.858
and

00:07:43.898 --> 00:07:44.098
isn’t

00:07:44.143 --> 00:07:44.413
always

00:07:44.461 --> 00:07:44.653
very

00:07:44.749 --> 00:07:45.133
easy

00:07:45.893 --> 00:07:46.013
but

00:07:46.039 --> 00:07:46.091
it

00:07:46.144 --> 00:07:46.250
is

00:07:46.314 --> 00:07:46.890
extremely

00:07:46.946 --> 00:07:47.450
important

00:07:47.503 --> 00:07:47.609
to

00:07:47.677 --> 00:07:48.085
ensure

00:07:48.105 --> 00:07:48.165
the

00:07:48.229 --> 00:07:49.125
sustainability

00:07:49.205 --> 00:07:49.365
of

00:07:49.425 --> 00:07:49.605
any

00:07:49.678 --> 00:07:50.554
organisation

00:07:50.772 --> 00:07:52.152
Conclusion

00:07:52.338 --> 00:07:53.268
Multi

00:07:53.334 --> 00:07:53.664
cloud

00:07:53.744 --> 00:07:53.904
is

00:07:53.944 --> 00:07:54.064
the

00:07:54.124 --> 00:07:54.544
present

00:07:54.644 --> 00:07:54.944
and

00:07:55.012 --> 00:07:55.420
future

00:07:55.473 --> 00:07:55.579
of

00:07:55.632 --> 00:07:55.897
cloud

00:07:55.955 --> 00:07:56.535
technology

00:07:56.847 --> 00:07:57.495
something

00:07:57.527 --> 00:07:57.655
that

00:07:57.703 --> 00:07:58.135
companies

00:07:58.199 --> 00:07:58.455
must

00:07:58.495 --> 00:07:58.775
account

00:07:58.855 --> 00:07:59.095
for

00:07:59.201 --> 00:07:59.413
by

00:07:59.456 --> 00:07:59.972
implementing

00:08:00.028 --> 00:08:00.532
efficient

00:08:00.594 --> 00:08:01.090
security

00:08:01.162 --> 00:08:01.810
solutions

00:08:02.170 --> 00:08:02.770
The

00:08:02.827 --> 00:08:03.169
rising

00:08:03.227 --> 00:08:03.807
importance

00:08:03.860 --> 00:08:03.966
of

00:08:04.046 --> 00:08:04.526
remote

00:08:04.566 --> 00:08:04.686
and

00:08:04.766 --> 00:08:05.246
hybrid

00:08:05.326 --> 00:08:05.646
work

00:08:05.859 --> 00:08:06.285
as

00:08:06.317 --> 00:08:06.445
well

00:08:06.498 --> 00:08:06.604
as

00:08:06.664 --> 00:08:07.084
digital

00:08:07.137 --> 00:08:07.561
channels

00:08:07.614 --> 00:08:07.720
in

00:08:07.760 --> 00:08:07.880
how

00:08:07.944 --> 00:08:08.520
companies

00:08:08.610 --> 00:08:09.240
operate

00:08:09.368 --> 00:08:09.880
does

00:08:09.940 --> 00:08:10.120
not

00:08:10.184 --> 00:08:10.440
make

00:08:10.472 --> 00:08:10.600
this

00:08:10.696 --> 00:08:11.080
task

00:08:11.160 --> 00:08:11.640
easier

00:08:12.066 --> 00:08:12.758
As

00:08:12.798 --> 00:08:12.998
multi

00:08:13.064 --> 00:08:13.394
cloud

00:08:13.454 --> 00:08:13.874
becomes

00:08:13.922 --> 00:08:14.114
more

00:08:14.170 --> 00:08:14.674
prevalent

00:08:15.127 --> 00:08:15.233
it

00:08:15.313 --> 00:08:15.869
enforces

00:08:15.909 --> 00:08:16.029
the

00:08:16.093 --> 00:08:16.349
need

00:08:16.375 --> 00:08:16.427
to

00:08:16.492 --> 00:08:17.142
constantly

00:08:17.232 --> 00:08:17.862
improve

00:08:17.912 --> 00:08:18.262
current

00:08:18.324 --> 00:08:18.820
security

00:08:18.908 --> 00:08:19.700
solutions

00:08:19.840 --> 00:08:20.260
and

00:08:20.313 --> 00:08:20.419
to

00:08:20.469 --> 00:08:20.819
develop

00:08:20.879 --> 00:08:21.059
new

00:08:21.152 --> 00:08:21.617
tools

00:08:21.729 --> 00:08:22.177
that

00:08:22.225 --> 00:08:22.417
help

00:08:22.443 --> 00:08:22.495
to

00:08:22.555 --> 00:08:22.975
protect

00:08:23.035 --> 00:08:23.455
various

00:08:23.516 --> 00:08:24.248
environments

00:08:24.314 --> 00:08:25.040
efficiently