WEBVTT

00:05.910 --> 00:08.050
Welcome, DEF CON travelers.

00:08.050 --> 00:18.330
You found Ticketing to Takeoff, an airport hacking choose your own adventure, brought to you by the Aerospace Village at DEF CON.

00:18.330 --> 00:35.450
I'm Liz Wharton, Chief of Staff at Scythe, but today I will merely be your narrator, your guide, helping you through the decisions that have already been made because you've made and created and voted on this adventure.

00:35.450 --> 00:51.470
When we talk about airports and airport cybersecurity, and particularly when we talk about the aviation industry, cybersecurity in general, what we're forgetting is how far airlines and airports have come.

00:51.470 --> 01:06.870
That as we've become more digitized, as everything is connected, as air travel has grown, so has the threat landscape, and so has, well, the attacks, vulnerabilities, and the pieces that make up this adventure.

01:06.870 --> 01:29.170
Decisions that you've made from the time you leave your home to transportation to the airport, departures, decisions made during flight, arrival, transit to your destination, all provide, well, additional players and pieces, but additional threats and opportunities for bad actors.

01:29.170 --> 01:51.410
As the GAO noted in a recent report, that airlines and their IT infrastructure and their systems also provide opportunities for potential IT outage effects from planning the trip, reservations, frequent flyer systems, to check-in, to boarding, to at the airport,

01:51.410 --> 02:12.630
with the airline's mobile app, the airport kiosk, the check-in, the boarding, the baggage, the planes, the flight planning, the dispatch, all of these come together and have potential outage effects on, in some cases, systems that were not built nor designed for the amount of impact that they have.

02:12.650 --> 02:23.990
But when we look at the playing field for our adventure today, the attack surface, it's not bounded like you find in most, in fact, it's quite expansive.

02:24.190 --> 02:31.770
As you'll be traveling through our fictitious airports, you'll notice that, well, not everything is in the same place.

02:31.770 --> 02:34.870
Not every airport is designed differently.

02:34.890 --> 02:54.910
So to create and craft policies, procedures, all the different pieces that will go into what I hope you gain from today's conversation and, well, future conversations, is that airports and securing airports, be it the physical, the systems, the software,

02:54.910 --> 02:58.330
all of the pieces that come into play airports, is not easy.

02:58.370 --> 03:16.170
In fact, we may not even get through or scratch the surface of all the different parts because, well, who knows, between cyber squirrels and different choices that are made, you may not even get past, well, ticketing.

03:16.170 --> 03:21.070
Because within the airport attack surface, you also have a lot of players.

03:21.090 --> 03:29.830
You have from air traffic control to the many cities that airports truly are, to security, to your gate.

03:29.830 --> 03:31.510
It's a minefield.

03:32.090 --> 03:36.170
Protected and controlled by airlines themselves.

03:36.170 --> 03:39.030
Each of the airlines plays a part in this.

03:39.030 --> 03:58.850
The airport authorities, be it the local governments or other authorities, to the different, well, local law enforcement, to the FAA, DHS, security, concessions, vendors, the electricity, all the different telecommunication services that flow into each airport,

03:58.850 --> 04:01.550
well, those are a different provider.

04:01.550 --> 04:08.710
For example, at the Atlanta Airport, power is provided by Georgia Power under different agreements that have been put into place.

04:08.710 --> 04:18.810
So whether those provide opportunities for protection or vulnerabilities is open.

04:18.950 --> 04:23.990
Also, you have to look at the third-party providers, the multi-use software and systems.

04:23.990 --> 04:31.570
For example, Garmin recently provided a great example of, well, when we think of Garmin, what do we really think of?

04:31.570 --> 04:38.230
Do we think of the watch, the directions, you know, our tracking, our steps, etc.?

04:38.230 --> 04:56.810
Do we really think of the fact that Garmin provides aviation services, from flight planning to mapping, and that when a ransomware attack hits Garmin, that it's also impacting the avionics, the airport?

04:56.810 --> 05:07.830
And a shameless plug for a breakdown of the recent Garmin ransomware attack and attack factors, check out Threat Thursday in the notes.

05:08.710 --> 05:16.770
And when we're talking and weaving our narrative story today, we also have to look at what is the intent.

05:16.770 --> 05:28.830
That when we have incidents such as glitches, breaches, and, well, Agent Cyber Squirrel hitting airports, the intent and the result matter, but sometimes don't.

