WEBVTT

00:00:06.360 --> 00:00:07.480
Welcome in San Diego.

00:00:07.480 --> 00:00:11.400
It's Jade Hindman on this episode of KPBS Midday Edition.

00:00:11.400 --> 00:00:16.160
From Microsoft to flights and now banking , we're talking about tech troubles.

00:00:16.160 --> 00:00:18.680
This is KPBS Midday Edition.

00:00:18.680 --> 00:00:21.280
Connecting our communities through conversation.

00:00:30.000 --> 00:00:33.000
America's airports are looking to get back on track today.

00:00:33.000 --> 00:00:37.280
After Friday's nationwide ground stop upended air travel across the country.

00:00:37.280 --> 00:00:42.120
It was the longest nationwide grounding of flights since the September 11th attacks.

00:00:42.120 --> 00:00:46.800
Federal officials are blaming a routine telecommunications update for the outage.

00:00:46.800 --> 00:00:51.240
Here's what Transportation Secretary Sean Duffy had to say about it on Friday.

00:00:51.720 --> 00:00:56.040
We have old , uh , old switches , old routers.

00:00:56.040 --> 00:01:01.140
We use 1980s , uh , little copper lines.

00:01:01.180 --> 00:01:04.380
It's an old system that went down and went down everywhere.

00:01:04.380 --> 00:01:05.540
It got overloaded.

00:01:05.580 --> 00:01:09.020
New information , of course , is still emerging about that.

00:01:09.060 --> 00:01:12.420
But Friday's air traffic outage is not even the most recent.

00:01:12.460 --> 00:01:22.420
Today , several major banks have been reporting outages , and these failures are causing many people to ask how safe and secure is the technology we depend on?

00:01:22.540 --> 00:01:26.300
Joining me to help us understand what's happening is Nicholas Beyer.

00:01:26.340 --> 00:01:32.500
He's a San Diego based cybersecurity expert and educator at the University of San Diego.

00:01:32.620 --> 00:01:35.020
Nico , welcome back to Midday Edition.

00:01:35.060 --> 00:01:36.220
Thanks for having me.

00:01:36.380 --> 00:01:40.940
Glad to have you here for this , because you're one of the bright minds who can break this down.

00:01:41.100 --> 00:01:47.460
So we just heard the Transportation secretary statement on the cause of Friday's nationwide flight stoppage.

00:01:47.500 --> 00:01:49.500
What do you make of that explanation?

00:01:49.740 --> 00:01:50.980
That's a great question.

00:01:50.980 --> 00:02:01.550
So to me , that indicates that they did not do proper testing and or they did not have a threat model that allowed them to plan for such failures.

00:02:01.590 --> 00:02:12.430
Normally when you're making such a big change , you model out what could potentially go wrong and you have a plan for restoring it to the previously known good configuration.

00:02:12.430 --> 00:02:24.470
And it seems to me as though that was not fully done in this particular case , because it took them a little bit longer than we would have hoped to identify the root cause.

00:02:24.670 --> 00:02:27.670
Now you point to a lack of planning potentially here.

00:02:27.670 --> 00:02:32.190
How could this have been avoided and how has it been avoided up to this point?

00:02:32.230 --> 00:02:32.790
Sure.

00:02:32.790 --> 00:02:35.830
So normally what will happen is when a change is made.

00:02:36.070 --> 00:02:45.470
Um , the folks that are making the change will identify how the change is going to be made , how one system will move to the other , and what could go wrong.

00:02:45.470 --> 00:02:51.550
So , for example , in this case , we saw that one particular router began flooding others.

00:02:51.550 --> 00:02:55.990
And we're still unsure whether that's faulty hardware or a misconfiguration.

00:02:55.990 --> 00:03:05.530
But it's important for the folks making the change to have a plan to restore to a known good configuration in case something like this goes wrong.

00:03:05.530 --> 00:03:12.050
Now , this was a telecommunications change , so they're changing the way that the traffic gets from one place to the other.

00:03:12.050 --> 00:03:14.370
So that's a little bit easier said than done.

00:03:14.370 --> 00:03:22.290
But we would hope that at such a high and important level that they would have conducted this type of change control beforehand.

00:03:22.290 --> 00:03:23.690
But have they done this before?

