1
00:00:00,900 --> 00:00:11,380
Yesterday, our teams collectively worked their way through Challenges 0 through 2, leaving with half of the challenges solved by at least one team, and three challenges remaining to be solved today.

2
00:00:11,920 --> 00:00:18,060
PFS grew their lead throughout the day yesterday, but the biggest drama occurred after hours.

3
00:00:18,060 --> 00:00:19,000
When the 4 p.m.

4
00:00:19,000 --> 00:00:25,780
Pacific deadline for the On Orbit Challenge passed, only four teams had submitted solutions deemed acceptable.

5
00:00:25,780 --> 00:00:27,620
What's an acceptable solution?

6
00:00:28,860 --> 00:00:31,760
Let's take a look at solving the On Orbit Challenge.

7
00:00:31,940 --> 00:00:34,380
First, some terms you'll want to know.

8
00:00:34,640 --> 00:00:36,860
Two-line element set, or TLE.

9
00:00:37,000 --> 00:00:42,620
A data format containing information about an object's position and velocity at a specific point in time.

10
00:00:42,620 --> 00:00:48,740
It is used to calculate where a satellite will be at some point in the future, with increasing uncertainty the further out in time.

11
00:00:48,740 --> 00:00:50,400
Window of opportunity.

12
00:00:50,560 --> 00:00:55,260
The period of time during which the satellite can be positioned to complete the desired goal.

13
00:00:55,260 --> 00:00:56,740
Vector.

14
00:00:56,740 --> 00:01:00,000
A line indicating a specific direction in magnitude.

15
00:01:00,160 --> 00:01:07,260
A satellite will have assigned X, Y, and Z vectors associated with the body of the vehicle that can be used in a coordinate system.

16
00:01:07,260 --> 00:01:14,420
Camera boresight, camera mounting position, and camera body vector all describe the satellite camera and where it's pointed.

17
00:01:14,520 --> 00:01:15,460
Quaternion.

18
00:01:15,460 --> 00:01:19,180
A number system that is handy for calculating 3D rotations.

19
00:01:19,640 --> 00:01:20,600
Got it?

20
00:01:20,600 --> 00:01:21,660
Here we go.

21
00:01:21,660 --> 00:01:24,300
The first step in solving the on-orbit challenge.

22
00:01:24,320 --> 00:01:26,040
Identify the key data.

23
00:01:26,080 --> 00:01:34,100
The TLE, camera mounting position, target, and window of opportunity are all supplied in the challenge description or the on-orbit handbook.

24
00:01:34,260 --> 00:01:39,380
The data is used to calculate the orbit of both the satellite and the moon toward the window of opportunity.

25
00:01:39,380 --> 00:01:43,340
And don't forget to grab the camera body vector, which will be needed later.

26
00:01:43,580 --> 00:01:44,740
The second step.

27
00:01:44,740 --> 00:01:49,020
Calculate the time of image by defining the relationship between these key vectors.

28
00:01:49,020 --> 00:01:50,100
1.

29
00:01:50,100 --> 00:01:54,800
Determine the satellite-to-moon vector, which points directly from the satellite towards the moon.

30
00:01:54,800 --> 00:01:55,340
2.

31
00:01:55,340 --> 00:02:00,060
Determine the nadir vector, which points directly from the satellite towards the center of the Earth.

32
00:02:00,060 --> 00:02:00,740
3.

33
00:02:00,740 --> 00:02:02,480
Determine the angle between 1.

34
00:02:02,480 --> 00:02:06,000
the satellite-to-moon vector and the nadir vector and 2.

35
00:02:06,000 --> 00:02:10,200
the angle between the satellite negative Z vector and the camera body vector.

36
00:02:10,200 --> 00:02:20,900
The instance when the difference between the two angles is minimized gives us the time of image, the moment along its orbit when the satellite will be in position to take our all-important moonshot.

37
00:02:21,840 --> 00:02:23,220
The third step.

38
00:02:23,220 --> 00:02:29,440
Calculate the attitude or the position within its orbit that the satellite must take for the camera to capture the image.