05:29.190 --> 05:40.530
Is chaos criminal carnage, or really is it just an oopsie that results in chaos, criminal activities, or carnage?

05:40.910 --> 05:44.590
And further, what are the incident impacts?

05:44.590 --> 05:55.950
That a power outage at Delta's operations center in August of 2016, $150 million and two days worth of cancellations.

05:55.950 --> 06:03.650
That a software glitch with one vendor provided worldwide check-in and booking issues.

06:03.650 --> 06:07.710
That a data breach results in fines at one airport.

06:07.710 --> 06:22.590
That a Southwest computer outage led to $177 million of damages and three days of outages and flight disruptions.

06:22.590 --> 06:29.030
All of these potentially could have been worse, and all of them, well, potential threats.

06:29.030 --> 06:33.230
So from ticketing to takeoff, it's going to be quite an adventure.

06:33.750 --> 06:35.150
Shall we begin?

06:36.550 --> 06:46.730
And beware and warning, because this talk is different from other talks, other technical talks, and other talks in the aerospace village.

06:46.730 --> 06:56.470
For in this talk, you and you alone, assuming you voted in the Twitter polls, are in charge of what happens.

06:56.930 --> 07:06.450
The mission was to see if you and your data can make it safely to your flight from ticketing to takeoff.

07:06.450 --> 07:10.490
You have to dodge the delays and the data breaches.

07:11.190 --> 07:13.890
And so, shall we begin?

07:13.890 --> 07:17.030
It's time to pack your things and head to the airport.

07:17.030 --> 07:20.390
And our first decision point...

07:20.390 --> 07:22.550
do you decide to pack it all?

07:22.550 --> 07:23.450
Check a bag?

07:23.450 --> 07:30.150
I mean, you're going to Vegas for a week for DEFCON and all of the other villages.

07:30.250 --> 07:33.210
Or do you bring a carry-on?

07:33.210 --> 07:35.470
Put everything in a bucket and see what happens.

07:35.470 --> 07:40.450
Well, you chose a carry-on.

07:40.670 --> 07:51.610
Wise move, because airline baggage check-in and tracking has the potential for delays, not to mention data breaches.

07:51.950 --> 07:58.210
So now that you've got your backpack on and you're about to head out, it's a digital and app world.

07:58.210 --> 08:00.590
Who even has a printer at home these days?

08:00.590 --> 08:04.770
So when it comes to your boarding pass and your ticket, do you print it at home?

08:04.890 --> 08:08.050
Do you use the airline's app boarding pass?

08:08.150 --> 08:11.290
Or, like me, I do a combination.

08:11.290 --> 08:15.810
I also take a screenshot of my boarding pass should something go wrong.

08:15.830 --> 08:20.410
Well, almost evenly split, but did you choose wisely?

08:20.410 --> 08:24.730
You chose to print your boarding pass at home.

08:24.770 --> 08:33.610
Well, well done, because ticketing frequently leads to, well, delays and data breaches.

08:34.450 --> 08:46.650
So now that you have your bags packed, your tickets in hand, and you're heading into the airport, you know that sometimes there are long lines at ticketing and check-in.

08:46.650 --> 08:53.750
And what if you want to switch your seat before you actually board the flight depending on what you see around you?

08:53.750 --> 09:00.190
So, DEFCON safe mode, secure aerospace travelers, what do you decide to do?

09:01.290 --> 09:19.030
Overwhelming majority, you chose to check in online with the 24-hour advance window, avoiding the kiosks, and, well, the airline app, because you know the check-ins are, well, the threat there are delays.

09:19.070 --> 09:34.350
So much so that when a third-party provider covers, well, most of the airlines, you see a 30-minute outage of their software can lead to three airlines going down.

09:35.110 --> 09:44.070
A couple days later, a different airport service provider covered five airlines in 40 minutes.

09:44.570 --> 09:54.410
Saver was at it again on April 29th, just less than a month later, 90 minutes, three airlines.

09:54.610 --> 10:06.110
So you've checked in online, you've shown up at the airport, and you're a seasoned road warrior, even if it seems like forever since, well, our last flight.

10:06.110 --> 10:10.130
Cutting it close to departure time, and it's a big airport.

10:10.210 --> 10:14.150
Flying on a weekday morning, bold move.

10:14.150 --> 10:16.130
Are you feeling lucky?

10:16.530 --> 10:25.730
So for decision for the fourth decision point, DEFCON safe mode, secure aerospace travelers, what did you decide to do?