00:03:24.370 --> 00:03:26.330
Have they made these types of changes?

00:03:26.370 --> 00:03:28.050
Yeah , these are pretty routine.

00:03:28.050 --> 00:03:32.170
And a lot of the times we don't we don't realize that they're actually happening.

00:03:32.170 --> 00:03:33.730
And that's the way that it's supposed to be.

00:03:33.730 --> 00:03:37.330
When changes are made , the customer is not supposed to realize that it's happening.

00:03:37.330 --> 00:03:40.010
And afterwards they will say , hey , we made this change.

00:03:40.010 --> 00:03:41.170
Look how great it is.

00:03:41.170 --> 00:03:47.010
But it seems like in this case , they did not have all their ducks in a row before they actually made the change.

00:03:47.050 --> 00:03:48.170
A routine change.

00:03:48.410 --> 00:04:00.990
Okay , with a software outage of this scope , one of the first things that that came to a lot of people's minds , I'm sure , um , and even mine was this is a cyber attack.

00:04:01.030 --> 00:04:03.110
I mean , what do you think about that possibility?

00:04:03.630 --> 00:04:05.070
They've ruled that out.

00:04:05.430 --> 00:04:10.190
They've said that it's not a not a cyber attack , which is good , right?

00:04:10.230 --> 00:04:14.830
But we still had a loss of availability of that FAA system.

00:04:15.350 --> 00:04:18.310
But this was not a cyber attack based on the information that we have.

00:04:18.350 --> 00:04:21.110
Now another culprit that's been brought up is AI.

00:04:21.150 --> 00:04:26.070
The FAA , in fact , is about to roll out an AI powered smart system.

00:04:26.110 --> 00:04:29.710
Officials are saying this , though , was not the cause.

00:04:29.750 --> 00:04:33.710
But what questions about AI come up for you around this outage?

00:04:34.230 --> 00:04:36.350
So this was not caused by AI.

00:04:36.390 --> 00:04:45.870
As you mentioned , they were just changing how the traffic gets from one place to the other , but they could have definitely leveraged AI to check this change and come up with back out plans.

00:04:46.230 --> 00:04:49.350
Um , we've seen other issues previously.

00:04:49.390 --> 00:05:04.490
So for example , vulnerabilities like the PHP vulnerability that we had a few weeks ago , um , which was facilitated by AI helping folks discover more attackers discover these types of vulnerabilities more easily.

00:05:04.970 --> 00:05:14.970
Because we have AI models that are really good at cybersecurity now and that are freely and openly available to those who have the hardware to run these models.

00:05:15.090 --> 00:05:15.610
Hmm.

00:05:15.730 --> 00:05:23.970
You know , does an outage like this sort of make you more concerned about flying yourself?

00:05:24.850 --> 00:05:27.370
Um , definitely a little bit.

00:05:27.370 --> 00:05:32.810
But at the same time , this is what comes with integrating technology into our daily lives.

00:05:32.810 --> 00:05:42.330
So there's really no way for us to go back unless we go back to good old , old fashioned radios like we had back in the day.

00:05:42.530 --> 00:05:45.050
But I don't see that happening anytime soon.

00:05:45.090 --> 00:05:46.770
I was personally affected.

00:05:46.810 --> 00:05:47.650
Um , so.

00:05:47.690 --> 00:05:48.370
Yeah.

00:05:48.410 --> 00:05:50.810
So it's just part of traveling these days , right?

00:05:50.850 --> 00:05:52.450
There's always going to be some kind of delay.

00:05:52.450 --> 00:05:55.890
And unfortunately , this time it was due to a technological issue.

00:05:55.930 --> 00:05:58.210
Well , we're glad you made it back safely.

00:05:58.290 --> 00:06:02.420
Um , the FAA , the FAA's outage was not the only major one.

00:06:02.420 --> 00:06:07.620
Last week , Microsoft Outlook , one of the most common email platforms , had a global outage as well.

00:06:07.620 --> 00:06:09.220
What can you tell us about that?

00:06:09.260 --> 00:06:09.780
Sure.

00:06:09.820 --> 00:06:10.060
Yeah.

00:06:10.060 --> 00:06:15.700
So that was definitely also on the news that was caused by a combination of three different bugs.

