WEBVTT - The State of Cybersecurity

0:00:02.480 --> 0:00:05.480
<v Speaker 1>Get in touch with technology with tech Stuff from how

0:00:05.559 --> 0:00:14.880
<v Speaker 1>Stuff Looks Coming. Hey there everyone, and welcome to Tech Stuff.

0:00:14.920 --> 0:00:20.160
<v Speaker 1>My name is Jonathan Strickland, and here is Lauren Vogelbaum. Yep,

0:00:20.320 --> 0:00:23.280
<v Speaker 1>that's that's that's my co host. Everybody. Today, we're going

0:00:23.320 --> 0:00:26.840
<v Speaker 1>to talk a little bit about security. It's an important thing,

0:00:27.040 --> 0:00:30.800
<v Speaker 1>cyber security specifically. Yeah, you've got to secure your cybers,

0:00:30.960 --> 0:00:33.880
<v Speaker 1>all your cybers, all your cybers are belonging to you

0:00:34.000 --> 0:00:37.400
<v Speaker 1>and should continue to do so. Um. Yeah, we're we're

0:00:37.400 --> 0:00:41.280
<v Speaker 1>talking about cybersecurity because because President of Wilma did, yes

0:00:41.320 --> 0:00:44.480
<v Speaker 1>he did. The President of the United States of America

0:00:45.000 --> 0:00:47.880
<v Speaker 1>had his State of the Union address, which is when

0:00:47.920 --> 0:00:50.000
<v Speaker 1>the president, if you are not from the United States,

0:00:50.040 --> 0:00:55.000
<v Speaker 1>were perhaps just our politically, uh, completely separate from anything

0:00:55.040 --> 0:00:57.560
<v Speaker 1>that goes on, a little bit lost and confused perhaps,

0:00:57.640 --> 0:01:00.000
<v Speaker 1>or maybe maybe you haven't been to the internet. Maybe

0:01:00.040 --> 0:01:03.440
<v Speaker 1>you live as a hermit often the distance and you

0:01:03.560 --> 0:01:06.640
<v Speaker 1>only get human contact through podcasts, in which case, hey,

0:01:06.640 --> 0:01:10.160
<v Speaker 1>thanks for choosing ours. But yeah, every every year the

0:01:10.440 --> 0:01:15.200
<v Speaker 1>president has this this forum where he begins to to

0:01:15.360 --> 0:01:20.160
<v Speaker 1>address how the country is doing and what his administration

0:01:20.280 --> 0:01:23.160
<v Speaker 1>or her administration. Should we ever get a female president.

0:01:23.480 --> 0:01:27.839
<v Speaker 1>I'm sure it's someday, someday, any any year now, but anyway,

0:01:27.959 --> 0:01:31.600
<v Speaker 1>that is when the president will lay out plans for

0:01:31.760 --> 0:01:34.520
<v Speaker 1>what is going what the government will focus on in

0:01:34.560 --> 0:01:37.760
<v Speaker 1>the following year, assuming the rest of the government plays ball,

0:01:38.000 --> 0:01:41.959
<v Speaker 1>because again the United States government, it's not just the president, sure,

0:01:42.160 --> 0:01:44.479
<v Speaker 1>but but it's kind of saying what's important. Yeah, yeah,

0:01:44.520 --> 0:01:47.680
<v Speaker 1>And I personally kind of side note. I feel like

0:01:47.720 --> 0:01:52.200
<v Speaker 1>this has become less critical to politics now, in this

0:01:52.200 --> 0:01:55.000
<v Speaker 1>this our information age, than it was, for example, fifty

0:01:55.040 --> 0:01:57.520
<v Speaker 1>or sixty years ago, when people didn't really have direct

0:01:57.560 --> 0:02:00.760
<v Speaker 1>and continual access to everything bloody going on in the

0:02:00.760 --> 0:02:02.920
<v Speaker 1>government all the time. Yeah, that's that's a good point

0:02:03.000 --> 0:02:05.960
<v Speaker 1>because earlier you would hear the president essentially during the

0:02:06.000 --> 0:02:10.240
<v Speaker 1>State of the Union address and after any major event

0:02:10.440 --> 0:02:13.720
<v Speaker 1>like a catastrophe or not even not not necessarily something bad,

0:02:13.760 --> 0:02:15.520
<v Speaker 1>but usually it had to be something big, and then

0:02:15.520 --> 0:02:18.280
<v Speaker 1>the president would end up addressing the nation about it.

0:02:18.919 --> 0:02:21.200
<v Speaker 1>But in this case, we now live in a world

0:02:21.280 --> 0:02:24.560
<v Speaker 1>where we get this information on a fairly continuous basis.

0:02:24.560 --> 0:02:26.760
<v Speaker 1>I mean, you could follow the president on Twitter and

0:02:26.800 --> 0:02:30.560
<v Speaker 1>get information or just the twenty four hour news coverage

0:02:30.720 --> 0:02:33.359
<v Speaker 1>of what's going on the government's out there too. Anyways.

0:02:33.400 --> 0:02:35.600
<v Speaker 1>State the Union kind of traditionally seen as a big

0:02:35.639 --> 0:02:39.760
<v Speaker 1>important event here in the US. So during the State

0:02:39.800 --> 0:02:43.000
<v Speaker 1>of the Union, one of the many points the President

0:02:43.240 --> 0:02:47.440
<v Speaker 1>addressed was cybersecurity. Now that was not the the the

0:02:47.600 --> 0:02:49.600
<v Speaker 1>entire focus of the speech. In fact, it only took

0:02:49.639 --> 0:02:51.800
<v Speaker 1>up a small section about a minute and a half.

0:02:51.840 --> 0:02:53.639
<v Speaker 1>I think. Yeah. In fact I can I can read

0:02:53.639 --> 0:02:57.200
<v Speaker 1>out verbatim what he said because the text is available

0:02:57.360 --> 0:03:00.760
<v Speaker 1>on the on the Internet of all things. So here's

0:03:00.760 --> 0:03:05.200
<v Speaker 1>what President Obama had to say about cyber security. America

0:03:05.360 --> 0:03:08.680
<v Speaker 1>must also face the rapidly growing threat from cyber attacks.

0:03:08.720 --> 0:03:12.239
<v Speaker 1>We know hackers steal people's identities and infiltrate private email.

0:03:12.520 --> 0:03:15.600
<v Speaker 1>We know foreign countries and companies swipe our corporate secrets.

0:03:15.960 --> 0:03:18.880
<v Speaker 1>Now our enemies are also seeking the ability to sabotage

0:03:18.880 --> 0:03:21.960
<v Speaker 1>our power grid, our financial institutions, and our air traffic

0:03:21.960 --> 0:03:25.080
<v Speaker 1>control systems. We cannot look back years from now and

0:03:25.120 --> 0:03:27.640
<v Speaker 1>wonder why we did nothing in the face of real

0:03:27.680 --> 0:03:30.960
<v Speaker 1>threats to our security and our economy. That's why earlier

0:03:31.000 --> 0:03:33.560
<v Speaker 1>today I signed a new executive order that will strengthen

0:03:33.560 --> 0:03:37.240
<v Speaker 1>our cyber defenses by increasing information sharing and developing standards

0:03:37.280 --> 0:03:40.440
<v Speaker 1>to protect our national security, our jobs, and our privacy.

0:03:40.720 --> 0:03:43.400
<v Speaker 1>Now Congress must act as well by passing legislation to

0:03:43.400 --> 0:03:46.400
<v Speaker 1>give our government a greater capacity secure our networks ended

0:03:46.440 --> 0:03:50.440
<v Speaker 1>to our attacks. So really, this of course just served

0:03:50.520 --> 0:03:53.200
<v Speaker 1>to alert the nation to yes, we are aware of

0:03:53.200 --> 0:03:55.560
<v Speaker 1>the problem, and yes we are going to do something

0:03:55.680 --> 0:03:59.280
<v Speaker 1>to respond to this problem. But of course the speech

0:03:59.360 --> 0:04:02.160
<v Speaker 1>was not the right venue to go into detail about

0:04:02.360 --> 0:04:04.200
<v Speaker 1>what that was going to be, right right, These these

0:04:04.280 --> 0:04:06.560
<v Speaker 1>kinds of speeches aren't really used for extreme detail of

0:04:06.600 --> 0:04:10.840
<v Speaker 1>any kind. It's it's more more hey stuff, Yeah, hey, problem,

0:04:10.920 --> 0:04:13.680
<v Speaker 1>we're gonna fix it. How are we going to fix it?

0:04:14.400 --> 0:04:18.120
<v Speaker 1>Look over here at the Chewbacca. Um. Yeah, And this

0:04:18.200 --> 0:04:21.360
<v Speaker 1>is regardless of who is in power. It's just that's

0:04:21.400 --> 0:04:23.360
<v Speaker 1>the way, that's the way it works. Yeah, we We are,

0:04:23.400 --> 0:04:25.320
<v Speaker 1>by the way, trying very hard in this episode to

0:04:25.480 --> 0:04:28.400
<v Speaker 1>to not let any of our personal politics enter into

0:04:28.480 --> 0:04:31.280
<v Speaker 1>this discussion. Sure, so this is this is actually us

0:04:31.320 --> 0:04:33.520
<v Speaker 1>being being as fair as we possibly can be. And

0:04:33.560 --> 0:04:35.080
<v Speaker 1>if we wind up making a little bit of fun

0:04:35.120 --> 0:04:38.880
<v Speaker 1>of any given administration, it's not Yeah, it's not politically motivated.

0:04:39.120 --> 0:04:41.560
<v Speaker 1>Now in this case, it's motivated by our knowledge of

0:04:41.600 --> 0:04:45.240
<v Speaker 1>how technology works, how policy works, and how those two

0:04:45.800 --> 0:04:50.279
<v Speaker 1>things don't necessarily mesh very well. Uh. And that that's

0:04:50.279 --> 0:04:55.040
<v Speaker 1>regardless of what your political stances, whether you're conservative or liberal,

0:04:55.160 --> 0:04:58.520
<v Speaker 1>no matter what it's it's just the technology is kind

0:04:58.520 --> 0:05:02.200
<v Speaker 1>of a political uh, just as a tool. Now you

0:05:02.240 --> 0:05:05.120
<v Speaker 1>can use it for political means. But anyway, getting into this,

0:05:05.200 --> 0:05:07.520
<v Speaker 1>we we really wanted to talk more about the Executive

0:05:07.600 --> 0:05:11.799
<v Speaker 1>Order itself because that's where the approach that that Obama

0:05:11.880 --> 0:05:14.080
<v Speaker 1>wants the government to take. That's where that's where it

0:05:14.120 --> 0:05:16.560
<v Speaker 1>comes from, right right, And UM, I I read I

0:05:16.600 --> 0:05:18.960
<v Speaker 1>read a great write up that Michael Daniel, who is

0:05:19.040 --> 0:05:22.400
<v Speaker 1>Obama's cybersecurity coordinator, wrote up about it, UM and he

0:05:22.440 --> 0:05:24.960
<v Speaker 1>was just saying that that basically the Executive Order breaks

0:05:24.960 --> 0:05:28.720
<v Speaker 1>down into three parts and that's um basically just uh,

0:05:28.920 --> 0:05:32.159
<v Speaker 1>it covers information sharing first off, which means that it

0:05:32.520 --> 0:05:36.640
<v Speaker 1>really wants the different segments of the government to work

0:05:36.800 --> 0:05:39.760
<v Speaker 1>with all of these private companies that run run our