10:25.730 --> 10:33.230
TSA pre-check, clear, or regular TSA security lines?

10:33.630 --> 10:46.290
Most of us seemed, most of you seem to be, well, hesitant with the facial recognition that comes with clear, but you're okay with providing some data and information because you're TSA pre-check.

10:46.370 --> 10:54.530
Well, what seems like a safe move could lead to delays and a data breach.

10:54.910 --> 10:57.750
Well, here's what happens.

10:57.750 --> 11:03.150
Is it security theater where you have moving parts and multiple players?

11:03.150 --> 11:05.870
Because when you have nationwide U.S.

11:05.870 --> 11:25.550
Customs computer outages causing gigantic lines at airports, you had JFK, LAX, SFO, Philadelphia, O'Hare, Midway, SeaTac, and other airports all confirming delays, our airport is probably hit by those.

11:25.730 --> 11:42.050
So not only do you have a delay with pre-check, but one of the recent trends has been for one provider to provide some of the software and systems support for TSA.

11:42.090 --> 11:56.630
In this case, facial recognition software provider and systems provider MEC well, pretty much covers European airports and most airports across the U.S.

11:56.810 --> 12:02.350
And while they take a long time to admit it, they've had a breach.

12:02.490 --> 12:08.070
The facial recognition data collected by U.S.

12:08.070 --> 12:08.730
airlines and U.S.

12:08.730 --> 12:19.450
citizens is stored for 12 hours, for between 12 hours and two weeks, and 75 years for non-U.S.

12:19.450 --> 12:20.250
citizens.

12:20.250 --> 12:29.570
And that data is stored in several government databases which border officials can pull up when you're arriving or leaving the U.S., including at airports.

12:30.270 --> 12:38.070
And well, MEC is not very good at confirming their security breaches or giving a lot of detail.

12:38.070 --> 12:47.390
So in this case, you didn't avoid the delays and you didn't avoid the data breach, but you made it through security.

12:47.630 --> 12:56.070
Because when you have these data breaches, well, quite frankly, what are you going to do?

12:56.490 --> 13:01.030
Well, worrying about that check-in and those security lines can be a headache.

13:01.030 --> 13:04.010
And of course, you forgot to pack your headphones.

13:04.030 --> 13:06.610
It's a long flight ahead of us to Vegas.

13:06.610 --> 13:11.790
So, DEF CON safe mode, secure aerospace travelers, do you?

13:11.930 --> 13:29.410
Well, stop what you're doing because you've got to have your headphones, noise-canceling headphones, and knowing your luck so far, there's probably going to be a screaming child or disruptive, I don't know, people.

13:29.430 --> 13:31.950
So, do you stop and buy them now?

13:32.010 --> 13:34.490
Or maybe we'll wait a little bit.

13:34.490 --> 13:39.830
If there's a place to buy some closer to the gate, sure, we'll go with that.

13:39.830 --> 13:42.910
Or quite frankly, you're feeling lucky.

13:42.910 --> 13:44.890
You're going to go for a roll the dice.

13:44.890 --> 13:46.710
And well, who cares?

13:47.930 --> 13:53.090
Well, a slight, slight, slight majority went with, who cares?

13:53.330 --> 13:57.990
You'll figure something out and you'll find a way to entertain yourself without your headphones.

13:58.290 --> 14:05.750
Which, when it comes to airport vendors and the threats of data breaches, probably wasn't a bad idea.

14:06.590 --> 14:10.970
So, now you've made it to decision point number six.

14:10.970 --> 14:16.330
Your departure gate is farther from the main terminal than you originally thought.

14:16.330 --> 14:19.350
It's time to move and get in those steps.

14:19.350 --> 14:23.010
But quite frankly, who wants to carry our bags that far?

14:23.010 --> 14:27.610
I mean, keeping in mind, we've got a carry-on and a backpack.

14:27.870 --> 14:36.390
And while, while we've got our traveling shoes on, we haven't been exercising quite as much during COVID.

14:36.390 --> 14:42.570
So, DEFCON safe mode, secure aerospace travelers, what do you want to do?

14:42.570 --> 14:44.590
Do you want to take the people mover?

14:44.590 --> 14:46.470
Take the airport train?

14:46.470 --> 14:50.010
Or, one, two step, let's walk there.

14:50.330 --> 14:53.770
And you chose to walk there.

14:53.770 --> 15:01.330
Which, while we're going to get in the steps and we're going to walk this way, we had a double whammy.

