[00:02.600 --> 00:09.380]  Welcome to Space Security Challenge 2020, HackASAT, the final event. As the democratization
[00:09.380 --> 00:14.860]  of space opens up a new frontier for exploration and innovation, we see new cybersecurity
[00:14.860 --> 00:21.480]  vulnerabilities emerging. The Space Security Challenge is designed to inspire the world's
[00:21.480 --> 00:27.180]  top cybersecurity talent to develop the skills necessary to secure this last frontier of
[00:27.180 --> 00:35.160]  cybersecurity, space. And already we've made a ton of progress. I'll catch you up. This spring,
[00:35.160 --> 00:40.180]  we hosted over 2,000 teams who worked their way through a set of foundational space cybersecurity
[00:40.180 --> 00:46.600]  challenges in our HackASAT qualification round. Now, eight finalist teams are stepping up to
[00:46.600 --> 01:00.930]  the ultimate challenge. They are hacking a satellite. Welcome to Space Security Challenge
[01:00.930 --> 01:07.310]  2020, or HackASAT. I'm your host, Jordan Wines, and I'm very excited to be with you today. I'm here
[01:07.310 --> 01:13.190]  in Melbourne, Florida at HackASAT HQ, where eight satellites are spinning out of control as the
[01:13.190 --> 01:20.570]  teams do their best to restore functionality, all for a piece of a $100,000 prize pool.
[01:20.570 --> 01:25.510]  These teams from 11 different countries around the world include not only some that are very
[01:25.510 --> 01:31.010]  familiar to those of us from the Capture the Flag, or CTF community, but also include many
[01:31.010 --> 01:36.190]  newcomers who assembled just to answer the call for HackASAT. Let's meet our teams.
[02:17.570 --> 02:23.590]  To get to this final event, individuals on these eight teams had to beat out over 6,000 other
[02:23.590 --> 02:29.310]  competitors for a coveted invitation. This required mastery not only in traditional CTF hacking skills
[02:29.310 --> 02:35.310]  like reverse engineering and vulnerability research, but also in areas new to the CTF community,
[02:35.310 --> 02:41.910]  including orbital mechanics, astrophysics, space-based communication systems, and many others.
[02:41.910 --> 02:47.330]  Today and tomorrow, each of our eight teams will race the others through a series of challenges
[02:47.330 --> 02:53.150]  to regain control over their Flatsat. If you followed our story at HackASAT.com
[02:53.150 --> 03:00.170]  and Launch.com.com, you might know that through some bad code and poor business choices,
[03:00.170 --> 03:05.670]  our defunct Launch.com company has accidentally triggered a satellite intended for the year 2000
[03:05.670 --> 03:11.870]  to be launched in 2020 with no one in control. In our fictional storyline, this satellite has
[03:11.870 --> 03:16.550]  been co-opted by nefarious forces, and it's up to our competitors to regain control over
[03:16.550 --> 03:21.950]  the many components. Since qualifying, each team was shipped a physical Flatsat,
[03:21.950 --> 03:27.270]  and these Flatsats are not only prizes for their qualifying performance, but also allow the teams
[03:27.270 --> 03:32.550]  to become familiar with the hardware and software before this final event. So what's the difference
[03:32.550 --> 03:38.090]  between a satellite and a Flatsat? Think of a Flatsat as a bench version for testing components
[03:38.090 --> 03:43.490]  of an actual satellite without necessarily being exactly what you would send into space.
[03:43.490 --> 03:48.850]  The satellites you can watch in our live webcams are Flatsats. But don't worry,
[03:48.850 --> 03:54.090]  not all of the competition this weekend will be terrestrial. The game has actually been underway
[03:54.090 --> 03:59.490]  for one hour now, and our team's first challenge has been to regain control of the ground station
[03:59.490 --> 04:04.650]  that they'll be using to communicate with their Flatsats. Being good hackers, of course, we call
[04:04.650 --> 04:13.350]  this Challenge Zero. Challenge Zero. Here's what we know. An adversary has obtained access to the
[04:13.350 --> 04:19.930]  satellite's ground station. Once they obtained access, they kicked us out. The challenge? Teams must
[04:19.930 --> 04:32.560]  obtain network access to the ground station. This is called Challenge Zero because it's required for
[04:32.560 --> 04:38.440]  the teams to even kick the game off. While most of our challenges will have teams focusing on
[04:38.440 --> 04:43.400]  components that are inside of their Flatsats, Challenge Zero is all about gaining access to
[04:43.400 --> 04:48.200]  the ground station that they'll be using to communicate with their Flatsat. And again, this
[04:48.200 --> 04:52.680]  is not a simulation. All of these eight Flatsats may be here on Earth, but they're completely
[04:53.260 --> 04:57.940]  untethered, floating on a cushion of air, and each one being connected wirelessly from a separate
[04:57.940 --> 05:03.840]  radio link. In the first hour of gameplay, teams have been getting their bearings and working on
[05:03.840 --> 05:09.660]  solving Challenge Zero. In fact, just before this broadcast went live, we received word that this
[05:09.660 --> 05:15.440]  challenge was actually solved by Team Samurai. Congratulations to them. Let's go ahead and see
[05:15.700 --> 05:51.070]  a little bit more about Team Samurai. Team Samurai is a mainstay in the CTF community. In fact, one
[05:51.070 --> 05:55.950]  of the fun facts about this community is that I've competed against Samurai about as many times as
[05:55.950 --> 06:00.470]  I've actually competed with them. This community is tight-knit, people move around between them,
[06:00.470 --> 06:05.350]  and it's good to see them jump into the lead and take a start on the scoreboard. They're now going
[06:05.350 --> 06:09.410]  to be focusing on Challenge One, which we're going to give you a little bit of a hint on what that
[06:09.410 --> 06:17.510]  entails now. Challenge number one. Here's what we know. Having access to the ground station means we
[06:17.510 --> 06:21.890]  can attempt communication, but the satellite is spinning out of control, which complicates
[06:21.890 --> 06:27.170]  everything. The challenge. Teams must regain communication with the satellite.
[06:37.490 --> 06:42.370]  While this event was originally planned to be in person during DEFCON in the
[06:42.370 --> 06:47.590]  Aerospace Village, thanks to the tireless efforts of dozens of people involved behind the scenes,
[06:47.590 --> 06:52.690]  we're instead streaming to you live throughout the event. Not only has the game itself been adapted
[06:52.690 --> 06:58.010]  to allow for remote participation from our eight teams over VPN, but the spectator experience has
[06:58.010 --> 07:03.950]  changed as well. There are many different ways you can now experience HackASAT. For a simpler
[07:03.950 --> 07:10.050]  interface, just visit hackasat.com with a web-based scoreboard, these periodic live updates streamed
[07:10.050 --> 07:17.070]  and links to other resources. For a more immersive experience, head over to virtual.hackasat.com
[07:17.070 --> 07:21.950]  where you can get all of the above and more, including watching our satellites live via one
[07:21.950 --> 07:28.290]  of four dedicated webcam feeds, get more technical game data from the 3D octagon scoreboard, as well
[07:28.290 --> 07:33.530]  as many other resources about our competitors, the flatsats, the technologies involved in space,
[07:33.530 --> 07:38.390]  and even communicate with other viewers in a dedicated chat and have a few social interactions.
[07:38.390 --> 07:42.830]  No need to remember all that just now though, all you have to remember is that you can find it all
[07:42.830 --> 07:49.330]  on hackasat.com and virtual.hackasat.com. The HackASAT team is also partnering with the
[07:49.330 --> 07:53.990]  Aerospace Village, one of the many villages you'd normally get to experience in person at DEF CON.