0:05:39.800 --> 0:05:44.800
<v Speaker 1>technology infrastructure and our power infrastructure, UM to share information

0:05:44.839 --> 0:05:50.240
<v Speaker 1>about any any cyber threats that are going on. And UM, yeah,

0:05:50.240 --> 0:05:53.800
<v Speaker 1>that's the first big section because obviously the issue here

0:05:53.880 --> 0:05:56.960
<v Speaker 1>is that sometimes the government gets information, but depending upon

0:05:57.000 --> 0:05:59.479
<v Speaker 1>the classification of that information, they may not be able

0:05:59.520 --> 0:06:03.200
<v Speaker 1>to share it very on a very wide distribution. And

0:06:03.360 --> 0:06:07.120
<v Speaker 1>beyond that, sometimes when you get information in the government,

0:06:07.160 --> 0:06:10.720
<v Speaker 1>it's really hard for the information to escape the government.

0:06:10.960 --> 0:06:12.640
<v Speaker 1>So in other words, this is supposed to lay the

0:06:12.640 --> 0:06:16.480
<v Speaker 1>groundwork to allow the government to share information with entities

0:06:16.839 --> 0:06:20.240
<v Speaker 1>that are critical to our infrastructure, and also going the

0:06:20.279 --> 0:06:26.560
<v Speaker 1>other way, giving giving those entities, uh basic incentive, thank

0:06:26.560 --> 0:06:29.440
<v Speaker 1>you so much, incentive to also share any information that

0:06:29.480 --> 0:06:31.880
<v Speaker 1>they have about some cyber texts, any cyber attacks that

0:06:31.960 --> 0:06:33.880
<v Speaker 1>might be occurring back to the government so that the

0:06:33.880 --> 0:06:37.080
<v Speaker 1>government can do more to help out right, And we'll

0:06:37.120 --> 0:06:39.760
<v Speaker 1>we'll dive into more about how that's a challenge in

0:06:39.800 --> 0:06:42.719
<v Speaker 1>a little bit because as it turns out, you know,

0:06:42.800 --> 0:06:50.000
<v Speaker 1>it sounds, yeah, totally everybody like like we just got attacked,

0:06:50.000 --> 0:06:52.080
<v Speaker 1>we should let the government know. But I'll get into

0:06:52.120 --> 0:06:57.080
<v Speaker 1>why a lot of companies don't really necessarily see that

0:06:57.200 --> 0:06:59.760
<v Speaker 1>as the best option, right right, All right, So that's

0:06:59.800 --> 0:07:04.880
<v Speaker 1>part one. Part to UM kind of outlines a flexible

0:07:05.160 --> 0:07:09.520
<v Speaker 1>risk based package of core practices based on existing standards

0:07:09.520 --> 0:07:14.040
<v Speaker 1>of cybersecurity. Yeah, so this is looking at there there

0:07:14.080 --> 0:07:18.440
<v Speaker 1>are several organizations already that are working toward the best

0:07:18.440 --> 0:07:21.960
<v Speaker 1>practices for cybersecurity, and so this is kind of trying

0:07:22.000 --> 0:07:24.080
<v Speaker 1>to to say, let's take a look at all of

0:07:24.120 --> 0:07:27.400
<v Speaker 1>this stuff and and pick and choose the best out

0:07:27.400 --> 0:07:29.840
<v Speaker 1>of all of it and use that as the framework

0:07:29.880 --> 0:07:33.120
<v Speaker 1>for what everyone should do. That's also possibly going to

0:07:33.160 --> 0:07:36.000
<v Speaker 1>be a bottleneck, but I'll get to that when we

0:07:36.080 --> 0:07:39.360
<v Speaker 1>get a little further into this. Yes. Yes, the third

0:07:39.480 --> 0:07:44.160
<v Speaker 1>The third part then deals with privacy protections, because when

0:07:44.240 --> 0:07:47.160
<v Speaker 1>you're dealing with these companies that have a lot of

0:07:47.200 --> 0:07:50.880
<v Speaker 1>private citizens data or even their own private corporate data

0:07:51.240 --> 0:07:53.280
<v Speaker 1>or you know, or or on the other end from

0:07:53.280 --> 0:07:56.520
<v Speaker 1>the government, the government doesn't doesn't want anything sensitive to

0:07:56.600 --> 0:07:59.880
<v Speaker 1>end up being revealed that they don't want to give out. Right. Yeah,

0:08:00.440 --> 0:08:04.320
<v Speaker 1>you know, companies have proprietary information for example, So let's

0:08:04.320 --> 0:08:08.360
<v Speaker 1>say that a cyber attack focuses on something that involves

0:08:08.400 --> 0:08:12.520
<v Speaker 1>proprietary information, information that is necessary for that company to

0:08:12.600 --> 0:08:15.880
<v Speaker 1>keep secret. It's a trade secret. It's something that allows

0:08:15.960 --> 0:08:18.480
<v Speaker 1>them to do business the way they do it and

0:08:18.520 --> 0:08:21.080
<v Speaker 1>make money and make money. Yeah. So for example, just

0:08:21.120 --> 0:08:23.080
<v Speaker 1>this is a random example that I just thought up

0:08:23.160 --> 0:08:26.880
<v Speaker 1>right now, but the Google algorithm. Okay, because Google algorithm,

0:08:26.960 --> 0:08:30.880
<v Speaker 1>that's essentially the the the recipe that tells Google how

0:08:30.960 --> 0:08:34.840
<v Speaker 1>to rank search results on any given query. Well, that's

0:08:34.840 --> 0:08:37.800
<v Speaker 1>a that's pretty useful information to have, especially if you're

0:08:37.800 --> 0:08:42.240
<v Speaker 1>building websites. But let's say that cyber they the Google

0:08:42.280 --> 0:08:45.040
<v Speaker 1>suffered a cyber attack and part of the information that

0:08:45.160 --> 0:08:48.040
<v Speaker 1>was compromised was this Google algorithm, which is kind of

0:08:48.080 --> 0:08:51.720
<v Speaker 1>like their their secret sauce. You know, it's it's not

0:08:51.960 --> 0:08:57.000
<v Speaker 1>not published, right, is the mathematical Horsey sauce. Yes, it is, Yes,

0:08:57.040 --> 0:08:59.360
<v Speaker 1>it's it's part of their eleven Herbs and spices, and

0:08:59.679 --> 0:09:03.000
<v Speaker 1>so they don't want the information getting out. And if

0:09:03.000 --> 0:09:05.600
<v Speaker 1>they were to report the information to the government, it's

0:09:05.600 --> 0:09:10.160
<v Speaker 1>possible that part of the distribution of information to everybody else,

0:09:10.320 --> 0:09:12.520
<v Speaker 1>you know, saying like, well, Google was attacked, so these

0:09:12.559 --> 0:09:14.600
<v Speaker 1>other companies need to be aware of this as well.

0:09:15.240 --> 0:09:18.440
<v Speaker 1>The worry is that the algorithm itself would become part

0:09:18.440 --> 0:09:21.960
<v Speaker 1>of that information distribution and then Google loses its advantage

0:09:21.960 --> 0:09:25.080
<v Speaker 1>in the marketplace. That's that's just a simple example, and

0:09:25.120 --> 0:09:27.560
<v Speaker 1>it may even be unrealistic in the sense of what

0:09:27.559 --> 0:09:31.040
<v Speaker 1>we're talking about here, but it's just to kind of illustrate, uh,

0:09:31.200 --> 0:09:34.000
<v Speaker 1>why the government needs to take this into account when

0:09:34.200 --> 0:09:37.520
<v Speaker 1>formulating policy. Yeah, and and so those are the basic

0:09:37.559 --> 0:09:40.480
<v Speaker 1>three parts and uh, and the administration is really big

0:09:40.559 --> 0:09:42.880
<v Speaker 1>on on saying that you know that that they want

0:09:42.920 --> 0:09:45.840
<v Speaker 1>to work really hard with with companies and with the

0:09:45.920 --> 0:09:48.720
<v Speaker 1>different government organizations to make all of this as sensical

0:09:48.960 --> 0:09:54.040
<v Speaker 1>and um, not like work, more like sharing and hugging. Yeah,

0:09:54.280 --> 0:09:56.800
<v Speaker 1>there needs to be sharing and hugging well while standing

0:09:56.920 --> 0:09:59.720
<v Speaker 1>shoulder to shoulder to keep the cyber attackers at bay.

0:10:00.320 --> 0:10:02.080
<v Speaker 1>And you know, and so they say that they worked

0:10:02.080 --> 0:10:06.840
<v Speaker 1>with with over two companies directly and and fifteen million

0:10:06.840 --> 0:10:09.720
<v Speaker 1>employees and all kinds of crazy numbers like that, trying

0:10:09.720 --> 0:10:13.439
<v Speaker 1>to trying to work to get this information together. And

0:10:13.440 --> 0:10:15.560
<v Speaker 1>and to be fair, we should also point out that

0:10:15.640 --> 0:10:18.360
<v Speaker 1>these are it's a directive, but again it does not

0:10:19.200 --> 0:10:22.720
<v Speaker 1>lay out step by step how this is going to happen.

0:10:22.800 --> 0:10:27.599
<v Speaker 1>It's more like saying to specific departments within the government, Hey,

0:10:27.640 --> 0:10:30.240
<v Speaker 1>this is what I want. Here's the result I want.

0:10:30.640 --> 0:10:33.480
<v Speaker 1>You have two hundred and forty days to return to

0:10:33.520 --> 0:10:37.120
<v Speaker 1>me the result I want go And it's up to

0:10:37.200 --> 0:10:41.000
<v Speaker 1>that individual department to determine what are the steps that

0:10:41.040 --> 0:10:43.880
<v Speaker 1>it needs to take in order to meet the requirements

0:10:43.920 --> 0:10:46.800
<v Speaker 1>of this executive order. Uh. This is also something that

0:10:46.840 --> 0:10:49.439
<v Speaker 1>I've seen critics point at, saying, a lot of the

0:10:49.480 --> 0:10:52.360
<v Speaker 1>time tables that are discussed within the Executive Order are

0:10:52.400 --> 0:10:56.920
<v Speaker 1>not necessarily realistic because you're talking about navigating such a

0:10:57.000 --> 0:11:00.360
<v Speaker 1>complex issue, not just from the technology side, but from

0:11:00.360 --> 0:11:04.319
<v Speaker 1>the existing policy side. That uh, that in order to

0:11:04.320 --> 0:11:07.680
<v Speaker 1>to find something that satisfies the needs of the Executive

0:11:07.760 --> 0:11:10.760
<v Speaker 1>Order and does not violate any of these other entities

0:11:10.760 --> 0:11:14.520
<v Speaker 1>that are already out there is a huge challenge. And

0:11:14.520 --> 0:11:18.080
<v Speaker 1>two hundred forty days, which is just one of the deadlines.

0:11:18.120 --> 0:11:19.840
<v Speaker 1>There's some that are like a hundred twenty days, depending

0:11:19.920 --> 0:11:21.640
<v Speaker 1>upon what it is. But it's just it's just not

0:11:21.760 --> 0:11:24.600
<v Speaker 1>enough time, right and especially considering that if you've been

0:11:24.640 --> 0:11:26.360
<v Speaker 1>paying attention to the news at all, and say the

0:11:26.400 --> 0:11:30.760
<v Speaker 1>past existence of reality, you may have noticed that the