15:01.330 --> 15:07.150
Both delays as well as the dreaded agent cyber squirrel.

15:07.150 --> 15:09.890
Well, in this case, just an agent squirrel.

15:09.930 --> 15:19.850
Because LAX, on Thanksgiving Day 2015, had cyber squirrel reports, a squirrel plus a transformer.

15:19.850 --> 15:37.690
Which, in this case, while the power outages weren't severe in the surrounding area, at the airport you had the moving walkways, the elevators, the escalators, the screening equipment, the baggage screening equipment that just stopped.

15:37.830 --> 15:51.190
So, while none of the outages completely shut down the airport, well, for those of us trying to get our bags from security checkpoint to terminal, it's going to be a little bit of a long hike.

15:51.190 --> 15:55.130
All those speedy ways to get there are no longer at our advantage.

15:55.130 --> 15:58.810
Thanks to Captain Chaos, cyber squirrel.

16:00.110 --> 16:04.150
But, we finally made it to the gate area.

16:04.150 --> 16:07.950
And, well, decision point number seven.

16:08.330 --> 16:13.730
In this case, you know, beer pairs well with breakfast, right?

16:13.730 --> 16:22.270
We have had to deal with all kinds of different challenges and, well, there are no seats at the bar.

16:22.830 --> 16:31.050
The restaurant doesn't look too crowded and, well, a table it is, if that's what we want to do.

16:31.430 --> 16:35.390
So, DEFCON safe mode, secure aerospace travelers.

16:35.610 --> 16:37.910
What do we want to do?

16:38.250 --> 16:48.450
Do we, okay, take time, stop for one-on-one only because, well, again, beer pairs well with breakfast?

16:49.010 --> 16:55.390
Or, do we decide to wait a little bit because, quite frankly, we're in first class.

16:55.390 --> 16:58.810
Oh, did I mention we only travel first class?

16:58.810 --> 17:02.810
And first class has beer, even in the morning.

17:02.810 --> 17:23.270
And it looks like the majority of us, well, chose beer first class, not going to stop, which is not a bad thing because one of the other hidden hazards are the point-of-sale systems and the threats in restaurants of data breaches.

17:23.270 --> 17:27.670
Not only that, there's also a potential for delays.

17:27.850 --> 17:33.230
You don't know what systems the airport or restaurants at airports are running off of.

17:33.230 --> 17:44.070
Are they bringing in their own Wi-Fi network or are they piggybacking off of an airport facilities or nearby vendors or hers?

17:44.070 --> 17:50.590
Are they piggybacking off of, well, free airport Wi-Fi?

17:50.890 --> 17:52.890
That's not secure.

17:53.470 --> 17:56.450
But there's no rest for the wicked.

17:56.450 --> 18:19.170
And as we reach decision point eight, well, not only is there no rest for the wicked, there's no rest for travelers with laptops and deadlines because we don't get to fly first class and we're not heading to DEFCON unless we're big shots and we need to review a draft file and respond ASAP.

18:19.170 --> 18:25.970
So we pulled our laptop and DEFCON safe mode, secure aerospace travelers.

18:25.970 --> 18:27.450
What do we do next?

18:27.590 --> 18:31.230
Do we tether to our cell phone to connect for Wi-Fi?

18:31.430 --> 18:34.090
Do we use the airport's free Wi-Fi?

18:34.630 --> 18:39.450
Or do we carry a cell tower in our backpack?

18:39.450 --> 18:47.630
Because, you know, Wi-Fi pineapple and Wi-Fi cactus, they could have made it through airport security.

18:47.810 --> 18:49.630
So let's see.

18:49.630 --> 19:07.950
And while while we do miss the sights of pineapple Wi-Fi and cell towers in our backpack, the good thing is is our data coverage on our cell phone will allow us to tether to it.

19:07.970 --> 19:14.470
Which, tether not to free Wi-Fi because the threats there are data breaches.

19:16.290 --> 19:27.690
So as we've sat, we've reviewed our documents, and we're looking around, we've reached decision point number nine because storm clouds are gathering on the horizon.

19:27.870 --> 19:32.390
And we think, hmm, there may be potential flight delays.

19:32.430 --> 19:39.370
Locusts, storms, it's not winter, but still stranger things have happened.

19:39.410 --> 19:42.790
And what happens if we miss our connection?

19:43.050 --> 19:47.130
Luckily, the airline we're flying on has an app.