39
00:02:29,540 --> 00:02:32,760
This is accomplished by lots of math.

40
00:02:33,140 --> 00:02:38,600
Specifically, something called a direction cosine matrix, DCM, or rotation matrix.

41
00:02:38,600 --> 00:02:41,840
The DCM calculates a satellite attitude that points 1.

42
00:02:41,840 --> 00:02:44,320
the camera boresight to the moon and 2.

43
00:02:44,320 --> 00:02:50,440
the satellite's negative Z vector to Earth's center, which is the attitude needed to accomplish the goal.

44
00:02:50,940 --> 00:03:02,540
The DCM supplies us with a specific quaternion which, when uploaded and applied to the satellite's attitude determination and control system, ADCS, moves the satellite into the desired position.

45
00:03:02,540 --> 00:03:04,500
On to the final step.

46
00:03:04,500 --> 00:03:08,240
Apply all that information and get the image we're after.

47
00:03:08,780 --> 00:03:18,320
We take the time of image and back out the commands around it, giving the satellite enough time to apply the quaternion and be in position when it arrives at the window of opportunity.

48
00:03:18,340 --> 00:03:20,840
The proper order of commands would be as follows.

49
00:03:20,840 --> 00:03:31,460
Turn on the ADCS, slew to the commanded quaternion, turn the camera on, set the exposure time, capture the image, and finally, turn the camera off.

50
00:03:31,460 --> 00:03:32,600
That's it.

51
00:03:32,600 --> 00:03:34,160
Challenge accomplished.

52
00:03:34,700 --> 00:03:39,320
But what does all of this have to do with hacking and keeping our satellites secure?

53
00:03:39,400 --> 00:03:42,740
The on-orbit challenge was completed with full trust.

54
00:03:42,740 --> 00:03:47,480
Our satellites rely on data and sensors from multiple sources in order to complete an objective.

55
00:03:47,480 --> 00:03:51,480
The TLE that was provided relied on data from the satellite and ground stations.

56
00:03:51,480 --> 00:03:55,620
Authenticated communications were required to upload the proper command sequence.

57
00:03:55,620 --> 00:04:01,040
Trusted execution was required to process sensor and actuator data to close control loops.

58
00:04:01,040 --> 00:04:05,360
Secure onboard communications were required to carry out operations in orbit.

59
00:04:05,560 --> 00:04:21,000
We need security-focused people to help with these problems because just as much as it takes a team of people to strap explosives to a computer to get a satellite into orbit, it takes a team of people from both space and security communities to ensure that space remains a viable,

60
00:04:21,000 --> 00:04:22,500
usable resource.

61
00:04:24,640 --> 00:04:31,520
The four teams with successful on-orbit solutions during the time period were Poland Cannon to Space.

62
00:04:31,520 --> 00:04:34,620
In fact, theirs came well over an hour before anyone else's.

63
00:04:34,700 --> 00:04:46,280
ADD Vulcan, Flux Rocket Repeat, and Samurai all came in within about 10 minutes of each other within the last 15 minutes of that window.

64
00:04:46,600 --> 00:04:52,480
Remember, the on-orbit portion involves a team computing a mission plan for an actual satellite to take a picture of a moon.

65
00:04:52,480 --> 00:04:58,500
All acceptable solutions were evaluated and the most accurate solution submitted before the 4 p.m.

66
00:04:58,500 --> 00:05:02,460
deadline will be chosen to be sent into space into our orbiting satellite.

67
00:05:02,520 --> 00:05:06,730
We'll learn whose solution that was amongst those four later on today.

68
00:05:07,060 --> 00:05:10,920
As we entered into our overtime period after the 4 p.m.

69
00:05:10,920 --> 00:05:14,980
deadline yesterday, the alternate acceptance criteria kicked into play.

70
00:05:14,980 --> 00:05:17,640
While the four teams submitting before 4 p.m.

71
00:05:17,640 --> 00:05:25,100
were automatically eligible for their solution to be sent and automatically into prize eligibility, we had to get more teams available.