0:11:30.800 --> 0:11:34.560
<v Speaker 1>different parts of American political system don't necessarily work together

0:11:34.640 --> 0:11:37.400
<v Speaker 1>extremely well, and so so things. I mean, for for example,

0:11:37.440 --> 0:11:39.880
<v Speaker 1>there was a Cybersecurity Act last year I believe that

0:11:39.960 --> 0:11:43.120
<v Speaker 1>tried to go through Congress. It made it past No,

0:11:43.280 --> 0:11:45.920
<v Speaker 1>that was the other one. It got failbustered by the Republicans.

0:11:45.920 --> 0:11:47.480
<v Speaker 1>They were saying that it was going to place too

0:11:47.520 --> 0:11:49.800
<v Speaker 1>much of a burden on the companies, that it would affect,

0:11:49.800 --> 0:11:51.840
<v Speaker 1>and and all kinds of stuff like that has been

0:11:51.840 --> 0:11:53.520
<v Speaker 1>going on for the past three and a half years,

0:11:53.600 --> 0:11:57.240
<v Speaker 1>or really since the mid nineties when computer networks became

0:11:57.280 --> 0:11:59.719
<v Speaker 1>a really integral part of business. Yeah. This this is

0:11:59.720 --> 0:12:03.240
<v Speaker 1>a complicated issue because on one hand, you're talking about

0:12:03.320 --> 0:12:07.520
<v Speaker 1>protecting a lot of private entities, and private entities do

0:12:07.600 --> 0:12:11.480
<v Speaker 1>not have any connection to the government other than paying taxes. Honestly,

0:12:11.520 --> 0:12:14.199
<v Speaker 1>as I'm sure we're all aware, but anyway, these private

0:12:14.280 --> 0:12:16.880
<v Speaker 1>entities don't necessarily have any other connection to the government.

0:12:16.880 --> 0:12:19.240
<v Speaker 1>They're not run by the government. It's not a socialist

0:12:19.320 --> 0:12:22.960
<v Speaker 1>kind of structure. It's private structure. Uh. But that means

0:12:23.000 --> 0:12:26.559
<v Speaker 1>that they you know, how far can the government come

0:12:26.640 --> 0:12:30.120
<v Speaker 1>in to try and protect these entities When the entity

0:12:30.160 --> 0:12:33.480
<v Speaker 1>itself is in control of something that's vital to the

0:12:33.520 --> 0:12:37.760
<v Speaker 1>operation of business or national security, then there it is

0:12:37.800 --> 0:12:40.160
<v Speaker 1>in the government's interest to come in and say, look,

0:12:40.240 --> 0:12:42.679
<v Speaker 1>I know that we don't have any uh any call

0:12:42.760 --> 0:12:44.960
<v Speaker 1>and how you run your business, that's not our job,

0:12:45.080 --> 0:12:48.040
<v Speaker 1>but we need to protect it because how your business

0:12:48.080 --> 0:12:53.480
<v Speaker 1>performs affects the citizens of this country. So I guess

0:12:53.480 --> 0:12:55.280
<v Speaker 1>we can start diving into the example order. Did you

0:12:55.360 --> 0:12:57.040
<v Speaker 1>have something else you wanted to mention before we did that?

0:12:57.080 --> 0:12:59.480
<v Speaker 1>And that's about it, all right, So here's the here's

0:12:59.480 --> 0:13:04.679
<v Speaker 1>an opening paragraph from part of the executive order. Does

0:13:04.720 --> 0:13:07.000
<v Speaker 1>the policy of the United States to enhance the security

0:13:07.080 --> 0:13:10.000
<v Speaker 1>and resilience of the nation's critical infrastructure and to maintain

0:13:10.040 --> 0:13:13.480
<v Speaker 1>a cyber environment that encourages efficiency, innovation, and economic prosperity

0:13:13.520 --> 0:13:18.000
<v Speaker 1>while promoting safety, security, business competentiality, privacy, and civil liberties.

0:13:18.040 --> 0:13:20.120
<v Speaker 1>We can achieve these goals through a partnership with the

0:13:20.160 --> 0:13:23.880
<v Speaker 1>owners and operators of critical infrastructure to improve cybersecurity information sharing,

0:13:23.920 --> 0:13:28.760
<v Speaker 1>and collaboratively develop and implement risk based standards. As a

0:13:28.760 --> 0:13:32.520
<v Speaker 1>as a mouthful, fascinating, that was so thrilling. It was, Yeah,

0:13:32.520 --> 0:13:35.959
<v Speaker 1>it's it's it's it's not quite legally ease, it's not

0:13:36.240 --> 0:13:40.640
<v Speaker 1>it's not so dense as to be uh, completely inoperable.

0:13:40.920 --> 0:13:42.840
<v Speaker 1>You can't understand a word of it without having like

0:13:42.880 --> 0:13:45.640
<v Speaker 1>three lawyers on your team, but it does. It does

0:13:45.800 --> 0:13:47.960
<v Speaker 1>make it kind of you know, it's it's this very

0:13:48.040 --> 0:13:51.319
<v Speaker 1>formal sort of language. Part of the issue here also

0:13:51.440 --> 0:13:54.520
<v Speaker 1>is that some people argue that the terms are not

0:13:55.320 --> 0:14:00.160
<v Speaker 1>narrowly defined enough to make it meaningful. For example, you

0:14:00.160 --> 0:14:04.400
<v Speaker 1>talk about operators of critical infrastructure, um, they there are

0:14:04.440 --> 0:14:07.400
<v Speaker 1>some people who say that that's not specific enough. You know,

0:14:07.480 --> 0:14:10.720
<v Speaker 1>you don't you know how what? What? What is infrastructure?

0:14:11.160 --> 0:14:13.760
<v Speaker 1>Are we talking? Are we talking just things like power grids?

0:14:14.240 --> 0:14:16.959
<v Speaker 1>I mean that would clearly be critical infrastructure. Does it

0:14:17.040 --> 0:14:20.480
<v Speaker 1>extend to UH to telephones, does it extend to dams?

0:14:20.640 --> 0:14:24.800
<v Speaker 1>Or doesn't extend to UH? To cybersecurity firms? Because if

0:14:24.840 --> 0:14:27.440
<v Speaker 1>you're talking about something now that where you're really trying

0:14:27.480 --> 0:14:30.360
<v Speaker 1>to protect people from cyber attacks, does that mean does

0:14:30.360 --> 0:14:33.720
<v Speaker 1>that extend to the point that cybersecurity firms become part

0:14:33.720 --> 0:14:37.880
<v Speaker 1>of this critical infrastructure because they are the protection against

0:14:37.960 --> 0:14:41.000
<v Speaker 1>that sort of thing. Um. I'm sure that those kind

0:14:41.040 --> 0:14:43.240
<v Speaker 1>of definitions will be worked out. And sometimes this sort

0:14:43.240 --> 0:14:46.880
<v Speaker 1>of legislation or these executive orders I should say, not

0:14:46.880 --> 0:14:49.360
<v Speaker 1>not legislation, but this executive order. And sometimes these things

0:14:49.400 --> 0:14:53.000
<v Speaker 1>are are vaguely worded on purpose to try and have

0:14:53.040 --> 0:14:56.040
<v Speaker 1>the broadest possible application, and then you narrow it down

0:14:56.160 --> 0:14:58.200
<v Speaker 1>as it's put into practice. And that's the feeling that

0:14:58.240 --> 0:15:00.200
<v Speaker 1>I get from this, and especially since they're kind up

0:15:00.200 --> 0:15:03.280
<v Speaker 1>going like, yeah, do this thing and you work it out. Yeah.

0:15:03.320 --> 0:15:05.480
<v Speaker 1>So I'm gonna go through a little bit kind of

0:15:05.520 --> 0:15:07.760
<v Speaker 1>point by point of some of the sections here, and

0:15:07.800 --> 0:15:10.480
<v Speaker 1>then after I do that, we'll we'll kind of talk

0:15:10.520 --> 0:15:13.560
<v Speaker 1>about some of the the not just criticisms, but just

0:15:13.600 --> 0:15:17.000
<v Speaker 1>some of the observations people have made about this. So,

0:15:17.000 --> 0:15:20.440
<v Speaker 1>so it begins by talking about distributing reports of detected

0:15:20.480 --> 0:15:24.400
<v Speaker 1>cyber security threats to private sector companies as long as

0:15:24.400 --> 0:15:28.240
<v Speaker 1>those reports do not endanger investigations and law enforcement efforts

0:15:28.320 --> 0:15:31.600
<v Speaker 1>and they are unclassified. So, in other words, when the

0:15:31.640 --> 0:15:34.520
<v Speaker 1>government gets, say a report that there's a threat, a

0:15:34.600 --> 0:15:39.160
<v Speaker 1>cyber threat, uh, this is what would allow the government

0:15:39.200 --> 0:15:43.000
<v Speaker 1>to send that information out to the various parties that

0:15:43.120 --> 0:15:45.920
<v Speaker 1>could be affected by this cyber threat and to kind

0:15:45.920 --> 0:15:48.680
<v Speaker 1>of give them a heads up saying, look, we've detected

0:15:48.720 --> 0:15:53.840
<v Speaker 1>that there's some operation in let's say China, whether it's

0:15:54.000 --> 0:15:56.800
<v Speaker 1>state backed or it's a group of hackers who are

0:15:56.840 --> 0:15:58.800
<v Speaker 1>working on their own or whatever, or maybe it's a

0:15:59.240 --> 0:16:01.800
<v Speaker 1>Russian group that looks like it's working out of China.

0:16:02.680 --> 0:16:04.960
<v Speaker 1>This is complicated. We can't really be sure because the

0:16:04.960 --> 0:16:08.000
<v Speaker 1>way the internet works in the way hackers get around

0:16:08.000 --> 0:16:10.440
<v Speaker 1>this sort of thing. But they've detected that there's this

0:16:10.520 --> 0:16:13.520
<v Speaker 1>credible threat, and they've detected what the potential targets are.

0:16:13.880 --> 0:16:16.360
<v Speaker 1>This part of the executive order gives the government the

0:16:16.400 --> 0:16:19.640
<v Speaker 1>ability to say, hey, heads up, it's coming in. And

0:16:19.680 --> 0:16:22.880
<v Speaker 1>this is actually an expansion of a currently existing program

0:16:23.120 --> 0:16:28.040
<v Speaker 1>um called the Defense Industrial Based Information Sharing Program, which

0:16:28.120 --> 0:16:31.360
<v Speaker 1>I believe currently exists to allow government contractors to receive

0:16:31.440 --> 0:16:34.680
<v Speaker 1>real time reports about these threats. Right, and so again,

0:16:34.880 --> 0:16:38.440
<v Speaker 1>the reason why they say it can't endanger investigations is clearly,

0:16:38.480 --> 0:16:42.760
<v Speaker 1>if there's a like UH and a law enforcement group,

0:16:42.760 --> 0:16:45.280
<v Speaker 1>whether it's it's the United States or it could be

0:16:45.400 --> 0:16:50.960
<v Speaker 1>some UH international type of UH law enforcement group looking

0:16:51.000 --> 0:16:55.400
<v Speaker 1>into the problem, then by sharing information, you could compromise

0:16:55.560 --> 0:16:59.280
<v Speaker 1>that that investigation. So it's a delicate thing. It's it's

0:16:59.320 --> 0:17:01.480
<v Speaker 1>not something where every single time there's going to be

