[00:05.920 --> 00:11.280]  Thanks, everyone, for the second day of the curative event, which is DEF CON.
[00:12.000 --> 00:17.280]  So I'm Andy Cooper, one of the founders of the OSDF Village, and I'm here doing the fireside chat.
[00:17.280 --> 00:17.800]  Chris?
[00:17.800 --> 00:20.980]  Yeah, Chris Roberts, CISO over at Boom Supersonic.
[00:20.980 --> 00:26.820]  I love the intro, because when I was interviewed, they were like, hey, how do you fancy securing the next generation of Lord Dart?
[00:26.820 --> 00:28.400]  And I'm like, yes.
[00:29.780 --> 00:37.220]  Now, as Chris has said, he hasn't been killed at all, so I'm going to keep an eye out for white screens or red faces.
[00:37.980 --> 00:41.920]  So if anybody feels a bit uncomfortable, please just raise your hand.
[00:41.920 --> 00:44.760]  This is a safe space for everybody, really.
[00:49.060 --> 01:07.920]  So the OSDF Village is all about having great, vibrant voices talking about things they're passionate about and how we can collaborate together to make the aerospace sector as safe and secure as possible and bring in all those voices, be they faculty,
[01:07.920 --> 01:09.820]  be they researchers, government, industry.
[01:11.020 --> 01:19.820]  And that's why our fireside chat with Chris is, we believe, is really important, because Chris has been around this topic for years.
[01:19.900 --> 01:23.500]  He's got loads of experience and his perspective on this.
[01:23.500 --> 01:30.540]  But he now finds himself, as a CISO, securing one of the most vast next-gen aircraft in the world.
[01:31.300 --> 01:42.660]  So we really want to get him in the perspective of how we do it, what is the right shape, and then to, like, necessarily get the same offer out to the community going forward.
[01:42.660 --> 01:43.600]  So, Chris?
[01:43.600 --> 01:44.680]  Yeah, I love the idea.
[01:44.680 --> 01:45.380]  Absolutely.
[01:45.380 --> 01:49.000]  And, I mean, to Pete's point as well, we're fortunate.
[01:49.000 --> 01:51.320]  We have an entire greenfield.
[01:51.320 --> 01:57.420]  So the lovely thing about being at Boom is our ability to actually take a step back and go, how have things been done?
[01:58.080 --> 02:00.620]  Versus maybe, how would we like to do them differently?
[02:00.620 --> 02:14.320]  Look at the community, look at what we've done in our own industries, learn from that, and maybe more efficiently and more effectively bring that into our small little world of aviation, see how it works, and then see if we can work with the rest of the teams out there too.
[02:14.320 --> 02:16.540]  So join me in a quick elevator pitch on Boom.
[02:16.860 --> 02:18.820]  Yeah, I mean, perfect example.
[02:18.820 --> 02:21.500]  How many of you, a quick show of hands, how many of you remember the Concorde?
[02:21.500 --> 02:25.420]  Not necessarily show your age on Remember It, but know what the hell the stupid thing is.
[02:25.760 --> 02:42.100]  So take the Concorde and the technology that was built in the 50s, 60s, and 70s, fast forward that to the 2020s with better aerodynamics, better fluid dynamic knowledge, better engine knowledge, better metallurgy knowledge, better knowledge of how we can actually punch through the air faster,
[02:42.100 --> 02:45.060]  more effectively, sustainable aviation fuel.
[02:45.060 --> 02:57.440]  Apply that, chuck something up at 60,000 feet, and instead of most of us spending 6, 8, 10, 12 hours on a tin can, we take one to two-thirds of that away, get you there faster, quicker, and safer.
[02:57.440 --> 03:00.120]  That, literally, is Boom Supersonic.
[03:00.880 --> 03:05.340]  A new viewpoint is the effect of securing the ground up.
[03:05.340 --> 03:11.600]  But the first thing for me, talking about the threats, be that environmental, be that adversaries, be that...
[03:11.600 --> 03:15.520]  How do you make the groundwork of what it is you're defending against?
[03:15.520 --> 03:22.460]  I think it's... I'm fortunate, because, again, I'm lucky we've got a lot of people inside the company who have come from the industry.
[03:22.740 --> 03:29.160]  So there's a lot of teams out there that have come from the Lockheeds and various other teams, the Skunk Works teams and Formula One teams.
[03:29.160 --> 03:31.260]  So they understand what data is.
[03:31.260 --> 03:42.520]  They understand, maybe, how certain data has to be classified, how certain data can't leave these shores, and how certain data and certain systems are core and key.
[03:42.520 --> 03:44.420]  So, basically, what are the keys to our kingdom?
[03:44.420 --> 03:45.580]  Intellectual property.
[03:45.840 --> 03:47.300]  So that's a nice starting ground.
[03:47.300 --> 03:49.940]  And then it's building awareness and understanding around that.
[03:49.940 --> 03:54.620]  But the first thing, honestly, a CISO does when they walk in is go, What do I have?
[03:54.740 --> 03:57.360]  So looking at the assets that the organization have.
[03:57.360 --> 04:04.380]  We have, three and a half hours away from here in Moab, an experimental jet that's going through final FAA certification.
[04:04.920 --> 04:07.700]  That thing's absolutely bloody amazing.
[04:07.840 --> 04:13.940]  Now, right next to my office in Colorado, we have the full-size Ironbird, which we're building everything in.
[04:13.940 --> 04:16.200]  And now in North Carolina, we have the factory.
[04:16.460 --> 04:22.200]  So each one of those is an entirely different ecosphere as to what we need to do with threats.
[04:22.320 --> 04:24.200]  Some of it's intellectual property and data.
[04:24.200 --> 04:26.340]  Some of it is technical information.
[04:26.340 --> 04:33.580]  Some of it is just data that we need to ensure the integrity and the safety of the systems that we're building.
[04:33.580 --> 04:43.900]  In other words, when the FAA says, Hey, in 20 years' time, give me all the records for that chassis number or engine number or whatever, we can produce that in an immutable manner.
[04:43.900 --> 04:45.800]  So there's all sorts of different considerations.
[04:45.800 --> 04:47.560]  But again, all comes down to data.
[04:48.720 --> 05:01.960]  And from that perspective of getting the groundwork done, working across the company, I mean, we've seen the evolutionary journey that the sector has had and manufacturing has had on a boxy platform.
[05:02.640 --> 05:05.360]  You're starting that journey from scratch with the company.
[05:06.300 --> 05:09.720]  Is it an easy conversation to talk about?
[05:09.720 --> 05:13.040]  Right, we need to be getting ready for doing this in a secure manner.
[05:13.840 --> 05:19.640]  With getting ready against these threats, we've got to have a high-trust environment across all of these systems.
[05:19.700 --> 05:21.260]  Is that an easy conversation?
[05:22.720 --> 05:30.780]  Internally, I think it's easier because we don't have legacy of 20, 30, 40, or almost 100 years' worth of that to deal with.
[05:30.840 --> 05:33.320]  But we deal with supply chains just as everybody else does.
[05:33.320 --> 05:36.340]  You know, I looked it up before I came on stage here.
[05:36.340 --> 05:36.900]  I looked it up.
[05:36.900 --> 05:41.680]  One of the other major manufacturers has about 20,000 suppliers.
[05:41.680 --> 05:43.000]  We're not there yet.
[05:43.000 --> 05:45.900]  We have about maybe a couple of hundred suppliers.
[05:46.040 --> 05:49.200]  So it isn't just how I manage... Oops, I'm going to get yelled at for bashing this.
[05:49.200 --> 05:51.480]  It isn't just how I manage my own security.
[05:51.480 --> 05:55.040]  It's how do I impart some of that knowledge onto the supply chain.
[05:55.260 --> 05:56.720]  We've taken a different approach.
[05:56.720 --> 05:58.660]  We've taken it from a very human approach.
[05:59.100 --> 06:04.800]  I come from a very technical background, but I also come from a background where I've done a lot of outreach.
[06:04.800 --> 06:08.140]  So rather than looking at somebody going, You work for my company.
[06:08.140 --> 06:10.100]  You will be very, very respectful of my data.
[06:10.100 --> 06:12.620]  And God forbid the fact that you move that data anywhere.
[06:12.840 --> 06:15.560]  I go, hey, how can I help you with the human?
[06:15.900 --> 06:17.360]  How can I help your family?
[06:17.360 --> 06:22.120]  How can I help the kids, the guardians, those around you be more aware of safety and security?
[06:22.260 --> 06:25.100]  How do I empower you to make better decisions?
[06:25.100 --> 06:26.180]  We're all going to click shit.
[06:26.180 --> 06:27.540]  I mean, let's face it, we do.
[06:27.960 --> 06:33.580]  But how do I get you to ask a question or two before you click something so that you're more aware?
[06:33.580 --> 06:35.980]  And you spread that word to the engineering teams.
[06:35.980 --> 06:38.620]  You spread it to the design teams, the manufacturer.
[06:39.360 --> 06:48.220]  I mean, our finance teams are probably among the worst because we're pre-revenue, so they start sending out prospectuses and financial data all over the place.
[06:48.360 --> 06:51.480]  And I'm like, okay, would you send your home bank records everywhere?
[06:51.480 --> 06:52.380]  And they're like, oh, heck no.
[06:52.380 --> 06:54.720]  I'm like, so why is it okay to send ours?
[06:54.720 --> 06:56.320]  Oh, didn't think of it that way.
[06:56.580 --> 06:59.360]  So then you take a step back and go, well, how would you send the bank records?
[06:59.360 --> 07:00.160]  Well, I'd encrypt them.
[07:00.160 --> 07:00.440]  All right.
[07:00.440 --> 07:05.060]  Then let's give you a technology and a tool and a process that you can do that easily.
[07:05.060 --> 07:08.420]  So you're winning the conversation internally.
[07:08.520 --> 07:10.420]  So let's talk about the platform itself.
[07:11.640 --> 07:14.300]  So as you said before, you've got a Greenfield site.
[07:14.660 --> 07:16.060]  Build this as your platform.
[07:16.980 --> 07:17.660]  Where do you go?
[07:17.660 --> 07:18.440]  How do you start?
[07:18.940 --> 07:20.120]  Take a step back.
[07:21.180 --> 07:21.820]  Sorry.
[07:22.400 --> 07:27.780]  We have a fairly... like a lot of us, I mean, we're all beholden to regulatory compliance.
[07:28.000 --> 07:31.220]  So when I walked into Boom, I'm like, where are we from a maturity standpoint?
[07:31.220 --> 07:34.540]  I was met with this, I'm like, all right, let's have the conversation.
[07:34.540 --> 07:38.520]  So we sat down and used NIST's cybersecurity framework.
[07:38.600 --> 07:40.800]  And we sat down and said, what's important to us?
[07:40.800 --> 07:45.580]  Again, I always, whenever I walk into a company, I typically ask a simple question.
[07:45.580 --> 07:46.840]  How can I kill you?
[07:46.980 --> 07:48.640]  And it's not a facetious question.
[07:48.640 --> 07:49.620]  It's not being an arsehole.
[07:49.620 --> 07:53.700]  It's what could I do to take you down in the next 24 hours?
[07:53.780 --> 07:57.100]  Is it put a handful of sand in the 3D machine printer?
[07:57.100 --> 07:58.980]  Is it stop the supply chain?
[07:58.980 --> 08:00.320]  Is it break the network?
[08:00.320 --> 08:05.860]  And once we've figured that out between all the different parties, now we know what we all have to address and what we care about.
[08:06.200 --> 08:08.780]  But the cybersecurity framework gives us some help on that one.
[08:08.780 --> 08:11.700]  Because it's like, hey, we need to be at a maturity level of X.
[08:11.700 --> 08:12.820]  We want to be here.
[08:12.880 --> 08:14.000]  This is where we're at.
[08:14.000 --> 08:15.680]  Now how do we address that?
[08:15.680 --> 08:21.580]  And just to evolve our conversation a bit more, look at the cybersecurity framework.
[08:22.480 --> 08:26.360]  What do you find are the main gaps and overlaps of what you're trying to achieve?
[08:26.360 --> 08:27.220]  Oh, it's a ton.
[08:27.660 --> 08:28.920]  Yeah, oh, there's an absolute ton.
[08:28.920 --> 08:34.240]  I mean, when we walked in, I walked in, and I'm like, okay, you know, we have an endpoint detection.
[08:34.360 --> 08:35.040]  Great, yay.
[08:35.040 --> 08:35.880]  Is it working?
[08:36.380 --> 08:38.460]  I'm like, okay, let's have that conversation.
[08:38.740 --> 08:41.800]  Then you start having the conversation about, you know, where is my core data?
[08:41.800 --> 08:42.360]  Well, we don't know.
[08:42.360 --> 08:43.680]  Well, let's figure that out.
[08:43.680 --> 08:48.400]  Then the conversation is, look, if I poke something at 2 o'clock in the morning, who's going to be aware of it?
[08:48.440 --> 08:50.840]  So you start knocking off the low-hanging fruit.
[08:50.840 --> 08:54.920]  I mean, the biggest one for us is, where's the data, and who has eyes on it?
[08:55.040 --> 09:03.000]  So at that point, we went out, and we got a managed security provider because I don't want to build a sock-on-the-knock team, not of the size we're at, but I want to trust somebody.
[09:03.000 --> 09:03.900]  So we went out.
[09:03.980 --> 09:05.420]  We hung out with the Newspire crew.
[09:05.420 --> 09:07.460]  Maria was freaking amazing.
[09:07.460 --> 09:09.500]  She is a partner, not a vendor.
[09:09.760 --> 09:12.280]  And together, we've sat down, and we've figured it all out.
[09:12.680 --> 09:15.240]  So that's great.
[09:15.300 --> 09:17.740]  And then you're transporting that into the platform.
[09:17.840 --> 09:18.200]  Yep .
[09:18.620 --> 09:19.240]  That's the next big one.
[09:19.240 --> 09:20.400]  That's the next big one.
[09:20.400 --> 09:22.140]  That's what we're doing over at iInvert.
[09:22.820 --> 09:33.720]  That is now collaborating with a lot of the third-party vendors, quite a lot of the folks that are next door, and a lot that we have to still have conversations with because they're going to come to us and go, hey, here's our widget.
[09:33.720 --> 09:35.160]  That goes in that part of the airplane.
[09:35.160 --> 09:36.400]  And I'm like, no, it doesn't.
[09:37.180 --> 09:39.580]  It doesn't because we want to do things differently.
[09:39.580 --> 09:43.800]  It doesn't because we want to help you evolve your security.
[09:43.800 --> 09:45.860]  We want to help you evolve the safety.
[09:46.340 --> 09:51.180]  And P.S., not only that, all of the data is going to end up in my...
[09:51.180 --> 09:59.100]  I'll use AI, and you can throw something at me, but I'm actually building a fucking AI engine, not something that says AI and is just machine learning on steroids.
[09:59.540 --> 10:02.560]  We're building a platform that...
[10:02.560 --> 10:05.940]  Nice way of putting it is we're basically building a self-healing airplane.
[10:06.460 --> 10:22.080]  And so everything that we're putting on that plane, we're able to pull the data off, take a look at a platform envelope and basically a flight envelope and how it should operate versus how it does versus all of the ancillary elements that it should be working with and having the system make decisions.
[10:22.100 --> 10:25.940]  So anything that's coming into the plane has to be able to understand that.
[10:25.940 --> 10:27.500]  So I have that as the leverage.
[10:28.020 --> 10:31.520]  I also have the leverage as, hey, we're doing things differently.
[10:31.520 --> 10:33.480]  We're coming at this from a different approach.
[10:33.480 --> 10:34.960]  Let's have the conversations.
[10:34.960 --> 10:37.440]  Let's try to improve this.
[10:37.440 --> 10:40.300]  So let's just expand on that.
[10:40.300 --> 10:43.220]  So we're talking about that from an environmental point of view.
[10:43.340 --> 10:48.020]  Typically, engines are very well-connected computers.
[10:48.020 --> 10:49.840]  Most aircraft are currently as is.
[10:49.840 --> 10:51.580]  We're talking about doing more than that.
[10:51.580 --> 10:54.580]  So it's just engine data, cockpit data?
[10:54.580 --> 10:58.400]  Yep, engine data, cockpit data, atmospherics data, anything.
[10:58.400 --> 11:00.380]  I mean, we're carbon fiber wings.
[11:00.380 --> 11:05.000]  So now we're going to pull all the sensor architecture off of those wings and make individual decisions there.
[11:05.000 --> 11:07.360]  The entire fuselage is carbon fiber as well.
[11:07.360 --> 11:09.080]  And also, we're building our own engine.
[11:09.080 --> 11:10.640]  So I have an advantage there.
[11:10.720 --> 11:14.800]  Because we're not having to go out to any other manufacturers and go, hey, we need your stuff.
[11:14.800 --> 11:15.680]  We can actually build.
[11:15.680 --> 11:20.340]  So I walk over to the engineering team and go, hey, I need to pull the stats off of that and drop them in here.
[11:20.340 --> 11:21.280]  And they're like, okay.
[11:22.280 --> 11:23.960]  So that's the data architecture.
[11:23.960 --> 11:26.500]  And the question is, how do you secure that?
[11:26.500 --> 11:27.980]  So you're moving it all up.
[11:29.100 --> 11:31.620]  Massive pipe going back to home base.
[11:31.620 --> 11:32.380]  Oh, yeah.
[11:32.380 --> 11:34.960]  It has to be maintained and secured.
[11:34.960 --> 11:35.640]  Oh , yeah.
[11:35.640 --> 11:38.740]  Because it has a massive attack in here somewhere.
[11:38.800 --> 11:39.560]  Oh, yeah.
[11:39.560 --> 11:40.800]  So what's that like?
[11:42.160 --> 11:45.740]  So we've encryption at rest, encryption in data, in motion.
[11:45.740 --> 11:46.840]  Not too bad.
[11:46.860 --> 11:49.820]  What we're building, and I'm working with Arti Raman.
[11:49.820 --> 11:50.680]  It's absolutely amazing.
[11:50.680 --> 11:52.160]  She's over at Titanium IO.
[11:52.240 --> 11:54.520]  We're working with her on data in use.
[11:54.520 --> 11:56.560]  So encryption of data assets in use.
[11:56.560 --> 12:04.620]  So as that data is flowing in, we can actually leave it in an encrypted state and still take action upon it, which is freaking amazing.
[12:05.020 --> 12:06.360]  So, yeah.
[12:06.360 --> 12:08.000]  There's some cool tech we're doing.
[12:08.000 --> 12:10.240]  And, again, here's the fun thing about it.
[12:10.240 --> 12:15.120]  And I made this promise years and years ago, probably on live television, but I'll make it here and now.
[12:15.120 --> 12:23.240]  When we get to a point where, from a boom standpoint, that chassis is ready to be rolled somewhere, it's coming here.
[12:23.600 --> 12:29.240]  We're going to roll it out, open the doors and go, bug bounty, have at it.
[12:29.700 --> 12:34.460]  So any of you that want to have a poke of the stuff that we're building, I actively encourage you.
[12:34.460 --> 12:37.080]  Like, seriously, freaking actively encourage you.
[12:37.080 --> 12:39.420]  I think the crowd went actually down on their boots.
[12:40.780 --> 12:42.900]  I was getting clapped at the start.
[12:42.900 --> 12:49.140]  I mean, to have a manufacturer roll up on the platform and go, have at it, it's not very easy.
[12:49.640 --> 12:51.620]  So, A, looking forward to it.
[12:51.960 --> 12:53.860]  We're going to need a big boat for this.
[12:55.840 --> 12:59.240]  So, from that perspective, bug bounty and all that stuff is great.
[12:59.720 --> 13:03.900]  But, actually, you're also talking about doing things like digital twins and things like that as well.
[13:03.900 --> 13:05.860]  So you look after the life of the platform.
[13:07.080 --> 13:11.940]  How many of you are familiar with what a digital twin is?
[13:12.160 --> 13:13.440]  How many of you are not?
[13:14.000 --> 13:14.620]  Put a hand up.
[13:14.620 --> 13:15.100]  Awesome.
[13:15.100 --> 13:16.040]  So it's simple.
[13:17.400 --> 13:19.640]  I like people that don't know things.
[13:19.640 --> 13:26.420]  So, you take a physical engine, and this actually happens in the marine side of the world, like heavily in the marine side of the world as well.
[13:26.600 --> 13:28.940]  You take an engine, those darn things are expensive.
[13:28.960 --> 13:32.520]  You want to know when it's going to break before it breaks.
[13:32.520 --> 13:39.800]  In other words, if I'm going from London to Sydney, I want to know before it leaves London if there's a likelihood of it breaking before it gets to Sydney.
[13:39.800 --> 13:44.060]  Because I'm either going to swap it out, change it out, or I'll have a car waiting for me when it gets to Sydney.
[13:44.340 --> 13:52.760]  You can do that on the physical, but if you have a digital twin, it's basically a computer, 3D, 4D, multi-dimensional model of what that plane has gone through.
[13:52.760 --> 14:00.720]  The stresses, the heat, the systems, the cycles, the locations, all of that data is fed in from a metallurgy standpoint, a design standpoint.
[14:00.720 --> 14:02.780]  All of these things is fed into this plane.
[14:02.860 --> 14:06.380]  It's literally a digital version of a physical asset.
[14:06.380 --> 14:08.180]  It's gone through the same stresses .
[14:08.300 --> 14:13.900]  So we're building that, not just for the actual engines, but we're building it for as much of the system as humanly possible .
[14:13.900 --> 14:18.420]  Because now, the idea is , now we can get into the more predictive side of the world.
[14:18.420 --> 14:25.040]  In other words, if it's going over the Arctic more than it's going over a sandbox, is a widget likely to change and fail more often?
[14:25.040 --> 14:26.640]  Is something else likely to happen?
[14:26.640 --> 14:28.820]  Are the passengers likely to be affected more?
[14:28.820 --> 14:31.100]  So you start building the relationships.
[14:31.100 --> 14:38.340]  For those of you who build relational architectures in thread intelligence, say, you build strong and weak relationships between each one of these systems.
[14:38.340 --> 14:43.560]  You basically throw an intelligence model at it and go, tell me when this bloody thing's gonna break.
[14:43.560 --> 14:45.980]  You do that for everything, including atmospherics.
[14:46.080 --> 14:55.740]  I'm building an atmospherics engine in, so I know what I'm likely to be flying through, pulling it out of nowhere and going, hey, how does that affect my digital twin on this route versus this time?
[14:55.740 --> 14:59.520]  And you build a model, and then you go, right, now tell me when the thing's gonna break.
[14:59.520 --> 15:00.780]  I think I rely on the computer.
[15:00.780 --> 15:08.540]  So we've noticed with the innovation of a long time, like ART, or the YMCA, for that matter, it uses something called the T-index.
[15:08.540 --> 15:11.380]  It still happens, but everybody's got an ART that has a T-index.
[15:11.600 --> 15:20.220]  And the way that they used to check, and I will use it a bit more, is to go try to rapidly give that wing lots to do over a short period of time.
[15:20.220 --> 15:26.940]  So they used to build a graph, full size, and then basically flex it, put it as far as they wanted it to go.
[15:26.940 --> 15:32.120]  So the same thing they did with ART, 10,000 bootflexes for each stack.
[15:32.240 --> 15:38.240]  That then gave them their buffer, their graph, and they had 5,000 bootflexes for each wing.
[15:38.240 --> 15:42.380]  That's how a lot of the same problems with stability and innovation can be reduced.
[15:43.320 --> 15:46.060]  It didn't use to be as much stability as that.
[15:46.360 --> 15:48.160]  Oh yeah, absolutely, yeah.
[15:48.160 --> 15:57.920]  And the nice thing about it is, is we use 60, 70 million core hours of HPC compute at the moment for the flight.
[15:57.920 --> 16:05.220]  You can throw this stuff at that and tell, and you can say, hey, if I fly this route, give me the predictive analytics as to basically when it's going to fail.
[16:05.220 --> 16:06.560]  It's beautiful.
[16:08.260 --> 16:08.700]  So...
[16:08.700 --> 16:09.160]  ...
[16:11.900 --> 16:12.340]  ...
[16:13.400 --> 16:13.840]  ...
[16:17.080 --> 16:17.520]  ...
[16:17.520 --> 16:18.020]  ...
[16:20.580 --> 16:21.020]  ...
[16:21.020 --> 16:21.840]  ...
[16:23.740 --> 16:24.260]  ...
[16:25.000 --> 16:25.520]  ...
[16:30.260 --> 16:30.780]  ...
[16:31.380 --> 16:31.900]  ...
[16:33.300 --> 16:33.820]  ...
[16:35.500 --> 16:41.780]  I think if we take the entire journey, for so many years, I was focused on the technology.
[16:41.860 --> 16:44.320]  For so many years, it was chased with technology.
[16:44.320 --> 16:48.600]  I didn't take that step back and go, how do I communicate that effectively?
[16:48.600 --> 16:49.240]  I mean, let's face it.
[16:49.240 --> 16:50.460]  We all know what happened.
[16:50.980 --> 16:54.520]  I didn't... I thought I communicated effectively and efficiently.
[16:54.520 --> 16:55.980]  It's obvious it didn't happen.
[16:55.980 --> 16:59.520]  It's obvious that two-way communication failed and failed miserably.
[16:59.640 --> 17:00.560]  No blame anywhere.
[17:00.560 --> 17:01.500]  It happened.
[17:01.860 --> 17:05.280]  The learning lesson there is we have to do a better job.
[17:05.280 --> 17:05.820]  Both teams.
[17:05.820 --> 17:06.300]  Both sides.
[17:06.300 --> 17:07.260]  I'm now on the other side.
[17:07.260 --> 17:10.700]  I'm actually researching my own stuff and still researching stuff in there.
[17:10.880 --> 17:12.300]  But I now have to look at it.
[17:12.300 --> 17:12.960]  We had somebody.
[17:12.960 --> 17:16.460]  Somebody hit me up the other day and said, hey, I found a vulnerability in the site.
[17:16.460 --> 17:17.060]  I'm like, brilliant.
[17:17.060 --> 17:18.160]  Tell me about it.
[17:18.540 --> 17:22.680]  I don't have a formal panel room, but tell me about it and I'll figure out a way to say thank you.
[17:23.000 --> 17:25.080]  And so I think a lot of it is communication.
[17:25.080 --> 17:28.440]  And a lot of it now, thankfully, is down to collaboration.
[17:28.560 --> 17:33.640]  This whole area is freaking amazing because it's collaborative.
[17:34.200 --> 17:35.700]  It's not adversarial.
[17:35.900 --> 17:37.580]  These are people sitting here and talking.
[17:37.580 --> 17:42.700]  For those of you that follow me on LinkedIn, I put a post out last evening.
[17:42.740 --> 17:43.640]  And you'll see it.
[17:43.640 --> 17:44.940]  It talks about a handshake.
[17:44.980 --> 17:48.900]  It talks about a very, very special handshake that happened yesterday.
[17:49.040 --> 17:50.160]  That's here.
[17:50.460 --> 17:52.260]  And so we have the collaboration.
[17:52.260 --> 17:53.540]  We have the cooperation.
[17:53.540 --> 17:54.520]  Now we've got to coordinate.
[17:54.520 --> 17:55.800]  I think that's the big one.
[17:55.800 --> 17:59.360]  My former younger self is how do we coordinate more efficiently?
[17:59.740 --> 18:01.100]  That's one of the big ones.
[18:01.100 --> 18:02.880]  I mean, we all know to ask the questions.
[18:02.880 --> 18:03.780]  We all know to learn.
[18:03.780 --> 18:05.780]  We all know to investigate stuff.
[18:05.780 --> 18:14.380]  But it's how do I take that information and basically use it and share it in a way that everybody benefits rather than turning the adversarial side.
[18:14.380 --> 18:15.380]  I mean, it's rough.
[18:15.560 --> 18:18.620]  I'd probably also say, hey, you know, land and then tweet.
[18:18.620 --> 18:20.940]  That would be the one thing if I was still allowed on Twitter.
[18:20.940 --> 18:21.500]  But I'm not.
[18:21.500 --> 18:23.040]  So that's a different conversation.
[18:23.800 --> 18:25.080]  You know, there's life.
[18:26.380 --> 18:30.140]  I just want to say, it's really, really great to be here.
[18:30.140 --> 18:31.720]  Absolutely chuffed to be here.
[18:32.160 --> 18:33.400]  Long overdue.
[18:33.980 --> 18:36.020]  And as you say, completely separate that.
[18:36.140 --> 18:39.500]  Collaboration, working together, and then building trust.
[18:39.500 --> 18:42.740]  Because everything you're doing in your platform is all about building trust in the platform.
[18:42.740 --> 18:43.660]  Oh yeah, absolutely.
[18:43.660 --> 18:45.980]  No matter what threat that's here, it's building trust in the platform.
[18:46.160 --> 18:53.780]  Which is completely chimes with the village and all the amazing communities we've got in the village and doing all this stuff next to them.
[18:53.780 --> 18:54.340]  Totally.
[18:54.340 --> 18:54.960]  Thank you.
[18:55.240 --> 18:56.520]  Absolutely appreciate it.
[18:56.520 --> 18:58.060]  Thank you so much for coming.
[18:58.180 --> 18:59.360]  This was good.
[18:59.500 --> 19:03.060]  We'll be back for questions as we go through.
[19:03.260 --> 19:10.380]  Please see this as a re-start, as another addition to getting back in and learning where to go.
[19:10.380 --> 19:10.960]  Totally.
[19:10.960 --> 19:13.600]  Hopefully next year I'll bring more than just Boomstickers.
[19:15.140 --> 19:18.360]  Yeah, we're not bringing alcohol here again.
[19:18.360 --> 19:19.580]  Sorry on the Goon side.
[19:19.580 --> 19:20.560]  Like, seriously, sorry.
[19:20.560 --> 19:22.060]  Did not mean to get yelled at.
[19:22.640 --> 19:23.420]  Fish.
[19:24.900 --> 19:27.080]  Thank you very much.
[19:27.300 --> 19:28.140]  Good to talk to you.
[19:28.140 --> 19:31.960]  It's a pleasure to be back for the first panel of the day.
[19:31.960 --> 19:36.760]  Up next is myself, where you can see the founders of Village.
[19:36.800 --> 19:40.680]  And we're going to talk about how Earth came up here.
[19:40.740 --> 19:45.620]  Some of the lessons that we received about trying to get off the ground.
[19:45.620 --> 19:48.880]  And also some of the music stories that have not been recorded.
[19:48.880 --> 19:50.400]  And then we can release it for everyone.
[19:50.920 --> 19:54.540]  So yeah, certainly looking forward to conversations with you.
[19:54.540 --> 19:55.660]  Thank you guys so much.