00:06:15.700 --> 00:06:51.700
So initially there was a bug introduced in July and then once that was combined with a different chain , two other changes that they made , which included moving how the team's traffic goes to different systems , it caused the systems to go offline , and then the systems that are supposed to check that , called the health check system , were not able to tell whether a system was online or offline , and then it resulted in the traffic going to a much smaller pool of servers , which overloaded the systems which caused the outage.

00:06:52.420 --> 00:06:56.420
What similarities do you see between the outlook and the FAA outages?

00:06:56.460 --> 00:06:58.260
There needs to be better planning.

00:06:58.260 --> 00:07:06.880
So these are both things that could have been tested ahead of time and any issues could have potentially been identified.

00:07:07.200 --> 00:07:14.360
Be that as it may , though , if folks test , that doesn't always mean that they're going to find the issues that will occur.

00:07:14.360 --> 00:07:23.440
And that's why it's important to do planning and identify anything that could go wrong to the best of their ability , and then have a plan to restore just in case it does.

00:07:23.440 --> 00:07:24.400
Something does go wrong.

00:07:24.440 --> 00:07:32.640
Why do you think folks are having such a tough time with that planning , which is something that's happened , you know , routinely for a long time here.

00:07:32.840 --> 00:07:41.720
Having worked in the industry for a really long time , this is actually a problem that all kinds of organizations have , from really big banks to really small companies.

00:07:41.760 --> 00:07:48.480
Change management is something that's very difficult and tedious , and you're not always going to get it right.

00:07:48.480 --> 00:07:56.400
That's why we try to do the planning , try to identify anything that could go wrong and then have a plan to restore , just in case.

00:07:56.400 --> 00:07:59.680
As humans , we're not able to predict.

00:07:59.680 --> 00:08:04.300
We don't have a crystal ball that's going to tell us everything that's going to happen.

00:08:04.740 --> 00:08:08.660
And so that's just the nature of updating technology.

00:08:08.660 --> 00:08:17.700
So it seems like last week the stars aligned and there were a bunch of different things that happened within the span of a few days across different vendors and organizations.

00:08:17.860 --> 00:08:18.340
All right.

00:08:18.340 --> 00:08:27.100
Well , not to make people even more concerned about our tech , but a security researcher found security risks in a common technology used on the web.

00:08:27.100 --> 00:08:29.500
Today , the technology is called PHP.

00:08:30.060 --> 00:08:35.380
Can you tell us more about the concerns there and what it is and what's being done to fix them?

00:08:35.420 --> 00:08:35.820
Sure.

00:08:35.820 --> 00:08:42.940
So PHP is a programming language that underpins a lot of different websites and web applications.

00:08:42.940 --> 00:08:55.300
So in this case there was a vulnerability called PHP to shell , which was identified , and it allowed folks to run code on systems that had the affected version without actually logging in.

00:08:55.300 --> 00:08:57.060
So that's very , very concerning.

00:08:57.060 --> 00:08:59.580
It was had a critical severity rating.

00:08:59.710 --> 00:09:13.470
and recently the Cybersecurity Infrastructure and Security Agency added this vulnerability to the Known Exploited Vulnerabilities list , which means that they have observed it being exploited in the wild.

00:09:14.070 --> 00:09:25.430
We've also seen , through separate reporting that the North Koreans are now starting to exploit systems that have not yet patched this vulnerability.

00:09:25.430 --> 00:09:49.430
So , um , for folks listening , it's really important to reach out to the folks that are running your website or running any web facing services and ask questions about what they're doing to remediate this particular vulnerability , because unfortunately , it's not something that regular people can go and fix , because this is something that affects , um , systems and mechanisms that are on the back end , on the front end.

00:09:49.470 --> 00:09:55.870
Speaking of vulnerabilities and systems , um , you know , cyber attacks come in a lot of different forms.

00:09:55.870 --> 00:10:00.610
I think the last time we spoke , you told us about how local water systems were vulnerable to cyber attacks.

00:10:00.650 --> 00:10:08.610
Recently in Europe , there were cyber attacks that were targeted towards refrigerators and grocery stores.

00:10:08.650 --> 00:10:10.770
What can you tell me about that?

00:10:10.770 --> 00:10:14.530
And is that something that could happen here and even in our own homes?

00:10:14.570 --> 00:10:16.290
So that's a great one.