0:17:01.480 --> 0:17:03.680
<v Speaker 1>a threat, there's automatically going to be a report generator

0:17:03.720 --> 0:17:05.600
<v Speaker 1>that gets sent out. It's going to be a case

0:17:05.640 --> 0:17:09.960
<v Speaker 1>by case basis. The next section talks about how classified

0:17:10.000 --> 0:17:13.800
<v Speaker 1>reports will go to critical infrastructure entities that are authorized

0:17:13.840 --> 0:17:17.840
<v Speaker 1>to receive them. So there will be some privately held

0:17:17.880 --> 0:17:22.840
<v Speaker 1>companies that will be authorized to receive classified information, assuming

0:17:22.840 --> 0:17:25.920
<v Speaker 1>that classified information relates to that entity in some way.

0:17:26.040 --> 0:17:27.840
<v Speaker 1>I think it's also talking a little bit about trying

0:17:27.840 --> 0:17:33.520
<v Speaker 1>to expedite the process of getting clearances for appropriate uh

0:17:33.880 --> 0:17:37.760
<v Speaker 1>A individuals and also state and government representatives to give

0:17:37.880 --> 0:17:40.560
<v Speaker 1>that stuff. Yeah, exactly, yes. So this this again is

0:17:40.600 --> 0:17:42.919
<v Speaker 1>kind of like cutting away some of the red tape

0:17:43.400 --> 0:17:47.159
<v Speaker 1>that would exist between information and the and the entity

0:17:47.240 --> 0:17:50.119
<v Speaker 1>that would most benefit from receiving it, uh in a

0:17:50.240 --> 0:17:53.760
<v Speaker 1>in a cyber attack kind of situation. It would also

0:17:53.840 --> 0:17:57.600
<v Speaker 1>expand the Enhanced Cyber Security Services Program to all critical

0:17:57.640 --> 0:18:03.360
<v Speaker 1>infrastructure sectors, which is a voluntary information sharing program and

0:18:03.440 --> 0:18:05.840
<v Speaker 1>it offers this is where you were talking about, it's

0:18:05.840 --> 0:18:08.560
<v Speaker 1>offering the cross fight info to the private sector folks,

0:18:08.600 --> 0:18:12.520
<v Speaker 1>but also it's a sharing program that is supposed to

0:18:12.640 --> 0:18:18.280
<v Speaker 1>encourage companies to share information between each other to say, uh,

0:18:18.320 --> 0:18:22.000
<v Speaker 1>there's this cyber attack that we've we've detected and it

0:18:22.040 --> 0:18:25.280
<v Speaker 1>could affect your industry as well as ours. So the

0:18:25.320 --> 0:18:28.520
<v Speaker 1>idea is that it's supposed to encourage these companies to participate,

0:18:28.560 --> 0:18:32.280
<v Speaker 1>but it is voluntary. We'll get into that when we

0:18:32.320 --> 0:18:37.280
<v Speaker 1>get into the criticisms. Um Also, beyond the security clearance

0:18:37.320 --> 0:18:41.240
<v Speaker 1>being expedited, we have private sector experts will be invited

0:18:41.359 --> 0:18:43.840
<v Speaker 1>to come and speak to the government on a regular

0:18:43.880 --> 0:18:46.399
<v Speaker 1>basis to keep the government informed about cyber risks and

0:18:46.480 --> 0:18:49.040
<v Speaker 1>the best practices to respond to them. Now, this is

0:18:49.119 --> 0:18:51.520
<v Speaker 1>essentially the part of the executive Order that recognizes the

0:18:51.520 --> 0:18:54.280
<v Speaker 1>fact that the people who hold positions of power in

0:18:54.359 --> 0:19:01.000
<v Speaker 1>politics may not be technologically qualified. They maybe savvy, but

0:19:01.080 --> 0:19:05.000
<v Speaker 1>even a technologically savvy person would not necessarily be up

0:19:05.000 --> 0:19:08.200
<v Speaker 1>to date on the latest cyber threats. And so this

0:19:08.280 --> 0:19:11.080
<v Speaker 1>is this is to give the government the chance to

0:19:11.720 --> 0:19:17.879
<v Speaker 1>maintain a an ongoing dialogue with experts in the cybersecurity

0:19:17.920 --> 0:19:21.399
<v Speaker 1>field so that the best policies are formed as a result,

0:19:21.440 --> 0:19:23.560
<v Speaker 1>and that the best practices are formed as a result,

0:19:23.600 --> 0:19:26.679
<v Speaker 1>because what works today may not work in three months.

0:19:26.840 --> 0:19:31.240
<v Speaker 1>It's a funny thing about technology. And then, uh, the

0:19:31.840 --> 0:19:35.879
<v Speaker 1>next section is the one that's all about privacy and

0:19:35.920 --> 0:19:39.680
<v Speaker 1>civil liberties because apparent that it's it's a really big

0:19:39.720 --> 0:19:42.199
<v Speaker 1>issue in the idea that a lot of these companies

0:19:42.240 --> 0:19:45.200
<v Speaker 1>have a lot of our data, not just corporate data,

0:19:45.240 --> 0:19:48.720
<v Speaker 1>but our personal data. So think about it like power companies,

0:19:48.760 --> 0:19:53.040
<v Speaker 1>gas companies. Uh, you've got you've got credit card companies.

0:19:53.080 --> 0:19:55.480
<v Speaker 1>You should you know, all sorts of vendors out there

0:19:55.520 --> 0:20:00.800
<v Speaker 1>have information, social networking companies, all of these have personal

0:20:00.840 --> 0:20:05.119
<v Speaker 1>information that could put citizens at risk if that information

0:20:05.160 --> 0:20:08.840
<v Speaker 1>were shared to a broader audience. So that's the part

0:20:08.840 --> 0:20:12.520
<v Speaker 1>where the executive Order says, Okay, we want this culture

0:20:12.760 --> 0:20:15.000
<v Speaker 1>of sharing. We want to be able to get the

0:20:15.040 --> 0:20:17.399
<v Speaker 1>information to where it needs to be so that we

0:20:17.440 --> 0:20:20.360
<v Speaker 1>can protect ourselves, but we don't want to do that

0:20:20.520 --> 0:20:24.639
<v Speaker 1>at the expense of personal privacy and civil liberties. We

0:20:24.680 --> 0:20:29.360
<v Speaker 1>don't want to violate anyone's privacy or expectation to privacy. Um,

0:20:29.400 --> 0:20:32.719
<v Speaker 1>so we don't want a credit card company to send

0:20:32.960 --> 0:20:36.919
<v Speaker 1>information to some other entity that just so happens to

0:20:37.000 --> 0:20:41.240
<v Speaker 1>have the the all the credit card numbers, names, addresses,

0:20:41.280 --> 0:20:44.000
<v Speaker 1>credit scores of everyone who's a customer with that credit

0:20:44.040 --> 0:20:47.320
<v Speaker 1>card company, because that would be a bad thing. And

0:20:47.440 --> 0:20:49.560
<v Speaker 1>so one of the things that this this requires is

0:20:49.640 --> 0:20:54.520
<v Speaker 1>a regular assessments in public reporting of any kind of mishaps. Yeah,

0:20:54.600 --> 0:20:57.879
<v Speaker 1>so it's an ongoing dialogue again with the government to

0:20:57.920 --> 0:21:02.080
<v Speaker 1>make sure that this is done an appropriate way, because

0:21:02.160 --> 0:21:06.040
<v Speaker 1>I mean, obviously, when when people start to worry about security.

0:21:06.400 --> 0:21:10.120
<v Speaker 1>It's it can be I won't say easy, but it's

0:21:10.160 --> 0:21:13.960
<v Speaker 1>possible that you overlook other concerns that you should really

0:21:14.160 --> 0:21:16.919
<v Speaker 1>take into mind when you're trying to protect yourself. We

0:21:17.240 --> 0:21:20.080
<v Speaker 1>we usually see this in the wake of some sort

0:21:20.119 --> 0:21:24.080
<v Speaker 1>of actual attack, where an attack happens and then we

0:21:24.160 --> 0:21:25.879
<v Speaker 1>just want to respond to that and make sure it

0:21:25.920 --> 0:21:30.400
<v Speaker 1>doesn't happen again. And you can easily set aside other

0:21:30.480 --> 0:21:32.199
<v Speaker 1>concerns that you really need to keep in mind the

0:21:32.200 --> 0:21:34.840
<v Speaker 1>whole time. Well, before we move on to the rest

0:21:34.920 --> 0:21:37.159
<v Speaker 1>of the executive Order, I think now would be a

0:21:37.160 --> 0:21:40.320
<v Speaker 1>good time to take a quick break and thank our sponsor,

0:21:40.800 --> 0:21:43.880
<v Speaker 1>and now back to the show. So the next section

0:21:45.040 --> 0:21:50.000
<v Speaker 1>is all about consulting and getting various departments to talk

0:21:50.040 --> 0:21:52.960
<v Speaker 1>to each other to improve security measures, so when one

0:21:53.200 --> 0:21:57.119
<v Speaker 1>group sees something that's working, it can communicate that with

0:21:57.160 --> 0:21:59.320
<v Speaker 1>other groups. It's kind of it's kind of this idea

0:21:59.359 --> 0:22:05.280
<v Speaker 1>of UH inciting cooperation between departments and other entities. Then

0:22:05.560 --> 0:22:08.800
<v Speaker 1>there's a section. I've got a direct quote here, and

0:22:09.640 --> 0:22:12.920
<v Speaker 1>the Secretary of Commerce shall direct the Director of the

0:22:13.040 --> 0:22:18.320
<v Speaker 1>National Institute of Standards and Technology UH for here. Henceford

0:22:18.359 --> 0:22:21.600
<v Speaker 1>known as a director to lead the development of a

0:22:21.680 --> 0:22:26.240
<v Speaker 1>framework to reduce cyber risks to critical infrastructure, henceforth known

0:22:26.280 --> 0:22:30.280
<v Speaker 1>as the cybersecurity Framework. The cybersecurity Framework shall include a

0:22:30.280 --> 0:22:35.320
<v Speaker 1>set of standards, methodologies, procedures, and processes that align policy, business,

0:22:35.359 --> 0:22:39.879
<v Speaker 1>and technological approaches to address cyber risks. That's essentially saying

0:22:40.359 --> 0:22:43.760
<v Speaker 1>you have to take everything into consideration and make it

0:22:43.880 --> 0:22:48.440
<v Speaker 1>into a cyber security approach that takes all of that

0:22:48.520 --> 0:22:51.640
<v Speaker 1>into account and works, which is huge. I mean, that's

0:22:51.640 --> 0:22:57.720
<v Speaker 1>just incredibly complex. I mean, policy alone is complicated, yes,

0:22:57.800 --> 0:23:00.160
<v Speaker 1>a little bit. And then you've got technology, which is

0:23:00.520 --> 0:23:05.120
<v Speaker 1>constantly evolving. So what by the time you're finished drafting

0:23:05.119 --> 0:23:11.480
<v Speaker 1>a policy, it may be that the technology has so Now, granted,

0:23:11.920 --> 0:23:14.760
<v Speaker 1>I'm not blaming anyone for this, because it's just that's

0:23:14.800 --> 0:23:18.320
<v Speaker 1>just how reality is. And I don't know how else

0:23:18.320 --> 0:23:20.640
<v Speaker 1>you could word this in a way that would make

0:23:20.720 --> 0:23:23.080
<v Speaker 1>sense and and get across the importance of what needs

