WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:27.850 align:start position:0% [Applause] 00:00:27.850 --> 00:00:27.860 align:start position:0% 00:00:27.860 --> 00:00:31.130 align:start position:0% so 00:00:31.130 --> 00:00:31.140 align:start position:0% 00:00:31.140 --> 00:00:58.040 align:start position:0% [Music] 00:00:58.040 --> 00:00:58.050 align:start position:0% 00:00:58.050 --> 00:01:08.540 align:start position:0% difficult<00:01:05.180> so<00:01:06.180> here's<00:01:06.510> a<00:01:06.600> little<00:01:06.810> bit<00:01:07.550> today 00:01:08.540 --> 00:01:08.550 align:start position:0% difficult so here's a little bit today 00:01:08.550 --> 00:01:11.030 align:start position:0% difficult so here's a little bit today I'm<00:01:09.060> just<00:01:09.510> -<00:01:09.659> morning<00:01:10.020> this<00:01:10.470> is<00:01:10.650> not<00:01:10.680> going<00:01:10.979> to 00:01:11.030 --> 00:01:11.040 align:start position:0% I'm just - morning this is not going to 00:01:11.040 --> 00:01:13.370 align:start position:0% I'm just - morning this is not going to be<00:01:11.130> super<00:01:11.280> technical<00:01:11.700> talk<00:01:12.000> I<00:01:12.390> couldn't<00:01:13.229> hold 00:01:13.370 --> 00:01:13.380 align:start position:0% be super technical talk I couldn't hold 00:01:13.380 --> 00:01:25.130 align:start position:0% be super technical talk I couldn't hold up<00:01:13.590> to<00:01:13.710> github<00:01:13.920> the<00:01:17.180> shooting<00:01:18.180> or<00:01:24.140> super 00:01:25.130 --> 00:01:25.140 align:start position:0% up to github the shooting or super 00:01:25.140 --> 00:01:27.830 align:start position:0% up to github the shooting or super support<00:01:25.770> so<00:01:26.670> the<00:01:26.940> first<00:01:27.149> thing<00:01:27.330> I<00:01:27.420> always<00:01:27.690> have 00:01:27.830 --> 00:01:27.840 align:start position:0% support so the first thing I always have 00:01:27.840 --> 00:01:29.810 align:start position:0% support so the first thing I always have to<00:01:27.930> talk<00:01:28.080> about<00:01:28.259> generally<00:01:29.070> is<00:01:29.310> what<00:01:29.670> is 00:01:29.810 --> 00:01:29.820 align:start position:0% to talk about generally is what is 00:01:29.820 --> 00:01:32.060 align:start position:0% to talk about generally is what is security<00:01:30.380> how<00:01:31.380> does<00:01:31.500> it<00:01:31.619> work 00:01:32.060 --> 00:01:32.070 align:start position:0% security how does it work 00:01:32.070 --> 00:01:33.710 align:start position:0% security how does it work why<00:01:32.310> is<00:01:32.369> it<00:01:32.670> there<00:01:32.880> how<00:01:33.300> long<00:01:33.450> has<00:01:33.570> it<00:01:33.600> been 00:01:33.710 --> 00:01:33.720 align:start position:0% why is it there how long has it been 00:01:33.720 --> 00:01:36.469 align:start position:0% why is it there how long has it been there<00:01:34.340> we'll<00:01:35.340> talk<00:01:35.490> a<00:01:35.520> little<00:01:35.700> bit<00:01:35.940> about<00:01:36.090> our 00:01:36.469 --> 00:01:36.479 align:start position:0% there we'll talk a little bit about our 00:01:36.479 --> 00:01:39.499 align:start position:0% there we'll talk a little bit about our first<00:01:36.750> main<00:01:37.080> that<00:01:37.320> security<00:01:37.920> and<00:01:38.130> did<00:01:38.340> I<00:01:38.670> will 00:01:39.499 --> 00:01:39.509 align:start position:0% first main that security and did I will 00:01:39.509 --> 00:01:42.350 align:start position:0% first main that security and did I will refer<00:01:39.780> to<00:01:39.810> this<00:01:40.050> is<00:01:40.229> story<00:01:40.470> time<00:01:40.710> and<00:01:41.280> my<00:01:42.090> team 00:01:42.350 --> 00:01:42.360 align:start position:0% refer to this is story time and my team 00:01:42.360 --> 00:01:43.969 align:start position:0% refer to this is story time and my team who<00:01:42.570> are<00:01:42.600> here<00:01:42.720> are<00:01:43.140> probably<00:01:43.440> tired<00:01:43.740> of 00:01:43.969 --> 00:01:43.979 align:start position:0% who are here are probably tired of 00:01:43.979 --> 00:01:52.060 align:start position:0% who are here are probably tired of hearing<00:01:44.039> the<00:01:44.399> stories<00:01:44.759> but<00:01:45.450> if<00:01:46.550> go<00:01:47.550> time<00:01:47.850> so<00:01:48.660> I 00:01:52.060 --> 00:01:52.070 align:start position:0% 00:01:52.070 --> 00:01:54.410 align:start position:0% or<00:01:53.070> how<00:01:53.369> we<00:01:53.429> started<00:01:53.820> thinking<00:01:53.970> about<00:01:54.270> these 00:01:54.410 --> 00:01:54.420 align:start position:0% or how we started thinking about these 00:01:54.420 --> 00:01:56.870 align:start position:0% or how we started thinking about these things<00:01:54.679> I'm<00:01:55.679> talking<00:01:56.100> a<00:01:56.460> little<00:01:56.580> bit<00:01:56.729> about 00:01:56.870 --> 00:01:56.880 align:start position:0% things I'm talking a little bit about 00:01:56.880 --> 00:01:58.669 align:start position:0% things I'm talking a little bit about some<00:01:57.300> of<00:01:57.330> the<00:01:57.509> things<00:01:57.810> that<00:01:58.080> come<00:01:58.259> up<00:01:58.380> when 00:01:58.669 --> 00:01:58.679 align:start position:0% some of the things that come up when 00:01:58.679 --> 00:02:00.499 align:start position:0% some of the things that come up when you're<00:01:58.800> trying<00:01:59.159> to<00:01:59.340> manage<00:01:59.520> to<00:01:59.880> centralize 00:02:00.499 --> 00:02:00.509 align:start position:0% you're trying to manage to centralize 00:02:00.509 --> 00:02:03.199 align:start position:0% you're trying to manage to centralize yet<00:02:01.020> coordinating<00:02:01.890> in<00:02:02.220> response<00:02:02.670> especially 00:02:03.199 --> 00:02:03.209 align:start position:0% yet coordinating in response especially 00:02:03.209 --> 00:02:05.419 align:start position:0% yet coordinating in response especially when<00:02:03.780> you<00:02:03.869> have<00:02:04.200> lots<00:02:05.009> and<00:02:05.130> lots<00:02:05.310> of 00:02:05.419 --> 00:02:05.429 align:start position:0% when you have lots and lots of 00:02:05.429 --> 00:02:07.240 align:start position:0% when you have lots and lots of stakeholders<00:02:05.670> and 00:02:07.240 --> 00:02:07.250 align:start position:0% stakeholders and 00:02:07.250 --> 00:02:10.520 align:start position:0% stakeholders and in<00:02:08.250> our<00:02:08.429> case<00:02:08.729> you<00:02:09.030> know<00:02:09.090> Adam<00:02:09.780> poor<00:02:10.140> people 00:02:10.520 --> 00:02:10.530 align:start position:0% in our case you know Adam poor people 00:02:10.530 --> 00:02:13.400 align:start position:0% in our case you know Adam poor people might<00:02:10.860> people<00:02:11.039> in<00:02:11.250> Syria<00:02:11.640> and<00:02:12.000> then<00:02:12.840> and<00:02:13.110> also 00:02:13.400 --> 00:02:13.410 align:start position:0% might people in Syria and then and also 00:02:13.410 --> 00:02:14.990 align:start position:0% might people in Syria and then and also we'll<00:02:13.530> talk<00:02:13.800> a<00:02:14.099> little<00:02:14.220> bit<00:02:14.459> about<00:02:14.640> how 00:02:14.990 --> 00:02:15.000 align:start position:0% we'll talk a little bit about how 00:02:15.000 --> 00:02:17.360 align:start position:0% we'll talk a little bit about how governance<00:02:15.510> is<00:02:15.810> very<00:02:16.290> uniquely<00:02:16.739> positioned 00:02:17.360 --> 00:02:17.370 align:start position:0% governance is very uniquely positioned 00:02:17.370 --> 00:02:19.699 align:start position:0% governance is very uniquely positioned to<00:02:17.580> be<00:02:17.970> able<00:02:18.209> to<00:02:18.660> help<00:02:18.900> us<00:02:19.140> when<00:02:19.410> we're<00:02:19.590> trying 00:02:19.699 --> 00:02:19.709 align:start position:0% to be able to help us when we're trying 00:02:19.709 --> 00:02:22.640 align:start position:0% to be able to help us when we're trying to<00:02:19.860> be<00:02:19.980> more<00:02:20.040> proactive<00:02:20.400> and<00:02:21.120> prepared<00:02:21.930> when 00:02:22.640 --> 00:02:22.650 align:start position:0% to be more proactive and prepared when 00:02:22.650 --> 00:02:25.300 align:start position:0% to be more proactive and prepared when responding<00:02:23.190> to<00:02:23.220> sue<00:02:23.459> areas 00:02:25.300 --> 00:02:25.310 align:start position:0% responding to sue areas 00:02:25.310 --> 00:02:29.210 align:start position:0% responding to sue areas so<00:02:26.480> just<00:02:27.480> to<00:02:27.840> front<00:02:28.319> just<00:02:28.650> to<00:02:28.769> talk<00:02:28.950> a<00:02:28.980> little 00:02:29.210 --> 00:02:29.220 align:start position:0% so just to front just to talk a little 00:02:29.220 --> 00:02:32.900 align:start position:0% so just to front just to talk a little bit<00:02:29.340> about<00:02:29.489> what<00:02:29.880> security<00:02:30.269> is<00:02:30.630> I<00:02:31.550> will<00:02:32.550> skip 00:02:32.900 --> 00:02:32.910 align:start position:0% bit about what security is I will skip 00:02:32.910 --> 00:02:35.509 align:start position:0% bit about what security is I will skip over<00:02:33.180> about<00:02:33.810> ten<00:02:34.349> thousand<00:02:34.860> years<00:02:35.010> of 00:02:35.509 --> 00:02:35.519 align:start position:0% over about ten thousand years of 00:02:35.519 --> 00:02:37.940 align:start position:0% over about ten thousand years of examples<00:02:36.090> of<00:02:36.209> human<00:02:36.390> seems<00:02:36.840> horrible<00:02:37.709> and 00:02:37.940 --> 00:02:37.950 align:start position:0% examples of human seems horrible and 00:02:37.950 --> 00:02:40.490 align:start position:0% examples of human seems horrible and managing<00:02:38.430> keys<00:02:38.900> there's<00:02:39.900> some<00:02:40.049> great<00:02:40.260> stories 00:02:40.490 --> 00:02:40.500 align:start position:0% managing keys there's some great stories 00:02:40.500 --> 00:02:43.850 align:start position:0% managing keys there's some great stories from<00:02:40.769> ancient<00:02:41.010> Rome<00:02:41.400> about<00:02:42.000> how<00:02:42.410> you<00:02:43.410> if<00:02:43.739> you 00:02:43.850 --> 00:02:43.860 align:start position:0% from ancient Rome about how you if you 00:02:43.860 --> 00:02:45.710 align:start position:0% from ancient Rome about how you if you had<00:02:44.040> a<00:02:44.069> key<00:02:44.280> would<00:02:44.580> have<00:02:44.790> invented<00:02:45.120> a<00:02:45.360> piece<00:02:45.569> of 00:02:45.710 --> 00:02:45.720 align:start position:0% had a key would have invented a piece of 00:02:45.720 --> 00:02:46.339 align:start position:0% had a key would have invented a piece of jewelry 00:02:46.339 --> 00:02:46.349 align:start position:0% jewelry 00:02:46.349 --> 00:02:49.699 align:start position:0% jewelry let's<00:02:46.739> get<00:02:46.890> that<00:02:47.040> today<00:02:47.450> but<00:02:48.450> security<00:02:49.200> is<00:02:49.290> a 00:02:49.699 --> 00:02:49.709 align:start position:0% let's get that today but security is a 00:02:49.709 --> 00:02:53.089 align:start position:0% let's get that today but security is a scary<00:02:50.519> face<00:02:50.790> it's<00:02:51.269> the<00:02:51.590> seven<00:02:52.590> principles 00:02:53.089 --> 00:02:53.099 align:start position:0% scary face it's the seven principles 00:02:53.099 --> 00:02:56.000 align:start position:0% scary face it's the seven principles that<00:02:53.459> are<00:02:53.580> extremely<00:02:54.120> important<00:02:54.810> to<00:02:55.049> player 00:02:56.000 --> 00:02:56.010 align:start position:0% that are extremely important to player 00:02:56.010 --> 00:02:58.130 align:start position:0% that are extremely important to player and<00:02:56.370> implement<00:02:57.060> correctly<00:02:57.299> and<00:02:57.870> the<00:02:57.959> right 00:02:58.130 --> 00:02:58.140 align:start position:0% and implement correctly and the right 00:02:58.140 --> 00:03:00.710 align:start position:0% and implement correctly and the right places<00:02:58.440> to<00:02:59.220> make<00:02:59.370> sure<00:02:59.670> that<00:02:59.940> you<00:03:00.209> are 00:03:00.710 --> 00:03:00.720 align:start position:0% places to make sure that you are 00:03:00.720 --> 00:03:02.390 align:start position:0% places to make sure that you are protecting<00:03:01.470> and<00:03:01.709> defending<00:03:01.769> what's 00:03:02.390 --> 00:03:02.400 align:start position:0% protecting and defending what's 00:03:02.400 --> 00:03:05.030 align:start position:0% protecting and defending what's important<00:03:02.849> to<00:03:03.000> you<00:03:03.209> your<00:03:03.660> communities<00:03:04.319> and 00:03:05.030 --> 00:03:05.040 align:start position:0% important to you your communities and 00:03:05.040 --> 00:03:08.509 align:start position:0% important to you your communities and the<00:03:05.640> conditions<00:03:06.239> right<00:03:06.420> for<00:03:07.069> one<00:03:08.069> there 00:03:08.509 --> 00:03:08.519 align:start position:0% the conditions right for one there 00:03:08.519 --> 00:03:10.699 align:start position:0% the conditions right for one there especially<00:03:08.849> public<00:03:09.239> activity<00:03:10.019> there's 00:03:10.699 --> 00:03:10.709 align:start position:0% especially public activity there's 00:03:10.709 --> 00:03:13.759 align:start position:0% especially public activity there's opportunity<00:03:11.549> rigor<00:03:12.200> minimization<00:03:13.200> and<00:03:13.620> the 00:03:13.759 --> 00:03:13.769 align:start position:0% opportunity rigor minimization and the 00:03:13.769 --> 00:03:15.890 align:start position:0% opportunity rigor minimization and the compartment<00:03:14.340> ation<00:03:14.730> is<00:03:14.880> extremely<00:03:15.390> important 00:03:15.890 --> 00:03:15.900 align:start position:0% compartment ation is extremely important 00:03:15.900 --> 00:03:17.449 align:start position:0% compartment ation is extremely important making<00:03:16.350> sure<00:03:16.470> that<00:03:16.620> you're<00:03:16.739> not<00:03:16.859> putting<00:03:16.920> all 00:03:17.449 --> 00:03:17.459 align:start position:0% making sure that you're not putting all 00:03:17.459 --> 00:03:19.130 align:start position:0% making sure that you're not putting all of<00:03:17.489> your<00:03:17.790> most<00:03:18.000> valuable<00:03:18.420> things<00:03:18.750> in<00:03:18.900> one 00:03:19.130 --> 00:03:19.140 align:start position:0% of your most valuable things in one 00:03:19.140 --> 00:03:37.350 align:start position:0% of your most valuable things in one place<00:03:19.730> but<00:03:20.730> you're<00:03:21.120> distributing<00:03:21.450> them 00:03:37.350 --> 00:03:37.360 align:start position:0% 00:03:37.360 --> 00:03:39.670 align:start position:0% personality<00:03:38.360> and<00:03:38.990> what<00:03:39.140> we<00:03:39.260> do<00:03:39.380> a<00:03:39.410> little 00:03:39.670 --> 00:03:39.680 align:start position:0% personality and what we do a little 00:03:39.680 --> 00:03:42.180 align:start position:0% personality and what we do a little extra<00:03:40.130> things<00:03:40.400> but<00:03:40.910> these<00:03:41.240> principles 00:03:42.180 --> 00:03:42.190 align:start position:0% extra things but these principles 00:03:42.190 --> 00:03:45.760 align:start position:0% extra things but these principles especially<00:03:43.190> if<00:03:43.370> you<00:03:44.320> help<00:03:45.320> improve<00:03:45.740> your 00:03:45.760 --> 00:03:45.770 align:start position:0% especially if you help improve your 00:03:45.770 --> 00:03:48.280 align:start position:0% especially if you help improve your thinking<00:03:46.340> about<00:03:46.730> practice<00:03:47.300> in<00:03:47.600> the<00:03:47.780> security 00:03:48.280 --> 00:03:48.290 align:start position:0% thinking about practice in the security 00:03:48.290 --> 00:03:50.470 align:start position:0% thinking about practice in the security space<00:03:48.640> there's<00:03:49.640> some<00:03:49.760> other<00:03:49.880> aspects<00:03:50.390> of 00:03:50.470 --> 00:03:50.480 align:start position:0% space there's some other aspects of 00:03:50.480 --> 00:03:52.860 align:start position:0% space there's some other aspects of security<00:03:50.960> that<00:03:51.560> are<00:03:51.800> incredibly<00:03:52.400> difficult 00:03:52.860 --> 00:03:52.870 align:start position:0% security that are incredibly difficult 00:03:52.870 --> 00:03:56.650 align:start position:0% security that are incredibly difficult technical<00:03:53.870> piece<00:03:54.790> of<00:03:55.790> us<00:03:55.910> get<00:03:56.060> very<00:03:56.240> excited 00:03:56.650 --> 00:03:56.660 align:start position:0% technical piece of us get very excited 00:03:56.660 --> 00:03:58.480 align:start position:0% technical piece of us get very excited about<00:03:56.690> it<00:03:56.990> but<00:03:57.500> there's<00:03:57.710> also<00:03:57.860> a<00:03:57.980> human<00:03:58.280> thing 00:03:58.480 --> 00:03:58.490 align:start position:0% about it but there's also a human thing 00:03:58.490 --> 00:04:01.090 align:start position:0% about it but there's also a human thing because<00:03:59.180> humans<00:04:00.020> are<00:04:00.170> very<00:04:00.200> very<00:04:00.860> difficult 00:04:01.090 --> 00:04:01.100 align:start position:0% because humans are very very difficult 00:04:01.100 --> 00:04:05.530 align:start position:0% because humans are very very difficult to<00:04:02.650> Courtney<00:04:03.650> and<00:04:03.950> organize<00:04:04.490> and<00:04:04.790> manage<00:04:05.030> when 00:04:05.530 --> 00:04:05.540 align:start position:0% to Courtney and organize and manage when 00:04:05.540 --> 00:04:08.170 align:start position:0% to Courtney and organize and manage when we<00:04:05.720> have<00:04:05.930> very<00:04:06.230> strong<00:04:06.640> intense<00:04:07.640> emotions 00:04:08.170 --> 00:04:08.180 align:start position:0% we have very strong intense emotions 00:04:08.180 --> 00:04:10.960 align:start position:0% we have very strong intense emotions like<00:04:08.840> fear<00:04:09.020> which<00:04:09.620> is<00:04:09.920> kind<00:04:10.370> of<00:04:10.490> a<00:04:10.580> big<00:04:10.760> deal 00:04:10.960 --> 00:04:10.970 align:start position:0% like fear which is kind of a big deal 00:04:10.970 --> 00:04:12.850 align:start position:0% like fear which is kind of a big deal when<00:04:11.600> you're<00:04:11.840> in<00:04:11.930> the<00:04:12.020> middle<00:04:12.230> of<00:04:12.260> a<00:04:12.380> security 00:04:12.850 --> 00:04:12.860 align:start position:0% when you're in the middle of a security 00:04:12.860 --> 00:04:15.130 align:start position:0% when you're in the middle of a security emergency<00:04:12.980> and<00:04:13.700> you<00:04:14.180> think<00:04:14.450> this<00:04:14.630> thing<00:04:14.870> you 00:04:15.130 --> 00:04:15.140 align:start position:0% emergency and you think this thing you 00:04:15.140 --> 00:04:18.430 align:start position:0% emergency and you think this thing you might<00:04:15.290> have<00:04:15.350> done<00:04:15.590> is<00:04:15.800> zero<00:04:16.160> day<00:04:17.170> there's<00:04:18.170> also 00:04:18.430 --> 00:04:18.440 align:start position:0% might have done is zero day there's also 00:04:18.440 --> 00:04:20.289 align:start position:0% might have done is zero day there's also the<00:04:18.830> question<00:04:18.950> of<00:04:19.280> being<00:04:19.459> proactive<00:04:19.820> about 00:04:20.289 --> 00:04:20.299 align:start position:0% the question of being proactive about 00:04:20.299 --> 00:04:23.140 align:start position:0% the question of being proactive about security<00:04:20.930> meaning<00:04:21.769> that<00:04:21.799> you<00:04:22.460> try<00:04:22.820> to<00:04:22.850> stop 00:04:23.140 --> 00:04:23.150 align:start position:0% security meaning that you try to stop 00:04:23.150 --> 00:04:24.820 align:start position:0% security meaning that you try to stop bad<00:04:23.390> things<00:04:23.420> from<00:04:23.780> happening<00:04:23.930> and<00:04:24.560> you 00:04:24.820 --> 00:04:24.830 align:start position:0% bad things from happening and you 00:04:24.830 --> 00:04:28.750 align:start position:0% bad things from happening and you identify<00:04:25.070> risk<00:04:25.760> early<00:04:26.210> and<00:04:26.510> you<00:04:27.080> step<00:04:27.530> in<00:04:27.760> and 00:04:28.750 --> 00:04:28.760 align:start position:0% identify risk early and you step in and 00:04:28.760 --> 00:04:30.700 align:start position:0% identify risk early and you step in and you<00:04:29.090> take<00:04:29.360> time<00:04:29.630> to<00:04:29.690> mitigate<00:04:30.260> problems 00:04:30.700 --> 00:04:30.710 align:start position:0% you take time to mitigate problems 00:04:30.710 --> 00:04:32.980 align:start position:0% you take time to mitigate problems before<00:04:30.950> they<00:04:31.400> really<00:04:31.760> become<00:04:32.180> emergencies 00:04:32.980 --> 00:04:32.990 align:start position:0% before they really become emergencies 00:04:32.990 --> 00:04:35.610 align:start position:0% before they really become emergencies and<00:04:33.260> then<00:04:33.800> there's<00:04:34.220> reactive<00:04:34.850> security 00:04:35.610 --> 00:04:35.620 align:start position:0% and then there's reactive security 00:04:35.620 --> 00:04:38.230 align:start position:0% and then there's reactive security incident<00:04:36.620> response<00:04:36.740> is<00:04:37.280> an<00:04:37.430> area<00:04:37.760> where<00:04:38.120> you 00:04:38.230 --> 00:04:38.240 align:start position:0% incident response is an area where you 00:04:38.240 --> 00:04:39.940 align:start position:0% incident response is an area where you can<00:04:38.390> be<00:04:38.540> proactive<00:04:39.320> and 00:04:39.940 --> 00:04:39.950 align:start position:0% can be proactive and 00:04:39.950 --> 00:04:42.610 align:start position:0% can be proactive and run<00:04:40.670> books<00:04:40.910> and<00:04:41.210> planning<00:04:41.690> for<00:04:41.900> emergencies 00:04:42.610 --> 00:04:42.620 align:start position:0% run books and planning for emergencies 00:04:42.620 --> 00:04:45.220 align:start position:0% run books and planning for emergencies that<00:04:42.890> will<00:04:43.550> naturally<00:04:43.850> come<00:04:44.570> up<00:04:44.600> in<00:04:44.960> the 00:04:45.220 --> 00:04:45.230 align:start position:0% that will naturally come up in the 00:04:45.230 --> 00:04:47.560 align:start position:0% that will naturally come up in the course<00:04:45.440> of<00:04:45.650> running<00:04:45.770> the<00:04:45.980> watching<00:04:46.570> but 00:04:47.560 --> 00:04:47.570 align:start position:0% course of running the watching but 00:04:47.570 --> 00:04:50.410 align:start position:0% course of running the watching but reactive<00:04:48.530> because<00:04:49.100> you<00:04:49.460> basically<00:04:49.700> have<00:04:50.270> to 00:04:50.410 --> 00:04:50.420 align:start position:0% reactive because you basically have to 00:04:50.420 --> 00:04:52.840 align:start position:0% reactive because you basically have to detect<00:04:50.960> that<00:04:51.590> this<00:04:51.770> badness<00:04:52.280> has<00:04:52.430> happened 00:04:52.840 --> 00:04:52.850 align:start position:0% detect that this badness has happened 00:04:52.850 --> 00:04:54.610 align:start position:0% detect that this badness has happened where<00:04:53.120> this<00:04:53.210> incident<00:04:53.780> is<00:04:53.900> occurring<00:04:54.380> and 00:04:54.610 --> 00:04:54.620 align:start position:0% where this incident is occurring and 00:04:54.620 --> 00:04:56.590 align:start position:0% where this incident is occurring and then<00:04:55.190> spring<00:04:55.580> into<00:04:55.910> action 00:04:56.590 --> 00:04:56.600 align:start position:0% then spring into action 00:04:56.600 --> 00:04:59.620 align:start position:0% then spring into action there's<00:04:57.230> also<00:04:57.500> a<00:04:58.100> very<00:04:58.700> very<00:04:58.820> deep<00:04:59.360> line 00:04:59.620 --> 00:04:59.630 align:start position:0% there's also a very very deep line 00:04:59.630 --> 00:05:02.560 align:start position:0% there's also a very very deep line between<00:05:00.220> offensive<00:05:01.220> security<00:05:01.760> and<00:05:02.030> defensive 00:05:02.560 --> 00:05:02.570 align:start position:0% between offensive security and defensive 00:05:02.570 --> 00:05:05.860 align:start position:0% between offensive security and defensive security<00:05:03.580> in<00:05:04.580> the<00:05:04.760> security<00:05:05.270> space 00:05:05.860 --> 00:05:05.870 align:start position:0% security in the security space 00:05:05.870 --> 00:05:09.040 align:start position:0% security in the security space I<00:05:05.900> am<00:05:06.410> hardcore<00:05:07.070> blue<00:05:07.280> team<00:05:07.520> you<00:05:08.270> name<00:05:08.450> I<00:05:08.660> wanna 00:05:09.040 --> 00:05:09.050 align:start position:0% I am hardcore blue team you name I wanna 00:05:09.050 --> 00:05:10.660 align:start position:0% I am hardcore blue team you name I wanna build<00:05:09.200> defenses<00:05:09.410> I'm<00:05:10.100> going<00:05:10.340> to<00:05:10.400> protect 00:05:10.660 --> 00:05:10.670 align:start position:0% build defenses I'm going to protect 00:05:10.670 --> 00:05:12.760 align:start position:0% build defenses I'm going to protect people<00:05:11.090> I<00:05:11.300> want<00:05:11.480> to<00:05:11.510> protect<00:05:11.660> a<00:05:12.020> news<00:05:12.290> I<00:05:12.470> want 00:05:12.760 --> 00:05:12.770 align:start position:0% people I want to protect a news I want 00:05:12.770 --> 00:05:15.670 align:start position:0% people I want to protect a news I want to<00:05:12.890> care<00:05:13.190> for<00:05:13.460> and<00:05:13.760> maintain<00:05:13.820> things<00:05:14.600> a<00:05:14.960> lot 00:05:15.670 --> 00:05:15.680 align:start position:0% to care for and maintain things a lot 00:05:15.680 --> 00:05:18.700 align:start position:0% to care for and maintain things a lot but<00:05:16.430> offensive<00:05:17.420> security<00:05:17.900> can<00:05:18.320> be<00:05:18.350> very 00:05:18.700 --> 00:05:18.710 align:start position:0% but offensive security can be very 00:05:18.710 --> 00:05:23.830 align:start position:0% but offensive security can be very important<00:05:21.610> are<00:05:22.610> in<00:05:22.940> space<00:05:23.360> freighter<00:05:23.720> that 00:05:23.830 --> 00:05:23.840 align:start position:0% important are in space freighter that 00:05:23.840 --> 00:05:26.830 align:start position:0% important are in space freighter that much<00:05:24.140> work<00:05:24.560> and<00:05:24.730> attacking<00:05:25.730> things<00:05:26.210> and<00:05:26.510> going 00:05:26.830 --> 00:05:26.840 align:start position:0% much work and attacking things and going 00:05:26.840 --> 00:05:28.720 align:start position:0% much work and attacking things and going after<00:05:27.140> them<00:05:27.320> and<00:05:27.590> deeply<00:05:28.070> understanding 00:05:28.720 --> 00:05:28.730 align:start position:0% after them and deeply understanding 00:05:28.730 --> 00:05:31.360 align:start position:0% after them and deeply understanding there<00:05:28.880> are<00:05:29.000> they<00:05:29.090> break<00:05:29.390> can<00:05:30.200> inform<00:05:30.710> how<00:05:31.310> do 00:05:31.360 --> 00:05:31.370 align:start position:0% there are they break can inform how do 00:05:31.370 --> 00:05:34.330 align:start position:0% there are they break can inform how do you<00:05:31.520> run<00:05:31.730> your<00:05:31.910> defense<00:05:33.070> some<00:05:34.070> of<00:05:34.160> the<00:05:34.220> ways 00:05:34.330 --> 00:05:34.340 align:start position:0% you run your defense some of the ways 00:05:34.340 --> 00:05:36.190 align:start position:0% you run your defense some of the ways that<00:05:34.370> you<00:05:34.610> see<00:05:34.640> security<00:05:35.120> happen<00:05:35.690> in<00:05:35.900> planning 00:05:36.190 --> 00:05:36.200 align:start position:0% that you see security happen in planning 00:05:36.200 --> 00:05:38.860 align:start position:0% that you see security happen in planning organizations<00:05:36.920> tend<00:05:37.910> to<00:05:38.090> become<00:05:38.240> security 00:05:38.860 --> 00:05:38.870 align:start position:0% organizations tend to become security 00:05:38.870 --> 00:05:41.230 align:start position:0% organizations tend to become security programs<00:05:39.580> depending<00:05:40.580> on<00:05:40.850> what<00:05:41.090> your 00:05:41.230 --> 00:05:41.240 align:start position:0% programs depending on what your 00:05:41.240 --> 00:05:43.180 align:start position:0% programs depending on what your organization<00:05:41.930> does<00:05:41.960> you<00:05:42.500> can<00:05:42.650> have<00:05:42.770> product 00:05:43.180 --> 00:05:43.190 align:start position:0% organization does you can have product 00:05:43.190 --> 00:05:45.160 align:start position:0% organization does you can have product security<00:05:43.730> could<00:05:44.030> have<00:05:44.090> application<00:05:44.810> security 00:05:45.160 --> 00:05:45.170 align:start position:0% security could have application security 00:05:45.170 --> 00:05:47.440 align:start position:0% security could have application security or<00:05:45.530> infrastructure<00:05:46.100> security<00:05:46.400> they<00:05:47.180> can<00:05:47.330> all 00:05:47.440 --> 00:05:47.450 align:start position:0% or infrastructure security they can all 00:05:47.450 --> 00:05:49.240 align:start position:0% or infrastructure security they can all be<00:05:47.600> in<00:05:47.690> one<00:05:47.900> room<00:05:48.110> they<00:05:48.560> would<00:05:48.830> be<00:05:48.920> separate 00:05:49.240 --> 00:05:49.250 align:start position:0% be in one room they would be separate 00:05:49.250 --> 00:05:51.700 align:start position:0% be in one room they would be separate programs<00:05:49.760> it<00:05:50.360> really<00:05:50.810> depends<00:05:51.380> on<00:05:51.500> how 00:05:51.700 --> 00:05:51.710 align:start position:0% programs it really depends on how 00:05:51.710 --> 00:05:55.950 align:start position:0% programs it really depends on how critical<00:05:52.190> each<00:05:52.460> of<00:05:52.610> those<00:05:52.760> things 00:05:55.950 --> 00:05:55.960 align:start position:0% 00:05:55.960 --> 00:05:58.950 align:start position:0% and<00:05:56.139> the<00:05:56.320> operation<00:05:56.830> of<00:05:56.919> your<00:05:57.070> network<00:05:57.960> but 00:05:58.950 --> 00:05:58.960 align:start position:0% and the operation of your network but 00:05:58.960 --> 00:06:01.350 align:start position:0% and the operation of your network but then<00:05:59.110> there<00:05:59.229> are<00:05:59.290> also<00:05:59.440> things<00:05:59.770> that<00:06:00.210> we<00:06:01.210> don't 00:06:01.350 --> 00:06:01.360 align:start position:0% then there are also things that we don't 00:06:01.360 --> 00:06:04.529 align:start position:0% then there are also things that we don't really<00:06:01.660> cover<00:06:02.290> as<00:06:02.530> much<00:06:02.770> that<00:06:03.370> are<00:06:03.669> just<00:06:04.360> as 00:06:04.529 --> 00:06:04.539 align:start position:0% really cover as much that are just as 00:06:04.539 --> 00:06:06.110 align:start position:0% really cover as much that are just as important<00:06:05.020> as<00:06:05.139> the<00:06:05.259> technical<00:06:05.380> ones 00:06:06.110 --> 00:06:06.120 align:start position:0% important as the technical ones 00:06:06.120 --> 00:06:08.370 align:start position:0% important as the technical ones operational<00:06:07.120> security<00:06:07.479> is<00:06:07.930> one<00:06:08.169> of<00:06:08.289> the 00:06:08.370 --> 00:06:08.380 align:start position:0% operational security is one of the 00:06:08.380 --> 00:06:11.310 align:start position:0% operational security is one of the things<00:06:08.650> that<00:06:08.979> watching<00:06:09.400> space<00:06:09.699> and<00:06:10.320> very 00:06:11.310 --> 00:06:11.320 align:start position:0% things that watching space and very 00:06:11.320 --> 00:06:13.320 align:start position:0% things that watching space and very significantly<00:06:12.100> behind<00:06:12.639> where<00:06:12.910> it<00:06:13.000> needs<00:06:13.210> to 00:06:13.320 --> 00:06:13.330 align:start position:0% significantly behind where it needs to 00:06:13.330 --> 00:06:17.189 align:start position:0% significantly behind where it needs to be<00:06:13.560> at<00:06:14.560> the<00:06:14.710> airport<00:06:14.800> penguin<00:06:16.199> assessments 00:06:17.189 --> 00:06:17.199 align:start position:0% be at the airport penguin assessments 00:06:17.199 --> 00:06:23.129 align:start position:0% be at the airport penguin assessments are<00:06:17.410> difficult<00:06:18.039> I<00:06:18.780> run<00:06:21.210> security<00:06:22.210> on<00:06:22.810> it's<00:06:22.990> in 00:06:23.129 --> 00:06:23.139 align:start position:0% are difficult I run security on it's in 00:06:23.139 --> 00:06:25.920 align:start position:0% are difficult I run security on it's in the<00:06:23.199> last<00:06:23.440> two<00:06:23.800> years<00:06:23.830> okay<00:06:24.539> well<00:06:25.539> it<00:06:25.690> would<00:06:25.900> be 00:06:25.920 --> 00:06:25.930 align:start position:0% the last two years okay well it would be 00:06:25.930 --> 00:06:27.150 align:start position:0% the last two years okay well it would be important<00:06:26.410> to<00:06:26.440> make<00:06:26.590> sure<00:06:26.650> that<00:06:26.889> you<00:06:26.979> have 00:06:27.150 --> 00:06:27.160 align:start position:0% important to make sure that you have 00:06:27.160 --> 00:06:28.980 align:start position:0% important to make sure that you have someone<00:06:27.370> independently<00:06:28.180> evaluating<00:06:28.900> your 00:06:28.980 --> 00:06:28.990 align:start position:0% someone independently evaluating your 00:06:28.990 --> 00:06:31.620 align:start position:0% someone independently evaluating your codes<00:06:29.320> all<00:06:30.190> of<00:06:30.430> the<00:06:30.520> business<00:06:30.820> negotiation 00:06:31.620 --> 00:06:31.630 align:start position:0% codes all of the business negotiation 00:06:31.630 --> 00:06:33.659 align:start position:0% codes all of the business negotiation that<00:06:31.960> goes<00:06:31.990> online<00:06:32.320> and<00:06:32.650> scoping<00:06:33.160> out<00:06:33.280> and<00:06:33.520> on 00:06:33.659 --> 00:06:33.669 align:start position:0% that goes online and scoping out and on 00:06:33.669 --> 00:06:35.640 align:start position:0% that goes online and scoping out and on it<00:06:33.880> and<00:06:34.060> defining<00:06:34.690> the<00:06:34.780> testing<00:06:35.199> you<00:06:35.229> need<00:06:35.470> to 00:06:35.640 --> 00:06:35.650 align:start position:0% it and defining the testing you need to 00:06:35.650 --> 00:06:38.400 align:start position:0% it and defining the testing you need to do<00:06:35.830> these<00:06:36.490> are<00:06:36.789> things<00:06:37.090> that<00:06:37.240> are<00:06:37.510> hard<00:06:37.750> they 00:06:38.400 --> 00:06:38.410 align:start position:0% do these are things that are hard they 00:06:38.410 --> 00:06:40.920 align:start position:0% do these are things that are hard they are<00:06:38.550> immensely<00:06:39.550> difficult<00:06:40.090> to<00:06:40.479> do<00:06:40.630> if<00:06:40.780> you've 00:06:40.920 --> 00:06:40.930 align:start position:0% are immensely difficult to do if you've 00:06:40.930 --> 00:06:43.740 align:start position:0% are immensely difficult to do if you've never<00:06:41.080> heard<00:06:41.320> before<00:06:41.560> like<00:06:42.400> how<00:06:42.940> to<00:06:43.270> think 00:06:43.740 --> 00:06:43.750 align:start position:0% never heard before like how to think 00:06:43.750 --> 00:06:45.120 align:start position:0% never heard before like how to think about<00:06:43.810> them<00:06:44.139> in<00:06:44.260> a<00:06:44.320> comprehensive<00:06:45.039> and 00:06:45.120 --> 00:06:45.130 align:start position:0% about them in a comprehensive and 00:06:45.130 --> 00:06:47.370 align:start position:0% about them in a comprehensive and programmatic<00:06:45.490> way<00:06:45.910> to<00:06:46.600> make<00:06:46.750> sure<00:06:46.990> that<00:06:47.169> that 00:06:47.370 --> 00:06:47.380 align:start position:0% programmatic way to make sure that that 00:06:47.380 --> 00:06:48.950 align:start position:0% programmatic way to make sure that that bought<00:06:47.650> it<00:06:47.830> you're<00:06:48.070> releasing<00:06:48.400> to<00:06:48.699> the<00:06:48.760> public 00:06:48.950 --> 00:06:48.960 align:start position:0% bought it you're releasing to the public 00:06:48.960 --> 00:06:51.659 align:start position:0% bought it you're releasing to the public actually<00:06:49.960> does<00:06:50.530> attest<00:06:50.979> to<00:06:51.070> the<00:06:51.280> things<00:06:51.490> that 00:06:51.659 --> 00:06:51.669 align:start position:0% actually does attest to the things that 00:06:51.669 --> 00:06:53.520 align:start position:0% actually does attest to the things that you're<00:06:51.820> claiming<00:06:52.060> it<00:06:52.300> does<00:06:52.479> and<00:06:52.960> we've<00:06:53.169> chosen 00:06:53.520 --> 00:06:53.530 align:start position:0% you're claiming it does and we've chosen 00:06:53.530 --> 00:06:55.620 align:start position:0% you're claiming it does and we've chosen the<00:06:53.860> correct<00:06:54.009> remediation<00:06:54.849> steps<00:06:55.150> to<00:06:55.479> close 00:06:55.620 --> 00:06:55.630 align:start position:0% the correct remediation steps to close 00:06:55.630 --> 00:06:57.719 align:start position:0% the correct remediation steps to close bugs<00:06:55.990> or<00:06:56.349> issues<00:06:56.710> that<00:06:56.740> were<00:06:57.070> surfaced<00:06:57.460> within 00:06:57.719 --> 00:06:57.729 align:start position:0% bugs or issues that were surfaced within 00:06:57.729 --> 00:06:59.879 align:start position:0% bugs or issues that were surfaced within me<00:06:57.820> on<00:06:57.940> it<00:06:58.120> and<00:06:58.389> then<00:06:59.139> there's<00:06:59.320> education 00:06:59.879 --> 00:06:59.889 align:start position:0% me on it and then there's education 00:06:59.889 --> 00:07:02.430 align:start position:0% me on it and then there's education that's<00:07:00.880> also<00:07:01.300> extremely<00:07:01.539> difficult<00:07:02.020> if 00:07:02.430 --> 00:07:02.440 align:start position:0% that's also extremely difficult if 00:07:02.440 --> 00:07:11.399 align:start position:0% that's also extremely difficult if you're<00:07:02.770> in<00:07:02.979> a<00:07:03.099> smaller<00:07:03.400> company<00:07:09.900> an<00:07:10.900> incident 00:07:11.399 --> 00:07:11.409 align:start position:0% you're in a smaller company an incident 00:07:11.409 --> 00:07:14.070 align:start position:0% you're in a smaller company an incident response<00:07:11.560> which<00:07:12.400> is<00:07:12.820> the<00:07:13.030> one<00:07:13.300> for<00:07:13.690> me<00:07:13.810> that 00:07:14.070 --> 00:07:14.080 align:start position:0% response which is the one for me that 00:07:14.080 --> 00:07:15.810 align:start position:0% response which is the one for me that has<00:07:14.169> been<00:07:14.440> the<00:07:14.620> most<00:07:14.800> interesting<00:07:15.220> and 00:07:15.810 --> 00:07:15.820 align:start position:0% has been the most interesting and 00:07:15.820 --> 00:07:18.990 align:start position:0% has been the most interesting and watching<00:07:16.300> space<00:07:16.570> because<00:07:17.580> other<00:07:18.580> people<00:07:18.940> in 00:07:18.990 --> 00:07:19.000 align:start position:0% watching space because other people in 00:07:19.000 --> 00:07:22.620 align:start position:0% watching space because other people in conventional<00:07:19.599> technology<00:07:21.120> but<00:07:22.120> I<00:07:22.150> also<00:07:22.330> get 00:07:22.620 --> 00:07:22.630 align:start position:0% conventional technology but I also get 00:07:22.630 --> 00:07:25.200 align:start position:0% conventional technology but I also get challenges<00:07:23.320> that<00:07:23.590> they<00:07:23.740> maybe<00:07:24.610> wouldn't<00:07:25.060> know 00:07:25.200 --> 00:07:25.210 align:start position:0% challenges that they maybe wouldn't know 00:07:25.210 --> 00:07:27.240 align:start position:0% challenges that they maybe wouldn't know how<00:07:25.389> to<00:07:25.449> solve<00:07:25.750> even<00:07:26.229> if<00:07:26.320> we<00:07:26.470> told<00:07:26.620> them<00:07:26.860> which 00:07:27.240 --> 00:07:27.250 align:start position:0% how to solve even if we told them which 00:07:27.250 --> 00:07:30.120 align:start position:0% how to solve even if we told them which is<00:07:27.400> kind<00:07:27.550> of<00:07:27.699> exciting<00:07:28.000> and<00:07:28.479> I<00:07:28.990> personally<00:07:29.949> am 00:07:30.120 --> 00:07:30.130 align:start position:0% is kind of exciting and I personally am 00:07:30.130 --> 00:07:31.170 align:start position:0% is kind of exciting and I personally am very<00:07:30.490> competitive 00:07:31.170 --> 00:07:31.180 align:start position:0% very competitive 00:07:31.180 --> 00:07:33.810 align:start position:0% very competitive with<00:07:31.389> security<00:07:31.750> like<00:07:32.260> I<00:07:32.470> want<00:07:32.740> us<00:07:32.949> as<00:07:33.370> a<00:07:33.430> space 00:07:33.810 --> 00:07:33.820 align:start position:0% with security like I want us as a space 00:07:33.820 --> 00:07:36.779 align:start position:0% with security like I want us as a space to<00:07:34.090> win<00:07:34.419> I<00:07:34.750> want<00:07:35.349> to<00:07:35.409> I<00:07:35.710> want<00:07:36.250> to<00:07:36.520> be<00:07:36.610> like 00:07:36.779 --> 00:07:36.789 align:start position:0% to win I want to I want to be like 00:07:36.789 --> 00:07:37.430 align:start position:0% to win I want to I want to be like looking 00:07:37.430 --> 00:07:37.440 align:start position:0% looking 00:07:37.440 --> 00:07:39.200 align:start position:0% looking while<00:07:37.920> everyone<00:07:38.310> is<00:07:38.430> making<00:07:38.670> stupid 00:07:39.200 --> 00:07:39.210 align:start position:0% while everyone is making stupid 00:07:39.210 --> 00:07:41.420 align:start position:0% while everyone is making stupid blockchain<00:07:39.690> jokes<00:07:39.960> so<00:07:40.830> this<00:07:41.010> incident 00:07:41.420 --> 00:07:41.430 align:start position:0% blockchain jokes so this incident 00:07:41.430 --> 00:07:43.280 align:start position:0% blockchain jokes so this incident response<00:07:41.820> areas<00:07:42.210> thanks<00:07:42.690> for<00:07:42.840> thanking<00:07:43.110> me<00:07:43.260> a 00:07:43.280 --> 00:07:43.290 align:start position:0% response areas thanks for thanking me a 00:07:43.290 --> 00:07:46.100 align:start position:0% response areas thanks for thanking me a huge<00:07:43.680> opportunity<00:07:43.980> to<00:07:44.370> shine<00:07:44.600> Wow<00:07:45.660> and<00:07:45.990> then 00:07:46.100 --> 00:07:46.110 align:start position:0% huge opportunity to shine Wow and then 00:07:46.110 --> 00:07:47.330 align:start position:0% huge opportunity to shine Wow and then there's<00:07:46.260> just<00:07:46.410> a<00:07:46.500> couple<00:07:46.650> of<00:07:46.830> other<00:07:46.980> things 00:07:47.330 --> 00:07:47.340 align:start position:0% there's just a couple of other things 00:07:47.340 --> 00:07:49.700 align:start position:0% there's just a couple of other things about<00:07:47.580> security<00:07:48.390> that<00:07:48.810> I've<00:07:48.990> really<00:07:49.410> learned 00:07:49.700 --> 00:07:49.710 align:start position:0% about security that I've really learned 00:07:49.710 --> 00:07:51.430 align:start position:0% about security that I've really learned and<00:07:50.010> taken<00:07:50.340> to<00:07:50.430> hearts<00:07:50.640> and<00:07:50.790> practitioner 00:07:51.430 --> 00:07:51.440 align:start position:0% and taken to hearts and practitioner 00:07:51.440 --> 00:07:53.330 align:start position:0% and taken to hearts and practitioner security<00:07:52.440> is<00:07:52.530> very<00:07:52.770> much<00:07:52.920> a<00:07:52.950> shared 00:07:53.330 --> 00:07:53.340 align:start position:0% security is very much a shared 00:07:53.340 --> 00:07:56.210 align:start position:0% security is very much a shared responsibility<00:07:54.530> there's<00:07:55.530> only<00:07:55.680> so<00:07:55.920> much<00:07:56.040> I 00:07:56.210 --> 00:07:56.220 align:start position:0% responsibility there's only so much I 00:07:56.220 --> 00:07:58.250 align:start position:0% responsibility there's only so much I can<00:07:56.340> do<00:07:56.670> is<00:07:56.820> core<00:07:57.120> maintainer<00:07:57.540> or<00:07:57.810> a<00:07:57.930> core 00:07:58.250 --> 00:07:58.260 align:start position:0% can do is core maintainer or a core 00:07:58.260 --> 00:08:00.380 align:start position:0% can do is core maintainer or a core developer<00:07:58.320> to<00:07:59.190> make<00:07:59.430> my<00:07:59.580> community<00:07:59.760> secure 00:08:00.380 --> 00:08:00.390 align:start position:0% developer to make my community secure 00:08:00.390 --> 00:08:03.020 align:start position:0% developer to make my community secure there's<00:08:00.720> lots<00:08:00.990> of<00:08:01.140> stuff<00:08:01.440> that<00:08:01.710> I<00:08:02.040> need<00:08:02.730> them 00:08:03.020 --> 00:08:03.030 align:start position:0% there's lots of stuff that I need them 00:08:03.030 --> 00:08:06.350 align:start position:0% there's lots of stuff that I need them to<00:08:03.270> do<00:08:03.480> and<00:08:03.780> to<00:08:03.900> be<00:08:03.930> set<00:08:04.260> up<00:08:04.470> to<00:08:04.500> do<00:08:04.830> to<00:08:05.520> help<00:08:05.730> so 00:08:06.350 --> 00:08:06.360 align:start position:0% to do and to be set up to do to help so 00:08:06.360 --> 00:08:08.270 align:start position:0% to do and to be set up to do to help so that<00:08:06.480> we're<00:08:06.600> able<00:08:06.780> to<00:08:07.320> quickly<00:08:07.920> resolve 00:08:08.270 --> 00:08:08.280 align:start position:0% that we're able to quickly resolve 00:08:08.280 --> 00:08:11.870 align:start position:0% that we're able to quickly resolve issues<00:08:08.670> and<00:08:09.210> build<00:08:09.450> immunity<00:08:10.400> and<00:08:11.400> security 00:08:11.870 --> 00:08:11.880 align:start position:0% issues and build immunity and security 00:08:11.880 --> 00:08:13.370 align:start position:0% issues and build immunity and security is<00:08:11.940> definitely<00:08:12.480> much<00:08:12.720> much<00:08:12.960> more<00:08:13.200> than 00:08:13.370 --> 00:08:13.380 align:start position:0% is definitely much much more than 00:08:13.380 --> 00:08:16.010 align:start position:0% is definitely much much more than funding<00:08:13.680> all<00:08:14.130> of<00:08:14.160> the<00:08:14.400> bugs<00:08:14.610> in<00:08:14.820> code<00:08:14.850> the<00:08:15.720> next 00:08:16.010 --> 00:08:16.020 align:start position:0% funding all of the bugs in code the next 00:08:16.020 --> 00:08:17.330 align:start position:0% funding all of the bugs in code the next time<00:08:16.170> I'm<00:08:16.290> in<00:08:16.350> it<00:08:16.500> tells<00:08:16.710> me<00:08:16.860> it's<00:08:16.980> my<00:08:17.130> job<00:08:17.310> to 00:08:17.330 --> 00:08:17.340 align:start position:0% time I'm in it tells me it's my job to 00:08:17.340 --> 00:08:19.580 align:start position:0% time I'm in it tells me it's my job to find<00:08:17.610> all<00:08:17.790> of<00:08:17.820> the<00:08:18.060> bugs<00:08:18.270> I'm<00:08:18.930> going<00:08:19.170> to<00:08:19.260> get<00:08:19.380> a 00:08:19.580 --> 00:08:19.590 align:start position:0% find all of the bugs I'm going to get a 00:08:19.590 --> 00:08:22.880 align:start position:0% find all of the bugs I'm going to get a level<00:08:19.890> of<00:08:20.160> staff<00:08:20.400> see<00:08:20.640> that<00:08:21.440> it's<00:08:22.440> relatively 00:08:22.880 --> 00:08:22.890 align:start position:0% level of staff see that it's relatively 00:08:22.890 --> 00:08:24.890 align:start position:0% level of staff see that it's relatively unmatched<00:08:23.460> for<00:08:23.760> me<00:08:23.910> and<00:08:24.180> give<00:08:24.330> them<00:08:24.450> a<00:08:24.540> lecture 00:08:24.890 --> 00:08:24.900 align:start position:0% unmatched for me and give them a lecture 00:08:24.900 --> 00:08:27.170 align:start position:0% unmatched for me and give them a lecture about<00:08:24.990> stopping<00:08:25.650> the<00:08:25.800> bugs<00:08:25.980> from<00:08:26.190> definitely 00:08:27.170 --> 00:08:27.180 align:start position:0% about stopping the bugs from definitely 00:08:27.180 --> 00:08:29.440 align:start position:0% about stopping the bugs from definitely more<00:08:27.900> than<00:08:28.050> anything<00:08:28.290> else<00:08:28.620> though 00:08:29.440 --> 00:08:29.450 align:start position:0% more than anything else though 00:08:29.450 --> 00:08:36.580 align:start position:0% more than anything else though Security's<00:08:30.450> really<00:08:30.720> don't<00:08:30.870> enable<00:08:31.080> in<00:08:31.380> and 00:08:36.580 --> 00:08:36.590 align:start position:0% 00:08:36.590 --> 00:08:39.020 align:start position:0% one<00:08:37.590> thing<00:08:37.770> that's<00:08:37.890> really<00:08:38.010> important<00:08:38.760> we<00:08:38.909> all 00:08:39.020 --> 00:08:39.030 align:start position:0% one thing that's really important we all 00:08:39.030 --> 00:08:41.500 align:start position:0% one thing that's really important we all know<00:08:39.210> Security's<00:08:39.750> never<00:08:40.050> going<00:08:40.260> to<00:08:40.320> be<00:08:40.469> a<00:08:40.830> late 00:08:41.500 --> 00:08:41.510 align:start position:0% know Security's never going to be a late 00:08:41.510 --> 00:08:45.620 align:start position:0% know Security's never going to be a late 100<00:08:42.510> percent<00:08:42.930> guaranteed<00:08:43.490> but<00:08:44.490> it's<00:08:45.450> more 00:08:45.620 --> 00:08:45.630 align:start position:0% 100 percent guaranteed but it's more 00:08:45.630 --> 00:08:47.030 align:start position:0% 100 percent guaranteed but it's more successful<00:08:46.320> when<00:08:46.470> we<00:08:46.530> make<00:08:46.770> it<00:08:46.890> more 00:08:47.030 --> 00:08:47.040 align:start position:0% successful when we make it more 00:08:47.040 --> 00:08:49.220 align:start position:0% successful when we make it more expensive<00:08:47.370> for<00:08:47.760> an<00:08:47.910> attacker<00:08:48.240> to<00:08:48.600> launch<00:08:48.930> a 00:08:49.220 --> 00:08:49.230 align:start position:0% expensive for an attacker to launch a 00:08:49.230 --> 00:08:51.440 align:start position:0% expensive for an attacker to launch a successful<00:08:49.740> attack<00:08:49.950> all<00:08:50.700> we<00:08:50.940> have<00:08:51.060> to<00:08:51.210> do<00:08:51.300> will 00:08:51.440 --> 00:08:51.450 align:start position:0% successful attack all we have to do will 00:08:51.450 --> 00:08:53.630 align:start position:0% successful attack all we have to do will be<00:08:51.570> one<00:08:51.810> is<00:08:52.320> where<00:08:52.560> the<00:08:52.740> attackers<00:08:53.160> are<00:08:53.250> and 00:08:53.630 --> 00:08:53.640 align:start position:0% be one is where the attackers are and 00:08:53.640 --> 00:08:55.400 align:start position:0% be one is where the attackers are and make<00:08:53.790> them<00:08:53.970> jump<00:08:54.120> through<00:08:54.330> hoops<00:08:54.360> and<00:08:54.870> lots<00:08:55.290> of 00:08:55.400 --> 00:08:55.410 align:start position:0% make them jump through hoops and lots of 00:08:55.410 --> 00:08:57.680 align:start position:0% make them jump through hoops and lots of money<00:08:55.590> and<00:08:55.920> have<00:08:56.100> to<00:08:56.130> do<00:08:56.430> things<00:08:56.700> that<00:08:56.940> are<00:08:57.090> not 00:08:57.680 --> 00:08:57.690 align:start position:0% money and have to do things that are not 00:08:57.690 --> 00:09:00.980 align:start position:0% money and have to do things that are not male<00:08:58.620> individual<00:08:59.460> scalable<00:09:00.120> I'm<00:09:00.690> too 00:09:00.980 --> 00:09:00.990 align:start position:0% male individual scalable I'm too 00:09:00.990 --> 00:09:03.170 align:start position:0% male individual scalable I'm too exhausting<00:09:01.560> and<00:09:01.860> maybe<00:09:02.340> if<00:09:02.580> not<00:09:02.760> make<00:09:02.910> them<00:09:03.060> go 00:09:03.170 --> 00:09:03.180 align:start position:0% exhausting and maybe if not make them go 00:09:03.180 --> 00:09:03.500 align:start position:0% exhausting and maybe if not make them go away 00:09:03.500 --> 00:09:03.510 align:start position:0% away 00:09:03.510 --> 00:09:05.330 align:start position:0% away make<00:09:04.170> them<00:09:04.320> leave<00:09:04.440> us<00:09:04.590> alone<00:09:04.710> for<00:09:05.100> a<00:09:05.130> while 00:09:05.330 --> 00:09:05.340 align:start position:0% make them leave us alone for a while 00:09:05.340 --> 00:09:09.290 align:start position:0% make them leave us alone for a while there<00:09:06.300> are<00:09:06.330> things<00:09:06.870> that<00:09:06.960> we<00:09:07.380> can<00:09:07.920> do<00:09:08.190> in<00:09:09.000> order 00:09:09.290 --> 00:09:09.300 align:start position:0% there are things that we can do in order 00:09:09.300 --> 00:09:12.120 align:start position:0% there are things that we can do in order to<00:09:09.480> plan<00:09:09.780> and<00:09:10.260> prepare<00:09:10.620> for<00:09:10.920> incident 00:09:12.120 --> 00:09:12.130 align:start position:0% to plan and prepare for incident 00:09:12.130 --> 00:09:15.240 align:start position:0% to plan and prepare for incident that<00:09:12.760> other<00:09:13.860> organizations<00:09:14.860> and<00:09:15.070> other 00:09:15.240 --> 00:09:15.250 align:start position:0% that other organizations and other 00:09:15.250 --> 00:09:17.820 align:start position:0% that other organizations and other technologies<00:09:15.940> can<00:09:16.300> but<00:09:17.200> more<00:09:17.410> than<00:09:17.560> anything 00:09:17.820 --> 00:09:17.830 align:start position:0% technologies can but more than anything 00:09:17.830 --> 00:09:19.710 align:start position:0% technologies can but more than anything else<00:09:18.130> it's<00:09:18.400> really<00:09:18.730> important<00:09:19.480> to<00:09:19.570> recognize 00:09:19.710 --> 00:09:19.720 align:start position:0% else it's really important to recognize 00:09:19.720 --> 00:09:23.490 align:start position:0% else it's really important to recognize the<00:09:20.440> decentralization<00:09:21.540> might<00:09:22.540> make<00:09:22.839> parts<00:09:23.290> of 00:09:23.490 --> 00:09:23.500 align:start position:0% the decentralization might make parts of 00:09:23.500 --> 00:09:26.579 align:start position:0% the decentralization might make parts of security<00:09:24.040> more<00:09:24.610> complex<00:09:25.060> it<00:09:25.870> doesn't<00:09:26.320> require 00:09:26.579 --> 00:09:26.589 align:start position:0% security more complex it doesn't require 00:09:26.589 --> 00:09:29.160 align:start position:0% security more complex it doesn't require us<00:09:26.890> to<00:09:26.920> reinvent<00:09:27.550> the<00:09:27.730> wheel<00:09:27.850> if<00:09:28.150> we<00:09:28.660> are<00:09:28.779> more 00:09:29.160 --> 00:09:29.170 align:start position:0% us to reinvent the wheel if we are more 00:09:29.170 --> 00:09:30.810 align:start position:0% us to reinvent the wheel if we are more busy<00:09:29.380> reinventing<00:09:29.770> the<00:09:30.220> wheel<00:09:30.339> than<00:09:30.610> anything 00:09:30.810 --> 00:09:30.820 align:start position:0% busy reinventing the wheel than anything 00:09:30.820 --> 00:09:32.460 align:start position:0% busy reinventing the wheel than anything else<00:09:31.089> we're<00:09:31.690> gonna<00:09:31.779> miss<00:09:32.020> a<00:09:32.050> lot<00:09:32.350> of 00:09:32.460 --> 00:09:32.470 align:start position:0% else we're gonna miss a lot of 00:09:32.470 --> 00:09:35.790 align:start position:0% else we're gonna miss a lot of opportunities<00:09:33.130> to<00:09:33.540> get<00:09:34.540> very<00:09:34.930> small<00:09:35.050> very 00:09:35.790 --> 00:09:35.800 align:start position:0% opportunities to get very small very 00:09:35.800 --> 00:09:39.590 align:start position:0% opportunities to get very small very nuanced<00:09:36.220> very<00:09:36.580> important<00:09:37.150> things<00:09:37.390> right<00:09:37.690> so 00:09:39.590 --> 00:09:39.600 align:start position:0% nuanced very important things right so 00:09:39.600 --> 00:09:42.990 align:start position:0% nuanced very important things right so this<00:09:40.600> is<00:09:40.779> the<00:09:40.930> story<00:09:41.230> of<00:09:41.320> time<00:09:41.730> once<00:09:42.730> upon<00:09:42.850> a 00:09:42.990 --> 00:09:43.000 align:start position:0% this is the story of time once upon a 00:09:43.000 --> 00:09:46.950 align:start position:0% this is the story of time once upon a time<00:09:43.270> I<00:09:43.660> made<00:09:44.410> a<00:09:44.740> fatal<00:09:45.010> error<00:09:45.310> of<00:09:45.870> accepting<00:09:46.870> a 00:09:46.950 --> 00:09:46.960 align:start position:0% time I made a fatal error of accepting a 00:09:46.960 --> 00:09:50.670 align:start position:0% time I made a fatal error of accepting a keynote<00:09:47.350> in<00:09:47.529> Australia<00:09:48.370> and<00:09:49.360> so<00:09:50.290> I<00:09:50.320> was<00:09:50.500> like 00:09:50.670 --> 00:09:50.680 align:start position:0% keynote in Australia and so I was like 00:09:50.680 --> 00:09:53.880 align:start position:0% keynote in Australia and so I was like 17<00:09:51.580> and<00:09:51.610> 18<00:09:52.150> time<00:09:52.510> zones<00:09:52.779> away<00:09:52.930> from<00:09:53.500> my<00:09:53.680> core 00:09:53.880 --> 00:09:53.890 align:start position:0% 17 and 18 time zones away from my core 00:09:53.890 --> 00:09:56.579 align:start position:0% 17 and 18 time zones away from my core development<00:09:54.220> team<00:09:54.480> now<00:09:55.480> I<00:09:55.839> made<00:09:56.410> it<00:09:56.500> a<00:09:56.560> point 00:09:56.579 --> 00:09:56.589 align:start position:0% development team now I made it a point 00:09:56.589 --> 00:09:58.200 align:start position:0% development team now I made it a point to<00:09:56.860> make<00:09:57.070> sure<00:09:57.130> I<00:09:57.339> still<00:09:57.640> showed<00:09:57.880> up<00:09:58.000> for<00:09:58.150> my 00:09:58.200 --> 00:09:58.210 align:start position:0% to make sure I still showed up for my 00:09:58.210 --> 00:09:59.460 align:start position:0% to make sure I still showed up for my meetings<00:09:58.540> and<00:09:58.779> did<00:09:58.870> all<00:09:58.990> the<00:09:59.110> stuff<00:09:59.290> I<00:09:59.410> was 00:09:59.460 --> 00:09:59.470 align:start position:0% meetings and did all the stuff I was 00:09:59.470 --> 00:10:03.269 align:start position:0% meetings and did all the stuff I was supposed<00:09:59.740> to<00:09:59.830> do<00:10:00.360> but<00:10:01.380> in<00:10:02.380> the<00:10:02.680> middle<00:10:02.890> of<00:10:03.160> this 00:10:03.269 --> 00:10:03.279 align:start position:0% supposed to do but in the middle of this 00:10:03.279 --> 00:10:05.460 align:start position:0% supposed to do but in the middle of this week<00:10:03.490> that<00:10:03.760> I'm<00:10:03.850> in<00:10:03.970> Australia<00:10:04.300> and<00:10:05.020> like<00:10:05.200> I'm 00:10:05.460 --> 00:10:05.470 align:start position:0% week that I'm in Australia and like I'm 00:10:05.470 --> 00:10:08.310 align:start position:0% week that I'm in Australia and like I'm getting<00:10:05.710> late<00:10:06.430> chewed<00:10:07.360> up<00:10:07.540> by<00:10:07.570> the<00:10:07.839> ocean<00:10:08.290> and 00:10:08.310 --> 00:10:08.320 align:start position:0% getting late chewed up by the ocean and 00:10:08.320 --> 00:10:10.950 align:start position:0% getting late chewed up by the ocean and spit<00:10:08.710> right<00:10:08.860> back<00:10:09.040> out<00:10:09.220> at<00:10:09.339> the<00:10:09.370> beach<00:10:09.610> I<00:10:10.060> have 00:10:10.950 --> 00:10:10.960 align:start position:0% spit right back out at the beach I have 00:10:10.960 --> 00:10:13.200 align:start position:0% spit right back out at the beach I have a<00:10:11.320> high<00:10:11.680> severity<00:10:12.010> security<00:10:12.760> incident 00:10:13.200 --> 00:10:13.210 align:start position:0% a high severity security incident 00:10:13.210 --> 00:10:17.670 align:start position:0% a high severity security incident planned<00:10:13.810> in<00:10:14.260> my<00:10:14.920> security<00:10:15.550> app<00:10:15.880> in<00:10:16.390> once<00:10:16.779> so<00:10:17.500> I 00:10:17.670 --> 00:10:17.680 align:start position:0% planned in my security app in once so I 00:10:17.680 --> 00:10:19.440 align:start position:0% planned in my security app in once so I have<00:10:17.980> been<00:10:18.100> planning<00:10:18.279> for<00:10:18.459> this<00:10:18.670> for<00:10:18.730> a<00:10:19.000> year 00:10:19.440 --> 00:10:19.450 align:start position:0% have been planning for this for a year 00:10:19.450 --> 00:10:21.240 align:start position:0% have been planning for this for a year and<00:10:20.020> a<00:10:20.110> half<00:10:20.230> at<00:10:20.380> this<00:10:20.470> point<00:10:20.740> I'm<00:10:20.950> like<00:10:21.040> our 00:10:21.240 --> 00:10:21.250 align:start position:0% and a half at this point I'm like our 00:10:21.250 --> 00:10:22.140 align:start position:0% and a half at this point I'm like our parts<00:10:21.550> go<00:10:21.730> time 00:10:22.140 --> 00:10:22.150 align:start position:0% parts go time 00:10:22.150 --> 00:10:24.210 align:start position:0% parts go time all<00:10:22.240> the<00:10:22.450> stuff<00:10:22.690> that<00:10:22.720> I<00:10:22.930> do<00:10:22.990> it<00:10:23.950> works 00:10:24.210 --> 00:10:24.220 align:start position:0% all the stuff that I do it works 00:10:24.220 --> 00:10:26.460 align:start position:0% all the stuff that I do it works somebody<00:10:24.940> give<00:10:25.060> me<00:10:25.089> a<00:10:25.209> bug<00:10:25.390> oh<00:10:25.660> my<00:10:25.930> god<00:10:26.080> I'm<00:10:26.230> so 00:10:26.460 --> 00:10:26.470 align:start position:0% somebody give me a bug oh my god I'm so 00:10:26.470 --> 00:10:28.980 align:start position:0% somebody give me a bug oh my god I'm so excited<00:10:26.620> and<00:10:27.220> a<00:10:27.940> few<00:10:28.120> of<00:10:28.209> my<00:10:28.360> colleagues<00:10:28.450> but 00:10:28.980 --> 00:10:28.990 align:start position:0% excited and a few of my colleagues but 00:10:28.990 --> 00:10:31.079 align:start position:0% excited and a few of my colleagues but this<00:10:29.650> is<00:10:29.770> not<00:10:29.950> exciting<00:10:30.220> what<00:10:30.550> is<00:10:30.700> wrong<00:10:30.850> with 00:10:31.079 --> 00:10:31.089 align:start position:0% this is not exciting what is wrong with 00:10:31.089 --> 00:10:35.430 align:start position:0% this is not exciting what is wrong with you<00:10:31.270> but<00:10:32.520> how<00:10:33.520> did<00:10:33.670> you<00:10:33.700> come<00:10:33.880> in<00:10:34.180> and<00:10:34.990> it 00:10:35.430 --> 00:10:35.440 align:start position:0% you but how did you come in and it 00:10:35.440 --> 00:10:37.860 align:start position:0% you but how did you come in and it looked<00:10:35.620> at<00:10:35.770> it<00:10:35.800> and<00:10:36.190> I<00:10:36.520> realized<00:10:37.000> uh-oh<00:10:37.390> this 00:10:37.860 --> 00:10:37.870 align:start position:0% looked at it and I realized uh-oh this 00:10:37.870 --> 00:10:40.530 align:start position:0% looked at it and I realized uh-oh this is<00:10:38.050> a<00:10:38.080> problem<00:10:38.700> basically<00:10:39.700> the<00:10:39.850> issue<00:10:40.000> Croker 00:10:40.530 --> 00:10:40.540 align:start position:0% is a problem basically the issue Croker 00:10:40.540 --> 00:10:43.829 align:start position:0% is a problem basically the issue Croker security<00:10:41.080> model<00:10:41.410> in<00:10:41.650> that<00:10:42.480> it<00:10:43.480> would<00:10:43.600> allow 00:10:43.829 --> 00:10:43.839 align:start position:0% security model in that it would allow 00:10:43.839 --> 00:10:46.530 align:start position:0% security model in that it would allow for<00:10:44.020> someone<00:10:44.890> to<00:10:45.010> be<00:10:45.160> able<00:10:45.339> to<00:10:45.730> find<00:10:46.180> bond 00:10:46.530 --> 00:10:46.540 align:start position:0% for someone to be able to find bond 00:10:46.540 --> 00:10:48.840 align:start position:0% for someone to be able to find bond their<00:10:46.900> stink<00:10:47.290> and<00:10:47.500> not<00:10:47.680> have<00:10:47.920> to<00:10:48.130> wait<00:10:48.370> three 00:10:48.840 --> 00:10:48.850 align:start position:0% their stink and not have to wait three 00:10:48.850 --> 00:10:50.220 align:start position:0% their stink and not have to wait three weeks<00:10:49.060> which<00:10:49.510> is<00:10:49.660> something<00:10:49.900> that<00:10:50.080> is 00:10:50.220 --> 00:10:50.230 align:start position:0% weeks which is something that is 00:10:50.230 --> 00:10:51.150 align:start position:0% weeks which is something that is built-in 00:10:51.150 --> 00:10:51.160 align:start position:0% built-in 00:10:51.160 --> 00:10:55.800 align:start position:0% built-in to<00:10:51.339> our<00:10:52.649> perfect<00:10:53.649> to<00:10:53.740> economic<00:10:54.190> layer<00:10:54.399> and<00:10:55.329> it 00:10:55.800 --> 00:10:55.810 align:start position:0% to our perfect to economic layer and it 00:10:55.810 --> 00:10:58.079 align:start position:0% to our perfect to economic layer and it under<00:10:56.110> my<00:10:56.259> practical<00:10:56.800> II<00:10:56.889> anything<00:10:57.819> that<00:10:57.970> you 00:10:58.079 --> 00:10:58.089 align:start position:0% under my practical II anything that you 00:10:58.089 --> 00:10:59.850 align:start position:0% under my practical II anything that you would<00:10:58.240> want<00:10:58.420> to<00:10:58.480> do<00:10:58.660> on<00:10:58.690> the<00:10:58.899> network<00:10:59.230> on<00:10:59.649> not 00:10:59.850 --> 00:10:59.860 align:start position:0% would want to do on the network on not 00:10:59.860 --> 00:11:03.269 align:start position:0% would want to do on the network on not later<00:11:00.069> so<00:11:01.000> what<00:11:01.329> we<00:11:01.449> realized<00:11:01.899> was<00:11:02.379> to<00:11:03.100> fix 00:11:03.269 --> 00:11:03.279 align:start position:0% later so what we realized was to fix 00:11:03.279 --> 00:11:05.670 align:start position:0% later so what we realized was to fix this<00:11:03.490> we<00:11:04.029> were<00:11:04.300> going<00:11:04.600> to<00:11:04.779> have<00:11:04.959> to<00:11:05.170> do<00:11:05.319> an 00:11:05.670 --> 00:11:05.680 align:start position:0% this we were going to have to do an 00:11:05.680 --> 00:11:07.619 align:start position:0% this we were going to have to do an emergency<00:11:05.829> one<00:11:06.519> er<00:11:06.610> ability<00:11:06.970> coordination 00:11:07.619 --> 00:11:07.629 align:start position:0% emergency one er ability coordination 00:11:07.629 --> 00:11:10.110 align:start position:0% emergency one er ability coordination exercise<00:11:08.220> meaning<00:11:09.220> you're<00:11:09.490> going<00:11:09.550> to<00:11:09.790> have<00:11:09.970> to 00:11:10.110 --> 00:11:10.120 align:start position:0% exercise meaning you're going to have to 00:11:10.120 --> 00:11:13.650 align:start position:0% exercise meaning you're going to have to patch<00:11:10.269> the<00:11:10.480> code<00:11:10.889> we<00:11:11.889> were<00:11:12.310> going<00:11:12.910> to<00:11:13.209> have<00:11:13.509> to 00:11:13.650 --> 00:11:13.660 align:start position:0% patch the code we were going to have to 00:11:13.660 --> 00:11:16.400 align:start position:0% patch the code we were going to have to develop<00:11:13.870> some<00:11:14.199> willing<00:11:14.620> to<00:11:14.980> investigate 00:11:16.400 --> 00:11:16.410 align:start position:0% develop some willing to investigate 00:11:16.410 --> 00:11:18.689 align:start position:0% develop some willing to investigate exploitation<00:11:17.410> because<00:11:17.889> if<00:11:18.009> exploitation 00:11:18.689 --> 00:11:18.699 align:start position:0% exploitation because if exploitation 00:11:18.699 --> 00:11:19.410 align:start position:0% exploitation because if exploitation happened 00:11:19.410 --> 00:11:19.420 align:start position:0% happened 00:11:19.420 --> 00:11:21.720 align:start position:0% happened I<00:11:19.449> better<00:11:20.139> be<00:11:20.230> ready<00:11:20.500> to<00:11:20.829> show<00:11:21.069> people<00:11:21.279> where 00:11:21.720 --> 00:11:21.730 align:start position:0% I better be ready to show people where 00:11:21.730 --> 00:11:23.490 align:start position:0% I better be ready to show people where it<00:11:21.850> happened<00:11:22.209> why<00:11:22.449> it<00:11:22.509> happened<00:11:22.660> is<00:11:23.139> how<00:11:23.319> it 00:11:23.490 --> 00:11:23.500 align:start position:0% it happened why it happened is how it 00:11:23.500 --> 00:11:27.150 align:start position:0% it happened why it happened is how it happened<00:11:23.889> and<00:11:24.629> additionally<00:11:25.629> we<00:11:25.920> had<00:11:26.920> to 00:11:27.150 --> 00:11:27.160 align:start position:0% happened and additionally we had to 00:11:27.160 --> 00:11:30.780 align:start position:0% happened and additionally we had to think<00:11:27.490> through<00:11:28.050> notification<00:11:29.069> so<00:11:30.069> my<00:11:30.399> office 00:11:30.780 --> 00:11:30.790 align:start position:0% think through notification so my office 00:11:30.790 --> 00:11:32.850 align:start position:0% think through notification so my office wall<00:11:31.029> at<00:11:31.389> home<00:11:31.449> has<00:11:32.079> all<00:11:32.350> of<00:11:32.379> these<00:11:32.560> sticky 00:11:32.850 --> 00:11:32.860 align:start position:0% wall at home has all of these sticky 00:11:32.860 --> 00:11:35.429 align:start position:0% wall at home has all of these sticky notes<00:11:32.980> on<00:11:33.339> it<00:11:33.430> it<00:11:33.610> looks<00:11:33.819> like<00:11:34.199> kind<00:11:35.199> of<00:11:35.290> looks 00:11:35.429 --> 00:11:35.439 align:start position:0% notes on it it looks like kind of looks 00:11:35.439 --> 00:11:37.730 align:start position:0% notes on it it looks like kind of looks like<00:11:35.670> it<00:11:36.670> would<00:11:36.730> be<00:11:36.910> received<00:11:37.029> earring<00:11:37.540> up 00:11:37.730 --> 00:11:37.740 align:start position:0% like it would be received earring up 00:11:37.740 --> 00:11:41.670 align:start position:0% like it would be received earring up fine<00:11:38.970> basically<00:11:39.970> what<00:11:40.629> my<00:11:40.779> office<00:11:41.139> walls<00:11:41.439> does 00:11:41.670 --> 00:11:41.680 align:start position:0% fine basically what my office walls does 00:11:41.680 --> 00:11:43.889 align:start position:0% fine basically what my office walls does for<00:11:41.980> me<00:11:42.069> is<00:11:42.189> best<00:11:42.459> it's<00:11:43.149> got<00:11:43.329> the<00:11:43.449> process 00:11:43.889 --> 00:11:43.899 align:start position:0% for me is best it's got the process 00:11:43.899 --> 00:11:45.809 align:start position:0% for me is best it's got the process mapped<00:11:44.139> out<00:11:44.350> just<00:11:44.860> document<00:11:45.370> to<00:11:45.459> the<00:11:45.579> three<00:11:45.699> or 00:11:45.809 --> 00:11:45.819 align:start position:0% mapped out just document to the three or 00:11:45.819 --> 00:11:49.110 align:start position:0% mapped out just document to the three or four<00:11:46.000> different<00:11:46.089> places<00:11:46.379> and<00:11:47.379> I<00:11:48.009> because<00:11:48.970> they 00:11:49.110 --> 00:11:49.120 align:start position:0% four different places and I because they 00:11:49.120 --> 00:11:50.850 align:start position:0% four different places and I because they already<00:11:49.449> planned<00:11:49.930> on<00:11:50.079> having<00:11:50.290> to<00:11:50.529> do<00:11:50.680> this 00:11:50.850 --> 00:11:50.860 align:start position:0% already planned on having to do this 00:11:50.860 --> 00:11:54.320 align:start position:0% already planned on having to do this knew<00:11:51.730> what<00:11:52.089> was<00:11:52.660> next 00:11:54.320 --> 00:11:54.330 align:start position:0% knew what was next 00:11:54.330 --> 00:11:55.490 align:start position:0% knew what was next [Music] 00:11:55.490 --> 00:11:55.500 align:start position:0% [Music] 00:11:55.500 --> 00:11:59.429 align:start position:0% [Music] how<00:11:56.500> may<00:11:56.709> I<00:11:57.069> have<00:11:57.550> a<00:11:57.579> moment<00:11:57.850> but<00:11:58.600> what<00:11:59.139> we<00:11:59.290> knew 00:11:59.429 --> 00:11:59.439 align:start position:0% how may I have a moment but what we knew 00:11:59.439 --> 00:12:02.100 align:start position:0% how may I have a moment but what we knew we<00:11:59.589> wanted<00:11:59.829> in<00:12:00.220> the<00:12:00.670> case<00:12:00.910> of<00:12:01.089> any<00:12:01.329> security 00:12:02.100 --> 00:12:02.110 align:start position:0% we wanted in the case of any security 00:12:02.110 --> 00:12:04.259 align:start position:0% we wanted in the case of any security emergency<00:12:02.459> was<00:12:03.459> if<00:12:03.579> we<00:12:03.670> wanted<00:12:03.850> to<00:12:03.970> be<00:12:04.089> able<00:12:04.149> to 00:12:04.259 --> 00:12:04.269 align:start position:0% emergency was if we wanted to be able to 00:12:04.269 --> 00:12:05.819 align:start position:0% emergency was if we wanted to be able to be<00:12:04.389> the<00:12:04.509> best<00:12:04.540> dependency<00:12:05.380> that<00:12:05.500> we<00:12:05.649> could 00:12:05.819 --> 00:12:05.829 align:start position:0% be the best dependency that we could 00:12:05.829 --> 00:12:08.759 align:start position:0% be the best dependency that we could mean<00:12:06.040> to<00:12:06.730> people<00:12:07.149> who<00:12:07.240> rely<00:12:07.600> on<00:12:07.870> our<00:12:07.930> code<00:12:08.290> we 00:12:08.759 --> 00:12:08.769 align:start position:0% mean to people who rely on our code we 00:12:08.769 --> 00:12:10.290 align:start position:0% mean to people who rely on our code we wanted<00:12:09.040> to<00:12:09.130> make<00:12:09.250> sure<00:12:09.279> that<00:12:09.399> we<00:12:09.699> reduce<00:12:09.939> harm 00:12:10.290 --> 00:12:10.300 align:start position:0% wanted to make sure that we reduce harm 00:12:10.300 --> 00:12:12.449 align:start position:0% wanted to make sure that we reduce harm we<00:12:11.199> wanted<00:12:11.589> to<00:12:11.709> make<00:12:11.860> sure<00:12:11.889> that<00:12:12.100> we've 00:12:12.449 --> 00:12:12.459 align:start position:0% we wanted to make sure that we've 00:12:12.459 --> 00:12:13.689 align:start position:0% we wanted to make sure that we've provided<00:12:12.699> visibility 00:12:13.689 --> 00:12:13.699 align:start position:0% provided visibility 00:12:13.699 --> 00:12:15.999 align:start position:0% provided visibility transparency<00:12:14.480> and<00:12:14.929> the<00:12:15.589> way<00:12:15.739> that<00:12:15.889> we 00:12:15.999 --> 00:12:16.009 align:start position:0% transparency and the way that we 00:12:16.009 --> 00:12:19.569 align:start position:0% transparency and the way that we specifically<00:12:16.609> do<00:12:16.939> that<00:12:17.149> case<00:12:17.869> is<00:12:18.579> very 00:12:19.569 --> 00:12:19.579 align:start position:0% specifically do that case is very 00:12:19.579 --> 00:12:23.079 align:start position:0% specifically do that case is very comprehensive<00:12:20.709> incident<00:12:21.709> report<00:12:22.339> post<00:12:22.639> that 00:12:23.079 --> 00:12:23.089 align:start position:0% comprehensive incident report post that 00:12:23.089 --> 00:12:25.389 align:start position:0% comprehensive incident report post that I<00:12:23.329> put<00:12:23.359> up<00:12:23.720> within<00:12:24.379> a<00:12:24.499> week<00:12:24.559> or<00:12:24.919> so<00:12:25.160> of 00:12:25.389 --> 00:12:25.399 align:start position:0% I put up within a week or so of 00:12:25.399 --> 00:12:27.759 align:start position:0% I put up within a week or so of something<00:12:26.029> bad<00:12:26.660> happening<00:12:26.720> that<00:12:27.379> requires 00:12:27.759 --> 00:12:27.769 align:start position:0% something bad happening that requires 00:12:27.769 --> 00:12:30.460 align:start position:0% something bad happening that requires emergency<00:12:28.429> exercises<00:12:28.999> a<00:12:29.509> couple<00:12:30.290> of<00:12:30.379> things 00:12:30.460 --> 00:12:30.470 align:start position:0% emergency exercises a couple of things 00:12:30.470 --> 00:12:32.229 align:start position:0% emergency exercises a couple of things we<00:12:30.679> knew<00:12:30.829> we<00:12:30.980> were<00:12:31.069> going<00:12:31.160> to<00:12:31.220> come<00:12:31.399> up<00:12:31.519> against 00:12:32.229 --> 00:12:32.239 align:start position:0% we knew we were going to come up against 00:12:32.239 --> 00:12:36.039 align:start position:0% we knew we were going to come up against we<00:12:33.109> knew<00:12:33.259> that<00:12:33.309> we<00:12:34.309> time<00:12:34.970> was<00:12:35.540> really<00:12:35.869> really 00:12:36.039 --> 00:12:36.049 align:start position:0% we knew that we time was really really 00:12:36.049 --> 00:12:38.439 align:start position:0% we knew that we time was really really important<00:12:36.679> here<00:12:36.980> we<00:12:37.549> are<00:12:37.579> monitoring<00:12:38.179> for 00:12:38.439 --> 00:12:38.449 align:start position:0% important here we are monitoring for 00:12:38.449 --> 00:12:40.929 align:start position:0% important here we are monitoring for exploitation<00:12:39.290> we<00:12:39.949> were<00:12:40.040> able<00:12:40.220> to<00:12:40.399> see<00:12:40.730> where 00:12:40.929 --> 00:12:40.939 align:start position:0% exploitation we were able to see where 00:12:40.939 --> 00:12:42.009 align:start position:0% exploitation we were able to see where the<00:12:41.059> person<00:12:41.329> who<00:12:41.449> reported<00:12:41.629> the 00:12:42.009 --> 00:12:42.019 align:start position:0% the person who reported the 00:12:42.019 --> 00:12:44.259 align:start position:0% the person who reported the vulnerability<00:12:42.709> had<00:12:43.369> been<00:12:43.609> exploiting<00:12:44.179> the 00:12:44.259 --> 00:12:44.269 align:start position:0% vulnerability had been exploiting the 00:12:44.269 --> 00:12:45.849 align:start position:0% vulnerability had been exploiting the buyer<00:12:44.449> just<00:12:44.689> to<00:12:44.899> check<00:12:45.109> and<00:12:45.290> see<00:12:45.410> if<00:12:45.499> it<00:12:45.649> works 00:12:45.849 --> 00:12:45.859 align:start position:0% buyer just to check and see if it works 00:12:45.859 --> 00:12:47.829 align:start position:0% buyer just to check and see if it works they<00:12:46.609> did<00:12:46.819> this<00:12:46.910> in<00:12:47.089> a<00:12:47.149> way<00:12:47.179> that<00:12:47.419> didn't<00:12:47.689> cause 00:12:47.829 --> 00:12:47.839 align:start position:0% they did this in a way that didn't cause 00:12:47.839 --> 00:12:51.129 align:start position:0% they did this in a way that didn't cause harm<00:12:48.259> but<00:12:48.619> we<00:12:49.489> also<00:12:49.699> knew<00:12:50.059> if<00:12:50.299> one<00:12:50.600> person<00:12:51.019> knew 00:12:51.129 --> 00:12:51.139 align:start position:0% harm but we also knew if one person knew 00:12:51.139 --> 00:12:53.229 align:start position:0% harm but we also knew if one person knew about<00:12:51.259> the<00:12:51.559> spot<00:12:51.859> it<00:12:52.399> was<00:12:52.549> likely<00:12:52.790> other 00:12:53.229 --> 00:12:53.239 align:start position:0% about the spot it was likely other 00:12:53.239 --> 00:12:55.239 align:start position:0% about the spot it was likely other people<00:12:53.749> could<00:12:54.049> have<00:12:54.230> Co<00:12:54.439> discovered<00:12:54.919> it<00:12:55.040> and 00:12:55.239 --> 00:12:55.249 align:start position:0% people could have Co discovered it and 00:12:55.249 --> 00:12:57.849 align:start position:0% people could have Co discovered it and just<00:12:55.519> didn't<00:12:55.790> say<00:12:55.999> anything<00:12:56.439> because<00:12:57.439> we<00:12:57.769> knew 00:12:57.849 --> 00:12:57.859 align:start position:0% just didn't say anything because we knew 00:12:57.859 --> 00:13:00.549 align:start position:0% just didn't say anything because we knew time<00:12:58.129> is<00:12:58.279> of<00:12:58.399> the<00:12:58.429> essence<00:12:58.910> here<00:12:59.079> it<00:13:00.079> was 00:13:00.549 --> 00:13:00.559 align:start position:0% time is of the essence here it was 00:13:00.559 --> 00:13:02.530 align:start position:0% time is of the essence here it was especially<00:13:01.009> important<00:13:01.879> for<00:13:01.999> us<00:13:02.149> to<00:13:02.359> make<00:13:02.509> sure 00:13:02.530 --> 00:13:02.540 align:start position:0% especially important for us to make sure 00:13:02.540 --> 00:13:04.679 align:start position:0% especially important for us to make sure that<00:13:02.959> our<00:13:03.139> communication<00:13:03.919> and<00:13:04.100> coordination 00:13:04.679 --> 00:13:04.689 align:start position:0% that our communication and coordination 00:13:04.689 --> 00:13:08.349 align:start position:0% that our communication and coordination was<00:13:05.689> fast<00:13:06.559> and<00:13:06.919> it<00:13:07.339> was<00:13:07.639> good<00:13:07.910> and<00:13:08.149> it<00:13:08.299> was 00:13:08.349 --> 00:13:08.359 align:start position:0% was fast and it was good and it was 00:13:08.359 --> 00:13:11.199 align:start position:0% was fast and it was good and it was clear<00:13:08.869> and<00:13:09.230> when<00:13:09.949> we<00:13:10.100> were<00:13:10.189> asking<00:13:10.639> people<00:13:10.699> are 00:13:11.199 --> 00:13:11.209 align:start position:0% clear and when we were asking people are 00:13:11.209 --> 00:13:13.059 align:start position:0% clear and when we were asking people are recommending<00:13:11.899> that<00:13:11.929> our<00:13:12.259> validators<00:13:12.769> do 00:13:13.059 --> 00:13:13.069 align:start position:0% recommending that our validators do 00:13:13.069 --> 00:13:15.309 align:start position:0% recommending that our validators do specific<00:13:13.639> things<00:13:13.839> we're<00:13:14.839> not<00:13:14.899> telling<00:13:15.139> them 00:13:15.309 --> 00:13:15.319 align:start position:0% specific things we're not telling them 00:13:15.319 --> 00:13:18.099 align:start position:0% specific things we're not telling them what<00:13:15.439> to<00:13:15.470> do<00:13:15.759> but<00:13:16.759> we<00:13:16.939> specifically<00:13:17.689> aren't 00:13:18.099 --> 00:13:18.109 align:start position:0% what to do but we specifically aren't 00:13:18.109 --> 00:13:19.569 align:start position:0% what to do but we specifically aren't making<00:13:18.259> sure<00:13:18.619> everything<00:13:19.249> we<00:13:19.369> say<00:13:19.549> is 00:13:19.569 --> 00:13:19.579 align:start position:0% making sure everything we say is 00:13:19.579 --> 00:13:22.029 align:start position:0% making sure everything we say is actionable<00:13:20.239> and<00:13:20.449> clear<00:13:20.779> one<00:13:21.499> thing<00:13:21.529> that<00:13:21.889> we 00:13:22.029 --> 00:13:22.039 align:start position:0% actionable and clear one thing that we 00:13:22.039 --> 00:13:24.429 align:start position:0% actionable and clear one thing that we committed<00:13:22.399> to<00:13:22.489> very<00:13:23.059> early<00:13:23.480> on<00:13:23.509> was<00:13:24.049> making 00:13:24.429 --> 00:13:24.439 align:start position:0% committed to very early on was making 00:13:24.439 --> 00:13:29.879 align:start position:0% committed to very early on was making sure<00:13:24.649> that<00:13:24.799> we<00:13:25.009> pre<00:13:25.309> notified<00:13:26.619> people<00:13:27.619> who<00:13:28.100> are 00:13:29.879 --> 00:13:29.889 align:start position:0% sure that we pre notified people who are 00:13:29.889 --> 00:13:33.400 align:start position:0% sure that we pre notified people who are who<00:13:30.889> rely<00:13:31.489> on<00:13:31.519> our<00:13:31.759> code<00:13:31.999> meaning<00:13:32.809> instead<00:13:33.289> of 00:13:33.400 --> 00:13:33.410 align:start position:0% who rely on our code meaning instead of 00:13:33.410 --> 00:13:34.929 align:start position:0% who rely on our code meaning instead of just<00:13:33.589> dropping<00:13:33.919> a<00:13:34.129> security<00:13:34.579> bug<00:13:34.759> into 00:13:34.929 --> 00:13:34.939 align:start position:0% just dropping a security bug into 00:13:34.939 --> 00:13:37.859 align:start position:0% just dropping a security bug into Tuesday<00:13:35.419> Monday<00:13:36.350> I<00:13:36.649> send<00:13:37.309> our<00:13:37.399> message 00:13:37.859 --> 00:13:37.869 align:start position:0% Tuesday Monday I send our message 00:13:37.869 --> 00:13:41.319 align:start position:0% Tuesday Monday I send our message through<00:13:38.869> our<00:13:38.899> forum<00:13:39.489> through<00:13:40.489> a<00:13:40.789> mailing<00:13:41.059> list 00:13:41.319 --> 00:13:41.329 align:start position:0% through our forum through a mailing list 00:13:41.329 --> 00:13:43.090 align:start position:0% through our forum through a mailing list or<00:13:41.600> through<00:13:41.779> every<00:13:42.019> nail<00:13:42.139> any<00:13:42.470> other<00:13:42.709> channel 00:13:43.090 --> 00:13:43.100 align:start position:0% or through every nail any other channel 00:13:43.100 --> 00:13:44.739 align:start position:0% or through every nail any other channel that<00:13:43.220> we<00:13:43.339> need<00:13:43.459> to<00:13:43.579> send<00:13:43.759> it<00:13:43.879> through<00:13:44.089> to<00:13:44.600> say 00:13:44.739 --> 00:13:44.749 align:start position:0% that we need to send it through to say 00:13:44.749 --> 00:13:46.539 align:start position:0% that we need to send it through to say hey<00:13:44.989> heads<00:13:45.350> up<00:13:45.529> you're<00:13:45.859> probably<00:13:46.129> going<00:13:46.459> to 00:13:46.539 --> 00:13:46.549 align:start position:0% hey heads up you're probably going to 00:13:46.549 --> 00:13:49.059 align:start position:0% hey heads up you're probably going to need<00:13:46.669> to<00:13:46.819> patch<00:13:47.029> we've<00:13:47.600> got<00:13:47.779> a<00:13:47.809> bug<00:13:48.049> here<00:13:48.439> and 00:13:49.059 --> 00:13:49.069 align:start position:0% need to patch we've got a bug here and 00:13:49.069 --> 00:13:52.419 align:start position:0% need to patch we've got a bug here and if<00:13:49.699> you're<00:13:50.089> high<00:13:50.449> or<00:13:50.749> critical<00:13:50.779> disparity<00:13:51.739> but 00:13:52.419 --> 00:13:52.429 align:start position:0% if you're high or critical disparity but 00:13:52.429 --> 00:13:54.249 align:start position:0% if you're high or critical disparity but the<00:13:52.819> patch<00:13:53.029> will<00:13:53.329> land<00:13:53.509> around<00:13:53.839> this<00:13:53.959> time 00:13:54.249 --> 00:13:54.259 align:start position:0% the patch will land around this time 00:13:54.259 --> 00:13:56.409 align:start position:0% the patch will land around this time part<00:13:55.100> of<00:13:55.129> the<00:13:55.220> reason<00:13:55.459> we<00:13:55.579> do<00:13:55.759> that<00:13:55.789> is<00:13:56.179> because 00:13:56.409 --> 00:13:56.419 align:start position:0% part of the reason we do that is because 00:13:56.419 --> 00:13:58.269 align:start position:0% part of the reason we do that is because we<00:13:56.779> have<00:13:56.809> an<00:13:57.079> extremely<00:13:57.410> global<00:13:57.829> community 00:13:58.269 --> 00:13:58.279 align:start position:0% we have an extremely global community 00:13:58.279 --> 00:14:01.659 align:start position:0% we have an extremely global community and<00:13:58.639> if<00:13:59.389> we<00:13:59.839> have<00:14:00.169> everything<00:14:00.589> decided<00:14:01.429> on 00:14:01.659 --> 00:14:01.669 align:start position:0% and if we have everything decided on 00:14:01.669 --> 00:14:03.449 align:start position:0% and if we have everything decided on Pacific<00:14:02.149> Standard<00:14:02.359> Time 00:14:03.449 --> 00:14:03.459 align:start position:0% Pacific Standard Time 00:14:03.459 --> 00:14:04.650 align:start position:0% Pacific Standard Time always<00:14:03.610> waking<00:14:03.939> up<00:14:04.029> at<00:14:04.179> 2:00<00:14:04.300> in<00:14:04.449> the<00:14:04.480> morning 00:14:04.650 --> 00:14:04.660 align:start position:0% always waking up at 2:00 in the morning 00:14:04.660 --> 00:14:07.199 align:start position:0% always waking up at 2:00 in the morning and<00:14:05.019> somebody's<00:14:05.709> always<00:14:06.009> you<00:14:06.519> know<00:14:06.610> having<00:14:06.999> to 00:14:07.199 --> 00:14:07.209 align:start position:0% and somebody's always you know having to 00:14:07.209 --> 00:14:09.359 align:start position:0% and somebody's always you know having to jump<00:14:07.569> away<00:14:07.689> from<00:14:07.809> the<00:14:08.110> dinner<00:14:08.259> table<00:14:08.709> and<00:14:08.889> go 00:14:09.359 --> 00:14:09.369 align:start position:0% jump away from the dinner table and go 00:14:09.369 --> 00:14:11.910 align:start position:0% jump away from the dinner table and go deal<00:14:09.610> with<00:14:09.639> some<00:14:10.569> security<00:14:11.379> patch<00:14:11.559> that's 00:14:11.910 --> 00:14:11.920 align:start position:0% deal with some security patch that's 00:14:11.920 --> 00:14:15.030 align:start position:0% deal with some security patch that's incredibly<00:14:12.550> important<00:14:13.119> for<00:14:13.209> them<00:14:13.769> to<00:14:14.769> apply 00:14:15.030 --> 00:14:15.040 align:start position:0% incredibly important for them to apply 00:14:15.040 --> 00:14:18.239 align:start position:0% incredibly important for them to apply so<00:14:15.970> in<00:14:16.509> addition<00:14:16.809> to<00:14:17.019> this<00:14:17.230> we<00:14:17.829> knew<00:14:18.009> we<00:14:18.160> were 00:14:18.239 --> 00:14:18.249 align:start position:0% so in addition to this we knew we were 00:14:18.249 --> 00:14:19.879 align:start position:0% so in addition to this we knew we were going<00:14:18.429> to<00:14:18.550> need<00:14:18.819> a<00:14:19.089> little<00:14:19.240> bit<00:14:19.389> of<00:14:19.480> discretion 00:14:19.879 --> 00:14:19.889 align:start position:0% going to need a little bit of discretion 00:14:19.889 --> 00:14:21.660 align:start position:0% going to need a little bit of discretion we<00:14:20.889> were<00:14:20.949> gonna<00:14:21.069> have<00:14:21.249> to<00:14:21.279> handle<00:14:21.610> this 00:14:21.660 --> 00:14:21.670 align:start position:0% we were gonna have to handle this 00:14:21.670 --> 00:14:24.449 align:start position:0% we were gonna have to handle this privately<00:14:21.999> we<00:14:22.629> can't<00:14:22.869> release<00:14:23.499> an<00:14:23.740> exploit<00:14:24.249> to 00:14:24.449 --> 00:14:24.459 align:start position:0% privately we can't release an exploit to 00:14:24.459 --> 00:14:26.549 align:start position:0% privately we can't release an exploit to the<00:14:24.550> entire<00:14:24.910> world<00:14:24.939> look<00:14:25.629> what<00:14:25.809> we<00:14:25.929> found 00:14:26.549 --> 00:14:26.559 align:start position:0% the entire world look what we found 00:14:26.559 --> 00:14:29.090 align:start position:0% the entire world look what we found because<00:14:27.279> badness<00:14:27.730> happens<00:14:28.089> when<00:14:28.329> you<00:14:28.449> do<00:14:28.600> that 00:14:29.090 --> 00:14:29.100 align:start position:0% because badness happens when you do that 00:14:29.100 --> 00:14:32.100 align:start position:0% because badness happens when you do that so<00:14:30.100> we<00:14:30.220> realize<00:14:30.550> we<00:14:30.670> have<00:14:30.819> to<00:14:30.850> quickly<00:14:31.240> stand 00:14:32.100 --> 00:14:32.110 align:start position:0% so we realize we have to quickly stand 00:14:32.110 --> 00:14:34.410 align:start position:0% so we realize we have to quickly stand up<00:14:32.379> a<00:14:32.649> safe<00:14:32.889> space<00:14:33.189> where<00:14:33.550> we<00:14:33.790> can<00:14:33.939> talk<00:14:34.179> to<00:14:34.329> our 00:14:34.410 --> 00:14:34.420 align:start position:0% up a safe space where we can talk to our 00:14:34.420 --> 00:14:36.600 align:start position:0% up a safe space where we can talk to our network<00:14:34.720> operators<00:14:35.290> in<00:14:35.949> this<00:14:36.220> missive 00:14:36.600 --> 00:14:36.610 align:start position:0% network operators in this missive 00:14:36.610 --> 00:14:38.609 align:start position:0% network operators in this missive encased<00:14:36.970> we<00:14:37.360> already<00:14:37.720> know<00:14:37.869> the<00:14:38.050> topology<00:14:38.350> of 00:14:38.609 --> 00:14:38.619 align:start position:0% encased we already know the topology of 00:14:38.619 --> 00:14:41.069 align:start position:0% encased we already know the topology of our<00:14:38.709> network<00:14:38.980> pretty<00:14:39.220> well<00:14:39.399> so<00:14:40.089> we<00:14:40.660> created 00:14:41.069 --> 00:14:41.079 align:start position:0% our network pretty well so we created 00:14:41.079 --> 00:14:44.069 align:start position:0% our network pretty well so we created telegram<00:14:41.709> room<00:14:41.949> which<00:14:42.550> was<00:14:43.179> a<00:14:43.209> moment<00:14:43.689> that<00:14:43.749> we 00:14:44.069 --> 00:14:44.079 align:start position:0% telegram room which was a moment that we 00:14:44.079 --> 00:14:47.489 align:start position:0% telegram room which was a moment that we want<00:14:44.259> to<00:14:44.410> hide<00:14:44.589> a<00:14:44.619> new<00:14:44.829> table<00:14:45.329> but<00:14:46.329> we<00:14:47.259> have<00:14:47.379> new 00:14:47.489 --> 00:14:47.499 align:start position:0% want to hide a new table but we have new 00:14:47.499 --> 00:14:48.840 align:start position:0% want to hide a new table but we have new opportunities<00:14:48.129> to<00:14:48.160> do<00:14:48.399> things<00:14:48.579> much<00:14:48.790> better 00:14:48.840 --> 00:14:48.850 align:start position:0% opportunities to do things much better 00:14:48.850 --> 00:14:50.850 align:start position:0% opportunities to do things much better than<00:14:49.300> getting<00:14:49.600> 100<00:14:50.079> people<00:14:50.379> in<00:14:50.499> a<00:14:50.559> telegram 00:14:50.850 --> 00:14:50.860 align:start position:0% than getting 100 people in a telegram 00:14:50.860 --> 00:14:54.480 align:start position:0% than getting 100 people in a telegram room<00:14:51.309> and<00:14:52.170> talking<00:14:53.170> about<00:14:53.410> explanation<00:14:54.399> of 00:14:54.480 --> 00:14:54.490 align:start position:0% room and talking about explanation of 00:14:54.490 --> 00:14:57.600 align:start position:0% room and talking about explanation of scenarios<00:14:54.999> and<00:14:55.420> security<00:14:56.110> flaws<00:14:56.369> one<00:14:57.369> thing 00:14:57.600 --> 00:14:57.610 align:start position:0% scenarios and security flaws one thing 00:14:57.610 --> 00:14:59.669 align:start position:0% scenarios and security flaws one thing that<00:14:57.759> was<00:14:57.850> particularly<00:14:58.480> rough<00:14:59.110> in<00:14:59.350> this 00:14:59.669 --> 00:14:59.679 align:start position:0% that was particularly rough in this 00:14:59.679 --> 00:15:02.040 align:start position:0% that was particularly rough in this specific<00:15:00.249> spot<00:15:00.369> though<00:15:00.730> when<00:15:01.629> we<00:15:01.779> were<00:15:01.899> trying 00:15:02.040 --> 00:15:02.050 align:start position:0% specific spot though when we were trying 00:15:02.050 --> 00:15:03.929 align:start position:0% specific spot though when we were trying to<00:15:02.199> clean<00:15:02.410> notify<00:15:02.769> people<00:15:03.189> but<00:15:03.610> we<00:15:03.730> have<00:15:03.910> a 00:15:03.929 --> 00:15:03.939 align:start position:0% to clean notify people but we have a 00:15:03.939 --> 00:15:07.109 align:start position:0% to clean notify people but we have a critical<00:15:04.389> emergency<00:15:04.959> in<00:15:05.170> the<00:15:05.319> hopper<00:15:05.639> we<00:15:06.639> were 00:15:07.109 --> 00:15:07.119 align:start position:0% critical emergency in the hopper we were 00:15:07.119 --> 00:15:08.850 align:start position:0% critical emergency in the hopper we were trying<00:15:07.420> to<00:15:07.629> go<00:15:07.779> and<00:15:08.110> make<00:15:08.259> sure<00:15:08.410> that<00:15:08.529> we<00:15:08.709> reach 00:15:08.850 --> 00:15:08.860 align:start position:0% trying to go and make sure that we reach 00:15:08.860 --> 00:15:11.579 align:start position:0% trying to go and make sure that we reach out<00:15:09.129> to<00:15:09.519> all<00:15:10.299> of<00:15:10.360> these<00:15:10.749> different<00:15:10.959> projects 00:15:11.579 --> 00:15:11.589 align:start position:0% out to all of these different projects 00:15:11.589 --> 00:15:13.470 align:start position:0% out to all of these different projects and<00:15:11.860> all<00:15:12.069> of<00:15:12.220> these<00:15:12.309> different<00:15:12.490> companies<00:15:12.879> for 00:15:13.470 --> 00:15:13.480 align:start position:0% and all of these different companies for 00:15:13.480 --> 00:15:14.429 align:start position:0% and all of these different companies for environment<00:15:13.990> are<00:15:14.079> toast 00:15:14.429 --> 00:15:14.439 align:start position:0% environment are toast 00:15:14.439 --> 00:15:16.650 align:start position:0% environment are toast more<00:15:15.369> than<00:15:15.549> anything<00:15:15.879> else<00:15:16.149> the<00:15:16.480> most 00:15:16.650 --> 00:15:16.660 align:start position:0% more than anything else the most 00:15:16.660 --> 00:15:19.429 align:start position:0% more than anything else the most frustrating<00:15:17.319> thing<00:15:17.619> but<00:15:18.459> there<00:15:18.999> were<00:15:19.119> no 00:15:19.429 --> 00:15:19.439 align:start position:0% frustrating thing but there were no 00:15:19.439 --> 00:15:22.169 align:start position:0% frustrating thing but there were no operational<00:15:20.439> practically<00:15:21.009> no<00:15:21.220> operational 00:15:22.169 --> 00:15:22.179 align:start position:0% operational practically no operational 00:15:22.179 --> 00:15:26.340 align:start position:0% operational practically no operational Security<00:15:22.929> Act<00:15:23.290> email<00:15:24.160> inboxes<00:15:24.819> when<00:15:25.720> a<00:15:25.929> human 00:15:26.340 --> 00:15:26.350 align:start position:0% Security Act email inboxes when a human 00:15:26.350 --> 00:15:27.929 align:start position:0% Security Act email inboxes when a human behind<00:15:26.619> them<00:15:26.920> there<00:15:27.429> was<00:15:27.519> no<00:15:27.730> way<00:15:27.910> for 00:15:27.929 --> 00:15:27.939 align:start position:0% behind them there was no way for 00:15:27.939 --> 00:15:30.900 align:start position:0% behind them there was no way for companies<00:15:28.329> to<00:15:28.929> get<00:15:29.470> a<00:15:29.769> straight<00:15:30.279> security 00:15:30.900 --> 00:15:30.910 align:start position:0% companies to get a straight security 00:15:30.910 --> 00:15:34.319 align:start position:0% companies to get a straight security message<00:15:31.509> from<00:15:31.720> us<00:15:32.309> and<00:15:33.309> a<00:15:33.399> lot<00:15:33.549> of<00:15:33.699> cases<00:15:33.910> when 00:15:34.319 --> 00:15:34.329 align:start position:0% message from us and a lot of cases when 00:15:34.329 --> 00:15:35.939 align:start position:0% message from us and a lot of cases when we<00:15:34.480> were<00:15:34.600> trying<00:15:34.809> to<00:15:34.959> proactively<00:15:35.470> reach<00:15:35.769> out 00:15:35.939 --> 00:15:35.949 align:start position:0% we were trying to proactively reach out 00:15:35.949 --> 00:15:38.129 align:start position:0% we were trying to proactively reach out to<00:15:36.069> exchanges<00:15:36.639> they<00:15:37.089> told<00:15:37.449> us<00:15:37.689> to<00:15:37.899> file 00:15:38.129 --> 00:15:38.139 align:start position:0% to exchanges they told us to file 00:15:38.139 --> 00:15:41.100 align:start position:0% to exchanges they told us to file customer<00:15:38.740> support<00:15:39.100> tickets<00:15:39.549> which<00:15:40.480> is<00:15:40.629> not 00:15:41.100 --> 00:15:41.110 align:start position:0% customer support tickets which is not 00:15:41.110 --> 00:15:43.049 align:start position:0% customer support tickets which is not available<00:15:41.339> and<00:15:42.339> it<00:15:42.429> put<00:15:42.610> me<00:15:42.759> in<00:15:42.850> a<00:15:42.939> position 00:15:43.049 --> 00:15:43.059 align:start position:0% available and it put me in a position 00:15:43.059 --> 00:15:45.629 align:start position:0% available and it put me in a position where<00:15:43.420> I<00:15:43.569> had<00:15:44.019> to<00:15:44.199> hope<00:15:44.470> that<00:15:45.069> when<00:15:45.249> we<00:15:45.279> have 00:15:45.629 --> 00:15:45.639 align:start position:0% where I had to hope that when we have 00:15:45.639 --> 00:15:48.749 align:start position:0% where I had to hope that when we have emergency<00:15:46.329> part<00:15:47.319> forking<00:15:47.799> happening<00:15:48.220> in<00:15:48.309> 24 00:15:48.749 --> 00:15:48.759 align:start position:0% emergency part forking happening in 24 00:15:48.759 --> 00:15:49.680 align:start position:0% emergency part forking happening in 24 hours 00:15:49.680 --> 00:15:49.690 align:start position:0% hours 00:15:49.690 --> 00:15:51.300 align:start position:0% hours some<00:15:49.990> exchanges<00:15:50.650> going<00:15:50.950> to<00:15:51.070> pay<00:15:51.280> less 00:15:51.300 --> 00:15:51.310 align:start position:0% some exchanges going to pay less 00:15:51.310 --> 00:15:54.240 align:start position:0% some exchanges going to pay less attention<00:15:51.550> in<00:15:52.300> public<00:15:52.630> process<00:15:53.110> or<00:15:53.920> in 00:15:54.240 --> 00:15:54.250 align:start position:0% attention in public process or in 00:15:54.250 --> 00:15:58.050 align:start position:0% attention in public process or in advisory<00:15:55.290> from<00:15:56.290> support<00:15:56.980> all<00:15:57.610> the<00:15:57.850> way<00:15:57.940> to 00:15:58.050 --> 00:15:58.060 align:start position:0% advisory from support all the way to 00:15:58.060 --> 00:16:00.540 align:start position:0% advisory from support all the way to engineering<00:15:58.660> their<00:15:58.780> security<00:15:59.320> in<00:15:59.980> enough 00:16:00.540 --> 00:16:00.550 align:start position:0% engineering their security in enough 00:16:00.550 --> 00:16:02.790 align:start position:0% engineering their security in enough time<00:16:00.910> for<00:16:01.150> them<00:16:01.270> to<00:16:01.330> act<00:16:01.690> but<00:16:01.930> leave<00:16:02.200> and<00:16:02.500> not 00:16:02.790 --> 00:16:02.800 align:start position:0% time for them to act but leave and not 00:16:02.800 --> 00:16:04.860 align:start position:0% time for them to act but leave and not be<00:16:03.010> harmed<00:16:03.460> because<00:16:03.700> realistically<00:16:04.390> the 00:16:04.860 --> 00:16:04.870 align:start position:0% be harmed because realistically the 00:16:04.870 --> 00:16:07.770 align:start position:0% be harmed because realistically the moment<00:16:05.260> attach<00:16:05.680> plans<00:16:06.610> in<00:16:07.300> your<00:16:07.570> code 00:16:07.770 --> 00:16:07.780 align:start position:0% moment attach plans in your code 00:16:07.780 --> 00:16:11.010 align:start position:0% moment attach plans in your code Facebook<00:16:08.230> and<00:16:08.380> your<00:16:08.590> github<00:16:08.920> repo<00:16:09.570> not<00:16:10.570> really 00:16:11.010 --> 00:16:11.020 align:start position:0% Facebook and your github repo not really 00:16:11.020 --> 00:16:13.080 align:start position:0% Facebook and your github repo not really trivial<00:16:11.290> if<00:16:11.740> you're<00:16:11.920> good<00:16:12.190> at<00:16:12.550> rehearsing 00:16:13.080 --> 00:16:13.090 align:start position:0% trivial if you're good at rehearsing 00:16:13.090 --> 00:16:16.110 align:start position:0% trivial if you're good at rehearsing hearing<00:16:13.570> to<00:16:14.110> figure<00:16:14.440> out<00:16:14.680> what<00:16:15.340> changed<00:16:15.910> and 00:16:16.110 --> 00:16:16.120 align:start position:0% hearing to figure out what changed and 00:16:16.120 --> 00:16:17.970 align:start position:0% hearing to figure out what changed and to<00:16:16.210> find<00:16:16.450> and<00:16:16.630> exploit<00:16:17.050> and<00:16:17.350> then<00:16:17.440> turn<00:16:17.770> them 00:16:17.970 --> 00:16:17.980 align:start position:0% to find and exploit and then turn them 00:16:17.980 --> 00:16:20.280 align:start position:0% to find and exploit and then turn them around<00:16:18.130> and<00:16:18.520> automate<00:16:19.120> attacks<00:16:19.450> against 00:16:20.280 --> 00:16:20.290 align:start position:0% around and automate attacks against 00:16:20.290 --> 00:16:21.840 align:start position:0% around and automate attacks against anyone<00:16:20.620> who<00:16:20.650> hasn't<00:16:20.980> passed<00:16:21.280> yet 00:16:21.840 --> 00:16:21.850 align:start position:0% anyone who hasn't passed yet 00:16:21.850 --> 00:16:24.330 align:start position:0% anyone who hasn't passed yet it's<00:16:22.300> basically<00:16:23.020> relatively<00:16:23.950> simple 00:16:24.330 --> 00:16:24.340 align:start position:0% it's basically relatively simple 00:16:24.340 --> 00:16:29.340 align:start position:0% it's basically relatively simple reconnaissance<00:16:25.000> and<00:16:27.120> so<00:16:28.120> if<00:16:28.780> you<00:16:28.990> happen<00:16:29.170> to 00:16:29.340 --> 00:16:29.350 align:start position:0% reconnaissance and so if you happen to 00:16:29.350 --> 00:16:31.590 align:start position:0% reconnaissance and so if you happen to know<00:16:29.530> anyone<00:16:29.740> in<00:16:30.280> a<00:16:30.430> position<00:16:30.700> at<00:16:31.030> an<00:16:31.210> exchange 00:16:31.590 --> 00:16:31.600 align:start position:0% know anyone in a position at an exchange 00:16:31.600 --> 00:16:34.320 align:start position:0% know anyone in a position at an exchange to<00:16:31.840> set<00:16:32.020> up<00:16:32.110> a<00:16:32.200> security<00:16:32.350> act<00:16:32.950> if<00:16:33.550> it<00:16:33.760> company 00:16:34.320 --> 00:16:34.330 align:start position:0% to set up a security act if it company 00:16:34.330 --> 00:16:37.620 align:start position:0% to set up a security act if it company who<00:16:34.930> relies<00:16:35.530> on<00:16:35.560> blockchain<00:16:36.190> code<00:16:36.670> if<00:16:37.390> you're 00:16:37.620 --> 00:16:37.630 align:start position:0% who relies on blockchain code if you're 00:16:37.630 --> 00:16:39.990 align:start position:0% who relies on blockchain code if you're a<00:16:37.690> developer<00:16:37.960> who<00:16:38.590> you<00:16:39.040> know<00:16:39.130> works<00:16:39.640> with<00:16:39.970> a 00:16:39.990 --> 00:16:40.000 align:start position:0% a developer who you know works with a 00:16:40.000 --> 00:16:42.230 align:start position:0% a developer who you know works with a bunch<00:16:40.270> of<00:16:40.360> different<00:16:40.660> projects<00:16:41.080> Holy's 00:16:42.230 --> 00:16:42.240 align:start position:0% bunch of different projects Holy's 00:16:42.240 --> 00:16:45.210 align:start position:0% bunch of different projects Holy's security<00:16:43.240> a<00:16:43.420> Kitfox<00:16:43.750> but<00:16:44.560> some<00:16:44.860> form<00:16:45.160> of 00:16:45.210 --> 00:16:45.220 align:start position:0% security a Kitfox but some form of 00:16:45.220 --> 00:16:47.640 align:start position:0% security a Kitfox but some form of obnoxious<00:16:46.060> alerting<00:16:46.540> so<00:16:47.170> that<00:16:47.290> instead<00:16:47.590> of 00:16:47.640 --> 00:16:47.650 align:start position:0% obnoxious alerting so that instead of 00:16:47.650 --> 00:16:49.950 align:start position:0% obnoxious alerting so that instead of just<00:16:47.860> having<00:16:48.040> that<00:16:48.340> be<00:16:48.520> a<00:16:48.550> reactant<00:16:49.240> place<00:16:49.480> we 00:16:49.950 --> 00:16:49.960 align:start position:0% just having that be a reactant place we 00:16:49.960 --> 00:16:51.840 align:start position:0% just having that be a reactant place we can<00:16:50.140> at<00:16:50.260> least<00:16:50.290> quickly<00:16:51.010> good<00:16:51.340> to<00:16:51.610> you<00:16:51.670> and 00:16:51.840 --> 00:16:51.850 align:start position:0% can at least quickly good to you and 00:16:51.850 --> 00:16:56.220 align:start position:0% can at least quickly good to you and tell<00:16:52.030> me<00:16:52.120> what's<00:16:52.360> up<00:16:53.100> so<00:16:54.660> we<00:16:55.660> have<00:16:55.840> this<00:16:55.960> giant 00:16:56.220 --> 00:16:56.230 align:start position:0% tell me what's up so we have this giant 00:16:56.230 --> 00:16:58.500 align:start position:0% tell me what's up so we have this giant perspective<00:16:57.040> and<00:16:57.340> basically<00:16:57.910> what<00:16:58.090> happened 00:16:58.500 --> 00:16:58.510 align:start position:0% perspective and basically what happened 00:16:58.510 --> 00:17:00.930 align:start position:0% perspective and basically what happened as<00:16:58.750> part<00:16:58.990> of<00:16:59.080> the<00:16:59.170> retrospective<00:16:59.830> what's<00:17:00.760> this 00:17:00.930 --> 00:17:00.940 align:start position:0% as part of the retrospective what's this 00:17:00.940 --> 00:17:03.780 align:start position:0% as part of the retrospective what's this I<00:17:01.270> had<00:17:01.930> to<00:17:01.960> figure<00:17:02.200> out<00:17:02.410> a<00:17:02.440> bunch<00:17:02.680> of<00:17:02.830> ways<00:17:03.010> to 00:17:03.780 --> 00:17:03.790 align:start position:0% I had to figure out a bunch of ways to 00:17:03.790 --> 00:17:06.120 align:start position:0% I had to figure out a bunch of ways to make<00:17:04.000> the<00:17:04.180> process<00:17:04.600> that<00:17:04.900> we<00:17:05.200> had<00:17:05.830> to<00:17:05.980> go 00:17:06.120 --> 00:17:06.130 align:start position:0% make the process that we had to go 00:17:06.130 --> 00:17:08.370 align:start position:0% make the process that we had to go through<00:17:06.310> this<00:17:06.520> first<00:17:06.730> time<00:17:07.030> much<00:17:07.990> much<00:17:08.230> much 00:17:08.370 --> 00:17:08.380 align:start position:0% through this first time much much much 00:17:08.380 --> 00:17:10.980 align:start position:0% through this first time much much much better<00:17:08.590> and<00:17:09.040> I<00:17:09.550> will<00:17:09.730> be<00:17:10.000> I'll<00:17:10.240> make<00:17:10.510> sure<00:17:10.720> I 00:17:10.980 --> 00:17:10.990 align:start position:0% better and I will be I'll make sure I 00:17:10.990 --> 00:17:13.140 align:start position:0% better and I will be I'll make sure I post<00:17:11.260> these<00:17:11.410> slides<00:17:11.470> online<00:17:11.890> and<00:17:12.460> it<00:17:12.640> links<00:17:13.120> to 00:17:13.140 --> 00:17:13.150 align:start position:0% post these slides online and it links to 00:17:13.150 --> 00:17:14.670 align:start position:0% post these slides online and it links to all<00:17:13.390> of<00:17:13.510> the<00:17:13.600> things<00:17:13.630> that<00:17:14.020> I've<00:17:14.110> screen<00:17:14.410> right 00:17:14.670 --> 00:17:14.680 align:start position:0% all of the things that I've screen right 00:17:14.680 --> 00:17:17.550 align:start position:0% all of the things that I've screen right here<00:17:14.710> but<00:17:15.670> basically<00:17:15.820> what<00:17:16.810> we<00:17:16.960> realize<00:17:17.350> this 00:17:17.550 --> 00:17:17.560 align:start position:0% here but basically what we realize this 00:17:17.560 --> 00:17:21.390 align:start position:0% here but basically what we realize this is<00:17:18.000> we<00:17:19.000> built<00:17:19.240> a<00:17:19.360> public<00:17:19.660> watching<00:17:20.190> and<00:17:21.190> it's 00:17:21.390 --> 00:17:21.400 align:start position:0% is we built a public watching and it's 00:17:21.400 --> 00:17:23.220 align:start position:0% is we built a public watching and it's probably<00:17:21.640> time<00:17:22.000> to<00:17:22.150> figure<00:17:22.330> out<00:17:22.510> how<00:17:22.900> and 00:17:23.220 --> 00:17:23.230 align:start position:0% probably time to figure out how and 00:17:23.230 --> 00:17:26.190 align:start position:0% probably time to figure out how and where<00:17:23.440> the<00:17:23.770> firefighters<00:17:24.430> and<00:17:24.670> our<00:17:25.480> emergency 00:17:26.190 --> 00:17:26.200 align:start position:0% where the firefighters and our emergency 00:17:26.200 --> 00:17:28.630 align:start position:0% where the firefighters and our emergency services<00:17:26.700> so 00:17:28.630 --> 00:17:28.640 align:start position:0% services so 00:17:28.640 --> 00:17:30.190 align:start position:0% services so that<00:17:28.970> was<00:17:29.060> interesting<00:17:29.330> about<00:17:29.630> me<00:17:29.870> being<00:17:30.080> an 00:17:30.190 --> 00:17:30.200 align:start position:0% that was interesting about me being an 00:17:30.200 --> 00:17:33.400 align:start position:0% that was interesting about me being an Australian<00:17:30.830> Spence<00:17:31.190> I<00:17:31.460> happen<00:17:32.450> to<00:17:32.480> be 00:17:33.400 --> 00:17:33.410 align:start position:0% Australian Spence I happen to be 00:17:33.410 --> 00:17:35.530 align:start position:0% Australian Spence I happen to be speaking<00:17:33.890> at<00:17:34.280> a<00:17:34.340> conference<00:17:34.760> that<00:17:35.120> was<00:17:35.240> their 00:17:35.530 --> 00:17:35.540 align:start position:0% speaking at a conference that was their 00:17:35.540 --> 00:17:37.660 align:start position:0% speaking at a conference that was their national<00:17:36.080> conference<00:17:36.290> or<00:17:36.890> their<00:17:37.130> computer 00:17:37.660 --> 00:17:37.670 align:start position:0% national conference or their computer 00:17:37.670 --> 00:17:40.900 align:start position:0% national conference or their computer emergency<00:17:37.910> response<00:17:38.630> teams<00:17:38.990> which<00:17:39.860> I<00:17:40.220> wanted 00:17:40.900 --> 00:17:40.910 align:start position:0% emergency response teams which I wanted 00:17:40.910 --> 00:17:42.340 align:start position:0% emergency response teams which I wanted to<00:17:40.970> go<00:17:41.090> there<00:17:41.300> because<00:17:41.660> we<00:17:41.750> wanted<00:17:41.990> to<00:17:42.140> learn<00:17:42.290> a 00:17:42.340 --> 00:17:42.350 align:start position:0% to go there because we wanted to learn a 00:17:42.350 --> 00:17:45.070 align:start position:0% to go there because we wanted to learn a lot<00:17:42.620> about<00:17:42.830> this<00:17:43.310> public-private<00:17:44.080> academic 00:17:45.070 --> 00:17:45.080 align:start position:0% lot about this public-private academic 00:17:45.080 --> 00:17:46.980 align:start position:0% lot about this public-private academic partnership<00:17:45.710> of<00:17:46.160> a<00:17:46.280> bunch<00:17:46.520> of<00:17:46.610> organizations 00:17:46.980 --> 00:17:46.990 align:start position:0% partnership of a bunch of organizations 00:17:46.990 --> 00:17:51.730 align:start position:0% partnership of a bunch of organizations who<00:17:47.990> get<00:17:48.500> an<00:17:48.620> emergency<00:17:49.090> can<00:17:50.090> pop<00:17:50.690> up<00:17:50.900> and<00:17:51.080> they 00:17:51.730 --> 00:17:51.740 align:start position:0% who get an emergency can pop up and they 00:17:51.740 --> 00:17:54.700 align:start position:0% who get an emergency can pop up and they immediately<00:17:52.700> help<00:17:53.240> organizations<00:17:54.200> of<00:17:54.470> any 00:17:54.700 --> 00:17:54.710 align:start position:0% immediately help organizations of any 00:17:54.710 --> 00:17:56.470 align:start position:0% immediately help organizations of any size<00:17:55.040> of<00:17:55.370> any<00:17:55.580> kind 00:17:56.470 --> 00:17:56.480 align:start position:0% size of any kind 00:17:56.480 --> 00:17:59.080 align:start position:0% size of any kind all<00:17:56.750> of<00:17:56.930> these<00:17:57.140> problems<00:17:57.710> they<00:17:57.980> come<00:17:58.220> when<00:17:58.850> big 00:17:59.080 --> 00:17:59.090 align:start position:0% all of these problems they come when big 00:17:59.090 --> 00:18:00.610 align:start position:0% all of these problems they come when big security<00:17:59.600> problems<00:17:59.990> happen 00:18:00.610 --> 00:18:00.620 align:start position:0% security problems happen 00:18:00.620 --> 00:18:03.340 align:start position:0% security problems happen this<00:18:00.950> particular<00:18:01.580> sir<00:18:01.940> even<00:18:02.840> though<00:18:02.960> hard<00:18:03.230> to 00:18:03.340 --> 00:18:03.350 align:start position:0% this particular sir even though hard to 00:18:03.350 --> 00:18:06.030 align:start position:0% this particular sir even though hard to eat<00:18:03.470> alone<00:18:03.860> I<00:18:04.130> think<00:18:04.190> all<00:18:04.460> had<00:18:04.850> some<00:18:05.090> fantastic 00:18:06.030 --> 00:18:06.040 align:start position:0% eat alone I think all had some fantastic 00:18:06.040 --> 00:18:08.530 align:start position:0% eat alone I think all had some fantastic stories<00:18:07.040> about<00:18:07.520> how<00:18:07.820> they<00:18:08.060> helped<00:18:08.330> their 00:18:08.530 --> 00:18:08.540 align:start position:0% stories about how they helped their 00:18:08.540 --> 00:18:10.620 align:start position:0% stories about how they helped their members<00:18:08.900> and<00:18:09.170> how<00:18:09.350> they<00:18:09.500> were<00:18:09.620> able<00:18:09.800> to<00:18:10.040> help 00:18:10.620 --> 00:18:10.630 align:start position:0% members and how they were able to help 00:18:10.630 --> 00:18:13.150 align:start position:0% members and how they were able to help civic<00:18:11.630> governments<00:18:12.230> and<00:18:12.410> university<00:18:13.100> is 00:18:13.150 --> 00:18:13.160 align:start position:0% civic governments and university is 00:18:13.160 --> 00:18:15.730 align:start position:0% civic governments and university is basically<00:18:13.670> patched<00:18:14.120> and<00:18:14.510> quickly<00:18:15.110> identified 00:18:15.730 --> 00:18:15.740 align:start position:0% basically patched and quickly identified 00:18:15.740 --> 00:18:25.740 align:start position:0% basically patched and quickly identified what<00:18:21.760> we<00:18:22.760> have<00:18:23.480> public<00:18:23.900> stuff<00:18:24.110> it's<00:18:24.380> important 00:18:25.740 --> 00:18:25.750 align:start position:0% what we have public stuff it's important 00:18:25.750 --> 00:18:29.170 align:start position:0% what we have public stuff it's important so<00:18:26.750> what<00:18:27.200> we<00:18:27.290> realized<00:18:27.470> is<00:18:28.040> we<00:18:29.000> should 00:18:29.170 --> 00:18:29.180 align:start position:0% so what we realized is we should 00:18:29.180 --> 00:18:32.140 align:start position:0% so what we realized is we should probably<00:18:29.360> stand<00:18:29.780> this<00:18:29.960> up<00:18:30.640> we<00:18:31.640> can<00:18:31.790> leave<00:18:31.970> it 00:18:32.140 --> 00:18:32.150 align:start position:0% probably stand this up we can leave it 00:18:32.150 --> 00:18:34.210 align:start position:0% probably stand this up we can leave it someone<00:18:32.480> decentralized<00:18:33.170> you<00:18:33.590> probably<00:18:33.950> need 00:18:34.210 --> 00:18:34.220 align:start position:0% someone decentralized you probably need 00:18:34.220 --> 00:18:36.280 align:start position:0% someone decentralized you probably need some<00:18:34.280> folks<00:18:34.670> from<00:18:34.790> our<00:18:34.970> management<00:18:35.330> probably 00:18:36.280 --> 00:18:36.290 align:start position:0% some folks from our management probably 00:18:36.290 --> 00:18:38.890 align:start position:0% some folks from our management probably need<00:18:36.470> for<00:18:36.710> developers<00:18:37.250> we<00:18:37.970> definitely<00:18:38.570> have 00:18:38.890 --> 00:18:38.900 align:start position:0% need for developers we definitely have 00:18:38.900 --> 00:18:44.160 align:start position:0% need for developers we definitely have to<00:18:38.930> give<00:18:39.440> our<00:18:39.800> network<00:18:40.160> operators<00:18:40.850> as<00:18:41.090> a<00:18:41.510> table 00:18:44.160 --> 00:18:44.170 align:start position:0% 00:18:44.170 --> 00:18:46.690 align:start position:0% you<00:18:45.170> don't<00:18:45.380> just<00:18:45.740> have<00:18:45.980> to<00:18:46.040> have<00:18:46.310> everyone 00:18:46.690 --> 00:18:46.700 align:start position:0% you don't just have to have everyone 00:18:46.700 --> 00:18:49.450 align:start position:0% you don't just have to have everyone around<00:18:46.940> for<00:18:47.270> an<00:18:47.360> emergency<00:18:47.750> we<00:18:48.470> can<00:18:48.680> also<00:18:49.010> use 00:18:49.450 --> 00:18:49.460 align:start position:0% around for an emergency we can also use 00:18:49.460 --> 00:18:52.030 align:start position:0% around for an emergency we can also use this<00:18:49.700> group<00:18:50.000> as<00:18:50.210> a<00:18:51.080> way<00:18:51.350> to<00:18:51.440> make<00:18:51.590> everyone's 00:18:52.030 --> 00:18:52.040 align:start position:0% this group as a way to make everyone's 00:18:52.040 --> 00:18:54.700 align:start position:0% this group as a way to make everyone's murder<00:18:52.370> about<00:18:52.850> insecurity<00:18:53.380> instead<00:18:54.380> of<00:18:54.500> being 00:18:54.700 --> 00:18:54.710 align:start position:0% murder about insecurity instead of being 00:18:54.710 --> 00:18:56.080 align:start position:0% murder about insecurity instead of being in<00:18:54.830> a<00:18:54.890> position<00:18:55.160> where<00:18:55.520> we're<00:18:55.760> the<00:18:55.910> ones 00:18:56.080 --> 00:18:56.090 align:start position:0% in a position where we're the ones 00:18:56.090 --> 00:18:58.420 align:start position:0% in a position where we're the ones doling<00:18:56.600> out<00:18:56.690> advisories<00:18:57.560> and<00:18:57.830> maturity 00:18:58.420 --> 00:18:58.430 align:start position:0% doling out advisories and maturity 00:18:58.430 --> 00:19:01.270 align:start position:0% doling out advisories and maturity models<00:18:58.910> and<00:18:59.210> all<00:19:00.050> kinds<00:19:00.560> of<00:19:00.620> tips<00:19:00.890> for<00:19:01.100> how<00:19:01.250> to 00:19:01.270 --> 00:19:01.280 align:start position:0% models and all kinds of tips for how to 00:19:01.280 --> 00:19:06.080 align:start position:0% models and all kinds of tips for how to run<00:19:02.000> your<00:19:02.030> AWS<00:19:02.840> staff<00:19:03.230> or<00:19:03.500> your<00:19:03.590> GP 00:19:06.080 --> 00:19:06.090 align:start position:0% run your AWS staff or your GP 00:19:06.090 --> 00:19:08.719 align:start position:0% run your AWS staff or your GP put<00:19:06.690> out<00:19:06.899> proactive<00:19:07.799> educational 00:19:08.719 --> 00:19:08.729 align:start position:0% put out proactive educational 00:19:08.729 --> 00:19:11.389 align:start position:0% put out proactive educational information<00:19:09.389> to<00:19:09.899> help<00:19:10.139> mature<00:19:10.559> the<00:19:11.070> entire 00:19:11.389 --> 00:19:11.399 align:start position:0% information to help mature the entire 00:19:11.399 --> 00:19:15.229 align:start position:0% information to help mature the entire network<00:19:12.139> so<00:19:13.399> here's<00:19:14.399> what<00:19:14.580> we<00:19:14.700> came<00:19:14.879> up<00:19:15.059> with 00:19:15.229 --> 00:19:15.239 align:start position:0% network so here's what we came up with 00:19:15.239 --> 00:19:18.739 align:start position:0% network so here's what we came up with as<00:19:15.539> potential<00:19:16.499> core<00:19:16.769> refinement<00:19:17.749> it's 00:19:18.739 --> 00:19:18.749 align:start position:0% as potential core refinement it's 00:19:18.749 --> 00:19:21.169 align:start position:0% as potential core refinement it's probably<00:19:19.200> best<00:19:19.440> when<00:19:19.830> you<00:19:20.039> are<00:19:20.119> responding<00:19:21.119> to 00:19:21.169 --> 00:19:21.179 align:start position:0% probably best when you are responding to 00:19:21.179 --> 00:19:22.909 align:start position:0% probably best when you are responding to an<00:19:21.359> incident<00:19:21.629> and<00:19:22.139> not<00:19:22.289> have<00:19:22.619> to<00:19:22.739> deal<00:19:22.859> with 00:19:22.909 --> 00:19:22.919 align:start position:0% an incident and not have to deal with 00:19:22.919 --> 00:19:26.259 align:start position:0% an incident and not have to deal with like<00:19:23.159> 107<00:19:24.090> people<00:19:24.419> at<00:19:24.539> once<00:19:24.779> it<00:19:25.529> gets<00:19:25.739> busy 00:19:26.259 --> 00:19:26.269 align:start position:0% like 107 people at once it gets busy 00:19:26.269 --> 00:19:28.700 align:start position:0% like 107 people at once it gets busy it's<00:19:27.269> usually<00:19:27.450> better<00:19:27.869> than<00:19:28.080> five<00:19:28.289> your<00:19:28.499> end 00:19:28.700 --> 00:19:28.710 align:start position:0% it's usually better than five your end 00:19:28.710 --> 00:19:32.419 align:start position:0% it's usually better than five your end as<00:19:29.219> less<00:19:29.489> than<00:19:29.700> 10<00:19:29.909> I<00:19:30.649> was<00:19:31.649> thinking<00:19:31.979> about<00:19:32.129> fun 00:19:32.419 --> 00:19:32.429 align:start position:0% as less than 10 I was thinking about fun 00:19:32.429 --> 00:19:34.009 align:start position:0% as less than 10 I was thinking about fun outfits<00:19:32.849> to<00:19:33.029> plan<00:19:33.269> for<00:19:33.570> when<00:19:33.690> we<00:19:33.809> have<00:19:33.840> to 00:19:34.009 --> 00:19:34.019 align:start position:0% outfits to plan for when we have to 00:19:34.019 --> 00:19:36.589 align:start position:0% outfits to plan for when we have to respond<00:19:34.499> to<00:19:34.619> emergencies<00:19:35.359> spacesuits<00:19:36.359> make 00:19:36.589 --> 00:19:36.599 align:start position:0% respond to emergencies spacesuits make 00:19:36.599 --> 00:19:38.329 align:start position:0% respond to emergencies spacesuits make it<00:19:36.719> really<00:19:36.960> hurt<00:19:37.200> too<00:19:37.320> tight<00:19:37.559> so<00:19:37.859> I<00:19:38.070> killed 00:19:38.329 --> 00:19:38.339 align:start position:0% it really hurt too tight so I killed 00:19:38.339 --> 00:19:41.119 align:start position:0% it really hurt too tight so I killed that<00:19:38.489> idea<00:19:38.989> but<00:19:39.989> that<00:19:40.109> being<00:19:40.289> said<00:19:40.379> we 00:19:41.119 --> 00:19:41.129 align:start position:0% that idea but that being said we 00:19:41.129 --> 00:19:43.459 align:start position:0% that idea but that being said we basically<00:19:41.729> decided<00:19:42.210> you<00:19:42.690> know<00:19:42.839> what<00:19:43.169> we<00:19:43.440> are 00:19:43.459 --> 00:19:43.469 align:start position:0% basically decided you know what we are 00:19:43.469 --> 00:19:45.979 align:start position:0% basically decided you know what we are going<00:19:43.889> to<00:19:44.009> take<00:19:44.519> this<00:19:44.700> group<00:19:44.940> together<00:19:45.149> we 00:19:45.979 --> 00:19:45.989 align:start position:0% going to take this group together we 00:19:45.989 --> 00:19:47.209 align:start position:0% going to take this group together we need<00:19:46.139> to<00:19:46.259> make<00:19:46.440> sure<00:19:46.619> that<00:19:46.830> we've<00:19:47.009> got<00:19:47.190> people 00:19:47.209 --> 00:19:47.219 align:start position:0% need to make sure that we've got people 00:19:47.219 --> 00:19:48.619 align:start position:0% need to make sure that we've got people who<00:19:47.700> are<00:19:47.729> from<00:19:47.999> different<00:19:48.029> parts<00:19:48.419> of<00:19:48.570> the 00:19:48.619 --> 00:19:48.629 align:start position:0% who are from different parts of the 00:19:48.629 --> 00:19:50.719 align:start position:0% who are from different parts of the world<00:19:48.779> that<00:19:49.080> aren't<00:19:49.499> just<00:19:49.739> North<00:19:49.889> America<00:19:50.399> and 00:19:50.719 --> 00:19:50.729 align:start position:0% world that aren't just North America and 00:19:50.729 --> 00:19:53.119 align:start position:0% world that aren't just North America and we<00:19:51.719> probably<00:19:51.960> need<00:19:52.349> to<00:19:52.379> make<00:19:52.619> sure<00:19:52.679> that<00:19:52.979> it's 00:19:53.119 --> 00:19:53.129 align:start position:0% we probably need to make sure that it's 00:19:53.129 --> 00:19:55.310 align:start position:0% we probably need to make sure that it's distributed<00:19:53.759> across<00:19:54.179> multiple<00:19:54.779> kinds<00:19:55.139> of 00:19:55.310 --> 00:19:55.320 align:start position:0% distributed across multiple kinds of 00:19:55.320 --> 00:19:56.899 align:start position:0% distributed across multiple kinds of stakeholders<00:19:55.589> so<00:19:56.159> we<00:19:56.249> have<00:19:56.399> valid<00:19:56.669> leaders 00:19:56.899 --> 00:19:56.909 align:start position:0% stakeholders so we have valid leaders 00:19:56.909 --> 00:19:58.669 align:start position:0% stakeholders so we have valid leaders from<00:19:57.059> tons<00:19:57.299> of<00:19:57.479> stake<00:19:57.690> and<00:19:58.259> we<00:19:58.409> have<00:19:58.529> small 00:19:58.669 --> 00:19:58.679 align:start position:0% from tons of stake and we have small 00:19:58.679 --> 00:20:01.190 align:start position:0% from tons of stake and we have small validator<00:19:59.279> community<00:19:59.909> aren't<00:20:00.119> as<00:20:00.359> mature<00:20:00.690> on 00:20:01.190 --> 00:20:01.200 align:start position:0% validator community aren't as mature on 00:20:01.200 --> 00:20:04.519 align:start position:0% validator community aren't as mature on the<00:20:01.289> security<00:20:01.799> front<00:20:01.859> and<00:20:02.369> who<00:20:03.299> need<00:20:04.049> a<00:20:04.080> little 00:20:04.519 --> 00:20:04.529 align:start position:0% the security front and who need a little 00:20:04.529 --> 00:20:07.310 align:start position:0% the security front and who need a little bit<00:20:04.739> more<00:20:04.919> support<00:20:05.369> from<00:20:05.519> us<00:20:05.789> to<00:20:06.779> be<00:20:06.929> doing<00:20:07.229> the 00:20:07.310 --> 00:20:07.320 align:start position:0% bit more support from us to be doing the 00:20:07.320 --> 00:20:10.369 align:start position:0% bit more support from us to be doing the best<00:20:07.499> big<00:20:07.799> canvas<00:20:08.279> particular<00:20:08.879> mix<00:20:09.210> those<00:20:10.200> who 00:20:10.369 --> 00:20:10.379 align:start position:0% best big canvas particular mix those who 00:20:10.379 --> 00:20:11.959 align:start position:0% best big canvas particular mix those who realize<00:20:10.679> we<00:20:10.889> probably<00:20:11.129> should<00:20:11.489> outline 00:20:11.959 --> 00:20:11.969 align:start position:0% realize we probably should outline 00:20:11.969 --> 00:20:16.009 align:start position:0% realize we probably should outline expectations<00:20:12.960> for<00:20:13.109> service<00:20:13.849> so<00:20:14.849> initially<00:20:15.839> we 00:20:16.009 --> 00:20:16.019 align:start position:0% expectations for service so initially we 00:20:16.019 --> 00:20:18.499 align:start position:0% expectations for service so initially we were<00:20:16.139> thinking<00:20:16.499> maybe<00:20:16.649> running<00:20:16.919> here<00:20:17.339> that<00:20:18.330> we 00:20:18.499 --> 00:20:18.509 align:start position:0% were thinking maybe running here that we 00:20:18.509 --> 00:20:20.299 align:start position:0% were thinking maybe running here that we would<00:20:18.629> have<00:20:18.839> people<00:20:19.109> as<00:20:19.469> a<00:20:19.559> part<00:20:19.950> of<00:20:20.190> our 00:20:20.299 --> 00:20:20.309 align:start position:0% would have people as a part of our 00:20:20.309 --> 00:20:22.969 align:start position:0% would have people as a part of our certain<00:20:20.700> which<00:20:20.999> we<00:20:21.330> are<00:20:21.659> working<00:20:22.289> on<00:20:22.559> coding 00:20:22.969 --> 00:20:22.979 align:start position:0% certain which we are working on coding 00:20:22.979 --> 00:20:25.999 align:start position:0% certain which we are working on coding now<00:20:23.659> but<00:20:24.659> we<00:20:24.779> wanted<00:20:24.960> to<00:20:25.109> make<00:20:25.259> sure<00:20:25.289> that 00:20:25.999 --> 00:20:26.009 align:start position:0% now but we wanted to make sure that 00:20:26.009 --> 00:20:27.049 align:start position:0% now but we wanted to make sure that we're<00:20:26.399> keeping<00:20:26.549> them<00:20:26.789> accountable 00:20:27.049 --> 00:20:27.059 align:start position:0% we're keeping them accountable 00:20:27.059 --> 00:20:29.899 align:start position:0% we're keeping them accountable especially<00:20:27.539> in<00:20:28.109> the<00:20:28.229> areas<00:20:28.589> of<00:20:28.909> potentiality 00:20:29.899 --> 00:20:29.909 align:start position:0% especially in the areas of potentiality 00:20:29.909 --> 00:20:32.610 align:start position:0% especially in the areas of potentiality and<00:20:29.940> respond<00:20:30.599> if<00:20:31.289> direct<00:20:31.619> or<00:20:31.799> thirteen 00:20:32.610 --> 00:20:32.620 align:start position:0% and respond if direct or thirteen 00:20:32.620 --> 00:20:34.409 align:start position:0% and respond if direct or thirteen and<00:20:32.770> you<00:20:32.980> cut<00:20:33.190> access<00:20:33.460> to<00:20:33.700> the<00:20:33.940> internal<00:20:34.240> 'ti 00:20:34.409 --> 00:20:34.419 align:start position:0% and you cut access to the internal 'ti 00:20:34.419 --> 00:20:36.930 align:start position:0% and you cut access to the internal 'ti information<00:20:35.020> I<00:20:35.260> don't<00:20:36.250> have<00:20:36.400> to<00:20:36.490> be<00:20:36.580> worried 00:20:36.930 --> 00:20:36.940 align:start position:0% information I don't have to be worried 00:20:36.940 --> 00:20:39.480 align:start position:0% information I don't have to be worried that<00:20:37.360> you<00:20:37.600> realized<00:20:38.169> you<00:20:38.620> couldn't<00:20:38.890> use<00:20:39.159> some 00:20:39.480 --> 00:20:39.490 align:start position:0% that you realized you couldn't use some 00:20:39.490 --> 00:20:41.519 align:start position:0% that you realized you couldn't use some learner<00:20:40.090> ability<00:20:40.480> that<00:20:40.630> you<00:20:40.690> have<00:20:40.750> access<00:20:41.049> to 00:20:41.519 --> 00:20:41.529 align:start position:0% learner ability that you have access to 00:20:41.529 --> 00:20:44.430 align:start position:0% learner ability that you have access to to<00:20:41.860> exploit<00:20:42.370> you<00:20:42.760> know<00:20:42.880> a<00:20:43.150> validator<00:20:43.690> in<00:20:44.380> a 00:20:44.430 --> 00:20:44.440 align:start position:0% to exploit you know a validator in a 00:20:44.440 --> 00:20:51.450 align:start position:0% to exploit you know a validator in a single<00:20:44.860> environment<00:20:49.260> post<00:20:50.260> too<00:20:50.559> much<00:20:50.710> and 00:20:51.450 --> 00:20:51.460 align:start position:0% single environment post too much and 00:20:51.460 --> 00:20:54.450 align:start position:0% single environment post too much and telegram<00:20:52.000> channels<00:20:52.470> so<00:20:53.470> there's<00:20:54.250> a<00:20:54.309> couple 00:20:54.450 --> 00:20:54.460 align:start position:0% telegram channels so there's a couple 00:20:54.460 --> 00:20:55.980 align:start position:0% telegram channels so there's a couple things<00:20:54.669> we<00:20:54.850> still<00:20:55.029> like<00:20:55.150> to<00:20:55.179> do<00:20:55.450> to<00:20:55.720> make<00:20:55.840> this 00:20:55.980 --> 00:20:55.990 align:start position:0% things we still like to do to make this 00:20:55.990 --> 00:20:58.260 align:start position:0% things we still like to do to make this successful<00:20:56.380> we<00:20:57.070> have<00:20:57.309> to<00:20:57.730> encourage 00:20:58.260 --> 00:20:58.270 align:start position:0% successful we have to encourage 00:20:58.270 --> 00:21:00.120 align:start position:0% successful we have to encourage everybody<00:20:58.690> to<00:20:58.900> start<00:20:59.200> the<00:20:59.380> security<00:20:59.919> act 00:21:00.120 --> 00:21:00.130 align:start position:0% everybody to start the security act 00:21:00.130 --> 00:21:03.840 align:start position:0% everybody to start the security act email<00:21:00.549> address<00:21:00.909> so<00:21:01.630> we<00:21:02.080> kind<00:21:02.529> send<00:21:03.370> out<00:21:03.580> our 00:21:03.840 --> 00:21:03.850 align:start position:0% email address so we kind send out our 00:21:03.850 --> 00:21:07.409 align:start position:0% email address so we kind send out our signal<00:21:04.390> flare<00:21:04.630> when<00:21:04.960> bad<00:21:05.110> things<00:21:05.140> happen<00:21:06.419> we 00:21:07.409 --> 00:21:07.419 align:start position:0% signal flare when bad things happen we 00:21:07.419 --> 00:21:09.060 align:start position:0% signal flare when bad things happen we are<00:21:07.450> working<00:21:07.750> on<00:21:07.990> adding<00:21:08.260> a<00:21:08.529> security 00:21:09.060 --> 00:21:09.070 align:start position:0% are working on adding a security 00:21:09.070 --> 00:21:12.090 align:start position:0% are working on adding a security perimeter<00:21:09.340> to<00:21:09.789> the<00:21:09.880> cosmos<00:21:10.270> SDK<00:21:10.830> basically<00:21:11.830> a 00:21:12.090 --> 00:21:12.100 align:start position:0% perimeter to the cosmos SDK basically a 00:21:12.100 --> 00:21:14.159 align:start position:0% perimeter to the cosmos SDK basically a place<00:21:12.399> to<00:21:12.669> state<00:21:12.880> your<00:21:13.029> security<00:21:13.450> I<00:21:13.720> email 00:21:14.159 --> 00:21:14.169 align:start position:0% place to state your security I email 00:21:14.169 --> 00:21:17.460 align:start position:0% place to state your security I email address<00:21:14.500> where<00:21:15.309> I<00:21:15.490> can<00:21:16.000> query<00:21:16.929> the<00:21:17.169> network 00:21:17.460 --> 00:21:17.470 align:start position:0% address where I can query the network 00:21:17.470 --> 00:21:20.100 align:start position:0% address where I can query the network daily<00:21:18.250> for<00:21:18.549> our<00:21:18.789> time<00:21:19.029> note<00:21:19.240> and<00:21:19.809> have<00:21:20.080> a 00:21:20.100 --> 00:21:20.110 align:start position:0% daily for our time note and have a 00:21:20.110 --> 00:21:22.380 align:start position:0% daily for our time note and have a Security<00:21:20.710> Response<00:21:20.740> list<00:21:21.370> instead<00:21:21.880> of<00:21:22.120> going 00:21:22.380 --> 00:21:22.390 align:start position:0% Security Response list instead of going 00:21:22.390 --> 00:21:25.019 align:start position:0% Security Response list instead of going through<00:21:22.419> like<00:21:22.750> 110<00:21:23.710> websites<00:21:24.250> and<00:21:24.520> any<00:21:24.669> given 00:21:25.019 --> 00:21:25.029 align:start position:0% through like 110 websites and any given 00:21:25.029 --> 00:21:27.120 align:start position:0% through like 110 websites and any given time<00:21:25.270> and<00:21:25.600> hoping<00:21:25.990> and<00:21:26.320> by<00:21:26.470> the<00:21:26.529> way<00:21:26.710> to<00:21:26.770> get<00:21:26.919> to 00:21:27.120 --> 00:21:27.130 align:start position:0% time and hoping and by the way to get to 00:21:27.130 --> 00:21:30.450 align:start position:0% time and hoping and by the way to get to human<00:21:27.809> and<00:21:28.809> also<00:21:29.350> realized<00:21:29.980> we<00:21:30.309> should 00:21:30.450 --> 00:21:30.460 align:start position:0% human and also realized we should 00:21:30.460 --> 00:21:32.940 align:start position:0% human and also realized we should probably<00:21:30.700> go<00:21:31.210> ahead<00:21:31.240> and<00:21:31.929> start<00:21:32.350> working<00:21:32.470> on<00:21:32.890> a 00:21:32.940 --> 00:21:32.950 align:start position:0% probably go ahead and start working on a 00:21:32.950 --> 00:21:35.789 align:start position:0% probably go ahead and start working on a model<00:21:33.370> that<00:21:33.909> allows<00:21:34.330> us<00:21:34.360> to<00:21:34.870> elect 00:21:35.789 --> 00:21:35.799 align:start position:0% model that allows us to elect 00:21:35.799 --> 00:21:38.210 align:start position:0% model that allows us to elect individuals<00:21:36.669> to<00:21:36.940> be<00:21:37.029> represented<00:21:37.690> in<00:21:37.779> this 00:21:38.210 --> 00:21:38.220 align:start position:0% individuals to be represented in this 00:21:38.220 --> 00:21:40.410 align:start position:0% individuals to be represented in this instead<00:21:39.220> of<00:21:39.340> just<00:21:39.550> picking<00:21:39.850> on<00:21:40.090> a<00:21:40.120> bunch<00:21:40.330> of 00:21:40.410 --> 00:21:40.420 align:start position:0% instead of just picking on a bunch of 00:21:40.420 --> 00:21:42.300 align:start position:0% instead of just picking on a bunch of people<00:21:40.750> I<00:21:40.810> know<00:21:41.020> that's<00:21:41.500> probably<00:21:41.710> not<00:21:42.100> the 00:21:42.300 --> 00:21:42.310 align:start position:0% people I know that's probably not the 00:21:42.310 --> 00:21:44.700 align:start position:0% people I know that's probably not the best<00:21:42.340> way<00:21:42.760> to<00:21:43.060> make<00:21:43.510> this<00:21:43.870> particular<00:21:44.530> group 00:21:44.700 --> 00:21:44.710 align:start position:0% best way to make this particular group 00:21:44.710 --> 00:21:46.680 align:start position:0% best way to make this particular group work<00:21:45.010> especially<00:21:45.490> because<00:21:46.060> of<00:21:46.270> the<00:21:46.480> need<00:21:46.660> for 00:21:46.680 --> 00:21:46.690 align:start position:0% work especially because of the need for 00:21:46.690 --> 00:21:49.500 align:start position:0% work especially because of the need for trucks<00:21:47.460> what's<00:21:48.460> really<00:21:48.670> interesting<00:21:48.940> about 00:21:49.500 --> 00:21:49.510 align:start position:0% trucks what's really interesting about 00:21:49.510 --> 00:21:52.830 align:start position:0% trucks what's really interesting about this<00:21:49.960> is<00:21:50.320> we<00:21:51.280> internally<00:21:51.880> have<00:21:52.390> been<00:21:52.540> playing 00:21:52.830 --> 00:21:52.840 align:start position:0% this is we internally have been playing 00:21:52.840 --> 00:21:54.300 align:start position:0% this is we internally have been playing this<00:21:52.990> on<00:21:53.170> the<00:21:53.320> movie<00:21:53.680> called<00:21:53.950> inquanok 00:21:54.300 --> 00:21:54.310 align:start position:0% this on the movie called inquanok 00:21:54.310 --> 00:21:56.190 align:start position:0% this on the movie called inquanok receipt<00:21:54.970> and<00:21:55.300> we've<00:21:55.480> been<00:21:55.630> thinking<00:21:55.930> about 00:21:56.190 --> 00:21:56.200 align:start position:0% receipt and we've been thinking about 00:21:56.200 --> 00:21:59.780 align:start position:0% receipt and we've been thinking about how<00:21:56.950> floor<00:21:57.550> to<00:21:57.730> garments<00:21:58.330> can<00:21:58.570> be<00:21:58.750> a<00:21:58.960> tool<00:21:59.290> to 00:21:59.780 --> 00:21:59.790 align:start position:0% how floor to garments can be a tool to 00:21:59.790 --> 00:22:03.260 align:start position:0% how floor to garments can be a tool to help<00:22:00.790> us<00:22:01.240> accomplish<00:22:01.690> things<00:22:02.080> in<00:22:02.260> a<00:22:02.380> wider 00:22:03.260 --> 00:22:03.270 align:start position:0% help us accomplish things in a wider 00:22:03.270 --> 00:22:07.110 align:start position:0% help us accomplish things in a wider context<00:22:04.270> but<00:22:04.990> I'm<00:22:05.320> pretty<00:22:05.680> proud<00:22:05.920> that<00:22:06.520> I<00:22:06.790> got 00:22:07.110 --> 00:22:07.120 align:start position:0% context but I'm pretty proud that I got 00:22:07.120 --> 00:22:08.550 align:start position:0% context but I'm pretty proud that I got to<00:22:07.240> work<00:22:07.390> with<00:22:07.510> a<00:22:07.600> copy<00:22:07.810> of<00:22:07.960> our<00:22:08.110> protocol 00:22:08.550 --> 00:22:08.560 align:start position:0% to work with a copy of our protocol 00:22:08.560 --> 00:22:10.260 align:start position:0% to work with a copy of our protocol apparently<00:22:09.070> this<00:22:09.190> is<00:22:09.400> really<00:22:09.730> the<00:22:09.910> first 00:22:10.260 --> 00:22:10.270 align:start position:0% apparently this is really the first 00:22:10.270 --> 00:22:12.360 align:start position:0% apparently this is really the first application<00:22:11.230> of<00:22:11.470> that<00:22:11.830> liquid<00:22:12.070> democracy 00:22:12.360 --> 00:22:12.370 align:start position:0% application of that liquid democracy 00:22:12.370 --> 00:22:15.150 align:start position:0% application of that liquid democracy principle<00:22:13.360> that<00:22:13.960> we<00:22:14.260> have<00:22:14.290> been<00:22:14.950> talking 00:22:15.150 --> 00:22:15.160 align:start position:0% principle that we have been talking 00:22:15.160 --> 00:22:17.479 align:start position:0% principle that we have been talking about<00:22:15.400> over<00:22:16.000> the<00:22:16.090> past 00:22:17.479 --> 00:22:17.489 align:start position:0% about over the past 00:22:17.489 --> 00:22:20.609 align:start position:0% about over the past when<00:22:18.489> a<00:22:18.609> delivery<00:22:18.730> to<00:22:19.330> a<00:22:19.359> new<00:22:19.600> module<00:22:19.899> is<00:22:20.379> we're 00:22:20.609 --> 00:22:20.619 align:start position:0% when a delivery to a new module is we're 00:22:20.619 --> 00:22:23.070 align:start position:0% when a delivery to a new module is we're making<00:22:20.919> sure<00:22:20.950> that<00:22:21.159> we<00:22:21.700> are<00:22:21.960> writing<00:22:22.960> the<00:22:23.049> code 00:22:23.070 --> 00:22:23.080 align:start position:0% making sure that we are writing the code 00:22:23.080 --> 00:22:25.080 align:start position:0% making sure that we are writing the code that<00:22:23.590> will<00:22:23.739> govern<00:22:23.950> the<00:22:24.249> ability<00:22:24.639> to<00:22:24.669> turn<00:22:24.970> out 00:22:25.080 --> 00:22:25.090 align:start position:0% that will govern the ability to turn out 00:22:25.090 --> 00:22:27.570 align:start position:0% that will govern the ability to turn out transfers<00:22:25.600> if<00:22:25.899> there's<00:22:26.109> an<00:22:26.200> emergency<00:22:26.580> we 00:22:27.570 --> 00:22:27.580 align:start position:0% transfers if there's an emergency we 00:22:27.580 --> 00:23:14.149 align:start position:0% transfers if there's an emergency we have<00:22:27.609> ten<00:22:27.970> people<00:22:56.639> and<00:22:57.639> we<00:22:58.359> need<00:22:58.509> to<00:22:58.889> go 00:23:14.149 --> 00:23:14.159 align:start position:0% 00:23:14.159 --> 00:23:16.560 align:start position:0% interesting<00:23:15.159> but<00:23:15.879> there's<00:23:16.090> one<00:23:16.299> particular 00:23:16.560 --> 00:23:16.570 align:start position:0% interesting but there's one particular 00:23:16.570 --> 00:23:19.739 align:start position:0% interesting but there's one particular thing<00:23:17.320> where<00:23:17.919> basically<00:23:18.509> they<00:23:19.509> have<00:23:19.690> a 00:23:19.739 --> 00:23:19.749 align:start position:0% thing where basically they have a 00:23:19.749 --> 00:23:22.710 align:start position:0% thing where basically they have a complex<00:23:20.169> ceremony<00:23:20.739> the<00:23:21.460> other<00:23:21.489> goal<00:23:21.879> if<00:23:22.539> I 00:23:22.710 --> 00:23:22.720 align:start position:0% complex ceremony the other goal if I 00:23:22.720 --> 00:23:24.950 align:start position:0% complex ceremony the other goal if I flip<00:23:23.409> the<00:23:23.559> room<00:23:23.739> key<00:23:23.950> among<00:23:24.190> seven 00:23:24.950 --> 00:23:24.960 align:start position:0% flip the room key among seven 00:23:24.960 --> 00:23:26.750 align:start position:0% flip the room key among seven that's<00:23:25.620> the<00:23:25.860> example<00:23:26.250> that<00:23:26.280> I'm<00:23:26.430> looking<00:23:26.550> to 00:23:26.750 --> 00:23:26.760 align:start position:0% that's the example that I'm looking to 00:23:26.760 --> 00:23:30.980 align:start position:0% that's the example that I'm looking to engineer<00:23:27.660> so<00:23:28.200> finally<00:23:29.120> really<00:23:30.120> quick<00:23:30.300> plot 00:23:30.980 --> 00:23:30.990 align:start position:0% engineer so finally really quick plot 00:23:30.990 --> 00:23:33.470 align:start position:0% engineer so finally really quick plot chains<00:23:31.290> and<00:23:32.040> forward<00:23:32.430> mediation<00:23:32.910> tools<00:23:33.150> more 00:23:33.470 --> 00:23:33.480 align:start position:0% chains and forward mediation tools more 00:23:33.480 --> 00:23:34.600 align:start position:0% chains and forward mediation tools more than<00:23:33.690> anything<00:23:33.870> else 00:23:34.600 --> 00:23:34.610 align:start position:0% than anything else 00:23:34.610 --> 00:23:36.800 align:start position:0% than anything else nine-tenths<00:23:35.610> of<00:23:35.700> security<00:23:36.180> is<00:23:36.300> making<00:23:36.660> sure 00:23:36.800 --> 00:23:36.810 align:start position:0% nine-tenths of security is making sure 00:23:36.810 --> 00:23:38.150 align:start position:0% nine-tenths of security is making sure that<00:23:36.930> you're<00:23:37.110> using<00:23:37.140> the<00:23:37.530> right<00:23:37.560> tool<00:23:37.980> to<00:23:38.010> get 00:23:38.150 --> 00:23:38.160 align:start position:0% that you're using the right tool to get 00:23:38.160 --> 00:23:40.940 align:start position:0% that you're using the right tool to get the<00:23:38.280> job<00:23:38.490> done<00:23:38.670> and<00:23:39.420> happen<00:23:40.140> to<00:23:40.170> think<00:23:40.440> on<00:23:40.830> the 00:23:40.940 --> 00:23:40.950 align:start position:0% the job done and happen to think on the 00:23:40.950 --> 00:23:44.000 align:start position:0% the job done and happen to think on the incident<00:23:41.340> response<00:23:41.700> part<00:23:42.050> we<00:23:43.050> could<00:23:43.830> build 00:23:44.000 --> 00:23:44.010 align:start position:0% incident response part we could build 00:23:44.010 --> 00:23:45.800 align:start position:0% incident response part we could build the<00:23:44.190> security<00:23:44.520> incident<00:23:44.880> response<00:23:45.180> that<00:23:45.690> we 00:23:45.800 --> 00:23:45.810 align:start position:0% the security incident response that we 00:23:45.810 --> 00:23:48.830 align:start position:0% the security incident response that we want<00:23:45.960> to<00:23:46.050> be<00:23:46.110> in<00:23:46.230> the<00:23:46.350> world<00:23:47.210> that<00:23:48.210> being<00:23:48.510> said 00:23:48.830 --> 00:23:48.840 align:start position:0% want to be in the world that being said 00:23:48.840 --> 00:23:50.930 align:start position:0% want to be in the world that being said I<00:23:49.170> wanna<00:23:49.680> make<00:23:49.800> sure<00:23:49.980> that<00:23:50.130> I<00:23:50.340> have<00:23:50.640> a<00:23:50.700> shout 00:23:50.930 --> 00:23:50.940 align:start position:0% I wanna make sure that I have a shout 00:23:50.940 --> 00:23:54.020 align:start position:0% I wanna make sure that I have a shout out<00:23:50.970> to<00:23:51.810> my<00:23:52.080> core<00:23:52.440> developers<00:23:53.010> who<00:23:53.490> have<00:23:53.910> been 00:23:54.020 --> 00:23:54.030 align:start position:0% out to my core developers who have been 00:23:54.030 --> 00:23:56.240 align:start position:0% out to my core developers who have been helping<00:23:54.450> make<00:23:55.080> this<00:23:55.320> idea<00:23:55.710> come<00:23:56.040> to<00:23:56.070> life 00:23:56.240 --> 00:23:56.250 align:start position:0% helping make this idea come to life 00:23:56.250 --> 00:23:59.540 align:start position:0% helping make this idea come to life especially<00:23:57.120> rifle<00:23:58.050> into<00:23:58.380> the<00:23:58.620> cloud<00:23:58.920> he<00:23:59.490> is 00:23:59.540 --> 00:23:59.550 align:start position:0% especially rifle into the cloud he is 00:23:59.550 --> 00:24:01.160 align:start position:0% especially rifle into the cloud he is one<00:23:59.760> of<00:23:59.790> the<00:24:00.000> first<00:24:00.180> people<00:24:00.420> to<00:24:00.570> get<00:24:00.720> excited 00:24:01.160 --> 00:24:01.170 align:start position:0% one of the first people to get excited 00:24:01.170 --> 00:24:03.590 align:start position:0% one of the first people to get excited about<00:24:01.230> liquid<00:24:01.680> democracy<00:24:01.910> and<00:24:02.910> whose<00:24:03.300> natural 00:24:03.590 --> 00:24:03.600 align:start position:0% about liquid democracy and whose natural 00:24:03.600 --> 00:24:06.860 align:start position:0% about liquid democracy and whose natural state<00:24:04.110> is<00:24:04.320> just<00:24:04.680> one<00:24:05.300> so<00:24:06.300> thank<00:24:06.480> you<00:24:06.540> very<00:24:06.570> much 00:24:06.860 --> 00:24:06.870 align:start position:0% state is just one so thank you very much 00:24:06.870 --> 00:24:08.840 align:start position:0% state is just one so thank you very much if<00:24:07.110> I<00:24:07.200> have<00:24:07.380> any<00:24:07.530> questions<00:24:08.040> and<00:24:08.310> rant<00:24:08.490> over<00:24:08.640> a 00:24:08.840 --> 00:24:08.850 align:start position:0% if I have any questions and rant over a 00:24:08.850 --> 00:24:10.610 align:start position:0% if I have any questions and rant over a little<00:24:09.090> bit<00:24:09.300> but<00:24:09.360> happy<00:24:09.990> to<00:24:10.020> take<00:24:10.290> them<00:24:10.440> in<00:24:10.590> the 00:24:10.610 --> 00:24:10.620 align:start position:0% little bit but happy to take them in the 00:24:10.620 --> 00:24:16.100 align:start position:0% little bit but happy to take them in the hallway 00:24:16.100 --> 00:24:16.110 align:start position:0% 00:24:16.110 --> 00:24:25.020 align:start position:0% [Applause] 00:24:25.020 --> 00:24:25.030 align:start position:0% 00:24:25.030 --> 00:24:27.090 align:start position:0% you