WEBVTT

00:01.110 --> 00:05.330
Challenge 3 Here's what we know.

00:05.330 --> 00:09.350
With the update to the ADCS, the teams have regained control of the satellite.

00:09.350 --> 00:13.350
But we still can't communicate with the payload module or operate the imager.

00:13.390 --> 00:17.990
In addition, the majority of useful commands are not being accepted by the flight software.

00:17.990 --> 00:21.510
We have to ask ourselves, what else did they damage on this satellite?

00:21.610 --> 00:22.630
The challenge?

00:22.630 --> 00:27.190
Teams must restore communication with the payload module so we can get it working again.

00:27.490 --> 00:28.930
Here's how they do it.

00:28.930 --> 00:34.870
The teams find that their initial commands to communicate with the payload module are not being accepted by the flight software.

00:35.030 --> 00:40.330
It's clear that the command and data handling C&DH system is not working appropriately.

00:40.330 --> 00:46.830
In fact, payload commands, and the majority of the other commands, have been disabled in the C&DH system.

00:47.010 --> 00:54.470
It turns out the attacker has modified the C&DH flight software and are now running their own code on board the space vehicle.

00:54.570 --> 01:02.850
The attacker code is rejecting the majority of commands to the satellite including firmware updates, firmware restore, and ADCS commands.

01:02.850 --> 01:08.490
As a result, it is not possible to restore the failsafe image as the restore command has been disabled.

01:09.210 --> 01:15.750
Lucky for the teams, the attacker was sloppy and inadvertently introduced a vulnerability in the new firmware image.

01:15.750 --> 01:23.390
Teams exploit this vulnerability and use it to repair the system and restore the C&DH software back to normal operation.

01:23.450 --> 01:27.790
Once that is complete, they are able to communicate with the payload module once again.