0:23:23.119 --> 0:23:24.600
<v Speaker 1>to be done. Yeah, and and that is that is

0:23:24.600 --> 0:23:26.480
<v Speaker 1>a good I mean, I feel like they've got enough

0:23:26.520 --> 0:23:28.679
<v Speaker 1>of a cautionary air about it that it's not just

0:23:28.760 --> 0:23:30.600
<v Speaker 1>you know, they're not just sitting there quoting Tim Gotten

0:23:30.600 --> 0:23:33.760
<v Speaker 1>going well, make it work. But yeah, yeah, but it

0:23:33.840 --> 0:23:37.120
<v Speaker 1>does kind of start to set in how enormous this

0:23:37.160 --> 0:23:40.399
<v Speaker 1>issue is. It's also enormously important, So I'm very glad

0:23:40.440 --> 0:23:42.919
<v Speaker 1>that the government is looking into it, and they have

0:23:43.080 --> 0:23:45.760
<v Speaker 1>been looking into it. That whould also I'm sure we

0:23:45.920 --> 0:23:48.280
<v Speaker 1>kind of alluded to it already. This is not the

0:23:48.320 --> 0:23:51.320
<v Speaker 1>first time the government has looked at cybersecurity, but it's

0:23:51.440 --> 0:23:53.760
<v Speaker 1>it's you know, they're seeing it as it's just going

0:23:53.800 --> 0:23:56.960
<v Speaker 1>to get increasingly important as time goes on. Next, they

0:23:57.080 --> 0:24:02.080
<v Speaker 1>said that the Cybersecurity Framework shall provide a poritized, flexible, repeatable,

0:24:02.080 --> 0:24:06.840
<v Speaker 1>performance based and cost effective approach, including information security measures

0:24:06.840 --> 0:24:10.840
<v Speaker 1>and controls, to help owners and operators of critical infrastructure, identify, assess,

0:24:10.920 --> 0:24:15.000
<v Speaker 1>and manage cyber risk. This is also a huge thing.

0:24:15.119 --> 0:24:16.879
<v Speaker 1>I mean, it's it's it's a it's a tall order

0:24:16.960 --> 0:24:20.680
<v Speaker 1>because you're talking about an approach that is going to

0:24:20.680 --> 0:24:25.560
<v Speaker 1>work in The approach ideally should work in every case

0:24:25.720 --> 0:24:30.600
<v Speaker 1>across multiple industries, because the idea of it being repeatable

0:24:30.680 --> 0:24:33.840
<v Speaker 1>means that it can't be something that, oh, because this

0:24:34.080 --> 0:24:37.640
<v Speaker 1>threat was the specific to this industry, then it can't

0:24:37.680 --> 0:24:40.480
<v Speaker 1>work for over here and or or even just that

0:24:40.840 --> 0:24:43.720
<v Speaker 1>because our approach work for this threat but the reason

0:24:43.760 --> 0:24:45.800
<v Speaker 1>why it worked for this threat was because of x

0:24:46.400 --> 0:24:49.119
<v Speaker 1>uh that you know, that might mean that it's not repeatable.

0:24:49.200 --> 0:24:51.680
<v Speaker 1>So it's a very challenging thing. Again, I'm not saying

0:24:51.720 --> 0:24:54.320
<v Speaker 1>it's impossible, but you know, and again and there's not

0:24:54.400 --> 0:24:56.199
<v Speaker 1>much they could What else are they gonna say, like

0:24:56.800 --> 0:24:59.680
<v Speaker 1>produce an infinite number of responses that can work in

0:25:00.000 --> 0:25:02.480
<v Speaker 1>any given situation, depending upon which response you're using in

0:25:02.520 --> 0:25:04.399
<v Speaker 1>which industry. I mean, that just wouldn't work. Oh no, no,

0:25:04.560 --> 0:25:06.399
<v Speaker 1>And they do talk a lot about scaling. They want

0:25:06.440 --> 0:25:07.959
<v Speaker 1>to make sure that this is going to work just

0:25:08.000 --> 0:25:11.000
<v Speaker 1>as well for for small small companies as well as

0:25:11.040 --> 0:25:14.280
<v Speaker 1>big companies, and yeah, across the board. But that just

0:25:14.320 --> 0:25:16.199
<v Speaker 1>makes it harder. Yeah, yeah, in fact, and then the

0:25:16.240 --> 0:25:18.800
<v Speaker 1>next section says, you gotta do all this without impacting

0:25:18.800 --> 0:25:22.840
<v Speaker 1>business and privacy. So you have to come up with

0:25:22.960 --> 0:25:26.680
<v Speaker 1>a way to protect our businesses and our infrastructure in

0:25:27.040 --> 0:25:29.200
<v Speaker 1>such a way that it's not going to negatively impact

0:25:29.200 --> 0:25:32.000
<v Speaker 1>those businesses. So you can't come up with a plan

0:25:32.480 --> 0:25:35.879
<v Speaker 1>that protects everyone, but it ends up taking a cut

0:25:35.920 --> 0:25:39.159
<v Speaker 1>of everyone's profits because they have to do spend so

0:25:39.200 --> 0:25:41.440
<v Speaker 1>many work hours doing this thing. Oh you know, which

0:25:41.520 --> 0:25:45.120
<v Speaker 1>is why the Republicans last year filibustered that last Act

0:25:45.200 --> 0:25:47.880
<v Speaker 1>and and and it's tough, I mean uh. And we'll

0:25:47.880 --> 0:25:50.560
<v Speaker 1>get into more about wine stuff in a second. Also,

0:25:50.680 --> 0:25:53.000
<v Speaker 1>the that's where they introduced the idea of the open

0:25:53.040 --> 0:25:57.200
<v Speaker 1>public review and comment process so that this becomes an

0:25:57.280 --> 0:26:01.320
<v Speaker 1>evolving policy over time, which again I'm very glad that

0:26:01.400 --> 0:26:03.679
<v Speaker 1>kind of stuff is built into this executive order. It

0:26:03.800 --> 0:26:07.879
<v Speaker 1>recognizes that this is a problem that is going to

0:26:08.000 --> 0:26:11.840
<v Speaker 1>change over time, and you cannot create a policy and

0:26:11.960 --> 0:26:15.040
<v Speaker 1>expected to be evergreen, and that it's going to that

0:26:15.119 --> 0:26:18.560
<v Speaker 1>one approach once you've once you've established it is going

0:26:18.600 --> 0:26:22.320
<v Speaker 1>to work forever. This is the sort of interesting because

0:26:22.320 --> 0:26:25.119
<v Speaker 1>there are other policies that were created back when the

0:26:25.160 --> 0:26:29.280
<v Speaker 1>telephone industry was first coming into prominence that still affect

0:26:29.280 --> 0:26:32.000
<v Speaker 1>how the Internet works today. And there are a lot

0:26:32.040 --> 0:26:35.440
<v Speaker 1>of people who who protest that. They say, look, these

0:26:35.480 --> 0:26:39.240
<v Speaker 1>were policies that were made for a much older telecommunications

0:26:39.280 --> 0:26:42.800
<v Speaker 1>network that could do a very limited number of things,

0:26:43.160 --> 0:26:45.840
<v Speaker 1>and now you're applying it to a much more complex

0:26:45.880 --> 0:26:49.879
<v Speaker 1>system that is far more sophisticated, and the implications for

0:26:49.960 --> 0:26:53.920
<v Speaker 1>how it works are far more complicated. Expecting those rules

0:26:53.960 --> 0:26:57.560
<v Speaker 1>to apply to this thing is unrealistic, and you've got

0:26:57.560 --> 0:27:00.280
<v Speaker 1>a lot of that kind of discussion going on, mostly

0:27:00.400 --> 0:27:03.199
<v Speaker 1>in in uh interest groups that like you know that

0:27:03.280 --> 0:27:07.920
<v Speaker 1>are forming up about protecting the Internet. But um, anyway,

0:27:07.960 --> 0:27:09.680
<v Speaker 1>that's that's kind of a similar thing like that. It

0:27:09.800 --> 0:27:12.840
<v Speaker 1>built into this is saying let's have this ongoing public

0:27:12.880 --> 0:27:17.440
<v Speaker 1>discourse so that we can avoid this if if possible,

0:27:17.440 --> 0:27:20.200
<v Speaker 1>it's gonna be you know, we're gonna see it anyway,

0:27:20.280 --> 0:27:22.680
<v Speaker 1>because it's impossible to avoid it completely, but at least

0:27:22.720 --> 0:27:26.879
<v Speaker 1>they're looking into that. Then you've got the Latin next

0:27:27.600 --> 0:27:30.159
<v Speaker 1>section where it says the Secretary and coordination with sector

0:27:30.240 --> 0:27:33.720
<v Speaker 1>specific agencies, shall establish a voluntary program to support the

0:27:33.760 --> 0:27:36.399
<v Speaker 1>adoption of the Cybersecurity Framework by owners and operators of

0:27:36.400 --> 0:27:39.639
<v Speaker 1>critical infrastructure and any other interested entities to get a

0:27:40.000 --> 0:27:45.840
<v Speaker 1>the program. Um, here's that voluntary program bit again. Okay,

0:27:46.880 --> 0:27:49.159
<v Speaker 1>I'll say that just until I finished this last one.

0:27:49.160 --> 0:27:52.240
<v Speaker 1>Here's my last point. Within one fifty days of the

0:27:52.359 --> 0:27:54.640
<v Speaker 1>date of this order, the Secretary shall use a risk

0:27:54.720 --> 0:27:58.760
<v Speaker 1>based approach to identify critical infrastructure where cybersecurity incident could

0:27:58.760 --> 0:28:02.000
<v Speaker 1>reasonably result and kind strophic, regional, or national effects on

0:28:02.040 --> 0:28:06.440
<v Speaker 1>public health or safety, economic security, or national security entities

0:28:06.480 --> 0:28:10.359
<v Speaker 1>identified as such can then appeal that. So, in other words,

0:28:10.640 --> 0:28:14.560
<v Speaker 1>if you are the head of a company and the

0:28:14.640 --> 0:28:17.600
<v Speaker 1>United States government government starts to look at all the

0:28:17.600 --> 0:28:20.680
<v Speaker 1>companies that are part of this infrastructure and they identify

0:28:20.720 --> 0:28:25.160
<v Speaker 1>your company as being one of these incredibly critical Yes,

0:28:25.359 --> 0:28:28.120
<v Speaker 1>not like it's critical because of the services you provide

0:28:28.480 --> 0:28:30.640
<v Speaker 1>and the likelihood that you would be a target for

0:28:30.840 --> 0:28:35.120
<v Speaker 1>a cyber attack. Um, then they could designate you as

0:28:35.119 --> 0:28:38.680
<v Speaker 1>such and you would be able to appeal because if

0:28:38.760 --> 0:28:42.720
<v Speaker 1>you are one of these critical infrastructure entities, you're going

0:28:42.760 --> 0:28:45.440
<v Speaker 1>to have to jump through a lot more hoops than

0:28:45.480 --> 0:28:48.720
<v Speaker 1>you would if you were not. So companies actually kind

0:28:48.760 --> 0:28:50.920
<v Speaker 1>of have an incentive to not be one of these

0:28:50.960 --> 0:28:53.640
<v Speaker 1>things because then they if they are one, they're going

0:28:53.640 --> 0:28:57.960
<v Speaker 1>to have to conform to more UH specific policies. Right

0:28:58.000 --> 0:29:02.440
<v Speaker 1>because they are considered critical elements of the infrastructure. It

