WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:05.180 align:start position:0% I<00:00:02.419> always<00:00:03.419> try<00:00:03.570> to<00:00:03.629> keep<00:00:03.870> on<00:00:04.020> top<00:00:04.200> of<00:00:04.259> the 00:00:05.180 --> 00:00:05.190 align:start position:0% I always try to keep on top of the 00:00:05.190 --> 00:00:08.360 align:start position:0% I always try to keep on top of the latest<00:00:05.520> technology<00:00:06.299> trends<00:00:06.930> and<00:00:07.350> threats<00:00:08.099> are 00:00:08.360 --> 00:00:08.370 align:start position:0% latest technology trends and threats are 00:00:08.370 --> 00:00:12.350 align:start position:0% latest technology trends and threats are a<00:00:08.460> really<00:00:09.059> big<00:00:09.300> part<00:00:09.690> of<00:00:10.070> tech<00:00:11.070> because<00:00:11.880> I<00:00:12.150> need 00:00:12.350 --> 00:00:12.360 align:start position:0% a really big part of tech because I need 00:00:12.360 --> 00:00:14.089 align:start position:0% a really big part of tech because I need to<00:00:12.389> protect<00:00:12.780> myself<00:00:12.990> I<00:00:13.380> need<00:00:13.530> to<00:00:13.620> protect<00:00:13.920> my 00:00:14.089 --> 00:00:14.099 align:start position:0% to protect myself I need to protect my 00:00:14.099 --> 00:00:16.939 align:start position:0% to protect myself I need to protect my customers<00:00:14.639> and<00:00:14.849> I<00:00:15.030> need<00:00:15.540> to<00:00:15.690> be<00:00:15.949> responsible 00:00:16.939 --> 00:00:16.949 align:start position:0% customers and I need to be responsible 00:00:16.949 --> 00:00:20.450 align:start position:0% customers and I need to be responsible to<00:00:17.070> you<00:00:17.400> my<00:00:17.609> viewers<00:00:18.090> and<00:00:18.359> and<00:00:19.260> help<00:00:19.770> you<00:00:20.039> to<00:00:20.279> be 00:00:20.450 --> 00:00:20.460 align:start position:0% to you my viewers and and help you to be 00:00:20.460 --> 00:00:22.700 align:start position:0% to you my viewers and and help you to be ready<00:00:20.820> and<00:00:21.240> prepared<00:00:21.869> for<00:00:21.960> the<00:00:22.230> threats<00:00:22.560> that 00:00:22.700 --> 00:00:22.710 align:start position:0% ready and prepared for the threats that 00:00:22.710 --> 00:00:26.509 align:start position:0% ready and prepared for the threats that are<00:00:22.920> coming<00:00:23.279> over<00:00:23.939> the<00:00:24.060> horizon<00:00:24.210> here<00:00:25.170> as<00:00:25.519> you 00:00:26.509 --> 00:00:26.519 align:start position:0% are coming over the horizon here as you 00:00:26.519 --> 00:00:28.730 align:start position:0% are coming over the horizon here as you know<00:00:26.609> here<00:00:27.060> the<00:00:27.539> first<00:00:27.810> month<00:00:28.050> of<00:00:28.170> January 00:00:28.730 --> 00:00:28.740 align:start position:0% know here the first month of January 00:00:28.740 --> 00:00:31.550 align:start position:0% know here the first month of January starts<00:00:29.369> to<00:00:29.490> wrap<00:00:29.699> up<00:00:30.050> the<00:00:31.050> first<00:00:31.080> month<00:00:31.470> of 00:00:31.550 --> 00:00:31.560 align:start position:0% starts to wrap up the first month of 00:00:31.560 --> 00:00:34.459 align:start position:0% starts to wrap up the first month of 2020<00:00:32.189> I<00:00:32.219> should<00:00:32.489> say<00:00:32.640> January<00:00:33.059> being<00:00:33.630> that<00:00:34.230> my 00:00:34.459 --> 00:00:34.469 align:start position:0% 2020 I should say January being that my 00:00:34.469 --> 00:00:35.060 align:start position:0% 2020 I should say January being that my first<00:00:34.680> month 00:00:35.060 --> 00:00:35.070 align:start position:0% first month 00:00:35.070 --> 00:00:38.900 align:start position:0% first month yes<00:00:35.630> you're<00:00:36.630> saying<00:00:36.840> you<00:00:37.290> knew<00:00:37.649> what<00:00:38.010> I<00:00:38.040> meant 00:00:38.900 --> 00:00:38.910 align:start position:0% yes you're saying you knew what I meant 00:00:38.910 --> 00:00:41.330 align:start position:0% yes you're saying you knew what I meant January<00:00:39.690> does<00:00:39.899> feel<00:00:40.140> very<00:00:40.170> long<00:00:40.649> though<00:00:40.890> but 00:00:41.330 --> 00:00:41.340 align:start position:0% January does feel very long though but 00:00:41.340 --> 00:00:43.670 align:start position:0% January does feel very long though but we're<00:00:42.000> really<00:00:42.270> it<00:00:42.780> does<00:00:43.020> and<00:00:43.410> when<00:00:43.559> we're 00:00:43.670 --> 00:00:43.680 align:start position:0% we're really it does and when we're 00:00:43.680 --> 00:00:45.799 align:start position:0% we're really it does and when we're seeing<00:00:43.860> an<00:00:44.129> evolution<00:00:44.280> in<00:00:44.910> malware<00:00:45.600> we're 00:00:45.799 --> 00:00:45.809 align:start position:0% seeing an evolution in malware we're 00:00:45.809 --> 00:00:49.250 align:start position:0% seeing an evolution in malware we're seeing<00:00:46.079> things<00:00:46.890> transition<00:00:47.610> from<00:00:47.850> viruses<00:00:48.390> to 00:00:49.250 --> 00:00:49.260 align:start position:0% seeing things transition from viruses to 00:00:49.260 --> 00:00:53.420 align:start position:0% seeing things transition from viruses to malware<00:00:49.550> to<00:00:50.550> ransomware<00:00:51.059> and<00:00:51.480> now<00:00:52.020> even<00:00:52.980> file 00:00:53.420 --> 00:00:53.430 align:start position:0% malware to ransomware and now even file 00:00:53.430 --> 00:00:55.970 align:start position:0% malware to ransomware and now even file this<00:00:53.699> attacks<00:00:54.120> we're<00:00:55.050> seeing<00:00:55.320> Hardware 00:00:55.970 --> 00:00:55.980 align:start position:0% this attacks we're seeing Hardware 00:00:55.980 --> 00:00:59.209 align:start position:0% this attacks we're seeing Hardware attacks<00:00:56.399> and<00:00:56.730> firmware<00:00:57.559> infiltrations<00:00:58.559> and 00:00:59.209 --> 00:00:59.219 align:start position:0% attacks and firmware infiltrations and 00:00:59.219 --> 00:01:01.400 align:start position:0% attacks and firmware infiltrations and things<00:01:00.059> that<00:01:00.180> we've<00:01:00.390> never<00:01:00.719> ever<00:01:00.899> even 00:01:01.400 --> 00:01:01.410 align:start position:0% things that we've never ever even 00:01:01.410 --> 00:01:03.349 align:start position:0% things that we've never ever even encountered<00:01:01.739> before<00:01:02.399> but<00:01:02.579> those<00:01:02.730> are<00:01:02.879> very 00:01:03.349 --> 00:01:03.359 align:start position:0% encountered before but those are very 00:01:03.359 --> 00:01:06.890 align:start position:0% encountered before but those are very real<00:01:03.690> threats<00:01:04.110> here<00:01:04.470> as<00:01:04.589> we<00:01:05.159> enter<00:01:05.430> 2020<00:01:06.150> so 00:01:06.890 --> 00:01:06.900 align:start position:0% real threats here as we enter 2020 so 00:01:06.900 --> 00:01:09.320 align:start position:0% real threats here as we enter 2020 so the<00:01:07.229> opportunity<00:01:07.890> arose<00:01:08.220> and<00:01:08.760> I<00:01:08.939> spent<00:01:09.210> some 00:01:09.320 --> 00:01:09.330 align:start position:0% the opportunity arose and I spent some 00:01:09.330 --> 00:01:11.149 align:start position:0% the opportunity arose and I spent some time<00:01:09.390> there<00:01:09.600> I<00:01:10.110> want<00:01:10.380> to<00:01:10.439> jump<00:01:10.710> into<00:01:11.040> an 00:01:11.149 --> 00:01:11.159 align:start position:0% time there I want to jump into an 00:01:11.159 --> 00:01:15.679 align:start position:0% time there I want to jump into an interview<00:01:11.720> with<00:01:12.720> Raph<00:01:13.439> bovar<00:01:14.030> at<00:01:15.030> ESET 00:01:15.679 --> 00:01:15.689 align:start position:0% interview with Raph bovar at ESET 00:01:15.689 --> 00:01:19.760 align:start position:0% interview with Raph bovar at ESET headquarters<00:01:16.560> in<00:01:16.770> Toronto<00:01:17.670> Ontario<00:01:18.770> hey 00:01:19.760 --> 00:01:19.770 align:start position:0% headquarters in Toronto Ontario hey 00:01:19.770 --> 00:01:20.240 align:start position:0% headquarters in Toronto Ontario hey sorry<00:01:20.040> man 00:01:20.240 --> 00:01:20.250 align:start position:0% sorry man 00:01:20.250 --> 00:01:21.410 align:start position:0% sorry man thanks<00:01:20.549> for<00:01:20.640> being<00:01:20.729> here<00:01:20.820> thanks<00:01:21.299> for<00:01:21.330> having 00:01:21.410 --> 00:01:21.420 align:start position:0% thanks for being here thanks for having 00:01:21.420 --> 00:01:24.050 align:start position:0% thanks for being here thanks for having a<00:01:21.780> heavy<00:01:21.960> well<00:01:22.170> thanks<00:01:22.439> can<00:01:23.400> you<00:01:23.490> tell<00:01:23.670> the 00:01:24.050 --> 00:01:24.060 align:start position:0% a heavy well thanks can you tell the 00:01:24.060 --> 00:01:25.340 align:start position:0% a heavy well thanks can you tell the folks<00:01:24.090> who<00:01:24.360> are<00:01:24.420> watching<00:01:24.570> a<00:01:25.020> little<00:01:25.200> bit 00:01:25.340 --> 00:01:25.350 align:start position:0% folks who are watching a little bit 00:01:25.350 --> 00:01:26.719 align:start position:0% folks who are watching a little bit about<00:01:25.500> what<00:01:25.710> you<00:01:25.830> do<00:01:25.979> here<00:01:26.280> at<00:01:26.460> ESET 00:01:26.719 --> 00:01:26.729 align:start position:0% about what you do here at ESET 00:01:26.729 --> 00:01:28.910 align:start position:0% about what you do here at ESET headquarters<00:01:27.270> so<00:01:27.810> Robbie<00:01:28.020> I<00:01:28.110> am<00:01:28.560> actually<00:01:28.740> the 00:01:28.910 --> 00:01:28.920 align:start position:0% headquarters so Robbie I am actually the 00:01:28.920 --> 00:01:31.910 align:start position:0% headquarters so Robbie I am actually the sibling<00:01:29.340> here<00:01:29.610> I<00:01:29.880> am<00:01:30.329> the<00:01:30.479> lead<00:01:30.650> engineer<00:01:31.650> for 00:01:31.910 --> 00:01:31.920 align:start position:0% sibling here I am the lead engineer for 00:01:31.920 --> 00:01:34.670 align:start position:0% sibling here I am the lead engineer for the<00:01:32.040> for<00:01:32.280> the<00:01:32.369> attack<00:01:32.729> team<00:01:32.939> in<00:01:33.090> Canada<00:01:33.420> and<00:01:33.680> I 00:01:34.670 --> 00:01:34.680 align:start position:0% the for the attack team in Canada and I 00:01:34.680 --> 00:01:37.190 align:start position:0% the for the attack team in Canada and I am<00:01:34.890> mostly<00:01:35.280> the<00:01:35.670> tech<00:01:35.970> guy<00:01:36.240> that<00:01:36.600> will<00:01:36.840> support 00:01:37.190 --> 00:01:37.200 align:start position:0% am mostly the tech guy that will support 00:01:37.200 --> 00:01:40.039 align:start position:0% am mostly the tech guy that will support sales<00:01:37.740> in<00:01:38.310> general<00:01:38.549> between<00:01:39.450> the<00:01:39.689> Canadian 00:01:40.039 --> 00:01:40.049 align:start position:0% sales in general between the Canadian 00:01:40.049 --> 00:01:41.780 align:start position:0% sales in general between the Canadian territory<00:01:40.170> so<00:01:40.799> a<00:01:40.829> very<00:01:41.009> technical<00:01:41.220> mind 00:01:41.780 --> 00:01:41.790 align:start position:0% territory so a very technical mind 00:01:41.790 --> 00:01:43.760 align:start position:0% territory so a very technical mind you're<00:01:42.750> very<00:01:42.960> familiar<00:01:43.110> with<00:01:43.409> the<00:01:43.619> inner 00:01:43.760 --> 00:01:43.770 align:start position:0% you're very familiar with the inner 00:01:43.770 --> 00:01:45.770 align:start position:0% you're very familiar with the inner workings<00:01:43.799> of<00:01:44.310> the<00:01:44.430> products<00:01:44.939> yep<00:01:45.149> I'm<00:01:45.390> doing 00:01:45.770 --> 00:01:45.780 align:start position:0% workings of the products yep I'm doing 00:01:45.780 --> 00:01:47.990 align:start position:0% workings of the products yep I'm doing that<00:01:45.960> has<00:01:46.140> all<00:01:46.380> the<00:01:46.619> geeky<00:01:47.159> talk<00:01:47.430> with<00:01:47.759> the 00:01:47.990 --> 00:01:48.000 align:start position:0% that has all the geeky talk with the 00:01:48.000 --> 00:01:50.539 align:start position:0% that has all the geeky talk with the other<00:01:48.119> text<00:01:48.600> and<00:01:48.720> other<00:01:48.780> customers<00:01:49.560> yeah<00:01:49.950> and 00:01:50.539 --> 00:01:50.549 align:start position:0% other text and other customers yeah and 00:01:50.549 --> 00:01:53.060 align:start position:0% other text and other customers yeah and the<00:01:51.329> main<00:01:51.659> driver<00:01:51.930> for<00:01:52.020> that<00:01:52.290> is<00:01:52.439> to<00:01:52.649> be<00:01:52.920> able 00:01:53.060 --> 00:01:53.070 align:start position:0% the main driver for that is to be able 00:01:53.070 --> 00:01:55.249 align:start position:0% the main driver for that is to be able to<00:01:53.280> technically<00:01:54.060> position<00:01:54.570> the<00:01:54.689> products<00:01:55.049> and 00:01:55.249 --> 00:01:55.259 align:start position:0% to technically position the products and 00:01:55.259 --> 00:01:56.959 align:start position:0% to technically position the products and see<00:01:55.439> if<00:01:55.710> we<00:01:55.829> can<00:01:56.040> address<00:01:56.189> all<00:01:56.520> the<00:01:56.640> customer 00:01:56.959 --> 00:01:56.969 align:start position:0% see if we can address all the customer 00:01:56.969 --> 00:01:57.469 align:start position:0% see if we can address all the customer requirements 00:01:57.469 --> 00:01:57.479 align:start position:0% requirements 00:01:57.479 --> 00:02:00.100 align:start position:0% requirements sure<00:01:57.930> so<00:01:58.500> part<00:01:58.770> of<00:01:58.799> that<00:01:58.860> comes<00:01:59.189> from 00:02:00.100 --> 00:02:00.110 align:start position:0% sure so part of that comes from 00:02:00.110 --> 00:02:03.950 align:start position:0% sure so part of that comes from educating<00:02:01.130> end-users<00:02:02.130> to<00:02:02.329> understand<00:02:03.329> what 00:02:03.950 --> 00:02:03.960 align:start position:0% educating end-users to understand what 00:02:03.960 --> 00:02:05.300 align:start position:0% educating end-users to understand what the<00:02:04.110> cyber<00:02:04.409> security<00:02:04.829> threat<00:02:05.100> landscape 00:02:05.300 --> 00:02:05.310 align:start position:0% the cyber security threat landscape 00:02:05.310 --> 00:02:07.280 align:start position:0% the cyber security threat landscape looks<00:02:05.820> like<00:02:06.090> absolutely<00:02:06.899> yeah<00:02:06.960> and<00:02:07.110> we've 00:02:07.280 --> 00:02:07.290 align:start position:0% looks like absolutely yeah and we've 00:02:07.290 --> 00:02:08.960 align:start position:0% looks like absolutely yeah and we've really<00:02:07.860> really<00:02:07.979> seen<00:02:08.190> that<00:02:08.369> change<00:02:08.399> over<00:02:08.910> the 00:02:08.960 --> 00:02:08.970 align:start position:0% really really seen that change over the 00:02:08.970 --> 00:02:10.089 align:start position:0% really really seen that change over the past<00:02:09.030> couple<00:02:09.300> of<00:02:09.390> years<00:02:09.479> I<00:02:09.690> think<00:02:09.720> especially 00:02:10.089 --> 00:02:10.099 align:start position:0% past couple of years I think especially 00:02:10.099 --> 00:02:12.280 align:start position:0% past couple of years I think especially was<00:02:11.099> it 00:02:12.280 --> 00:02:12.290 align:start position:0% was it 00:02:12.290 --> 00:02:15.470 align:start position:0% was it 2017<00:02:13.290> when<00:02:13.530> wanna<00:02:13.770> cry<00:02:14.070> dropped<00:02:14.240> yes<00:02:15.240> this<00:02:15.330> is 00:02:15.470 --> 00:02:15.480 align:start position:0% 2017 when wanna cry dropped yes this is 00:02:15.480 --> 00:02:18.500 align:start position:0% 2017 when wanna cry dropped yes this is like<00:02:15.570> the<00:02:15.720> first<00:02:16.310> ransomware<00:02:17.310> that<00:02:17.970> really 00:02:18.500 --> 00:02:18.510 align:start position:0% like the first ransomware that really 00:02:18.510 --> 00:02:20.180 align:start position:0% like the first ransomware that really made<00:02:18.690> its<00:02:18.840> way<00:02:18.990> around<00:02:19.140> the<00:02:19.320> world<00:02:19.470> and<00:02:20.010> was 00:02:20.180 --> 00:02:20.190 align:start position:0% made its way around the world and was 00:02:20.190 --> 00:02:23.630 align:start position:0% made its way around the world and was really<00:02:20.610> really<00:02:20.790> huge<00:02:21.030> how<00:02:21.870> did<00:02:22.080> that<00:02:22.640> impact 00:02:23.630 --> 00:02:23.640 align:start position:0% really really huge how did that impact 00:02:23.640 --> 00:02:25.610 align:start position:0% really really huge how did that impact the<00:02:23.970> direction<00:02:24.450> of<00:02:24.510> a<00:02:24.630> kind<00:02:24.840> like<00:02:24.930> you<00:02:25.170> said<00:02:25.380> we 00:02:25.610 --> 00:02:25.620 align:start position:0% the direction of a kind like you said we 00:02:25.620 --> 00:02:28.370 align:start position:0% the direction of a kind like you said we should<00:02:25.860> not<00:02:26.100> see<00:02:26.430> any<00:02:26.790> any<00:02:27.170> numbers<00:02:28.170> going 00:02:28.370 --> 00:02:28.380 align:start position:0% should not see any any numbers going 00:02:28.380 --> 00:02:30.140 align:start position:0% should not see any any numbers going down<00:02:28.500> whenever<00:02:29.190> it<00:02:29.370> comes<00:02:29.490> to<00:02:29.700> the<00:02:29.820> ransomware 00:02:30.140 --> 00:02:30.150 align:start position:0% down whenever it comes to the ransomware 00:02:30.150 --> 00:02:33.320 align:start position:0% down whenever it comes to the ransomware it's<00:02:30.510> still<00:02:30.870> the<00:02:31.080> the<00:02:31.290> really<00:02:31.890> prevalent<00:02:32.330> and 00:02:33.320 --> 00:02:33.330 align:start position:0% it's still the the really prevalent and 00:02:33.330 --> 00:02:35.690 align:start position:0% it's still the the really prevalent and and<00:02:33.720> everybody<00:02:34.620> in<00:02:34.770> a<00:02:34.830> way<00:02:35.010> is<00:02:35.250> kind<00:02:35.280> of 00:02:35.690 --> 00:02:35.700 align:start position:0% and everybody in a way is kind of 00:02:35.700 --> 00:02:38.990 align:start position:0% and everybody in a way is kind of experiencing<00:02:36.600> it<00:02:36.720> we<00:02:37.560> do<00:02:37.830> have<00:02:37.860> a<00:02:38.190> pretty<00:02:38.700> good 00:02:38.990 --> 00:02:39.000 align:start position:0% experiencing it we do have a pretty good 00:02:39.000 --> 00:02:41.720 align:start position:0% experiencing it we do have a pretty good protection<00:02:39.209> against<00:02:39.959> it<00:02:40.080> so<00:02:40.380> I<00:02:40.590> I<00:02:41.250> don't 00:02:41.720 --> 00:02:41.730 align:start position:0% protection against it so I I don't 00:02:41.730 --> 00:02:44.180 align:start position:0% protection against it so I I don't expect<00:02:42.450> my<00:02:42.690> existing<00:02:43.500> customers<00:02:43.890> that<00:02:44.070> are 00:02:44.180 --> 00:02:44.190 align:start position:0% expect my existing customers that are 00:02:44.190 --> 00:02:45.800 align:start position:0% expect my existing customers that are running<00:02:44.430> updated<00:02:44.970> products<00:02:45.390> and<00:02:45.480> everything 00:02:45.800 --> 00:02:45.810 align:start position:0% running updated products and everything 00:02:45.810 --> 00:02:49.610 align:start position:0% running updated products and everything from<00:02:46.739> being<00:02:47.010> acted<00:02:47.820> to<00:02:48.030> those<00:02:48.209> threats<00:02:48.989> but 00:02:49.610 --> 00:02:49.620 align:start position:0% from being acted to those threats but 00:02:49.620 --> 00:02:51.729 align:start position:0% from being acted to those threats but it's<00:02:49.739> something<00:02:49.950> that's<00:02:50.280> already<00:02:50.459> very<00:02:51.390> very 00:02:51.729 --> 00:02:51.739 align:start position:0% it's something that's already very very 00:02:51.739 --> 00:02:54.830 align:start position:0% it's something that's already very very live<00:02:52.739> very<00:02:53.190> very<00:02:53.520> present<00:02:53.850> in<00:02:54.180> our<00:02:54.330> day-to-day 00:02:54.830 --> 00:02:54.840 align:start position:0% live very very present in our day-to-day 00:02:54.840 --> 00:02:57.890 align:start position:0% live very very present in our day-to-day operations<00:02:56.390> something<00:02:57.390> else<00:02:57.630> that<00:02:57.780> right 00:02:57.890 --> 00:02:57.900 align:start position:0% operations something else that right 00:02:57.900 --> 00:03:00.229 align:start position:0% operations something else that right that<00:02:58.050> I<00:02:58.110> usually<00:02:58.680> highlight<00:02:59.100> on<00:02:59.730> the<00:02:59.940> on<00:03:00.090> the 00:03:00.229 --> 00:03:00.239 align:start position:0% that I usually highlight on the on the 00:03:00.239 --> 00:03:02.479 align:start position:0% that I usually highlight on the on the threat<00:03:00.840> landscape<00:03:01.110> that<00:03:01.470> we<00:03:01.620> have<00:03:01.800> recently 00:03:02.479 --> 00:03:02.489 align:start position:0% threat landscape that we have recently 00:03:02.489 --> 00:03:06.770 align:start position:0% threat landscape that we have recently is<00:03:03.030> the<00:03:03.510> upcoming<00:03:04.610> releases<00:03:05.610> of<00:03:06.060> the<00:03:06.239> file<00:03:06.510> as 00:03:06.770 --> 00:03:06.780 align:start position:0% is the upcoming releases of the file as 00:03:06.780 --> 00:03:10.310 align:start position:0% is the upcoming releases of the file as malware<00:03:07.050> so<00:03:08.010> if<00:03:08.760> you<00:03:09.270> have<00:03:09.480> for<00:03:09.660> example<00:03:09.720> an 00:03:10.310 --> 00:03:10.320 align:start position:0% malware so if you have for example an 00:03:10.320 --> 00:03:12.979 align:start position:0% malware so if you have for example an endpoint<00:03:10.680> security<00:03:11.190> product<00:03:12.030> that's<00:03:12.690> running 00:03:12.979 --> 00:03:12.989 align:start position:0% endpoint security product that's running 00:03:12.989 --> 00:03:14.420 align:start position:0% endpoint security product that's running on<00:03:13.140> your<00:03:13.230> computer<00:03:13.290> either<00:03:13.770> an<00:03:13.980> AV 00:03:14.420 --> 00:03:14.430 align:start position:0% on your computer either an AV 00:03:14.430 --> 00:03:16.850 align:start position:0% on your computer either an AV anti-malware<00:03:14.940> or<00:03:15.470> whichever<00:03:16.470> name<00:03:16.830> you 00:03:16.850 --> 00:03:16.860 align:start position:0% anti-malware or whichever name you 00:03:16.860 --> 00:03:21.770 align:start position:0% anti-malware or whichever name you prefer<00:03:17.700> to<00:03:17.850> call<00:03:17.970> it<00:03:18.030> yeah<00:03:18.390> I<00:03:19.489> still<00:03:20.489> have<00:03:20.790> the 00:03:21.770 --> 00:03:21.780 align:start position:0% prefer to call it yeah I still have the 00:03:21.780 --> 00:03:24.830 align:start position:0% prefer to call it yeah I still have the need<00:03:22.019> to<00:03:22.049> scan<00:03:22.650> files<00:03:22.980> so<00:03:23.940> however<00:03:24.120> the<00:03:24.540> idea 00:03:24.830 --> 00:03:24.840 align:start position:0% need to scan files so however the idea 00:03:24.840 --> 00:03:27.410 align:start position:0% need to scan files so however the idea of<00:03:24.930> a<00:03:25.110> file<00:03:25.410> as<00:03:25.650> malware<00:03:26.010> is<00:03:26.400> there's<00:03:26.850> no<00:03:27.060> files 00:03:27.410 --> 00:03:27.420 align:start position:0% of a file as malware is there's no files 00:03:27.420 --> 00:03:30.320 align:start position:0% of a file as malware is there's no files okay<00:03:27.989> so<00:03:28.049> how<00:03:28.470> do<00:03:28.530> you<00:03:28.920> scan<00:03:29.310> something<00:03:29.340> if 00:03:30.320 --> 00:03:30.330 align:start position:0% okay so how do you scan something if 00:03:30.330 --> 00:03:33.020 align:start position:0% okay so how do you scan something if it's<00:03:30.690> it's<00:03:31.230> not<00:03:31.470> available<00:03:31.709> in<00:03:31.980> a<00:03:32.040> computer<00:03:32.430> so 00:03:33.020 --> 00:03:33.030 align:start position:0% it's it's not available in a computer so 00:03:33.030 --> 00:03:35.390 align:start position:0% it's it's not available in a computer so those<00:03:33.330> those<00:03:33.810> malware's<00:03:34.709> are<00:03:34.890> in<00:03:34.950> general 00:03:35.390 --> 00:03:35.400 align:start position:0% those those malware's are in general 00:03:35.400 --> 00:03:38.449 align:start position:0% those those malware's are in general being<00:03:35.640> running<00:03:36.570> by<00:03:37.049> scripts<00:03:37.500> on<00:03:37.680> draw 00:03:38.449 --> 00:03:38.459 align:start position:0% being running by scripts on draw 00:03:38.459 --> 00:03:41.319 align:start position:0% being running by scripts on draw webpages<00:03:39.030> malicious<00:03:39.720> web<00:03:39.900> pages<00:03:40.140> right<00:03:40.380> and 00:03:41.319 --> 00:03:41.329 align:start position:0% webpages malicious web pages right and 00:03:41.329 --> 00:03:43.699 align:start position:0% webpages malicious web pages right and the<00:03:42.329> most<00:03:42.480> common<00:03:42.870> one<00:03:43.049> today<00:03:43.350> is<00:03:43.470> probably 00:03:43.699 --> 00:03:43.709 align:start position:0% the most common one today is probably 00:03:43.709 --> 00:03:46.250 align:start position:0% the most common one today is probably the<00:03:43.980> quaint<00:03:44.459> miners<00:03:44.850> so<00:03:45.209> it's<00:03:45.750> a<00:03:45.870> script<00:03:46.170> that 00:03:46.250 --> 00:03:46.260 align:start position:0% the quaint miners so it's a script that 00:03:46.260 --> 00:03:48.710 align:start position:0% the quaint miners so it's a script that we<00:03:46.500> run<00:03:46.680> on<00:03:46.860> a<00:03:46.950> given<00:03:47.220> computer<00:03:47.549> and<00:03:47.910> that 00:03:48.710 --> 00:03:48.720 align:start position:0% we run on a given computer and that 00:03:48.720 --> 00:03:51.560 align:start position:0% we run on a given computer and that computer<00:03:48.780> will<00:03:49.560> start<00:03:49.730> mining<00:03:50.730> bitcoins<00:03:51.269> for 00:03:51.560 --> 00:03:51.570 align:start position:0% computer will start mining bitcoins for 00:03:51.570 --> 00:03:54.100 align:start position:0% computer will start mining bitcoins for the<00:03:51.780> for<00:03:52.140> the<00:03:52.320> motors<00:03:52.950> so<00:03:53.190> you<00:03:53.430> call<00:03:53.670> these 00:03:54.100 --> 00:03:54.110 align:start position:0% the for the motors so you call these 00:03:54.110 --> 00:03:57.710 align:start position:0% the for the motors so you call these file<00:03:55.110> lists<00:03:55.530> malware<00:03:56.459> so<00:03:56.850> does<00:03:57.390> that<00:03:57.540> mean 00:03:57.710 --> 00:03:57.720 align:start position:0% file lists malware so does that mean 00:03:57.720 --> 00:04:00.110 align:start position:0% file lists malware so does that mean that<00:03:58.140> it<00:03:58.260> just<00:03:58.410> loads<00:03:58.620> right<00:03:58.890> into<00:03:59.190> RAM<00:03:59.519> from<00:03:59.970> a 00:04:00.110 --> 00:04:00.120 align:start position:0% that it just loads right into RAM from a 00:04:00.120 --> 00:04:02.509 align:start position:0% that it just loads right into RAM from a website<00:04:00.630> yes<00:04:00.870> it<00:04:01.140> will<00:04:01.380> actually<00:04:01.829> be<00:04:02.010> it<00:04:02.220> it 00:04:02.509 --> 00:04:02.519 align:start position:0% website yes it will actually be it it 00:04:02.519 --> 00:04:04.310 align:start position:0% website yes it will actually be it it will<00:04:02.700> be<00:04:02.790> a<00:04:02.820> script<00:04:03.150> that<00:04:03.420> will<00:04:03.630> be<00:04:03.840> running<00:04:04.110> in 00:04:04.310 --> 00:04:04.320 align:start position:0% will be a script that will be running in 00:04:04.320 --> 00:04:06.500 align:start position:0% will be a script that will be running in memory<00:04:04.519> whenever<00:04:05.519> you<00:04:05.970> go<00:04:06.150> to<00:04:06.209> those<00:04:06.450> websites 00:04:06.500 --> 00:04:06.510 align:start position:0% memory whenever you go to those websites 00:04:06.510 --> 00:04:09.770 align:start position:0% memory whenever you go to those websites and<00:04:07.440> if<00:04:07.980> your<00:04:08.459> existing<00:04:08.880> endpoint<00:04:09.660> security 00:04:09.770 --> 00:04:09.780 align:start position:0% and if your existing endpoint security 00:04:09.780 --> 00:04:12.410 align:start position:0% and if your existing endpoint security product<00:04:10.410> cannot<00:04:10.890> scan<00:04:11.310> or<00:04:11.670> cannot<00:04:11.940> protect 00:04:12.410 --> 00:04:12.420 align:start position:0% product cannot scan or cannot protect 00:04:12.420 --> 00:04:15.259 align:start position:0% product cannot scan or cannot protect your<00:04:12.810> memory<00:04:13.500> in<00:04:13.739> real<00:04:13.980> time<00:04:14.280> you<00:04:14.850> will<00:04:15.060> be 00:04:15.259 --> 00:04:15.269 align:start position:0% your memory in real time you will be 00:04:15.269 --> 00:04:17.390 align:start position:0% your memory in real time you will be subset<00:04:15.840> susceptible<00:04:16.470> to<00:04:16.500> that<00:04:16.950> kind<00:04:17.010> of 00:04:17.390 --> 00:04:17.400 align:start position:0% subset susceptible to that kind of 00:04:17.400 --> 00:04:18.050 align:start position:0% subset susceptible to that kind of threat 00:04:18.050 --> 00:04:18.060 align:start position:0% threat 00:04:18.060 --> 00:04:19.580 align:start position:0% threat in<00:04:18.120> general<00:04:18.479> so<00:04:18.989> sounds<00:04:19.200> to<00:04:19.260> me<00:04:19.350> like<00:04:19.380> another 00:04:19.580 --> 00:04:19.590 align:start position:0% in general so sounds to me like another 00:04:19.590 --> 00:04:20.310 align:start position:0% in general so sounds to me like another like 00:04:20.310 --> 00:04:20.320 align:start position:0% like 00:04:20.320 --> 00:04:22.140 align:start position:0% like wanna<00:04:20.470> cry<00:04:20.710> as<00:04:20.890> the<00:04:21.130> first<00:04:21.370> kind<00:04:21.610> of<00:04:21.760> example 00:04:22.140 --> 00:04:22.150 align:start position:0% wanna cry as the first kind of example 00:04:22.150 --> 00:04:25.020 align:start position:0% wanna cry as the first kind of example of<00:04:22.180> ransomware<00:04:22.630> another<00:04:23.590> threat<00:04:23.950> where<00:04:24.190> basic 00:04:25.020 --> 00:04:25.030 align:start position:0% of ransomware another threat where basic 00:04:25.030 --> 00:04:27.750 align:start position:0% of ransomware another threat where basic like<00:04:25.680> antivirus<00:04:26.680> and<00:04:26.860> use<00:04:27.130> the<00:04:27.250> absolutely 00:04:27.750 --> 00:04:27.760 align:start position:0% like antivirus and use the absolutely 00:04:27.760 --> 00:04:30.420 align:start position:0% like antivirus and use the absolutely virus<00:04:28.060> because<00:04:28.330> here<00:04:29.010> anti-malware<00:04:30.010> is<00:04:30.370> a 00:04:30.420 --> 00:04:30.430 align:start position:0% virus because here anti-malware is a 00:04:30.430 --> 00:04:32.460 align:start position:0% virus because here anti-malware is a term<00:04:30.670> that<00:04:30.700> we<00:04:31.030> in<00:04:31.480> the<00:04:31.660> industry<00:04:31.780> use<00:04:32.230> these 00:04:32.460 --> 00:04:32.470 align:start position:0% term that we in the industry use these 00:04:32.470 --> 00:04:34.740 align:start position:0% term that we in the industry use these days<00:04:32.710> because<00:04:33.010> really<00:04:33.970> it's<00:04:34.090> not<00:04:34.210> just 00:04:34.740 --> 00:04:34.750 align:start position:0% days because really it's not just 00:04:34.750 --> 00:04:36.450 align:start position:0% days because really it's not just viruses<00:04:35.470> that<00:04:35.620> we<00:04:35.710> are<00:04:35.980> dealing<00:04:36.100> with<00:04:36.280> those 00:04:36.450 --> 00:04:36.460 align:start position:0% viruses that we are dealing with those 00:04:36.460 --> 00:04:40.290 align:start position:0% viruses that we are dealing with those threats<00:04:36.760> anymore<00:04:37.150> so<00:04:37.420> so<00:04:37.900> is<00:04:38.080> antivirus<00:04:39.010> is<00:04:39.340> it 00:04:40.290 --> 00:04:40.300 align:start position:0% threats anymore so so is antivirus is it 00:04:40.300 --> 00:04:43.560 align:start position:0% threats anymore so so is antivirus is it sufficient<00:04:40.630> anymore<00:04:41.470> I<00:04:42.270> don't<00:04:43.270> I<00:04:43.420> don't 00:04:43.560 --> 00:04:43.570 align:start position:0% sufficient anymore I don't I don't 00:04:43.570 --> 00:04:45.540 align:start position:0% sufficient anymore I don't I don't believe<00:04:43.960> in<00:04:44.110> C<00:04:44.260> virus<00:04:44.590> has<00:04:44.770> been<00:04:44.800> sufficient 00:04:45.540 --> 00:04:45.550 align:start position:0% believe in C virus has been sufficient 00:04:45.550 --> 00:04:48.060 align:start position:0% believe in C virus has been sufficient for<00:04:45.760> a<00:04:45.790> long<00:04:46.120> time<00:04:46.510> so<00:04:46.930> not<00:04:47.350> only<00:04:47.710> we<00:04:47.830> have<00:04:47.860> the 00:04:48.060 --> 00:04:48.070 align:start position:0% for a long time so not only we have the 00:04:48.070 --> 00:04:51.180 align:start position:0% for a long time so not only we have the viruses<00:04:48.820> out<00:04:49.000> there<00:04:49.200> we<00:04:50.200> have<00:04:50.410> those<00:04:50.650> files<00:04:50.980> as 00:04:51.180 --> 00:04:51.190 align:start position:0% viruses out there we have those files as 00:04:51.190 --> 00:04:55.380 align:start position:0% viruses out there we have those files as malware's<00:04:51.610> we<00:04:51.880> have<00:04:52.090> the<00:04:52.300> crypto<00:04:54.150> actors<00:04:55.150> in 00:04:55.380 --> 00:04:55.390 align:start position:0% malware's we have the crypto actors in 00:04:55.390 --> 00:04:57.060 align:start position:0% malware's we have the crypto actors in general<00:04:55.720> the<00:04:55.840> ransom<00:04:56.200> layers<00:04:56.410> we<00:04:57.040> have 00:04:57.060 --> 00:04:57.070 align:start position:0% general the ransom layers we have 00:04:57.070 --> 00:04:59.820 align:start position:0% general the ransom layers we have Trojans<00:04:57.820> we<00:04:58.000> have<00:04:58.240> back<00:04:58.600> doors<00:04:58.630> we<00:04:59.620> have 00:04:59.820 --> 00:04:59.830 align:start position:0% Trojans we have back doors we have 00:04:59.830 --> 00:05:02.850 align:start position:0% Trojans we have back doors we have exploits<00:05:00.370> so<00:05:00.880> in<00:05:01.240> general<00:05:01.810> is<00:05:02.080> antivirus 00:05:02.850 --> 00:05:02.860 align:start position:0% exploits so in general is antivirus 00:05:02.860 --> 00:05:06.090 align:start position:0% exploits so in general is antivirus enough<00:05:03.190> you<00:05:03.850> know<00:05:04.210> is<00:05:04.930> it<00:05:05.230> better<00:05:05.560> than<00:05:05.740> not 00:05:06.090 --> 00:05:06.100 align:start position:0% enough you know is it better than not 00:05:06.100 --> 00:05:08.430 align:start position:0% enough you know is it better than not having<00:05:06.460> anything<00:05:06.820> yes<00:05:07.360> sir<00:05:07.690> but<00:05:08.050> if<00:05:08.140> you<00:05:08.260> have 00:05:08.430 --> 00:05:08.440 align:start position:0% having anything yes sir but if you have 00:05:08.440 --> 00:05:10.500 align:start position:0% having anything yes sir but if you have the<00:05:08.620> option<00:05:08.920> and<00:05:09.190> yes<00:05:09.580> you<00:05:09.910> do<00:05:10.120> have<00:05:10.330> the 00:05:10.500 --> 00:05:10.510 align:start position:0% the option and yes you do have the 00:05:10.510 --> 00:05:11.940 align:start position:0% the option and yes you do have the options<00:05:10.840> sometimes<00:05:11.350> we're<00:05:11.560> talking<00:05:11.860> about 00:05:11.940 --> 00:05:11.950 align:start position:0% options sometimes we're talking about 00:05:11.950 --> 00:05:14.220 align:start position:0% options sometimes we're talking about one<00:05:12.520> dollar<00:05:12.820> more<00:05:13.180> expensive<00:05:13.750> or<00:05:13.960> something 00:05:14.220 --> 00:05:14.230 align:start position:0% one dollar more expensive or something 00:05:14.230 --> 00:05:16.860 align:start position:0% one dollar more expensive or something like<00:05:14.320> that<00:05:14.500> you<00:05:15.190> can<00:05:15.490> go<00:05:15.730> to<00:05:15.790> a<00:05:16.030> full<00:05:16.420> suite<00:05:16.840> of 00:05:16.860 --> 00:05:16.870 align:start position:0% like that you can go to a full suite of 00:05:16.870 --> 00:05:20.190 align:start position:0% like that you can go to a full suite of an<00:05:17.740> endpoint<00:05:18.010> security<00:05:18.340> product<00:05:19.090> which<00:05:19.900> will 00:05:20.190 --> 00:05:20.200 align:start position:0% an endpoint security product which will 00:05:20.200 --> 00:05:23.610 align:start position:0% an endpoint security product which will provide<00:05:20.920> you<00:05:21.130> a<00:05:21.190> much<00:05:21.430> better<00:05:22.620> protection 00:05:23.610 --> 00:05:23.620 align:start position:0% provide you a much better protection 00:05:23.620 --> 00:05:25.500 align:start position:0% provide you a much better protection overall<00:05:24.070> protection<00:05:24.490> on<00:05:24.580> your<00:05:24.640> computer<00:05:25.030> okay 00:05:25.500 --> 00:05:25.510 align:start position:0% overall protection on your computer okay 00:05:25.510 --> 00:05:27.270 align:start position:0% overall protection on your computer okay so<00:05:25.570> I<00:05:25.660> don't<00:05:25.750> want<00:05:25.960> to<00:05:26.050> I<00:05:26.260> don't<00:05:26.890> want<00:05:27.010> to<00:05:27.190> give 00:05:27.270 --> 00:05:27.280 align:start position:0% so I don't want to I don't want to give 00:05:27.280 --> 00:05:28.830 align:start position:0% so I don't want to I don't want to give the<00:05:27.370> impression<00:05:27.460> that<00:05:27.820> this<00:05:28.030> is<00:05:28.090> a<00:05:28.540> sales 00:05:28.830 --> 00:05:28.840 align:start position:0% the impression that this is a sales 00:05:28.840 --> 00:05:30.990 align:start position:0% the impression that this is a sales pitch<00:05:29.140> that<00:05:29.170> we're<00:05:29.650> trying<00:05:30.010> to<00:05:30.160> say<00:05:30.340> you<00:05:30.880> know 00:05:30.990 --> 00:05:31.000 align:start position:0% pitch that we're trying to say you know 00:05:31.000 --> 00:05:33.450 align:start position:0% pitch that we're trying to say you know choose<00:05:31.270> ESET<00:05:31.900> endpoint<00:05:32.380> protection<00:05:32.460> advanced 00:05:33.450 --> 00:05:33.460 align:start position:0% choose ESET endpoint protection advanced 00:05:33.460 --> 00:05:35.700 align:start position:0% choose ESET endpoint protection advanced because<00:05:34.120> it's<00:05:34.450> a<00:05:34.540> sales<00:05:34.780> pitch<00:05:35.080> I<00:05:35.230> want<00:05:35.650> to 00:05:35.700 --> 00:05:35.710 align:start position:0% because it's a sales pitch I want to 00:05:35.710 --> 00:05:39.810 align:start position:0% because it's a sales pitch I want to instead<00:05:35.950> kind<00:05:36.550> of<00:05:36.640> what<00:05:37.390> what<00:05:37.890> features<00:05:38.890> of<00:05:39.280> a 00:05:39.810 --> 00:05:39.820 align:start position:0% instead kind of what what features of a 00:05:39.820 --> 00:05:40.830 align:start position:0% instead kind of what what features of a product<00:05:40.060> like<00:05:40.270> endpoint<00:05:40.780> protection 00:05:40.830 --> 00:05:40.840 align:start position:0% product like endpoint protection 00:05:40.840 --> 00:05:44.160 align:start position:0% product like endpoint protection advanced<00:05:41.650> isn't<00:05:42.130> it<00:05:42.190> that<00:05:42.910> are<00:05:43.360> taking 00:05:44.160 --> 00:05:44.170 align:start position:0% advanced isn't it that are taking 00:05:44.170 --> 00:05:45.990 align:start position:0% advanced isn't it that are taking protection<00:05:44.920> to<00:05:45.040> the<00:05:45.160> next<00:05:45.340> level<00:05:45.670> for<00:05:45.910> those 00:05:45.990 --> 00:05:46.000 align:start position:0% protection to the next level for those 00:05:46.000 --> 00:05:48.480 align:start position:0% protection to the next level for those users<00:05:46.270> so<00:05:46.630> file<00:05:47.350> this<00:05:47.560> attacks<00:05:47.950> yep 00:05:48.480 --> 00:05:48.490 align:start position:0% users so file this attacks yep 00:05:48.490 --> 00:05:50.220 align:start position:0% users so file this attacks yep ransomware<00:05:49.120> attacks<00:05:49.300> like<00:05:49.930> these<00:05:50.050> are 00:05:50.220 --> 00:05:50.230 align:start position:0% ransomware attacks like these are 00:05:50.230 --> 00:05:52.800 align:start position:0% ransomware attacks like these are threats<00:05:50.530> that<00:05:50.800> can<00:05:51.040> take<00:05:51.250> businesses<00:05:51.820> and<00:05:52.090> put 00:05:52.800 --> 00:05:52.810 align:start position:0% threats that can take businesses and put 00:05:52.810 --> 00:05:54.630 align:start position:0% threats that can take businesses and put them<00:05:52.930> out<00:05:53.080> of<00:05:53.230> this<00:05:53.380> gifts<00:05:53.740> yep<00:05:54.010> then<00:05:54.310> and 00:05:54.630 --> 00:05:54.640 align:start position:0% them out of this gifts yep then and 00:05:54.640 --> 00:05:56.490 align:start position:0% them out of this gifts yep then and bankrupt<00:05:55.210> their<00:05:55.420> owners<00:05:55.750> yeah<00:05:56.290> absolutely 00:05:56.490 --> 00:05:56.500 align:start position:0% bankrupt their owners yeah absolutely 00:05:56.500 --> 00:05:59.100 align:start position:0% bankrupt their owners yeah absolutely that's<00:05:56.950> the<00:05:57.160> reason<00:05:57.880> saying<00:05:58.150> yeah<00:05:58.390> so<00:05:58.810> what 00:05:59.100 --> 00:05:59.110 align:start position:0% that's the reason saying yeah so what 00:05:59.110 --> 00:06:01.560 align:start position:0% that's the reason saying yeah so what what<00:05:59.410> features<00:06:00.070> so<00:06:00.520> are<00:06:00.670> those<00:06:00.820> more<00:06:01.090> advanced 00:06:01.560 --> 00:06:01.570 align:start position:0% what features so are those more advanced 00:06:01.570 --> 00:06:03.270 align:start position:0% what features so are those more advanced why<00:06:01.810> do<00:06:01.870> I<00:06:02.020> need<00:06:02.110> to<00:06:02.230> pay<00:06:02.470> more<00:06:02.710> and<00:06:03.130> yeah 00:06:03.270 --> 00:06:03.280 align:start position:0% why do I need to pay more and yeah 00:06:03.280 --> 00:06:04.050 align:start position:0% why do I need to pay more and yeah absolutely 00:06:04.050 --> 00:06:04.060 align:start position:0% absolutely 00:06:04.060 --> 00:06:06.300 align:start position:0% absolutely it<00:06:04.270> specifically<00:06:04.960> tree<00:06:05.200> set<00:06:05.440> the<00:06:05.770> modules 00:06:06.300 --> 00:06:06.310 align:start position:0% it specifically tree set the modules 00:06:06.310 --> 00:06:08.280 align:start position:0% it specifically tree set the modules that<00:06:06.490> we<00:06:06.700> add<00:06:06.970> those<00:06:07.270> more<00:06:07.630> advanced<00:06:07.990> features 00:06:08.280 --> 00:06:08.290 align:start position:0% that we add those more advanced features 00:06:08.290 --> 00:06:09.960 align:start position:0% that we add those more advanced features is<00:06:08.470> called<00:06:08.680> hips<00:06:08.950> which<00:06:09.340> stands<00:06:09.610> for<00:06:09.700> host 00:06:09.960 --> 00:06:09.970 align:start position:0% is called hips which stands for host 00:06:09.970 --> 00:06:12.060 align:start position:0% is called hips which stands for host intrusion<00:06:10.240> prevention<00:06:10.570> system<00:06:11.140> and<00:06:11.800> that's 00:06:12.060 --> 00:06:12.070 align:start position:0% intrusion prevention system and that's 00:06:12.070 --> 00:06:13.920 align:start position:0% intrusion prevention system and that's where<00:06:12.460> we<00:06:12.700> have<00:06:12.940> the<00:06:13.300> advanced<00:06:13.750> memory 00:06:13.920 --> 00:06:13.930 align:start position:0% where we have the advanced memory 00:06:13.930 --> 00:06:15.780 align:start position:0% where we have the advanced memory scanner<00:06:14.320> which<00:06:14.650> is<00:06:14.680> basically<00:06:15.130> protecting 00:06:15.780 --> 00:06:15.790 align:start position:0% scanner which is basically protecting 00:06:15.790 --> 00:06:18.030 align:start position:0% scanner which is basically protecting your<00:06:16.000> memory<00:06:16.390> in<00:06:16.540> real<00:06:16.750> time<00:06:16.990> the<00:06:17.350> final<00:06:17.590> and 00:06:18.030 --> 00:06:18.040 align:start position:0% your memory in real time the final and 00:06:18.040 --> 00:06:20.100 align:start position:0% your memory in real time the final and that<00:06:18.220> mostly<00:06:18.910> associated<00:06:19.480> to<00:06:19.570> the<00:06:19.690> file<00:06:19.900> as 00:06:20.100 --> 00:06:20.110 align:start position:0% that mostly associated to the file as 00:06:20.110 --> 00:06:23.670 align:start position:0% that mostly associated to the file as malware<00:06:20.760> we<00:06:21.760> have<00:06:22.060> the<00:06:22.480> exploit<00:06:22.990> blocker<00:06:23.320> so 00:06:23.670 --> 00:06:23.680 align:start position:0% malware we have the exploit blocker so 00:06:23.680 --> 00:06:25.980 align:start position:0% malware we have the exploit blocker so let's<00:06:23.890> say<00:06:24.070> whenever<00:06:24.820> a<00:06:25.030> new<00:06:25.180> company 00:06:25.980 --> 00:06:25.990 align:start position:0% let's say whenever a new company 00:06:25.990 --> 00:06:28.500 align:start position:0% let's say whenever a new company releases<00:06:26.770> a<00:06:26.800> publicly<00:06:27.550> available<00:06:27.790> exploit 00:06:28.500 --> 00:06:28.510 align:start position:0% releases a publicly available exploit 00:06:28.510 --> 00:06:30.930 align:start position:0% releases a publicly available exploit for<00:06:29.020> a<00:06:29.080> vulnerability<00:06:29.560> let's<00:06:30.310> say<00:06:30.490> this<00:06:30.730> week 00:06:30.930 --> 00:06:30.940 align:start position:0% for a vulnerability let's say this week 00:06:30.940 --> 00:06:32.710 align:start position:0% for a vulnerability let's say this week we<00:06:31.120> actually<00:06:31.240> had<00:06:31.600> a<00:06:31.630> pretty<00:06:31.900> severe 00:06:32.710 --> 00:06:32.720 align:start position:0% we actually had a pretty severe 00:06:32.720 --> 00:06:34.810 align:start position:0% we actually had a pretty severe vulnerability<00:06:33.410> with<00:06:33.560> Microsoft<00:06:34.070> and<00:06:34.340> they 00:06:34.810 --> 00:06:34.820 align:start position:0% vulnerability with Microsoft and they 00:06:34.820 --> 00:06:36.820 align:start position:0% vulnerability with Microsoft and they actually<00:06:35.150> release<00:06:35.450> the<00:06:35.690> patch<00:06:35.900> the<00:06:36.410> next<00:06:36.680> day 00:06:36.820 --> 00:06:36.830 align:start position:0% actually release the patch the next day 00:06:36.830 --> 00:06:38.140 align:start position:0% actually release the patch the next day or<00:06:36.950> something<00:06:37.130> like<00:06:37.250> that 00:06:38.140 --> 00:06:38.150 align:start position:0% or something like that 00:06:38.150 --> 00:06:42.100 align:start position:0% or something like that we<00:06:38.600> will<00:06:39.430> prevent<00:06:40.430> that<00:06:40.880> vulnerability<00:06:41.570> from 00:06:42.100 --> 00:06:42.110 align:start position:0% we will prevent that vulnerability from 00:06:42.110 --> 00:06:45.280 align:start position:0% we will prevent that vulnerability from being<00:06:42.440> exploited<00:06:43.390> this<00:06:44.390> is<00:06:44.600> exactly<00:06:44.990> what<00:06:45.200> he 00:06:45.280 --> 00:06:45.290 align:start position:0% being exploited this is exactly what he 00:06:45.290 --> 00:06:47.110 align:start position:0% being exploited this is exactly what he said<00:06:45.530> accomplished<00:06:46.310> with<00:06:46.520> wanna<00:06:46.820> cry 00:06:47.110 --> 00:06:47.120 align:start position:0% said accomplished with wanna cry 00:06:47.120 --> 00:06:50.170 align:start position:0% said accomplished with wanna cry absolutely<00:06:47.930> yes<00:06:48.200> it<00:06:48.440> was<00:06:48.590> eternal<00:06:49.370> it<00:06:49.580> was<00:06:49.790> yep 00:06:50.170 --> 00:06:50.180 align:start position:0% absolutely yes it was eternal it was yep 00:06:50.180 --> 00:06:52.750 align:start position:0% absolutely yes it was eternal it was yep it<00:06:50.420> was<00:06:50.630> the<00:06:50.690> summer<00:06:51.050> vulnerability<00:06:51.830> and<00:06:52.340> yes 00:06:52.750 --> 00:06:52.760 align:start position:0% it was the summer vulnerability and yes 00:06:52.760 --> 00:06:54.580 align:start position:0% it was the summer vulnerability and yes we<00:06:52.970> were<00:06:53.240> able<00:06:53.420> to<00:06:53.600> actually<00:06:53.810> prevent<00:06:54.350> that 00:06:54.580 --> 00:06:54.590 align:start position:0% we were able to actually prevent that 00:06:54.590 --> 00:06:56.410 align:start position:0% we were able to actually prevent that vulnerability<00:06:55.250> from<00:06:55.400> being<00:06:55.670> exploited<00:06:56.150> in 00:06:56.410 --> 00:06:56.420 align:start position:0% vulnerability from being exploited in 00:06:56.420 --> 00:06:58.360 align:start position:0% vulnerability from being exploited in the<00:06:56.510> first<00:06:56.720> place<00:06:56.930> so<00:06:57.320> even<00:06:57.620> though<00:06:57.770> wanna<00:06:58.130> cry 00:06:58.360 --> 00:06:58.370 align:start position:0% the first place so even though wanna cry 00:06:58.370 --> 00:07:00.430 align:start position:0% the first place so even though wanna cry had<00:06:58.760> never<00:06:58.940> been<00:06:59.120> discovered<00:06:59.420> or<00:06:59.900> ESET<00:07:00.290> was 00:07:00.430 --> 00:07:00.440 align:start position:0% had never been discovered or ESET was 00:07:00.440 --> 00:07:01.900 align:start position:0% had never been discovered or ESET was already<00:07:00.710> proactively<00:07:01.310> protected<00:07:01.850> absolutely 00:07:01.900 --> 00:07:01.910 align:start position:0% already proactively protected absolutely 00:07:01.910 --> 00:07:04.810 align:start position:0% already proactively protected absolutely and<00:07:02.630> we<00:07:02.930> were<00:07:03.170> actually<00:07:03.290> providing<00:07:04.280> that<00:07:04.460> kind 00:07:04.810 --> 00:07:04.820 align:start position:0% and we were actually providing that kind 00:07:04.820 --> 00:07:07.480 align:start position:0% and we were actually providing that kind of<00:07:04.970> fix<00:07:05.600> two<00:07:06.260> weeks<00:07:06.470> before<00:07:06.890> when<00:07:07.190> a<00:07:07.220> crime 00:07:07.480 --> 00:07:07.490 align:start position:0% of fix two weeks before when a crime 00:07:07.490 --> 00:07:09.790 align:start position:0% of fix two weeks before when a crime actually<00:07:07.790> existed<00:07:08.570> fantastic<00:07:09.230> we<00:07:09.380> had<00:07:09.620> that 00:07:09.790 --> 00:07:09.800 align:start position:0% actually existed fantastic we had that 00:07:09.800 --> 00:07:12.250 align:start position:0% actually existed fantastic we had that kind<00:07:10.100> of<00:07:10.220> preventive<00:07:11.120> maintenance<00:07:11.480> let's<00:07:12.140> say 00:07:12.250 --> 00:07:12.260 align:start position:0% kind of preventive maintenance let's say 00:07:12.260 --> 00:07:14.380 align:start position:0% kind of preventive maintenance let's say and<00:07:13.130> you<00:07:13.190> want<00:07:13.310> an<00:07:13.490> anti-malware<00:07:13.850> product 00:07:14.380 --> 00:07:14.390 align:start position:0% and you want an anti-malware product 00:07:14.390 --> 00:07:16.240 align:start position:0% and you want an anti-malware product that<00:07:14.480> is<00:07:14.630> going<00:07:14.810> to<00:07:15.020> be<00:07:15.110> proactive<00:07:15.440> instead<00:07:15.980> of 00:07:16.240 --> 00:07:16.250 align:start position:0% that is going to be proactive instead of 00:07:16.250 --> 00:07:18.550 align:start position:0% that is going to be proactive instead of reactive<00:07:16.480> absolutely<00:07:17.480> yes<00:07:17.690> because<00:07:17.870> in<00:07:18.230> the 00:07:18.550 --> 00:07:18.560 align:start position:0% reactive absolutely yes because in the 00:07:18.560 --> 00:07:19.870 align:start position:0% reactive absolutely yes because in the case<00:07:18.740> of<00:07:18.890> something<00:07:19.130> like<00:07:19.220> ransomware<00:07:19.640> you 00:07:19.870 --> 00:07:19.880 align:start position:0% case of something like ransomware you 00:07:19.880 --> 00:07:21.010 align:start position:0% case of something like ransomware you can<00:07:20.030> lose<00:07:20.210> everything 00:07:21.010 --> 00:07:21.020 align:start position:0% can lose everything 00:07:21.020 --> 00:07:23.860 align:start position:0% can lose everything yep<00:07:21.500> and<00:07:21.740> so<00:07:22.100> there<00:07:22.310> is<00:07:22.430> no<00:07:22.790> reactive<00:07:23.690> response 00:07:23.860 --> 00:07:23.870 align:start position:0% yep and so there is no reactive response 00:07:23.870 --> 00:07:26.200 align:start position:0% yep and so there is no reactive response to<00:07:24.350> that<00:07:24.470> then<00:07:24.950> I<00:07:25.160> hope<00:07:25.460> your<00:07:25.610> backups<00:07:26.090> are 00:07:26.200 --> 00:07:26.210 align:start position:0% to that then I hope your backups are 00:07:26.210 --> 00:07:28.600 align:start position:0% to that then I hope your backups are good<00:07:26.440> yes<00:07:27.440> actually 00:07:28.600 --> 00:07:28.610 align:start position:0% good yes actually 00:07:28.610 --> 00:07:30.580 align:start position:0% good yes actually going<00:07:29.360> back<00:07:29.540> to<00:07:29.570> that<00:07:29.780> initial<00:07:30.110> question 00:07:30.580 --> 00:07:30.590 align:start position:0% going back to that initial question 00:07:30.590 --> 00:07:32.560 align:start position:0% going back to that initial question about<00:07:30.620> the<00:07:31.160> current<00:07:31.460> threat<00:07:31.669> landscape<00:07:31.940> you 00:07:32.560 --> 00:07:32.570 align:start position:0% about the current threat landscape you 00:07:32.570 --> 00:07:34.120 align:start position:0% about the current threat landscape you are<00:07:32.690> seeing<00:07:32.930> the<00:07:33.200> still<00:07:33.530> you're<00:07:33.770> seeing<00:07:34.040> a 00:07:34.120 --> 00:07:34.130 align:start position:0% are seeing the still you're seeing a 00:07:34.130 --> 00:07:36.700 align:start position:0% are seeing the still you're seeing a really<00:07:34.580> prevalent<00:07:34.900> presence<00:07:35.900> of<00:07:36.080> the<00:07:36.530> res 00:07:36.700 --> 00:07:36.710 align:start position:0% really prevalent presence of the res 00:07:36.710 --> 00:07:39.820 align:start position:0% really prevalent presence of the res more<00:07:36.919> however<00:07:37.460> now<00:07:37.850> the<00:07:37.910> the<00:07:38.690> crypto<00:07:39.410> actors 00:07:39.820 --> 00:07:39.830 align:start position:0% more however now the the crypto actors 00:07:39.830 --> 00:07:41.470 align:start position:0% more however now the the crypto actors in<00:07:40.040> just<00:07:40.220> in<00:07:40.400> this<00:07:40.580> general<00:07:41.000> they<00:07:41.240> are<00:07:41.270> not 00:07:41.470 --> 00:07:41.480 align:start position:0% in just in this general they are not 00:07:41.480 --> 00:07:43.390 align:start position:0% in just in this general they are not only<00:07:41.810> encrypting<00:07:42.380> your<00:07:42.500> data<00:07:42.710> and<00:07:43.040> holding 00:07:43.390 --> 00:07:43.400 align:start position:0% only encrypting your data and holding 00:07:43.400 --> 00:07:45.550 align:start position:0% only encrypting your data and holding you<00:07:43.460> for<00:07:43.669> ransom<00:07:43.910> but<00:07:44.630> if<00:07:44.900> you're<00:07:45.050> not<00:07:45.230> paying 00:07:45.550 --> 00:07:45.560 align:start position:0% you for ransom but if you're not paying 00:07:45.560 --> 00:07:47.290 align:start position:0% you for ransom but if you're not paying they<00:07:45.800> are<00:07:45.890> actually<00:07:46.250> releasing<00:07:46.760> the<00:07:46.880> data<00:07:47.060> and 00:07:47.290 --> 00:07:47.300 align:start position:0% they are actually releasing the data and 00:07:47.300 --> 00:07:49.270 align:start position:0% they are actually releasing the data and selling<00:07:47.660> that<00:07:47.780> data<00:07:48.020> so<00:07:48.770> it's<00:07:48.950> going<00:07:49.160> to<00:07:49.220> be 00:07:49.270 --> 00:07:49.280 align:start position:0% selling that data so it's going to be 00:07:49.280 --> 00:07:51.700 align:start position:0% selling that data so it's going to be even<00:07:49.430> more<00:07:49.790> yes<00:07:50.600> well<00:07:50.930> that<00:07:51.260> can<00:07:51.470> be<00:07:51.560> even 00:07:51.700 --> 00:07:51.710 align:start position:0% even more yes well that can be even 00:07:51.710 --> 00:07:55.120 align:start position:0% even more yes well that can be even worse<00:07:51.860> yeah<00:07:52.700> so<00:07:53.479> Wow<00:07:54.110> yeah<00:07:54.620> that's<00:07:54.950> scary 00:07:55.120 --> 00:07:55.130 align:start position:0% worse yeah so Wow yeah that's scary 00:07:55.130 --> 00:07:55.770 align:start position:0% worse yeah so Wow yeah that's scary stuff 00:07:55.770 --> 00:07:55.780 align:start position:0% stuff 00:07:55.780 --> 00:07:58.570 align:start position:0% stuff what<00:07:56.780> else<00:07:56.930> does<00:07:57.200> does<00:07:57.800> your<00:07:57.919> product<00:07:58.220> so 00:07:58.570 --> 00:07:58.580 align:start position:0% what else does does your product so 00:07:58.580 --> 00:08:02.590 align:start position:0% what else does does your product so again<00:07:58.940> to<00:07:59.900> just<00:08:00.380> look<00:08:00.560> at<00:08:00.710> why<00:08:01.250> I<00:08:01.760> get<00:08:02.510> the 00:08:02.590 --> 00:08:02.600 align:start position:0% again to just look at why I get the 00:08:02.600 --> 00:08:04.270 align:start position:0% again to just look at why I get the question<00:08:02.690> all<00:08:03.020> the<00:08:03.050> time<00:08:03.140> Ralph<00:08:03.650> yep<00:08:03.770> why 00:08:04.270 --> 00:08:04.280 align:start position:0% question all the time Ralph yep why 00:08:04.280 --> 00:08:07.360 align:start position:0% question all the time Ralph yep why should<00:08:05.150> I<00:08:05.240> buy<00:08:05.540> the<00:08:06.410> greater<00:08:06.680> product<00:08:07.190> when 00:08:07.360 --> 00:08:07.370 align:start position:0% should I buy the greater product when 00:08:07.370 --> 00:08:09.130 align:start position:0% should I buy the greater product when the<00:08:07.490> antivirus<00:08:08.060> has<00:08:08.240> been<00:08:08.390> working<00:08:08.690> so<00:08:08.900> well 00:08:09.130 --> 00:08:09.140 align:start position:0% the antivirus has been working so well 00:08:09.140 --> 00:08:10.150 align:start position:0% the antivirus has been working so well for<00:08:09.169> me<00:08:09.530> for<00:08:09.770> so<00:08:09.919> long 00:08:10.150 --> 00:08:10.160 align:start position:0% for me for so long 00:08:10.160 --> 00:08:12.070 align:start position:0% for me for so long so<00:08:10.669> as<00:08:11.060> you<00:08:11.240> said<00:08:11.450> it<00:08:11.600> might<00:08:11.750> be<00:08:11.870> a<00:08:11.900> couple 00:08:12.070 --> 00:08:12.080 align:start position:0% so as you said it might be a couple 00:08:12.080 --> 00:08:15.430 align:start position:0% so as you said it might be a couple bucks<00:08:12.320> more<00:08:12.590> don't<00:08:13.250> learn<00:08:13.430> so<00:08:14.000> more<00:08:14.270> per<00:08:14.990> seat 00:08:15.430 --> 00:08:15.440 align:start position:0% bucks more don't learn so more per seat 00:08:15.440 --> 00:08:17.830 align:start position:0% bucks more don't learn so more per seat which<00:08:16.010> can<00:08:16.340> be<00:08:16.729> a<00:08:16.760> lot<00:08:17.000> if<00:08:17.180> you've<00:08:17.300> got<00:08:17.479> ten 00:08:17.830 --> 00:08:17.840 align:start position:0% which can be a lot if you've got ten 00:08:17.840 --> 00:08:19.659 align:start position:0% which can be a lot if you've got ten thousand<00:08:18.229> computers<00:08:18.620> but<00:08:18.800> in<00:08:18.979> a<00:08:19.040> in<00:08:19.400> a<00:08:19.520> small 00:08:19.659 --> 00:08:19.669 align:start position:0% thousand computers but in a in a small 00:08:19.669 --> 00:08:22.480 align:start position:0% thousand computers but in a in a small medium<00:08:20.450> business<00:08:20.780> it's<00:08:20.960> not<00:08:21.050> that<00:08:21.350> much<00:08:21.530> why 00:08:22.480 --> 00:08:22.490 align:start position:0% medium business it's not that much why 00:08:22.490 --> 00:08:26.020 align:start position:0% medium business it's not that much why would<00:08:22.550> I<00:08:22.790> pay<00:08:23.120> more<00:08:23.860> the<00:08:24.860> additional<00:08:25.610> features 00:08:26.020 --> 00:08:26.030 align:start position:0% would I pay more the additional features 00:08:26.030 --> 00:08:28.510 align:start position:0% would I pay more the additional features that<00:08:26.180> we<00:08:26.360> have<00:08:26.390> in<00:08:27.050> the<00:08:27.290> full<00:08:27.620> endpoint 00:08:28.510 --> 00:08:28.520 align:start position:0% that we have in the full endpoint 00:08:28.520 --> 00:08:31.570 align:start position:0% that we have in the full endpoint security<00:08:28.780> solution<00:08:30.040> from<00:08:31.040> a<00:08:31.130> technical 00:08:31.570 --> 00:08:31.580 align:start position:0% security solution from a technical 00:08:31.580 --> 00:08:33.100 align:start position:0% security solution from a technical perspective<00:08:31.760> and<00:08:32.479> again<00:08:32.659> I'm<00:08:32.780> talking<00:08:32.960> about 00:08:33.100 --> 00:08:33.110 align:start position:0% perspective and again I'm talking about 00:08:33.110 --> 00:08:36.430 align:start position:0% perspective and again I'm talking about $1<00:08:33.890> more<00:08:34.039> is<00:08:34.909> well<00:08:35.390> worth<00:08:35.630> it<00:08:35.750> the<00:08:35.990> value<00:08:36.289> is 00:08:36.430 --> 00:08:36.440 align:start position:0% $1 more is well worth it the value is 00:08:36.440 --> 00:08:39.159 align:start position:0% $1 more is well worth it the value is actually<00:08:36.620> there<00:08:36.979> so<00:08:37.580> I'm<00:08:37.760> thinking<00:08:38.210> of<00:08:38.360> not 00:08:39.159 --> 00:08:39.169 align:start position:0% actually there so I'm thinking of not 00:08:39.169 --> 00:08:41.290 align:start position:0% actually there so I'm thinking of not only<00:08:39.440> adding<00:08:40.250> additional<00:08:40.550> layers<00:08:41.270> of 00:08:41.290 --> 00:08:41.300 align:start position:0% only adding additional layers of 00:08:41.300 --> 00:08:43.300 align:start position:0% only adding additional layers of protection<00:08:41.810> to<00:08:42.169> your<00:08:42.289> computer<00:08:42.740> either<00:08:43.039> at 00:08:43.300 --> 00:08:43.310 align:start position:0% protection to your computer either at 00:08:43.310 --> 00:08:44.420 align:start position:0% protection to your computer either at home<00:08:43.520> or<00:08:43.580> or 00:08:44.420 --> 00:08:44.430 align:start position:0% home or or 00:08:44.430 --> 00:08:46.880 align:start position:0% home or or at<00:08:44.490> your<00:08:44.730> business<00:08:45.050> but<00:08:46.050> I'm<00:08:46.170> also<00:08:46.380> getting 00:08:46.880 --> 00:08:46.890 align:start position:0% at your business but I'm also getting 00:08:46.890 --> 00:08:48.769 align:start position:0% at your business but I'm also getting additional<00:08:47.460> visibility<00:08:48.330> on<00:08:48.480> what's 00:08:48.769 --> 00:08:48.779 align:start position:0% additional visibility on what's 00:08:48.779 --> 00:08:50.750 align:start position:0% additional visibility on what's happening<00:08:49.230> on<00:08:49.290> your<00:08:49.320> environment<00:08:49.920> as<00:08:50.040> well<00:08:50.220> so 00:08:50.750 --> 00:08:50.760 align:start position:0% happening on your environment as well so 00:08:50.760 --> 00:08:53.240 align:start position:0% happening on your environment as well so let's<00:08:50.970> say<00:08:51.290> one<00:08:52.290> of<00:08:52.380> the<00:08:52.529> features<00:08:52.890> on<00:08:53.100> that 00:08:53.240 --> 00:08:53.250 align:start position:0% let's say one of the features on that 00:08:53.250 --> 00:08:56.300 align:start position:0% let's say one of the features on that new<00:08:53.640> on<00:08:54.480> that<00:08:54.510> bigger<00:08:55.380> product<00:08:55.980> let's<00:08:56.130> say<00:08:56.160> the 00:08:56.300 --> 00:08:56.310 align:start position:0% new on that bigger product let's say the 00:08:56.310 --> 00:08:58.850 align:start position:0% new on that bigger product let's say the endpoint<00:08:56.610> security<00:08:56.760> is<00:08:57.630> a<00:08:57.990> personal<00:08:58.680> firewall 00:08:58.850 --> 00:08:58.860 align:start position:0% endpoint security is a personal firewall 00:08:58.860 --> 00:09:00.949 align:start position:0% endpoint security is a personal firewall which<00:08:59.339> will<00:08:59.670> potentially<00:09:00.240> hit<00:09:00.450> place<00:09:00.630> your 00:09:00.949 --> 00:09:00.959 align:start position:0% which will potentially hit place your 00:09:00.959 --> 00:09:03.350 align:start position:0% which will potentially hit place your Windows<00:09:01.350> Firewall<00:09:01.560> in<00:09:01.920> my<00:09:02.130> computer<00:09:02.399> and<00:09:02.940> not 00:09:03.350 --> 00:09:03.360 align:start position:0% Windows Firewall in my computer and not 00:09:03.360 --> 00:09:05.590 align:start position:0% Windows Firewall in my computer and not only<00:09:03.540> it<00:09:03.810> will<00:09:04.050> allow<00:09:04.350> you<00:09:04.410> to<00:09:04.740> actually<00:09:04.890> have 00:09:05.590 --> 00:09:05.600 align:start position:0% only it will allow you to actually have 00:09:05.600 --> 00:09:08.030 align:start position:0% only it will allow you to actually have visibility<00:09:06.600> on<00:09:06.690> the<00:09:06.720> network<00:09:07.170> layer<00:09:07.410> so 00:09:08.030 --> 00:09:08.040 align:start position:0% visibility on the network layer so 00:09:08.040 --> 00:09:10.550 align:start position:0% visibility on the network layer so instead<00:09:08.670> of<00:09:08.730> only<00:09:09.060> looking<00:09:09.330> for<00:09:09.570> viruses<00:09:10.350> or 00:09:10.550 --> 00:09:10.560 align:start position:0% instead of only looking for viruses or 00:09:10.560 --> 00:09:12.260 align:start position:0% instead of only looking for viruses or Trojans<00:09:11.070> or<00:09:11.190> ransomware 00:09:12.260 --> 00:09:12.270 align:start position:0% Trojans or ransomware 00:09:12.270 --> 00:09:14.150 align:start position:0% Trojans or ransomware I'm<00:09:12.720> also<00:09:12.959> looking<00:09:13.230> for<00:09:13.589> duplicate<00:09:14.010> IP 00:09:14.150 --> 00:09:14.160 align:start position:0% I'm also looking for duplicate IP 00:09:14.160 --> 00:09:15.889 align:start position:0% I'm also looking for duplicate IP address<00:09:14.610> and<00:09:14.790> looking<00:09:15.060> for<00:09:15.270> DNS<00:09:15.720> poisoning 00:09:15.889 --> 00:09:15.899 align:start position:0% address and looking for DNS poisoning 00:09:15.899 --> 00:09:19.190 align:start position:0% address and looking for DNS poisoning that's<00:09:16.500> interesting<00:09:17.270> yeah<00:09:18.270> yeah<00:09:18.600> so<00:09:18.899> now 00:09:19.190 --> 00:09:19.200 align:start position:0% that's interesting yeah yeah so now 00:09:19.200 --> 00:09:22.610 align:start position:0% that's interesting yeah yeah so now possibly<00:09:20.100> network<00:09:20.880> traffic<00:09:21.510> problems<00:09:22.410> or 00:09:22.610 --> 00:09:22.620 align:start position:0% possibly network traffic problems or 00:09:22.620 --> 00:09:24.620 align:start position:0% possibly network traffic problems or even<00:09:22.649> social<00:09:23.100> yes<00:09:23.550> which<00:09:24.149> are<00:09:24.390> not 00:09:24.620 --> 00:09:24.630 align:start position:0% even social yes which are not 00:09:24.630 --> 00:09:29.510 align:start position:0% even social yes which are not necessarily<00:09:27.589> security<00:09:28.589> incidents<00:09:29.160> but<00:09:29.370> it 00:09:29.510 --> 00:09:29.520 align:start position:0% necessarily security incidents but it 00:09:29.520 --> 00:09:32.030 align:start position:0% necessarily security incidents but it can<00:09:29.760> be<00:09:30.000> a<00:09:30.029> natural<00:09:30.690> threat<00:09:30.959> so<00:09:31.589> for<00:09:31.709> example 00:09:32.030 --> 00:09:32.040 align:start position:0% can be a natural threat so for example 00:09:32.040 --> 00:09:33.889 align:start position:0% can be a natural threat so for example one<00:09:32.310> of<00:09:32.339> the<00:09:32.580> detection<00:09:33.270> that<00:09:33.360> we<00:09:33.480> have<00:09:33.660> is<00:09:33.870> a 00:09:33.889 --> 00:09:33.899 align:start position:0% one of the detection that we have is a 00:09:33.899 --> 00:09:37.100 align:start position:0% one of the detection that we have is a port<00:09:34.260> scanning<00:09:34.560> so<00:09:34.890> maybe<00:09:35.430> your<00:09:36.000> users<00:09:36.480> is<00:09:36.810> a 00:09:37.100 --> 00:09:37.110 align:start position:0% port scanning so maybe your users is a 00:09:37.110 --> 00:09:39.710 align:start position:0% port scanning so maybe your users is a given<00:09:37.830> actor<00:09:38.190> inside<00:09:38.700> your<00:09:38.880> network<00:09:38.970> is 00:09:39.710 --> 00:09:39.720 align:start position:0% given actor inside your network is 00:09:39.720 --> 00:09:42.410 align:start position:0% given actor inside your network is scanning<00:09:40.490> your<00:09:41.490> servers<00:09:41.970> for<00:09:42.180> whatever 00:09:42.410 --> 00:09:42.420 align:start position:0% scanning your servers for whatever 00:09:42.420 --> 00:09:45.079 align:start position:0% scanning your servers for whatever reason<00:09:42.959> where's<00:09:43.709> they're<00:09:44.220> not<00:09:44.700> supposed<00:09:45.029> to 00:09:45.079 --> 00:09:45.089 align:start position:0% reason where's they're not supposed to 00:09:45.089 --> 00:09:47.420 align:start position:0% reason where's they're not supposed to be<00:09:45.240> doing<00:09:45.450> that<00:09:45.570> so<00:09:45.839> yeah<00:09:46.230> it<00:09:46.680> gives<00:09:47.130> you<00:09:47.279> that 00:09:47.420 --> 00:09:47.430 align:start position:0% be doing that so yeah it gives you that 00:09:47.430 --> 00:09:49.220 align:start position:0% be doing that so yeah it gives you that visibility<00:09:47.850> so<00:09:48.180> you<00:09:48.240> can<00:09:48.450> actually<00:09:48.660> go<00:09:48.959> to<00:09:49.020> the 00:09:49.220 --> 00:09:49.230 align:start position:0% visibility so you can actually go to the 00:09:49.230 --> 00:09:50.540 align:start position:0% visibility so you can actually go to the user<00:09:49.380> and<00:09:49.560> have<00:09:49.770> a<00:09:49.800> conversation<00:09:50.010> to<00:09:50.520> see 00:09:50.540 --> 00:09:50.550 align:start position:0% user and have a conversation to see 00:09:50.550 --> 00:09:52.190 align:start position:0% user and have a conversation to see what's<00:09:50.820> what's<00:09:51.150> going<00:09:51.420> on<00:09:51.540> yeah<00:09:51.900> I've<00:09:52.050> never 00:09:52.190 --> 00:09:52.200 align:start position:0% what's what's going on yeah I've never 00:09:52.200 --> 00:09:53.810 align:start position:0% what's what's going on yeah I've never really<00:09:52.500> thought<00:09:52.650> about<00:09:52.709> that<00:09:52.920> as<00:09:53.250> a<00:09:53.279> threat 00:09:53.810 --> 00:09:53.820 align:start position:0% really thought about that as a threat 00:09:53.820 --> 00:09:56.810 align:start position:0% really thought about that as a threat yeah<00:09:54.660> because<00:09:54.870> like<00:09:55.170> a<00:09:55.230> duplicate<00:09:56.130> IP<00:09:56.279> address 00:09:56.810 --> 00:09:56.820 align:start position:0% yeah because like a duplicate IP address 00:09:56.820 --> 00:09:58.190 align:start position:0% yeah because like a duplicate IP address you<00:09:56.910> just<00:09:56.970> think<00:09:57.270> oh<00:09:57.360> well<00:09:57.570> I<00:09:57.600> accidentally 00:09:58.190 --> 00:09:58.200 align:start position:0% you just think oh well I accidentally 00:09:58.200 --> 00:10:00.110 align:start position:0% you just think oh well I accidentally assign<00:09:58.410> same<00:09:58.740> IP<00:09:58.980> to<00:09:59.250> a<00:09:59.279> printer<00:09:59.700> or<00:09:59.730> something 00:10:00.110 --> 00:10:00.120 align:start position:0% assign same IP to a printer or something 00:10:00.120 --> 00:10:01.940 align:start position:0% assign same IP to a printer or something but<00:10:00.240> what<00:10:00.330> if<00:10:00.450> it's<00:10:00.630> a<00:10:00.779> thread<00:10:01.050> actor<00:10:01.410> exactly 00:10:01.940 --> 00:10:01.950 align:start position:0% but what if it's a thread actor exactly 00:10:01.950 --> 00:10:04.460 align:start position:0% but what if it's a thread actor exactly yeah<00:10:02.070> maybe<00:10:02.520> someone<00:10:02.970> is<00:10:03.060> doing<00:10:03.570> that<00:10:04.020> IP 00:10:04.460 --> 00:10:04.470 align:start position:0% yeah maybe someone is doing that IP 00:10:04.470 --> 00:10:07.460 align:start position:0% yeah maybe someone is doing that IP address<00:10:04.589> yeah<00:10:04.980> mm-hmm<00:10:05.550> interesting<00:10:06.350> and<00:10:07.350> you 00:10:07.460 --> 00:10:07.470 align:start position:0% address yeah mm-hmm interesting and you 00:10:07.470 --> 00:10:09.710 align:start position:0% address yeah mm-hmm interesting and you mentioned<00:10:07.740> about<00:10:07.770> the<00:10:07.920> firewall<00:10:08.339> how<00:10:08.580> and<00:10:09.240> I 00:10:09.710 --> 00:10:09.720 align:start position:0% mentioned about the firewall how and I 00:10:09.720 --> 00:10:11.090 align:start position:0% mentioned about the firewall how and I don't<00:10:09.750> want<00:10:10.110> to<00:10:10.200> put<00:10:10.440> you<00:10:10.529> too<00:10:10.680> much<00:10:10.860> on<00:10:11.040> the 00:10:11.090 --> 00:10:11.100 align:start position:0% don't want to put you too much on the 00:10:11.100 --> 00:10:12.230 align:start position:0% don't want to put you too much on the spot<00:10:11.339> but<00:10:11.520> yeah<00:10:11.610> absolutely<00:10:11.700> I<00:10:12.180> mean 00:10:12.230 --> 00:10:12.240 align:start position:0% spot but yeah absolutely I mean 00:10:12.240 --> 00:10:14.090 align:start position:0% spot but yeah absolutely I mean Microsoft<00:10:12.779> Windows<00:10:13.110> 10<00:10:13.290> comes<00:10:13.860> with<00:10:14.070> a 00:10:14.090 --> 00:10:14.100 align:start position:0% Microsoft Windows 10 comes with a 00:10:14.100 --> 00:10:16.269 align:start position:0% Microsoft Windows 10 comes with a firewall<00:10:14.520> yep<00:10:14.940> so<00:10:15.270> do<00:10:15.420> I<00:10:15.480> really<00:10:15.870> need<00:10:16.050> to 00:10:16.269 --> 00:10:16.279 align:start position:0% firewall yep so do I really need to 00:10:16.279 --> 00:10:19.070 align:start position:0% firewall yep so do I really need to supplement<00:10:17.279> my<00:10:17.370> anti-malware<00:10:18.360> with<00:10:18.750> a 00:10:19.070 --> 00:10:19.080 align:start position:0% supplement my anti-malware with a 00:10:19.080 --> 00:10:21.769 align:start position:0% supplement my anti-malware with a firewall<00:10:19.830> for<00:10:20.040> Mesa<00:10:20.310> we<00:10:20.490> do<00:10:20.700> see<00:10:20.940> a<00:10:20.970> two<00:10:21.450> main 00:10:21.769 --> 00:10:21.779 align:start position:0% firewall for Mesa we do see a two main 00:10:21.779 --> 00:10:24.620 align:start position:0% firewall for Mesa we do see a two main approaches<00:10:22.560> for<00:10:23.160> that<00:10:23.700> hit<00:10:23.940> placement<00:10:24.450> let's 00:10:24.620 --> 00:10:24.630 align:start position:0% approaches for that hit placement let's 00:10:24.630 --> 00:10:26.900 align:start position:0% approaches for that hit placement let's say<00:10:24.810> so<00:10:25.350> the<00:10:25.500> first<00:10:25.709> one<00:10:25.860> is<00:10:25.890> ease<00:10:26.130> of<00:10:26.279> use<00:10:26.520> so 00:10:26.900 --> 00:10:26.910 align:start position:0% say so the first one is ease of use so 00:10:26.910 --> 00:10:28.910 align:start position:0% say so the first one is ease of use so we<00:10:27.060> do<00:10:27.270> provide<00:10:27.420> a<00:10:27.720> management<00:10:28.170> console<00:10:28.740> that 00:10:28.910 --> 00:10:28.920 align:start position:0% we do provide a management console that 00:10:28.920 --> 00:10:32.150 align:start position:0% we do provide a management console that will<00:10:29.190> allow<00:10:29.610> you<00:10:29.670> to<00:10:30.150> have<00:10:30.440> much<00:10:31.440> more 00:10:32.150 --> 00:10:32.160 align:start position:0% will allow you to have much more 00:10:32.160 --> 00:10:34.100 align:start position:0% will allow you to have much more user-friendly<00:10:32.959> configuration<00:10:33.959> and 00:10:34.100 --> 00:10:34.110 align:start position:0% user-friendly configuration and 00:10:34.110 --> 00:10:35.720 align:start position:0% user-friendly configuration and deployment<00:10:34.200> of<00:10:34.709> that<00:10:34.920> that's<00:10:35.190> specific<00:10:35.640> and 00:10:35.720 --> 00:10:35.730 align:start position:0% deployment of that that's specific and 00:10:35.730 --> 00:10:37.010 align:start position:0% deployment of that that's specific and we're<00:10:35.910> talking<00:10:36.060> centralized<00:10:36.810> management 00:10:37.010 --> 00:10:37.020 align:start position:0% we're talking centralized management 00:10:37.020 --> 00:10:39.769 align:start position:0% we're talking centralized management slowly<00:10:37.650> okay<00:10:38.070> so<00:10:38.130> all<00:10:38.630> 10,000<00:10:39.630> of<00:10:39.690> my 00:10:39.769 --> 00:10:39.779 align:start position:0% slowly okay so all 10,000 of my 00:10:39.779 --> 00:10:41.690 align:start position:0% slowly okay so all 10,000 of my computer's<00:10:40.230> yes<00:10:40.350> absolutely<00:10:40.800> four<00:10:41.190> or<00:10:41.490> five 00:10:41.690 --> 00:10:41.700 align:start position:0% computer's yes absolutely four or five 00:10:41.700 --> 00:10:43.340 align:start position:0% computer's yes absolutely four or five of<00:10:41.970> my<00:10:42.120> computer's<00:10:42.630> just<00:10:42.990> create<00:10:43.260> the 00:10:43.340 --> 00:10:43.350 align:start position:0% of my computer's just create the 00:10:43.350 --> 00:10:45.110 align:start position:0% of my computer's just create the policies<00:10:43.920> and<00:10:44.250> you<00:10:44.430> push<00:10:44.670> it<00:10:44.820> out<00:10:44.910> to<00:10:45.029> your 00:10:45.110 --> 00:10:45.120 align:start position:0% policies and you push it out to your 00:10:45.120 --> 00:10:46.970 align:start position:0% policies and you push it out to your computers<00:10:45.600> yes<00:10:45.990> again<00:10:46.290> it's<00:10:46.440> fully<00:10:46.680> automated 00:10:46.970 --> 00:10:46.980 align:start position:0% computers yes again it's fully automated 00:10:46.980 --> 00:10:49.180 align:start position:0% computers yes again it's fully automated so<00:10:47.250> it's<00:10:47.370> it's<00:10:47.640> pretty<00:10:47.970> convenient<00:10:48.450> to<00:10:48.839> use 00:10:49.180 --> 00:10:49.190 align:start position:0% so it's it's pretty convenient to use 00:10:49.190 --> 00:10:51.650 align:start position:0% so it's it's pretty convenient to use and<00:10:50.190> the<00:10:50.430> second<00:10:50.760> main<00:10:50.880> reason<00:10:51.270> is<00:10:51.450> the 00:10:51.650 --> 00:10:51.660 align:start position:0% and the second main reason is the 00:10:51.660 --> 00:10:53.870 align:start position:0% and the second main reason is the visibility<00:10:52.079> so<00:10:52.470> you<00:10:52.709> do<00:10:52.950> have<00:10:52.980> access<00:10:53.670> to<00:10:53.820> a 00:10:53.870 --> 00:10:53.880 align:start position:0% visibility so you do have access to a 00:10:53.880 --> 00:10:56.020 align:start position:0% visibility so you do have access to a lot<00:10:54.180> of<00:10:54.360> reporting<00:10:54.930> that's<00:10:55.170> actually<00:10:55.560> coming 00:10:56.020 --> 00:10:56.030 align:start position:0% lot of reporting that's actually coming 00:10:56.030 --> 00:10:59.350 align:start position:0% lot of reporting that's actually coming on<00:10:56.090> the<00:10:56.690> natural<00:10:57.140> fire<00:10:57.380> rope<00:10:57.590> component<00:10:58.360> let's 00:10:59.350 --> 00:10:59.360 align:start position:0% on the natural fire rope component let's 00:10:59.360 --> 00:11:02.020 align:start position:0% on the natural fire rope component let's say<00:10:59.570> you<00:10:59.630> can<00:11:00.200> get<00:11:00.440> a<00:11:00.500> list<00:11:00.770> of<00:11:01.040> all<00:11:01.310> the<00:11:01.730> users 00:11:02.020 --> 00:11:02.030 align:start position:0% say you can get a list of all the users 00:11:02.030 --> 00:11:04.810 align:start position:0% say you can get a list of all the users on<00:11:02.600> your<00:11:02.750> network<00:11:02.830> that's<00:11:03.830> had<00:11:04.250> a<00:11:04.280> port 00:11:04.810 --> 00:11:04.820 align:start position:0% on your network that's had a port 00:11:04.820 --> 00:11:06.760 align:start position:0% on your network that's had a port scanner<00:11:05.150> on<00:11:05.480> your<00:11:05.690> environment<00:11:05.960> on<00:11:06.350> a<00:11:06.440> given 00:11:06.760 --> 00:11:06.770 align:start position:0% scanner on your environment on a given 00:11:06.770 --> 00:11:08.980 align:start position:0% scanner on your environment on a given time<00:11:07.220> frame<00:11:07.250> so<00:11:08.060> that's<00:11:08.300> the<00:11:08.630> kind<00:11:08.870> of 00:11:08.980 --> 00:11:08.990 align:start position:0% time frame so that's the kind of 00:11:08.990 --> 00:11:10.740 align:start position:0% time frame so that's the kind of awareness<00:11:09.530> that<00:11:09.890> kind<00:11:10.100> of<00:11:10.160> visibility<00:11:10.310> that 00:11:10.740 --> 00:11:10.750 align:start position:0% awareness that kind of visibility that 00:11:10.750 --> 00:11:13.810 align:start position:0% awareness that kind of visibility that some<00:11:11.750> other<00:11:11.960> vendors<00:11:12.920> will<00:11:13.070> not<00:11:13.280> allow<00:11:13.580> you<00:11:13.640> to 00:11:13.810 --> 00:11:13.820 align:start position:0% some other vendors will not allow you to 00:11:13.820 --> 00:11:17.350 align:start position:0% some other vendors will not allow you to have<00:11:14.380> great<00:11:15.380> so<00:11:16.190> looking<00:11:16.610> at<00:11:16.760> now<00:11:16.970> here<00:11:17.210> we<00:11:17.330> are 00:11:17.350 --> 00:11:17.360 align:start position:0% have great so looking at now here we are 00:11:17.360 --> 00:11:18.280 align:start position:0% have great so looking at now here we are it's<00:11:17.600> 2020 00:11:18.280 --> 00:11:18.290 align:start position:0% it's 2020 00:11:18.290 --> 00:11:22.000 align:start position:0% it's 2020 yep<00:11:18.650> q1<00:11:19.130> 2020<00:11:19.900> being<00:11:20.900> that<00:11:21.080> we're<00:11:21.260> here<00:11:21.830> at 00:11:22.000 --> 00:11:22.010 align:start position:0% yep q1 2020 being that we're here at 00:11:22.010 --> 00:11:24.040 align:start position:0% yep q1 2020 being that we're here at ESET<00:11:22.400> headquarters<00:11:23.000> what<00:11:23.270> kind<00:11:23.510> of<00:11:23.690> threats 00:11:24.040 --> 00:11:24.050 align:start position:0% ESET headquarters what kind of threats 00:11:24.050 --> 00:11:28.870 align:start position:0% ESET headquarters what kind of threats are<00:11:24.530> we<00:11:25.010> preparing<00:11:25.670> for<00:11:26.360> in<00:11:27.320> this<00:11:27.950> new<00:11:28.160> year<00:11:28.190> is 00:11:28.870 --> 00:11:28.880 align:start position:0% are we preparing for in this new year is 00:11:28.880 --> 00:11:32.800 align:start position:0% are we preparing for in this new year is is<00:11:29.630> there<00:11:29.840> an<00:11:29.930> evolution<00:11:30.590> like<00:11:31.370> in<00:11:31.670> 2017<00:11:32.660> we 00:11:32.800 --> 00:11:32.810 align:start position:0% is there an evolution like in 2017 we 00:11:32.810 --> 00:11:34.950 align:start position:0% is there an evolution like in 2017 we really<00:11:33.230> saw<00:11:33.410> an<00:11:33.530> evolution<00:11:34.040> from<00:11:34.220> viruses 00:11:34.950 --> 00:11:34.960 align:start position:0% really saw an evolution from viruses 00:11:34.960 --> 00:11:37.810 align:start position:0% really saw an evolution from viruses ransomware<00:11:35.960> and<00:11:36.380> things<00:11:36.860> are<00:11:37.040> continuing<00:11:37.670> to 00:11:37.810 --> 00:11:37.820 align:start position:0% ransomware and things are continuing to 00:11:37.820 --> 00:11:39.580 align:start position:0% ransomware and things are continuing to progress<00:11:38.000> the<00:11:38.360> imagine<00:11:38.720> file<00:11:38.960> list<00:11:39.230> attacks 00:11:39.580 --> 00:11:39.590 align:start position:0% progress the imagine file list attacks 00:11:39.590 --> 00:11:42.190 align:start position:0% progress the imagine file list attacks what<00:11:40.550> else<00:11:40.670> our<00:11:40.820> thank<00:11:41.330> you<00:11:41.420> for<00:11:41.720> for<00:11:41.870> actually 00:11:42.190 --> 00:11:42.200 align:start position:0% what else our thank you for for actually 00:11:42.200 --> 00:11:44.560 align:start position:0% what else our thank you for for actually a<00:11:42.430> touching<00:11:43.430> based<00:11:43.610> on<00:11:43.760> that<00:11:43.880> one<00:11:44.090> and<00:11:44.210> I<00:11:44.390> will 00:11:44.560 --> 00:11:44.570 align:start position:0% a touching based on that one and I will 00:11:44.570 --> 00:11:47.590 align:start position:0% a touching based on that one and I will actually<00:11:44.750> look<00:11:45.320> at<00:11:45.530> the<00:11:45.650> cameras<00:11:46.070> a<00:11:46.600> everybody 00:11:47.590 --> 00:11:47.600 align:start position:0% actually look at the cameras a everybody 00:11:47.600 --> 00:11:51.370 align:start position:0% actually look at the cameras a everybody we<00:11:48.470> have<00:11:48.740> the<00:11:49.090> depth<00:11:50.090> malware's<00:11:50.660> of<00:11:50.930> the<00:11:51.140> the 00:11:51.370 --> 00:11:51.380 align:start position:0% we have the depth malware's of the the 00:11:51.380 --> 00:11:54.660 align:start position:0% we have the depth malware's of the the the<00:11:51.710> actual<00:11:52.070> evil<00:11:52.760> players<00:11:53.120> in<00:11:53.870> the<00:11:54.050> industry 00:11:54.660 --> 00:11:54.670 align:start position:0% the actual evil players in the industry 00:11:54.670 --> 00:11:58.000 align:start position:0% the actual evil players in the industry every<00:11:55.670> single<00:11:56.120> day<00:11:56.300> they<00:11:56.540> are<00:11:56.570> going<00:11:57.320> better 00:11:58.000 --> 00:11:58.010 align:start position:0% every single day they are going better 00:11:58.010 --> 00:11:59.950 align:start position:0% every single day they are going better and<00:11:58.340> better<00:11:58.580> and<00:11:58.820> better<00:11:59.030> so<00:11:59.300> it's<00:11:59.540> not<00:11:59.750> only 00:11:59.950 --> 00:11:59.960 align:start position:0% and better and better so it's not only 00:11:59.960 --> 00:12:02.200 align:start position:0% and better and better so it's not only important<00:12:00.560> to<00:12:00.650> hit<00:12:00.950> new<00:12:01.160> your<00:12:01.370> license<00:12:01.790> it's 00:12:02.200 --> 00:12:02.210 align:start position:0% important to hit new your license it's 00:12:02.210 --> 00:12:04.210 align:start position:0% important to hit new your license it's imperative<00:12:02.930> that<00:12:03.110> you<00:12:03.380> guys<00:12:03.530> actually<00:12:03.800> keep 00:12:04.210 --> 00:12:04.220 align:start position:0% imperative that you guys actually keep 00:12:04.220 --> 00:12:06.910 align:start position:0% imperative that you guys actually keep your<00:12:04.430> ESET<00:12:05.090> product<00:12:05.420> or<00:12:05.810> any<00:12:06.380> other<00:12:06.530> product 00:12:06.910 --> 00:12:06.920 align:start position:0% your ESET product or any other product 00:12:06.920 --> 00:12:09.220 align:start position:0% your ESET product or any other product that<00:12:07.100> you<00:12:07.250> might<00:12:07.370> have<00:12:07.520> today<00:12:07.850> as<00:12:08.110> updated<00:12:09.110> as 00:12:09.220 --> 00:12:09.230 align:start position:0% that you might have today as updated as 00:12:09.230 --> 00:12:11.830 align:start position:0% that you might have today as updated as possible<00:12:09.770> so<00:12:10.280> you<00:12:10.370> have<00:12:10.700> the<00:12:11.090> evolution<00:12:11.810> of 00:12:11.830 --> 00:12:11.840 align:start position:0% possible so you have the evolution of 00:12:11.840 --> 00:12:12.970 align:start position:0% possible so you have the evolution of the<00:12:11.990> restaurant<00:12:12.350> where<00:12:12.440> you<00:12:12.530> have<00:12:12.770> the 00:12:12.970 --> 00:12:12.980 align:start position:0% the restaurant where you have the 00:12:12.980 --> 00:12:15.160 align:start position:0% the restaurant where you have the evolution<00:12:13.460> of<00:12:13.490> the<00:12:13.670> file<00:12:13.910> as<00:12:14.180> a<00:12:14.210> malware<00:12:14.570> if 00:12:15.160 --> 00:12:15.170 align:start position:0% evolution of the file as a malware if 00:12:15.170 --> 00:12:17.170 align:start position:0% evolution of the file as a malware if you<00:12:15.440> are<00:12:15.560> running<00:12:15.800> your<00:12:16.190> antivirus<00:12:16.580> or<00:12:17.000> your 00:12:17.170 --> 00:12:17.180 align:start position:0% you are running your antivirus or your 00:12:17.180 --> 00:12:18.970 align:start position:0% you are running your antivirus or your anti-malware<00:12:17.600> product<00:12:18.170> from<00:12:18.440> three<00:12:18.800> years 00:12:18.970 --> 00:12:18.980 align:start position:0% anti-malware product from three years 00:12:18.980 --> 00:12:21.610 align:start position:0% anti-malware product from three years ago<00:12:19.100> you<00:12:19.580> might<00:12:19.820> be<00:12:20.060> losing<00:12:20.510> some<00:12:20.780> advant 00:12:21.610 --> 00:12:21.620 align:start position:0% ago you might be losing some advant 00:12:21.620 --> 00:12:23.850 align:start position:0% ago you might be losing some advant advantage<00:12:21.860> in<00:12:22.670> there<00:12:22.820> so<00:12:23.450> you<00:12:23.540> might<00:12:23.750> be 00:12:23.850 --> 00:12:23.860 align:start position:0% advantage in there so you might be 00:12:23.860 --> 00:12:26.500 align:start position:0% advantage in there so you might be actually<00:12:24.860> lagging<00:12:25.250> behind<00:12:25.370> and<00:12:25.910> sometime 00:12:26.500 --> 00:12:26.510 align:start position:0% actually lagging behind and sometime 00:12:26.510 --> 00:12:28.540 align:start position:0% actually lagging behind and sometime they<00:12:26.870> will<00:12:26.900> eventually<00:12:27.740> win<00:12:28.100> over<00:12:28.340> your 00:12:28.540 --> 00:12:28.550 align:start position:0% they will eventually win over your 00:12:28.550 --> 00:12:30.280 align:start position:0% they will eventually win over your computer<00:12:29.000> and<00:12:29.210> you<00:12:29.480> might<00:12:29.660> experience<00:12:30.020> some 00:12:30.280 --> 00:12:30.290 align:start position:0% computer and you might experience some 00:12:30.290 --> 00:12:32.410 align:start position:0% computer and you might experience some some<00:12:30.740> loss<00:12:30.950> or<00:12:31.190> some<00:12:31.370> incidents<00:12:31.910> in<00:12:32.030> general 00:12:32.410 --> 00:12:32.420 align:start position:0% some loss or some incidents in general 00:12:32.420 --> 00:12:34.800 align:start position:0% some loss or some incidents in general so<00:12:33.020> it's<00:12:33.170> really<00:12:33.470> important<00:12:34.100> as<00:12:34.250> a<00:12:34.490> vendor 00:12:34.800 --> 00:12:34.810 align:start position:0% so it's really important as a vendor 00:12:34.810 --> 00:12:37.210 align:start position:0% so it's really important as a vendor should<00:12:35.810> be<00:12:35.990> as<00:12:36.170> updated<00:12:36.680> as<00:12:36.830> possible 00:12:37.210 --> 00:12:37.220 align:start position:0% should be as updated as possible 00:12:37.220 --> 00:12:38.800 align:start position:0% should be as updated as possible whenever<00:12:37.430> really<00:12:37.880> is<00:12:37.940> a<00:12:38.030> new<00:12:38.180> a<00:12:38.210> new<00:12:38.330> feature<00:12:38.690> a 00:12:38.800 --> 00:12:38.810 align:start position:0% whenever really is a new a new feature a 00:12:38.810 --> 00:12:40.660 align:start position:0% whenever really is a new a new feature a new<00:12:38.960> feature<00:12:39.200> a<00:12:39.350> new<00:12:39.620> version<00:12:39.920> of<00:12:40.220> the<00:12:40.340> product 00:12:40.660 --> 00:12:40.670 align:start position:0% new feature a new version of the product 00:12:40.670 --> 00:12:42.910 align:start position:0% new feature a new version of the product it's<00:12:41.300> important<00:12:41.780> that<00:12:41.810> you<00:12:42.050> actually<00:12:42.200> try<00:12:42.890> to 00:12:42.910 --> 00:12:42.920 align:start position:0% it's important that you actually try to 00:12:42.920 --> 00:12:45.730 align:start position:0% it's important that you actually try to be<00:12:43.220> as<00:12:43.460> updated<00:12:43.790> as<00:12:43.910> possible<00:12:44.300> work<00:12:44.840> with<00:12:45.170> your 00:12:45.730 --> 00:12:45.740 align:start position:0% be as updated as possible work with your 00:12:45.740 --> 00:12:47.590 align:start position:0% be as updated as possible work with your vendor<00:12:46.010> work<00:12:46.550> with<00:12:46.730> your<00:12:46.970> partner<00:12:47.330> and<00:12:47.450> work 00:12:47.590 --> 00:12:47.600 align:start position:0% vendor work with your partner and work 00:12:47.600 --> 00:12:49.960 align:start position:0% vendor work with your partner and work with<00:12:47.810> your<00:12:48.050> IT<00:12:48.170> departments<00:12:48.860> so<00:12:49.280> so<00:12:49.700> you<00:12:49.760> you 00:12:49.960 --> 00:12:49.970 align:start position:0% with your IT departments so so you you 00:12:49.970 --> 00:12:55.180 align:start position:0% with your IT departments so so you you are<00:12:50.300> well<00:12:50.660> protected<00:12:52.270> we<00:12:53.270> are<00:12:53.540> seeing<00:12:54.190> coming 00:12:55.180 --> 00:12:55.190 align:start position:0% are well protected we are seeing coming 00:12:55.190 --> 00:12:56.830 align:start position:0% are well protected we are seeing coming back<00:12:55.490> to<00:12:55.640> your<00:12:55.730> question<00:12:55.790> we<00:12:56.300> are<00:12:56.480> seeing<00:12:56.690> a 00:12:56.830 --> 00:12:56.840 align:start position:0% back to your question we are seeing a 00:12:56.840 --> 00:12:59.710 align:start position:0% back to your question we are seeing a lot<00:12:57.020> of<00:12:57.160> the 00:12:59.710 --> 00:12:59.720 align:start position:0% lot of the 00:12:59.720 --> 00:13:02.650 align:start position:0% lot of the the<00:12:59.960> movements<00:13:00.950> in<00:13:01.100> general<00:13:01.550> whenever<00:13:02.270> we<00:13:02.630> are 00:13:02.650 --> 00:13:02.660 align:start position:0% the movements in general whenever we are 00:13:02.660 --> 00:13:05.410 align:start position:0% the movements in general whenever we are looking<00:13:03.080> at<00:13:03.200> the<00:13:03.620> data<00:13:03.860> so<00:13:04.790> we<00:13:04.820> are<00:13:05.030> seeing<00:13:05.300> a 00:13:05.410 --> 00:13:05.420 align:start position:0% looking at the data so we are seeing a 00:13:05.420 --> 00:13:07.840 align:start position:0% looking at the data so we are seeing a lot<00:13:05.630> of<00:13:05.690> the<00:13:06.260> new<00:13:06.440> threats<00:13:06.830> coming<00:13:07.220> from<00:13:07.580> two 00:13:07.840 --> 00:13:07.850 align:start position:0% lot of the new threats coming from two 00:13:07.850 --> 00:13:11.680 align:start position:0% lot of the new threats coming from two main<00:13:08.920> avenues<00:13:09.920> let's<00:13:10.130> say<00:13:10.310> so<00:13:11.150> the<00:13:11.270> first<00:13:11.510> one 00:13:11.680 --> 00:13:11.690 align:start position:0% main avenues let's say so the first one 00:13:11.690 --> 00:13:12.670 align:start position:0% main avenues let's say so the first one is<00:13:11.720> hardware 00:13:12.670 --> 00:13:12.680 align:start position:0% is hardware 00:13:12.680 --> 00:13:15.610 align:start position:0% is hardware so<00:13:12.920> whenever<00:13:13.370> thinking<00:13:14.000> of<00:13:14.120> FEMA<00:13:14.930> for<00:13:15.230> example 00:13:15.610 --> 00:13:15.620 align:start position:0% so whenever thinking of FEMA for example 00:13:15.620 --> 00:13:17.740 align:start position:0% so whenever thinking of FEMA for example you<00:13:15.800> have<00:13:16.010> a<00:13:16.040> BIOS<00:13:16.460> update<00:13:16.790> you<00:13:17.330> have<00:13:17.510> a<00:13:17.540> new 00:13:17.740 --> 00:13:17.750 align:start position:0% you have a BIOS update you have a new 00:13:17.750 --> 00:13:20.170 align:start position:0% you have a BIOS update you have a new chipset<00:13:18.530> on<00:13:18.710> your<00:13:18.830> computer<00:13:19.250> yes<00:13:19.850> it's 00:13:20.170 --> 00:13:20.180 align:start position:0% chipset on your computer yes it's 00:13:20.180 --> 00:13:24.490 align:start position:0% chipset on your computer yes it's actually<00:13:20.390> possible<00:13:20.810> to<00:13:21.140> in<00:13:21.800> fact<00:13:22.130> or<00:13:22.460> true<00:13:23.500> - 00:13:24.490 --> 00:13:24.500 align:start position:0% actually possible to in fact or true - 00:13:24.500 --> 00:13:26.560 align:start position:0% actually possible to in fact or true - in<00:13:24.560> fact<00:13:24.800> that<00:13:25.220> given<00:13:25.640> a<00:13:25.670> component<00:13:26.210> on<00:13:26.450> your 00:13:26.560 --> 00:13:26.570 align:start position:0% in fact that given a component on your 00:13:26.570 --> 00:13:31.420 align:start position:0% in fact that given a component on your computer<00:13:28.600> another<00:13:29.600> point<00:13:30.020> that<00:13:30.110> we<00:13:30.440> have<00:13:30.830> and 00:13:31.420 --> 00:13:31.430 align:start position:0% computer another point that we have and 00:13:31.430 --> 00:13:33.100 align:start position:0% computer another point that we have and we<00:13:31.730> actually<00:13:31.940> have<00:13:32.330> a<00:13:32.360> lot<00:13:32.600> of<00:13:32.720> research<00:13:33.080> going 00:13:33.100 --> 00:13:33.110 align:start position:0% we actually have a lot of research going 00:13:33.110 --> 00:13:36.280 align:start position:0% we actually have a lot of research going on<00:13:33.560> on<00:13:33.800> that<00:13:34.100> specific<00:13:34.790> one<00:13:34.940> is<00:13:35.180> the<00:13:35.510> user 00:13:36.280 --> 00:13:36.290 align:start position:0% on on that specific one is the user 00:13:36.290 --> 00:13:39.430 align:start position:0% on on that specific one is the user behavior<00:13:36.890> so<00:13:37.520> let's<00:13:37.730> say<00:13:37.940> that<00:13:38.180> usually<00:13:38.720> when 00:13:39.430 --> 00:13:39.440 align:start position:0% behavior so let's say that usually when 00:13:39.440 --> 00:13:40.930 align:start position:0% behavior so let's say that usually when you<00:13:39.530> think<00:13:39.560> user<00:13:39.950> behavior<00:13:40.430> probably<00:13:40.820> the 00:13:40.930 --> 00:13:40.940 align:start position:0% you think user behavior probably the 00:13:40.940 --> 00:13:43.660 align:start position:0% you think user behavior probably the biggest<00:13:41.120> example<00:13:41.390> is<00:13:41.870> credit<00:13:42.380> card<00:13:42.670> company 00:13:43.660 --> 00:13:43.670 align:start position:0% biggest example is credit card company 00:13:43.670 --> 00:13:45.820 align:start position:0% biggest example is credit card company so<00:13:44.210> you<00:13:44.240> have<00:13:44.660> your<00:13:44.840> credit<00:13:45.110> card<00:13:45.140> in<00:13:45.380> Canada 00:13:45.820 --> 00:13:45.830 align:start position:0% so you have your credit card in Canada 00:13:45.830 --> 00:13:47.650 align:start position:0% so you have your credit card in Canada that<00:13:46.160> credit<00:13:46.520> card<00:13:46.550> has<00:13:46.880> been<00:13:47.060> used<00:13:47.300> in 00:13:47.650 --> 00:13:47.660 align:start position:0% that credit card has been used in 00:13:47.660 --> 00:13:51.880 align:start position:0% that credit card has been used in somewhere<00:13:48.440> in<00:13:48.560> Asia<00:13:48.740> and<00:13:49.690> hey<00:13:50.710> even<00:13:51.710> though 00:13:51.880 --> 00:13:51.890 align:start position:0% somewhere in Asia and hey even though 00:13:51.890 --> 00:13:54.610 align:start position:0% somewhere in Asia and hey even though online<00:13:52.780> shopping<00:13:53.780> is<00:13:53.900> available<00:13:54.380> everywhere 00:13:54.610 --> 00:13:54.620 align:start position:0% online shopping is available everywhere 00:13:54.620 --> 00:13:56.620 align:start position:0% online shopping is available everywhere it<00:13:55.160> might<00:13:55.460> create<00:13:55.730> a<00:13:55.820> trigger<00:13:56.090> hey<00:13:56.330> it's 00:13:56.620 --> 00:13:56.630 align:start position:0% it might create a trigger hey it's 00:13:56.630 --> 00:13:58.150 align:start position:0% it might create a trigger hey it's something<00:13:56.960> that<00:13:57.320> card<00:13:57.560> is<00:13:57.650> not<00:13:57.770> supposed<00:13:58.100> to 00:13:58.150 --> 00:13:58.160 align:start position:0% something that card is not supposed to 00:13:58.160 --> 00:14:00.820 align:start position:0% something that card is not supposed to be<00:13:58.340> used<00:13:58.550> in<00:13:59.030> Asia<00:13:59.660> for<00:13:59.810> example<00:14:00.230> in<00:14:00.320> Europe<00:14:00.650> or 00:14:00.820 --> 00:14:00.830 align:start position:0% be used in Asia for example in Europe or 00:14:00.830 --> 00:14:05.020 align:start position:0% be used in Asia for example in Europe or anywhere<00:14:01.130> else<00:14:01.870> and<00:14:02.870> we<00:14:03.320> are<00:14:03.680> started<00:14:04.400> to<00:14:04.430> see 00:14:05.020 --> 00:14:05.030 align:start position:0% anywhere else and we are started to see 00:14:05.030 --> 00:14:08.530 align:start position:0% anywhere else and we are started to see some<00:14:05.630> some<00:14:05.990> some<00:14:06.610> efforts<00:14:07.610> from<00:14:08.150> different 00:14:08.530 --> 00:14:08.540 align:start position:0% some some some efforts from different 00:14:08.540 --> 00:14:11.140 align:start position:0% some some some efforts from different vendors<00:14:08.870> actually<00:14:09.020> to<00:14:09.800> try<00:14:10.100> to<00:14:10.160> correlate<00:14:10.880> all 00:14:11.140 --> 00:14:11.150 align:start position:0% vendors actually to try to correlate all 00:14:11.150 --> 00:14:14.830 align:start position:0% vendors actually to try to correlate all the<00:14:11.330> incidents<00:14:11.750> or<00:14:11.960> all<00:14:12.140> the<00:14:12.410> the<00:14:13.840> incidents 00:14:14.830 --> 00:14:14.840 align:start position:0% the incidents or all the the incidents 00:14:14.840 --> 00:14:16.180 align:start position:0% the incidents or all the the incidents in<00:14:14.930> general<00:14:15.200> the<00:14:15.290> security<00:14:15.710> state<00:14:15.920> that<00:14:16.100> we 00:14:16.180 --> 00:14:16.190 align:start position:0% in general the security state that we 00:14:16.190 --> 00:14:18.850 align:start position:0% in general the security state that we flag<00:14:16.460> and<00:14:17.360> we<00:14:17.540> also<00:14:17.720> try<00:14:18.020> to<00:14:18.080> map<00:14:18.350> that<00:14:18.620> to<00:14:18.740> the 00:14:18.850 --> 00:14:18.860 align:start position:0% flag and we also try to map that to the 00:14:18.860 --> 00:14:21.250 align:start position:0% flag and we also try to map that to the actual<00:14:18.980> user<00:14:19.280> behavior<00:14:19.790> so<00:14:19.940> hey<00:14:20.120> that<00:14:20.870> user 00:14:21.250 --> 00:14:21.260 align:start position:0% actual user behavior so hey that user 00:14:21.260 --> 00:14:24.280 align:start position:0% actual user behavior so hey that user has<00:14:21.530> just<00:14:22.340> had<00:14:22.640> his<00:14:22.880> email<00:14:23.210> access<00:14:23.480> in<00:14:23.840> Canada 00:14:24.280 --> 00:14:24.290 align:start position:0% has just had his email access in Canada 00:14:24.290 --> 00:14:27.520 align:start position:0% has just had his email access in Canada being<00:14:24.920> accessed<00:14:25.490> in<00:14:25.910> Europe<00:14:26.570> name<00:14:27.170> that's<00:14:27.410> a 00:14:27.520 --> 00:14:27.530 align:start position:0% being accessed in Europe name that's a 00:14:27.530 --> 00:14:28.930 align:start position:0% being accessed in Europe name that's a user<00:14:27.770> that's<00:14:27.950> always<00:14:28.100> traveling<00:14:28.670> so<00:14:28.760> yeah 00:14:28.930 --> 00:14:28.940 align:start position:0% user that's always traveling so yeah 00:14:28.940 --> 00:14:31.090 align:start position:0% user that's always traveling so yeah it's<00:14:29.120> kind<00:14:29.330> of<00:14:29.510> expected<00:14:30.050> maybe<00:14:30.680> not<00:14:30.920> that 00:14:31.090 --> 00:14:31.100 align:start position:0% it's kind of expected maybe not that 00:14:31.100 --> 00:14:33.130 align:start position:0% it's kind of expected maybe not that user<00:14:31.310> is<00:14:31.460> an<00:14:31.580> internal<00:14:32.000> user<00:14:32.030> he<00:14:32.420> has<00:14:32.690> no 00:14:33.130 --> 00:14:33.140 align:start position:0% user is an internal user he has no 00:14:33.140 --> 00:14:35.500 align:start position:0% user is an internal user he has no reason<00:14:33.440> to<00:14:33.650> have<00:14:33.950> that<00:14:34.190> kind<00:14:34.430> of<00:14:34.550> exposure<00:14:35.270> in 00:14:35.500 --> 00:14:35.510 align:start position:0% reason to have that kind of exposure in 00:14:35.510 --> 00:14:37.360 align:start position:0% reason to have that kind of exposure in there<00:14:35.690> so<00:14:36.200> we<00:14:36.320> can<00:14:36.350> actually<00:14:36.650> create<00:14:37.010> a<00:14:37.100> ticket 00:14:37.360 --> 00:14:37.370 align:start position:0% there so we can actually create a ticket 00:14:37.370 --> 00:14:39.960 align:start position:0% there so we can actually create a ticket and<00:14:37.760> we<00:14:37.910> can<00:14:38.270> flag<00:14:38.600> that<00:14:38.870> as<00:14:38.930> a<00:14:39.380> potential 00:14:39.960 --> 00:14:39.970 align:start position:0% and we can flag that as a potential 00:14:39.970 --> 00:14:42.970 align:start position:0% and we can flag that as a potential incident<00:14:40.970> so<00:14:41.300> your<00:14:41.630> admins<00:14:42.230> can<00:14:42.380> can<00:14:42.740> take<00:14:42.950> a 00:14:42.970 --> 00:14:42.980 align:start position:0% incident so your admins can can take a 00:14:42.980 --> 00:14:45.310 align:start position:0% incident so your admins can can take a look<00:14:43.160> at<00:14:43.339> it<00:14:43.570> interesting<00:14:44.570> and<00:14:44.750> we<00:14:44.990> can<00:14:45.170> do 00:14:45.310 --> 00:14:45.320 align:start position:0% look at it interesting and we can do 00:14:45.320 --> 00:14:45.760 align:start position:0% look at it interesting and we can do that 00:14:45.760 --> 00:14:45.770 align:start position:0% that 00:14:45.770 --> 00:14:48.010 align:start position:0% that so<00:14:46.160> this<00:14:46.310> is<00:14:46.460> not<00:14:47.150> as<00:14:47.330> a<00:14:47.360> third-party<00:14:47.630> service 00:14:48.010 --> 00:14:48.020 align:start position:0% so this is not as a third-party service 00:14:48.020 --> 00:14:51.430 align:start position:0% so this is not as a third-party service but<00:14:48.380> as<00:14:48.500> an<00:14:48.650> internal<00:14:49.610> absolutely<00:14:50.300> our<00:14:50.600> yeah 00:14:51.430 --> 00:14:51.440 align:start position:0% but as an internal absolutely our yeah 00:14:51.440 --> 00:14:54.340 align:start position:0% but as an internal absolutely our yeah in<00:14:51.830> mastering<00:14:52.730> and<00:14:53.270> again<00:14:53.510> the<00:14:53.750> amount<00:14:54.170> of 00:14:54.340 --> 00:14:54.350 align:start position:0% in mastering and again the amount of 00:14:54.350 --> 00:14:56.380 align:start position:0% in mastering and again the amount of data<00:14:54.560> that's<00:14:54.710> coming<00:14:55.190> out<00:14:55.310> of<00:14:55.339> those<00:14:55.760> surfaces 00:14:56.380 --> 00:14:56.390 align:start position:0% data that's coming out of those surfaces 00:14:56.390 --> 00:14:59.500 align:start position:0% data that's coming out of those surfaces is<00:14:56.930> so<00:14:57.740> big<00:14:57.980> that<00:14:58.010> automation<00:14:58.760> is<00:14:59.180> it's 00:14:59.500 --> 00:14:59.510 align:start position:0% is so big that automation is it's 00:14:59.510 --> 00:15:01.480 align:start position:0% is so big that automation is it's critical<00:14:59.960> for<00:14:59.990> that<00:15:00.230> and<00:15:00.620> so<00:15:00.800> we<00:15:01.010> do<00:15:01.250> have<00:15:01.280> a 00:15:01.480 --> 00:15:01.490 align:start position:0% critical for that and so we do have a 00:15:01.490 --> 00:15:03.370 align:start position:0% critical for that and so we do have a lot<00:15:01.820> of<00:15:01.850> automation<00:15:02.420> capabilities<00:15:02.660> in<00:15:03.260> our 00:15:03.370 --> 00:15:03.380 align:start position:0% lot of automation capabilities in our 00:15:03.380 --> 00:15:05.220 align:start position:0% lot of automation capabilities in our products<00:15:03.860> yeah 00:15:05.220 --> 00:15:05.230 align:start position:0% products yeah 00:15:05.230 --> 00:15:07.260 align:start position:0% products yeah and<00:15:05.710> again<00:15:05.950> it's<00:15:06.130> everything<00:15:06.730> to<00:15:06.880> make<00:15:07.120> your 00:15:07.260 --> 00:15:07.270 align:start position:0% and again it's everything to make your 00:15:07.270 --> 00:15:08.880 align:start position:0% and again it's everything to make your life<00:15:07.480> easier<00:15:07.870> and<00:15:08.020> I've<00:15:08.110> never<00:15:08.680> really 00:15:08.880 --> 00:15:08.890 align:start position:0% life easier and I've never really 00:15:08.890 --> 00:15:10.320 align:start position:0% life easier and I've never really thought<00:15:08.920> of<00:15:09.100> it<00:15:09.310> outside<00:15:09.460> the<00:15:09.700> context<00:15:10.150> of<00:15:10.210> the 00:15:10.320 --> 00:15:10.330 align:start position:0% thought of it outside the context of the 00:15:10.330 --> 00:15:12.660 align:start position:0% thought of it outside the context of the credit<00:15:10.600> card<00:15:10.810> like<00:15:10.960> a<00:15:10.990> perfect<00:15:11.500> example<00:15:11.590> if<00:15:12.460> I 00:15:12.660 --> 00:15:12.670 align:start position:0% credit card like a perfect example if I 00:15:12.670 --> 00:15:14.970 align:start position:0% credit card like a perfect example if I view<00:15:12.730> it<00:15:12.910> and<00:15:13.480> you<00:15:13.780> see<00:15:14.050> it<00:15:14.170> sometimes<00:15:14.410> where 00:15:14.970 --> 00:15:14.980 align:start position:0% view it and you see it sometimes where 00:15:14.980 --> 00:15:17.580 align:start position:0% view it and you see it sometimes where is<00:15:15.250> it's<00:15:15.520> an<00:15:15.640> inconvenience<00:15:16.210> but<00:15:16.360> if<00:15:17.110> your 00:15:17.580 --> 00:15:17.590 align:start position:0% is it's an inconvenience but if your 00:15:17.590 --> 00:15:19.260 align:start position:0% is it's an inconvenience but if your credit<00:15:17.890> card<00:15:18.070> ever<00:15:18.220> was<00:15:18.490> stolen<00:15:18.910> and<00:15:19.060> used 00:15:19.260 --> 00:15:19.270 align:start position:0% credit card ever was stolen and used 00:15:19.270 --> 00:15:21.090 align:start position:0% credit card ever was stolen and used maliciously<00:15:20.170> then<00:15:20.440> you<00:15:20.560> want<00:15:20.770> to<00:15:20.830> know<00:15:20.950> about 00:15:21.090 --> 00:15:21.100 align:start position:0% maliciously then you want to know about 00:15:21.100 --> 00:15:22.650 align:start position:0% maliciously then you want to know about it<00:15:21.310> and<00:15:21.430> here's<00:15:21.760> a<00:15:21.820> service<00:15:22.390> that<00:15:22.510> you're 00:15:22.650 --> 00:15:22.660 align:start position:0% it and here's a service that you're 00:15:22.660 --> 00:15:26.330 align:start position:0% it and here's a service that you're offering<00:15:22.710> and<00:15:23.710> evolving<00:15:24.370> in<00:15:24.670> 2020<00:15:25.630> that<00:15:25.780> is 00:15:26.330 --> 00:15:26.340 align:start position:0% offering and evolving in 2020 that is 00:15:26.340 --> 00:15:29.280 align:start position:0% offering and evolving in 2020 that is in-house<00:15:27.340> so<00:15:27.730> absolutely<00:15:28.450> I<00:15:28.480> have<00:15:28.750> control 00:15:29.280 --> 00:15:29.290 align:start position:0% in-house so absolutely I have control 00:15:29.290 --> 00:15:30.870 align:start position:0% in-house so absolutely I have control over<00:15:29.320> that<00:15:29.530> so<00:15:30.250> you're<00:15:30.460> thinking<00:15:30.730> of<00:15:30.790> your 00:15:30.870 --> 00:15:30.880 align:start position:0% over that so you're thinking of your 00:15:30.880 --> 00:15:32.550 align:start position:0% over that so you're thinking of your credit<00:15:31.240> card<00:15:31.450> what<00:15:31.660> if<00:15:31.780> it's<00:15:32.020> your<00:15:32.260> email 00:15:32.550 --> 00:15:32.560 align:start position:0% credit card what if it's your email 00:15:32.560 --> 00:15:35.880 align:start position:0% credit card what if it's your email access<00:15:33.040> or<00:15:33.430> maybe<00:15:33.700> your<00:15:33.880> scene<00:15:34.060> number<00:15:34.890> public 00:15:35.880 --> 00:15:35.890 align:start position:0% access or maybe your scene number public 00:15:35.890 --> 00:15:38.310 align:start position:0% access or maybe your scene number public data<00:15:36.100> basically<00:15:36.640> it's<00:15:37.330> private<00:15:37.810> it<00:15:37.960> should<00:15:38.200> be 00:15:38.310 --> 00:15:38.320 align:start position:0% data basically it's private it should be 00:15:38.320 --> 00:15:40.500 align:start position:0% data basically it's private it should be private<00:15:38.710> and<00:15:38.950> we<00:15:39.460> are<00:15:39.550> trying<00:15:39.760> to<00:15:40.060> make<00:15:40.330> it 00:15:40.500 --> 00:15:40.510 align:start position:0% private and we are trying to make it 00:15:40.510 --> 00:15:43.020 align:start position:0% private and we are trying to make it remain<00:15:40.900> private<00:15:41.320> so<00:15:41.500> is<00:15:41.560> that<00:15:41.650> the<00:15:42.030> evolution 00:15:43.020 --> 00:15:43.030 align:start position:0% remain private so is that the evolution 00:15:43.030 --> 00:15:45.810 align:start position:0% remain private so is that the evolution of<00:15:43.210> malware<00:15:43.780> do<00:15:43.960> you<00:15:44.050> think<00:15:44.260> is<00:15:44.820> targeting 00:15:45.810 --> 00:15:45.820 align:start position:0% of malware do you think is targeting 00:15:45.820 --> 00:15:50.490 align:start position:0% of malware do you think is targeting data<00:15:46.470> yeah<00:15:47.470> I<00:15:47.500> would<00:15:48.010> say<00:15:48.040> so<00:15:48.370> I<00:15:49.200> don't<00:15:50.200> see 00:15:50.490 --> 00:15:50.500 align:start position:0% data yeah I would say so I don't see 00:15:50.500 --> 00:15:54.840 align:start position:0% data yeah I would say so I don't see specific<00:15:51.990> data<00:15:52.990> to<00:15:53.440> confirm<00:15:54.160> that<00:15:54.400> that 00:15:54.840 --> 00:15:54.850 align:start position:0% specific data to confirm that that 00:15:54.850 --> 00:15:56.700 align:start position:0% specific data to confirm that that application<00:15:55.270> but<00:15:55.840> I<00:15:55.870> do<00:15:56.080> believe<00:15:56.530> that's 00:15:56.700 --> 00:15:56.710 align:start position:0% application but I do believe that's 00:15:56.710 --> 00:15:58.170 align:start position:0% application but I do believe that's that's<00:15:57.100> something<00:15:57.400> that<00:15:57.520> is<00:15:57.610> going<00:15:57.760> to<00:15:57.820> happen 00:15:58.170 --> 00:15:58.180 align:start position:0% that's something that is going to happen 00:15:58.180 --> 00:16:02.070 align:start position:0% that's something that is going to happen we<00:15:58.840> are<00:15:58.870> having<00:15:59.500> we<00:15:59.950> are<00:15:59.980> three<00:16:00.730> SS<00:16:01.120> citizens 00:16:02.070 --> 00:16:02.080 align:start position:0% we are having we are three SS citizens 00:16:02.080 --> 00:16:05.160 align:start position:0% we are having we are three SS citizens we<00:16:02.230> are<00:16:02.380> actually<00:16:03.060> producing<00:16:04.060> more<00:16:04.900> data 00:16:05.160 --> 00:16:05.170 align:start position:0% we are actually producing more data 00:16:05.170 --> 00:16:07.050 align:start position:0% we are actually producing more data every<00:16:05.590> single<00:16:05.920> day<00:16:06.040> the<00:16:06.310> amount<00:16:06.550> of<00:16:06.760> data<00:16:06.940> that 00:16:07.050 --> 00:16:07.060 align:start position:0% every single day the amount of data that 00:16:07.060 --> 00:16:11.190 align:start position:0% every single day the amount of data that we<00:16:07.330> have<00:16:07.480> associated<00:16:07.930> to<00:16:08.200> our<00:16:08.910> profiles<00:16:10.200> is 00:16:11.190 --> 00:16:11.200 align:start position:0% we have associated to our profiles is 00:16:11.200 --> 00:16:14.400 align:start position:0% we have associated to our profiles is massive<00:16:12.130> either<00:16:12.670> from<00:16:13.180> financial<00:16:14.080> data 00:16:14.400 --> 00:16:14.410 align:start position:0% massive either from financial data 00:16:14.410 --> 00:16:17.490 align:start position:0% massive either from financial data healthcare<00:16:15.160> data<00:16:15.630> social<00:16:16.630> networking<00:16:17.140> data 00:16:17.490 --> 00:16:17.500 align:start position:0% healthcare data social networking data 00:16:17.500 --> 00:16:21.060 align:start position:0% healthcare data social networking data work<00:16:18.340> data<00:16:18.670> basically<00:16:19.320> so<00:16:20.320> we<00:16:20.560> should<00:16:20.830> see 00:16:21.060 --> 00:16:21.070 align:start position:0% work data basically so we should see 00:16:21.070 --> 00:16:25.500 align:start position:0% work data basically so we should see more<00:16:22.500> custom<00:16:23.500> attacks<00:16:24.190> targeting<00:16:24.970> specific 00:16:25.500 --> 00:16:25.510 align:start position:0% more custom attacks targeting specific 00:16:25.510 --> 00:16:27.650 align:start position:0% more custom attacks targeting specific users<00:16:25.930> don't<00:16:26.110> specifically<00:16:26.650> organizations 00:16:27.650 --> 00:16:27.660 align:start position:0% users don't specifically organizations 00:16:27.660 --> 00:16:32.130 align:start position:0% users don't specifically organizations interesting<00:16:28.660> so<00:16:29.880> well<00:16:30.880> RAF<00:16:31.450> it's<00:16:31.810> been<00:16:32.110> a 00:16:32.130 --> 00:16:32.140 align:start position:0% interesting so well RAF it's been a 00:16:32.140 --> 00:16:33.750 align:start position:0% interesting so well RAF it's been a pleasure<00:16:32.710> having<00:16:32.860> you<00:16:33.130> here<00:16:33.190> we've<00:16:33.520> learned 00:16:33.750 --> 00:16:33.760 align:start position:0% pleasure having you here we've learned 00:16:33.760 --> 00:16:35.700 align:start position:0% pleasure having you here we've learned sorry<00:16:34.180> I<00:16:34.660> don't<00:16:34.720> want<00:16:34.900> to<00:16:34.990> overwhelm<00:16:35.440> the 00:16:35.700 --> 00:16:35.710 align:start position:0% sorry I don't want to overwhelm the 00:16:35.710 --> 00:16:39.360 align:start position:0% sorry I don't want to overwhelm the viewers<00:16:37.530> grand<00:16:38.530> scheme<00:16:38.830> of<00:16:38.980> things 00:16:39.360 --> 00:16:39.370 align:start position:0% viewers grand scheme of things 00:16:39.370 --> 00:16:40.950 align:start position:0% viewers grand scheme of things I<00:16:39.490> mean<00:16:39.670> 2020<00:16:40.180> is<00:16:40.270> gonna<00:16:40.450> be<00:16:40.600> an<00:16:40.750> interesting 00:16:40.950 --> 00:16:40.960 align:start position:0% I mean 2020 is gonna be an interesting 00:16:40.960 --> 00:16:43.290 align:start position:0% I mean 2020 is gonna be an interesting year<00:16:41.350> I<00:16:41.530> think<00:16:41.830> from<00:16:42.280> the<00:16:42.370> cybersecurity<00:16:42.790> land 00:16:43.290 --> 00:16:43.300 align:start position:0% year I think from the cybersecurity land 00:16:43.300 --> 00:16:45.690 align:start position:0% year I think from the cybersecurity land absolutely<00:16:43.420> are<00:16:44.200> we<00:16:44.350> still<00:16:44.680> seeing<00:16:44.950> attacks 00:16:45.690 --> 00:16:45.700 align:start position:0% absolutely are we still seeing attacks 00:16:45.700 --> 00:16:47.310 align:start position:0% absolutely are we still seeing attacks in<00:16:45.940> the<00:16:46.060> ransomware<00:16:46.420> end<00:16:46.720> of<00:16:46.840> things<00:16:46.990> are<00:16:47.230> we 00:16:47.310 --> 00:16:47.320 align:start position:0% in the ransomware end of things are we 00:16:47.320 --> 00:16:49.470 align:start position:0% in the ransomware end of things are we still<00:16:47.590> yes<00:16:48.340> we<00:16:48.670> said<00:16:48.880> customers<00:16:49.330> are 00:16:49.470 --> 00:16:49.480 align:start position:0% still yes we said customers are 00:16:49.480 --> 00:16:51.780 align:start position:0% still yes we said customers are generally<00:16:50.050> protected<00:16:51.040> against<00:16:51.280> them<00:16:51.490> yes 00:16:51.780 --> 00:16:51.790 align:start position:0% generally protected against them yes 00:16:51.790 --> 00:16:53.790 align:start position:0% generally protected against them yes there's<00:16:52.120> to<00:16:52.420> a<00:16:52.450> lot<00:16:52.780> of<00:16:52.960> Renison<00:16:53.350> we're<00:16:53.530> going 00:16:53.790 --> 00:16:53.800 align:start position:0% there's to a lot of Renison we're going 00:16:53.800 --> 00:16:57.930 align:start position:0% there's to a lot of Renison we're going on<00:16:53.920> I<00:16:54.670> don't<00:16:55.000> see<00:16:55.360> that<00:16:55.510> going<00:16:56.200> down<00:16:56.610> not<00:16:57.610> not 00:16:57.930 --> 00:16:57.940 align:start position:0% on I don't see that going down not not 00:16:57.940 --> 00:17:01.200 align:start position:0% on I don't see that going down not not not<00:16:58.270> not<00:16:58.510> in<00:16:58.840> the<00:16:58.870> near<00:16:59.080> future<00:16:59.260> at<00:16:59.530> least<00:17:00.210> it's 00:17:01.200 --> 00:17:01.210 align:start position:0% not not in the near future at least it's 00:17:01.210 --> 00:17:05.840 align:start position:0% not not in the near future at least it's still<00:17:01.780> evolving<00:17:02.020> and<00:17:02.500> the<00:17:03.340> the<00:17:03.610> the<00:17:03.940> actual 00:17:05.840 --> 00:17:05.850 align:start position:0% still evolving and the the the actual 00:17:05.850 --> 00:17:07.380 align:start position:0% still evolving and the the the actual organizations<00:17:06.850> that<00:17:07.000> are<00:17:07.120> actually 00:17:07.380 --> 00:17:07.390 align:start position:0% organizations that are actually 00:17:07.390 --> 00:17:09.240 align:start position:0% organizations that are actually organization<00:17:07.900> on<00:17:07.959> the<00:17:08.050> back<00:17:08.170> end<00:17:08.380> that<00:17:09.100> are 00:17:09.240 --> 00:17:09.250 align:start position:0% organization on the back end that are 00:17:09.250 --> 00:17:11.160 align:start position:0% organization on the back end that are running<00:17:09.550> with<00:17:09.880> those<00:17:10.150> rare<00:17:10.420> somewhere<00:17:10.750> they 00:17:11.160 --> 00:17:11.170 align:start position:0% running with those rare somewhere they 00:17:11.170 --> 00:17:12.630 align:start position:0% running with those rare somewhere they are<00:17:11.199> still<00:17:11.709> making<00:17:11.890> a<00:17:12.100> profit 00:17:12.630 --> 00:17:12.640 align:start position:0% are still making a profit 00:17:12.640 --> 00:17:13.580 align:start position:0% are still making a profit that's<00:17:12.850> the<00:17:13.060> same 00:17:13.580 --> 00:17:13.590 align:start position:0% that's the same 00:17:13.590 --> 00:17:15.650 align:start position:0% that's the same so<00:17:14.070> yeah<00:17:14.460> the<00:17:14.730> question<00:17:15.030> for<00:17:15.210> years<00:17:15.390> when<00:17:15.570> it 00:17:15.650 --> 00:17:15.660 align:start position:0% so yeah the question for years when it 00:17:15.660 --> 00:17:17.660 align:start position:0% so yeah the question for years when it was<00:17:15.780> just<00:17:15.960> viruses<00:17:16.470> on<00:17:16.620> the<00:17:16.710> landscape<00:17:17.190> the 00:17:17.660 --> 00:17:17.670 align:start position:0% was just viruses on the landscape the 00:17:17.670 --> 00:17:18.860 align:start position:0% was just viruses on the landscape the question<00:17:17.970> was<00:17:18.120> always<00:17:18.270> what's<00:17:18.660> the 00:17:18.860 --> 00:17:18.870 align:start position:0% question was always what's the 00:17:18.870 --> 00:17:20.990 align:start position:0% question was always what's the motivation<00:17:19.230> of<00:17:19.560> a<00:17:19.620> hacker<00:17:19.830> yep<00:17:20.310> to<00:17:20.460> do<00:17:20.580> this 00:17:20.990 --> 00:17:21.000 align:start position:0% motivation of a hacker yep to do this 00:17:21.000 --> 00:17:23.000 align:start position:0% motivation of a hacker yep to do this yep<00:17:21.210> and<00:17:21.360> you<00:17:21.540> say<00:17:21.750> well<00:17:22.020> money<00:17:22.260> yep<00:17:22.800> because 00:17:23.000 --> 00:17:23.010 align:start position:0% yep and you say well money yep because 00:17:23.010 --> 00:17:24.770 align:start position:0% yep and you say well money yep because makes<00:17:23.490> money<00:17:23.670> ransomware<00:17:24.240> is<00:17:24.390> a<00:17:24.480> perfect 00:17:24.770 --> 00:17:24.780 align:start position:0% makes money ransomware is a perfect 00:17:24.780 --> 00:17:26.750 align:start position:0% makes money ransomware is a perfect example<00:17:24.930> or<00:17:25.380> it's<00:17:25.500> like<00:17:25.650> will<00:17:26.130> there<00:17:26.340> bring<00:17:26.640> in 00:17:26.750 --> 00:17:26.760 align:start position:0% example or it's like will there bring in 00:17:26.760 --> 00:17:28.850 align:start position:0% example or it's like will there bring in a<00:17:26.880> ton<00:17:27.210> of<00:17:27.270> money<00:17:27.510> in<00:17:27.810> order<00:17:28.140> to<00:17:28.290> create 00:17:28.850 --> 00:17:28.860 align:start position:0% a ton of money in order to create 00:17:28.860 --> 00:17:32.270 align:start position:0% a ton of money in order to create malware<00:17:29.760> yep<00:17:30.300> which<00:17:30.960> you<00:17:31.350> know<00:17:31.440> if<00:17:31.650> that's<00:17:32.130> a 00:17:32.270 --> 00:17:32.280 align:start position:0% malware yep which you know if that's a 00:17:32.280 --> 00:17:34.580 align:start position:0% malware yep which you know if that's a scary<00:17:32.520> thing<00:17:32.760> so<00:17:33.060> thank<00:17:33.390> you<00:17:33.450> for<00:17:33.660> working<00:17:34.500> to 00:17:34.580 --> 00:17:34.590 align:start position:0% scary thing so thank you for working to 00:17:34.590 --> 00:17:36.860 align:start position:0% scary thing so thank you for working to combat<00:17:34.770> that<00:17:35.340> thanks<00:17:35.790> man<00:17:35.940> now<00:17:36.450> of<00:17:36.540> course<00:17:36.690> you 00:17:36.860 --> 00:17:36.870 align:start position:0% combat that thanks man now of course you 00:17:36.870 --> 00:17:38.420 align:start position:0% combat that thanks man now of course you can<00:17:36.990> find<00:17:37.200> out<00:17:37.320> more<00:17:37.470> about<00:17:37.530> the<00:17:37.950> particular 00:17:38.420 --> 00:17:38.430 align:start position:0% can find out more about the particular 00:17:38.430 --> 00:17:39.770 align:start position:0% can find out more about the particular protections<00:17:39.120> that<00:17:39.240> we<00:17:39.510> were<00:17:39.600> discussing 00:17:39.770 --> 00:17:39.780 align:start position:0% protections that we were discussing 00:17:39.780 --> 00:17:42.830 align:start position:0% protections that we were discussing there<00:17:40.620> by<00:17:41.040> visiting<00:17:41.460> the<00:17:41.580> website<00:17:41.840> endpoint 00:17:42.830 --> 00:17:42.840 align:start position:0% there by visiting the website endpoint 00:17:42.840 --> 00:17:46.130 align:start position:0% there by visiting the website endpoint security<00:17:43.410> dot<00:17:44.190> CA<00:17:44.610> and<00:17:45.240> incidentally<00:17:45.990> we've 00:17:46.130 --> 00:17:46.140 align:start position:0% security dot CA and incidentally we've 00:17:46.140 --> 00:17:50.420 align:start position:0% security dot CA and incidentally we've got<00:17:46.320> some<00:17:46.530> more<00:17:47.120> video<00:17:48.410> help<00:17:49.410> and<00:17:49.770> and<00:17:50.070> some 00:17:50.420 --> 00:17:50.430 align:start position:0% got some more video help and and some 00:17:50.430 --> 00:17:52.580 align:start position:0% got some more video help and and some great<00:17:50.700> educational<00:17:51.510> content<00:17:51.960> there<00:17:52.170> that<00:17:52.200> is 00:17:52.580 --> 00:17:52.590 align:start position:0% great educational content there that is 00:17:52.590 --> 00:17:56.300 align:start position:0% great educational content there that is really<00:17:53.250> geared<00:17:53.460> toward<00:17:54.030> businesses<00:17:54.990> so<00:17:55.470> that 00:17:56.300 --> 00:17:56.310 align:start position:0% really geared toward businesses so that 00:17:56.310 --> 00:17:58.850 align:start position:0% really geared toward businesses so that information<00:17:57.210> is<00:17:57.360> there<00:17:57.660> as<00:17:57.930> a<00:17:57.990> resource<00:17:58.710> for 00:17:58.850 --> 00:17:58.860 align:start position:0% information is there as a resource for 00:17:58.860 --> 00:18:01.730 align:start position:0% information is there as a resource for you<00:17:59.040> to<00:17:59.160> be<00:17:59.280> able<00:17:59.340> to<00:17:59.780> to<00:18:00.780> just<00:18:00.960> watch<00:18:01.230> videos 00:18:01.730 --> 00:18:01.740 align:start position:0% you to be able to to just watch videos 00:18:01.740 --> 00:18:03.950 align:start position:0% you to be able to to just watch videos that<00:18:02.190> help<00:18:02.670> you<00:18:02.880> to<00:18:03.030> understand<00:18:03.540> the<00:18:03.720> threat 00:18:03.950 --> 00:18:03.960 align:start position:0% that help you to understand the threat 00:18:03.960 --> 00:18:07.520 align:start position:0% that help you to understand the threat landscape<00:18:04.200> and<00:18:04.740> and<00:18:05.030> with<00:18:06.030> that<00:18:06.360> at<00:18:06.990> endpoint 00:18:07.520 --> 00:18:07.530 align:start position:0% landscape and and with that at endpoint 00:18:07.530 --> 00:18:09.440 align:start position:0% landscape and and with that at endpoint security<00:18:07.710> dot<00:18:08.160> CA<00:18:08.460> you're<00:18:09.060> able<00:18:09.240> to<00:18:09.300> arm 00:18:09.440 --> 00:18:09.450 align:start position:0% security dot CA you're able to arm 00:18:09.450 --> 00:18:11.600 align:start position:0% security dot CA you're able to arm yourself<00:18:09.810> with<00:18:09.870> more<00:18:10.110> information<00:18:10.740> and<00:18:10.860> as<00:18:11.430> I 00:18:11.600 --> 00:18:11.610 align:start position:0% yourself with more information and as I 00:18:11.610 --> 00:18:13.220 align:start position:0% yourself with more information and as I kind<00:18:11.790> of<00:18:11.880> mentioned<00:18:11.940> it<00:18:12.360> and<00:18:12.480> alluded<00:18:12.960> to<00:18:13.080> in 00:18:13.220 --> 00:18:13.230 align:start position:0% kind of mentioned it and alluded to in 00:18:13.230 --> 00:18:15.170 align:start position:0% kind of mentioned it and alluded to in the<00:18:13.320> interview<00:18:13.650> it's<00:18:14.130> not<00:18:14.280> a<00:18:14.310> sales<00:18:14.610> pitch<00:18:14.910> for 00:18:15.170 --> 00:18:15.180 align:start position:0% the interview it's not a sales pitch for 00:18:15.180 --> 00:18:17.480 align:start position:0% the interview it's not a sales pitch for a<00:18:15.210> particular<00:18:15.510> product<00:18:15.990> or<00:18:16.230> brand<00:18:16.380> but<00:18:17.220> it<00:18:17.310> is 00:18:17.480 --> 00:18:17.490 align:start position:0% a particular product or brand but it is 00:18:17.490 --> 00:18:19.280 align:start position:0% a particular product or brand but it is an<00:18:17.790> educational<00:18:18.570> piece<00:18:18.690> that<00:18:18.930> helps<00:18:19.170> you<00:18:19.260> to 00:18:19.280 --> 00:18:19.290 align:start position:0% an educational piece that helps you to 00:18:19.290 --> 00:18:21.710 align:start position:0% an educational piece that helps you to understand<00:18:19.740> what<00:18:20.550> you<00:18:20.700> need<00:18:20.730> to<00:18:21.000> know<00:18:21.150> because 00:18:21.710 --> 00:18:21.720 align:start position:0% understand what you need to know because 00:18:21.720 --> 00:18:23.750 align:start position:0% understand what you need to know because things<00:18:21.960> are<00:18:22.110> really<00:18:22.350> evolving<00:18:22.920> ESET<00:18:23.670> has 00:18:23.750 --> 00:18:23.760 align:start position:0% things are really evolving ESET has 00:18:23.760 --> 00:18:27.410 align:start position:0% things are really evolving ESET has proven<00:18:24.000> themselves<00:18:24.240> to<00:18:24.570> be<00:18:25.280> as<00:18:26.280> we<00:18:27.180> talked 00:18:27.410 --> 00:18:27.420 align:start position:0% proven themselves to be as we talked 00:18:27.420 --> 00:18:30.380 align:start position:0% proven themselves to be as we talked about<00:18:27.540> with<00:18:27.750> wanna<00:18:27.990> cry<00:18:28.320> very<00:18:29.250> very<00:18:29.550> proactive 00:18:30.380 --> 00:18:30.390 align:start position:0% about with wanna cry very very proactive 00:18:30.390 --> 00:18:32.690 align:start position:0% about with wanna cry very very proactive being<00:18:31.050> able<00:18:31.110> to<00:18:31.260> block<00:18:31.560> a<00:18:31.830> threat<00:18:32.220> before<00:18:32.460> it 00:18:32.690 --> 00:18:32.700 align:start position:0% being able to block a threat before it 00:18:32.700 --> 00:18:36.320 align:start position:0% being able to block a threat before it was<00:18:32.910> even<00:18:33.560> known<00:18:34.640> yeah<00:18:35.640> it<00:18:35.820> wasn't<00:18:36.030> having<00:18:36.270> a 00:18:36.320 --> 00:18:36.330 align:start position:0% was even known yeah it wasn't having a 00:18:36.330 --> 00:18:38.900 align:start position:0% was even known yeah it wasn't having a thing<00:18:36.780> they<00:18:37.170> actually<00:18:37.320> blocked<00:18:37.860> the<00:18:38.220> exploit 00:18:38.900 --> 00:18:38.910 align:start position:0% thing they actually blocked the exploit 00:18:38.910 --> 00:18:41.660 align:start position:0% thing they actually blocked the exploit that<00:18:39.300> allowed<00:18:39.660> the<00:18:39.990> thing<00:18:40.260> to<00:18:40.500> exist<00:18:40.950> right<00:18:41.220> so 00:18:41.660 --> 00:18:41.670 align:start position:0% that allowed the thing to exist right so 00:18:41.670 --> 00:18:44.660 align:start position:0% that allowed the thing to exist right so that<00:18:41.820> when<00:18:42.090> the<00:18:42.300> thing<00:18:42.570> existed<00:18:43.560> the<00:18:44.280> exploit 00:18:44.660 --> 00:18:44.670 align:start position:0% that when the thing existed the exploit 00:18:44.670 --> 00:18:46.910 align:start position:0% that when the thing existed the exploit was<00:18:44.820> already<00:18:45.030> blocked<00:18:45.240> by<00:18:45.420> ESET<00:18:45.810> so<00:18:46.020> so<00:18:46.440> that 00:18:46.910 --> 00:18:46.920 align:start position:0% was already blocked by ESET so so that 00:18:46.920 --> 00:18:49.400 align:start position:0% was already blocked by ESET so so that proactive<00:18:47.700> nature<00:18:48.120> of<00:18:48.450> the<00:18:48.570> protection<00:18:49.050> to<00:18:49.080> me 00:18:49.400 --> 00:18:49.410 align:start position:0% proactive nature of the protection to me 00:18:49.410 --> 00:18:51.890 align:start position:0% proactive nature of the protection to me is<00:18:49.650> like<00:18:50.220> that's<00:18:50.670> where<00:18:51.060> it's<00:18:51.210> at<00:18:51.330> that's<00:18:51.360> what 00:18:51.890 --> 00:18:51.900 align:start position:0% is like that's where it's at that's what 00:18:51.900 --> 00:18:55.010 align:start position:0% is like that's where it's at that's what I<00:18:51.930> want<00:18:52.260> um<00:18:52.920> they<00:18:53.190> do<00:18:53.250> have<00:18:53.670> Linux<00:18:54.120> services 00:18:55.010 --> 00:18:55.020 align:start position:0% I want um they do have Linux services 00:18:55.020 --> 00:18:56.690 align:start position:0% I want um they do have Linux services available<00:18:55.230> as<00:18:55.650> well 00:18:56.690 --> 00:18:56.700 align:start position:0% available as well 00:18:56.700 --> 00:18:58.910 align:start position:0% available as well incidentally<00:18:57.450> they're<00:18:57.920> centralized 00:18:58.910 --> 00:18:58.920 align:start position:0% incidentally they're centralized 00:18:58.920 --> 00:19:01.070 align:start position:0% incidentally they're centralized management<00:18:59.160> console<00:18:59.760> that<00:18:59.910> we<00:19:00.000> discussed<00:19:00.420> is 00:19:01.070 --> 00:19:01.080 align:start position:0% management console that we discussed is 00:19:01.080 --> 00:19:03.770 align:start position:0% management console that we discussed is based<00:19:01.590> on<00:19:02.310> a<00:19:02.370> Linux<00:19:02.730> environment<00:19:02.850> so<00:19:03.480> the<00:19:03.600> one 00:19:03.770 --> 00:19:03.780 align:start position:0% based on a Linux environment so the one 00:19:03.780 --> 00:19:06.560 align:start position:0% based on a Linux environment so the one that<00:19:03.960> they<00:19:04.140> provide<00:19:04.560> is<00:19:04.920> sent<00:19:05.250> OS<00:19:05.550> I<00:19:05.910> have<00:19:06.540> a 00:19:06.560 --> 00:19:06.570 align:start position:0% that they provide is sent OS I have a 00:19:06.570 --> 00:19:08.600 align:start position:0% that they provide is sent OS I have a github<00:19:06.870> repository<00:19:07.230> that<00:19:07.890> allows<00:19:08.280> you<00:19:08.460> to 00:19:08.600 --> 00:19:08.610 align:start position:0% github repository that allows you to 00:19:08.610 --> 00:19:11.000 align:start position:0% github repository that allows you to install<00:19:08.940> it<00:19:09.000> on<00:19:09.330> Debian<00:19:09.930> buster 00:19:11.000 --> 00:19:11.010 align:start position:0% install it on Debian buster 00:19:11.010 --> 00:19:15.710 align:start position:0% install it on Debian buster that<00:19:11.460> is<00:19:11.700> github.com<00:19:12.630> slash<00:19:13.440> cat<00:19:13.800> 5<00:19:14.040> TV<00:19:14.940> slash 00:19:15.710 --> 00:19:15.720 align:start position:0% that is github.com slash cat 5 TV slash 00:19:15.720 --> 00:19:18.470 align:start position:0% that is github.com slash cat 5 TV slash ESET<00:19:16.350> you'll<00:19:16.560> see<00:19:16.770> the<00:19:16.890> installers<00:19:17.310> there<00:19:17.550> if 00:19:18.470 --> 00:19:18.480 align:start position:0% ESET you'll see the installers there if 00:19:18.480 --> 00:19:20.150 align:start position:0% ESET you'll see the installers there if you're<00:19:18.630> interested<00:19:19.080> so<00:19:19.440> there's<00:19:19.590> a<00:19:19.650> whole<00:19:19.950> lot 00:19:20.150 --> 00:19:20.160 align:start position:0% you're interested so there's a whole lot 00:19:20.160 --> 00:19:22.520 align:start position:0% you're interested so there's a whole lot of<00:19:20.190> support<00:19:20.430> there<00:19:20.820> and<00:19:21.290> endpoint<00:19:22.290> security 00:19:22.520 --> 00:19:22.530 align:start position:0% of support there and endpoint security 00:19:22.530 --> 00:19:24.590 align:start position:0% of support there and endpoint security dot<00:19:23.010> CA<00:19:23.280> is<00:19:23.400> a<00:19:23.520> great<00:19:23.910> place<00:19:24.180> that<00:19:24.210> it<00:19:24.480> all 00:19:24.590 --> 00:19:24.600 align:start position:0% dot CA is a great place that it all 00:19:24.600 --> 00:19:26.740 align:start position:0% dot CA is a great place that it all comes<00:19:24.870> together<00:19:25.020> with<00:19:25.440> blogs 00:19:26.740 --> 00:19:26.750 align:start position:0% comes together with blogs 00:19:26.750 --> 00:19:29.950 align:start position:0% comes together with blogs videos<00:19:27.080> podcasts<00:19:27.700> of<00:19:28.700> course<00:19:29.150> the<00:19:29.510> products 00:19:29.950 --> 00:19:29.960 align:start position:0% videos podcasts of course the products 00:19:29.960 --> 00:19:32.020 align:start position:0% videos podcasts of course the products themselves<00:19:30.760> recommendations<00:19:31.760> for<00:19:32.000> what 00:19:32.020 --> 00:19:32.030 align:start position:0% themselves recommendations for what 00:19:32.030 --> 00:19:34.150 align:start position:0% themselves recommendations for what would<00:19:32.390> work<00:19:32.600> in<00:19:32.780> your<00:19:32.810> environment<00:19:33.500> so<00:19:33.620> if 00:19:34.150 --> 00:19:34.160 align:start position:0% would work in your environment so if 00:19:34.160 --> 00:19:35.410 align:start position:0% would work in your environment so if you're<00:19:34.280> in<00:19:34.400> business<00:19:34.580> that's<00:19:35.000> where<00:19:35.210> you<00:19:35.300> want 00:19:35.410 --> 00:19:35.420 align:start position:0% you're in business that's where you want 00:19:35.420 --> 00:19:51.230 align:start position:0% you're in business that's where you want to<00:19:35.480> go<00:19:35.570> endpoint<00:19:36.560> security<00:19:36.890> dot<00:19:37.640> CA 00:19:51.230 --> 00:19:51.240 align:start position:0% 00:19:51.240 --> 00:19:54.279 align:start position:0% [Music]