19:47.130 --> 19:51.470
We can see over in the distance that there's a counter.

19:51.470 --> 19:56.670
There's a little bit of a line at the counter, but not enough to deter us.

19:56.690 --> 19:58.530
So what are we going to do?

19:58.570 --> 20:09.870
One, are we going to face down the storm because as DEFCON safe mode airspace travelers, let's admit it, we are the storm.

20:10.250 --> 20:13.910
Do we use the airline's app and switch to a later flight?

20:13.910 --> 20:20.070
Or do we go up to the counter and talk to the person from the airline and attempt to rebook?

20:20.070 --> 20:45.350
In a slight, slight majority, we decide to go to the counter and rebook, which turns out to be probably a pretty good idea because airline ticketing systems and those apps both have delays because if the app is out or hasn't been developed, you have problems with data breaches.

20:45.350 --> 20:51.670
For example, EasyJet had 9 million travel records taken in a data breach.

20:51.870 --> 21:04.310
And the British Airways was fined a record 230 million dollars after a data breach exposed the booking details of over half a million customers.

21:04.390 --> 21:11.250
Hackers had siphoned off thousands of credit card numbers after installing skimming malware on its website.

21:11.250 --> 21:18.590
So it's a good thing we didn't go to the website or use the app because that would have been bad.

21:18.590 --> 21:28.550
Instead, we just talked to a live person which is daunting enough, but at least we're still on track for our flight.

21:29.450 --> 21:38.150
Yet, because check-in counters do have software glitches as well.

21:38.150 --> 22:00.570
And well, unfortunately, as highlighted the Greater Toronto Airports Authority, they had an outage with their airline check-in system that impacted processes at both Terminal 1, 3, and had IBM technicians working with the technology authority to solve the problem.

22:00.570 --> 22:04.370
So the fears aren't always just the airlines.

22:04.370 --> 22:09.150
You also have to look at, well, what happens with the airline authorities?

22:09.450 --> 22:13.950
And are they providing assistance?

22:13.950 --> 22:15.050
Can they have those handles?

22:15.050 --> 22:17.230
And what happens when their systems go down?

22:17.510 --> 22:25.590
In Toronto's case, if you had checked in online ahead of time, which we did, you would have been fine.

22:25.590 --> 22:28.310
But then what happens when you're trying to rebook?

22:28.310 --> 22:35.890
And if you're having checked baggage and having to move through the airport, it caused additional delays.

22:35.970 --> 22:45.210
So unfortunately in our journey, we've had the potential, we've avoided most of this data breach issues, but we've been delayed.

22:45.210 --> 22:49.350
Not enough to miss our flight, but we've been delayed slightly.

22:49.350 --> 22:53.050
Which leads us to, we finally get to our gate.

22:53.050 --> 22:57.610
We show up and it's decision number 10.

22:58.470 --> 22:59.950
Surprise!

23:01.010 --> 23:07.230
It's a gate change and it's a crowded and noisy terminal.

23:07.410 --> 23:18.930
And let's be honest, who can ever truly hear what the airline attendants are saying and when they're announcing where you're supposed to go?

23:18.930 --> 23:21.730
Because we didn't catch it.

23:21.730 --> 23:24.490
The PA system was terrible.

23:24.490 --> 23:27.730
Now, where did they move our flight?

23:27.730 --> 23:28.650
What gate?

23:28.650 --> 23:32.030
Is it even on the same terminal anymore?

23:32.030 --> 23:34.050
We need to find out.

23:34.270 --> 23:39.970
So DEFCON, safe mode, secure airspace travelers, what do we do?

23:39.970 --> 23:43.090
Do we check the nearby display screens?

23:43.170 --> 23:48.410
Do we go to the airline app, cross our fingers and hope that it's updated?

23:48.730 --> 23:51.150
Or do we ask a stranger nearby?

23:51.330 --> 23:53.330
We've already spoken to one person.

23:53.330 --> 23:55.730
We spoke at the counter.

23:55.730 --> 23:58.710
That's a lot of peopling for one day.

23:58.710 --> 24:02.890
So an overwhelming majority didn't trust the app.

24:02.890 --> 24:06.950
Instead, we chose to check the display screens.

24:07.250 --> 24:14.190
Well, gate display screens are one of the big areas for delays.

24:14.910 --> 24:17.090
What do we mean?

24:17.310 --> 24:20.490
You knew it was going to pop its head somewhere in the story.