72
00:05:25,100 --> 00:05:26,800
The limit was six.

73
00:05:26,800 --> 00:05:32,620
This meant that two teams of the remaining four would be out of contention for the final prize pool.

74
00:05:32,880 --> 00:05:41,280
The four teams fighting for those two spots included PFS, 1553, 1064 Seabred, and Solarwine.

75
00:05:41,280 --> 00:05:48,480
1553 managed to submit a solution that was valid only three minutes after the deadline, quickly grabbing that fifth spot.

76
00:05:48,560 --> 00:05:54,680
That left PFS, 1064 Seabred, and Solarwine on the ropes for that last spot.

77
00:05:54,760 --> 00:06:04,540
PFS and 1064 Seabred were number one and number four on the scoreboard at that point, so no matter what happened, someone in contention for the podium would not be eligible.

78
00:06:04,540 --> 00:06:10,080
All of the contest organizers were on a shared video chat, waiting to see the results as they came in.

79
00:06:10,080 --> 00:06:18,400
1064 Seabred had what looked to be an extremely close solution that was just outside the acceptance criteria, and PFS didn't seem to be close.

80
00:06:18,400 --> 00:06:20,700
Then, at 7.48 p.m.

81
00:06:20,700 --> 00:06:22,980
Eastern, or 4.48 p.m.

82
00:06:22,980 --> 00:06:31,020
Pacific, PFS came in with a valid solution, just edging out 1064 Seabred and Solarwine on the list of on-orbit acceptance.

83
00:06:33,400 --> 00:06:39,280
Unfortunately, that means that 1064 Seabred and Solarwine are both ineligible for a spot on the podium.

84
00:06:39,280 --> 00:06:42,380
That said, they can still have an impact on the game.

85
00:06:42,440 --> 00:06:49,760
Either team scoring first blood will potentially change the number of available points left on the board for their competitors and impact the final result.

86
00:06:49,800 --> 00:06:58,720
It's sad to see two great teams out of contention for the prize pool, but they can still end up on the leaderboard from a points perspective and attain the associated bragging rights.

87
00:06:58,720 --> 00:07:03,400
In fact, let's go ahead and take a look at the scoreboard now in our live octagon feed.

88
00:07:04,340 --> 00:07:06,300
And they definitely haven't slowed down.

89
00:07:06,300 --> 00:07:10,600
You'll notice that Solarwine actually scored first blood on Challenge 3.

90
00:07:10,620 --> 00:07:13,560
Congratulations to them for the great work overnight.

91
00:07:13,700 --> 00:07:20,620
The pressure is now on the remaining teams to show that they made good use of the downtime as well to land Challenge 3.

92
00:07:20,620 --> 00:07:27,480
You can also see Flux Repeat Rocket scoring just before this broadcast with only a 5% reduction in total points.

93
00:07:27,480 --> 00:07:29,440
So that's a good amount of points for them.

94
00:07:29,760 --> 00:07:34,580
That means Solarwine and Flux Repeat Rocket are both moving on to Challenge 4.

95
00:08:00,330 --> 00:08:05,010
This is the first time we've seen Flux Repeat Rocket make a big move on the scoreboard.

96
00:08:05,010 --> 00:08:06,570
Let's check out their team bio.

97
00:08:36,200 --> 00:08:43,560
Like many of the combined CTF teams that we've seen here today, I have good memories of playing Hack Lou CTF.

98
00:08:43,560 --> 00:08:48,660
In fact, it's often the case that the competition participants are also organizers in other times.

99
00:08:48,660 --> 00:08:57,960
So one of those teams that makes up the composition of Flux Repeat Rocket, Flux Fingers, runs Hack Lou, which is another great CTF competition you should check out.

100
00:08:58,060 --> 00:08:59,720
What an exciting first day.

101
00:08:59,720 --> 00:09:04,420
I'm looking forward to seeing what happens today as our teams battle through these last few challenges.

102
00:09:04,420 --> 00:09:10,600
Come back and join us at our 10.50am Pacific, 1.50pm Eastern for our next competition update.