00:10:16.370 --> 00:10:22.730
So that's an example of something really interesting where cyber actually blends over into the physical world.

00:10:22.730 --> 00:10:27.250
So these attackers and in France that's been attributed to the Iranians.

00:10:27.290 --> 00:10:33.370
They went ahead and affected the cooling systems and the warning systems.

00:10:33.370 --> 00:10:36.410
So that's something that we've seen in the past.

00:10:36.410 --> 00:10:43.570
So they raised the temperature of the fridges to about 50°C.

00:10:43.570 --> 00:10:46.410
And they also interfered with the warning systems.

00:10:46.410 --> 00:10:55.490
So the folks monitoring the fridges were not actually able to see that until they realized that the food started going bad.

00:10:55.530 --> 00:11:02.270
They also attempted to do something similar for fridges in a blood bank , but they were not successful.

00:11:02.270 --> 00:11:08.350
And it's important to note that what we saw affected commercial fridges , not residential fridges.

00:11:08.350 --> 00:11:14.110
So these were fridges that are in a supermarket and it's not the first time that we've seen something like this.

00:11:14.110 --> 00:11:24.990
Many , many years ago when target got breached , they actually got breached through their air conditioning vendor which was monitoring their air conditioning systems or their HVAC systems remotely.

00:11:24.990 --> 00:11:37.390
So whenever you put something on the internet , you have to be prepared for it to potentially be accessed and modified by folks that shouldn't have access to modify or change those systems.

00:11:37.390 --> 00:11:40.110
So that's just the nature of putting things on the internet.

00:11:40.510 --> 00:11:47.110
Uh , your second part of systems that we have in our homes , we have smart devices that are continuing to go into our homes.

00:11:47.110 --> 00:11:53.270
And the more smart devices we put into our homes , the more vulnerabilities we are opening ourselves up to.

00:11:53.310 --> 00:11:59.190
So it's important for folks to keep that in mind when they're putting smart devices on their home networks.

00:11:59.250 --> 00:12:00.490
But when they keep it in mind.

00:12:00.530 --> 00:12:01.850
What do they need to do?

00:12:01.890 --> 00:12:06.290
So it's really important that you look at the security measures that the vendors are taking.

00:12:06.290 --> 00:12:11.130
Are they providing a mechanism that allows folks to patch these systems?

00:12:11.170 --> 00:12:18.930
Are they giving guidance on which traffic to go in and out , which is more than the average person will be able to configure?

00:12:18.970 --> 00:12:25.690
So the advice that I would give is if anything is internet connected , make sure that the vendor is able to update it.

00:12:25.730 --> 00:12:36.410
Make sure that your home router is able to identify any malicious traffic , including traffic going to smart devices , which of course is easier said than done.

00:12:36.450 --> 00:12:45.930
So I would say putting something that is connected to the internet on your home network , be aware that it could potentially be involved in cyber attack.

00:12:45.970 --> 00:12:52.130
Are there people that folks can just call to come and help them work through these things in their home?

00:12:53.090 --> 00:12:56.490
I don't know how to look at my router and know exactly.

00:12:56.490 --> 00:12:57.210
So it's a lot.

00:12:57.250 --> 00:13:02.540
It's very difficult for the common folks to go out and examine these things.

00:13:02.900 --> 00:13:08.340
If you have a family member that's a nerd , maybe a niece and nephew , something like that.

00:13:08.340 --> 00:13:13.140
I would recommend giving them a call , but this is definitely something we'll have to revisit.

00:13:13.180 --> 00:13:13.660
Okay.

00:13:13.700 --> 00:13:15.580
I've been speaking with Nicholas Beyer.

00:13:15.580 --> 00:13:20.740
He is a cybersecurity expert and adjunct professor at the University of San Diego.

00:13:20.780 --> 00:13:22.420
Nico , thank you so much for being here today.

00:13:22.460 --> 00:13:23.620
Thanks for having me.

00:13:30.820 --> 00:13:31.940
That's our show for today.

00:13:31.980 --> 00:13:33.540
I'm your host , Jade Hindman.

00:13:33.540 --> 00:13:35.660
Thanks for tuning in to Midday Edition.

00:13:35.780 --> 00:13:38.860
Be sure to have a great day on purpose , everyone.