24:20.490 --> 24:22.170
Well, ransomware.

24:22.170 --> 24:25.410
It's not just about taking down data.

24:25.590 --> 24:28.070
It takes down the systems as well.

24:28.070 --> 24:44.030
And in this case, the, well, Bristol airport got to find out exactly what that means when, in 2018, ransomware took out their signage with their gate information.

24:44.630 --> 24:51.490
Staff were left with having to hold up whiteboards directing people for where their flights are going.

24:51.490 --> 24:58.850
So in real time are having to take that information, write it out, and what happens when they start running out of whiteboard space?

24:58.850 --> 25:00.290
Well, they found out.

25:00.290 --> 25:01.590
It caused delays.

25:01.850 --> 25:07.590
So again, not a data breach because our data information isn't on those screens.

25:08.070 --> 25:11.170
But instead, it did cause a delay.

25:11.430 --> 25:15.370
We're cutting it awfully close to departure time, aren't we?

25:16.010 --> 25:21.150
Well, it's about time for boarding.

25:21.290 --> 25:24.270
And we're, we think we found where the right gate is.

25:24.270 --> 25:33.690
But at decision 11, hmm, what happens when the direction that we go?

25:33.690 --> 25:36.650
I mean, we can either go right or left.

25:36.650 --> 25:38.850
And we're savvy travelers.

25:38.850 --> 25:44.070
And while our frustrations are mounting, we're not going to panic.

25:44.070 --> 25:47.390
No, instead, DEFCON safe mode.

25:47.390 --> 25:49.410
Secure aerospace travelers.

25:49.610 --> 25:51.630
What do we decide to do?

25:51.790 --> 25:53.450
We can risk it.

25:53.450 --> 25:54.270
Go left.

25:54.270 --> 25:55.990
If it's wrong, we'll go right.

25:56.530 --> 26:04.830
Well, turns out the airport has its own app that, of course, while we're bored, we downloaded it.

26:04.830 --> 26:11.490
And, hmm, we can talk about whether to download stuff to our cell phone without properly vetting.

26:11.590 --> 26:14.310
But it also has a navigation feature.

26:14.310 --> 26:16.510
We want to choose that.

26:16.890 --> 26:25.990
Then again, we think about the issues with Garmin and all the other, well, where's our app data being sent?

26:25.990 --> 26:28.330
Where's our location data being sent?

26:28.870 --> 26:31.210
So, maybe we're not going to go there.

26:31.810 --> 26:39.910
And while we know some of the signage in the airport is out, surely not all of the signage is out.

26:39.910 --> 26:47.450
I mean, we can check the digital directory signs because, you know, they're running on a different system, aren't they?

26:47.930 --> 26:49.330
Spoiler alert.

26:49.330 --> 26:51.690
Most of the time, no.

26:51.810 --> 27:10.490
And the other thing is there's hidden dangers with the directory signs as well because, let's think of, think back to, oh, I don't know, some of the botnets, like the Mirai botnet that liked target IoT devices.

27:10.710 --> 27:16.070
Those LG screens you see all around the airport, what are those?

27:16.070 --> 27:19.770
But, waiting, danger, waiting to happen.

27:19.990 --> 27:22.630
In this case, we're going to risk it.

27:22.630 --> 27:24.250
We're not going to panic.

27:24.250 --> 27:30.810
We're going to check those digital directory signs because surely, surely, they're not all out again.

27:30.810 --> 27:49.510
Well, get ready for delays again because ransomware has hit multiple airports again, impacting the digital signage around the airport, displaying, again, only back black screens.

27:49.510 --> 28:02.250
Cleveland Hopkins International had this happen in April 2019, you know, back when people flew still, and took out their computing systems as well.

28:02.250 --> 28:11.010
So, like that, you had to worry about whether their email, their internal app, their internal direction, if they're able to get some of the information out of it.

28:11.010 --> 28:19.510
So, once again, wasn't our data that we were worried about as much here, but our ability to catch our flight.

28:19.510 --> 28:28.330
We're getting really delayed here, which leads us to, okay, we finally found the right direction.

28:28.330 --> 28:29.470
We're heading there.

28:29.470 --> 28:31.230
We're almost there.

28:31.330 --> 28:36.830
We skipped that beer because there was going to be some of that on first class.

28:37.090 --> 28:44.250
So, we're walking by the newsstand and we spot the bestseller Burnin book, and we've been meaning to read it.