0:29:02.440 --> 0:29:05.640
<v Speaker 1>takes that sticky voluntary term a little bit out of it. Yeah,

0:29:05.720 --> 0:29:08.680
<v Speaker 1>it does, because if they say, hey, no, really, really

0:29:09.680 --> 0:29:12.760
<v Speaker 1>you you are super important and if you go down,

0:29:12.840 --> 0:29:15.400
<v Speaker 1>then the United States is in a lot of trouble.

0:29:15.560 --> 0:29:18.600
<v Speaker 1>So you are part of this critical infrastructure, whether you

0:29:18.640 --> 0:29:20.920
<v Speaker 1>like it or not. So therefore, because of this, we

0:29:20.960 --> 0:29:24.400
<v Speaker 1>need you to follow these directions. Uh, and other companies

0:29:24.520 --> 0:29:26.440
<v Speaker 1>might be like, you know, I'd really like it if

0:29:26.480 --> 0:29:28.400
<v Speaker 1>I had more of a choice, because then I could

0:29:28.440 --> 0:29:30.800
<v Speaker 1>choose not to do that, and that would be awesome.

0:29:31.160 --> 0:29:34.160
<v Speaker 1>So that's why there's that appeal process, and that's where

0:29:34.160 --> 0:29:37.520
<v Speaker 1>we come to the problem with the voluntary nature of

0:29:37.720 --> 0:29:41.719
<v Speaker 1>much of this policy. The idea here is that again

0:29:41.840 --> 0:29:45.760
<v Speaker 1>we don't in the United States in particular, there's there's

0:29:45.760 --> 0:29:50.600
<v Speaker 1>a stigma against the government and private business. And and

0:29:50.680 --> 0:29:53.680
<v Speaker 1>I'm not saying that it's unwarranted. I'm not saying that

0:29:53.720 --> 0:29:56.680
<v Speaker 1>we should have a socialist country where every single business

0:29:56.760 --> 0:29:59.760
<v Speaker 1>is owned, at least in part or operated by the government.

0:29:59.840 --> 0:30:01.720
<v Speaker 1>That that's not what I'm saying at all. What I'm

0:30:01.720 --> 0:30:04.080
<v Speaker 1>saying is that it does mean that in order to

0:30:04.160 --> 0:30:09.880
<v Speaker 1>preserve this very important, very American idea of private business,

0:30:10.160 --> 0:30:12.960
<v Speaker 1>we don't let the government just come in and take

0:30:13.000 --> 0:30:15.960
<v Speaker 1>over and regulate us or or protect us to a

0:30:15.960 --> 0:30:18.000
<v Speaker 1>certain point. I mean, it's sort of our business. Yeah,

0:30:18.000 --> 0:30:21.600
<v Speaker 1>So there's there's a delicate nature here, and it's again

0:30:21.720 --> 0:30:23.640
<v Speaker 1>it's one of those things where it's it's a very

0:30:23.680 --> 0:30:28.600
<v Speaker 1>American approach and it's it's tough to work something like

0:30:28.640 --> 0:30:32.040
<v Speaker 1>cybersecurity in there and not make it a voluntary program,

0:30:32.040 --> 0:30:34.840
<v Speaker 1>because if we made it mandatory, the government would essentially

0:30:34.880 --> 0:30:37.720
<v Speaker 1>be saying, look, we're not telling you how to sell

0:30:37.800 --> 0:30:40.280
<v Speaker 1>your widgets, but we aren't telling you how to protect

0:30:40.320 --> 0:30:43.800
<v Speaker 1>your network. And that gets complicated. Even even if it's

0:30:43.880 --> 0:30:48.000
<v Speaker 1>for the greater good, it's it's a it's a tough thing.

0:30:48.080 --> 0:30:51.600
<v Speaker 1>And I mean I certainly if I owned a big business,

0:30:51.680 --> 0:30:54.600
<v Speaker 1>I would be thinking, look, I don't want to have

0:30:54.760 --> 0:30:58.080
<v Speaker 1>yet another set of policies that I have to uh,

0:30:58.120 --> 0:31:00.680
<v Speaker 1>I have to keep up with and follow up with

0:31:00.800 --> 0:31:02.959
<v Speaker 1>and spend my time and money taking care of. Right.

0:31:02.960 --> 0:31:05.520
<v Speaker 1>I don't want to get certified every couple of years

0:31:05.560 --> 0:31:08.160
<v Speaker 1>to make sure that I'm following this. Let me do

0:31:08.240 --> 0:31:10.800
<v Speaker 1>it on my own. It's in my best interest to

0:31:10.880 --> 0:31:13.600
<v Speaker 1>make sure that I'm not going to get attacked anyway. Yeah, exactly.

0:31:13.640 --> 0:31:17.440
<v Speaker 1>That's that's the business owner perspective is saying, look, I

0:31:17.440 --> 0:31:19.640
<v Speaker 1>don't want to get attacked because if I get attacked,

0:31:19.720 --> 0:31:22.600
<v Speaker 1>it hurts my bottom line. So I have I have

0:31:22.720 --> 0:31:29.360
<v Speaker 1>a market driven reason to prevent attacks. But the on

0:31:29.400 --> 0:31:31.920
<v Speaker 1>the flip side of that, the United States is saying, look,

0:31:31.920 --> 0:31:35.480
<v Speaker 1>these attacks are sophisticated, they're coming from multiple points, they

0:31:35.520 --> 0:31:40.160
<v Speaker 1>are using different methods to attack different systems, and in

0:31:40.200 --> 0:31:42.760
<v Speaker 1>some cases it may just be that your company isn't

0:31:42.840 --> 0:31:46.200
<v Speaker 1>a specific target, but it's part of a larger group

0:31:46.200 --> 0:31:50.000
<v Speaker 1>of targets, and we have to protect the United States citizens.

0:31:50.040 --> 0:31:53.280
<v Speaker 1>So there's their valid arguments on either side. Now, making

0:31:53.280 --> 0:31:57.160
<v Speaker 1>it a voluntary program helps both parties because the government

0:31:57.200 --> 0:32:00.200
<v Speaker 1>isn't saying, look, you have to follow this out of

0:32:00.280 --> 0:32:03.160
<v Speaker 1>rules or you can't do business in the the United States,

0:32:03.440 --> 0:32:06.600
<v Speaker 1>and the business can say, well, do we want to

0:32:06.640 --> 0:32:09.160
<v Speaker 1>be part of this so that we can help protect

0:32:09.240 --> 0:32:13.120
<v Speaker 1>our business as well as make sure that in our

0:32:13.160 --> 0:32:15.760
<v Speaker 1>own lives we don't go home and the power goes

0:32:15.760 --> 0:32:18.000
<v Speaker 1>off right right. And this is actually kind of in

0:32:18.040 --> 0:32:21.400
<v Speaker 1>contrast to UH. Interestingly enough, the European Commission also just

0:32:21.480 --> 0:32:25.440
<v Speaker 1>in this past week released a bunch of cybersecurity stuff

0:32:26.560 --> 0:32:29.040
<v Speaker 1>UM and and and there sounds like it might be

0:32:29.080 --> 0:32:31.960
<v Speaker 1>a little bit more mandatory. They want to introduce a

0:32:32.000 --> 0:32:36.440
<v Speaker 1>Computer Emergency Response Team a k A CERT to UH,

0:32:36.640 --> 0:32:40.560
<v Speaker 1>introduce laws compelling companies to disclose attack details to to

0:32:40.680 --> 0:32:44.200
<v Speaker 1>this national authority and and that this each each sert

0:32:44.440 --> 0:32:48.840
<v Speaker 1>would be responsible for defending these companies against attack, so

0:32:49.480 --> 0:32:50.760
<v Speaker 1>you know, and and it's it's it's in a little

0:32:50.760 --> 0:32:52.600
<v Speaker 1>bit more of of a planning stage, I think, than

0:32:53.040 --> 0:32:58.760
<v Speaker 1>than what Obama's orders outlining. But it is nonetheless, you know,

0:32:59.360 --> 0:33:02.120
<v Speaker 1>just just a little bit of contrast there. See, I

0:33:02.240 --> 0:33:06.480
<v Speaker 1>just wonder if the CERTs are a breath mint or

0:33:06.520 --> 0:33:10.120
<v Speaker 1>a candy mint. That's the first thing I thought. As

0:33:10.160 --> 0:33:12.880
<v Speaker 1>soon as you said certain, my brain turned off. These

0:33:12.920 --> 0:33:16.920
<v Speaker 1>are the deep questions that we ask here on tax staffs.

0:33:17.040 --> 0:33:19.840
<v Speaker 1>Shows you how Jonathan Strickland works, which is that he

0:33:19.960 --> 0:33:24.800
<v Speaker 1>is distracted by shiny things and puns and mints and mints. Yeah,

0:33:24.840 --> 0:33:30.160
<v Speaker 1>they are intensely flavorful. So yeah, I mean that voluntary

0:33:30.200 --> 0:33:31.920
<v Speaker 1>approach is one of the things that some people are

0:33:31.960 --> 0:33:37.760
<v Speaker 1>saying makes the Executive Order lack teeth because without without

0:33:38.040 --> 0:33:44.160
<v Speaker 1>really providing strong incentives, companies have no reason to join

0:33:44.280 --> 0:33:47.440
<v Speaker 1>this because because in the long run it will be

0:33:47.480 --> 0:33:52.200
<v Speaker 1>more work to have to conform to whatever the policy requires. Now,

0:33:52.240 --> 0:33:55.000
<v Speaker 1>if the incentives are big enough, whether they're you know,

0:33:55.080 --> 0:33:59.120
<v Speaker 1>tax breaks or whatever, then maybe companies will end up

0:33:59.200 --> 0:34:02.000
<v Speaker 1>joining because they'll think, well, whatever the work is to

0:34:02.360 --> 0:34:05.200
<v Speaker 1>conform to the policy. It's going to be balanced out

0:34:05.240 --> 0:34:08.399
<v Speaker 1>by the incentives. So the incentives, although they haven't been

0:34:08.400 --> 0:34:11.160
<v Speaker 1>really uh you know, they haven't been listed out yet,

0:34:11.400 --> 0:34:16.120
<v Speaker 1>it's possible they could be attractive enough for for companies

0:34:16.160 --> 0:34:18.200
<v Speaker 1>to join this. But that was one of the big

0:34:18.480 --> 0:34:22.320
<v Speaker 1>arguments I saw was that by making it voluntary, although

0:34:22.880 --> 0:34:27.600
<v Speaker 1>every single UM business analysts I saw who said it,

0:34:27.600 --> 0:34:29.480
<v Speaker 1>they said, well, the problem is it's voluntary, so it's

0:34:29.480 --> 0:34:31.279
<v Speaker 1>not gonna work very well. But on the other hand,

0:34:31.280 --> 0:34:34.160
<v Speaker 1>if it were mandatory, everyone would be freaking out. So

0:34:34.920 --> 0:34:38.680
<v Speaker 1>it's almost like there's no right approach, right unless unless

0:34:38.680 --> 0:34:40.960
<v Speaker 1>you're able to provide those amazing incentives you could, you

0:34:40.960 --> 0:34:43.799
<v Speaker 1>cannot make it mandatory and not have everyone riot. Yeah,

0:34:44.000 --> 0:34:47.440
<v Speaker 1>so um. The Also they mentioned that the the this

