WEBVTT 00:02.380 --> 00:04.900 Thank you , Dr Merritt . Next up , we 00:04.909 --> 00:07.131 have our five eyes panel with featuring 00:07.131 --> 00:09.298 rep featuring representatives from our 00:09.298 --> 00:11.298 partner nations . The panel will be 00:11.298 --> 00:13.187 moderated by Defense Intelligence 00:13.187 --> 00:14.798 Agency , Deputy Director for 00:14.798 --> 00:16.631 Commonwealth Integration , Major 00:16.631 --> 00:19.659 General Dominic Goulet . Please welcome 00:19.670 --> 00:22.510 the board . Sorry , please welcome the 00:22.520 --> 00:23.739 panel to the stage . 00:31.209 --> 00:34.790 Worry of me . Me right today , I saw me 01:05.510 --> 01:09.330 r well , tough crowd , tough 01:09.339 --> 01:13.059 crowd . Um So good 01:13.069 --> 01:14.847 afternoon . It's a pleasure and 01:14.847 --> 01:16.958 privilege uh to be here with you this 01:16.958 --> 01:18.769 afternoon for this week . Uh as 01:18.779 --> 01:20.668 mentioned , Dom Goulet , I am the 01:20.668 --> 01:22.501 Deputy Director for Commonwealth 01:22.501 --> 01:24.723 Integration within Defense Intelligence 01:24.723 --> 01:26.946 Agency . I'm the fourth Deputy Director 01:26.946 --> 01:29.279 for Commonwealth Integration since 2015 . 01:29.279 --> 01:31.390 Um And for those who are not familiar 01:31.390 --> 01:33.557 with the role of the office , it is to 01:33.557 --> 01:36.660 support the director in evolving and 01:36.669 --> 01:38.669 enabling partner integration across 01:38.669 --> 01:40.780 agencies , full spectrum activities . 01:41.589 --> 01:44.419 We've heard this morning and just after 01:44.430 --> 01:47.110 lunch , many references to partners and 01:47.120 --> 01:49.980 allies uh which is absolutely fantastic 01:49.989 --> 01:52.211 to hear . Uh I'm looking forward to the 01:52.211 --> 01:54.378 panel where we will actually hear from 01:54.650 --> 01:56.300 allies in Austin 01:59.629 --> 02:01.830 in terms of how we can best get after 02:01.839 --> 02:03.617 it so that we can fight tonight 02:03.617 --> 02:05.728 interoperable . So we can support the 02:05.728 --> 02:08.339 war fighter and we can defend and win 02:08.350 --> 02:11.679 the next wars decisively . I also like 02:11.688 --> 02:15.078 to echo what Doctor Dixon and General 02:15.089 --> 02:17.488 Henry mentioned this morning in terms 02:17.498 --> 02:19.331 of how do we grow the small e in 02:19.331 --> 02:22.190 enterprise so that we have unfinished 02:22.199 --> 02:23.643 business uh to quote them 02:25.600 --> 02:28.259 credible military power is critical to 02:28.270 --> 02:30.369 shaping adversarial perceptions and 02:30.380 --> 02:32.380 intent and deterring strategic comp 02:32.380 --> 02:35.229 competitors . Our collective military 02:35.240 --> 02:37.410 power achieved through integrated 02:37.419 --> 02:39.610 deterrent with allies and partners 02:40.320 --> 02:42.679 across war fighting domains , theaters 02:42.690 --> 02:45.039 in spectrum of competition allows us to 02:45.050 --> 02:47.789 prevent and if needed decisively win 02:47.800 --> 02:51.029 wars . The Linchpin to integrated 02:51.039 --> 02:53.229 deterrent is information technology 02:54.610 --> 02:56.499 wielding a modernized connected , 02:56.499 --> 02:58.554 secure and resilient it . Enterprise 02:58.554 --> 03:00.539 assures unparalleled overmatch in 03:00.550 --> 03:04.529 competition and conflict . So 03:04.539 --> 03:06.428 how do we achieve and maintain it 03:06.428 --> 03:10.009 superiority ? Dia cio for its part 03:10.199 --> 03:11.550 has prioritized partner 03:11.559 --> 03:13.615 interoperability in its strategy and 03:13.615 --> 03:15.860 supporting initiatives . And I am 03:15.869 --> 03:17.869 pleased to say continues to deliver 03:17.869 --> 03:19.813 critical capability to support our 03:19.813 --> 03:22.539 closest commonwealth allies . A great 03:22.550 --> 03:25.029 example of dia s efforts is the ongoing 03:25.039 --> 03:27.039 development of the machine assisted 03:27.039 --> 03:29.580 analytical rapid repository or Mars 03:29.589 --> 03:32.380 program of record designed to replace 03:32.389 --> 03:34.445 the modernized integrated database . 03:34.445 --> 03:36.445 Mars development has from day one , 03:36.610 --> 03:38.666 been undertaken such a way to enable 03:38.666 --> 03:40.559 partner integration and adopt and 03:40.570 --> 03:43.009 adoption and ultimately continued 03:43.020 --> 03:45.187 interoperability in support to the war 03:45.187 --> 03:47.789 fighter . This will ensure that the US 03:47.800 --> 03:49.960 and its allies continues to best 03:49.970 --> 03:51.692 leverage foundational military 03:51.692 --> 03:53.803 intelligence required at the speed of 03:53.803 --> 03:57.009 mission . And we know why this matters . 03:57.770 --> 03:59.381 DS efforts to prioritize the 03:59.381 --> 04:01.492 modernization of information networks 04:01.492 --> 04:03.603 and computing are critical as we scan 04:03.603 --> 04:05.949 today's security environment , we face 04:05.960 --> 04:08.182 a multitude of threat actors across the 04:08.182 --> 04:10.182 spectrum of competition that pose a 04:10.182 --> 04:12.071 serious threat to the rules based 04:12.071 --> 04:14.899 global order . China is rapidly 04:14.910 --> 04:16.966 advancing its military modernization 04:16.966 --> 04:19.140 and developing capabilities critical 04:19.149 --> 04:20.816 for potential future military 04:21.200 --> 04:24.390 operations against Taiwan Russia . 04:24.399 --> 04:26.621 Despite despite its war of attrition in 04:26.621 --> 04:29.200 Ukraine continues to advance its space 04:29.209 --> 04:31.869 and counter space strategy . Emphasize 04:31.880 --> 04:33.936 its military posture presence in the 04:33.936 --> 04:37.000 Arctic , modernize its nuclear triad 04:37.279 --> 04:39.501 and expand co-operation with partners . 04:40.769 --> 04:43.329 Iran continues to position itself as a 04:43.339 --> 04:45.339 dominant regional power . And North 04:45.339 --> 04:47.100 Korea wields the missiles and 04:47.109 --> 04:49.649 conventional capabilities to hold us 04:49.660 --> 04:52.100 forces and allies in Northeast Asia in 04:52.109 --> 04:55.200 Northeast Asia at risk . All of this 04:55.209 --> 04:57.880 without mentioning terrorism and global 04:58.209 --> 05:01.779 instability as such leaders at all 05:01.790 --> 05:03.846 levels should continuously be asking 05:03.846 --> 05:06.068 themselves key questions with a view of 05:06.068 --> 05:08.290 ensuring a strong integrated deterrence 05:08.290 --> 05:10.568 with allies and partners . For example , 05:10.568 --> 05:12.790 how do we maintain our ability at speed 05:12.790 --> 05:14.457 of mission to fight tonight ? 05:14.457 --> 05:16.512 Successfully deploying and employing 05:16.512 --> 05:18.457 modern connected secured resilient 05:18.457 --> 05:20.568 networks that provide the data needed 05:20.568 --> 05:22.512 to continue to effectively support 05:22.512 --> 05:24.679 decision makers and war fighters . And 05:24.679 --> 05:26.512 how do we continue to enable our 05:26.512 --> 05:28.290 respective cio s with the right 05:28.290 --> 05:30.068 resources policies and critical 05:30.068 --> 05:31.957 enablers necessary to establish , 05:31.957 --> 05:34.068 maintain and safeguard our respective 05:34.068 --> 05:37.440 and collective it superiority . So to 05:37.450 --> 05:39.228 help us get after some of these 05:39.228 --> 05:41.339 questions and to broaden our thinking 05:41.339 --> 05:43.061 on how we can continue to best 05:43.061 --> 05:45.228 integrate with allies and partners . I 05:45.228 --> 05:47.339 am pleased to introduce the following 05:47.339 --> 05:49.339 distinguished panelists . Brigadier 05:49.339 --> 05:51.283 Andrew mcbain serves as a Director 05:51.283 --> 05:53.506 General Intelligence Data and targeting 05:53.506 --> 05:55.839 for the Department of Defense Australia . 05:55.839 --> 05:57.506 In this role , he manages the 05:57.506 --> 05:59.728 Australian Defense targeting enterprise 05:59.728 --> 06:01.617 geospatial capability program and 06:01.617 --> 06:03.672 foundational military intelligence , 06:03.672 --> 06:05.617 delivering intelligence capability 06:05.617 --> 06:05.480 outcomes , defense and whole of 06:05.489 --> 06:08.500 government . Brigadier General , Eric 06:08.510 --> 06:10.510 Vanderberg is a director of General 06:10.510 --> 06:12.454 Intelligence Enterprise within the 06:12.454 --> 06:14.677 Canine Forces Intelligence Command . He 06:14.677 --> 06:16.677 oversees the design development and 06:16.677 --> 06:18.843 implementation of defense intelligence 06:18.843 --> 06:20.899 capabilities within the , the Canine 06:20.899 --> 06:20.660 Department of National Defense and the 06:20.670 --> 06:23.059 Can Arm Forces . And he is responsible 06:23.070 --> 06:25.292 for the oversight , ongoing sustainment 06:25.292 --> 06:27.459 and continuous development of Canada's 06:27.459 --> 06:29.237 top secret defense intelligence 06:29.237 --> 06:31.470 networks . Captain Brennan Brendan 06:31.480 --> 06:33.591 Oakley is the Deputy Chief of Defense 06:33.591 --> 06:35.424 Intelligence for the New Zealand 06:35.424 --> 06:38.220 Defense Force and in a subsidiary role , 06:38.230 --> 06:40.008 he has a responsibility for the 06:40.008 --> 06:42.063 progression of information and cyber 06:42.063 --> 06:44.286 domain capability projects . During his 06:44.286 --> 06:46.174 30 years of service , he has held 06:46.174 --> 06:48.230 senior positions within the Navy and 06:48.230 --> 06:50.063 the Wire Defense Force including 06:50.063 --> 06:51.952 Director of Naval Engineering and 06:51.952 --> 06:51.579 Director of Strategic Joint 06:51.589 --> 06:55.209 Communications . Mr Jack Maxton is the 06:55.220 --> 06:57.053 chief information officer for UK 06:57.053 --> 06:59.164 Defense Intelligence . In this role , 06:59.164 --> 07:01.220 he leads a digital strategy across a 07:01.220 --> 07:03.276 mul a multi intelligence environment 07:03.276 --> 07:05.053 including all source analysis , 07:05.053 --> 07:07.053 geospatial intelligence , cyber and 07:07.053 --> 07:09.350 electromagnetic effects , training and 07:09.359 --> 07:11.026 other specialist intelligence 07:11.026 --> 07:13.070 capability disciplines . He is 07:13.079 --> 07:15.301 responsible for the day to day delivery 07:15.301 --> 07:17.412 of defense intelligence specialist it 07:17.412 --> 07:19.135 services and for delivering an 07:19.135 --> 07:21.246 ambitious program to transform UK D I 07:21.246 --> 07:23.412 through the adoption , adoption of new 07:23.412 --> 07:25.523 cloud advanced analytics technologies 07:25.523 --> 07:28.829 at pace . And finally , Mr Austin 07:28.839 --> 07:30.561 Martin currently serves as the 07:30.561 --> 07:32.561 Assistant Director for Five Eyes It 07:32.561 --> 07:34.283 Integration within Dia S Chief 07:34.283 --> 07:36.450 Information Office . In this role . He 07:36.450 --> 07:38.617 is responsible for advising the cio on 07:38.617 --> 07:40.617 the full spectrum of capability and 07:40.617 --> 07:42.672 services provided by Dia to the Five 07:42.672 --> 07:44.839 Eyes defense and national Intelligence 07:44.839 --> 07:47.061 enterprises . He previously served as a 07:47.061 --> 07:48.672 senior technical advisor for 07:48.672 --> 07:50.839 International Systems along with other 07:50.839 --> 07:53.006 foreign partner relations roles within 07:53.006 --> 07:56.450 Dia S Chief Information Office . Thank 07:56.459 --> 07:58.200 you , gentlemen , welcome . 08:00.920 --> 08:03.519 Mhm . So this year's conference is 08:03.529 --> 08:05.696 centered around it integration and its 08:05.696 --> 08:07.640 role within the realm of strategic 08:07.640 --> 08:09.640 deterrence in a competition space . 08:09.640 --> 08:11.959 Often we think of it uh and the 08:11.970 --> 08:13.914 challenges in terms of integrating 08:13.914 --> 08:16.081 across the five eyes , we think of the 08:16.081 --> 08:18.248 technical impediments , but often what 08:18.248 --> 08:20.303 we find is the policy impediments or 08:20.303 --> 08:22.303 challenges um that we first need to 08:22.303 --> 08:24.303 overcome to get after the technical 08:24.303 --> 08:26.414 solutions . Um So I'd like to hear um 08:26.414 --> 08:28.459 from yourselves in terms of perhaps 08:28.470 --> 08:30.526 some examples of where perhaps we've 08:30.526 --> 08:32.748 gotten the policy right ? Or we , we've 08:32.748 --> 08:34.859 been able to align the policy against 08:34.859 --> 08:36.692 our objectives and we're able to 08:36.692 --> 08:38.526 overcome some of these technical 08:38.526 --> 08:40.692 impediments . Austin . I'll start with 08:40.692 --> 08:43.026 you , please . Sure , thanks , sir . So , 08:43.026 --> 08:45.026 um you know , I think it's inherent 08:45.026 --> 08:46.914 that being a part of a government 08:46.914 --> 08:49.137 organization , there's , there's policy 08:49.137 --> 08:48.890 and , and within Dia specifically we 08:48.900 --> 08:50.844 have , you know , Cio and then dia 08:50.844 --> 08:53.159 department I see . And even um us laws 08:53.169 --> 08:55.280 that are codified in the US code that 08:55.280 --> 08:57.447 give us some left and right boundaries 08:57.447 --> 08:59.502 of where we need to operate . Um You 08:59.502 --> 09:01.613 know , II I think I'd be preaching to 09:01.613 --> 09:03.669 the choir here if um you know , if I 09:03.669 --> 09:05.780 said that uh policy sometimes doesn't 09:05.780 --> 09:08.002 keep pace with the technical innovation 09:08.002 --> 09:09.891 that we have . Um But where we've 09:09.891 --> 09:12.058 really found success is um approaching 09:12.058 --> 09:14.113 a problem outside of the policy . So 09:14.113 --> 09:16.336 approach a problem that we're presented 09:16.336 --> 09:18.336 with for it , integration with uh a 09:18.336 --> 09:20.502 foreign partner or in a , in a foreign 09:20.502 --> 09:22.502 partner space and uh gather all the 09:22.502 --> 09:24.669 relevant stakeholders and come up with 09:24.669 --> 09:26.502 a plan of action that takes into 09:26.502 --> 09:26.409 account all of the relevant laws , 09:26.419 --> 09:29.590 security uh concerns any of the um the 09:29.599 --> 09:31.821 physical or the cyber concerns and then 09:31.821 --> 09:33.932 the actual it hardware and what we're 09:33.932 --> 09:35.543 pulling itself . Uh and then 09:35.543 --> 09:37.543 approaching the policy to see if we 09:37.543 --> 09:39.429 need to change it or if uh if it 09:39.440 --> 09:41.496 doesn't need to be changed or if the 09:41.496 --> 09:43.551 policy doesn't exist , then advising 09:43.551 --> 09:45.607 the appropriate policy makers within 09:45.607 --> 09:47.607 either dia or OD and I or , or your 09:47.607 --> 09:50.080 respective IC uh to uh to either create 09:50.090 --> 09:52.090 the policy vet it and approve it so 09:52.090 --> 09:54.257 that we can move out . Thanks , Austin 09:54.257 --> 09:57.539 Jack , I think the place I would start 09:57.549 --> 09:59.789 is when you consider the , the 09:59.799 --> 10:02.320 standards that these policies drive , 10:02.330 --> 10:04.441 sometimes we just have to apply a bit 10:04.441 --> 10:07.520 of pragmatism and not take , not try 10:07.530 --> 10:10.070 and achieve a common standard or way of 10:10.080 --> 10:12.302 working . But sometimes we just need to 10:12.302 --> 10:14.358 take the highest standards . And you 10:14.358 --> 10:16.413 see that um in many of you will have 10:16.413 --> 10:18.524 been to RF Witton in Cambridgeshire , 10:18.524 --> 10:20.691 which is the largest five eye skiff in 10:20.691 --> 10:22.691 the world . We were able to achieve 10:22.691 --> 10:24.913 that by actually taking the highest and 10:24.913 --> 10:26.913 most stringent policy standards and 10:26.913 --> 10:29.024 those I know it when I get searched , 10:29.024 --> 10:31.136 going in there every morning . Um But 10:31.136 --> 10:33.247 actually , that's an example of where 10:33.247 --> 10:35.413 we've been pragmatically able to bring 10:35.413 --> 10:35.049 that together . And the result was 10:35.219 --> 10:37.750 achieved by the people wanting to make 10:37.760 --> 10:39.969 that happen . And I think that's the 10:39.979 --> 10:42.035 important thing as well . We need to 10:42.035 --> 10:44.146 not let this get in the way , not let 10:44.146 --> 10:46.368 computers know you get in the way of us 10:46.368 --> 10:46.169 being able to do some really good 10:46.179 --> 10:49.369 things together . Thanks Jack Brendan , 10:49.380 --> 10:51.969 uh Kora Tako Kato . Good afternoon . Um 10:51.979 --> 10:54.146 As mentioned , Brendan Oakley from the 10:54.146 --> 10:56.312 New Zealand Defense Force . Uh First , 10:56.312 --> 10:58.535 I'd like to thank you very much for the 10:58.535 --> 10:57.929 invitation . I was very privileged to 10:57.940 --> 11:00.107 attend Dous last year in Portland . Uh 11:00.107 --> 11:02.107 Looking forward to it here in Omaha 11:02.107 --> 11:04.051 over the next couple of days uh to 11:04.051 --> 11:06.051 answer the question . Uh policy and 11:06.051 --> 11:08.273 technology go hand in hand for enabling 11:08.273 --> 11:11.320 it integration . I see policy is a 11:11.330 --> 11:13.890 great way of uh ensuring we're 11:13.900 --> 11:15.956 delivering the right outcomes uh for 11:15.956 --> 11:18.233 our people . Uh what do I mean by that , 11:18.299 --> 11:21.140 uh the ability to provide , uh I 11:21.289 --> 11:23.869 suppose , systems that are by design , 11:24.020 --> 11:27.359 secure and drop and scalable , but also 11:27.369 --> 11:29.702 to those resources that we're investing , 11:29.702 --> 11:31.758 we know we're going to get the right 11:31.758 --> 11:31.479 outcome , which is , which is 11:31.489 --> 11:33.630 absolutely vital to our war fighters 11:34.840 --> 11:36.951 for a small nation like New Zealand , 11:36.951 --> 11:38.840 it's absolutely vital uh that our 11:38.840 --> 11:40.784 policy is aligned organizationally 11:40.784 --> 11:43.150 nationally and with alliances such as 11:43.159 --> 11:46.700 five eyes to ensure we are opp and able 11:46.710 --> 11:49.320 to integrate our it and our systems to 11:49.330 --> 11:52.159 get that information seamlessly uh to 11:52.169 --> 11:54.239 our people . I was mentioned earlier 11:54.250 --> 11:57.190 today by the general with uh a policy 11:57.200 --> 11:59.729 or a , a framework that's been adopted 11:59.739 --> 12:01.795 by partners and that's that the NATO 12:01.795 --> 12:04.090 Federated Mission network or FMN as , 12:04.099 --> 12:06.155 as as it's called and the success of 12:06.155 --> 12:08.969 that uh helping drive ahead uh drop 12:09.599 --> 12:11.655 with our partners . And there's some 12:11.655 --> 12:13.543 great examples given earlier this 12:13.543 --> 12:15.710 morning , noting technology is rapidly 12:15.710 --> 12:18.039 advancing . Uh our policies need to 12:18.049 --> 12:19.993 keep up as well . And I think it's 12:19.993 --> 12:22.409 recognized that having adequate policy 12:22.419 --> 12:24.570 enables it integration and therefore 12:24.580 --> 12:27.859 interoperability . Uh If we get this 12:27.869 --> 12:30.289 right , uh the policy , right , which 12:30.299 --> 12:32.530 enables the technology . Uh we vastly 12:32.539 --> 12:35.030 improve our collective capability and 12:35.039 --> 12:37.150 therefore it's a force multiplier so 12:37.159 --> 12:39.460 policy can never be forgotten . Uh And 12:39.469 --> 12:40.969 we need to aid it with our 12:40.969 --> 12:43.510 technological advancement . Thank you , 12:43.520 --> 12:47.190 Brent Eric . Um Thank you , sir . So 12:47.200 --> 12:49.200 Brigadier General Eric Vanderberg , 12:49.200 --> 12:51.422 great to be back at do this is my third 12:51.422 --> 12:53.422 do . Um And you know , I've seen it 12:53.422 --> 12:55.422 sort of gets better and better . Uh 12:55.422 --> 12:57.256 every year , the uh the level of 12:57.256 --> 12:59.489 discussion , um the moderators , our 12:59.500 --> 13:02.200 moderator is amazing . Um 13:04.130 --> 13:06.919 You paid me for that . Uh I just uh not 13:07.130 --> 13:09.489 picking up on what Brendan said . I 13:09.500 --> 13:11.799 think if we think about policy and we 13:11.809 --> 13:15.559 think about um technology , there is a , 13:15.570 --> 13:18.469 a natural friction there . Um And I 13:18.479 --> 13:20.646 think we generally default to the fact 13:20.646 --> 13:23.075 that we think that policy inhibits um 13:23.085 --> 13:25.029 our technological advances . But I 13:25.029 --> 13:27.141 think we can flip it around as well . 13:27.141 --> 13:29.363 There's a lot of legacy systems that we 13:29.363 --> 13:31.307 have that actually prevent us from 13:31.307 --> 13:33.474 having the policy that we need . Um So 13:33.474 --> 13:36.945 it is very much a balancing act of um 13:36.955 --> 13:39.705 where do we put policy in place ? And 13:39.715 --> 13:42.169 at what time ? And I think if we think 13:42.179 --> 13:44.346 about uh the work that we've done with 13:44.346 --> 13:48.169 Mars , it's really forced us um to 13:48.179 --> 13:51.489 acknowledge the fact that policy is not 13:51.630 --> 13:53.686 an afterthought . OK ? We've come up 13:53.686 --> 13:55.797 with a great technological solution . 13:55.797 --> 13:57.963 Now , let's figure out how we make the 13:57.963 --> 14:00.019 policy work . Um They have to work , 14:00.019 --> 14:02.241 you know , side by side as we're making 14:02.241 --> 14:04.408 advances in technology , we have to be 14:04.408 --> 14:06.519 developing the policy at that point . 14:06.519 --> 14:08.741 Um And I think as we look to the future 14:08.849 --> 14:11.000 um when we get to that zero trust 14:11.010 --> 14:13.640 environment , um and we have , you know , 14:13.799 --> 14:17.059 a and A B A in place it's really gonna 14:17.070 --> 14:20.739 allow sort of the policy um to step out 14:20.750 --> 14:22.789 uh working in that environment to 14:22.799 --> 14:24.688 really give us what we need to be 14:24.688 --> 14:27.150 interoperable . Um So I think that uh 14:27.320 --> 14:29.431 it's really , I think it's there is a 14:29.431 --> 14:31.598 friction , there is a natural friction 14:31.598 --> 14:33.376 which is ne generally seen as a 14:33.376 --> 14:35.487 negative thing . But really , I think 14:35.487 --> 14:37.264 we can flip that around , it is 14:37.264 --> 14:39.487 positive in the sense that , you know , 14:39.487 --> 14:41.709 technology forces policy to keep up and 14:41.709 --> 14:43.931 we will soon be in a place where policy 14:43.931 --> 14:46.098 is gonna force technology to keep up . 14:46.098 --> 14:48.153 Thank you . Hey sir , thanks for the 14:48.153 --> 14:50.320 question . And I might riff off Eric's 14:50.320 --> 14:53.450 point just here about policy driving um 14:53.460 --> 14:56.989 technology and and integration . So um 14:57.000 --> 14:59.409 I'll start with a macro position . The 14:59.419 --> 15:01.141 Australian government recently 15:01.141 --> 15:03.363 announced its national defense strategy 15:03.363 --> 15:05.308 front and center of that . Our pre 15:05.308 --> 15:06.975 eminent strategic priority is 15:06.975 --> 15:09.141 deterrence and a and a subtext of that 15:09.141 --> 15:11.141 is integration . So it's consistent 15:11.141 --> 15:13.308 with the theme of this conference . Um 15:13.308 --> 15:15.141 that's both an imprimatur and an 15:15.141 --> 15:17.440 impetus for us to build partnerships 15:17.450 --> 15:19.640 that are interoperable and to be seen 15:19.650 --> 15:21.919 to be interoperable . And so when we 15:21.929 --> 15:23.651 start to consider deterrence , 15:23.651 --> 15:25.596 deterrence can be achieved through 15:25.596 --> 15:27.651 multiple vectors , um development of 15:27.651 --> 15:29.762 credible military forces as we talked 15:29.762 --> 15:31.985 about building visible partnerships and 15:31.985 --> 15:33.707 alliances which by default are 15:33.707 --> 15:36.070 interoperable and also demonstrating a 15:36.080 --> 15:38.080 keen understanding of our operating 15:38.080 --> 15:40.024 environment or the battle space in 15:40.024 --> 15:42.136 which we might fight . And an example 15:42.136 --> 15:44.191 of where we've been able to overcome 15:44.191 --> 15:46.247 some of these , these challenges and 15:46.247 --> 15:48.413 use policy to drive things forward was 15:48.413 --> 15:50.358 with the um an initiative that was 15:50.358 --> 15:50.299 announced by Secretary Austin and our 15:50.309 --> 15:52.700 Deputy Prime Minister last year , which 15:52.710 --> 15:54.710 is the Combined Intelligence Center 15:54.710 --> 15:56.750 Australia , which is a , it's a co 15:56.799 --> 15:58.743 effort by the Defense Intelligence 15:58.743 --> 16:00.743 Agency of the United States and the 16:00.743 --> 16:02.799 Defense Intelligence Organization of 16:02.799 --> 16:04.929 Australia , where it's a , a joint 16:04.940 --> 16:08.039 facility in Canberra , working to 16:08.559 --> 16:11.229 croce rich insights into our operating 16:11.239 --> 16:13.859 environment . Um So we can understand 16:13.869 --> 16:16.090 but also be seen to be building that 16:16.099 --> 16:18.979 partnership now implicit in that um 16:18.989 --> 16:21.100 achievement of that high level policy 16:21.100 --> 16:23.322 goal from both of our countries was the 16:23.322 --> 16:26.210 need to overcome a series of policy um 16:26.280 --> 16:28.390 challenges that at a more sort of 16:28.400 --> 16:31.940 organizational level which we were able 16:31.950 --> 16:33.950 to overcome because of a clear eyed 16:33.950 --> 16:36.099 focus on the mission , the desired 16:36.109 --> 16:38.700 outcome . Um and a willingness of , of 16:38.710 --> 16:40.654 high level stakeholders across our 16:40.654 --> 16:42.766 organization to really buy in to what 16:42.766 --> 16:44.932 we were doing . And I'm pleased to say 16:44.932 --> 16:46.988 that it's operating now and I'm sure 16:46.988 --> 16:49.266 we'll go from success to success . Hey , 16:49.266 --> 16:51.659 thanks Andy . Um Yeah , I think the , 16:51.669 --> 16:54.669 the policy technical um chicken and egg 16:54.830 --> 16:57.039 um issue if you will uh is one that 16:57.049 --> 16:59.382 we've been tackling for quite some time . 16:59.382 --> 17:01.549 Um And one of the things that we often 17:01.549 --> 17:03.549 refer to back at the agency , and I 17:03.549 --> 17:05.382 know we've discussed this is the 17:05.382 --> 17:07.438 mindset , the culture if we get that 17:07.438 --> 17:09.660 right , the technical and policy , what 17:09.660 --> 17:11.827 we perceive as impediments , we can at 17:11.827 --> 17:14.160 least align ourselves to get after them . 17:14.160 --> 17:16.105 Um And I think that is the driving 17:16.105 --> 17:18.216 force . I think your , your reference 17:18.216 --> 17:20.327 to the KA , as we say in Australia or 17:20.327 --> 17:22.382 the kick a in the US and in Canada , 17:22.382 --> 17:26.109 it's the kick a a um it just 17:26.119 --> 17:29.300 is um I think those are great examples 17:29.369 --> 17:31.536 um as well as the Jack , you mentioned 17:31.540 --> 17:33.849 the witten as the largest five eyes uh 17:33.859 --> 17:36.319 skiff . I think of Sr Joe and I think 17:36.329 --> 17:39.160 of those opportunities we've had um 17:39.170 --> 17:41.329 downrange on during coalition 17:41.339 --> 17:43.506 operations where we've been in a skiff 17:43.506 --> 17:45.561 environment where we've been able to 17:45.561 --> 17:47.672 quickly get after those technical and 17:47.672 --> 17:50.099 policy uh challenges because we knew we 17:50.109 --> 17:52.439 had to , it was um at risk of mission , 17:52.449 --> 17:54.839 so great , uh great uh great discussion , 17:54.849 --> 17:57.016 gentlemen , uh to kick off our panel , 17:57.959 --> 17:59.859 the world of it , Five eyes , it 17:59.869 --> 18:01.925 integration is incredibly complex to 18:01.925 --> 18:03.925 navigate , particularly when viewed 18:03.925 --> 18:06.091 through the lens of having to not only 18:06.091 --> 18:08.147 work through our own unique national 18:08.147 --> 18:10.369 technical and policy environments , but 18:10.369 --> 18:12.313 also having to work alongside four 18:12.313 --> 18:13.980 other equally unique national 18:13.980 --> 18:15.980 environments to achieve a common uh 18:15.980 --> 18:17.980 five eye mission as people who live 18:17.980 --> 18:20.140 this reality on a daily basis . Can 18:20.150 --> 18:22.317 each of you provide some advice to the 18:22.317 --> 18:24.261 IT professionals here and watching 18:24.261 --> 18:26.261 online on how each of them can best 18:26.261 --> 18:28.150 contribute to the mission of it . 18:28.150 --> 18:30.261 Integration , Jack , we'll start with 18:30.261 --> 18:33.569 you . Uh Thank you . Um So I joined the 18:33.579 --> 18:35.635 Ministry of Defence in February this 18:35.635 --> 18:37.690 year . So this is my first ever time 18:37.690 --> 18:40.023 I've been to DOS and indeed to Nebraska . 18:40.023 --> 18:42.023 So thank you very much for the warm 18:42.023 --> 18:45.079 welcome . I was amazed at the 18:45.089 --> 18:48.040 complexity of the landscape that uh 18:48.050 --> 18:50.630 encompasses five eyes . It , I mean , 18:50.640 --> 18:54.000 it really is breathtaking . Um It's far 18:54.010 --> 18:55.954 too much for one person to hold in 18:55.954 --> 18:58.339 their heads at any one time . Um It's 18:58.349 --> 19:00.516 probably far too much for 10 people to 19:00.516 --> 19:02.516 hold in their heads . And so what I 19:02.516 --> 19:04.839 think that means is we need all of , I 19:04.849 --> 19:07.189 need , we need all of your help sitting 19:07.199 --> 19:09.550 in the audience to help us streamline 19:09.560 --> 19:12.030 and simplify that environment . So that 19:12.040 --> 19:14.207 means when we're thinking about making 19:14.207 --> 19:16.290 new investments in products that are 19:16.300 --> 19:18.699 going to support the productivity or 19:18.709 --> 19:20.765 productivity of our analysts or give 19:20.765 --> 19:22.987 them new insights , we need you to help 19:22.987 --> 19:25.098 us make sure those products are based 19:25.098 --> 19:27.209 on open standards that we can share . 19:27.209 --> 19:29.042 They're based on architectures , 19:29.042 --> 19:31.265 reference architectures , like the ones 19:31.265 --> 19:33.320 that Dr Merritt spoke about just now 19:33.320 --> 19:35.431 and we need your help to , to join up 19:35.431 --> 19:37.487 for us . You know , we're not in the 19:37.487 --> 19:39.653 world anymore . I don't think of being 19:39.653 --> 19:42.453 able to buy exquisite whole stacks of 19:43.745 --> 19:46.416 from industry , but that means we also 19:46.426 --> 19:48.956 need to come and talk to you more . If 19:48.965 --> 19:51.076 I was saying this in the UK , I would 19:51.076 --> 19:53.076 say that we need to come out of the 19:53.076 --> 19:55.696 shadows from defense intelligence and 19:55.786 --> 19:58.725 talk to industry more and be clear 19:58.735 --> 20:00.846 about our challenge , challenges with 20:00.846 --> 20:02.855 you and be clear about how you can 20:03.189 --> 20:05.599 support us in uh in joining them up . 20:05.609 --> 20:07.776 So if anyone's sitting in the audience 20:07.776 --> 20:09.776 thinking , gosh , I've got just the 20:09.776 --> 20:11.665 idea for that , please , please , 20:11.665 --> 20:13.776 please do come and talk to me because 20:13.776 --> 20:15.887 I'm sure me and the rest of the panel 20:15.887 --> 20:15.780 will be delighted to hear the the ideas 20:15.790 --> 20:18.030 for that . Ok , thanks Jack Brendan . 20:18.359 --> 20:20.581 Thank you , sir . Uh As mentioned , the 20:20.581 --> 20:22.470 previous question was that common 20:22.470 --> 20:24.640 frameworks helps to create some 20:24.650 --> 20:26.872 consistency . And I think that's what's 20:26.872 --> 20:28.983 required that consistency and it will 20:28.983 --> 20:30.928 unravel some of the complexity and 20:30.928 --> 20:33.094 hopefully reduce uniqueness across our 20:33.094 --> 20:35.339 nations . Uh Hopefully , we we are 20:35.349 --> 20:37.405 starting to see some of that clarity 20:37.405 --> 20:39.810 across the five eyes and maybe it's 20:39.819 --> 20:42.041 hopefully helping you to understand our 20:42.041 --> 20:44.041 objectives for the interoperability 20:44.041 --> 20:46.152 integration and essentially our North 20:46.152 --> 20:48.729 Star with regards to advice to the IT 20:48.739 --> 20:51.189 professionals . Uh Firstly , a huge 20:51.199 --> 20:53.479 thank you for what you do . Uh You 20:53.489 --> 20:56.160 enable our militaries to be a drop ball 20:56.170 --> 20:58.003 and perform and be successful in 20:58.003 --> 21:00.170 operation . So the first thing is , is 21:00.170 --> 21:03.180 thank you . Uh Thinking of advice was 21:03.189 --> 21:06.109 really to look at promote , help us 21:06.119 --> 21:08.989 understand uh your value proposition , 21:09.000 --> 21:11.278 help us understand the value you bring , 21:11.589 --> 21:13.756 concentrate what you are , what you're 21:13.756 --> 21:15.756 good at . Uh to do that . You might 21:15.756 --> 21:17.867 have to understand the ecosystem that 21:17.867 --> 21:19.978 you're the full ecosystem that you're 21:19.978 --> 21:22.200 operating in . I would encourage you to 21:22.200 --> 21:24.311 explore and leverage off others to go 21:24.311 --> 21:26.819 further and faster . Uh Be curious how 21:26.829 --> 21:28.996 others work as well . There's a lot to 21:28.996 --> 21:31.109 be learned from each other being 21:31.119 --> 21:33.286 discussed heavily this morning . Never 21:33.286 --> 21:35.119 lose sight of relationships . Uh 21:35.119 --> 21:37.341 Relationships are so important and with 21:37.341 --> 21:39.619 industry , it's a trusted relationship . 21:40.810 --> 21:42.754 The why has been mentioned several 21:42.754 --> 21:44.532 times this morning as well ? Uh 21:44.532 --> 21:46.532 Understanding the big picture , the 21:46.532 --> 21:48.810 objective I I mentioned the North Star , 21:48.810 --> 21:50.921 what are we trying to achieve ? Uh so 21:50.921 --> 21:53.088 understand those customer requirements 21:53.088 --> 21:55.143 and the in the in outcome required , 21:55.239 --> 21:57.350 I'm probably hammering it pretty hard 21:57.350 --> 21:59.572 today , but build it solutions based on 21:59.572 --> 22:01.350 common standards to ensure that 22:01.350 --> 22:04.449 integration and probability . Now 22:04.459 --> 22:06.681 there's probably a piece I was thinking 22:06.681 --> 22:08.403 it's probably putting a bit of 22:08.403 --> 22:10.515 attention to the traditional business 22:10.515 --> 22:12.403 model . Uh And it's enabling data 22:12.403 --> 22:14.292 portability across systems across 22:14.292 --> 22:16.126 networks , across applications , 22:16.126 --> 22:18.760 working closer with competitors uh for 22:18.770 --> 22:21.260 that sort of military capability to get 22:21.270 --> 22:23.381 that mission success . We're gonna be 22:23.381 --> 22:25.603 working with a number of suppliers , uh 22:25.603 --> 22:27.603 a number of industries to assist us 22:27.603 --> 22:29.826 with that , the more we understand each 22:29.826 --> 22:29.709 other and can work together , we can 22:29.719 --> 22:31.941 get , get much better as a collective . 22:33.489 --> 22:35.600 Now , I I couldn't help myself when I 22:35.600 --> 22:37.589 made some notes , giving you some 22:37.599 --> 22:39.655 advice , but I think it's also too , 22:39.655 --> 22:41.821 how do we such as the five eyes assist 22:41.821 --> 22:44.910 you and with the need to 22:44.920 --> 22:47.219 reproduce release 22:48.329 --> 22:50.880 technology solutions and a rapidly 22:50.890 --> 22:52.939 evolving environment , we need to 22:52.949 --> 22:55.709 remove barriers uh in a time when 22:55.719 --> 22:58.709 resource uh and finance is is 22:58.719 --> 23:00.941 constrained , we need to make things go 23:00.941 --> 23:03.609 faster , go quicker . And I know it was 23:03.619 --> 23:05.786 discussed , it was discussed last year 23:05.786 --> 23:07.675 at Portland . I got approached by 23:07.675 --> 23:09.841 several people saying I'd love to hear 23:09.841 --> 23:11.897 it mentioned with regards to some of 23:11.897 --> 23:13.675 the antiquated processes uh and 23:13.675 --> 23:15.897 techniques that the militaries may have 23:15.897 --> 23:18.063 if they can get from a point from step 23:18.063 --> 23:20.008 one to step 10 and using two steps 23:20.008 --> 23:21.952 instead of going through the whole 23:21.952 --> 23:23.952 process , and it's still using best 23:23.952 --> 23:25.841 practice and transparent , we can 23:25.841 --> 23:28.008 produce a better product faster and it 23:28.008 --> 23:30.008 gets to a war fighter faster , that 23:30.008 --> 23:32.119 gives them that sort of information , 23:32.119 --> 23:31.959 that sort of decision making edge . So 23:31.969 --> 23:34.119 I think the things we can do as well 23:35.020 --> 23:38.189 lastly , uh and being a military 23:38.199 --> 23:40.890 professional myself , often we of we 23:40.900 --> 23:43.410 seek 100% solutions the whole time when 23:43.420 --> 23:45.750 an 80% solution would be adequate . And 23:45.760 --> 23:47.927 again , putting the war fighter at the 23:47.927 --> 23:50.093 center of that adequate solution , get 23:50.093 --> 23:52.093 them at a quicker time to give that 23:52.093 --> 23:53.760 decision advantage to be more 23:53.760 --> 23:56.093 successful operations . We must do that . 23:56.093 --> 23:58.093 Thank you . Thanks , Brandon Eric . 23:58.093 --> 24:00.770 Thank you . Um Yeah , so I agree with 24:00.780 --> 24:03.790 what Jack and uh Brendan has have said . 24:04.040 --> 24:07.170 Um So if I was to still it down maybe 24:07.180 --> 24:09.530 to two points , um I would say the 24:09.540 --> 24:12.489 first one is focus on adaptability . 24:13.229 --> 24:16.530 So we live and we operate in very , in 24:16.540 --> 24:18.890 a very dynamic uh operating environment . 24:19.069 --> 24:21.589 Things are always changing . Um We seem 24:21.599 --> 24:24.869 to be pivoting quite a lot . Um We need 24:24.880 --> 24:27.439 to find solutions quickly . Um And so I 24:27.449 --> 24:29.660 guess the first piece would be be 24:29.670 --> 24:32.790 adaptable . Um Don't be wed to the work 24:32.800 --> 24:35.022 you're doing . Um because we might have 24:35.022 --> 24:37.022 to ask you to , you know , to shift 24:37.022 --> 24:38.911 focus , you know , on a moment to 24:38.911 --> 24:38.780 something different that has a higher 24:38.790 --> 24:41.410 priority . So first one adaptability 24:41.420 --> 24:44.359 and then the second one um would be 24:44.369 --> 24:46.319 prioritized collaboration and 24:46.329 --> 24:48.459 communication , especially when we 24:48.469 --> 24:50.413 start thinking about the Five Eyes 24:50.413 --> 24:54.160 community . Um It's vital um that 24:54.180 --> 24:57.380 we are able to communicate . Um So just 24:57.390 --> 24:59.390 a second ago , Major General Goulet 24:59.390 --> 25:01.557 made a joke about three different ways 25:01.557 --> 25:03.619 to say ka um but there are different 25:03.630 --> 25:05.852 ways that we say things within the Five 25:05.852 --> 25:07.908 Ice . Um Lieutenant Lieutenant , for 25:07.908 --> 25:10.589 example , we come from different 25:10.900 --> 25:12.733 backgrounds . We've gone through 25:12.733 --> 25:14.567 different education , we work in 25:14.567 --> 25:16.400 different environments . We have 25:16.400 --> 25:18.869 different policies . So getting or 25:18.880 --> 25:21.000 taking the opportunity to talk with 25:21.010 --> 25:23.229 your colleagues in the various nations 25:23.239 --> 25:25.572 to understand where they're coming from , 25:25.572 --> 25:28.209 making sure that , you know , when you 25:28.219 --> 25:30.441 say something that they understand what 25:30.441 --> 25:34.099 you've meant . Um So putting a slight 25:34.109 --> 25:36.109 twist on an old adage , we are five 25:36.119 --> 25:38.589 nations separated by a common language . 25:38.770 --> 25:41.270 Um Just keep that in mind . I know as 25:41.280 --> 25:43.113 you're working as you're driving 25:43.113 --> 25:45.169 towards interoperability in the five 25:45.169 --> 25:47.619 eyes and I guess maybe I'd add a third 25:47.750 --> 25:51.699 and the third would be patience . Um So 25:51.709 --> 25:54.900 have patience with , with us , the uh 25:54.910 --> 25:57.339 senior leadership as we sort of try to 25:57.349 --> 26:01.339 translate um government direction into 26:01.349 --> 26:04.089 military and defense priorities . Um 26:04.099 --> 26:06.155 and have patience with the fact that 26:06.155 --> 26:08.321 there are policy impediments . As we , 26:08.321 --> 26:10.321 we've just talked about , there are 26:10.321 --> 26:12.377 things that are gonna , gonna get in 26:12.377 --> 26:14.655 our way . Um But at the end of the day , 26:14.655 --> 26:16.543 with stronger policy uh with your 26:16.543 --> 26:18.655 patience , your adaptability and your 26:18.655 --> 26:20.710 communication skills , you know , we 26:20.710 --> 26:22.988 will get to mission success at the end . 26:22.988 --> 26:25.155 So , thank you very much . Thank you , 26:25.155 --> 26:28.089 Eric and Andy , sir . Thank you . Um 26:28.739 --> 26:30.900 So I guess the first thing I would 26:30.910 --> 26:34.329 offer is that conferences like this are 26:34.439 --> 26:36.829 powerful in focusing our attention on 26:36.839 --> 26:39.339 the mission , but very often in the day 26:39.349 --> 26:41.571 to day hustle and bustle of what we are 26:41.571 --> 26:43.405 doing , we can lose sight of the 26:43.405 --> 26:45.571 mission as we focus inwards on what we 26:45.571 --> 26:44.689 are trying to do in our individual 26:44.699 --> 26:47.520 projects or , or initiatives . And I 26:47.530 --> 26:50.989 would offer that um keeping our mind's 26:51.000 --> 26:54.420 eye on the mission um of it supporting 26:54.430 --> 26:56.208 the war fighter , enabling that 26:56.208 --> 26:58.263 decision making needs to be front of 26:58.263 --> 27:00.374 mind at all times . Um And , and then 27:00.374 --> 27:02.319 focusing on how to get to yes , as 27:02.319 --> 27:04.430 quickly as we can to build up on , on 27:04.430 --> 27:06.750 Eric's Point . Um Integration has been 27:06.760 --> 27:08.927 a theme and the word trust has come up 27:08.927 --> 27:10.927 a couple of times , trust is key to 27:10.927 --> 27:12.816 integration , but key to trust is 27:12.816 --> 27:15.920 understanding . And I think we in 27:15.930 --> 27:18.380 government um and industry partners 27:18.390 --> 27:20.223 need to get better at explaining 27:20.223 --> 27:21.946 requirements to each other and 27:21.946 --> 27:23.946 explaining really complex technical 27:23.946 --> 27:26.001 things to senior decision makers who 27:26.001 --> 27:28.112 may have strong policy backgrounds or 27:28.112 --> 27:30.001 operational backgrounds and don't 27:30.001 --> 27:31.723 understand the benefits of the 27:31.723 --> 27:34.057 technology that you're bringing to bear . 27:34.057 --> 27:36.057 And so helping them understand what 27:36.057 --> 27:35.890 that is . So they can go through the 27:35.900 --> 27:38.060 risk reward calculus is a really 27:38.069 --> 27:40.236 critical skill . And I think something 27:40.236 --> 27:42.402 we need to strive to do um continually 27:42.402 --> 27:46.189 better at um policy has come up a 27:46.199 --> 27:48.530 couple of times today . And I , I was 27:48.540 --> 27:50.762 thinking um as I was listening to the , 27:50.762 --> 27:52.929 the really interesting presentation by 27:52.929 --> 27:54.929 um Mr Ker actually about the potted 27:54.929 --> 27:56.929 history of innovation here in Omaha 27:56.929 --> 28:00.760 that um most innovation or 28:00.770 --> 28:04.079 most truly disruptive technologies . Um 28:04.849 --> 28:06.793 Well , there are actually very few 28:06.793 --> 28:08.460 disruptive , truly disruptive 28:08.460 --> 28:10.405 technologies . Most disruption and 28:10.405 --> 28:12.627 innovation happens when people find new 28:12.627 --> 28:15.660 ways to use existing technologies , but 28:15.670 --> 28:17.837 those existing technologies often have 28:17.837 --> 28:19.892 policies written for them that don't 28:19.892 --> 28:22.059 keep pace with that innovation . So we 28:22.059 --> 28:24.226 don't approach it with , with the same 28:24.226 --> 28:26.337 mindset . What does that mean for all 28:26.337 --> 28:28.448 of you though ? I would encourage you 28:28.448 --> 28:30.614 if you come up against policy barriers 28:30.614 --> 28:33.140 um that you don't just stop there if 28:33.150 --> 28:36.150 you see a really powerful technology or 28:36.160 --> 28:38.209 an innovation challenge the policy 28:38.219 --> 28:40.441 settings because they may not have kept 28:40.441 --> 28:42.386 pace and to go to my comment about 28:42.386 --> 28:44.330 being able to explain things in an 28:44.330 --> 28:46.441 understandable manner , make sure you 28:46.441 --> 28:48.441 push that up . I've seen changes in 28:48.441 --> 28:50.663 policy settings in the five eyes in the 28:50.663 --> 28:50.140 last two years . That would have been 28:50.150 --> 28:53.089 unthinkable um two years ago , because 28:53.099 --> 28:55.321 the right people with the right ability 28:55.321 --> 28:57.321 to influence and understanding what 28:57.321 --> 28:59.432 that audience , their target audience 28:59.432 --> 28:59.329 needs to pick up on a point of an 28:59.339 --> 29:01.450 earlier presenter we're able to do is 29:01.450 --> 29:03.790 get policy settings changed and let 29:03.800 --> 29:06.022 those technologies flourish . Now , I'm 29:06.022 --> 29:08.078 not trying to , to make light of how 29:08.078 --> 29:10.078 difficult that is . But I would say 29:10.078 --> 29:12.133 that's a , that's a really important 29:12.133 --> 29:14.189 thing . So don't self limit based on 29:14.189 --> 29:16.189 current policy settings or what you 29:16.189 --> 29:18.133 think those policy settings are be 29:18.133 --> 29:20.244 willing to challenge it . Um And then 29:20.244 --> 29:19.949 the final thing , I would just offer to 29:19.959 --> 29:22.237 take up on Eric's point about patients . 29:22.709 --> 29:24.653 Um It's , it's a critical , it's a 29:24.653 --> 29:26.820 critical juggling act balancing time . 29:26.969 --> 29:29.191 Um There's an impetus to go forward and 29:29.191 --> 29:30.969 we've heard about our strategic 29:30.969 --> 29:32.858 circumstances . We've heard about 29:32.858 --> 29:34.913 patients pushing forward too quickly 29:34.913 --> 29:36.802 with new technologies that people 29:36.802 --> 29:38.580 aren't ready for can just be as 29:38.580 --> 29:40.802 deleterious as not actually challenging 29:40.802 --> 29:43.080 the status quo in the first place . So , 29:43.080 --> 29:45.247 um I've , I'm , I apologize , I forget 29:45.247 --> 29:47.136 who made the comment before about 29:47.136 --> 29:49.469 understanding target audiences . Um But , 29:49.469 --> 29:51.469 but I would foot stomp that point , 29:51.469 --> 29:53.636 understand the people you're trying to 29:53.636 --> 29:55.802 influence , understand what matters to 29:55.802 --> 29:55.680 them and then put it in a way that they 29:55.689 --> 29:57.800 can understand . So their risk reward 29:57.800 --> 29:59.880 calculus um is an easy one to make . 30:00.930 --> 30:03.208 Thank you , Andy Austin . Thanks , sir . 30:03.208 --> 30:05.152 So , um benefit of going last is I 30:05.152 --> 30:07.041 could get out easy because I uh I 30:07.041 --> 30:09.208 checked my notes and uh everybody made 30:09.208 --> 30:11.489 my points for me . But um I , I won't 30:11.500 --> 30:13.722 do that . I'll , I'll take this uh uh a 30:13.722 --> 30:15.722 slightly different direction . So , 30:15.722 --> 30:17.722 yeah , II , I wanted to Gene Eric's 30:17.722 --> 30:17.260 point because it was , it was one of 30:17.270 --> 30:19.548 the points I was gonna make , you know , 30:19.548 --> 30:21.326 the , I , I've , I've been very 30:21.326 --> 30:23.492 fortunate to spend a significant which 30:23.492 --> 30:25.659 in fact , the majority of my career uh 30:25.659 --> 30:27.714 working within the Five Eyes Defense 30:27.714 --> 30:30.109 Alliance . And uh one thing that you 30:30.119 --> 30:32.910 quickly come to learn is that we're all 30:32.920 --> 30:35.142 from English speaking nations . But the 30:35.142 --> 30:37.364 more you be around and , and , and work 30:37.364 --> 30:39.531 within the , the five eyes construct , 30:39.531 --> 30:41.729 the more you see the air quotes come 30:41.739 --> 30:44.030 around that English because of the 30:44.040 --> 30:46.550 different slang and , and , and , and 30:46.560 --> 30:49.369 uh idioms and everything . Um , but I 30:49.380 --> 30:52.630 would say that , uh my , my advice to , 30:53.089 --> 30:55.790 uh to the folks here about what they 30:55.800 --> 30:58.150 can do is , is , is approach with noble 30:58.160 --> 31:00.890 intent . So what , what , what I've 31:00.900 --> 31:03.369 seen in , in , in my time quite often 31:03.380 --> 31:07.089 is that , um , you know , people 31:07.180 --> 31:09.489 will approach a problem and stop at the 31:09.500 --> 31:12.500 first . No . Um , and , and a lot of 31:12.510 --> 31:15.780 the times what people might not realize 31:15.790 --> 31:19.140 is that yes , they said no , but it's 31:19.150 --> 31:21.317 because of this policy or it's because 31:21.317 --> 31:23.428 of this organizational thing . And so 31:23.428 --> 31:25.483 to Andy , to your point , you know , 31:25.483 --> 31:27.706 knowing who you're talking to , knowing 31:27.706 --> 31:29.928 what your target audience is and how to 31:29.928 --> 31:31.872 influence that . Um you know , not 31:31.872 --> 31:33.983 necessarily , not accepting no for an 31:33.983 --> 31:33.939 answer , but just approaching and 31:33.949 --> 31:36.005 trying to understand the problem and 31:36.005 --> 31:38.338 understand where somebody's coming from . 31:38.338 --> 31:40.560 Um Far too often . I think we've left , 31:40.560 --> 31:42.727 uh you know , we've left some problems 31:42.727 --> 31:44.949 on the cutting room floor uh because we 31:44.949 --> 31:44.339 think that it's an insurmountable 31:44.349 --> 31:46.460 problem when in fact , we just didn't 31:46.460 --> 31:48.793 have the right stakeholders in the room . 31:48.793 --> 31:48.680 And then the moment we got the right 31:48.689 --> 31:50.856 stakeholders in the room , it was just 31:50.856 --> 31:53.078 like a domino effect . And , you know , 31:53.078 --> 31:55.189 34 months later , we've achieved this 31:55.189 --> 31:57.189 massive success that we didn't even 31:57.189 --> 31:59.356 know was possible . So that that would 31:59.356 --> 31:59.140 be , that would be my advice since uh 31:59.469 --> 32:01.469 the rest of my notes were uh thanks 32:01.469 --> 32:03.691 Austin on , I'm not gonna repeat them . 32:03.691 --> 32:05.858 No , thank you gentlemen . Um A couple 32:05.858 --> 32:07.913 of key takeaways for myself . Um You 32:07.913 --> 32:09.969 know , Jack mentioned streamlining , 32:09.969 --> 32:11.913 simplifying it , right ? Um Having 32:11.913 --> 32:13.747 having the professionals help us 32:13.747 --> 32:15.913 understand what it is we are trying to 32:15.913 --> 32:18.247 get at um from a leadership perspective , 32:18.247 --> 32:21.599 trusts um being adaptable because we 32:21.609 --> 32:23.665 understand that techno technology is 32:23.665 --> 32:25.720 evolving at such a rate um trying to 32:25.720 --> 32:27.942 stay focused on one piece of technology 32:27.942 --> 32:30.430 today and not evolve from that uh is a 32:30.439 --> 32:33.099 fool's errand . Um I did like the , the 32:33.109 --> 32:35.165 piece if I can riff off the piece of 32:35.165 --> 32:37.439 the leadership and the patience . Um I 32:37.449 --> 32:39.579 think if you look at the generational 32:39.589 --> 32:42.099 gaps , perhaps , I think the patients 32:42.109 --> 32:45.510 piece as well is having that time to be 32:45.520 --> 32:47.910 able to speak to leadership decision 32:47.920 --> 32:50.087 makers in terms of what is it that you 32:50.087 --> 32:52.309 want to do in terms of achieving effect 32:52.349 --> 32:54.293 and support decision making or war 32:54.293 --> 32:56.405 fighting ? What are you trying to get 32:56.405 --> 32:58.405 after ? Help us better understand , 32:58.405 --> 33:00.349 better , develop that problem , uh 33:00.349 --> 33:02.460 understand the problem space and then 33:02.460 --> 33:04.571 the solution space that uh that comes 33:04.571 --> 33:04.319 with that . Um And I think that's to 33:04.329 --> 33:06.218 echo what general Henry said this 33:06.218 --> 33:08.385 morning about the why and the intent , 33:08.385 --> 33:10.607 right ? Leadership , I think owes it to 33:10.607 --> 33:13.130 um their , their members to explain the 33:13.140 --> 33:15.362 why and the intent so that you can then 33:15.362 --> 33:17.529 circle back with us and help us better 33:17.529 --> 33:19.696 understand what it is we are trying to 33:19.696 --> 33:21.751 frame . Um Especially if you look at 33:21.751 --> 33:24.020 again , technology , not all of us um 33:24.030 --> 33:26.640 are from , you know , this , this ocean , 33:26.650 --> 33:28.706 right ? This this kettle of fish . I 33:28.706 --> 33:30.817 have a humid background , Eddie has a 33:30.817 --> 33:32.983 humid background and there's diversity 33:32.983 --> 33:35.039 here . We don't always have the same 33:35.039 --> 33:37.206 understanding . Um Growing up , we had 33:37.206 --> 33:39.372 one , you know , one phone in the home 33:39.372 --> 33:39.030 plugged to the wall and I was my 33:39.040 --> 33:41.489 father's TV , remote . Um Things have 33:41.500 --> 33:43.849 changed , things have evolved . Um I 33:43.869 --> 33:46.091 think you probably all went through the 33:46.091 --> 33:48.313 same thing . Um And lastly , I like the 33:48.313 --> 33:51.160 focus on mission . And my key takeaway 33:51.170 --> 33:53.114 is that we either speak English or 33:53.114 --> 33:54.726 American . Is that correct ? 33:57.790 --> 34:00.359 I'll be outside after if you perfect . 34:00.709 --> 34:03.180 Um Appreciate that . So to riff off the 34:03.189 --> 34:05.680 leadership piece , um the next question 34:05.689 --> 34:09.689 really is how , you know , to the 34:09.699 --> 34:11.643 extent that you can in this form , 34:11.643 --> 34:13.699 understanding we are at the un class 34:13.699 --> 34:16.169 level . Can we , can you give examples 34:16.179 --> 34:19.929 of when perhaps information technology 34:20.080 --> 34:21.913 has been that critical factor in 34:21.913 --> 34:24.429 deciding mission success or outcome or 34:24.439 --> 34:26.699 where leadership has privileged and 34:26.709 --> 34:29.010 supported , enabled , whether it was 34:29.020 --> 34:32.929 the six function , the cio S the it um 34:33.070 --> 34:36.360 uh you know , peace to ensure mission 34:36.370 --> 34:38.600 success , it's often something that is 34:38.610 --> 34:40.840 perhaps at the leadership level , 34:40.850 --> 34:43.072 perhaps not thought of . It's something 34:43.072 --> 34:45.183 in the background it's running well , 34:45.183 --> 34:47.183 we don't think about it information 34:47.183 --> 34:49.350 technology until it goes sideways . Um 34:49.350 --> 34:51.572 So perhaps an example or two where it's 34:51.572 --> 34:53.739 been brought to the fore . Um And it's 34:53.739 --> 34:55.517 been leveraged um by leadership 34:55.517 --> 34:57.628 properly , Brandon , we'll start with 34:57.628 --> 34:59.628 you . Uh Thank you , sir . Before I 34:59.628 --> 35:01.850 dive into a couple of examples , uh you 35:01.850 --> 35:01.739 mentioned with regards to understanding 35:01.750 --> 35:03.694 what the C OS and it professionals 35:03.694 --> 35:05.694 undertake and I think that's really 35:05.694 --> 35:07.669 important . Uh again , with the it 35:07.679 --> 35:09.959 professionals , the coo s enabling all 35:09.969 --> 35:12.025 five domains across that information 35:12.025 --> 35:14.136 environment again , discussed earlier 35:14.136 --> 35:15.802 this morning . Uh The more we 35:15.802 --> 35:17.969 understand that the more we can change 35:17.969 --> 35:20.080 different ways of working uh and also 35:20.080 --> 35:22.247 be successful in operations . A couple 35:22.247 --> 35:24.302 of examples that I can share uh to a 35:24.302 --> 35:26.413 limited capacity . Uh One was regards 35:26.413 --> 35:28.580 an urgent , urgent need for large data 35:28.580 --> 35:30.747 files to be transferred . There wasn't 35:30.747 --> 35:32.691 the integration wasn't there . And 35:32.691 --> 35:32.679 that's the main reason we're here here 35:32.689 --> 35:34.745 over the next few days for that data 35:34.745 --> 35:37.078 integration between uh multiple nations . 35:37.360 --> 35:39.304 I suppose the example I have was a 35:39.304 --> 35:41.510 ability and permission space for an 35:41.520 --> 35:43.520 innovative solution to be developed 35:43.530 --> 35:45.969 using open source technology training 35:45.979 --> 35:48.389 and tools to enable this integration 35:48.399 --> 35:51.750 piece uh for for large data transfer to 35:51.760 --> 35:53.760 cry . You know , to , I suppose the 35:53.760 --> 35:55.593 necessity for it was time , time 35:55.593 --> 35:57.760 related to exploit that information at 35:57.760 --> 36:00.729 the speed of relevance . Uh It was so 36:00.739 --> 36:02.906 successful that it was later harnessed 36:02.906 --> 36:05.072 uh hard and somewhat and now it's used 36:05.072 --> 36:07.128 by other nations . I I can't provide 36:07.128 --> 36:09.183 any more detail on that but just the 36:09.183 --> 36:11.406 ability to use that open source rapidly 36:11.406 --> 36:13.461 to , to um undertake a problem to be 36:13.461 --> 36:15.572 successful in operations . Another is 36:15.572 --> 36:17.628 the ability to utilize technology at 36:17.628 --> 36:19.739 the edge . It's so important and it's 36:19.739 --> 36:21.906 been mentioned many times by the panel 36:21.906 --> 36:24.017 already today . The war fighter is at 36:24.017 --> 36:26.128 the center uh particularly for search 36:26.128 --> 36:28.183 and rescue operations , an area like 36:28.183 --> 36:30.406 New Zealand which is a large search and 36:30.406 --> 36:32.628 rescue area . Uh The ability to take uh 36:32.628 --> 36:34.850 large amounts of data and turn of vital 36:34.850 --> 36:36.961 information to keep and queue and tip 36:36.961 --> 36:39.183 uh an aircraft or a platform to certain 36:39.183 --> 36:41.419 areas which can be a lifesaver . See 36:41.429 --> 36:45.129 you . Thank you , Brendan Eric . Thank 36:45.139 --> 36:48.340 you , sir . So I was talking with my 36:48.350 --> 36:51.320 Director of uh Intelligence Enterprise 36:51.330 --> 36:54.169 Services about a similar topic uh the 36:54.179 --> 36:57.300 other day and I'm like , where does 36:57.629 --> 37:00.489 like giving the example of technology 37:00.500 --> 37:03.219 and you know , where , um you know , we 37:03.229 --> 37:05.419 can highlight it , it its importance . 37:05.729 --> 37:08.062 And he looked at me and he sort of said , 37:08.780 --> 37:10.891 you wouldn't ask me how to use this . 37:10.891 --> 37:13.058 Like when , when the steering wheel of 37:13.058 --> 37:15.002 your car was really helpful in you 37:15.002 --> 37:17.113 driving to work . So like , don't ask 37:17.113 --> 37:19.336 me when technology sort of , you know , 37:19.336 --> 37:21.391 enabled your missing success because 37:21.391 --> 37:23.613 the answer is always like everything we 37:23.613 --> 37:26.760 do is enabled by technology . Um and 37:26.770 --> 37:29.169 normally , and when it's done properly , 37:29.300 --> 37:32.120 it's transparent to the user , it's 37:32.129 --> 37:34.407 seamlessly operating in the background . 37:34.429 --> 37:37.129 And so like what has enabled mission 37:37.139 --> 37:40.159 success ? Well , it's policies such as 37:40.169 --> 37:43.419 ID M so identity management access . Um 37:43.429 --> 37:45.889 and you know , and , and A E it's these 37:45.899 --> 37:48.969 things in the background that allow us 37:48.979 --> 37:51.850 to do the work that we do . So if we 37:51.860 --> 37:53.689 think about PK I , so identity 37:53.699 --> 37:56.239 management . Um so as a policy , it was 37:56.250 --> 37:58.528 originally set up so that we could , I , 37:59.459 --> 38:01.719 we could share digital identities for 38:01.729 --> 38:04.110 access management . Um But it's now 38:04.120 --> 38:06.287 used for so much more because once you 38:06.287 --> 38:08.509 have that technology , it now allows us 38:08.509 --> 38:10.287 to access internal services and 38:10.287 --> 38:12.176 external services . And so in the 38:12.176 --> 38:14.287 background to the average user , they 38:14.287 --> 38:16.398 just know they have to log into their 38:16.398 --> 38:18.620 PK I , they don't , they wouldn't say , 38:18.620 --> 38:18.409 well , that was a great piece of 38:18.419 --> 38:20.600 technology that enabled me to have 38:20.610 --> 38:22.919 mission success . But without it , we 38:22.929 --> 38:24.929 wouldn't have interoperability , we 38:24.929 --> 38:26.929 wouldn't be able to access external 38:26.929 --> 38:29.151 services and therefore we wouldn't have 38:29.151 --> 38:31.207 mission success at the speed that we 38:31.207 --> 38:33.262 need today . So really when we think 38:33.262 --> 38:35.939 about uh that it's really that piece 38:35.949 --> 38:38.840 that I would uh um wanna highlight 38:38.850 --> 38:41.370 because if we think about it , um 38:41.379 --> 38:43.435 without getting into , don't delving 38:43.435 --> 38:45.657 into like really classified examples of 38:45.657 --> 38:48.149 some really exquisite bespoke um tool 38:48.159 --> 38:50.103 or service that was created . It's 38:50.103 --> 38:52.550 really all technology enables mission 38:52.560 --> 38:54.504 success . And so that's where I'll 38:54.504 --> 38:57.409 leave it as I pass over to uh Andy . 38:57.699 --> 38:59.969 Hey , thanks , Eric , thanks , sir . Um 39:00.239 --> 39:02.406 I might take a slightly different tack 39:02.406 --> 39:04.572 on this . Um , a lot of the discussion 39:04.572 --> 39:06.795 today has been about war fighting and I 39:06.795 --> 39:08.906 mentioned just a moment ago and we've 39:08.906 --> 39:10.961 talked about strategic circumstances 39:10.961 --> 39:13.072 and what have you . But , um , one of 39:13.072 --> 39:15.350 the other elements of national defense , 39:15.350 --> 39:17.350 certainly from , from an Australian 39:17.350 --> 39:19.295 standpoint is dealing with natural 39:19.295 --> 39:21.461 disasters . Um , and , and the example 39:21.461 --> 39:23.628 that springs to mind are the bushfires 39:23.628 --> 39:26.550 of 2009 , 2019 , 2020 . And I'm sure 39:26.560 --> 39:28.782 many of you would have seen that on the 39:28.782 --> 39:30.659 news media . Um Certainly living 39:30.669 --> 39:32.613 through it it felt like the entire 39:32.613 --> 39:34.725 country was on fire and Australia was 39:34.725 --> 39:34.360 certainly the hottest country in the 39:34.370 --> 39:36.703 world there for a little bit . Um We're , 39:36.703 --> 39:38.648 we're used to it , but that was an 39:38.648 --> 39:41.110 unprecedented um , a catastrophe , 39:41.120 --> 39:44.580 catastrophe for our nation . Um The 39:44.590 --> 39:46.590 Australian defense force along with 39:46.590 --> 39:48.868 local state , federal first responders , 39:48.868 --> 39:51.034 fire departments and so forth , put in 39:51.034 --> 39:53.146 a mammoth effort to , to fight that , 39:53.146 --> 39:55.540 that um natural disaster . But what 39:55.550 --> 39:58.310 wasn't apparent but was critical was 39:58.320 --> 40:00.431 the work done behind the scenes . But 40:00.431 --> 40:03.919 by defense it and IC um 40:04.070 --> 40:06.540 it professionals and in many regards , 40:06.550 --> 40:08.717 they were the unsung heroes of what we 40:08.717 --> 40:10.828 did there . Um That's not to diminish 40:10.828 --> 40:12.828 the people who are out on the front 40:12.828 --> 40:14.994 lines . But it is to say that that the 40:14.994 --> 40:14.679 it people behind the scenes who 40:14.689 --> 40:17.379 actually built a functioning cop at 40:17.389 --> 40:19.949 short notice and sustained that tying 40:19.959 --> 40:23.370 together data feeds from the IC into uh 40:23.379 --> 40:25.379 those local community agencies they 40:25.379 --> 40:28.530 never normally deal with or vice versa . 40:28.540 --> 40:30.762 Ingesting that information in to make a 40:30.762 --> 40:32.984 rich picture for the most senior levels 40:32.984 --> 40:35.151 of government to make decisions on was 40:35.151 --> 40:37.207 a powerful example of , of it really 40:37.207 --> 40:39.318 slewing onto a problem and getting it 40:39.318 --> 40:41.373 done . And um you know , there was a 40:41.379 --> 40:43.490 whole range of policy settings that , 40:43.490 --> 40:45.435 that challenge but , but even more 40:45.435 --> 40:47.879 fundamentally , local state federal 40:47.889 --> 40:49.667 agencies using a whole suite of 40:49.667 --> 40:52.570 different um it systems , different 40:52.580 --> 40:55.270 ages , different form factors . Um It 40:55.280 --> 40:57.447 was a mammoth effort behind the scenes 40:57.447 --> 40:59.669 and um you know , to , to your point or 40:59.669 --> 41:01.613 your question sir about the um the 41:01.613 --> 41:03.669 behind the scenes , I can't say that 41:03.669 --> 41:05.558 made the definitive edge , but it 41:05.558 --> 41:07.724 certainly made life a lot easier um in 41:07.724 --> 41:09.724 fighting that fire . So , thank you 41:09.724 --> 41:13.489 Andy . So um it's , yeah , I i 41:13.500 --> 41:16.129 it's it's pretty difficult to , to uh 41:16.139 --> 41:18.580 name specifics but going off of what um 41:18.590 --> 41:20.812 what Eric said , you know , if you , if 41:20.812 --> 41:24.610 you look at , um you know , the history 41:24.620 --> 41:26.787 of , of the Five Eyes Alliance all the 41:26.787 --> 41:28.620 way up to today and then looking 41:28.620 --> 41:30.676 forward into the future , technology 41:30.676 --> 41:32.842 really is underpinning everything that 41:32.842 --> 41:35.064 we do . Um The first thing that happens 41:35.064 --> 41:37.120 in a crisis usually is we try to get 41:37.120 --> 41:39.342 communication with our closest partners 41:39.342 --> 41:41.009 and it's usually the agencies 41:41.009 --> 41:43.176 represented here on this stage that we 41:43.176 --> 41:45.453 talk to . Um , you know , it , it , it , 41:45.453 --> 41:47.949 it underpins , it's , it's , it's step 41:47.959 --> 41:50.181 zero , it's not even step one and , and 41:50.181 --> 41:52.515 for the computer scientists in the room , 41:52.515 --> 41:54.403 you'll , you'll like that uh that 41:54.403 --> 41:56.570 reference . But uh you know , I it's , 41:56.570 --> 41:58.626 it's tough to , to , to call out any 41:58.626 --> 42:00.681 specific thing , uh at least from my 42:00.681 --> 42:02.792 experience in , in this forum . But , 42:02.792 --> 42:05.015 but that's , that's my , my input would 42:05.015 --> 42:07.237 be that , you know , it's , it's , it's 42:07.237 --> 42:09.459 the first thing that we do at the start 42:09.459 --> 42:11.626 of a crisis . It's the last thing that 42:11.626 --> 42:13.737 we stop at the end of a crisis and it 42:13.737 --> 42:16.570 is the foundation upon which we build 42:16.580 --> 42:18.419 whatever response or we monitor 42:18.429 --> 42:20.590 whatever situation that occurs 42:20.629 --> 42:22.796 regardless of awareness in the world . 42:23.159 --> 42:25.570 Thanks for asking , Jack . Uh So I'll 42:25.580 --> 42:29.580 offer two little stories for my nine 42:29.590 --> 42:31.899 months in D I . The first one is about 42:31.909 --> 42:35.189 our most red products . So if you look 42:35.199 --> 42:38.229 on Twitter or X and go to at defense HQ 42:38.239 --> 42:40.461 defense with AC , we spell it with AC , 42:40.461 --> 42:43.360 not an S um HQ . You'll see um our 42:43.379 --> 42:45.989 daily tweet about the war in Ukraine . 42:46.000 --> 42:50.000 So we publish assessment that's had 42:50.010 --> 42:52.066 over a billion views from the public 42:52.066 --> 42:54.121 every day about the war in Ukraine . 42:54.121 --> 42:56.343 But the Providence chain behind that is 42:56.343 --> 42:58.399 obviously a lot more complicated and 42:58.399 --> 43:00.621 I'm not able to go into that here , but 43:00.621 --> 43:02.566 actually being able to move our it 43:02.566 --> 43:04.760 professionals from thinking about just 43:04.770 --> 43:07.110 this as a classified problem to one 43:07.120 --> 43:09.231 that actually where we need to engage 43:09.231 --> 43:11.379 with the public and across government 43:11.389 --> 43:14.600 has been , has been really in 43:14.610 --> 43:16.610 transformational for us . We've had 43:16.610 --> 43:18.332 questions about what does your 43:18.332 --> 43:20.277 assessment , probability yardstick 43:20.277 --> 43:22.388 actually mean and start to get people 43:22.388 --> 43:24.554 thinking about the work and the impact 43:24.554 --> 43:26.989 that we have . Uh And the second one is 43:27.000 --> 43:29.280 um I'd been , this was over the summer . 43:29.290 --> 43:31.346 I , I sit on the eighth floor in the 43:31.346 --> 43:33.568 Ministry of Defense in Whitehall . So I 43:33.568 --> 43:35.901 was having my cup of tea in the morning . 43:35.901 --> 43:38.123 I was looking out over the river and uh 43:38.123 --> 43:40.540 into my office came a very cross 43:40.629 --> 43:43.340 analyst and she said to me , I want to 43:43.350 --> 43:46.060 complain about the new Intelligence 43:46.070 --> 43:48.237 Exchange app that you implemented last 43:48.237 --> 43:51.889 week . So we put a new system to , to , 43:51.899 --> 43:54.010 to share end product reporting , both 43:54.010 --> 43:56.066 from our five eyes partners and from 43:56.066 --> 43:58.288 the UK Intelligence community . And she 43:58.288 --> 44:00.343 said , I want to complain . I said , 44:00.343 --> 43:59.760 I'm sorry to hear that . What's , 43:59.780 --> 44:01.836 what's happened ? She said I got too 44:01.836 --> 44:03.891 much intelligence over the weekend . 44:03.891 --> 44:06.169 I've got 1000 reports to read and I 44:06.179 --> 44:09.209 don't know what to do . Um And uh I say 44:09.219 --> 44:11.052 that's a bit of a badge of pride 44:11.052 --> 44:12.997 actually , that we've been able to 44:12.997 --> 44:15.219 produce analyst too much intelligence . 44:15.219 --> 44:17.441 Um But actually we've , we've then been 44:17.441 --> 44:19.608 able to take strides to uh allow us to 44:19.608 --> 44:21.775 machine , consume sift and filter that 44:21.775 --> 44:23.997 intelligence . And that's allowed us to 44:23.997 --> 44:26.219 produce new insight and new products um 44:26.219 --> 44:28.386 much more quickly and we couldn't have 44:28.386 --> 44:30.219 done that uh Both without um our 44:30.219 --> 44:31.775 professionals across the UK 44:31.775 --> 44:34.449 intelligence community and U UK mod . 44:34.459 --> 44:36.459 But also we're taking a tiny bit of 44:36.459 --> 44:38.403 risk . We implemented that without 44:38.403 --> 44:40.181 training people . Hence I got a 44:40.181 --> 44:42.237 complaint . Um but we implemented it 44:42.237 --> 44:44.237 because we thought it was the right 44:44.237 --> 44:46.348 thing to do and we've seen the impact 44:46.348 --> 44:46.330 with senior decision makers um from 44:46.340 --> 44:48.929 doing that . Thanks Jack , gentlemen . 44:48.939 --> 44:50.772 Thank you for those comments and 44:50.772 --> 44:52.889 insights . Um Now over to the magic 44:52.899 --> 44:55.121 wand question or if you were king for a 44:55.121 --> 44:57.459 day . Um What is the one thing you 44:57.469 --> 44:59.979 would do to enable it integration 44:59.989 --> 45:01.933 across the five eyes , Eric , I'll 45:01.933 --> 45:05.070 start with you . Yeah , I think if I 45:05.080 --> 45:07.989 had a magic wand , the one thing I 45:08.000 --> 45:11.989 would do would be to create a 45:12.000 --> 45:15.719 unified sovereign agnostic agnostic 45:15.729 --> 45:18.409 cloud environment . Um So a cloud 45:18.419 --> 45:21.149 environment where all of the five eyes 45:21.320 --> 45:24.719 can develop can operate um can do their 45:24.729 --> 45:27.340 compute , can store data . And on the 45:27.350 --> 45:29.669 topic of data , every piece of data in 45:29.679 --> 45:31.457 this cloud environment would be 45:31.457 --> 45:33.457 properly tagged so that it could be 45:33.457 --> 45:37.350 accessed by see 45:37.360 --> 45:40.750 Laurie paid me for that one . um 45:42.939 --> 45:45.290 And if I had this magic wand , not only 45:45.300 --> 45:47.929 would this cloud be a top secret cloud , 45:48.159 --> 45:50.381 but it would be classification agnostic 45:50.381 --> 45:52.830 as well because the data is all tagged 45:52.840 --> 45:55.040 because all of my users all have the 45:55.050 --> 45:56.994 correct digital identities . I can 45:56.994 --> 45:58.883 store all the data in the cloud . 45:58.883 --> 46:00.717 Everyone can access what they're 46:00.717 --> 46:02.883 allowed to access when they're allowed 46:02.883 --> 46:04.606 to access it , it would enable 46:04.606 --> 46:07.100 interoperability , it would enable the 46:07.110 --> 46:10.260 development of new tools . Um And it 46:10.270 --> 46:13.219 would give us , you know , a platform 46:13.399 --> 46:16.100 that would be that one thing that I 46:16.110 --> 46:18.221 could then give an answer to the last 46:18.221 --> 46:20.277 question . Say this was the piece of 46:20.277 --> 46:22.709 technology that enabled mission success . 46:23.080 --> 46:25.540 So if I had the magic Wand , that would 46:25.550 --> 46:27.260 be it a 46:28.889 --> 46:32.469 nation agnostic cloud environment 46:33.129 --> 46:35.810 that allowed us to share an 46:35.820 --> 46:38.540 interoperable and still would have 46:38.679 --> 46:40.959 sovereign cloud capability within this 46:40.969 --> 46:42.969 cloud . We so we would all still be 46:42.969 --> 46:45.629 able to to store our sovereign data as 46:45.639 --> 46:49.070 well as operate as a uh true five eyes 46:49.080 --> 46:51.413 uh in that environment . So there we go . 46:51.413 --> 46:55.229 Thanks Eric Andy . Ah sir , I am 46:55.239 --> 46:57.406 maybe not as ambitious as Eric in that 46:57.406 --> 47:00.739 regard . But um I think if I was if I 47:00.750 --> 47:03.570 was to have the magic wand , I would 47:03.840 --> 47:06.062 have a design principle across the five 47:06.062 --> 47:08.300 countries that made um five eyes 47:08.310 --> 47:10.199 integration a foundational design 47:10.199 --> 47:13.080 principle of everything that we do . Um 47:13.090 --> 47:15.312 And if I was allowed to waive that wand 47:15.312 --> 47:17.439 a second time , I would also ask that 47:17.449 --> 47:19.616 uh policy kept pace with technological 47:19.616 --> 47:21.616 advancement . But those are the two 47:21.616 --> 47:23.782 things that I would , I would hope for 47:23.782 --> 47:26.116 from that magic wand waving thanks Andy . 47:26.116 --> 47:30.100 A Yeah . So um yeah , if I had the , 47:30.110 --> 47:32.429 the magic wand for a day , um and I'm 47:32.439 --> 47:34.439 gonna shamelessly score more points 47:34.439 --> 47:36.899 with Laurie and Mac and say that uh it 47:36.909 --> 47:40.909 would be um it would be 47:40.919 --> 47:43.120 that the , the fine grain tagging of 47:43.129 --> 47:45.629 data throughout the entirety of the , 47:45.639 --> 47:47.290 the fa defense and National 47:47.300 --> 47:49.189 Intelligence Enterprise . I think 47:49.189 --> 47:51.469 that's where um you know , we've made 47:51.479 --> 47:54.830 great strides um in , in , you know , 47:54.840 --> 47:56.951 in recent time and there's a lot more 47:56.951 --> 47:59.173 work to do . Um But I see that and then 47:59.173 --> 48:01.396 if I could go off of what Andy said and 48:01.396 --> 48:03.507 wave it a second time , uh the second 48:03.507 --> 48:05.507 time would be um related to what uh 48:05.507 --> 48:07.669 what Eric touched on was identity um 48:08.100 --> 48:10.540 and uh and , and identity attribute 48:10.550 --> 48:14.149 services to check . So I wrote down 48:14.159 --> 48:16.600 almost word for word um what Eric said . 48:16.610 --> 48:19.340 So uh so I'd love that but I'm not 48:19.350 --> 48:21.683 gonna use my go up on that because Eric , 48:21.683 --> 48:23.794 we've already got that from Eric . Um 48:23.794 --> 48:25.794 So if I wave my magic wand , what I 48:25.794 --> 48:29.479 would love us to do is to reduce almost 48:29.489 --> 48:32.679 to zero the unnecessary bureaucracy 48:32.689 --> 48:36.370 process things that are just 48:36.379 --> 48:38.435 holding us back that are adding very 48:38.435 --> 48:41.330 little value either to our security or 48:41.340 --> 48:43.229 to our intelligence mission . But 48:43.229 --> 48:45.507 because they've been there for so long , 48:45.507 --> 48:47.229 we've just got really , really 48:47.229 --> 48:50.750 comfortable with them , sir . Um I'll 48:50.760 --> 48:52.816 probably stick with the uh the , the 48:52.816 --> 48:55.093 theme of consistency and communication . 48:55.169 --> 48:57.250 Uh One source of the truth uh with 48:57.260 --> 48:59.482 regards to how we build and integrate . 48:59.830 --> 49:02.052 Uh We all know that as a small nation , 49:02.052 --> 49:04.219 we see programs of work and they drift 49:04.219 --> 49:06.163 off to internal needs , uh bespoke 49:06.163 --> 49:08.330 requirements and therefore we can lose 49:08.330 --> 49:10.552 that ability to integrate . So if I had 49:10.552 --> 49:12.386 the magic wand , it would be the 49:12.386 --> 49:14.219 ability to leveraging off what's 49:14.219 --> 49:16.108 already been discussed by my four 49:16.108 --> 49:18.330 learned panel members uh to rationalize 49:18.330 --> 49:20.497 our infrastructure . Uh So we think we 49:20.497 --> 49:22.719 reduced overheads , sustained overheads 49:22.719 --> 49:24.830 and therefore put greater efforts and 49:24.830 --> 49:26.941 focus on to trade craft and uh decent 49:26.941 --> 49:28.997 making excellence to , to enable our 49:28.997 --> 49:30.663 war fighters uh and strategic 49:30.663 --> 49:32.774 headquarters uh to get that advantage 49:32.774 --> 49:34.941 uh the decision advantage . OK . Thank 49:34.941 --> 49:37.189 you . Uh understanding that these 49:37.199 --> 49:39.255 gentlemen are , are living this on a 49:39.255 --> 49:41.032 daily basis and uh we've worked 49:41.032 --> 49:43.800 together on many things . Notably Mars . 49:44.199 --> 49:47.300 Um I think what you're hearing is those 49:47.310 --> 49:49.421 key challenges or views that we often 49:49.421 --> 49:51.477 come across in terms of why don't we 49:51.477 --> 49:53.310 just do this um from a five eyes 49:53.310 --> 49:55.310 perspective , understanding there's 49:55.310 --> 49:57.366 many reasons and complexities uh and 49:57.366 --> 49:59.421 layers that we need to navigate . Um 49:59.421 --> 50:01.643 But I think what you're hearing here is 50:01.643 --> 50:03.810 the some of the solution space um that 50:03.810 --> 50:05.754 we think we need to get after . So 50:05.754 --> 50:07.977 thank you very much for the insights on 50:07.977 --> 50:10.143 that piece . Um mindful of time . What 50:10.143 --> 50:12.830 I'd like to do here is a bit of a pivot . 50:13.280 --> 50:16.030 Um And I , I have not offered this 50:16.040 --> 50:18.399 question in advance to uh to the panel 50:18.409 --> 50:20.830 here . Um But I think what I think is , 50:20.840 --> 50:22.729 is really useful to hear from our 50:22.729 --> 50:26.570 partners , Austin as well . Um You know , 50:26.590 --> 50:29.909 n specifically us 50:29.919 --> 50:31.863 leadership , those that are making 50:31.863 --> 50:34.030 those decisions in terms of what is it 50:34.030 --> 50:36.197 that you would like to share with that 50:36.197 --> 50:38.419 us audience in terms of approaching the 50:38.419 --> 50:40.308 five eyes , the partners , how to 50:40.308 --> 50:42.252 better integrate or perhaps how to 50:42.252 --> 50:44.308 better um align what we're trying to 50:44.308 --> 50:46.363 get at . Um So with that , I'll turn 50:46.363 --> 50:48.475 over to Andy if you have any thoughts 50:48.475 --> 50:48.469 that you like to share with , with the 50:48.939 --> 50:52.830 uh with the US audience , um 50:57.350 --> 51:00.719 I guess , understanding , 51:00.770 --> 51:03.120 understanding our requirements and what 51:03.129 --> 51:06.000 we can contribute into the partnership 51:06.010 --> 51:08.066 from the outset is a really powerful 51:08.066 --> 51:11.790 thing . Um We will go to great lengths 51:11.800 --> 51:15.429 to um integrate into the US 51:15.439 --> 51:17.830 system um as well as the five eyes . 51:18.570 --> 51:21.520 But in doing so , we often incur um 51:21.530 --> 51:25.300 risk by through latency 51:25.500 --> 51:27.389 because we will always be playing 51:27.389 --> 51:29.389 catch-up as we understand what your 51:29.389 --> 51:31.611 requirements are . Um If you understand 51:31.611 --> 51:33.833 our needs and requirements early , that 51:33.833 --> 51:36.056 will allow us to be the most productive 51:36.056 --> 51:38.360 partner we can for the US , but also 51:38.370 --> 51:40.669 for the wider five eyes . And so um 51:40.679 --> 51:42.679 that would be the one thing I'd I'd 51:42.679 --> 51:45.012 offer out as a um as an initial thought . 51:45.012 --> 51:48.689 Ok , thanks Andy . So mindful that your 51:48.699 --> 51:52.179 career could be on the line here , the 51:52.189 --> 51:54.989 Fifth Wheel in the American . So , uh I , 51:55.000 --> 51:57.810 I think I think what I would offer um 51:57.820 --> 51:59.987 is something that was offered at uh at 51:59.987 --> 52:02.042 the , at the panel last year that um 52:02.042 --> 52:04.264 that kind of resonated with me a little 52:04.264 --> 52:07.949 bit and that's um you know , approach 52:08.379 --> 52:10.601 every problem that we do that we have , 52:10.601 --> 52:12.840 you know , that we're faced with , with 52:12.850 --> 52:15.183 five a partner interoperability in mind . 52:15.330 --> 52:18.360 Um I think Doug said it a few years 52:18.370 --> 52:20.800 back that um you know , 52:20.810 --> 52:24.310 interoperability costs minimal at the 52:24.320 --> 52:26.770 start and then it's exponentially large 52:26.780 --> 52:29.002 the further along in a product that you 52:29.002 --> 52:30.724 get . Um So starting it at the 52:30.724 --> 52:34.679 beginning is a cheap way to ensure 52:34.770 --> 52:36.659 that our closest partners and the 52:36.659 --> 52:38.826 people that we are going to be side by 52:38.826 --> 52:41.159 side with marching into whatever crisis , 52:41.159 --> 52:43.048 uh you know , from competition to 52:43.048 --> 52:45.103 crisis to conflict uh to making sure 52:45.103 --> 52:47.159 that they're in lockstep with us and 52:47.159 --> 52:48.992 have the same access and can see 52:48.992 --> 52:50.992 everything that they need to see to 52:50.992 --> 52:54.389 help us be um the uh the formidable 52:54.399 --> 52:56.732 force that , that we are as an alliance . 52:56.830 --> 53:00.189 Thank you , Austin Jack . I think for 53:00.199 --> 53:02.739 me , it's about getting to the place of 53:02.750 --> 53:05.739 really rich and deep data 53:05.750 --> 53:07.806 interoperability amongst us . And so 53:07.806 --> 53:09.917 that means being really serious about 53:09.917 --> 53:11.694 data tagging , data standards , 53:11.909 --> 53:14.076 attribute based access controls here , 53:14.076 --> 53:16.076 trust architecture , all the things 53:16.076 --> 53:18.187 we've been talking about this morning 53:18.187 --> 53:20.409 this afternoon , sorry , but also being 53:20.409 --> 53:22.576 clear from the US side where there are 53:22.576 --> 53:22.500 degrees of freedom and where there 53:22.510 --> 53:24.621 aren't where there is a great product 53:24.621 --> 53:26.843 that you have that you just really love 53:26.843 --> 53:28.954 us to implement . Please just tell us 53:28.954 --> 53:30.954 sometimes it's really handy to have 53:30.954 --> 53:32.899 that steer particularly when we're 53:32.899 --> 53:35.010 making our own investment decisions . 53:35.010 --> 53:37.794 And also there is some benefits of 53:37.804 --> 53:41.014 being smaller , sometimes more agile , 53:41.024 --> 53:43.024 sometimes more able to take risk in 53:43.024 --> 53:44.968 different areas . And so we should 53:44.968 --> 53:47.574 think amongst the five of us , how 53:47.584 --> 53:49.395 we're able to leverage both our 53:49.405 --> 53:51.534 national perspectives to be able to 53:51.544 --> 53:53.655 maximize the benefit of being able to 53:53.655 --> 53:57.090 do that . Thank you , Jack . Uh I I'll 53:57.100 --> 53:58.933 just say keep bringing us on the 53:58.933 --> 54:00.878 journey . Journey's been mentioned 54:00.878 --> 54:03.044 several times today too . Uh I in , in 54:03.044 --> 54:04.989 a previous role . And CJ C two was 54:04.989 --> 54:07.489 mentioned earlier today . Uh And they 54:07.500 --> 54:09.500 brought the , the five eyes in very 54:09.500 --> 54:11.611 early with CJ C two that helps us set 54:11.611 --> 54:13.500 that path , navigate that sort of 54:13.500 --> 54:15.550 program decision making uh finance 54:15.560 --> 54:17.504 allocation . So that's something I 54:17.504 --> 54:19.282 would stress . The other one is 54:19.282 --> 54:21.282 probably leveraging off some of the 54:21.282 --> 54:23.449 comments that have already been made , 54:23.449 --> 54:23.340 tell us what you'd like us to do , uh 54:23.350 --> 54:25.572 particularly as a smaller nation and uh 54:25.572 --> 54:27.406 much smaller than the UK uh that 54:27.406 --> 54:29.628 agility , we should be able to use that 54:29.628 --> 54:31.739 agility more . Uh How can you harness 54:31.739 --> 54:34.017 some of the strengths we bring as , as , 54:34.017 --> 54:36.128 as a smaller nation . Um That's so we 54:36.128 --> 54:38.294 can bring that , that added value to , 54:38.294 --> 54:40.350 to , to the US . Thank you , Brendan 54:40.350 --> 54:42.520 and Eric . Yeah , I think , um , 54:44.590 --> 54:46.423 so I think Canada is naturally a 54:46.423 --> 54:48.870 contribution , war warfare is the way 54:48.879 --> 54:50.935 we approach things . We'll always be 54:50.935 --> 54:53.320 part of a coalition . Um We'll , you 54:53.330 --> 54:55.274 know , whether or not it's NATO or 54:55.274 --> 54:57.552 coalition of the willing or , you know , 54:57.552 --> 55:01.350 it's in uh in NORAD . So I think what I 55:01.360 --> 55:03.582 would state uh would be or what I would 55:03.582 --> 55:05.909 ask is be honest with us about what 55:05.919 --> 55:08.370 your gaps are . If there are things 55:08.379 --> 55:09.990 where there are gaps in your 55:09.990 --> 55:12.212 capabilities and that's gonna be a hard 55:12.212 --> 55:14.435 conversation obviously to have . But if 55:14.435 --> 55:16.490 we're gonna put a limited investment 55:16.490 --> 55:18.323 into something I'd rather put an 55:18.323 --> 55:20.435 investment in something that is a gap 55:20.435 --> 55:22.657 for you . Therefore , we can contribute 55:22.657 --> 55:24.379 to the coalition as opposed to 55:24.379 --> 55:26.546 duplicating something that you already 55:26.546 --> 55:28.546 do . Um So let's make the five eyes 55:28.546 --> 55:30.768 function in a way that we can fill each 55:30.768 --> 55:33.504 other's gaps uh to move forward um and 55:33.514 --> 55:36.415 make the most out of the uh you know , 55:36.425 --> 55:38.369 the defense budgets that we have . 55:38.929 --> 55:40.929 Thank you . Thank you , gentlemen , 55:40.929 --> 55:43.096 appreciate it . Um , mindful of time . 55:43.096 --> 55:45.780 We're close to five minutes . Um I just 55:45.790 --> 55:47.899 wanna offer perhaps some closing 55:47.909 --> 55:49.687 remarks if you will or some key 55:49.687 --> 55:51.798 takeaways that at least I've noted or 55:52.010 --> 55:54.540 that I've come to experience as my time 55:54.550 --> 55:56.550 uh as D DC I in the last six months 55:56.550 --> 55:58.661 with the agency . Uh and then perhaps 55:58.661 --> 56:00.772 we'll have time for a question or two 56:00.772 --> 56:02.994 from the floor . Um And , and I'll echo 56:02.994 --> 56:05.106 and riff off some of the points gents 56:05.106 --> 56:07.383 that you've raised uh for the partners . 56:07.383 --> 56:07.129 I would offer that . It is a way of 56:07.139 --> 56:09.750 life . Partner integration uh is a way 56:09.760 --> 56:12.169 of life . Uh It's , it's second nature , 56:12.179 --> 56:14.149 it's innate . Um where , whereas 56:14.159 --> 56:16.103 sometimes with the US enterprise , 56:16.103 --> 56:18.159 given your scale and scope , um it's 56:18.159 --> 56:20.437 not necessarily a way of life up front . 56:20.437 --> 56:22.437 Um That said , I just want to offer 56:22.437 --> 56:24.492 that as , as thought , um ask of the 56:24.492 --> 56:26.659 partners what you want from them , the 56:26.659 --> 56:28.715 partners will leverage the US IC and 56:28.715 --> 56:31.030 dod as much as it can . Please ask the 56:31.040 --> 56:33.429 partners what they can contribute um to 56:33.439 --> 56:36.010 your efforts and initiative to the 56:36.020 --> 56:38.076 point of coalition warfare . It is a 56:38.076 --> 56:40.409 reality . Um , you can look at all 56:40.419 --> 56:42.419 recent conflict and dating back the 56:42.419 --> 56:44.752 first world War and perhaps even beyond , 56:44.752 --> 56:48.340 maybe not the war of 1812 . Um , but we , 56:48.800 --> 56:51.219 we co coalition warfare is a reality . 56:51.229 --> 56:53.540 We will be down range side by side , 56:53.550 --> 56:55.772 shoulder to shoulder . How do we remain 56:55.772 --> 56:57.939 interoperable ? How do we baseline the 56:57.939 --> 56:59.994 way we fight down range , the way to 56:59.994 --> 56:59.929 the way we do business today ? How do 56:59.939 --> 57:02.139 we , how do we achieve that ? Um 57:02.149 --> 57:04.260 Reminder of how , how do we strive to 57:04.260 --> 57:06.260 become integrated up front ? It was 57:06.260 --> 57:08.482 mentioned earlier . Uh One of the panel 57:08.482 --> 57:10.427 members , I forget who exactly but 57:10.427 --> 57:12.538 mentioned , integrate the partners up 57:12.538 --> 57:14.649 front , not after the fact . Uh I , I 57:14.649 --> 57:16.739 strongly advise um for that kind of 57:16.750 --> 57:18.806 approach . Um One of the things that 57:18.806 --> 57:20.639 was also raised was the right to 57:20.639 --> 57:22.750 release , right to release , right to 57:22.750 --> 57:24.917 release . I would , I would also offer 57:24.917 --> 57:27.139 and this becomes a bit more challenging 57:27.139 --> 57:29.159 the collector release . If we can 57:29.169 --> 57:31.002 collect a release , the right to 57:31.002 --> 57:33.629 release becomes a lot easier on behalf 57:33.639 --> 57:37.629 of everybody . Um And finally , 57:37.639 --> 57:41.580 I think I just want to , to say 57:41.590 --> 57:44.179 that uh before we end here . Uh I just 57:44.189 --> 57:46.520 wanna thank thank the panelists for uh 57:46.530 --> 57:49.010 your insights , your commitment to the 57:49.020 --> 57:51.270 mission . Um Many of you have flown 57:51.280 --> 57:54.469 from a place far , far away . Um And I 57:54.479 --> 57:56.423 do , I do appreciate your time and 57:56.423 --> 57:58.423 effort and your your willingness to 57:58.423 --> 58:00.860 share with , um with us today , uh in 58:00.870 --> 58:03.037 terms of what it is that we need to do 58:03.037 --> 58:05.169 as allies . Uh I think we are the 58:05.179 --> 58:07.969 closest of friends . Um And I think we 58:07.979 --> 58:10.090 need to continue to privilege that uh 58:10.090 --> 58:12.035 and work towards that because as I 58:12.035 --> 58:14.201 mentioned , I think we will be uh side 58:14.201 --> 58:17.179 by side uh tonight or tomorrow during 58:17.189 --> 58:20.080 crisis or conflict . Um And I also like 58:20.090 --> 58:22.649 to all kidding aside . Uh , I 58:22.659 --> 58:25.229 absolutely love my time at Dia . Um , 58:25.239 --> 58:27.520 and it's a real privilege to be D DC I 58:27.530 --> 58:29.586 and serve within the agency to serve 58:29.586 --> 58:32.219 within the US IC . Uh , and , and to be , 58:32.280 --> 58:34.391 uh , to be amongst you , uh , I think 58:34.391 --> 58:36.391 it's a great opportunity . Um , and 58:36.391 --> 58:38.340 it's fantastic , um , through and 58:38.350 --> 58:40.899 through . So please join me in thanking 58:40.909 --> 58:41.909 our panelists . 58:48.989 --> 58:50.989 Many are still jet lagged . We were 58:50.989 --> 58:53.211 fearful that perhaps the comfort of the 58:53.211 --> 58:54.989 chairs might be , uh , might be 58:54.989 --> 58:56.822 detrimental . Um , we do have 22 58:56.822 --> 58:59.045 minutes and 35 seconds if anybody would 58:59.045 --> 59:01.267 have a question , uh , please feel free 59:01.267 --> 59:04.649 to , uh , to ask the question . So , 59:04.659 --> 59:07.560 first of all , I just want to say hand 59:07.620 --> 59:09.620 of applause to our panelists here . 59:09.620 --> 59:10.787 These are our goal . 59:14.100 --> 59:15.899 Thank you . Yes . 59:18.090 --> 59:21.120 Um , you asked the question I was gonna 59:21.129 --> 59:23.240 ask and I'd like to pose that to each 59:23.240 --> 59:25.185 of the panelists . What is the one 59:25.185 --> 59:27.185 thing that they think that they can 59:27.185 --> 59:29.540 contribute best to the partnership as 59:29.560 --> 59:31.790 we go forward whether that's space or 59:31.800 --> 59:35.129 policy help or analytical or sensor or 59:35.139 --> 59:37.195 whatever it might be . Where do they 59:37.195 --> 59:38.861 think they can best help this 59:38.861 --> 59:42.719 partnership ? John 59:42.729 --> 59:44.909 Brandon , sir . Um look , I probably 59:44.919 --> 59:47.370 mentioned the , the scale of uh my 59:47.379 --> 59:49.379 defense force , New Zealand Defense 59:49.379 --> 59:51.379 Force . Uh There's one area that we 59:51.379 --> 59:53.546 don't have a lot of depth and a lot of 59:53.546 --> 59:52.870 areas , but we have a lot of breadth . 59:52.879 --> 59:55.046 So one area I think we can assist with 59:55.046 --> 59:59.020 is cohesion across the five . Thank 59:59.030 --> 01:00:01.699 you , Brendan . Anybody else , Eric , 01:00:03.459 --> 01:00:05.403 not a technological answer , but I 01:00:05.403 --> 01:00:07.181 think the one place where we've 01:00:07.181 --> 01:00:09.292 realized we need to step up or we can 01:00:09.292 --> 01:00:11.515 contribute is in the Arctic . Um And so 01:00:11.515 --> 01:00:13.792 I think as we sort of move out on that , 01:00:13.792 --> 01:00:15.792 I think there are benefits um for a 01:00:15.792 --> 01:00:17.959 number of our nations and then lessons 01:00:17.959 --> 01:00:20.015 to be learned when we look at the uh 01:00:20.015 --> 01:00:19.780 southern regions . So I think there is 01:00:19.790 --> 01:00:22.179 an area where uh Canada can definitely 01:00:22.189 --> 01:00:24.300 uh contribute to the five eyes moving 01:00:24.300 --> 01:00:26.979 forward . Yeah , I think um 01:00:28.699 --> 01:00:31.260 we have some very unique defense 01:00:31.270 --> 01:00:33.810 industry contributions . We can make um 01:00:33.820 --> 01:00:37.040 our geography , our place in the world , 01:00:37.050 --> 01:00:40.669 our um available resource means that we 01:00:40.679 --> 01:00:42.623 have to look at asymmetric ways of 01:00:42.623 --> 01:00:44.735 doing things . And that really drives 01:00:44.735 --> 01:00:46.901 some cutting edge tech innovation that 01:00:46.901 --> 01:00:48.957 might not be immediately apparent to 01:00:48.957 --> 01:00:50.901 the big systems where big industry 01:00:50.901 --> 01:00:53.068 deals . So I think we've got some real 01:00:53.068 --> 01:00:55.290 contributions we can make there Uh So I 01:00:55.290 --> 01:00:57.290 think we should continue the burden 01:00:57.290 --> 01:00:59.179 sharing we're already doing on uh 01:00:59.179 --> 01:01:01.235 particularly in our geo intelligence 01:01:01.235 --> 01:01:03.346 mission um for the European theater , 01:01:03.346 --> 01:01:05.679 for the war in Ukraine and other places , 01:01:06.560 --> 01:01:10.189 Austin . You're good . Fantastic . 01:01:10.270 --> 01:01:11.992 Just remember they are a force 01:01:11.992 --> 01:01:13.937 multiplier to everything you do in 01:01:13.937 --> 01:01:15.603 terms of placement and access 01:01:15.603 --> 01:01:15.570 capabilities and authorities uh 01:01:15.580 --> 01:01:17.909 integrated deterrent . I think we are 01:01:17.919 --> 01:01:20.197 much stronger . And uh thank you again , 01:01:20.197 --> 01:01:22.252 gentlemen . Uh It's been a fantastic 01:01:22.252 --> 01:01:24.363 panel . I appreciate it . Thank you . 01:01:29.310 --> 01:01:30.310 That's good . 01:01:33.790 --> 01:01:34.360 Thank you .