28:44.250 --> 29:00.930
I mean, Honest Cole and Peter Swinger did a great job, we heard, in bringing and predicting all of these IoT connected smart city, and one of my favorite, drone issues.

29:00.930 --> 29:10.430
And, well, we heard that lawyers get the short end of the stick, and this, and who doesn't like to see bad things happen to lawyers?

29:11.110 --> 29:16.230
So, DEF CON safe mode, secure airspace travelers, what are we going to do?

29:16.350 --> 29:28.130
Are we going to stop, get a book, and, oh wait, look, there's a sign at checkout that says, if you pay via this payment app, you'll get a free coffee.

29:28.350 --> 29:29.850
So, we didn't have a beer.

29:29.850 --> 29:31.510
Who doesn't want a free coffee?

29:31.890 --> 29:37.310
So, do we decide to go for the coffee, or buy the book, skip the coffee?

29:37.310 --> 29:39.930
We don't need another frequent shopper card.

29:39.930 --> 29:41.610
We don't need another stamp.

29:41.690 --> 29:46.450
Then again, it's on our business credit card, so who cares?

29:46.450 --> 29:47.530
I would never do that.

29:47.530 --> 29:48.810
I would never pick that one.

29:48.810 --> 29:53.490
But, for the purposes of our narration, who cares?

29:53.490 --> 29:55.110
It's the company's card.

29:55.110 --> 29:58.530
The data gets stolen, not our problem.

29:58.710 --> 30:04.150
Well, luckily, you chose to buy the book and skip the coffee.

30:04.210 --> 30:10.890
Solid choice, an excellent read, especially considering, well, you didn't pick up the headphones.

30:10.890 --> 30:19.990
Because again, the payment systems in the shops are notorious for data breaches, as well as, well, best practices.

30:20.270 --> 30:30.790
And with those third-party payment apps and different things, even within the airports, you've had currency exchanges go down to different attacks.

30:30.790 --> 30:36.870
So, okay, we finally made it to the gate.

30:36.930 --> 30:41.050
And well, we've made its decision, lucky 13.

30:41.050 --> 30:46.430
We've grabbed a seat in the boarding area, and we noticed that our cell phone battery is really low.

30:46.430 --> 30:53.210
I mean, we tethered it so that we could send and review those documents and those files.

30:53.570 --> 30:58.410
And well, how are we going to tweet and text from the flight?

30:58.810 --> 31:05.290
So, savvy DEF CON safe mode aerospace travelers, what are we going to do?

31:05.910 --> 31:15.030
Use the extra charger you're carrying in your backpack, because while you're not carrying a cell phone tower, well, you do know to pack an extra charger.

31:15.330 --> 31:17.810
Do we wait?

31:17.810 --> 31:18.350
Risk it?

31:18.350 --> 31:32.090
Because we are first class, and as we know from flying first class frequently, there's chargers, or there's outlets, and there's our free beer.

31:32.290 --> 31:41.830
Or do we go and find an outfit, or excuse me, an outlet, because quite frankly, you never know.

31:41.830 --> 31:52.990
And again, tweeting, how else are we going to show people that we're sitting in first class if we can't tweet a picture of us sitting in first class holding our free beer?

31:53.390 --> 31:57.290
Well, charging devices.

31:57.510 --> 32:10.470
Well, in this case, we're going to fall victim to Agent Cyber Squirrel, because Agent Cyber Squirrel, Captain Chaos, likes to cause brief power outages.

32:10.470 --> 32:20.910
And again, in this case, it was by Buffalo Niagara Falls or Niagara International Airport, caused a brief power outage.

32:20.910 --> 32:24.850
It affected gates, well, a select number of gates.

32:24.850 --> 32:28.310
It only caused one flight to be delayed for a few minutes.

32:28.390 --> 32:35.610
But in this case, luckily, we had our charger with us.

32:35.610 --> 32:49.130
So while Agent Squirrel caused a power outage at our gate, again, he didn't cause us to have any issues because our backup charger was fully charged.

32:49.290 --> 32:52.990
Well, decision time.

32:52.990 --> 32:58.090
It's finally, the gate agent is calling our flight.

32:58.090 --> 33:04.310
And don't forget, we're first class, because that's how we roll.

33:04.310 --> 33:08.150
And with first class, we're the first ones to board.

33:08.710 --> 33:17.650
But we notice, oh lovely, the airline is testing facial recognition for the boarding process.

33:17.650 --> 33:21.470
And you notice the line is piling up.