0:34:47.560 --> 0:34:52.040
<v Speaker 1>framework idea is incredibly complex, and part of that is

0:34:52.080 --> 0:34:54.760
<v Speaker 1>because they're already a lot of security frameworks that government

0:34:54.800 --> 0:34:58.359
<v Speaker 1>agencies have to abide by. So there's and I could

0:34:58.400 --> 0:35:00.919
<v Speaker 1>give you a list of acronyms and not being able

0:35:00.960 --> 0:35:02.680
<v Speaker 1>to tell you what any of them mean, but I'm

0:35:02.719 --> 0:35:06.120
<v Speaker 1>not going to insult you or myself by doing that.

0:35:06.280 --> 0:35:09.359
<v Speaker 1>But there are a lot of security frameworks already and

0:35:09.440 --> 0:35:13.640
<v Speaker 1>so this policy would have to work, uh, in an

0:35:13.680 --> 0:35:17.960
<v Speaker 1>alignment with those, because we've already got these rules that

0:35:17.960 --> 0:35:21.080
<v Speaker 1>that departments in the government have to follow, and so

0:35:21.239 --> 0:35:24.120
<v Speaker 1>unless they were to get rid of all that in

0:35:24.200 --> 0:35:27.120
<v Speaker 1>order to streamline it, this would be yet another set

0:35:27.160 --> 0:35:28.839
<v Speaker 1>of rules. So you think about it. If you've ever

0:35:28.920 --> 0:35:33.840
<v Speaker 1>had more than one boss, like at a time, and

0:35:34.040 --> 0:35:39.120
<v Speaker 1>you have different directions coming from both bosses, and you

0:35:39.160 --> 0:35:41.719
<v Speaker 1>have to figure out how to complete a project that

0:35:41.800 --> 0:35:44.600
<v Speaker 1>follows all of these rules, and some of them contradict

0:35:44.640 --> 0:35:47.359
<v Speaker 1>each other. You know, I've had that. Yeah, that's it

0:35:47.400 --> 0:35:50.560
<v Speaker 1>wasn't fine. I didn't like that. Just a stressful, frustrating experience.

0:35:50.560 --> 0:35:52.920
<v Speaker 1>Now expand that out to an entire government department and

0:35:52.960 --> 0:35:57.360
<v Speaker 1>you understand why they can get a little antsie at times. Um.

0:35:57.520 --> 0:36:02.560
<v Speaker 1>Then also there's still some questions about the privacy implications. Uh.

0:36:02.680 --> 0:36:07.040
<v Speaker 1>While the the executive order does talk about being careful

0:36:07.080 --> 0:36:12.240
<v Speaker 1>about privacy, it doesn't lay out any specifics on the approach,

0:36:12.280 --> 0:36:16.040
<v Speaker 1>and so that always makes people a little nervous. Yeah,

0:36:16.120 --> 0:36:19.840
<v Speaker 1>until until we know the particulars, you can't really be

0:36:19.920 --> 0:36:23.520
<v Speaker 1>sure that your privacy is going to be uh protected. Yeah, yeah,

0:36:24.000 --> 0:36:27.239
<v Speaker 1>it's supposed to be but until until I know the specifics,

0:36:27.280 --> 0:36:28.959
<v Speaker 1>we can't be sure. And are we going to apply

0:36:29.080 --> 0:36:32.799
<v Speaker 1>these same security measures to the to the information to

0:36:32.840 --> 0:36:35.000
<v Speaker 1>get sent out as a result of these security measures,

0:36:35.040 --> 0:36:38.320
<v Speaker 1>because otherwise it's just it's it's a it's a definite

0:36:38.920 --> 0:36:42.720
<v Speaker 1>vicious cycle. Uh. And and just you know again, because

0:36:42.760 --> 0:36:45.080
<v Speaker 1>there's so little detail here, you know, it's it's it's

0:36:45.360 --> 0:36:49.160
<v Speaker 1>putting a lot of of responsibility on these different departments.

0:36:49.560 --> 0:36:52.839
<v Speaker 1>It's hard to say how well this approach will work

0:36:52.880 --> 0:36:56.000
<v Speaker 1>because honestly, we just have the framework of what it's

0:36:56.000 --> 0:36:58.719
<v Speaker 1>supposed to do, not how it's supposed to do it.

0:36:59.280 --> 0:37:01.080
<v Speaker 1>So so it's a little too early for us to

0:37:01.120 --> 0:37:04.320
<v Speaker 1>say whether or not the policy that comes out of this,

0:37:04.440 --> 0:37:06.880
<v Speaker 1>assuming that one does come out of it, will be

0:37:06.920 --> 0:37:08.480
<v Speaker 1>a good one or a bad one. Because when we

0:37:08.520 --> 0:37:11.319
<v Speaker 1>also have to have Congress way in on this. Uh,

0:37:11.360 --> 0:37:14.240
<v Speaker 1>this is an executive order, but if we want laws passed,

0:37:14.280 --> 0:37:18.719
<v Speaker 1>that's when you start looking to Congress. And a lot

0:37:18.760 --> 0:37:21.320
<v Speaker 1>of the issues that have happened in the past few

0:37:21.480 --> 0:37:26.080
<v Speaker 1>years that have to do with security online also seemed

0:37:26.160 --> 0:37:31.960
<v Speaker 1>to involve intellectual property. Um, and that's I think it's

0:37:32.000 --> 0:37:37.960
<v Speaker 1>pretty ugly. I mean, we have and sis, these were

0:37:38.000 --> 0:37:41.640
<v Speaker 1>things that we're not just about protecting the well, that's

0:37:41.640 --> 0:37:44.680
<v Speaker 1>about protecting businesses use it, but not from cyber attacks

0:37:44.680 --> 0:37:46.920
<v Speaker 1>so much as piracy. But you know, that's the kind

0:37:46.920 --> 0:37:48.120
<v Speaker 1>of stuff that we see have and all the time,

0:37:48.120 --> 0:37:50.440
<v Speaker 1>because we've got a lot of powerful interest groups that

0:37:50.600 --> 0:37:55.400
<v Speaker 1>are campaigning very hard with certain members of Congress to

0:37:55.640 --> 0:37:59.920
<v Speaker 1>put forth legislation that would protect their industries and possibly

0:38:00.560 --> 0:38:05.040
<v Speaker 1>hurt uh, innocent users of the Internet as a result,

0:38:05.440 --> 0:38:09.960
<v Speaker 1>mostly through unintended consequences, not necessary, not not on purpose. Yeah,

0:38:10.000 --> 0:38:12.080
<v Speaker 1>I mean, but but but just like the Cyber Intelligence

0:38:12.120 --> 0:38:15.720
<v Speaker 1>Sharing and Protection Act of CISPA UM, you know, failed

0:38:15.800 --> 0:38:18.480
<v Speaker 1>to make it through the Senate. It was because it

0:38:18.520 --> 0:38:21.360
<v Speaker 1>was because basically the White House said, in this form

0:38:21.360 --> 0:38:24.640
<v Speaker 1>we're going to veto it because of privacy issues. Yeah. Yeah, See,

0:38:24.680 --> 0:38:28.040
<v Speaker 1>it's not an easy problem to solve at all. I mean,

0:38:28.080 --> 0:38:31.240
<v Speaker 1>there's there are a lot of mind fields around this problem.

0:38:31.280 --> 0:38:34.759
<v Speaker 1>So if it were just as simple as let's oh,

0:38:34.920 --> 0:38:37.879
<v Speaker 1>here here's your problem. Your firewall for the United States

0:38:37.960 --> 0:38:40.200
<v Speaker 1>wasn't flipped on, let me just turn the switch, then

0:38:40.239 --> 0:38:42.520
<v Speaker 1>that would be great. Unfortunately that's not the not not

0:38:42.640 --> 0:38:45.839
<v Speaker 1>the case. So yeah, it's it's gonna be it's gonna

0:38:45.840 --> 0:38:51.719
<v Speaker 1>be a tough tough act to to enact. Really, it's

0:38:51.719 --> 0:38:54.799
<v Speaker 1>gonna be a tough policy to create because to make

0:38:54.840 --> 0:38:59.000
<v Speaker 1>it effective and yet not violate our privacy or civil

0:38:59.000 --> 0:39:01.759
<v Speaker 1>liberties well or put too much of a burden on

0:39:01.800 --> 0:39:05.400
<v Speaker 1>private business, or not give enough incentive for private business

0:39:05.400 --> 0:39:09.239
<v Speaker 1>to even get involved with it. Um It's it's not

0:39:09.400 --> 0:39:11.880
<v Speaker 1>an easy thing to do, certainly not. And it also

0:39:11.960 --> 0:39:14.520
<v Speaker 1>requires a kind of a base level of just people

0:39:14.560 --> 0:39:16.880
<v Speaker 1>being aware of stuff. I mean, for example, in in

0:39:17.000 --> 0:39:20.080
<v Speaker 1>the news this week. Last week there was that kind

0:39:20.120 --> 0:39:23.360
<v Speaker 1>of hilarious thing where where the emergency alert system was

0:39:23.400 --> 0:39:26.080
<v Speaker 1>hacked in um On, Tanta, Michigan, California, and New Mexico,

0:39:26.120 --> 0:39:29.120
<v Speaker 1>I think, and they sent out that um hacker sent

0:39:29.160 --> 0:39:32.799
<v Speaker 1>out this zombie apocalypse warning. Oh right, right right, I

0:39:32.880 --> 0:39:37.400
<v Speaker 1>remember that. Yeah, the whole emergency alert the deadhead of

0:39:37.480 --> 0:39:39.600
<v Speaker 1>risen from the grave, that kind of thing, right right,

0:39:39.640 --> 0:39:41.919
<v Speaker 1>I think? I think, yeah, gaker, someone reported that four

0:39:41.960 --> 0:39:44.400
<v Speaker 1>people proceeded to freak write the hell out, and they

0:39:44.480 --> 0:39:48.279
<v Speaker 1>definitely called in. Four people called in concern, and of

0:39:48.320 --> 0:39:51.560
<v Speaker 1>course they may have just called in to ask y'all,

0:39:52.160 --> 0:39:54.799
<v Speaker 1>did you get hacked? We don't know. We don't know

0:39:54.840 --> 0:39:56.239
<v Speaker 1>what the nature of the calls were. We just know

0:39:56.320 --> 0:39:58.520
<v Speaker 1>that four people did actually call in. So whether or

0:39:58.520 --> 0:40:01.040
<v Speaker 1>not they were truly worried that the dead had risen

0:40:01.480 --> 0:40:03.680
<v Speaker 1>or they were just wondering what the heck went on,

0:40:04.200 --> 0:40:07.560
<v Speaker 1>we don't know. Right. But supposedly, according to the president

0:40:07.600 --> 0:40:12.280
<v Speaker 1>of the Michigan Association of Broadcasters, UH they routers reported

0:40:12.320 --> 0:40:15.280
<v Speaker 1>that they believed the hackers succeeded because the TV stations

0:40:15.280 --> 0:40:19.319
<v Speaker 1>had never changed the default passwords that were installed in

0:40:19.360 --> 0:40:25.320
<v Speaker 1>their hardware. Yeah, password one to three guys. It's great

0:40:25.640 --> 0:40:27.640
<v Speaker 1>and and and that kind of thing. I mean, just

0:40:27.640 --> 0:40:29.759
<v Speaker 1>just basic, you know. It's it's we really need to

0:40:31.080 --> 0:40:33.840
<v Speaker 1>just educate everyone about how the internet works, maybe, or