33:21.690 --> 33:24.370
So what are we going to do?

33:24.370 --> 33:26.530
We've made it this far.

33:26.530 --> 33:30.190
We have really got it close.

33:30.190 --> 33:33.070
And quite frankly, we're tired.

33:33.230 --> 33:37.890
So weary DEFCON safe mode, secure aerospace travelers.

33:38.430 --> 33:40.890
What do you decide to do?

33:41.250 --> 33:43.110
Do you opt out?

33:43.110 --> 33:49.890
Because you've heard all those stories about facial recognition and you know that a lot of those algorithms are wrong.

33:49.890 --> 33:54.610
And that's not to get into, well quite frankly, it's just an affront.

33:54.610 --> 33:58.450
You're not looking picture perfect right now.

33:58.830 --> 34:00.750
Eh, might as well.

34:00.750 --> 34:08.050
If it's going to keep the boarding process moving, and if it's going to be convenient, sure.

34:08.330 --> 34:18.510
But we did get that new AI facial recognition defeating tattoo and makeup.

34:18.510 --> 34:26.150
And while it was funny going through security, we're so close to boarding our flight.

34:26.290 --> 34:39.490
In this case, you decided stand up on principle and no, we're going to opt out and use the paper boarding pass.

34:39.490 --> 34:51.970
Well, not only does facial recognition at the gates and also throughout the airports with ticketing cause data breaches.

34:52.170 --> 34:53.730
And what happens?

34:53.730 --> 34:59.230
Are you going to get a new news job because your information, your biometrics are out there?

34:59.450 --> 35:02.170
It also causes delays.

35:02.390 --> 35:09.830
So you can opt out, but that's opting into wait and wait and wait.

35:09.830 --> 35:18.490
Because as we've learned through several different approaches, that yeah, you can opt out.

35:18.830 --> 35:25.090
And Zach Whitaker has a whole article from May 2019 that walks you through it.

35:25.090 --> 35:40.930
But know that opting out means they're going to go manual so that the airline staff will manually check your passport or boarding pass like they would normally do when you're boarding a plane.

35:40.930 --> 35:49.970
That also means you've got to sit to the side and everyone else who's going through the facial recognition is probably going to bump up ahead of you.

35:49.970 --> 35:56.850
So what's the point of having our first class perks if we're going to sit to the side?

35:56.850 --> 36:03.610
Well, that's assuming the facial recognition technology and equipment is even working.

36:03.610 --> 36:15.230
Because according to one of the watchdog groups, the facial recognition systems at airports only worked 85 percent in some cases.

36:15.370 --> 36:19.710
And quite frankly, we've got that new face tattoo.

36:20.050 --> 36:29.370
And well, all those delays and delays and delays were waiting and waiting and waiting.

36:29.390 --> 36:45.910
Well, and that's okay because quite frankly, we still made it onto our flight with our data breached through several different choices as well as our delays.

36:45.910 --> 36:52.890
But when the weather clears and our flights cleared from ticketing to takeoff, we've made it.

36:54.070 --> 36:59.710
And really through this hacking adventure, we've learned several different things.

36:59.710 --> 37:08.330
We've watched how the airports, the airlines, and well, vendors and different service providers all play together.

37:08.330 --> 37:16.550
And all some of the pressure points for where cyber security has a lot of policy, has a lot of room for development.

37:16.990 --> 37:25.050
But one of the other things to keep in mind is with each of the choices, there was a lot that we haven't uncovered or that we didn't get to discuss.

37:25.050 --> 37:33.370
Much like the choose your own adventures, you chose well, wisely, but you also chose poorly.

37:33.970 --> 37:36.730
You didn't die of dystheria.

37:37.210 --> 37:41.490
You didn't die, or excuse me, you didn't die of dysentery.

37:41.490 --> 37:46.190
You didn't die from agent cyber squirrel.

37:46.610 --> 37:54.930
But it's opened the doors and discussions to see how you would do the next time you go through, whether you would make the same choices.

37:54.930 --> 38:01.490
Because from ticketing to takeoff, airports truly are a hacking choose your own adventure.

38:01.530 --> 38:12.490
It's been fun to be your tour guide and I encourage you to check out the rest of the aerospace village and all that DEF CON has to offer as we go into safe mode and go digital.

38:12.490 --> 38:19.490
Find me at LawyerLiz and also follow Scythe at scythe underscore io.

38:19.490 --> 38:21.830
Thanks for flying with us.