0:40:34.120 --> 0:40:36.399
<v Speaker 1>or just make sure that everyone cares enough. We'll let

0:40:36.400 --> 0:40:40.960
<v Speaker 1>people know that there are uh default passwords and they

0:40:41.000 --> 0:40:45.200
<v Speaker 1>are pretty much standard across all devices of us from

0:40:45.200 --> 0:40:48.040
<v Speaker 1>a certain manufacturer. I mean maybe that it's admin for

0:40:48.200 --> 0:40:51.560
<v Speaker 1>one and password for another, but they are standard across.

0:40:51.560 --> 0:40:53.480
<v Speaker 1>And once you know what those standards are, that's the

0:40:53.520 --> 0:40:55.200
<v Speaker 1>first thing you try. And you can find them on

0:40:55.239 --> 0:40:57.600
<v Speaker 1>the internet, that's yeah, So you can find them by

0:40:57.640 --> 0:40:59.440
<v Speaker 1>buying one. That's all you have to do is go

0:40:59.440 --> 0:41:01.200
<v Speaker 1>out and you buy one of each thing and they're

0:41:01.239 --> 0:41:03.640
<v Speaker 1>not that expensive, Like you buy some routers, they're not

0:41:03.680 --> 0:41:06.680
<v Speaker 1>that that expensive. By buying each one and installing, you

0:41:06.719 --> 0:41:09.520
<v Speaker 1>see what the default password is, and then you just

0:41:09.600 --> 0:41:12.000
<v Speaker 1>add that to your dictionary attack. You know, you make

0:41:12.040 --> 0:41:15.920
<v Speaker 1>that priority one. So first first round of dictionary attack,

0:41:16.320 --> 0:41:19.480
<v Speaker 1>use the default password. If that works, your golden if not,

0:41:19.880 --> 0:41:22.759
<v Speaker 1>moved a step two. So I mean, yeah, it's it's

0:41:22.760 --> 0:41:24.960
<v Speaker 1>not good. And then on top of that, like on

0:41:25.000 --> 0:41:26.960
<v Speaker 1>a related thing, we haven't done an episode about this,

0:41:27.040 --> 0:41:30.600
<v Speaker 1>but on a kind of related idea about information online

0:41:30.680 --> 0:41:33.880
<v Speaker 1>and protecting ourselves and making sure we can respond to threats.

0:41:34.640 --> 0:41:39.520
<v Speaker 1>Another report that happened earlier in it was about the

0:41:39.560 --> 0:41:44.160
<v Speaker 1>FBI asking essentially asking internet companies for a wire tap

0:41:44.280 --> 0:41:48.280
<v Speaker 1>friendly back door into their systems. Now, this included everything

0:41:48.320 --> 0:41:52.160
<v Speaker 1>from infrastructure to actual corporations, and the FBI said, we

0:41:52.200 --> 0:41:54.680
<v Speaker 1>want to be able to get in there and check

0:41:54.719 --> 0:41:57.800
<v Speaker 1>on information when we are looking for things like cyber

0:41:58.400 --> 0:42:01.879
<v Speaker 1>terrorists or cyber warfare attacks and perhaps not thinking about

0:42:01.880 --> 0:42:04.239
<v Speaker 1>the fact that every time you you cut a new

0:42:04.280 --> 0:42:06.399
<v Speaker 1>door in a wall, it's that door can be used

0:42:06.400 --> 0:42:09.640
<v Speaker 1>by anybody exactly that's the issue here is that inner.

0:42:10.160 --> 0:42:12.440
<v Speaker 1>First of all, most of these systems already have back doors,

0:42:12.760 --> 0:42:15.279
<v Speaker 1>so really it would mean giving the FBI access to them,

0:42:15.320 --> 0:42:17.959
<v Speaker 1>because you have to have a way for an administrator

0:42:18.000 --> 0:42:20.200
<v Speaker 1>to get hold of the system so that when something

0:42:20.200 --> 0:42:22.359
<v Speaker 1>goes wrong, the administrator can fix it. As I learned

0:42:22.440 --> 0:42:26.279
<v Speaker 1>in the documentary Durassic Park. Yes, very important, that's a

0:42:26.280 --> 0:42:29.720
<v Speaker 1>good one. Yeah. Also it shows that when you create

0:42:29.840 --> 0:42:33.120
<v Speaker 1>a security back door that an administrator can get into,

0:42:33.400 --> 0:42:35.960
<v Speaker 1>a twelve year old girl can hack in because she

0:42:36.120 --> 0:42:38.959
<v Speaker 1>knows Unix was that Unix? I think it was Unix,

0:42:39.520 --> 0:42:42.600
<v Speaker 1>all of that out of I know this, I know,

0:42:42.719 --> 0:42:44.319
<v Speaker 1>she says, I know this, and then she sits down

0:42:44.320 --> 0:42:47.040
<v Speaker 1>in types and then by the third thing she's in. Uh,

0:42:47.080 --> 0:42:50.200
<v Speaker 1>because that's the rule of three in the Internet of Hollywood.

0:42:50.480 --> 0:42:55.000
<v Speaker 1>But yeah, the the point here is that by introducing vulnerabilities,

0:42:55.080 --> 0:42:59.160
<v Speaker 1>you have created the opportunity for the bad guys whoever

0:42:59.239 --> 0:43:01.680
<v Speaker 1>you want to say are the bad guys, to go

0:43:01.800 --> 0:43:05.320
<v Speaker 1>and infiltrate a system, so you don't Generally, that's considered

0:43:05.320 --> 0:43:07.440
<v Speaker 1>by most security experts to be what we call a

0:43:07.560 --> 0:43:11.719
<v Speaker 1>bad thing, giving more opportunity to people to infiltrate a

0:43:11.760 --> 0:43:14.319
<v Speaker 1>system is not a great idea. It doesn't help you

0:43:14.400 --> 0:43:19.200
<v Speaker 1>be safe. So we've got a lot of focus on

0:43:19.280 --> 0:43:24.040
<v Speaker 1>this this problem, and I'm at least confident that the

0:43:24.120 --> 0:43:27.879
<v Speaker 1>government is aware that there are experts out there who

0:43:28.000 --> 0:43:31.839
<v Speaker 1>can help guide this conversation. Whether they listen or not,

0:43:32.040 --> 0:43:34.840
<v Speaker 1>that's you know, that that remains to be seen. But

0:43:34.960 --> 0:43:39.919
<v Speaker 1>I hope that they are careful enough to consider exactly

0:43:40.040 --> 0:43:43.480
<v Speaker 1>the implications of these these policies so that when they're

0:43:43.560 --> 0:43:46.839
<v Speaker 1>enacting them, when they start to really build them out, uh,

0:43:46.880 --> 0:43:50.080
<v Speaker 1>they are doing it with the most accurate information. And

0:43:50.480 --> 0:43:52.440
<v Speaker 1>I already think they really do have the best of

0:43:52.440 --> 0:43:55.920
<v Speaker 1>intentions as far as cybersecurity is concerned. Whether or not

0:43:56.239 --> 0:43:59.839
<v Speaker 1>you agree considering you know, the business side of things

0:44:00.040 --> 0:44:02.759
<v Speaker 1>that that that's different, but but at least from the

0:44:02.800 --> 0:44:05.120
<v Speaker 1>idea we need to protect ourselves, I think we all

0:44:05.160 --> 0:44:07.960
<v Speaker 1>agree on that that the cyber threat is a real threat,

0:44:08.360 --> 0:44:10.719
<v Speaker 1>and it's a growing threat, and as we relying more

0:44:10.760 --> 0:44:13.000
<v Speaker 1>and more on these systems, it's just going to get

0:44:13.040 --> 0:44:17.120
<v Speaker 1>even to become an even more attractive target for someone

0:44:17.120 --> 0:44:19.920
<v Speaker 1>who wants to really wreak some havoc. So for all

0:44:19.920 --> 0:44:23.239
<v Speaker 1>those doctor evils, out there. I am not one, No,

0:44:23.400 --> 0:44:27.839
<v Speaker 1>certainly not. I don't own a cat. So anyway, that's

0:44:27.920 --> 0:44:31.359
<v Speaker 1>that's kind of the story about where we are right now.

0:44:31.400 --> 0:44:34.480
<v Speaker 1>As far as the the idea of trying to protect ourselves,

0:44:35.200 --> 0:44:37.359
<v Speaker 1>I know it was vague, but that's because again the

0:44:37.480 --> 0:44:40.600
<v Speaker 1>executive order was necessarily even it's all vague right now,

0:44:40.680 --> 0:44:42.759
<v Speaker 1>so you know, keep keep checking back. We'll let you

0:44:42.760 --> 0:44:46.759
<v Speaker 1>know if there are any definite development right and and

0:44:46.800 --> 0:44:49.839
<v Speaker 1>again I'll be amazed if this, if everyone is able

0:44:49.880 --> 0:44:51.480
<v Speaker 1>to meet the deadlines that are laid out in this

0:44:51.520 --> 0:44:54.400
<v Speaker 1>executive order. It would It's not that it's impossible, it

0:44:54.400 --> 0:45:00.480
<v Speaker 1>would just require a pretty remarkable turnaround. So we'll see

0:45:00.480 --> 0:45:05.680
<v Speaker 1>how it develops. We'll see how this could potentially impact business, individuals,

0:45:06.239 --> 0:45:09.120
<v Speaker 1>um and even our our national security. It's an important thing.

0:45:09.160 --> 0:45:11.160
<v Speaker 1>And keep in mind, you know, of course, for those

0:45:11.160 --> 0:45:13.440
<v Speaker 1>of us in the United States, there are lots of

0:45:13.480 --> 0:45:15.720
<v Speaker 1>other nations that are looking into this as well. Lauren

0:45:15.840 --> 0:45:19.480
<v Speaker 1>was talking about the European Union looking into ways of

0:45:19.520 --> 0:45:23.759
<v Speaker 1>protecting uh the the infrastructure in Europe. But this is

0:45:23.760 --> 0:45:27.160
<v Speaker 1>not localized to the United States as particular approaches. But

0:45:27.320 --> 0:45:30.800
<v Speaker 1>the problem is worldwide, So we're just gonna see lots

0:45:30.800 --> 0:45:34.200
<v Speaker 1>of different takes on this system and whether or not

0:45:35.000 --> 0:45:37.640
<v Speaker 1>any of them work better than others well, which is

0:45:37.719 --> 0:45:41.040
<v Speaker 1>let to wait and see. So with that in mind,

0:45:41.040 --> 0:45:43.480
<v Speaker 1>if you guys have any topics you would like us

0:45:43.520 --> 0:45:46.759
<v Speaker 1>to tackle in future episodes of tech Stuff, here's what

0:45:46.880 --> 0:45:49.200
<v Speaker 1>I would like you to do. I would like you

0:45:49.280 --> 0:45:52.200
<v Speaker 1>to send us an email our addresses tech stuff at

0:45:52.360 --> 0:45:55.360
<v Speaker 1>Discovery dot com, or let us know on Facebook or

0:45:55.400 --> 0:45:59.000
<v Speaker 1>Twitter are handled both of those as text stuff hs

0:45:59.239 --> 0:46:02.160
<v Speaker 1>W and Laura and I will talk you again really

0:46:02.239 --> 0:46:06.120
<v Speaker 1>soon for more on this and thousands of other topics.

0:46:06.360 --> 0:46:11.960
<v Speaker 1>Is it how stuff works dot com