WEBVTT

00:00:00.840 --> 00:00:03.799
The opinions expressed are those of the show

00:00:03.799 --> 00:00:08.060
hosts and may not necessarily be of any company

00:00:08.060 --> 00:00:19.719
in which the show hosts may represent. The following

00:00:19.719 --> 00:00:25.859
podcast may contain some strong language. Parental

00:00:25.859 --> 00:00:41.119
discretion is advised. Podcast 269 of the Security

00:00:41.119 --> 00:00:51.939
Box. PHI and our personal information. Why can't

00:00:51.939 --> 00:00:58.399
companies keep it secure? Recorded Wednesday,

00:00:58.780 --> 00:01:27.299
March 11th, 2026. Hello, folks. Welcome to TSB

00:01:27.299 --> 00:01:33.420
Program 269. I'm Jared Reimer. It's Wednesday,

00:01:33.659 --> 00:01:42.120
March 11th, 2026. And it feels pretty good to

00:01:42.120 --> 00:01:48.180
be back. But I think the Gremlins are still in...

00:01:53.099 --> 00:02:02.019
the computer because we definitely had at least

00:02:02.019 --> 00:02:11.240
one issue our files today are scams and how they've

00:02:11.240 --> 00:02:25.879
evolved scams in your inbox Questions to ask

00:02:25.879 --> 00:02:31.900
that can thwart scams. And to add insults to

00:02:31.900 --> 00:02:41.219
injury. Social network for AI is a bit concerning

00:02:41.219 --> 00:02:48.560
will be our video for today. Our topic is going

00:02:48.560 --> 00:03:04.789
to be... PHI, and our personal information. And

00:03:04.789 --> 00:03:20.449
this definitely has to have its whole segment

00:03:20.449 --> 00:03:48.349
on its own. That Is where we are Hopefully By

00:03:48.349 --> 00:04:03.110
next time The Gremlins will be completely Will

00:04:03.110 --> 00:04:07.389
be out of our computer. And we will redo. The

00:04:07.389 --> 00:04:13.409
scam segments. Next time. So that everybody can

00:04:13.409 --> 00:04:19.629
hear. The entire thing. I just don't have time

00:04:19.629 --> 00:04:31.910
to redo. The second file. Right now. So. Let's.

00:04:33.129 --> 00:04:46.230
Go ahead and push some buttons because our topic

00:04:46.230 --> 00:04:54.910
on PHI is going to be our longest segment to

00:04:54.910 --> 00:05:03.300
date. And a little over three hours. in length.

00:05:12.399 --> 00:05:19.120
So, I will see everybody next time when we talk

00:05:19.120 --> 00:05:30.079
about hallucinations and AI. Till then, see you

00:05:30.079 --> 00:06:25.550
next time. number 269. Yes, it's a week after

00:06:25.550 --> 00:06:31.629
we probably normally do this program, but this

00:06:31.629 --> 00:06:41.069
computer needed help. Seriously, needed help.

00:06:41.170 --> 00:06:44.100
And then I'm still not really set up. Because

00:06:44.100 --> 00:06:47.220
we're still just playing random material on the

00:06:47.220 --> 00:06:49.779
independent channel. But we're going to push

00:06:49.779 --> 00:06:53.860
forward and get automation eventually back up

00:06:53.860 --> 00:06:57.199
and running the way it should be. Mr. J is on

00:06:57.199 --> 00:07:08.040
Team Talk with me. Yep. And this is going to

00:07:08.040 --> 00:07:22.980
get very interesting. No kidding. So, we're going

00:07:22.980 --> 00:07:28.300
to start off with a little bit of phone line

00:07:28.300 --> 00:07:43.730
news. So, today is Wednesday, March 11th. Around

00:07:43.730 --> 00:07:52.389
the night, one of my buddies tells me about something

00:07:52.389 --> 00:08:00.870
that a caller posted on the bashing board. And

00:08:00.870 --> 00:08:12.089
this may be a little sexual, but maybe this goes...

00:08:12.560 --> 00:08:22.339
into the category of the stupid fuck award Mr.

00:08:22.579 --> 00:08:31.740
J uh oh so a guy goes somewhere and we'll tell

00:08:31.740 --> 00:08:39.139
you where in a minute and apparently he was there

00:08:39.139 --> 00:08:44.909
for a specific reason this time We'll tell you

00:08:44.909 --> 00:08:50.110
about that too. Well, apparently he was sitting

00:08:50.110 --> 00:08:55.409
down supposedly minding his own business when

00:08:55.409 --> 00:09:04.809
he calls into Livewire. And he happens to post

00:09:04.809 --> 00:09:13.960
in a lower than normal voice. If this particular

00:09:13.960 --> 00:09:22.159
guy gets pussy. Now that wouldn't be so bad.

00:09:25.419 --> 00:09:33.799
Except two things went wrong for him. The place

00:09:33.799 --> 00:09:45.500
where he was at and the consequences Uh -oh.

00:09:52.960 --> 00:10:04.100
Oh, no. So... Unbeknownst to me, but not surprising

00:10:04.100 --> 00:10:14.210
to me... I guess you're... Local church? Hands

00:10:14.210 --> 00:10:21.990
out food to people who need it, including disabled?

00:10:23.509 --> 00:10:29.409
That's, I mean, some churches, I think, probably

00:10:29.409 --> 00:10:32.529
have initiatives like that. So I'm not that surprised,

00:10:32.629 --> 00:10:38.669
but I think I know where this is going. So he

00:10:38.669 --> 00:10:44.960
was there. At this church. Oh, what an absolute

00:10:44.960 --> 00:10:58.440
idiot. He was at this church. And he thought

00:10:58.440 --> 00:11:11.950
he was quiet enough. Until... The bishop's wife

00:11:11.950 --> 00:11:24.309
and apparently his daughter either heard it or

00:11:24.309 --> 00:11:33.429
were around. And he was basically pulled into

00:11:33.429 --> 00:11:43.679
the office and said, if you do that, Again, it'll

00:11:43.679 --> 00:11:51.600
be a two -month ban from coming here. As it should

00:11:51.600 --> 00:12:08.819
be. But something tells me that if this guy is

00:12:08.819 --> 00:12:12.639
so willing to do this in a freaking place that's

00:12:12.639 --> 00:12:16.120
this public. There are other issues going on.

00:12:16.220 --> 00:12:23.659
That's my guess. Well, he has talked about publicly

00:12:23.659 --> 00:12:34.860
how short it is, how he can't get it up, and

00:12:38.399 --> 00:12:52.559
How he's still a virgin. Um... In his 50s, Mr.

00:12:52.899 --> 00:13:02.360
J. Uh... Just... I don't know what to say. I

00:13:02.360 --> 00:13:15.929
really... We actually talked to him about phone

00:13:15.929 --> 00:13:20.090
etiquette and other things at one point. And

00:13:20.090 --> 00:13:25.710
apparently he just doesn't get it. He got thrown

00:13:25.710 --> 00:13:33.350
out of where we are. And then this. Oh my gosh.

00:13:33.710 --> 00:13:37.629
And every time I say I think I heard it all.

00:13:41.679 --> 00:13:57.860
I hear something completely different. I know

00:13:57.860 --> 00:14:04.879
we've all made mistakes before. And some of us

00:14:04.879 --> 00:14:07.779
have gotten into legal trouble and learned our

00:14:07.779 --> 00:14:13.299
lesson. Some of us may have not learned our lesson

00:14:13.299 --> 00:14:16.440
and may still be in legal trouble. Here's the

00:14:16.440 --> 00:14:25.840
thing. But this guy is beyond help. That's what

00:14:25.840 --> 00:14:28.159
I was about to say. I don't think that was a

00:14:28.159 --> 00:14:44.080
mistake. I don't think that was a mistake. You

00:14:44.080 --> 00:14:47.059
think he intentionally did that not knowing that

00:14:47.059 --> 00:14:50.840
ears were possibly around. That could get him

00:14:50.840 --> 00:15:06.220
in trouble for that. Right. Okay. Here comes

00:15:06.220 --> 00:15:18.600
Terry. Oh, boy. Terry Ring, welcome to T -S -B.

00:15:20.279 --> 00:15:34.620
T -S -B. So, a stupid fuck award, Mr. Ring. There's

00:15:34.620 --> 00:15:44.850
a guy... Who went somewhere to get food. And

00:15:44.850 --> 00:15:50.470
happened to get on the phone line to post on

00:15:50.470 --> 00:15:53.929
board two over on Livewire. And apparently he

00:15:53.929 --> 00:15:57.769
was asking one of the guys whether he got any

00:15:57.769 --> 00:16:04.669
pussy. And it wouldn't be so bad. Except for

00:16:04.669 --> 00:16:12.299
two things. Where he was and his consequence

00:16:12.299 --> 00:16:24.080
if he ever did that again. Uh -oh. That's the

00:16:24.080 --> 00:16:28.620
second reaction. That's the second reaction I

00:16:28.620 --> 00:16:34.379
got out of them. Because that was Nick's reaction

00:16:34.379 --> 00:16:38.500
the first time he heard that. Where was he? Where

00:16:38.500 --> 00:16:49.120
was he? He was apparently at a church where the

00:16:49.120 --> 00:16:54.139
bishop's wife and his daughter we don't know

00:16:54.139 --> 00:16:56.179
how old the daughter is. We don't know anything.

00:16:57.960 --> 00:17:02.740
Right. Heard that. And he got pulled in the office

00:17:02.740 --> 00:17:07.079
and was told if he ever did that again A two

00:17:07.079 --> 00:17:10.259
-month suspension of coming back to get food.

00:17:14.660 --> 00:17:17.220
Oh, so it was one of those church things where

00:17:17.220 --> 00:17:24.740
he went and got free food from the church. And

00:17:24.740 --> 00:17:28.500
he just said that and the bishop and his daughter,

00:17:28.680 --> 00:17:32.319
oh my God. The bishop's wife. Oh, the bishop's

00:17:32.319 --> 00:17:36.390
wife heard it. Oh, shit. He's probably like,

00:17:36.450 --> 00:17:51.190
what? Uh -huh. I know I've told some of you what

00:17:51.190 --> 00:17:54.069
I was interested in, but could you, I guess now

00:17:54.069 --> 00:17:58.470
that two of you are here, could you imagine me

00:17:58.470 --> 00:18:02.490
asking whatever it would be that I would want?

00:18:05.480 --> 00:18:12.079
In a church. No. I couldn't. And would you come

00:18:12.079 --> 00:18:24.680
down here and kick my ass? Yeah, I mean, that's...

00:18:24.680 --> 00:18:29.359
Yeah, that... I mean, I accidentally swore one

00:18:29.359 --> 00:18:32.119
time in a church, but that was by mistake. Okay,

00:18:32.119 --> 00:18:36.240
but... You know, obviously I got reprimanded

00:18:36.240 --> 00:18:39.779
for it, but, you know. I got reprimanded on a

00:18:39.779 --> 00:18:44.180
phone line when I swore, and then one of the

00:18:44.180 --> 00:18:46.160
other people wanted to start with me and said,

00:18:46.200 --> 00:18:48.400
I already heard. You don't need to tell me, too.

00:18:48.920 --> 00:18:51.740
I already got reprimanded. That's not necessary.

00:18:53.019 --> 00:19:09.660
No. But this guy, your response was the same

00:19:09.660 --> 00:19:11.920
response Nick gave me at the beginning of the

00:19:11.920 --> 00:19:22.720
program. Yep. A church of all things. I mean,

00:19:22.759 --> 00:19:31.759
that's just like... And given this guy's pattern,

00:19:31.940 --> 00:19:34.279
he is going to do it again. I can predict it.

00:19:34.500 --> 00:19:37.400
I would have told him to leave right then and

00:19:37.400 --> 00:19:42.259
been like, dude, you need to go. I would have

00:19:42.259 --> 00:19:46.980
not even said, do that again, you get six months.

00:19:47.099 --> 00:19:50.180
I told them on Livewire, I said I would have

00:19:50.180 --> 00:19:53.259
just kicked his happy ass right out of here and

00:19:53.259 --> 00:19:58.380
said, you don't come back here. Exactly. Uh,

00:19:58.680 --> 00:20:02.200
I mean, he could have asked it a little bit different

00:20:02.200 --> 00:20:05.680
to where it wouldn't be as offensive. There's

00:20:05.680 --> 00:20:09.000
no way to ask that in a way that's not offensive,

00:20:09.140 --> 00:20:17.980
Terry. I mean... You could say the word sex.

00:20:18.099 --> 00:20:20.890
I mean, that's not really... too offensive. I

00:20:20.890 --> 00:20:23.329
mean, that's not... That's... But you're still

00:20:23.329 --> 00:20:26.890
in church. Well, okay, and then the whole sex

00:20:26.890 --> 00:20:30.450
before marriage comes up. I get that. I get that.

00:20:30.690 --> 00:20:33.769
Well, no, but that's not even something you should

00:20:33.769 --> 00:20:36.890
be talking about in that public place. No, you

00:20:36.890 --> 00:20:38.990
shouldn't. Especially in that environment. You

00:20:38.990 --> 00:20:44.440
shouldn't, but people don't think. Or you should

00:20:44.440 --> 00:20:46.759
have waited until at least you got outside and

00:20:46.759 --> 00:20:49.799
got to your car and been like, hey, you know.

00:20:50.960 --> 00:20:55.339
You shouldn't. Something like that. At least

00:20:55.339 --> 00:20:59.539
you're in your car or something. No, you should

00:20:59.539 --> 00:21:02.920
wait until you're home. Yeah, or that. Or that,

00:21:03.019 --> 00:21:06.400
yeah. Because, you know, if this is somebody

00:21:06.400 --> 00:21:10.160
who relies on, you know, paratransit or something,

00:21:10.220 --> 00:21:14.450
I don't know what his situation is. And, you

00:21:14.450 --> 00:21:16.210
know, you want to talk about a really bad twist

00:21:16.210 --> 00:21:21.190
if it's a female who's driving him. Yeah. Yeah,

00:21:21.250 --> 00:21:23.990
I mean, paratransit, I could see. Yeah, I could

00:21:23.990 --> 00:21:27.829
see. But, I mean, if you're driving yourself

00:21:27.829 --> 00:21:30.789
and it's just you in the car, then okay. I can

00:21:30.789 --> 00:21:33.069
already tell you that that's not going to happen,

00:21:33.170 --> 00:21:37.269
Terry, because he's disabled. Oh, okay. So then,

00:21:37.309 --> 00:21:39.130
yeah, okay. So then that's out of the question.

00:21:39.190 --> 00:21:41.890
So it's more likely that what I'm suggesting

00:21:41.890 --> 00:21:44.569
is probably closer. Yeah. It's more like, yeah,

00:21:44.769 --> 00:21:47.950
yeah, yeah. An Uber, Lyft, or anything. Yeah,

00:21:48.029 --> 00:21:49.869
I would wait till I get home and say something

00:21:49.869 --> 00:21:52.670
and then ask. Yeah, I would just imagine it's

00:21:52.670 --> 00:21:54.930
like, you know, the driver overhears that and,

00:21:55.049 --> 00:21:57.269
I mean, they hear a lot of shit. I get that.

00:21:57.309 --> 00:22:00.319
But they overhear that. It's like, um... What

00:22:00.319 --> 00:22:03.940
did you just say? And especially if the driver's,

00:22:03.960 --> 00:22:07.660
like, really religious, he probably said, get

00:22:07.660 --> 00:22:10.660
out of my car, man. Like, just go. Get. Like,

00:22:10.660 --> 00:22:13.680
especially in an Uber car. Like, I don't want

00:22:13.680 --> 00:22:16.660
anything to do with this. Out. No, they can't

00:22:16.660 --> 00:22:20.880
do that to a disabled person. You could turn

00:22:20.880 --> 00:22:23.460
around and say, that was my ride home. They'd

00:22:23.460 --> 00:22:25.339
let me out, and I don't even know where I am.

00:22:25.960 --> 00:22:31.129
They could be in a lot of trouble for that. Well,

00:22:31.129 --> 00:22:32.950
here's what they could turn around and say, though.

00:22:34.750 --> 00:22:41.369
He was saying words and making suggestions and

00:22:41.369 --> 00:22:43.970
innuendos that I found very offensive and unsafe.

00:22:45.789 --> 00:22:49.670
Your job is to drive. You can give him a bad

00:22:49.670 --> 00:22:52.029
rating and refuse to pick him up the next time.

00:22:54.369 --> 00:22:56.589
Oh, you can give him a bad rating on that trip,

00:22:56.849 --> 00:23:02.660
yeah. Correct. I don't want to use this customer

00:23:02.660 --> 00:23:06.940
anymore. If the customer does an Uber again,

00:23:07.119 --> 00:23:14.920
it wouldn't show that driver anymore. But at

00:23:14.920 --> 00:23:16.720
that point, he'd be looking at getting kicked

00:23:16.720 --> 00:23:26.009
off the program if he kept it up. Uber's already

00:23:26.009 --> 00:23:28.190
been under a lot of arrest because of safety.

00:23:28.809 --> 00:23:32.509
Correct. It's been sued multiple times. Correct.

00:23:35.349 --> 00:23:40.329
Mm -hmm. They don't want that on their conscience

00:23:40.329 --> 00:23:55.690
either, I'm sure, so... paratransit, I don't

00:23:55.690 --> 00:23:57.509
know if it's different. I don't know if they

00:23:57.509 --> 00:24:01.150
could just... They can't legally do that either.

00:24:02.210 --> 00:24:04.390
I mean, they could probably cancel you from the

00:24:04.390 --> 00:24:11.309
program afterwards. You know. The driver can

00:24:11.309 --> 00:24:16.769
turn you in and they could send you a letter

00:24:16.769 --> 00:24:20.509
afterward, but they can't kick you out. No, but

00:24:20.509 --> 00:24:22.329
that's what I'm saying is that they could be

00:24:22.329 --> 00:24:29.049
kicked off the program. After the fact. Yeah.

00:24:32.509 --> 00:24:36.849
What an idiot. Why would you like... That's probably

00:24:36.849 --> 00:24:43.930
the only way he gets food. I'm not going to sit

00:24:43.930 --> 00:24:48.309
there and... I'm just guessing, right? Maybe

00:24:48.309 --> 00:24:51.690
he does buy his own food too, but I'm just guessing.

00:24:53.000 --> 00:24:57.700
Why would you put that at risk if that's your

00:24:57.700 --> 00:25:02.700
only source of getting food? I'm not saying it

00:25:02.700 --> 00:25:05.400
is or isn't. Some people just don't care. I'm

00:25:05.400 --> 00:25:09.720
not saying it is or isn't. But I wouldn't put

00:25:09.720 --> 00:25:12.400
it at risk like that, especially if that was

00:25:12.400 --> 00:25:32.619
my only source of food. No way. No way. I think

00:25:32.619 --> 00:25:44.200
that gives us the stupid fuck award. At long

00:25:44.200 --> 00:25:49.140
last, yes. He would get that, yes. At long last.

00:26:04.009 --> 00:26:32.730
Yep, well said. I'm sorry. I'm sorry. I once

00:26:32.730 --> 00:26:38.089
used their products and they're one of the best

00:26:38.089 --> 00:26:45.069
in the business. They can protect you from all

00:26:45.069 --> 00:26:49.210
kinds of threats and they can make sure that

00:26:49.210 --> 00:26:55.769
you are not entering sensitive information in

00:26:55.769 --> 00:27:00.589
places where you should not be. If you've entered

00:27:00.589 --> 00:27:05.109
the information into the program, for example,

00:27:05.109 --> 00:27:09.789
if you enter your credit card number, it knows

00:27:09.789 --> 00:27:15.529
not to allow you to enter that information into

00:27:15.529 --> 00:27:22.069
places like email or unsecured websites. They've

00:27:22.069 --> 00:27:27.230
got products for home users and business users.

00:27:28.140 --> 00:27:35.440
And they also have a product that can do a simple

00:27:35.440 --> 00:27:46.140
scan as well. Their website is trendmicro .com.

00:27:48.539 --> 00:27:52.660
There's also a link to them on our website at

00:27:52.660 --> 00:27:58.019
emailhostsecurity .com. Select the resources

00:27:58.019 --> 00:28:02.799
page and look in the companies and resources

00:28:02.799 --> 00:28:10.400
section. All right, folks, let's go ahead and

00:28:10.400 --> 00:28:19.960
check out the blog. And yes, I'm going to put

00:28:19.960 --> 00:28:25.019
that up on the board because Michael did say.

00:28:27.279 --> 00:28:31.880
Let me see what the group said. So I'll put that

00:28:31.880 --> 00:28:48.740
up. Mr. Ring. Here we go with another I'm not

00:28:48.740 --> 00:28:55.880
laughing article. Doge seems to be back half

00:28:55.880 --> 00:29:12.279
a billion people may be at risk. Nice. If the

00:29:12.279 --> 00:29:22.599
story that cyber news excuse me is true and the

00:29:22.599 --> 00:29:30.200
gentleman who was never named Truly has God access

00:29:30.200 --> 00:29:39.619
into the Social Security Administration. Even

00:29:39.619 --> 00:29:43.839
while working for the Department of Government

00:29:43.839 --> 00:30:01.750
Inefficiency. We're in trouble. You have to remember

00:30:01.750 --> 00:30:06.970
that Doge has access from other articles to all

00:30:06.970 --> 00:30:11.609
of that stuff. Well, we covered... That's what

00:30:11.609 --> 00:30:15.589
I'm saying. We covered Doge. Yeah, we did. Ever

00:30:15.589 --> 00:30:30.509
since its inception. But this... This is beyond

00:30:30.509 --> 00:30:36.529
bad. Well, that's why I'm watching our governor's

00:30:36.529 --> 00:30:38.869
race carefully because the person that's running

00:30:38.869 --> 00:30:42.690
against our governor, Darren Bailey, he wants

00:30:42.690 --> 00:30:46.730
to put a Doge -like system in for Illinois. I'm

00:30:46.730 --> 00:30:58.460
like, oh, no. Oh, no. But if this is true, it's

00:30:58.460 --> 00:31:01.140
not going to matter, Terry. No, I'm not saying

00:31:01.140 --> 00:31:03.779
it's going to matter. I'm not saying it's going

00:31:03.779 --> 00:31:20.599
to matter. We're talking about 500 million people.

00:31:23.079 --> 00:31:25.339
Half a billion people. That's a lot of people.

00:31:29.740 --> 00:31:32.220
And apparently he's only taken two databases,

00:31:32.480 --> 00:31:38.420
which does include people who are living and

00:31:38.420 --> 00:31:46.440
dead. And there were specific names of these

00:31:46.440 --> 00:31:50.619
databases mentioned within the article, and ChatGPT

00:31:50.619 --> 00:31:56.880
even knows about it. And it even referenced an

00:31:56.880 --> 00:32:02.500
August 2025 cyber news article on the Department

00:32:02.500 --> 00:32:08.880
of Public, I mean, Governmental Inefficiency.

00:32:10.220 --> 00:32:16.599
It always loves when I tell it, gentlemen, that

00:32:16.599 --> 00:32:24.299
we've covered it. And we've called the Department

00:32:24.299 --> 00:32:28.259
of Government Efficiency the Department of Government

00:32:28.259 --> 00:32:34.720
Inefficiency. It always seems to be amused about

00:32:34.720 --> 00:32:40.960
that. I wonder how it would respond to my nickname

00:32:40.960 --> 00:32:43.440
for Windows Defender. I haven't tried doing this

00:32:43.440 --> 00:32:48.460
yet. Yes, Windows Offender. Which now I'm using

00:32:48.460 --> 00:32:51.180
because I haven't gotten Malwarebytes reinstalled

00:32:51.180 --> 00:33:00.400
yet. Fair enough. I mean, it's better than nothing,

00:33:00.460 --> 00:33:06.039
I guess. Well, and as it says, it's a different

00:33:06.039 --> 00:33:11.619
type of antivirus. It analyzes files when they're

00:33:11.619 --> 00:33:18.440
ran, not when downloaded. Which is probably better

00:33:18.440 --> 00:33:24.700
anyway because there could be false positives.

00:33:25.200 --> 00:33:33.099
So if it's not emitting any problems, then you're

00:33:33.099 --> 00:33:36.640
better off anyway. And we'll be talking about

00:33:36.640 --> 00:33:45.630
this type of thing in a future program. Here

00:33:45.630 --> 00:34:19.150
on TSB. And Mr. J. Mm -hmm. It's time to get

00:34:19.150 --> 00:34:30.190
offended. Black Santa. Oh, yes. And by the way,

00:34:30.289 --> 00:34:34.269
Cyber News does have a version of the article

00:34:34.269 --> 00:34:40.130
that I picked up from the computer. Black Santa?

00:34:40.570 --> 00:34:50.119
Of... Bleeping. Bleeping. Yes, Black Santa. Black

00:34:50.119 --> 00:34:54.079
Santa. It's a new... Anyone care to guess what

00:34:54.079 --> 00:34:58.440
kind of... I can't guess because I read it already

00:34:58.440 --> 00:35:03.000
blogged. This is? It's... Right, you've read

00:35:03.000 --> 00:35:07.219
it. It's something we've covered when it first

00:35:07.219 --> 00:35:15.300
came out, Mr. Ring. And we said we probably weren't

00:35:15.300 --> 00:35:20.260
going to see the end of it. And we were right.

00:35:20.460 --> 00:35:25.340
And we were right. And this will be the third

00:35:25.340 --> 00:35:34.719
time or so in the last year that this acronym

00:35:34.719 --> 00:35:45.360
has been talked about in a bad way. Uh -huh.

00:35:47.880 --> 00:35:59.480
It's an acronym. It stands for three words. Well,

00:35:59.559 --> 00:36:03.900
technically four. Technically four. Yeah, technically.

00:36:05.659 --> 00:36:19.860
One of the words is Not part of its acronym.

00:36:22.179 --> 00:36:42.900
Right. The answer? Endpoint. Detection. And response.

00:36:47.540 --> 00:36:58.619
Otherwise known as EDR killer. Killer. I hope

00:36:58.619 --> 00:37:03.179
we don't get any of that. Well, we already are.

00:37:03.260 --> 00:37:06.420
That's what we're saying. How about us personally?

00:37:06.840 --> 00:37:15.500
I would get it more than you. Yeah. Right. Because

00:37:15.500 --> 00:37:20.920
you're more known in the community. No. No, because

00:37:20.920 --> 00:37:27.039
he runs a small business. Yeah. Isn't that what

00:37:27.039 --> 00:37:28.860
they're targeting? I think that's what they target

00:37:28.860 --> 00:37:33.500
most of these businesses, right? Right. Well,

00:37:33.559 --> 00:37:39.239
this is HR departments. What this one's targeting

00:37:39.239 --> 00:37:42.820
is known as HR departments. The human resources

00:37:42.820 --> 00:37:47.699
department. Human resources, yeah. I am all of

00:37:47.699 --> 00:38:23.210
it. So, I expect... I expect... Yeah. Let's see.

00:38:23.230 --> 00:38:30.889
We've got zombie zip. Yeah. That concerns me

00:38:30.889 --> 00:38:37.409
a little bit. I haven't read it yet, but it's

00:38:37.409 --> 00:38:53.079
not understandable. It's a researcher who changed

00:38:53.079 --> 00:38:59.860
the way zip files work, I guess. In regards to

00:38:59.860 --> 00:39:07.840
the way that 50 out of 51 detection programs

00:39:07.840 --> 00:39:18.739
on which major virus scanning website VirusTotal?

00:39:19.019 --> 00:39:27.309
VirusTotal's correct. 50 out of 51 would allow

00:39:27.309 --> 00:39:34.829
you to unzip these even though the headers didn't

00:39:34.829 --> 00:39:43.590
match. That's kind of a little concerning. A

00:39:43.590 --> 00:39:50.550
little? A little? Yeah, just a little. It's a

00:39:50.550 --> 00:39:57.940
random yeah so one of us gets some dot zip and

00:39:57.940 --> 00:40:01.139
you know and here's the scenario it could come

00:40:01.139 --> 00:40:04.500
from one of us you know because maybe we've been

00:40:04.500 --> 00:40:07.300
hit somehow and you know the rest of the staff

00:40:07.300 --> 00:40:11.619
doesn't know and you know maybe one of us is

00:40:11.619 --> 00:40:13.300
in a hurry it's like oh it's fairly important

00:40:13.300 --> 00:40:16.659
i'll download it and you know they try to run

00:40:16.659 --> 00:40:19.260
it through virus total oh it looks fine and then

00:40:19.260 --> 00:40:28.900
of course you run it bang And then you're scrambling

00:40:28.900 --> 00:40:34.960
to try to redo things because it just wiped whatever,

00:40:35.239 --> 00:40:39.260
wiped your entire drive. It didn't say what it

00:40:39.260 --> 00:40:44.880
did. I mean, that's in theory what it could do.

00:40:45.199 --> 00:40:48.059
That's what I'm saying. That's a possibility.

00:40:48.260 --> 00:41:01.050
That's why I said that. Find another computer.

00:41:02.050 --> 00:41:12.550
Go get a drive that's not compromised. So make

00:41:12.550 --> 00:41:16.349
an ISO and then you go. Yeah, that would be a

00:41:16.349 --> 00:41:28.329
lot of work. So, Nick. Mm hmm. We haven't really

00:41:28.329 --> 00:41:34.030
talked about this very much. And I'm talking

00:41:34.030 --> 00:41:45.570
very specifically about IP version 6. Because

00:41:45.570 --> 00:41:58.880
it is not really widely used. And if it is, it's

00:41:58.880 --> 00:42:03.219
more of a background automatic thing, just like

00:42:03.219 --> 00:42:09.619
you getting on the internet can be. Because now

00:42:09.619 --> 00:42:24.579
we've got news about the ARPA TLD, which is mainly

00:42:24.579 --> 00:42:40.420
used... to do DNS lookups. Well, it owned Google

00:42:40.420 --> 00:42:57.150
in the IPv6 space. I'm not surprised. As much

00:42:57.150 --> 00:42:59.130
trouble as Google has been in over the years,

00:42:59.150 --> 00:43:00.949
I'm not surprised that they own them in that

00:43:00.949 --> 00:43:26.400
space. I forget the exact details, but... Essentially

00:43:26.400 --> 00:43:34.199
just corrupting this DNS lookup service. I mean,

00:43:34.219 --> 00:43:41.079
that's how I understood it. I don't know if I

00:43:41.079 --> 00:43:44.460
have this right either, to be honest. Essentially,

00:43:44.679 --> 00:43:49.920
so if somebody makes one of these lookup requests

00:43:49.920 --> 00:43:54.289
to something that looks... fraudulent or maybe

00:43:54.289 --> 00:43:56.389
suspicious, you know, like a phishing domain,

00:43:56.630 --> 00:44:05.429
it shows up as legit. Correct. That's the way

00:44:05.429 --> 00:44:06.510
I understood it. Oh, so I did understand that

00:44:06.510 --> 00:44:09.010
part. Yeah, that's the way I kind of understood

00:44:09.010 --> 00:44:13.010
it. Yeah, so, you know, it's been hijacked so

00:44:13.010 --> 00:44:18.170
that this, you know, shady -looking domain, you

00:44:18.170 --> 00:44:22.489
know, AppleCare... AppleCareForMe .com for something

00:44:22.489 --> 00:44:30.510
that's seen as a legitimate DNS address. Even

00:44:30.510 --> 00:44:42.510
though it's a phishing site. But this is done

00:44:42.510 --> 00:44:48.489
through IPv6, not 4. Just because it goes to

00:44:48.489 --> 00:44:55.210
look up to look up the you know the details of

00:44:55.210 --> 00:45:12.369
where this goes or what have you so I blogged

00:45:12.369 --> 00:45:21.349
Mr. J's very interesting find from Saturday.

00:45:23.630 --> 00:45:34.929
Yes. About another we don't know where the hell

00:45:34.929 --> 00:45:40.929
all our data is company. Oh, another one of those.

00:45:42.489 --> 00:45:45.769
This one's bad. It's only going to get worse,

00:45:45.929 --> 00:45:54.320
I think. The first number we get... Wait, there's

00:45:54.320 --> 00:45:56.920
two different stories. Which one am I talking

00:45:56.920 --> 00:46:01.039
about here? I think I know the one you're talking

00:46:01.039 --> 00:46:03.239
about. Yes, the first number we got for this

00:46:03.239 --> 00:46:11.800
was 10 million. Yes. But that has since been

00:46:11.800 --> 00:46:17.980
revised significantly upward. And we're now looking

00:46:17.980 --> 00:46:25.150
at... 25 million and counting. Counting. Now,

00:46:25.230 --> 00:46:34.329
does this sound to you like OPM in 15? I had

00:46:34.329 --> 00:46:40.110
to be corrected. OPM was 2015, not 18. So, I

00:46:40.110 --> 00:46:42.730
want to make that correction. We've been saying

00:46:42.730 --> 00:46:48.769
OPM was 18, but it was actually 15. So, chat

00:46:48.769 --> 00:46:53.710
GPT corrected me on that. So, I want to correct

00:46:53.710 --> 00:46:58.750
the record of that right now. Okay. Because I've

00:46:58.750 --> 00:47:10.730
been saying 18 for a while. But who thinks that

00:47:10.730 --> 00:47:17.489
this is OPM all over again? In some ways. It's

00:47:17.489 --> 00:47:24.250
similar. It's similar. I'm not saying it's exact.

00:47:26.150 --> 00:47:29.409
Because it's telling me the difference. The chat

00:47:29.409 --> 00:47:34.010
GPT told me the difference between the two. So

00:47:34.010 --> 00:47:40.909
now I'm asking, do you guys think it's OPM again

00:47:40.909 --> 00:47:55.750
in some ways? Yes. Go ahead. Well, yes, in terms

00:47:55.750 --> 00:48:04.510
of the data that was involved, I think it's very

00:48:04.510 --> 00:48:22.210
similar. Okay. Mm -hmm. And then I happened to

00:48:22.210 --> 00:48:28.150
find one of my own in the Better Late Than Never

00:48:28.150 --> 00:48:40.650
department. Yes. What was the name of this company?

00:48:43.550 --> 00:48:51.119
UFP, I believe. medical devices. And up until

00:48:51.119 --> 00:48:53.360
now, I have never heard of them. But yes, they've

00:48:53.360 --> 00:48:56.239
gotten hit. I've never heard of them either.

00:48:56.380 --> 00:49:08.659
OMP? UFP. I've never heard of them either. I

00:49:08.659 --> 00:49:15.329
suspect that unfortunately this is going to be

00:49:15.329 --> 00:49:18.889
updated and not in a good way. Because as of

00:49:18.889 --> 00:49:26.329
now, the claim is that there is no evidence that

00:49:26.329 --> 00:49:28.969
they have any personal information that's been

00:49:28.969 --> 00:49:33.369
taken. I wouldn't be so sure about that. I was

00:49:33.369 --> 00:49:36.730
going to say they don't have evidence. Exactly.

00:49:37.449 --> 00:49:44.420
They don't have evidence yet. Yet. I can just

00:49:44.420 --> 00:49:47.880
see bleeping in a few weeks or maybe a month

00:49:47.880 --> 00:49:52.480
or so. UFP, medical device manufacturer breach,

00:49:52.619 --> 00:49:55.920
worse than first thought, is probably what might

00:49:55.920 --> 00:50:00.699
happen. And then a few of us are just going to

00:50:00.699 --> 00:50:07.599
fall out of our chairs. So if you hear a... From

00:50:07.599 --> 00:50:12.170
there, you'll know why. I think... Actually,

00:50:13.829 --> 00:50:15.789
I think it's going to be different. I think a

00:50:15.789 --> 00:50:18.050
few of us are just going to be like, yeah, what

00:50:18.050 --> 00:50:22.889
else is new? We told you that was going to happen.

00:50:23.690 --> 00:50:36.489
We did. That was broken. Terry, I'm going to

00:50:36.489 --> 00:50:39.880
have to get you... A full version of this. I

00:50:39.880 --> 00:50:43.320
actually just taped this morning the three segments

00:50:43.320 --> 00:50:45.260
that are going to be part of today's program.

00:50:45.639 --> 00:50:51.360
But segment two, I think got commandeered by

00:50:51.360 --> 00:50:54.460
robots or something. I'm going to have to leave

00:50:54.460 --> 00:50:56.480
it because I'm sort of pressed for time to get

00:50:56.480 --> 00:51:00.679
the podcast out. But I am going to re -record

00:51:00.679 --> 00:51:04.559
this into one segment for you, which will sound

00:51:04.559 --> 00:51:10.039
a lot better than... The three. Because I was

00:51:10.039 --> 00:51:12.139
just going to merge it, but knowing that the

00:51:12.139 --> 00:51:16.079
second wasn't going to be all that great. But

00:51:16.079 --> 00:51:18.079
I'm letting the podcast know that I'm releasing

00:51:18.079 --> 00:51:21.800
it this way because while I could re -record

00:51:21.800 --> 00:51:27.539
the second segment, I do have other commitments

00:51:27.539 --> 00:51:31.340
tomorrow, so I want to try and get this out in

00:51:31.340 --> 00:51:37.579
a reasonable time manner. Right. Sorry for any

00:51:37.579 --> 00:51:42.360
robots. What we could do is re -air it again

00:51:42.360 --> 00:51:48.360
when we schedule 270, either in two or three

00:51:48.360 --> 00:51:50.739
weeks, depending on what the group would like

00:51:50.739 --> 00:52:05.230
to do. So, I'll redo it for you. Probably on

00:52:05.230 --> 00:52:16.630
Friday. And I guess Kim Commando put out something

00:52:16.630 --> 00:52:19.670
recently. I don't think I heard it yet, but I

00:52:19.670 --> 00:52:27.829
guess Korea has already been in our banks. Oh,

00:52:27.929 --> 00:52:36.949
great. As part of her minute. Probably South

00:52:36.949 --> 00:52:40.389
Korea again. They're always doing shit. I don't

00:52:40.389 --> 00:52:42.829
know if it's South Korea or North Korea, but

00:52:42.829 --> 00:52:46.230
I know that... It's more likely to be North.

00:52:47.230 --> 00:52:54.190
I know that somebody's at war, and I've seen

00:52:54.190 --> 00:52:57.789
bits and pieces of it on KNX. I refuse to read

00:52:57.789 --> 00:53:01.630
it, because there's not a damn thing I can do

00:53:01.630 --> 00:53:07.000
about it. Oh, no. I refuse to read. I would say

00:53:07.000 --> 00:53:12.059
it's more likely that we're talking about the

00:53:12.059 --> 00:53:16.260
North, not the South. I think you're right. The

00:53:16.260 --> 00:53:18.280
U .S. is only a part of that war because of the

00:53:18.280 --> 00:53:22.539
oil. That's why. Otherwise, they'd probably be

00:53:22.539 --> 00:53:26.000
involved. Well, not if it involves North Korea,

00:53:26.059 --> 00:53:29.179
no. We don't have oil reserves there that we

00:53:29.179 --> 00:53:32.579
want. No, but where we are, there's oil reserves.

00:53:37.420 --> 00:53:41.360
North Korea is the home of... North Korea is

00:53:41.360 --> 00:53:46.960
where Lazarus is based. So, not surprising. If

00:53:46.960 --> 00:53:51.300
this is the one we're talking about, they might

00:53:51.300 --> 00:53:55.679
have been up to this. There's a couple things

00:53:55.679 --> 00:54:02.579
going on. Did I find that there was another Russian...

00:54:04.960 --> 00:54:10.340
group. Did I post? I heard about that. Yes, you

00:54:10.340 --> 00:54:15.000
did. There was a new one. Did I post today about

00:54:15.000 --> 00:54:20.119
a Russian group that's now up to no good? It's

00:54:20.119 --> 00:54:24.460
not our usual suspects. Well, it may not be a

00:54:24.460 --> 00:54:27.699
new one, but maybe... No, it's a new one. No,

00:54:28.159 --> 00:54:35.280
it's a new one. No, you did, and... I know I

00:54:35.280 --> 00:54:37.619
heard about it on CyberWire too, but I can't

00:54:37.619 --> 00:54:40.860
remember who it was. But I don't know if it was

00:54:40.860 --> 00:54:47.340
today. It might have been yesterday. I know it

00:54:47.340 --> 00:54:52.019
was one of the last few days. Yeah. CyberWire

00:54:52.019 --> 00:54:59.659
did talk about it. The name's not coming to me.

00:54:59.719 --> 00:55:03.739
The name's not coming to me. Yeah, same way.

00:55:03.760 --> 00:55:08.019
It's not coming to me at the moment either. What

00:55:08.019 --> 00:55:13.760
was it, Mr. J? I don't remember now what the

00:55:13.760 --> 00:55:23.599
name of the thing was. Now I'm looking too. What

00:55:23.599 --> 00:55:41.510
is this? Because I know I read it too. Let me

00:55:41.510 --> 00:55:45.909
see here. I think it was a bleeping article.

00:55:46.010 --> 00:55:51.969
Let me go up there. A cyber warrior did post

00:55:51.969 --> 00:55:56.389
it, but I can't remember what day it was. I heard

00:55:56.389 --> 00:55:59.210
it. I'm like, oh, here we go. I know a new one.

00:56:01.409 --> 00:56:03.369
Because I've never heard of the group before

00:56:03.369 --> 00:56:10.650
either. Neither have I. I'm going, well, fun.

00:56:13.489 --> 00:56:25.840
Our new group, you got to watch out for it. Unless

00:56:25.840 --> 00:56:29.260
that was the EDR thing. Was that the new... I

00:56:29.260 --> 00:56:33.820
think that was the Russian group. That may have

00:56:33.820 --> 00:56:42.300
been. Yeah, Black Santa. Oh, yeah. That was probably

00:56:42.300 --> 00:56:46.159
the new one. Yeah, I think you're right. Okay,

00:56:46.380 --> 00:57:00.400
so... New Phantom... PM attack wave steals dev

00:57:00.400 --> 00:57:13.880
data. Oh, lovely. Medtech giant striker offline

00:57:13.880 --> 00:57:25.650
after Iran linked micro... What is this? Wiper

00:57:25.650 --> 00:57:38.630
malware attack. Oh. That's serious. Yeah. I think...

00:57:38.630 --> 00:57:42.369
Was Black Santa the name of the group? Or was

00:57:42.369 --> 00:57:46.489
Black Santa... That was... Okay, no. That was

00:57:46.489 --> 00:57:49.809
the name of the malware. Slash the EDR killer.

00:58:05.099 --> 00:58:07.880
I guess if you get hit, well, your Christmas

00:58:07.880 --> 00:58:13.219
won't be so merry this year. Yeah, it was a Russian

00:58:13.219 --> 00:58:18.280
-speaking threat actor. It's described as sophisticated,

00:58:18.400 --> 00:58:22.800
and it mixes social engineering with advanced

00:58:22.800 --> 00:58:31.840
evasion techniques. Wow. But no actual name.

00:58:32.760 --> 00:58:36.460
I don't think this thing mentioned a name. I

00:58:36.460 --> 00:58:40.739
would have mentioned it. No. Right, right. No,

00:58:40.840 --> 00:58:44.820
it just mentioned what they are distributing,

00:58:45.019 --> 00:58:52.099
but no name. I don't think... Maybe they don't

00:58:52.099 --> 00:58:55.860
have a name for them yet, or maybe they... They

00:58:55.860 --> 00:58:58.980
haven't classified it, apparently, yet. That's

00:58:58.980 --> 00:59:14.219
what I'm saying, is they... Okay, yeah, so that's

00:59:14.219 --> 00:59:16.760
just the name of the EDR killer. That's not the

00:59:16.760 --> 00:59:21.300
name of the group. I know I gave you the link,

00:59:21.400 --> 00:59:24.179
so you could just go directly to it, but I...

00:59:24.179 --> 00:59:29.360
That's what I'm doing, yeah. No mention, just...

00:59:29.360 --> 00:59:32.480
Okay. This is out there. This is what it is.

00:59:32.679 --> 00:59:35.239
I mean, that's kind of what I'm getting. That's

00:59:35.239 --> 00:59:37.039
what I... Okay, then that's what I got, too,

00:59:37.099 --> 00:59:40.119
because I thought I would have put the name of

00:59:40.119 --> 00:59:45.579
the group in there. Yeah. Again, again, again,

00:59:45.699 --> 00:59:51.340
again. It all comes down to the user because

00:59:51.340 --> 00:59:56.460
it says right here, it's distributed in phishing

00:59:56.460 --> 01:00:01.300
email. They believe. Well, that's they believe.

01:00:02.519 --> 01:00:08.420
It says they believe. We don't even know that.

01:00:10.639 --> 01:00:13.699
Yeah, I mean, it could be. They suspect. Okay,

01:00:13.780 --> 01:00:17.019
never mind. Yeah, I mean, it could be. That is

01:00:17.019 --> 01:00:20.119
how a lot of... How a lot of malware begins.

01:00:21.039 --> 01:00:28.380
Start, but it might not be. They believe that

01:00:28.380 --> 01:00:33.420
the target is downloading ISO files. Basically

01:00:33.420 --> 01:00:39.019
disk images. Yeah, I know. That's what ISO is.

01:00:39.760 --> 01:00:44.219
And we link to disk images and ISO in Wikipedia

01:00:44.219 --> 01:00:50.460
so that you guys can go and... One malicious

01:00:50.460 --> 01:01:06.699
ISO. Oh, that's what it does. So it executes

01:01:06.699 --> 01:01:10.219
the Windows PowerShell. You're fucked after that.

01:01:10.500 --> 01:01:16.639
Among other things, among other things, including

01:01:16.639 --> 01:01:26.659
getting rid of most, if not all, of your antivirus

01:01:26.659 --> 01:01:42.900
and disabling it. Mr. Ring. also downloads and

01:01:42.900 --> 01:01:49.559
executes a zip archive. Oh, boy. Yeah, it's bad.

01:01:51.599 --> 01:02:01.099
This is as bad as it gets, I think. Ooh. Stop

01:02:01.099 --> 01:02:07.980
sandboxes. Execution of... Most of these do now.

01:02:12.000 --> 01:02:18.400
VMs. Okay, well. That I don't think is new. That

01:02:18.400 --> 01:02:20.880
I don't think is new. A lot of them do that now.

01:02:21.360 --> 01:02:26.940
Yeah. No, the fact that it disables your antivirus

01:02:26.940 --> 01:02:35.860
and there's a hard -coded list. Yep. Yes. Including

01:02:35.860 --> 01:02:48.650
D. Crapper. Or as I call it, offender. I can

01:02:48.650 --> 01:02:52.269
also suppress Windows notifications to minimize

01:02:52.269 --> 01:03:08.780
alerts. Nick, Terry's done. I can tell. Question

01:03:08.780 --> 01:03:13.059
is, do you even think you can handle our main

01:03:13.059 --> 01:03:15.599
topic today, Terry? If you're already done by

01:03:15.599 --> 01:03:23.960
that... It says here, Ariaka did not share details

01:03:23.960 --> 01:03:28.559
on the actors or campaign details. So we don't

01:03:28.559 --> 01:03:34.059
know who it is. We don't know who it is. It could

01:03:34.059 --> 01:03:40.800
be our good friends. over there in Korea. It

01:03:40.800 --> 01:03:44.179
could be. It could be. It could be. It could

01:03:44.179 --> 01:03:47.340
be Lazarus. It could be Lazarus. That's what

01:03:47.340 --> 01:03:51.460
I was thinking. Although it's a Russian potentially

01:03:51.460 --> 01:03:56.639
speaking one. Yeah, but Lazarus could team up

01:03:56.639 --> 01:04:00.900
with anybody they want. Oh, they could. Road

01:04:00.900 --> 01:04:11.679
killer. Anti -driver. Hey, what? Terry's done,

01:04:11.820 --> 01:04:16.539
Nick. Terry's done. You know, we all know what

01:04:16.539 --> 01:04:25.340
that's for. And, um, yeah. Yeah, actually, he's

01:04:25.340 --> 01:04:34.019
still not wearing it. Well, I was... Colonel

01:04:34.019 --> 01:04:52.460
Hooks and I didn't even know, man. Yep, it's

01:04:52.460 --> 01:05:00.360
ugly. It's bad. Yeah, it's bad. And that list

01:05:00.360 --> 01:05:04.539
in that image that you see where it lists all

01:05:04.539 --> 01:05:08.960
of the antivirus or a lot of the antivirus programs

01:05:08.960 --> 01:05:13.699
that are shut down. Symantec. Symantec's in that

01:05:13.699 --> 01:05:19.349
list. Yeah. Some of them I don't recognize, but...

01:05:19.349 --> 01:05:25.190
Crappers in that list. Vectors in that list.

01:05:25.449 --> 01:05:30.289
Malwarebytes is probably there. There was one

01:05:30.289 --> 01:05:35.429
in there when I got JAWS GPT, as I call it. Python's

01:05:35.429 --> 01:05:39.329
in that list. Python is in this list. Python's...

01:05:39.329 --> 01:05:48.119
No, that's a... Python is a... Python is a programming

01:05:48.119 --> 01:05:52.639
tool, Mr. Rings. Yeah, that's not a virus. That's

01:05:52.639 --> 01:05:54.760
a programming tool. Yeah, not a language, but

01:05:54.760 --> 01:05:58.840
yeah, a programming tool. It's a programming

01:05:58.840 --> 01:06:04.940
language. Yeah, there's a lot in here. Yeah,

01:06:05.079 --> 01:06:06.780
I thought I'd seen things like... There was another

01:06:06.780 --> 01:06:11.420
one that caught my attention through Jaws GPT.

01:06:12.280 --> 01:06:14.800
That was closed. It was another major player

01:06:14.800 --> 01:06:17.360
that not too many people know about, but now

01:06:17.360 --> 01:06:21.219
I don't remember what it was. But I listed as

01:06:21.219 --> 01:06:25.159
part of our article what I wrote what JawsGPT

01:06:25.159 --> 01:06:29.920
said for that image. That came from chat, by

01:06:29.920 --> 01:06:34.300
the way. I didn't like the original writing that

01:06:34.300 --> 01:06:37.820
it gave me, so I said, show me more. So it shows

01:06:37.820 --> 01:06:42.489
me chat GPT versus Claude. So I took the chat

01:06:42.489 --> 01:06:54.170
GPT version of that. Got it. Chat GPT still beats

01:06:54.170 --> 01:06:59.090
Claude. I don't care what anyone says. And that's

01:06:59.090 --> 01:07:03.630
my opinion. I've used both just to show you guys

01:07:03.630 --> 01:07:06.730
what the difference is of what each says. But

01:07:06.730 --> 01:07:12.889
they both are good. And their own merits. But,

01:07:12.949 --> 01:07:16.469
I mean, Claude, I mean, ChatGPT actually describes

01:07:16.469 --> 01:07:20.530
more, I think. Like, if you do a photo, it'll

01:07:20.530 --> 01:07:22.969
actually tell you what the photo is. And I tried

01:07:22.969 --> 01:07:28.030
it with Claude, and it wouldn't even do it. I've

01:07:28.030 --> 01:07:32.909
been able to continue a conversation after it

01:07:32.909 --> 01:07:38.230
gives me a picture. No, but when you ask what's

01:07:38.230 --> 01:07:40.409
in it, it doesn't tell you. It says it can't

01:07:40.409 --> 01:07:42.510
tell you that. Like, I tried doing that, and

01:07:42.510 --> 01:07:45.170
it said it couldn't tell me that. Like, I asked,

01:07:45.210 --> 01:07:47.010
like, describe this picture to me, and it's like,

01:07:47.130 --> 01:07:53.170
I can't do that. For when I do a chat GPT, yeah.

01:07:54.170 --> 01:07:58.289
Hmm. I'm going to chat GPT right away. Boom.

01:08:00.090 --> 01:08:03.409
I got a description of that image from Claude.

01:08:06.659 --> 01:08:08.920
Weird. That's interesting because when I tried

01:08:08.920 --> 01:08:13.519
doing it, I took a picture of my desk and I asked

01:08:13.519 --> 01:08:15.719
it, well, what's on my desk? It said, oh, I can't

01:08:15.719 --> 01:08:22.399
tell you that. Because I wanted to test it. I

01:08:22.399 --> 01:08:26.819
wanted to fully test it and see. And it wouldn't

01:08:26.819 --> 01:08:31.239
tell me what was on my desk at all. It just said...

01:08:36.520 --> 01:08:38.319
what it was a picture of, but, like, when you

01:08:38.319 --> 01:08:42.500
ask more about it, like, say, like, I had a couple

01:08:42.500 --> 01:08:44.560
things on my desk. I'm like, well, what's this?

01:08:45.600 --> 01:08:48.560
What is this? Like, I gave it an item that was

01:08:48.560 --> 01:08:51.720
on my desk, and it's like, oh, I can't tell you

01:08:51.720 --> 01:08:55.859
about that. But, like, when I did it with ChatGPT,

01:08:55.939 --> 01:09:02.020
it's like, oh, this is a can of butane and this

01:09:02.020 --> 01:09:08.460
and that. And Claude couldn't do that. Probably

01:09:08.460 --> 01:09:12.060
because I saw the butane and thought it was going

01:09:12.060 --> 01:09:18.079
to be used for no good, so it's... Maybe, but...

01:09:18.079 --> 01:09:22.560
My chat told me what it was. It was like, oh,

01:09:22.560 --> 01:09:26.380
this is a can of Burnzomatic butane for a torch.

01:09:29.100 --> 01:09:33.100
And... I mean, I'm not saying Claude's bad. I'm

01:09:33.100 --> 01:09:35.600
not bashing Claude at all. I mean, I've used

01:09:35.600 --> 01:09:38.779
it. It's pretty good having a general conversation

01:09:38.779 --> 01:09:43.760
with it. Because it's baked into picture smart.

01:09:44.659 --> 01:09:48.079
If you say, tell me more, it'll give you chat

01:09:48.079 --> 01:09:51.060
GPT in one heading and Claude in the other. You

01:09:51.060 --> 01:09:58.100
can use what you want. Yeah, but I use the Claude

01:09:58.100 --> 01:10:02.279
app itself. And it didn't really tell me much.

01:10:02.279 --> 01:10:10.699
I don't know anything about that. itself, the

01:10:10.699 --> 01:10:20.180
actual app. And yeah, it couldn't really tell

01:10:20.180 --> 01:10:24.260
me a lot. That's why if I'm going to choose an

01:10:24.260 --> 01:10:28.380
AI, I would probably like, you know, for major

01:10:28.380 --> 01:10:37.680
stuff, I'm going to use chat because definitely

01:10:37.680 --> 01:11:08.560
better. that lights up. What else before we go

01:11:08.560 --> 01:11:26.770
into our topic? Well, we do have the Freight

01:11:26.770 --> 01:11:29.090
companies again being hit. I think we talked

01:11:29.090 --> 01:11:34.909
about on throwback, but that's happening. Go

01:11:34.909 --> 01:11:41.810
ahead and catch our listeners up on the latest

01:11:41.810 --> 01:11:49.770
on that since our last program, Mr. J. Okay,

01:11:49.869 --> 01:11:51.569
so it's been a while since I've read it, but

01:11:51.569 --> 01:11:57.880
essentially freight various freight agencies,

01:11:58.060 --> 01:12:02.000
some of which I've never heard of, are now being

01:12:02.000 --> 01:12:06.579
targeted with phishing attacks. And what I would

01:12:06.579 --> 01:12:13.560
say is, why are we surprised? And we covered

01:12:13.560 --> 01:12:19.439
it when it first broke through which blogger?

01:12:22.600 --> 01:12:24.960
If my memory serves me correctly. Who was that?

01:12:25.380 --> 01:12:36.680
Who was that? I... I even remember, too, reading

01:12:36.680 --> 01:12:40.420
this. That's what's so frustrating. If my memory

01:12:40.420 --> 01:12:45.359
serves me correctly, it was either one of two...

01:12:45.359 --> 01:13:05.779
Crabs. Or bleeping? I think it was Krebs. Wait

01:13:05.779 --> 01:13:08.239
a minute, no. Actually, I think it might have

01:13:08.239 --> 01:13:15.619
been bleeping. It was one of the two. But, some

01:13:15.619 --> 01:13:17.239
of the other things that I think have popped

01:13:17.239 --> 01:13:21.500
up since our last airing, Krebs did do a deep

01:13:21.500 --> 01:13:29.279
dive into box. I want to do a write -up on that

01:13:29.279 --> 01:13:38.220
because it's still in my email. And he also did

01:13:38.220 --> 01:13:43.340
one on Kim Wolf, too. And that was a two -article

01:13:43.340 --> 01:13:47.199
thing, but I only did the second. Link to the

01:13:47.199 --> 01:14:27.239
one. Okay. See if that's familiar. Okay, I'll

01:14:27.239 --> 01:14:29.859
go click on that, but that's the article I'm

01:14:29.859 --> 01:15:51.460
remembering from back then, yep. tools. Bleeping

01:15:51.460 --> 01:16:03.420
computer looks like where this came from. I knew

01:16:03.420 --> 01:16:09.979
it was one of two. And we covered this article.

01:16:14.920 --> 01:16:55.220
Yes. 262 will be your TSB. What else, Mr. J?

01:17:00.500 --> 01:17:04.680
Well, we talked about some of these on throwback,

01:17:04.739 --> 01:17:07.479
and I'm torn because it's basically the same

01:17:07.479 --> 01:17:12.079
crew. We had the one about the mental health

01:17:12.079 --> 01:17:17.840
apps, many of which have... Did I go completely

01:17:17.840 --> 01:17:30.890
freaking... utterly fucking ape. You did. You

01:17:30.890 --> 01:17:35.329
did on throwback, I remember. For the throwback

01:17:35.329 --> 01:17:39.550
crew, you did. You did, yes. I just kind of sat

01:17:39.550 --> 01:17:42.869
back and was like, oh, Jared's riled up tonight.

01:17:43.649 --> 01:17:55.510
Yes, I have four... I remember like reading this

01:17:55.510 --> 01:18:09.770
and I'm like, our people who need more help than

01:18:09.770 --> 01:18:20.010
your typical regular blind person. Yeah, I mean,

01:18:20.010 --> 01:18:22.689
it depends on what happened in her life, too.

01:18:23.250 --> 01:18:33.010
It's going to be completely done for. And these

01:18:33.010 --> 01:18:55.130
are your typical apps. I'll save the diatribe.

01:18:55.270 --> 01:19:05.350
Ask TSB for the archive if you want. Ask Throwback

01:19:05.350 --> 01:19:08.510
for the archive if you want it. Sorry. Because

01:19:08.510 --> 01:19:09.949
I don't have that archive. That was Saturday.

01:19:11.250 --> 01:19:18.069
Was that last Saturday? Saturday before... No,

01:19:18.229 --> 01:19:22.130
I think it was the 28th. Okay. I can grab it

01:19:22.130 --> 01:19:31.199
if you want. Because I'm like... This has to...

01:19:31.199 --> 01:19:37.640
I don't even know if I have words to be nice

01:19:37.640 --> 01:19:46.960
anymore about this article. It still rubs me

01:19:46.960 --> 01:19:55.949
the wrong way. 14 .7 million downloads, and these

01:19:55.949 --> 01:19:59.050
are really not that secure. And they have basically

01:19:59.050 --> 01:20:10.069
a lot of security holes. Yep. If you think it,

01:20:10.130 --> 01:20:16.930
it's probably there. It's like, could I be identified?

01:20:17.210 --> 01:20:21.270
Uh -huh. worried that someone's going to know

01:20:21.270 --> 01:20:25.770
about this. Yep, that's well -founded. A little

01:20:25.770 --> 01:20:29.810
too far -fetched. Yes, they already know about

01:20:29.810 --> 01:20:36.250
it. Well, I didn't need them to know that I'm

01:20:36.250 --> 01:20:41.810
not sleeping that great. Well, they know now.

01:20:47.810 --> 01:20:51.319
Well, the only really takes care of the problem

01:20:51.319 --> 01:20:57.579
is... Well, they know about that, too. Oh, yes,

01:20:57.579 --> 01:21:02.460
they do. They know about the Cialis that was

01:21:02.460 --> 01:21:07.079
given at the doctor's office for my... I don't

01:21:07.079 --> 01:21:10.260
want to say much more because it's going to feed

01:21:10.260 --> 01:21:12.880
into our topic somewhat, but... Oh, yeah, I'm

01:21:12.880 --> 01:21:14.779
not going to say much more either. Into this

01:21:14.779 --> 01:21:21.489
topic? Into our main one. I'm going to be switching

01:21:21.489 --> 01:21:34.630
over here in a minute. Yes. Okay. I wonder if

01:21:34.630 --> 01:21:37.130
the chat even said that it could tie that to

01:21:37.130 --> 01:21:40.850
269. And I said, I'm not even ready for 269 yet.

01:21:41.369 --> 01:21:46.170
Because I was still working on 68. Or no, I was...

01:21:46.170 --> 01:21:50.170
No, I was... Still dealing with the computer.

01:21:50.949 --> 01:21:54.210
No, I was still dealing with the computer. We

01:21:54.210 --> 01:21:57.890
could have. It would have been, I think, a natural

01:21:57.890 --> 01:22:13.340
tie -in, but yes. Mr. Ring. Yeah, I think now

01:22:13.340 --> 01:22:16.399
that I'm thinking about it, ChatGPT did say that

01:22:16.399 --> 01:22:20.039
that article could be fit with 269. I said, this

01:22:20.039 --> 01:22:23.680
is Nick's baby. I'm not doing anything with 269.

01:22:24.359 --> 01:22:28.439
I'm going to work on 270. My plan is... My plan

01:22:28.439 --> 01:22:34.399
is... Never mind. I didn't write it in there.

01:22:34.840 --> 01:22:37.119
I didn't write it in there, but I am aware of

01:22:37.119 --> 01:22:47.359
it. I'll just say that. Did I go on a diatribe

01:22:47.359 --> 01:23:00.039
on that? I think you did, actually. We're talking

01:23:00.039 --> 01:23:03.579
about the people who can't even speak up for

01:23:03.579 --> 01:23:19.510
themselves. Who have no idea what's going on.

01:23:29.670 --> 01:23:41.930
What else? Oh, boy. Not cyber security related,

01:23:42.090 --> 01:23:44.409
but there was the thing, and it really is irrelevant

01:23:44.409 --> 01:23:48.289
now, but the whole daylight saving time change

01:23:48.289 --> 01:23:53.869
announcement. Well, I only put that up so that

01:23:53.869 --> 01:23:59.090
the blog knows that we change times so that if

01:23:59.090 --> 01:24:01.850
they're expecting blogs at certain times and

01:24:01.850 --> 01:24:06.369
we schedule them, that we've changed the time

01:24:06.369 --> 01:24:13.939
on the blog. Okay. I do that every time. We just

01:24:13.939 --> 01:24:16.560
want people to know that we've changed the time

01:24:16.560 --> 01:24:20.460
because we have to do that by hand. It's minus

01:24:20.460 --> 01:24:24.600
seven hours or minus eight. There's no way to

01:24:24.600 --> 01:24:31.699
automate that. Oh, man. So I have to post or

01:24:31.699 --> 01:24:34.159
just leave it alone. I just change it internally,

01:24:34.220 --> 01:24:42.340
but I make it public so that... People are going,

01:24:42.420 --> 01:24:50.579
why are you posting an hour off? Right. Yeah.

01:24:59.680 --> 01:25:09.739
Okay. Who needs a break? Before we get in. I

01:25:09.739 --> 01:25:19.819
am okay. to our topic. Yeah, I'm good. Okay.

01:25:30.739 --> 01:25:51.859
Where is my file? Where's my file? TSB 269. PHI.

01:25:54.800 --> 01:26:01.300
And our personal information, Mr. J, why? Companies

01:26:01.300 --> 01:26:14.520
don't protect it. Why did we choose it? I think

01:26:14.520 --> 01:26:20.739
mainly it's because of some trends we've been

01:26:20.739 --> 01:26:23.239
seeing. I'm not going to name names and certain

01:26:23.239 --> 01:26:30.100
behaviors. Again, no names. And why this is potentially

01:26:30.100 --> 01:26:34.760
extremely risky to do. But it extends beyond

01:26:34.760 --> 01:26:40.289
that behavior of said individuals. And, you know,

01:26:40.310 --> 01:26:43.130
because I was, as you know, initially going to

01:26:43.130 --> 01:26:47.430
do that, but I think this is better. And what

01:26:47.430 --> 01:26:54.130
did you learn from you handling the topic versus

01:26:54.130 --> 01:27:03.350
me? Besides that I couldn't. Well, what I learned,

01:27:03.350 --> 01:27:05.770
unfortunately, is that there is a lot of overlap

01:27:05.770 --> 01:27:11.359
with what we've been talking about. And when

01:27:11.359 --> 01:27:16.399
I was sending all of the emails to chat, all

01:27:16.399 --> 01:27:20.699
of those emails, just to sort of see what it

01:27:20.699 --> 01:27:29.479
knew about. And it knows quite a bit. And then

01:27:29.479 --> 01:27:32.319
it's like, oh, you should do this as a topic.

01:27:32.399 --> 01:27:34.380
And then it would give me what the topic name

01:27:34.380 --> 01:27:40.130
is. And it's like, oh. So now it knows the entire

01:27:40.130 --> 01:27:52.729
topic history. Wow. Yeah. Well, I think what

01:27:52.729 --> 01:27:57.569
we are going to do, since I broke after the first

01:27:57.569 --> 01:28:00.689
file because I wanted to put that up on Livewire,

01:28:00.869 --> 01:28:04.069
what we're going to do now is we're going to

01:28:04.069 --> 01:28:10.560
break. We're going to play... the files and sorry

01:28:10.560 --> 01:28:14.800
for the second one being half robotic. I didn't

01:28:14.800 --> 01:28:18.020
realize it until I was done. We'll probably do

01:28:18.020 --> 01:28:22.300
a full taping of this and re -release it as part

01:28:22.300 --> 01:28:27.100
of 270. But I want to get these files out because

01:28:27.100 --> 01:28:33.000
one deals with scams in your inbox and the other

01:28:33.000 --> 01:28:39.399
and then That actually has a second segment dealing

01:28:39.399 --> 01:28:43.979
with three questions you could ask when you get

01:28:43.979 --> 01:28:49.819
a suspicious email. And the other one that we

01:28:49.819 --> 01:28:57.359
did tape came from chat GPT and a discussion.

01:29:01.960 --> 01:29:08.119
And I got into a whole scam discussion with it.

01:29:08.420 --> 01:29:18.199
And it actually talks about something we have

01:29:18.199 --> 01:29:21.159
actually talked about on this program before.

01:29:23.920 --> 01:29:39.880
Oh. Yep. The scam you'll know as the grandparent

01:29:39.880 --> 01:29:49.699
scam. Oh, not that one again. And the fact that

01:29:49.699 --> 01:29:55.720
tools can be used to mimic voices now and how

01:29:55.720 --> 01:30:00.539
easy it is for AI to now get involved and make

01:30:00.539 --> 01:30:09.880
it So we have segments on these. So we'll play

01:30:09.880 --> 01:30:14.300
these. I do seem to remember. We'll play these.

01:30:14.880 --> 01:30:19.199
You've got the braille files of those if you

01:30:19.199 --> 01:30:24.600
want to read them. They're not the greatest braille.

01:30:25.100 --> 01:30:27.420
I've got to do better, but I was kind of in a

01:30:27.420 --> 01:30:31.020
hurry. Now that I knew that TSB needed to be

01:30:31.020 --> 01:30:35.239
done. So we'll make sure that gets cleaned up.

01:30:35.600 --> 01:30:42.659
But we'll do those. And then when we come back,

01:30:42.819 --> 01:30:48.000
personal health information and why companies

01:30:48.000 --> 01:30:53.119
can't seem to keep our data safe. But yet, if

01:30:53.119 --> 01:31:00.239
you listen to Podcast 268, mean to toot my own

01:31:00.239 --> 01:31:04.880
horn here. Beep, beep. But I think I'm the only

01:31:04.880 --> 01:31:06.720
one that cares about our personal information.

01:31:07.880 --> 01:31:17.460
Oops. Did I just say that? Yes, you did. Well,

01:31:17.460 --> 01:31:19.680
Jared, you gotta remember what companies do with

01:31:19.680 --> 01:31:22.600
our personal information. They sell it. So, I

01:31:22.600 --> 01:31:27.920
mean, it's profit for them. I want profit, but...

01:31:29.609 --> 01:31:33.529
I think it's illegal to sell people's information

01:31:33.529 --> 01:31:36.189
without their knowledge. I think it is. I think

01:31:36.189 --> 01:31:45.090
it is. But it sits within this gray zone. Yeah.

01:31:47.409 --> 01:31:57.369
Because policies say we may. Well, I say I don't.

01:31:58.090 --> 01:32:04.880
Yes. Oh, if you opt in this, well, then I won't

01:32:04.880 --> 01:32:07.920
opt in next time. You know, I won't opt in. You

01:32:07.920 --> 01:32:17.159
know, it's stupid. It's like all these damn political

01:32:17.159 --> 01:32:21.300
texts I've been getting. Oh, my God. Oh, Nick.

01:32:22.479 --> 01:32:29.060
That reminds me. Uh -oh. Yes. Before. I push

01:32:29.060 --> 01:32:34.340
buttons. Preston and I were sending a bunch of

01:32:34.340 --> 01:32:40.060
texts in the group yesterday. And you happened

01:32:40.060 --> 01:32:47.319
to say that informed delivery notified you that

01:32:47.319 --> 01:32:50.359
you were going to get one of these in the mail.

01:32:52.260 --> 01:33:01.539
Correct. Tell us more. So this is about something

01:33:01.539 --> 01:33:06.119
here in California. There probably are variations

01:33:06.119 --> 01:33:11.220
of it in other states. The Transparency Act and

01:33:11.220 --> 01:33:15.659
this basically petition that is circulating.

01:33:28.060 --> 01:33:34.399
Depending on what is captured is very accessible,

01:33:34.579 --> 01:33:38.159
and you can know exactly what it is based on

01:33:38.159 --> 01:33:42.079
a few words. And that was one of them for this.

01:33:42.680 --> 01:33:52.819
And this was one of those. Oh, geez. Because

01:33:52.819 --> 01:33:56.739
I got a text message. about one of these things,

01:33:56.920 --> 01:34:03.659
and I refuse to click on links anymore. Right.

01:34:06.699 --> 01:34:08.899
I mean, I've been getting a ton of these political

01:34:08.899 --> 01:34:11.319
ads. I think I posted a couple of them in the

01:34:11.319 --> 01:34:17.680
group. You did. And I'm just like, here we go.

01:34:22.900 --> 01:34:25.619
And it's always the same thing, and this is part

01:34:25.619 --> 01:34:27.899
of the reason I unsubscribe from a bunch of them.

01:34:27.979 --> 01:34:30.699
It's, can you just chip in some so we can meet

01:34:30.699 --> 01:34:32.859
our end of quarter fundraising goal? It's like,

01:34:32.899 --> 01:34:39.079
I'm sick of this. Yeah. Yeah. No. I've actually

01:34:39.079 --> 01:34:43.239
tried to unsubscribe from them. I did type stop

01:34:43.239 --> 01:34:47.920
to a few of them. But somehow I'm still getting

01:34:47.920 --> 01:34:58.819
more of them. I was for a while on what I think

01:34:58.819 --> 01:35:04.779
was like the Trump campaigns text thing. Because

01:35:04.779 --> 01:35:07.420
it would start out like the same way. It was

01:35:07.420 --> 01:35:14.239
like 88022. I got those in 10 -digit phone numbers.

01:35:16.260 --> 01:35:18.640
Interesting. Yeah, because these I didn't. These

01:35:18.640 --> 01:35:22.920
I got as short codes. No, I got them in 10 -digit

01:35:22.920 --> 01:35:28.220
phone numbers. Huh. Yeah, after a while... And

01:35:28.220 --> 01:35:33.100
it tells me... If you don't... The latest one

01:35:33.100 --> 01:35:36.239
was, you're going to lose your MAGA membership.

01:35:36.800 --> 01:35:41.060
I got two of them. One from a 915 and another

01:35:41.060 --> 01:35:45.520
one from some other area code. If you don't fill

01:35:45.520 --> 01:35:48.729
this out in the next... You know, by midnight,

01:35:48.890 --> 01:35:52.489
you're going to lose your MAGA membership. Like,

01:35:52.489 --> 01:35:55.449
well, fine. I don't have one to begin with. I

01:35:55.449 --> 01:35:58.949
don't have one anyway. How can I lose a membership

01:35:58.949 --> 01:36:01.649
I don't have? That's okay. I got an Amazon one

01:36:01.649 --> 01:36:09.149
saying, oh, you had ordered an iPhone 13 Pro,

01:36:09.310 --> 01:36:14.329
and if you don't get back to us, the order will

01:36:14.329 --> 01:36:18.899
proceed. and be charged, whatever. I'm like,

01:36:18.960 --> 01:36:21.000
yeah, okay. Yeah, I never ordered an iPhone 13

01:36:21.000 --> 01:36:25.439
Pro on Amazon. Okay, sure. But even if you did...

01:36:25.439 --> 01:36:29.539
None of my payment methods... I was going to

01:36:29.539 --> 01:36:34.560
say, even if you did, it would already be fulfilled

01:36:34.560 --> 01:36:38.699
already. So why are you texting me telling me

01:36:38.699 --> 01:36:42.979
that I ordered an iPhone 13 if I don't do anything?

01:36:43.819 --> 01:36:45.680
Then you're going to ship it anyway. That's the

01:36:45.680 --> 01:36:53.819
hell what I want. Yes. Then I'm like, okay. I'm

01:36:53.819 --> 01:36:56.119
going to go and look just to make sure that nobody

01:36:56.119 --> 01:36:59.079
hacked my account because you never know. Nope.

01:36:59.399 --> 01:37:02.039
No iPhone 13 Pro in my orders list. I'm like,

01:37:02.079 --> 01:37:04.239
yeah, okay, right. Sure, I ordered an iPhone

01:37:04.239 --> 01:37:11.579
13 Pro. Go move on to someone else who will believe

01:37:11.579 --> 01:37:13.979
it because I'm not going to believe it. There

01:37:13.979 --> 01:37:18.359
undoubtedly will be someone who will. That's

01:37:18.359 --> 01:37:20.100
why they keep doing it, Terry. Yeah, I know.

01:37:20.659 --> 01:37:26.600
Remember that article we read about how I think

01:37:26.600 --> 01:37:29.739
after, what was it, a day or two, they just give

01:37:29.739 --> 01:37:34.460
up and move on if you don't respond or something

01:37:34.460 --> 01:37:37.739
like that? They haven't given up on me. They

01:37:37.739 --> 01:37:40.359
keep telling me my manga membership's expired.

01:37:41.979 --> 01:37:50.880
Oh, yeah. What the hell is manga? Manga, manga.

01:37:51.119 --> 01:38:01.880
Make America great again. Oh, Jesus. America's

01:38:01.880 --> 01:38:04.100
becoming... What do you get with that membership?

01:38:04.159 --> 01:38:10.239
Probably a free... Who knows? Free Trump t -shirt?

01:38:14.449 --> 01:38:17.449
Probably. Maybe you get some Trump socks. Yeah.

01:38:17.729 --> 01:38:22.229
Some Trump... Paraphernalia. Yeah, some Trump

01:38:22.229 --> 01:38:27.489
socks. Maybe a hat. Maybe a sign that says, Make

01:38:27.489 --> 01:38:32.909
America Great Again. Then I can never wave around

01:38:32.909 --> 01:38:42.569
because I'll probably get my ass... Yeah, right.

01:38:44.630 --> 01:38:55.250
Kicked. Yeah. Email, iMessage, tech, T -E -C

01:38:55.250 --> 01:39:00.470
-H at M -E -N -V -I dot org. Text or WhatsApp,

01:39:00.689 --> 01:39:07.590
804 -442 -6975. Call the comment line, 888 -405

01:39:07.590 --> 01:39:18.579
-7525. Q4. Gentlemen, I think what I'm going

01:39:18.579 --> 01:39:28.840
to do is I'm going to go find me a drink. Shall

01:39:28.840 --> 01:39:42.460
we play a song? Yes. Do I have any drinks in

01:39:42.460 --> 01:39:48.460
here? I'm going to go grab myself one. Let's...

01:39:48.460 --> 01:40:07.239
Play for the 35 acoustic pop hits from the guitar

01:40:07.239 --> 01:40:15.050
tribute players. And I'll play two. Should I

01:40:15.050 --> 01:40:18.310
play two? Give you guys a break? Sure, yeah.

01:40:19.310 --> 01:40:27.010
Might as well. Okay. We'll play Some Nights and

01:40:27.010 --> 01:40:41.399
a very popular track, Brimes' I'd Girl. This

01:40:41.399 --> 01:40:45.619
is a 2012 release, and after these two tracks,

01:40:45.720 --> 01:40:52.060
we will come back with more of TSB. You've got

01:40:52.060 --> 01:40:56.979
the Security Box Program 269 across the Jared

01:40:56.979 --> 01:41:23.250
Reimer Radio Network. Before we continue, I want

01:41:23.250 --> 01:41:26.350
to take a few minutes to follow up on something

01:41:26.350 --> 01:41:31.829
that came out of Saturday, February 21st or 28th's

01:41:31.829 --> 01:41:39.189
program. At the time I did this, the system put

01:41:39.189 --> 01:41:45.210
it as last week, but it's been some time, so

01:41:45.210 --> 01:41:50.640
I had to change it, and you can ask... Throwback

01:41:50.640 --> 01:41:54.439
Saturday night for either of those shows, and

01:41:54.439 --> 01:41:59.819
it might be there. During that discussion, the

01:41:59.819 --> 01:42:04.659
topic of scams came up again. When does it ever

01:42:04.659 --> 01:42:09.720
not come up, actually? And it made me realize

01:42:09.720 --> 01:42:15.260
just how much this evolved recently, especially

01:42:15.260 --> 01:42:23.000
with AI now being part... of the picture. So,

01:42:23.199 --> 01:42:30.340
for this episode, I've put together a short series

01:42:30.340 --> 01:42:37.439
of segments looking at modern scams, why we're

01:42:37.439 --> 01:42:42.359
seeing more of them, and how to recognize them

01:42:42.359 --> 01:42:47.979
quickly. We'll start with a look at how AI has

01:42:47.979 --> 01:42:57.529
changed The scam landscape. Oh, boy. That might

01:42:57.529 --> 01:43:04.710
actually be familiar to you guys, too. Because

01:43:04.710 --> 01:43:11.529
we've definitely talked about some of these as

01:43:11.529 --> 01:43:22.619
well. We're going to title this, AI Scam, The

01:43:22.619 --> 01:43:30.520
Same Tricks, Smarter Tools. Over the past few

01:43:30.520 --> 01:43:35.380
years, many of us have learned to recognize online

01:43:35.380 --> 01:43:42.300
scams, fake emails, urgent warnings, and messages.

01:43:43.880 --> 01:43:49.460
Trying to get us to act before we think. Well,

01:43:49.779 --> 01:43:57.119
some of us haven't been bitten. But something

01:43:57.119 --> 01:44:03.760
important has changed recently. The scams themselves

01:44:03.760 --> 01:44:11.810
are not new. What's new? Is that artificial intelligence

01:44:11.810 --> 01:44:20.189
is now helping criminals make those scams sound

01:44:20.189 --> 01:44:29.529
real. Sometimes very real. And that means the

01:44:29.529 --> 01:44:36.039
skills we learned years ago still work. But we

01:44:36.039 --> 01:44:43.739
need to apply them more carefully. So, let me

01:44:43.739 --> 01:44:51.500
explain. Years ago, many of us saw fake domain

01:44:51.500 --> 01:44:56.640
renewal emails. And from time to time, I've talked

01:44:56.640 --> 01:45:05.189
about those here on TSB. They claimed your website

01:45:05.189 --> 01:45:09.710
was about to expire within 24 hours. They looked

01:45:09.710 --> 01:45:13.850
official, used technical language, and tried

01:45:13.850 --> 01:45:24.170
to pressure you into paying immediately. But

01:45:24.170 --> 01:45:27.829
the problem here, if you really looked at the

01:45:27.829 --> 01:45:34.130
links, you found... That maybe it didn't make

01:45:34.130 --> 01:45:37.770
sense. Or maybe you own a domain and you just

01:45:37.770 --> 01:45:42.670
got curious. So you went looking. And it's offering

01:45:42.670 --> 01:45:50.590
services that your registrar may or may not offer.

01:45:52.289 --> 01:45:56.109
That probably mean nothing. And they charge an

01:45:56.109 --> 01:46:02.069
arm and a leg for. If you knew when your domain

01:46:02.069 --> 01:46:07.470
actually expired, the scam fell apart. And that's

01:46:07.470 --> 01:46:12.329
the whole point. Knowing when your domains expire,

01:46:12.569 --> 01:46:17.189
or even if you were curious, you'd be like, why

01:46:17.189 --> 01:46:26.109
is this costing so much? Today's AI scams work

01:46:26.109 --> 01:46:31.159
the same way just with better tools. Instead

01:46:31.159 --> 01:46:35.800
of fake registrar emails, scammers can now impersonate

01:46:35.800 --> 01:46:40.859
people. They can clone voices using audio taken

01:46:40.859 --> 01:46:46.739
from podcasts, social media, or public recordings.

01:46:46.939 --> 01:46:52.039
In some cases, only a short sample is needed.

01:46:52.340 --> 01:46:59.020
Yes, 11 labs, as an example, only needs 8 seconds

01:46:59.020 --> 01:47:09.300
to 10 seconds of your voice. And as it learns

01:47:09.300 --> 01:47:15.300
over time, it can make it sound just like you.

01:47:21.340 --> 01:47:27.760
So, Someone might receive a call that sounds

01:47:27.760 --> 01:47:31.899
exactly like a child, grandchild, co -worker,

01:47:32.039 --> 01:47:36.300
or friend saying, I'm in trouble. I need money

01:47:36.300 --> 01:47:42.819
right now. The emotional pressure is the same

01:47:42.819 --> 01:47:49.180
trick scammers have always used. Urgency. But

01:47:49.180 --> 01:47:54.369
now the voice sounds familiar. And... That's

01:47:54.369 --> 01:48:00.850
where people get caught off guard. Here's the

01:48:00.850 --> 01:48:05.710
important part. AI did not invent new scams.

01:48:05.989 --> 01:48:09.829
AI simply removed the obvious warning signs.

01:48:10.949 --> 01:48:19.050
Bad grammar is gone. Awkward wording is gone.

01:48:20.220 --> 01:48:27.140
Even fake voices can sound convincing. So, how

01:48:27.140 --> 01:48:34.239
do you protect yourself? Five seconds to come

01:48:34.239 --> 01:48:44.239
up with an answer. Starting now. The answer is

01:48:44.239 --> 01:48:49.100
surprisingly simple. You stop. trusting the incoming

01:48:49.100 --> 01:48:54.260
message and you verify using a different method

01:48:54.260 --> 01:49:00.680
security professionals call this out of band

01:49:00.680 --> 01:49:05.899
verification but it really just means this if

01:49:05.899 --> 01:49:10.760
someone contacts you with an emergency don't

01:49:10.760 --> 01:49:17.060
respond only through that same conversation use

01:49:17.060 --> 01:49:22.260
another channel if you get a call send a text

01:49:22.260 --> 01:49:27.380
message to the real person if you get a message

01:49:27.380 --> 01:49:33.760
call them directly using a number you already

01:49:33.760 --> 01:49:40.439
trust if you share location services with family

01:49:40.439 --> 01:49:45.689
or friends check those Not to reveal personal

01:49:45.689 --> 01:49:49.750
information, but to confirm whether the story

01:49:49.750 --> 01:49:55.729
even makes sense. For example, if someone claims

01:49:55.729 --> 01:50:00.789
they're stranded overseas, but you can see they

01:50:00.789 --> 01:50:05.130
appear to be at home, something clearly doesn't

01:50:05.130 --> 01:50:10.250
add up. We've done that with Nick. Remember that?

01:50:11.409 --> 01:50:16.800
We... played a little trick where we said, if

01:50:16.800 --> 01:50:22.960
I got a call from Nick, and Nick said that he

01:50:22.960 --> 01:50:28.619
was in Russia and needed help, because I follow

01:50:28.619 --> 01:50:35.000
Nick, I could get on my phone, I could go ahead

01:50:35.000 --> 01:50:41.260
and look, and I could say, well, Nick, this is

01:50:41.260 --> 01:50:47.409
very interesting. I see you're at home. I would

01:50:47.409 --> 01:50:53.789
never reveal Nick's current location or any location,

01:50:54.010 --> 01:51:01.350
but I could say something like, well, it looks

01:51:01.350 --> 01:51:07.069
like you're at home. And maybe he could say,

01:51:07.149 --> 01:51:12.569
well, I took a trip. Well, uh, How could you

01:51:12.569 --> 01:51:17.130
take a trip if your phone is telling me you're

01:51:17.130 --> 01:51:24.890
at home? So, I could then get on the phone and

01:51:24.890 --> 01:51:36.449
call him and do a little verification. Of course,

01:51:36.470 --> 01:51:39.090
I wouldn't use the same device in case I got

01:51:39.090 --> 01:51:43.300
voicemail. where the scammer could, in theory,

01:51:43.479 --> 01:51:49.000
get his phone number, because you can say, Hi,

01:51:49.260 --> 01:51:57.020
I'm Nick at 804 -442 -6975. Please leave a message

01:51:57.020 --> 01:52:00.420
and I'll get back to you. Now, of course, the

01:52:00.420 --> 01:52:03.979
804 number I just handed out is mine, but you

01:52:03.979 --> 01:52:11.260
get the idea right here. And here's an important

01:52:11.260 --> 01:52:15.560
rule to remember. Anyone who tells you not to

01:52:15.560 --> 01:52:19.680
verify is almost certainly trying to scam you.

01:52:20.119 --> 01:52:23.899
Real emergencies don't prevent verification.

01:52:24.720 --> 01:52:30.979
Scammers depend on panic and speed. They want

01:52:30.979 --> 01:52:36.960
you to act before you think. Another useful protection

01:52:36.960 --> 01:52:45.319
is... Something simple you can agree on ahead

01:52:45.319 --> 01:52:53.880
of time with people you trust. A verification

01:52:53.880 --> 01:53:00.560
question or phrase. Something only you and that

01:53:00.560 --> 01:53:06.829
person would know. AI can copy a voice. but it

01:53:06.829 --> 01:53:11.069
can't reliably know private agreements between

01:53:11.069 --> 01:53:17.770
real people. The big takeaway here is this. Technology

01:53:17.770 --> 01:53:23.470
changes, but scams don't. Whether it was fake

01:53:23.470 --> 01:53:29.289
domain renewal notices years ago or AI voice

01:53:29.289 --> 01:53:34.970
impersonation today, the goal is always the same.

01:53:35.720 --> 01:53:41.260
create urgency and gain trust long enough to

01:53:41.260 --> 01:53:48.039
make you act. And the defense is also the same.

01:53:49.239 --> 01:53:55.520
Slow down, verify independently, and trust relationships,

01:53:55.819 --> 01:54:01.899
not unexpected messages. If you ever receive

01:54:01.899 --> 01:54:06.079
something that feels urgent, or unusual, take

01:54:06.079 --> 01:54:09.939
a moment to confirm through another method before

01:54:09.939 --> 01:54:16.079
doing anything else. That one step defeats most

01:54:16.079 --> 01:54:24.039
scams immediately. If you've encountered something

01:54:24.039 --> 01:54:31.000
like this, or if you have questions, feel free

01:54:31.000 --> 01:54:35.130
to reach out after the show. Through our usual

01:54:35.130 --> 01:54:40.609
contact channels. Stay informed. And sharing

01:54:40.609 --> 01:54:48.350
experiences. Help everyone stay safer. What do

01:54:48.350 --> 01:54:55.350
you think? Email iMessage tech, T -E -C -H, at

01:54:55.350 --> 01:55:02.390
M -E -N -V -I dot org. Text or WhatsApp. The

01:55:02.390 --> 01:55:05.590
aforementioned 804 number I gave earlier when

01:55:05.590 --> 01:55:11.189
talking about calling Nick directly. Although

01:55:11.189 --> 01:55:17.369
it'll reach me, so call or text 804 -442 -6975.

01:55:19.470 --> 01:55:24.810
And you... You may also call the comment line

01:55:24.810 --> 01:55:31.130
at 888 -405 -7524 and drop a message and let

01:55:31.130 --> 01:55:37.310
me know what you think. Let's roll. Tell me what

01:55:37.310 --> 01:55:40.310
you think. I know we've talked about these things

01:55:40.310 --> 01:55:46.550
before, but during my downtime, I really started

01:55:46.550 --> 01:55:50.409
wondering how to better get this type of information

01:55:50.409 --> 01:55:55.829
out there. And this is another way to do it.

01:55:56.649 --> 01:56:01.069
Let people know what's out there. Let them figure

01:56:01.069 --> 01:56:07.710
it out. Let them understand. And let them ask

01:56:07.710 --> 01:56:26.119
questions. Understanding scams coming to email

01:56:26.119 --> 01:56:36.859
boxes. Why you're seeing so much scam email now.

01:56:39.159 --> 01:56:47.340
Over the past few weeks and honestly over the

01:56:47.340 --> 01:56:55.430
past few years. I've been seeing a lot of the

01:56:55.430 --> 01:57:00.250
junk that lands in my inbox and through my website

01:57:00.250 --> 01:57:07.130
contact forms. And if you run a website, a podcast,

01:57:07.409 --> 01:57:13.170
or even just an email address that's been around

01:57:13.170 --> 01:57:34.520
for a long time, email has exploded. You are

01:57:34.520 --> 01:57:41.020
getting job offers you never applied for, error

01:57:41.020 --> 01:57:45.579
reports for problems that don't exist, payment

01:57:45.579 --> 01:57:49.460
confirmations for things you never bought, and

01:57:49.460 --> 01:57:54.939
messages replying to conversations that never

01:57:54.939 --> 01:58:13.859
even happened. So, what changed? Here's the important

01:58:13.859 --> 01:58:19.340
part. The scammers themselves didn't really change.

01:58:19.779 --> 01:58:26.039
The writing changed. What we're seeing now is

01:58:26.039 --> 01:58:36.140
scammers using automated things and AI tools

01:58:36.140 --> 01:58:40.539
to generate endless variations of the same old

01:58:40.539 --> 01:58:49.319
tricks. So automation is out there and they're

01:58:49.319 --> 01:58:59.920
also using the same tricks. years ago these emails

01:58:59.920 --> 01:59:03.520
were easy to spot because the grammar was terrible

01:59:03.520 --> 01:59:09.300
and the stories were obvious today they sound

01:59:09.300 --> 01:59:14.359
more polite more professional and sometimes even

01:59:14.359 --> 01:59:20.399
personalized we talked about one of these job

01:59:20.399 --> 01:59:45.000
offers an email and we even read it on air but

01:59:45.000 --> 01:59:56.779
there's still telltale signs but underneath there's

01:59:56.779 --> 02:00:02.000
still running the same playbook. They pretend

02:00:02.000 --> 02:00:06.180
you already started something. A job application,

02:00:06.680 --> 02:00:10.100
a business conversation, a technical support

02:00:10.100 --> 02:00:16.199
request. Because people trust ongoing conversations

02:00:16.199 --> 02:00:20.579
more than random messages. We've talked through

02:00:20.579 --> 02:00:33.350
the last while about emails that start with on

02:00:33.350 --> 02:00:37.010
jaredramer .net. Would you like a price quote?

02:00:37.109 --> 02:00:43.109
We found a bunch of errors on your website. Well,

02:00:43.289 --> 02:00:45.930
why don't you just give me the error messages?

02:00:48.210 --> 02:00:52.609
Oh, and by the way, they are now sending email

02:00:52.609 --> 02:01:07.439
to themselves. Probably... a problem waiting

02:01:07.439 --> 02:01:12.260
for you. Undelivered emails, website errors,

02:01:12.479 --> 02:01:17.760
account issues because urgency makes people react

02:01:17.760 --> 02:01:22.300
before they think and they offer opportunities

02:01:22.300 --> 02:01:27.340
that sound easy. They won't work recognition

02:01:27.340 --> 02:01:34.159
awards investment money because curiosity lowers

02:01:37.800 --> 02:01:42.840
What's really happening is volume. These messages

02:01:42.840 --> 02:01:48.479
aren't written by a person sitting at a keyboard

02:01:48.479 --> 02:01:53.140
anymore. Software generates thousands of slightly

02:01:53.140 --> 02:01:57.100
different emails and sends them automatically.

02:01:58.020 --> 02:02:01.779
If even a tiny percentage of people respond,

02:02:02.119 --> 02:02:12.069
the scam works. it feels like you're suddenly

02:02:12.069 --> 02:02:19.489
downing a beer when you really should be looking

02:02:19.489 --> 02:02:23.609
at email and drowning in drunk mail. Okay, I

02:02:23.609 --> 02:02:27.090
added some of that, but think about it, folks.

02:02:29.270 --> 02:02:33.489
You probably want to drown in a beer or some

02:02:33.489 --> 02:02:41.159
alcohol if that's what you enjoy. Because you

02:02:41.159 --> 02:02:45.720
were actually drowning in junk mail. And there's

02:02:45.720 --> 02:02:49.359
nothing you can do about it except change your

02:02:49.359 --> 02:02:54.079
email address and hope it doesn't become pilfered.

02:02:56.340 --> 02:03:03.779
Your inbox didn't become less secure. The attackers

02:03:03.779 --> 02:03:07.779
just made sending messages cheaper. So the takeaway

02:03:07.779 --> 02:03:12.420
here is simple. Don't assume the increase means

02:03:12.420 --> 02:03:19.600
you're being specifically targeted or hacked.

02:03:19.939 --> 02:03:26.979
Most of the time, you're just seeing industrial

02:03:26.979 --> 02:03:46.439
scale automation. spot them. You'll understand

02:03:46.439 --> 02:03:52.180
what to look for and when not to respond to them.

02:03:53.500 --> 02:03:57.600
We'll continue with more of the podcast. This

02:03:57.600 --> 02:04:15.960
is TSB Program 269. Alright, folks, I know that

02:04:15.960 --> 02:04:19.720
the second file wasn't my best work. I'm still

02:04:19.720 --> 02:04:24.060
recovering from computer issues, and so excuse

02:04:24.060 --> 02:04:31.079
the robotic me. Hey, maybe that wouldn't be so

02:04:31.079 --> 02:04:36.579
bad for an occasional segment. I didn't even

02:04:36.579 --> 02:04:40.039
do it on purpose. I don't exactly know what happened.

02:04:40.720 --> 02:04:42.899
But we're going to move forward with our items.

02:04:43.739 --> 02:04:49.840
And I do know now that this is working. So, sorry

02:04:49.840 --> 02:04:54.939
again for the trouble. We've got a few gremlins

02:04:54.939 --> 02:05:01.180
still in the machine. Should I have to go to

02:05:01.180 --> 02:05:03.340
the Geek Squad and tell them I'm having issues

02:05:03.340 --> 02:05:08.750
again? I mean, the computer is working. Maybe

02:05:08.750 --> 02:05:12.670
there's a scammer who wanted to get in there.

02:05:12.810 --> 02:05:17.970
Maybe that's what happened. But we're going to

02:05:17.970 --> 02:05:21.909
get rid of the scammers because our next segment

02:05:21.909 --> 02:05:32.449
is Same Scams, New Packaging. Our second segment

02:05:32.449 --> 02:05:39.859
in a two -part segment dealing with scams is

02:05:39.859 --> 02:05:47.739
asking three different questions. Three questions

02:05:47.739 --> 02:05:56.560
that kill almost every scam. After running mail

02:05:56.560 --> 02:06:01.000
systems, websites, and online communities for

02:06:01.000 --> 02:06:05.550
more than 20 years, I've learned something interesting.

02:06:06.529 --> 02:06:10.229
You don't actually need to understand email headers,

02:06:10.489 --> 02:06:16.529
IP addresses, or cybersecurity tools to avoid

02:06:16.529 --> 02:06:22.470
most scams. You just need to ask three simple

02:06:22.470 --> 02:06:27.210
questions. See, you're probably going to sit

02:06:27.210 --> 02:06:31.609
there and go, Okay, Jared, now that the gremlins

02:06:31.609 --> 02:06:35.649
are out of your computer, Hopefully for good

02:06:35.649 --> 02:06:41.310
this time. What might those three questions be?

02:06:43.810 --> 02:06:49.510
Well, question number one. Did I start this interaction?

02:06:50.710 --> 02:06:58.729
I .e. the re -emails. If you didn't apply for

02:06:58.729 --> 02:07:04.340
a job, didn't request support, didn't start a

02:07:04.340 --> 02:07:08.699
conversation, and didn't try to buy anything,

02:07:09.239 --> 02:07:14.239
then an email claiming you did is already suspicious.

02:07:15.380 --> 02:07:22.560
A huge number of skins begin by pretending there

02:07:22.560 --> 02:07:27.539
was an earlier conversation. You'll see messages

02:07:27.539 --> 02:07:33.579
that start with re colon, i .e. R -E, colon,

02:07:33.819 --> 02:07:40.359
or follow -up. Even though you've never talked

02:07:40.359 --> 02:07:44.880
to that person before. That's not an accident.

02:07:45.819 --> 02:07:51.899
They're trying to create familiarity. So you

02:07:51.899 --> 02:07:58.699
stop questioning it. Real business communication

02:07:58.699 --> 02:08:08.359
using This tactic is never going to happen. And

02:08:08.359 --> 02:08:15.140
that's me adding that statement. Okay? Real business

02:08:15.140 --> 02:08:20.060
communication usually begins with something you

02:08:20.060 --> 02:08:28.500
actually remember doing. Like calling Apple and

02:08:28.500 --> 02:08:33.289
asking for something. in regards to setting up

02:08:33.289 --> 02:08:36.989
your iCloud account. They're going to send you

02:08:36.989 --> 02:08:42.529
an email that says, iCloud account setup instructions

02:08:42.529 --> 02:08:51.270
with a support ticket, maybe. That would be more

02:08:51.270 --> 02:08:57.329
familiar to you than follow -up support ticket.

02:08:57.979 --> 02:09:01.039
And by the way, that follow -up might have a

02:09:01.039 --> 02:09:08.720
colon beside it. Question number two. Is there

02:09:08.720 --> 02:09:15.060
proof or just claims? Real technical messages,

02:09:15.159 --> 02:09:20.100
including those that could be sent by somebody

02:09:20.100 --> 02:09:26.220
that you may not know, may include technical

02:09:26.220 --> 02:09:32.100
proof. information and details, especially if

02:09:32.100 --> 02:09:37.119
they are reporting a bug on a website. So real

02:09:37.119 --> 02:09:40.960
technical messages include details. They tell

02:09:40.960 --> 02:09:46.180
you exactly what page has a problem, what invoice

02:09:46.180 --> 02:09:51.140
number is involved, or what account action occurred.

02:09:51.899 --> 02:09:57.260
Scams stay vague. They say things like, We found

02:09:57.260 --> 02:10:02.680
issues or important messages are waiting, but

02:10:02.680 --> 02:10:07.680
never show anything specific. If someone claims

02:10:07.680 --> 02:10:13.260
they analyzed your website, but can't name a

02:10:13.260 --> 02:10:23.239
single page, that's not an analysis. That's bait.

02:10:27.310 --> 02:10:33.869
So, what's question number three? Why the urgency?

02:10:34.470 --> 02:10:39.890
Almost every scam tries to rush you. You have

02:10:39.890 --> 02:10:48.770
24 hours. 72 hours. Act now. Final notice. Real

02:10:48.770 --> 02:10:55.289
organizations don't panic you into immediate

02:10:55.289 --> 02:11:00.500
action. Banks, hosting providers, and legitimate

02:11:00.500 --> 02:11:05.460
companies expect verification steps and give

02:11:05.460 --> 02:11:10.840
you time to confirm information safely. Urgency

02:11:10.840 --> 02:11:16.600
is not a technical requirement. It's a psychological

02:11:16.600 --> 02:11:21.720
trick. So when you combine those three questions,

02:11:22.119 --> 02:11:31.409
Did I start this? Is there real proof? And why

02:11:31.409 --> 02:11:37.390
the rush? Most scam emails collapse instantly.

02:11:37.770 --> 02:11:44.449
You don't need advanced security knowledge. You

02:11:44.449 --> 02:11:49.270
just need to slow down long enough to apply basic

02:11:49.270 --> 02:11:53.670
logic. And after years of looking at this stuff,

02:11:54.430 --> 02:11:59.510
That's really the biggest lesson. Scams succeed

02:11:59.510 --> 02:12:08.250
when people feel rushed or confused. They fail

02:12:08.250 --> 02:12:13.710
when people pause and think. Ask those three

02:12:13.710 --> 02:12:17.750
questions and most of the junk in your inbox

02:12:17.750 --> 02:12:26.520
becomes exactly what it is. Noise. So what do

02:12:26.520 --> 02:12:32.840
you think? Do you agree? Do you not agree? Email,

02:12:33.039 --> 02:12:37.539
iMessage, text, or WhatsApp, or even call. The

02:12:37.539 --> 02:19:40.590
comment lines await. On TSB. Of finding out what

02:19:40.590 --> 02:19:50.709
broke in our Braille. Yes, because something

02:19:50.709 --> 02:19:58.389
did. Number seven. That's that heavy check mark.

02:20:09.389 --> 02:20:11.450
and I'm just going to change number nine. I'm

02:20:11.450 --> 02:20:21.030
not going to rerun files. No, no. Number five

02:20:21.030 --> 02:20:24.790
is the same thing. Okay, so it's just a heavy

02:20:24.790 --> 02:20:30.290
checkmark, people. That's what to know. I thought

02:20:30.290 --> 02:20:38.920
I caught all of them. It happens. You can see

02:20:38.920 --> 02:20:41.180
how big a file it is. I mean, I was surprised

02:20:41.180 --> 02:20:46.760
it was that big. Three. I'm just going to remove

02:20:46.760 --> 02:20:58.500
these, so if you guys... Oh, number one doesn't

02:20:58.500 --> 02:21:01.200
have a space. Okay, let's fix that. Dang it.

02:21:01.219 --> 02:21:17.229
Yes, you're right. Okay. want a copy you can

02:21:17.229 --> 02:21:20.350
always tell us and if we send you one and you're

02:21:20.350 --> 02:21:25.170
like I want you to send me a better copy then

02:21:25.170 --> 02:21:27.950
we'll regenerate the braille. Okay? How's that?

02:21:29.750 --> 02:21:32.950
That works. We'll send you our braille but if

02:21:32.950 --> 02:21:38.229
you have trouble reading it you can request a

02:21:38.229 --> 02:21:43.899
new one. Okay. I tried to find all of these and

02:21:43.899 --> 02:21:53.540
take all of these out, but... I wonder what it

02:21:53.540 --> 02:21:58.360
would have done in UEB. Probably the same thing.

02:21:58.840 --> 02:22:03.100
Because these are like hexadecimal symbolization

02:22:03.100 --> 02:22:11.159
things, is what this is. And Braille 2000 tries

02:22:11.159 --> 02:22:15.819
to figure it out, but it doesn't. It's just a

02:22:15.819 --> 02:22:21.000
bad transcription note. Okay. Back to the top

02:22:21.000 --> 02:22:26.559
with me. PHI, personal health information, and

02:22:26.559 --> 02:22:35.520
why companies don't protect it. Exactly. Well,

02:22:35.600 --> 02:22:41.930
because all they want is our data. I want your

02:22:41.930 --> 02:22:47.370
data too, but there's got to be a fine line between

02:22:47.370 --> 02:22:59.350
what data you need to do your job and too much

02:22:59.350 --> 02:23:07.549
data. Agreed. I just want to make sure we're...

02:23:07.799 --> 02:23:11.959
recording it on. Instead of, you know, they also

02:23:11.959 --> 02:23:14.479
just want to line their pockets with the data

02:23:14.479 --> 02:23:17.659
brokers paying them for it. So, I mean, that's...

02:23:17.659 --> 02:23:23.959
And it was funny that you mentioned data brokers

02:23:23.959 --> 02:23:32.799
because Twit at one point was was advertising

02:23:32.799 --> 02:23:40.280
Melissa and Then when I signed up for Incogni

02:23:40.280 --> 02:23:47.159
and I was looking on a regular basis, Melissa

02:23:47.159 --> 02:23:54.819
had removed my information. Oh, wow. So they're

02:23:54.819 --> 02:24:03.459
a data broker. Yes, they are. I just found that

02:24:03.459 --> 02:24:10.469
funny. Because they're touting it as, oh, get

02:24:10.469 --> 02:24:13.709
your email addresses cleaned up. Because you

02:24:13.709 --> 02:24:17.590
can find a whole bunch of people. You'll upload

02:24:17.590 --> 02:24:22.290
your database and get new email addresses with

02:24:22.290 --> 02:24:29.870
little effort. I don't know if Twit's even advertising

02:24:29.870 --> 02:24:37.190
them anymore. Oh, my goodness. Here comes. The

02:24:37.190 --> 02:24:51.829
boy of pressed. Of pressed. Yes. Here comes the

02:24:51.829 --> 02:25:02.370
boy of pressed. Yes. Hello, Jared. I'm here.

02:25:03.170 --> 02:25:05.309
Sorry, I've been listening and I've been working

02:25:05.309 --> 02:25:08.309
at the same time and my glasses need to be freaking

02:25:08.309 --> 02:25:13.850
charged. I literally got two, I got a few moving

02:25:13.850 --> 02:25:18.229
totes with me because I will be, I'm going to

02:25:18.229 --> 02:25:20.129
be moving out on Friday, ladies and gentlemen.

02:25:22.469 --> 02:25:27.329
Oh boy. We'll be signing the lease. So well between

02:25:27.329 --> 02:25:31.399
this weekend. I'm still working on getting the

02:25:31.399 --> 02:25:34.139
Wi -Fi situation worked out. But yeah, if you

02:25:34.139 --> 02:25:38.200
hear me multitask today, that's why. So, Mr.

02:25:38.739 --> 02:25:42.680
G, before we actually get into the topic, what

02:25:42.680 --> 02:25:48.100
did you think of our stupid fuck for segment

02:25:48.100 --> 02:25:52.719
one of today's program? Yes, I was literally

02:25:52.719 --> 02:25:55.420
about to talk to you about that because I was

02:25:55.420 --> 02:26:00.739
sitting there working on... working on a note

02:26:00.739 --> 02:26:03.520
and also working on some community findings from

02:26:03.520 --> 02:26:06.020
one of our clients. And I thought I was going

02:26:06.020 --> 02:26:08.100
to throw up in my workstation. It was that bad.

02:26:13.040 --> 02:26:17.159
I'm sure you heard all of our reactions. I did.

02:26:17.620 --> 02:26:20.200
I have a volumes that I got good love on VLC

02:26:20.200 --> 02:26:24.159
and I just took it all in and I was sitting there

02:26:24.159 --> 02:26:26.639
and I feel myself. Yeah, why am I not surprised

02:26:26.639 --> 02:26:39.280
he would do that? That was stupid. Wow. Knowing

02:26:39.280 --> 02:26:42.799
that the pastor's wife was probably listening

02:26:42.799 --> 02:26:45.219
in and, you know, was listening in and stuff.

02:26:47.719 --> 02:26:55.120
Oh, yeah. And the daughter. You're in the daughter.

02:26:59.280 --> 02:27:11.280
Yeah, you know... That's pretty much how that

02:27:11.280 --> 02:27:16.899
goes, so... Yeah, I'm afraid I have no sympathy.

02:27:18.920 --> 02:27:22.940
Next time you do that, it's two months, boy.

02:27:25.069 --> 02:27:27.829
I wouldn't even give them a next time. I mean,

02:27:27.870 --> 02:27:32.590
jeez. I would have thrown... It's like, no, you're

02:27:32.590 --> 02:27:35.909
out. That's really inappropriate and uncalled

02:27:35.909 --> 02:27:39.709
for. You're out. Especially in a church. Yeah.

02:27:44.930 --> 02:27:50.690
That's what I said. That's what I said when they

02:27:50.690 --> 02:27:53.979
brought it up to... As part of the discussion,

02:27:54.139 --> 02:28:00.219
I said I would have thrown his happy ass out.

02:28:00.979 --> 02:28:07.059
Out. I would have said, you get your food this

02:28:07.059 --> 02:28:15.379
time, but once you leave... You may not reenter

02:28:15.379 --> 02:28:21.899
the pregnancy. Once you leave, you can't come

02:28:21.899 --> 02:28:36.409
back. Can't come back, yeah. Once you leave,

02:28:36.469 --> 02:28:53.829
that's the end of your happy ass. Wow. Chinit

02:28:53.829 --> 02:28:57.489
ate this yesterday, but I wanted to try my chicken

02:28:57.489 --> 02:29:08.010
rice bowl. So, Mr. J, do you want to start our

02:29:08.010 --> 02:29:14.229
reading on the top of page 269 .1? I would be

02:29:14.229 --> 02:29:20.209
happy to. Please go ahead. This week, yes. First

02:29:20.209 --> 02:29:25.149
paragraph. This week on the podcast, our topic

02:29:25.149 --> 02:29:30.489
is PHI. Specifically, we will be discussing how

02:29:30.489 --> 02:29:33.870
various players in the healthcare industry have

02:29:33.870 --> 02:29:37.190
unfortunately failed to protect it in spite of

02:29:37.190 --> 02:29:41.350
their promises. This is especially disappointing

02:29:41.350 --> 02:29:47.729
given that PHI cannot be changed. We will also

02:29:47.729 --> 02:29:50.790
be discussing best practices that companies and

02:29:50.790 --> 02:29:55.030
individuals should follow to keep PHI as secure

02:29:55.030 --> 02:30:10.049
as possible. So, before we actually read, the

02:30:10.049 --> 02:30:15.049
question is, what is PHI? Before we actually

02:30:15.049 --> 02:30:21.889
read, What is it and what do you think it includes?

02:30:24.389 --> 02:30:28.229
Well, I'm actually going to take a stab at this

02:30:28.229 --> 02:30:34.909
because my last job I had remotely, I hadn't

02:30:34.909 --> 02:30:41.030
done a lot of PA, PHI, you know, in the retail

02:30:41.030 --> 02:30:48.420
pharmaceutical space. So PHI would be personal

02:30:48.420 --> 02:30:57.819
health information and that includes the patient's

02:30:57.819 --> 02:31:03.139
name, diagnosis, medications that they might

02:31:03.139 --> 02:31:12.299
be on, how long they've had the diagnosis. Oh,

02:31:12.319 --> 02:31:14.879
wait. So much for the HIPAA form that you have

02:31:14.879 --> 02:31:20.819
to sign once in a while. You know? Oh, I know.

02:31:21.479 --> 02:31:25.139
The HIPAA form that promises that they're not

02:31:25.139 --> 02:31:32.639
going to do that? Exactly. That form. That exact

02:31:32.639 --> 02:31:35.299
form that I'm talking about. Yep, so much for

02:31:35.299 --> 02:31:43.540
that. Yeah, so much. Although most, I mean, I

02:31:43.540 --> 02:31:47.100
haven't had a problem at my doctor's office yet.

02:31:47.620 --> 02:31:53.079
No, me neither. Me neither, really. No, I really

02:31:53.079 --> 02:31:59.000
haven't. And notice I said yet. I've been in

02:31:59.000 --> 02:32:02.719
other breaches, but never with the doctor's offices

02:32:02.719 --> 02:32:06.940
or anything. Well, I think the OPM breach was

02:32:06.940 --> 02:32:09.479
the end for me because I have nothing yet left.

02:32:13.000 --> 02:32:16.360
And if that thing comes out with the SSA that

02:32:16.360 --> 02:32:19.399
I posted this morning, that'll definitely be

02:32:19.399 --> 02:32:23.379
it. There won't be any discussion left. Nope.

02:32:28.799 --> 02:32:32.959
I mean, at that point, we should just do one

02:32:32.959 --> 02:32:36.799
sign -off episode. Guys, you're all screwed.

02:32:37.440 --> 02:32:39.739
This has been the Security Box. The Security

02:32:39.739 --> 02:32:43.059
Box. And we're signing off now. And then play...

02:32:43.059 --> 02:32:48.700
You know, on the Wheel of Fortune thing, you

02:32:48.700 --> 02:32:53.479
know how when you get the bankrupt sound? Let

02:32:53.479 --> 02:32:57.500
me just log out. That's it. Let me just log out

02:32:57.500 --> 02:33:04.409
right after that. Or you just play... And then

02:33:04.409 --> 02:33:10.670
it just signs out after that. Yep. And then you

02:33:10.670 --> 02:33:13.950
just hear dead air for like five minutes, and

02:33:13.950 --> 02:33:18.389
then it transitions to a song. Yep. And then

02:33:18.389 --> 02:33:21.909
the security hour, you know, that would be probably

02:33:21.909 --> 02:33:23.690
the end of that hour, too. That's right, you

02:33:23.690 --> 02:33:26.870
know? Yep. It'll be the end of all tech -related

02:33:26.870 --> 02:33:29.729
stuff. All tech -related. Because there's nothing

02:33:29.729 --> 02:33:32.069
to say anymore. We're all screwed at that point.

02:33:33.739 --> 02:33:40.780
The majority of this community, anyway. 500 million

02:33:40.780 --> 02:33:42.639
people, Jared? That's pretty much everybody.

02:33:42.780 --> 02:33:46.420
That's not just this community. A lot of people,

02:33:46.500 --> 02:33:53.120
yeah. Well, Nick, you do have a point. Yeah,

02:33:53.200 --> 02:33:55.180
this is not just this community that's going

02:33:55.180 --> 02:33:57.159
to be affected if that is actually true. That's

02:33:57.159 --> 02:33:59.840
probably like half the U .S., probably. More

02:33:59.840 --> 02:34:04.049
than that. No, that's... probably the entire...

02:34:04.049 --> 02:34:13.469
Terry, Terry, here, Terry. I'm going to ask Chet.

02:34:14.270 --> 02:34:23.110
Terry, hold on a minute, Terry. Terry, you need...

02:34:23.110 --> 02:34:25.770
What is the number of people that live in the

02:34:25.770 --> 02:34:34.309
U .S.? As of July 1st, 2025, the estimated population

02:34:34.309 --> 02:34:38.149
of the United States is about 341 .8 million

02:34:38.149 --> 02:34:40.649
people. So it's more than just the U .S. Every

02:34:40.649 --> 02:34:43.110
single person in the U .S. It's probably U .S.

02:34:43.110 --> 02:34:52.049
and probably Canada. Here, Terry. So, yeah. There,

02:34:54.850 --> 02:34:58.389
Terry. Once you read that article, that accompanying

02:34:58.389 --> 02:35:02.879
article, From that blog post, then we'll talk.

02:35:03.760 --> 02:35:07.659
That's a half a bill, a half a bill. A half a

02:35:07.659 --> 02:35:09.879
bill, bill, bill, bill, bill, bill, bill, bill,

02:35:09.879 --> 02:35:11.020
bill, bill, bill, bill, bill, bill, bill, bill,

02:35:11.020 --> 02:35:14.540
bill. And I just got a German job, red flag,

02:35:14.620 --> 02:35:17.700
email my spam or Gmail. Yeah, so we're talking,

02:35:17.899 --> 02:35:20.959
forget just talking about, you know, forget just

02:35:20.959 --> 02:35:24.760
this community. We're talking the entire country.

02:35:26.959 --> 02:35:31.639
Yeah. Stinks. Yeah. And then some. That's it.

02:35:32.600 --> 02:35:35.719
Well, some of those may be duplicated, and some

02:35:35.719 --> 02:35:41.319
of those may be people who are dead, so... Most

02:35:41.319 --> 02:35:54.200
likely. Um... Mr. Ye, would you like to read?

02:35:54.870 --> 02:35:58.809
Our next accompanying heading, what is PHI? I,

02:35:58.829 --> 02:36:02.909
I, I, I, I, I, I. Okay. Yes, I'd be happy to.

02:36:04.250 --> 02:36:08.909
What is PHI? And Preston already gave a pretty

02:36:08.909 --> 02:36:13.309
good definition of it, but this is what we are

02:36:13.309 --> 02:36:22.329
told thanks to the GPT of chat. Of chat. Protected

02:36:22.329 --> 02:36:27.600
health information. PHI includes any information

02:36:27.600 --> 02:36:31.360
that can identify an individual and relates to

02:36:31.360 --> 02:36:34.700
their physical or mental health, medical conditions,

02:36:35.100 --> 02:36:39.280
treatments, or payment for health care. This

02:36:39.280 --> 02:36:43.260
can include names, diagnoses, medical histories,

02:36:43.659 --> 02:36:48.120
test results, or even indirect identifiers shared

02:36:48.120 --> 02:36:54.760
in context. It is clear that this is extremely

02:36:54.760 --> 02:36:59.459
sensitive information. App developers, corporate

02:36:59.459 --> 02:37:03.079
websites and staff at medical facilities will

02:37:03.079 --> 02:37:06.000
assure us time and time again that our information

02:37:06.000 --> 02:37:10.299
is stored securely, encrypted or that our data

02:37:10.299 --> 02:37:15.879
is entirely anonymized. Unfortunately, as we

02:37:15.879 --> 02:37:18.780
have seen in too many breaches of health insurers,

02:37:19.079 --> 02:37:23.079
hospitals and others in health care. the reality

02:37:23.079 --> 02:37:27.719
is far more sobering. Despite their assurances,

02:37:28.000 --> 02:37:31.600
this data is appearing in breaches with an all

02:37:31.600 --> 02:37:35.899
too alarming frequency. Given how valuable it

02:37:35.899 --> 02:37:39.120
is to cyber criminals, I predict that we will

02:37:39.120 --> 02:37:43.440
see many more of them. And I want to just pause

02:37:43.440 --> 02:37:49.450
here because this relates to... The article that

02:37:49.450 --> 02:37:53.329
you posted about the mental health apps downloaded

02:37:53.329 --> 02:38:01.709
by, I think, about 14 .7 million people. So there

02:38:01.709 --> 02:38:04.270
was, yes, there was a researcher in that who

02:38:04.270 --> 02:38:08.149
actually gave just sort of a guesstimate and

02:38:08.149 --> 02:38:10.969
a figure about how valuable some of that actually

02:38:10.969 --> 02:38:15.370
is. And we're looking at $1 ,000 for some of

02:38:15.370 --> 02:38:18.940
this info. Yes. what it's selling for, for cyber

02:38:18.940 --> 02:38:23.200
criminals. Now, I want to take this a step further

02:38:23.200 --> 02:38:30.819
before we move along to talk about our next heading.

02:38:32.760 --> 02:38:36.819
If you are, and I think we did this on throwback,

02:38:37.059 --> 02:38:45.340
if you were an app developer and you wanted to

02:38:45.340 --> 02:38:54.370
program an app, Like the ones that were recently

02:38:54.370 --> 02:38:57.350
touted in that one article, or even your own

02:38:57.350 --> 02:39:07.090
health care app. How would you develop it, knowing

02:39:07.090 --> 02:39:19.049
that you have access to all this data? Because

02:39:19.049 --> 02:39:22.190
I had this long discussion with chat, and mainly

02:39:22.190 --> 02:39:25.729
because I understand programming, but I want

02:39:25.729 --> 02:39:29.489
to ask this for those who do not know or understand

02:39:29.489 --> 02:39:33.829
programming. How would you, if you were a programmer,

02:39:34.129 --> 02:39:42.469
how would you develop this to minimize its...

02:39:42.469 --> 02:39:46.969
What we're about to talk about. Its footprint...

02:39:52.600 --> 02:40:01.520
leaking or not this data. We'll start with the

02:40:01.520 --> 02:40:10.459
cooking man. Well, I think for me, I would make

02:40:10.459 --> 02:40:16.659
sure all boxes are labeled. I would make sure

02:40:16.659 --> 02:40:20.959
all consent forms are labeled. accessible in

02:40:20.959 --> 02:40:26.059
a format where we can understand because knowing

02:40:26.059 --> 02:40:29.719
that they may have to fill out you know certain

02:40:29.719 --> 02:40:35.700
forms to begin the process I would make sure

02:40:35.700 --> 02:40:41.000
that the screening process for signing up is

02:40:41.000 --> 02:40:55.440
utilized Okay. Transparency. In other words,

02:40:55.500 --> 02:40:57.200
it's what it sounds like. That sounds good. That

02:40:57.200 --> 02:40:59.340
sounds like transparency. Making sure things

02:40:59.340 --> 02:41:02.319
are accessible. Knowing what you are signing

02:41:02.319 --> 02:41:09.040
up for. Okay. Making sure forms are accessible

02:41:09.040 --> 02:41:15.719
if you need to fill one out. Okay. Yep. And also

02:41:15.719 --> 02:41:21.360
making sure they have a direct line of contact,

02:41:21.719 --> 02:41:25.340
you know, if said person may need assistance

02:41:25.340 --> 02:41:31.020
on filling out said form or getting in touch.

02:41:31.219 --> 02:41:36.059
And again, that, you know... Well, I like your

02:41:36.059 --> 02:41:42.500
thinking, except that isn't really what is recommended.

02:41:44.239 --> 02:41:54.520
Uh -oh. Hmm. Well, there is one, and we talked

02:41:54.520 --> 02:41:56.579
about it on throwback, but it's really stuck

02:41:56.579 --> 02:42:00.959
with me. But one of you may come up with it first.

02:42:02.920 --> 02:42:07.020
Well, I already gave it all of my answers, so

02:42:07.020 --> 02:42:10.659
I can't really talk about it. So I have to give

02:42:10.659 --> 02:42:17.139
this to all of you. Okay. And then I'll talk

02:42:17.139 --> 02:42:22.299
about what I would do. So I think the biggest

02:42:22.299 --> 02:42:25.020
one to me, and this is what's really resonated

02:42:25.020 --> 02:42:28.819
and stuck out from throwback. I don't know if

02:42:28.819 --> 02:42:31.700
I'm saying this correctly, but local storage

02:42:31.700 --> 02:42:36.319
architecture. Correct. You have, yes. So you

02:42:36.319 --> 02:42:41.180
have the app and develop it so that all this

02:42:41.180 --> 02:42:50.309
data is stored locally on your device. Period.

02:42:50.370 --> 02:42:55.670
End of story. End of discussion, yes. Whatever

02:42:55.670 --> 02:43:02.950
you type, whatever's wrong, it does not leave

02:43:02.950 --> 02:43:15.090
your device. Period. The moment it does that,

02:43:18.190 --> 02:43:27.090
That's a problem. That's it. Yeah. And I haven't

02:43:27.090 --> 02:43:30.170
done any local coding, but I see why it's an

02:43:30.170 --> 02:43:36.590
important factor. I mean, these poor people in

02:43:36.590 --> 02:43:45.610
this mental health apps, they've done nothing

02:43:45.610 --> 02:43:50.350
wrong. They're doing whatever their doctor wants

02:43:50.350 --> 02:43:55.090
them to do. And they're using the apps as intended.

02:43:55.569 --> 02:44:10.870
Correct. Yep. Yep. Now, if... If... I were to

02:44:10.870 --> 02:44:16.489
build it so you could share with your doctor...

02:44:18.829 --> 02:44:23.069
This information. There would be a dialogue.

02:44:27.969 --> 02:44:37.010
Once you share this. We have no way. To protect

02:44:37.010 --> 02:44:41.750
you. And that's where transparency comes in.

02:44:41.750 --> 02:44:45.610
That Preston was talking about. Correct. We have

02:44:45.610 --> 02:44:49.600
no way to protect you. From this getting loose,

02:44:49.719 --> 02:45:05.020
are you sure you would like to do this? There

02:45:05.020 --> 02:45:18.409
would be no links. There would be no way. for

02:45:18.409 --> 02:45:25.510
you to have an account on my server, there would

02:45:25.510 --> 02:45:39.809
be no sharing to social media. There would be

02:45:39.809 --> 02:45:54.700
no ability to export. And if I did, I would give

02:45:54.700 --> 02:45:57.420
you the same dialogue by exporting this data.

02:45:59.719 --> 02:46:07.940
I am not held responsible if it gets loose. And

02:46:07.940 --> 02:46:10.219
there should be no checkbox to say yes or no.

02:46:10.280 --> 02:46:12.440
You should actually have to type the word yes

02:46:12.440 --> 02:46:18.569
or no. Because I could just turn around and be

02:46:18.569 --> 02:46:20.409
like, oh, I'm going to JaredRiver .net. Okay,

02:46:20.450 --> 02:46:23.690
cool. I'll just check this box. Hey, the box

02:46:23.690 --> 02:46:26.469
is checked. All right, here you go. And that's

02:46:26.469 --> 02:46:34.209
where you would say, type in your response, yes

02:46:34.209 --> 02:46:36.950
or no. If no, then you won't be able to use this.

02:46:37.870 --> 02:46:43.049
But just remember that if yes, then you're putting

02:46:43.049 --> 02:46:46.870
yourself at risk. And then I would get a notice

02:46:46.870 --> 02:46:52.690
that stipulates, I would then get a note that

02:46:52.690 --> 02:46:59.389
stipulates that your device indicated that you

02:46:59.389 --> 02:47:06.069
understood the risks. Yep. Yes. And then I technically

02:47:06.069 --> 02:47:11.389
have to hold on to that. Right. And then if I'm

02:47:11.389 --> 02:47:19.469
sued. I would provide the notice that stipulates

02:47:19.469 --> 02:47:24.329
that the person understood that. I wouldn't have

02:47:24.329 --> 02:47:27.690
any details of who you are, what you're using

02:47:27.690 --> 02:47:33.469
the app for, but you would have an ID, just like

02:47:33.469 --> 02:47:37.989
any other app. Yeah, but you would totally, yeah,

02:47:38.010 --> 02:47:39.930
like I said, you could just turn around and say,

02:47:40.049 --> 02:47:44.959
look, I have a... legal, well not, you know,

02:47:44.959 --> 02:47:47.379
technically a binding document. This is what

02:47:47.379 --> 02:47:51.620
this person signed slash said they understood.

02:47:51.920 --> 02:47:57.100
They made this choice. I cannot be held responsible.

02:47:57.260 --> 02:48:04.299
I don't have the data. Right. Yep. If they shared

02:48:04.299 --> 02:48:06.700
it with their doctor, that means it's on their

02:48:06.700 --> 02:48:11.319
clipboard and they put it in their own doctor

02:48:11.319 --> 02:48:16.629
app. I would not be putting links on my server

02:48:16.629 --> 02:48:22.670
where anybody could access it. Right. Right.

02:48:22.850 --> 02:48:29.250
No. That is pretty much un -security -like, and

02:48:29.250 --> 02:48:42.090
it's too... I would also... Yeah. I would also

02:48:42.090 --> 02:48:47.430
make sure that this app is locked with a fingerprint

02:48:47.430 --> 02:48:53.049
or face ID or touch ID. Face ID or touch ID.

02:48:54.389 --> 02:48:59.209
I would have it set up so it would automatically

02:48:59.209 --> 02:49:02.049
prompt you like, hey, you have to use this. You

02:49:02.049 --> 02:49:05.250
have no choice. You don't have a choice. Even

02:49:05.250 --> 02:49:13.569
for local. That's what I would do. Face ID or

02:49:13.569 --> 02:49:17.389
touch ID, it has to be turned on. You're dealing

02:49:17.389 --> 02:49:21.450
with sensitive stuff. If you're writing personal

02:49:21.450 --> 02:49:24.229
stuff down about whatever's going on with you,

02:49:24.270 --> 02:49:31.170
whatever it may be, that's your business. You

02:49:31.170 --> 02:49:41.800
lock it behind your biometric. That is... Your

02:49:41.800 --> 02:49:46.819
problem. Instead of using a password, you would

02:49:46.819 --> 02:49:49.420
just use the biometric, which, yeah, makes sense.

02:49:49.520 --> 02:49:53.260
There would be no password. Yeah, I mean, if

02:49:53.260 --> 02:49:55.139
it's just for an app, yeah, but I mean, if you're

02:49:55.139 --> 02:49:58.420
having a website, too, you could technically...

02:49:58.420 --> 02:50:01.940
There is no website. What website, Terry? Yeah,

02:50:01.979 --> 02:50:04.540
yeah. The whole goal... Because some of these

02:50:04.540 --> 02:50:09.950
apps do have... web interfaces too. There would

02:50:09.950 --> 02:50:13.170
be no web interface. Yeah, you would create it

02:50:13.170 --> 02:50:18.489
with just an app. And if there was a web interface

02:50:18.489 --> 02:50:25.450
and you chose to use it by agreeing to share

02:50:25.450 --> 02:50:30.569
this with the website and me allowing you to

02:50:30.569 --> 02:50:34.270
create an account, it must be a strong password.

02:50:35.280 --> 02:50:43.659
That is used nowhere else. Right. And I would

02:50:43.659 --> 02:50:49.180
make sure that it's 16 to 20 characters, if not

02:50:49.180 --> 02:50:55.520
longer. A minimum of 16 these days. 16, yeah.

02:50:58.639 --> 02:51:04.270
Actually... a minimum of 12 these days. I'll

02:51:04.270 --> 02:51:17.829
make it easy. But, there would be limits. They'll

02:51:17.829 --> 02:51:21.309
duplicate letters. Yeah, I mean, there have been

02:51:21.309 --> 02:51:24.530
limits even on what you can upload to that part

02:51:24.530 --> 02:51:27.569
of the site, too, because you don't want, you

02:51:27.569 --> 02:51:45.420
know... By you agreeing to use the web interface,

02:51:45.760 --> 02:51:50.780
I'm not held responsible. That's what the legal

02:51:50.780 --> 02:51:54.940
agreement would show. So if you go ahead and

02:51:54.940 --> 02:52:01.000
upload your personal life, that's your doing.

02:52:01.920 --> 02:52:05.059
And if my server... I would do everything I could.

02:52:05.739 --> 02:52:09.139
to make sure my server was protected. But if

02:52:09.139 --> 02:52:12.420
there was a mistake, I'm not held responsible.

02:52:13.319 --> 02:52:23.059
And I don't know who you are. Right. I would

02:52:23.059 --> 02:52:26.479
make sure that the interface doesn't email me

02:52:26.479 --> 02:52:31.840
with any web details of anybody who uses it.

02:52:32.940 --> 02:52:35.979
All it would signify was that this device ID

02:52:35.979 --> 02:52:43.540
signified they understood the web access point

02:52:43.540 --> 02:52:52.440
of my app. That's it. Yeah. Yep. Yep. But, I

02:52:52.440 --> 02:52:54.420
mean, nowadays, I mean, you could get away with

02:52:54.420 --> 02:53:01.129
just using it mobilely. I mean, that's... But

02:53:01.129 --> 02:53:03.309
that's what I would do if I had a web component.

02:53:04.649 --> 02:53:15.329
Yeah. Yeah, pretty much. And what I would do

02:53:15.329 --> 02:53:17.790
also if I had a web component is I would say,

02:53:17.829 --> 02:53:22.110
okay, so the mobile side, you sign this privacy

02:53:22.110 --> 02:53:25.129
agreement. You're also going to sign it here,

02:53:25.270 --> 02:53:30.790
too. I would just because, right? You know, As

02:53:30.790 --> 02:53:33.270
soon as you sign into the web version on your

02:53:33.270 --> 02:53:38.690
PC, you would be presented with the same thing.

02:53:38.729 --> 02:53:41.709
And we would get a note stating the same thing.

02:53:41.889 --> 02:53:45.729
This browser on this operating system signed

02:53:45.729 --> 02:53:53.530
it. Yep. That's what I would do. Right. This

02:53:53.530 --> 02:54:00.440
Firefox on Windows. I don't know. Linux. Lindos.

02:54:01.340 --> 02:54:12.379
Lindos. Although, it'd probably be more specific

02:54:12.379 --> 02:54:15.700
because there's so many different flavors of

02:54:15.700 --> 02:54:19.899
Linux, so you'd probably get more... Yeah, it'd

02:54:19.899 --> 02:54:22.559
be like... Well, but we would make sure that

02:54:22.559 --> 02:54:32.899
the note we get captures everything. Right. Yeah.

02:54:32.899 --> 02:54:36.299
We wouldn't be collecting the username, the password,

02:54:36.500 --> 02:54:40.420
all of that. The note would just stipulate that

02:54:40.420 --> 02:54:46.239
the agreement was signed. Right. It doesn't even

02:54:46.239 --> 02:54:49.079
have to mention who it is. Because I don't want

02:54:49.079 --> 02:54:52.299
to have your data. The whole point of creating

02:54:52.299 --> 02:54:57.159
the app is for you to use the app. Not for me

02:54:57.159 --> 02:54:59.600
to know who you are. If I need to know who you

02:54:59.600 --> 02:55:04.120
are, then I got a problem. Uh -huh. Yeah, indeed.

02:55:06.840 --> 02:55:10.559
Especially if we get on the number's bad side.

02:55:11.139 --> 02:55:15.000
That's going to be bad. You wouldn't be getting

02:55:15.000 --> 02:55:17.299
on my bad side because I wouldn't know who you

02:55:17.299 --> 02:55:22.559
were. Right. Right. But even if I knew who you

02:55:22.559 --> 02:55:26.379
were... How would you be getting on my bad side?

02:55:26.479 --> 02:55:28.920
I'm not going in and reading all of your data.

02:55:29.899 --> 02:55:34.420
No. Because the way you've designed the app,

02:55:34.579 --> 02:55:42.700
you can't. You can't, yeah. Yep. Fully encrypted.

02:55:44.680 --> 02:55:54.530
Yep. Local storage. If web -based SS L -T -L

02:55:54.530 --> 02:56:08.389
-S. Ah, yes. Oh, boy. Yep. Oh, boy. Good job,

02:56:08.450 --> 02:56:12.129
guys. I like your line of thinking. All right.

02:56:12.149 --> 02:56:19.430
Awesome. Yeah, thanks. That wasn't so bad. I

02:56:19.430 --> 02:56:27.180
will take over. Go ahead. Hospitals. Let's begin

02:56:27.180 --> 02:56:32.559
our discussion with hospitals. The very institutions

02:56:32.559 --> 02:56:37.319
that many would assume would make storing health

02:56:37.319 --> 02:56:44.139
information securely a top priority. Priority.

02:56:45.559 --> 02:56:52.469
That's the point. That's the point. Sure, they

02:56:52.469 --> 02:56:54.389
don't even fucking upgrade their damn systems,

02:56:54.409 --> 02:56:56.950
let alone... We're getting to that, Terry. They

02:56:56.950 --> 02:57:01.729
can't, Terry. They can't. I know, but I'm saying

02:57:01.729 --> 02:57:07.389
it's just... That's their problems. But they

02:57:07.389 --> 02:57:11.250
can't. And we're getting to that, too. That's

02:57:11.250 --> 02:57:13.229
going to come up later as well, so that's perfect.

02:57:14.850 --> 02:57:22.190
Sadly... The reality is that hospitals engage

02:57:22.190 --> 02:57:26.129
in many questionable cybersecurity practices,

02:57:26.229 --> 02:57:32.909
which makes our PHI more vulnerable to exposure.

02:57:35.229 --> 02:57:42.170
Exactly. Some of the most serious are listed

02:57:42.170 --> 02:57:50.600
below. I think I forgot to take a space out.

02:57:50.719 --> 02:57:56.559
Oops. Okay, so the first item in this first list

02:57:56.559 --> 02:58:05.500
is using outdated technology and legacy systems.

02:58:06.100 --> 02:58:10.219
Okay, before we continue, given what we know,

02:58:10.440 --> 02:58:14.540
I mean, it's totally unacceptable, but you can't

02:58:14.540 --> 02:58:17.420
entirely blame them. But anyway, go ahead. I

02:58:17.420 --> 02:58:29.059
agree. Many hospitals... 10 -9 pressed? Yeah,

02:58:29.079 --> 02:58:35.180
you're good. Okay. Many hospitals still run aging

02:58:35.180 --> 02:58:39.600
infrastructure with... Oh, that was a paragraph.

02:58:39.760 --> 02:58:44.899
I see what happened. Okay. With... And we've

02:58:44.899 --> 02:58:49.879
got bulleted items here. Yep. Okay. I did do

02:58:49.879 --> 02:58:57.120
this correctly. Okay, so before I do this, there

02:58:57.120 --> 02:59:10.260
are four items. Mr. J cannot answer. No. Can

02:59:10.260 --> 02:59:18.229
anybody tell us what they might be. Let's do

02:59:18.229 --> 02:59:24.190
it that way. Great idea. Well, outdated software

02:59:24.190 --> 02:59:38.469
for one. What is this? Unsupported software is

02:59:38.469 --> 02:59:41.309
that particular item. Yeah, that's pretty much

02:59:41.309 --> 02:59:43.090
the same thing. We'll give you that. Perfect.

02:59:43.129 --> 02:59:58.440
We'll give you that, Terry. Go ahead. Who's next?

02:59:58.520 --> 03:00:24.420
And I'm also thinking there is Unpatched operating

03:00:24.420 --> 03:00:28.760
systems. That's the very first one. That is the

03:00:28.760 --> 03:00:32.920
very first item. That is the very first one.

03:00:33.120 --> 03:00:40.059
There are two more. So we have unpatched operating

03:00:40.059 --> 03:00:44.620
systems and unsupported or outdated software.

03:00:44.959 --> 03:00:48.620
I'll give you outdated. That's close enough.

03:00:49.299 --> 03:00:54.100
Yeah. Yeah. There are two more in this list.

03:00:54.500 --> 03:01:02.440
Another factor would be the bad part, too. Weak

03:01:02.440 --> 03:01:08.680
authentication practices. Oh, my gosh. Now we've

03:01:08.680 --> 03:01:14.860
got a third. That is the last item. Weak authentication

03:01:14.860 --> 03:01:21.899
systems, which goes into item number three, be

03:01:21.899 --> 03:01:26.879
dealing with? What did we just talk about just

03:01:26.879 --> 03:01:29.120
recently when I asked you how to build the app?

03:01:30.399 --> 03:01:35.260
Slash web portal. Or encryption. Or encryption.

03:01:36.139 --> 03:01:42.020
Or encryption practices. Is correct. Exactly

03:01:42.020 --> 03:01:47.739
right. The bulleted items are unpatched operating

03:01:47.739 --> 03:01:54.559
systems. Unsupported software. Poor encryption

03:01:54.559 --> 03:02:02.799
practices. Weak authentication systems. Adding

03:02:02.799 --> 03:02:10.459
to these practices is human error. While we make

03:02:10.459 --> 03:02:17.159
mistakes from time to time, oversights like the

03:02:17.159 --> 03:02:22.590
ones below can have disastrous consequences in

03:02:22.590 --> 03:02:29.270
this field. Stop me if you've heard any of the

03:02:29.270 --> 03:02:34.909
following before. Now, we have one, two, three,

03:02:35.110 --> 03:02:41.969
four. Four of them. And I will say, some of these

03:02:41.969 --> 03:02:46.930
are not necessarily cybersecurity, but most of

03:02:46.930 --> 03:02:53.600
them are. There is one that could be considered

03:02:53.600 --> 03:03:04.680
a mistake that could have consequences. Yeah,

03:03:04.719 --> 03:03:08.440
like your billing and insurance information somehow

03:03:08.440 --> 03:03:14.600
getting leaked. Credit card. Payment information.

03:03:16.040 --> 03:03:22.760
That... Actually, I do kind of want to give you

03:03:22.760 --> 03:03:31.280
that because it goes into one of them listed

03:03:31.280 --> 03:03:33.719
here, which is not part of the bulleted list,

03:03:33.799 --> 03:03:38.440
but it is definitely one that's important. Insider

03:03:38.440 --> 03:03:42.440
threats. Yes, that would be. Yeah, that would

03:03:42.440 --> 03:03:45.379
be. Sounds like what you're talking about there,

03:03:45.440 --> 03:03:50.309
Terry. Yeah, it is. Yeah. So yeah, that's not

03:03:50.309 --> 03:03:52.549
in the bulleted list, but it is mentioned. I

03:03:52.549 --> 03:04:09.110
did put it in. So yes, that qualifies. And what

03:04:09.110 --> 03:04:14.729
did I do here? Looks like I... Alright, well,

03:04:14.809 --> 03:04:16.329
I'm not going to worry about it. Alright, who's

03:04:16.329 --> 03:04:23.090
next? And I can't answer, so... I can't answer

03:04:23.090 --> 03:04:25.809
either because I'm looking at the items. But

03:04:25.809 --> 03:04:28.190
I just noticed that something happened with one

03:04:28.190 --> 03:04:31.549
of the paragraphs. But I don't exactly know what

03:04:31.549 --> 03:04:39.569
happened there. But that's okay. I think there

03:04:39.569 --> 03:04:45.209
might be a space there. Which made it 4 -1 instead

03:04:45.209 --> 03:04:48.510
of 3 -1, but that's okay. Go ahead, gentlemen.

03:04:49.469 --> 03:04:53.250
Insider threats is one. Yeah. Without giving

03:04:53.250 --> 03:04:58.350
away an answer, we literally, as in less than

03:04:58.350 --> 03:05:01.569
five minutes ago, were talking about one of the

03:05:01.569 --> 03:05:06.389
things that you would basically make mandatory

03:05:06.389 --> 03:05:12.049
on your site if you were developing an app for

03:05:12.049 --> 03:05:23.110
the web -based. Mm -hmm. Yeah, signing the privacy

03:05:23.110 --> 03:05:27.010
policies and stuff, or your HIPAA form. Well,

03:05:27.010 --> 03:05:31.270
that's... Yes, that's important, but there's...

03:05:31.270 --> 03:05:37.049
Really, what we're looking for here... Right,

03:05:37.209 --> 03:05:48.799
so... But good try, Tim. You almost have. Okay,

03:05:48.899 --> 03:05:53.079
let me... So, we've talked about one of these

03:05:53.079 --> 03:05:57.340
items. Okay, so number one in this is something

03:05:57.340 --> 03:06:07.440
we've talked about quite regularly. Oh, all the

03:06:07.440 --> 03:06:16.819
time. Quite regularly. Yeah. Open databases.

03:06:19.700 --> 03:06:27.180
Not exactly open databases here. But I think

03:06:27.180 --> 03:06:31.020
you may be starting to nibble at it somewhat.

03:06:31.020 --> 03:06:35.540
You're nibbling at it. You're crunching on the

03:06:35.540 --> 03:06:39.459
idea. You're crunching on the idea because open

03:06:39.459 --> 03:06:47.170
databases can be a result of what? A breach of

03:06:47.170 --> 03:06:52.250
the system. Nope. A breach of the system. A breach

03:06:52.250 --> 03:07:01.090
of the system is caused by what? It starts with

03:07:01.090 --> 03:07:28.469
an M. Now what? Nope. I mean, that... Nope. Terry

03:07:28.469 --> 03:07:32.049
was closer when he mentioned open databases,

03:07:32.129 --> 03:07:34.290
even though that's not entirely what we're looking

03:07:34.290 --> 03:08:04.510
for. Yeah. Open databases are part of what? So

03:08:04.510 --> 03:08:08.809
when you design a website slash an app, you have

03:08:08.809 --> 03:08:20.350
to do what with certain settings? Good job, Nick.

03:08:21.290 --> 03:08:33.329
Thanks. Migrate? Not if it's new. No, if you've

03:08:33.329 --> 03:08:35.930
just built it, you wouldn't need to be doing

03:08:35.930 --> 03:08:41.489
that yet. I mean, that would come later. You

03:08:41.489 --> 03:08:45.610
would migrate if you had to move servers, but

03:08:45.610 --> 03:08:58.770
we're not talking about that. Yeah, okay. Um...

03:08:58.770 --> 03:09:33.719
Maybe, uh... failing me. The word I'm thinking

03:09:33.719 --> 03:09:38.100
of... No, I wasn't going to give it away. It

03:09:38.100 --> 03:09:41.639
starts with a C. If we're both on the same page

03:09:41.639 --> 03:10:07.500
on this one. We are... No, that's not it. Is

03:10:07.500 --> 03:10:21.860
the beginning of the word. Mm -hmm. Create. Create.

03:10:23.120 --> 03:10:34.500
Order. Create. What? Creation. Well, sort of.

03:10:39.049 --> 03:10:48.409
We'll give you that. You create something so

03:10:48.409 --> 03:10:59.870
that it can do something else when you want to

03:10:59.870 --> 03:11:12.899
update it later as part of your account. So you

03:11:12.899 --> 03:11:24.379
create and then you condense it. No. Not exactly.

03:11:24.819 --> 03:11:30.319
Not quite. Not quite. You have the right idea.

03:11:31.159 --> 03:11:36.459
You create something and then it gets modified

03:11:36.459 --> 03:11:50.040
but it's Stored. Somewhere. Yeah, it's stored

03:11:50.040 --> 03:11:56.379
in the cloud. Okay, so cloud is your second word.

03:11:57.620 --> 03:12:08.719
And store is part of the third word. Yep. In

03:12:08.719 --> 03:12:23.729
item number one. Mm -hmm. So if you... Cloud

03:12:23.729 --> 03:12:29.469
storage. Okay, cloud storage is two out of the

03:12:29.469 --> 03:12:47.319
three words. So if you... Let's see. Misconfigured.

03:12:48.540 --> 03:12:52.420
Misconfigured is correct. You got it. That is

03:12:52.420 --> 03:12:55.459
exactly what it is. I was going to say, if you

03:12:55.459 --> 03:13:00.180
configure your cloud storage and something went

03:13:00.180 --> 03:13:07.500
wrong, then what would it be called? So misconfigure

03:13:07.500 --> 03:13:11.579
cloud storage is number one. That's exactly right.

03:13:11.819 --> 03:13:21.239
Now, number two isn't necessarily bad, but it

03:13:21.239 --> 03:13:32.159
can be depending on how bad it is. If you were

03:13:32.159 --> 03:13:37.290
to send something I'm not going to give the entire

03:13:37.290 --> 03:13:40.930
answer because send is part of the answer, but

03:13:40.930 --> 03:13:44.049
I'm not giving the entire thing away. But if

03:13:44.049 --> 03:13:51.610
you were sending something, and then you realized

03:13:51.610 --> 03:14:04.700
that something went wrong, what did you do? I

03:14:04.700 --> 03:14:08.040
think this is the best way I can do this. Well,

03:14:08.040 --> 03:14:10.799
actually, I have a bit of a story that I kind

03:14:10.799 --> 03:14:14.500
of wanted to mention when we got to this point.

03:14:14.559 --> 03:14:24.559
So this is perfect. Okay. So I received a notice,

03:14:24.819 --> 03:14:30.399
actually a confirmation email, from a doctor

03:14:30.399 --> 03:14:37.030
I've never even heard of. That I knew. Uh -huh.

03:14:37.409 --> 03:14:41.750
And not just that. That's one story. I also got

03:14:41.750 --> 03:14:45.870
many calls from an insurance company that were

03:14:45.870 --> 03:14:55.250
directed toward somebody else. Right. Not you

03:14:55.250 --> 03:14:58.010
in question. Correct. So what we're looking for

03:14:58.010 --> 03:15:02.610
is sending records to those, I mean, to the wrong

03:15:02.610 --> 03:15:05.690
patient. That is exactly what we're looking for.

03:15:05.690 --> 03:15:07.629
Ding, ding, ding, ding, ding, ding, ding, ding,

03:15:08.010 --> 03:15:09.250
ding, ding, ding, ding, ding, ding, ding, ding.

03:15:13.290 --> 03:15:19.450
Yes, I got many calls for Blanca Alarcon. And

03:15:19.450 --> 03:15:22.850
finally, when there was, yes, there was one day

03:15:22.850 --> 03:15:26.770
when she got, well, she was supposed to get a

03:15:26.770 --> 03:15:29.409
call confirming that she had an appointment.

03:15:29.450 --> 03:15:36.440
I got it instead. And so I finally did call,

03:15:36.739 --> 03:15:40.799
I think, whatever the doctor's office was. And

03:15:40.799 --> 03:15:45.440
I finally just told them, you know, this is not

03:15:45.440 --> 03:15:48.620
me. You know, and I really want to get this fixed

03:15:48.620 --> 03:15:52.700
because if there's anything more serious, that's

03:15:52.700 --> 03:15:56.360
potentially catastrophic. Well, what it turned

03:15:56.360 --> 03:15:59.239
out was that somebody apparently entered in the

03:15:59.239 --> 03:16:02.120
wrong phone Phone number. So that was a totally

03:16:02.120 --> 03:16:04.600
innocent mistake. Can happen to anybody, but

03:16:04.600 --> 03:16:10.020
yes, wrong records. But that's a big problem

03:16:10.020 --> 03:16:15.500
when it comes to health information. Right. And

03:16:15.500 --> 03:16:19.579
then the email story I was going to tell you

03:16:19.579 --> 03:16:23.760
was I got this appointment confirmation from

03:16:23.760 --> 03:16:27.920
Dr. I think it was Jason Simona in Michigan.

03:16:29.280 --> 03:16:33.840
And obviously, I don't live in Michigan. So that's

03:16:33.840 --> 03:16:35.620
not right. I don't even know who this person

03:16:35.620 --> 03:16:42.360
is. And yeah, so I called that office. Turned

03:16:42.360 --> 03:16:46.780
out somebody entered in the wrong email address.

03:16:50.059 --> 03:16:59.170
Oopsie. All right, so the final item. When you...

03:16:59.170 --> 03:17:02.530
There are two more that I see here, but yeah.

03:17:03.209 --> 03:17:08.290
Okay, you're right. So number three. When you

03:17:08.290 --> 03:17:15.129
want to get rid of something, there is a proper

03:17:15.129 --> 03:17:51.220
way to do that. And there is a... Or an... So

03:17:51.220 --> 03:17:57.389
if I were to... I don't know. say this would

03:17:57.389 --> 03:18:01.690
never happen, but if I were to suddenly come

03:18:01.690 --> 03:18:06.409
in to have a bunch of very sensitive personal

03:18:06.409 --> 03:18:09.290
information come into my possession, and all

03:18:09.290 --> 03:18:12.049
I did was basically just stuff it in a trash

03:18:12.049 --> 03:18:21.389
can, I would be accused of doing what? Improper

03:18:21.389 --> 03:18:28.280
disposal of physical data. The physical records.

03:18:28.920 --> 03:18:36.479
Preston must be reading. I think he is. All right,

03:18:36.479 --> 03:18:41.420
Terry. I'm not that stupid. Are you reading or

03:18:41.420 --> 03:18:46.840
are you... If you're reading, that's okay. Yeah,

03:18:46.840 --> 03:18:50.659
it's totally fine. I mean, I'm doing both, but

03:18:50.659 --> 03:18:53.059
I'm learning, so that's important. No, it's awesome.

03:18:53.399 --> 03:18:56.229
That's awesome. That's great. So, Terry. Since

03:18:56.229 --> 03:19:00.870
Preston also has a file open, item four, we've

03:19:00.870 --> 03:19:07.950
talked about every N, C, S. Oh, you're really

03:19:07.950 --> 03:19:12.149
bad. That's what I was going to say. He's a M.

03:19:13.729 --> 03:19:25.979
He's sounding horrible. Pop. Bang. Pop goes the

03:19:25.979 --> 03:19:32.760
Jared. So. There we go. Now you sound better.

03:19:32.760 --> 03:19:40.379
Try that again. Every NCSAM we talk about this.

03:19:41.399 --> 03:19:45.899
What is it? And this is usually the first topic.

03:19:46.639 --> 03:19:51.379
Passwords. Passwords is correct. The item says

03:19:51.379 --> 03:19:59.030
weak. Password. Practices. Practices. Well, that's

03:19:59.030 --> 03:20:01.329
anywhere, too. I mean, it's not just the health

03:20:01.329 --> 03:20:08.149
industry. Yes, that's exactly correct. Insider

03:20:08.149 --> 03:20:10.870
threats are a major concern as well, so we gave

03:20:10.870 --> 03:20:14.709
you guys that. And additionally, hospitals, like

03:20:14.709 --> 03:20:20.250
many others in this field, rely heavily on third

03:20:20.250 --> 03:20:25.479
-party systems. These can include billing companies,

03:20:25.760 --> 03:20:34.120
medical device manufacturers, and cloud providers.

03:20:36.579 --> 03:20:41.139
Like AWS. They're a big one. Right. They're the

03:20:41.139 --> 03:20:45.920
biggest. One of the biggest. The biggest. One

03:20:45.920 --> 03:20:50.020
of the biggest. Yep. There are two big cloud

03:20:50.020 --> 03:20:59.379
services. While convenient, this practice is

03:20:59.379 --> 03:21:03.620
dangerous as it dramatically increases the possible

03:21:03.620 --> 03:21:09.360
attack surface, given that those vendors may

03:21:09.360 --> 03:21:17.020
not have the best cybersecurity themselves. And

03:21:17.020 --> 03:21:20.799
before we continue, I want to stop and just say...

03:21:21.629 --> 03:21:25.510
That's why this story about the medical device

03:21:25.510 --> 03:21:28.969
manufacturer couldn't have been timed better.

03:21:29.090 --> 03:21:30.989
And that's why that's so important to mention

03:21:30.989 --> 03:21:38.430
it. And I think my copy of GPT said exactly the

03:21:38.430 --> 03:21:40.790
same thing, and it wanted me to incorporate it.

03:21:41.010 --> 03:21:43.889
And I said, we will, but this is Nick's topic,

03:21:44.069 --> 03:21:48.350
not mine. Well, that's kind of the way I wanted

03:21:48.350 --> 03:21:51.069
to incorporate it, you know, like discuss it

03:21:51.069 --> 03:21:52.969
in passing, like, you know, tie it to what we

03:21:52.969 --> 03:21:56.729
already discussed. Yeah, correct. I agree. Right.

03:21:56.909 --> 03:22:00.809
Yeah. But yeah, so that's exactly the one example

03:22:00.809 --> 03:22:05.329
is right there. And the other tie in conduit

03:22:05.329 --> 03:22:11.049
that we're dealing with because they have possession

03:22:11.049 --> 03:22:16.879
of exactly a lot of. A lot of health data, as

03:22:16.879 --> 03:22:20.760
we know, because they are basically the ones

03:22:20.760 --> 03:22:23.659
who are responsible from, based on what I read,

03:22:23.760 --> 03:22:27.940
processing Medicaid. And so, you know, those

03:22:27.940 --> 03:22:33.159
kinds of claims. So they are a third party. They

03:22:33.159 --> 03:22:38.059
are a third party data provider. And this is

03:22:38.059 --> 03:22:40.200
exactly the kind of thing that we're talking

03:22:40.200 --> 03:22:44.500
about right here. You know, not the... those

03:22:44.500 --> 03:22:47.799
entities themselves, but this third party that

03:22:47.799 --> 03:22:51.200
nobody's ever heard of that is the one storing

03:22:51.200 --> 03:22:53.559
slash handling all this data. And that reminded

03:22:53.559 --> 03:23:05.959
me of OP. OP, OP, M. M, yeah. Because nobody

03:23:05.959 --> 03:23:08.559
ever heard of them until we started getting letters,

03:23:08.659 --> 03:23:12.299
and my first comment was, who the hell are you?

03:23:14.609 --> 03:23:17.889
Exactly. And they're like, well, do you know

03:23:17.889 --> 03:23:21.850
somebody by the name of, and they gave me my

03:23:21.850 --> 03:23:24.569
grandfather's name, and I said, well, yeah, but

03:23:24.569 --> 03:23:29.709
he's gone. He's not living anymore. And they

03:23:29.709 --> 03:23:35.790
said, well, he signed you up for a job, and we

03:23:35.790 --> 03:23:38.389
do this, that, and the other. And I'm like, well,

03:23:38.489 --> 03:23:56.909
okay. Which is why I think I want to put out

03:23:56.909 --> 03:24:08.629
an ultimatum. And that is that if you are a company

03:24:08.629 --> 03:24:14.309
dealing with our information, the moment that

03:24:14.309 --> 03:24:25.659
you Do something with it. Like, give it to somebody

03:24:25.659 --> 03:24:30.440
without us knowing about it. You better turn

03:24:30.440 --> 03:24:33.180
around and let us know about it. This is our

03:24:33.180 --> 03:24:41.219
biller. This is what they're supposed to do with

03:24:41.219 --> 03:24:51.500
your info. Yeah. Yeah. So at least we know who

03:24:51.500 --> 03:25:06.719
the hell has our data. Yes. Yes. That's it. That's

03:25:06.719 --> 03:25:13.100
my ultimatum. Yes. And I think it's reasonable.

03:25:13.739 --> 03:25:16.940
And I think the people who get that information

03:25:16.940 --> 03:25:31.799
need to be the ones to notify us. Yep. Yep. Even

03:25:31.799 --> 03:25:33.799
if they send a letter out or an email saying,

03:25:33.920 --> 03:25:36.559
hey, we have your information. This is what we

03:25:36.559 --> 03:25:40.700
do. This is what we have. This is what we do.

03:25:41.500 --> 03:25:45.579
Correct. Make sure they tell you what information

03:25:45.579 --> 03:25:51.920
of yours they have, what they do and plan to

03:25:51.920 --> 03:25:55.340
do with it. Right. What information and why they

03:25:55.340 --> 03:26:02.020
have it. Exactly, yeah. Uh -huh. And do we have

03:26:02.020 --> 03:26:10.149
their consent? Yeah, do they consent to this?

03:26:11.590 --> 03:26:14.409
It's like, I bet a lot of people are, as they're

03:26:14.409 --> 03:26:16.270
probably saying now in some of those states,

03:26:16.409 --> 03:26:22.250
where there are big concentrations of breach

03:26:22.250 --> 03:26:24.170
data. A lot of these people are going, I don't

03:26:24.170 --> 03:26:26.350
know who Conduit is. I didn't tell them they

03:26:26.350 --> 03:26:29.750
could have my data. Well, and that's, again,

03:26:29.930 --> 03:26:33.850
that's where it comes to these data brokers buying

03:26:33.850 --> 03:26:38.540
data, you know. Illegally. I believe it's illegal.

03:26:38.920 --> 03:26:42.379
Illegally, exactly. I'm not disagreeing with

03:26:42.379 --> 03:26:48.479
you. But there's this fine line that they...

03:26:48.479 --> 03:27:07.250
It's a gray area. More or less. Mm -hmm. insurance

03:27:07.250 --> 03:27:14.549
companies is next. Oh my gosh. While medical

03:27:14.549 --> 03:27:19.569
facilities fail to protect our personal health

03:27:19.569 --> 03:27:24.069
information as they should, they are not the

03:27:24.069 --> 03:27:29.149
only ones in this field who are guilty. Nope.

03:27:29.450 --> 03:27:34.850
Insurance companies have an equally questionable

03:27:34.850 --> 03:27:41.469
track record. Okay, maybe I shouldn't do that.

03:27:43.610 --> 03:27:47.930
This is mainly due to an issue we've discussed

03:27:47.930 --> 03:27:53.049
time and time again on the podcast. Data retention

03:27:53.049 --> 03:28:02.190
practices. Retention. Oh damn. Exactly. They

03:28:02.829 --> 03:28:09.430
Will often store. And we have. One. Two. Three.

03:28:09.549 --> 03:28:18.930
Four. Three. Four. Yeah. Four of them. Well.

03:28:19.389 --> 03:28:26.629
So. Details is one. Terry already got one. All

03:28:26.629 --> 03:28:30.190
right. So. Decades. Personal information. Such

03:28:30.190 --> 03:28:35.520
as. Social Security number, address, phone number.

03:28:36.680 --> 03:28:39.340
That's another one. Okay, so Social Security

03:28:39.340 --> 03:28:44.940
number is item number three. Decades of claim

03:28:44.940 --> 03:28:49.780
data is item number one. Number one. And he got

03:28:49.780 --> 03:28:51.639
one of the others already. He got number two,

03:28:51.700 --> 03:28:55.159
financial data. Financial data is number two.

03:28:56.079 --> 03:29:00.540
So what's number four? What about medication

03:29:00.540 --> 03:29:10.780
records? Sort of close, but... Yeah, almost there.

03:29:11.059 --> 03:29:14.780
Almost there. I mean, because they do collect,

03:29:14.799 --> 03:29:18.059
like, what you take and stuff from meds, because

03:29:18.059 --> 03:29:22.379
I know... Meds is correct. We'll give it to you.

03:29:23.459 --> 03:29:28.459
The answer we're looking for is family, medical...

03:29:29.370 --> 03:29:34.250
History. History, oh yeah. Yeah, yeah, yep. Uh

03:29:34.250 --> 03:29:43.889
-huh. Which basically, yeah, you're... Large

03:29:43.889 --> 03:29:49.049
centralized databases like these create high

03:29:49.049 --> 03:29:54.989
-value breach targets while we know that we...

03:29:55.340 --> 03:29:58.639
We pretty much know that. I mean, Blue Cross.

03:30:01.120 --> 03:30:06.280
Shields. I remember that one. Anthem. Well, Anthem.

03:30:06.280 --> 03:30:08.760
Well, that's part of the whole Blue Cross. Didn't

03:30:08.760 --> 03:30:11.600
Humana get hit too, if I remember right? Humana

03:30:11.600 --> 03:30:16.559
got owned? What was it? UnitedHealthcare? UHF?

03:30:16.559 --> 03:30:19.399
There was another one, yep. Or UHC? Yep. They

03:30:19.399 --> 03:30:22.739
actually are asking me. They're actually asking

03:30:22.739 --> 03:30:25.700
me for my input. Maybe I should fill out the

03:30:25.700 --> 03:30:33.219
survey and tell them you already got owned. I

03:30:33.219 --> 03:30:40.920
cannot trust you. Yes. Are you right? Because

03:30:40.920 --> 03:30:45.319
they wanted me to take a survey. They wanted

03:30:45.319 --> 03:30:51.120
me to take a survey about something. I don't

03:30:51.120 --> 03:30:55.920
know. I haven't opened it yet. But I might have

03:30:55.920 --> 03:31:11.700
to do that on Friday. No, UHC. Yeah, UHC. Insurance

03:31:11.700 --> 03:31:16.040
companies are also notorious for another concerning

03:31:16.040 --> 03:31:22.260
behavior that we've mentioned frequently. The

03:31:22.260 --> 03:31:36.620
overcollection of data. Data is correct. Oh,

03:31:36.639 --> 03:31:41.530
I'm sorry. That's okay. Preston said it too.

03:31:41.670 --> 03:31:43.930
I think he started to say it anyway. He said

03:31:43.930 --> 03:31:48.610
it anyway. In addition to what was listed above,

03:31:48.969 --> 03:31:54.530
they can also collect and there's one, two, three

03:31:54.530 --> 03:32:06.450
of these. I don't know if you're using their

03:32:06.450 --> 03:32:08.649
application. You think you can collect your...

03:32:09.180 --> 03:32:23.540
Location data. No. That. No. I mean. Not in this

03:32:23.540 --> 03:32:28.139
list. No. Not here. Oh, not in this list. Okay.

03:32:28.280 --> 03:32:44.270
No. All of it. deals with some sort of data.

03:32:46.430 --> 03:32:51.829
Okay? Data's always going to be the last word

03:32:51.829 --> 03:33:09.309
in this bulleted list. Yep. procedures and tests

03:33:09.309 --> 03:33:20.370
and stuff like that. I think maybe that should

03:33:20.370 --> 03:33:22.969
have been listed. That should have been listed,

03:33:23.010 --> 03:33:35.209
but I don't see it here. No. And... I mean, I

03:33:35.209 --> 03:33:39.860
guess it... technically would have fallen under

03:33:39.860 --> 03:33:50.079
what was kind of in that first set of lists.

03:33:50.899 --> 03:33:53.899
Yeah, because we're talking about the medical

03:33:53.899 --> 03:33:59.559
histories, so that would be in there. Yeah. Which

03:33:59.559 --> 03:34:08.020
is why it doesn't show up here. If you... See

03:34:08.020 --> 03:34:19.600
a specialist because you are not... Mentally

03:34:19.600 --> 03:34:27.860
stable. Conforming to what would be considered

03:34:27.860 --> 03:34:36.700
norms. And you're known to... Yeah, so mental

03:34:36.700 --> 03:34:46.399
health data. Yeah. Not mental health. You act

03:34:46.399 --> 03:34:54.780
out and cause a scene and maybe you've been known

03:34:54.780 --> 03:35:01.799
to hit people. Yes. People talking about your

03:35:01.799 --> 03:35:08.120
bad... Starts with a B. Starts with a B. Behavior.

03:35:08.940 --> 03:35:14.159
We'll give it to you. Behavioral data. Behavioral

03:35:14.159 --> 03:35:23.079
data. That's right. Item number two. You go to

03:35:23.079 --> 03:35:28.719
the gym. You go to a restaurant. You go to the

03:35:28.719 --> 03:35:38.799
store. You go... and you eat about five and a

03:35:38.799 --> 03:35:43.280
half dozen boxes of donuts. And then you sit

03:35:43.280 --> 03:35:49.500
on the couch and watch TV. And wonder... Your

03:35:49.500 --> 03:35:56.319
weight. Not weight. Not weight. No. I mean, it

03:35:56.319 --> 03:36:00.700
does fall into a larger umbrella of things, though.

03:36:01.450 --> 03:36:12.290
Eating disorder. No. Okay. You're a vegan. You

03:36:12.290 --> 03:36:17.450
don't eat a lot of meat. You eat a lot of rice.

03:36:17.450 --> 03:36:24.969
You eat fish. You eat some chicken. But you stick

03:36:24.969 --> 03:36:34.000
to mainly healthy foods. You have a healthy what?

03:36:35.100 --> 03:36:38.639
Healthy what? Lifestyle. Lifestyle is correct.

03:36:39.600 --> 03:36:45.579
Lifestyle data is number two. Actually, I was

03:36:45.579 --> 03:36:51.420
going to guess metabolism. No. No. Metabolism

03:36:51.420 --> 03:36:55.180
is not it. Nick, you're going to have to help

03:36:55.180 --> 03:36:58.920
me with number three because I don't... Know

03:36:58.920 --> 03:37:05.799
how to... I'm trying to... Explain this one without

03:37:05.799 --> 03:37:10.739
giving it away. I'm trying to figure that out

03:37:10.739 --> 03:37:16.500
too. Nope. It's not a concept, I'll be honest

03:37:16.500 --> 03:37:20.020
here, that I truly understand. I don't either.

03:37:20.159 --> 03:37:28.760
But... I guess the way to look at it is... Say

03:37:28.760 --> 03:37:41.659
that you have a family member who contracted

03:37:41.659 --> 03:37:54.420
a certain condition. Yeah. What do you, let me

03:37:54.420 --> 03:37:58.180
think here. So if that family member, contracted

03:37:58.180 --> 03:38:08.739
a condition do you think they could in theory

03:38:08.739 --> 03:38:18.120
they could in theory pass it to you to you in

03:38:18.120 --> 03:38:26.639
some form STD that could be a form of what we're

03:38:26.639 --> 03:38:32.780
looking for. What was that? I missed what he

03:38:32.780 --> 03:38:38.079
said. It could be a form of what we're looking

03:38:38.079 --> 03:38:42.899
for. It could. It could be a form of it, yeah.

03:38:43.440 --> 03:38:52.139
Not the direct item, but a form of it. Yeah.

03:38:52.659 --> 03:38:56.979
So... All right. The first word I can think of,

03:38:57.020 --> 03:39:03.000
when we talk about, and this will be a totally

03:39:03.000 --> 03:39:05.200
different subject, guys, so sorry, but it'll

03:39:05.200 --> 03:39:10.479
make sense. When we talk about, you know, how

03:39:10.479 --> 03:39:12.899
the bear season is going to go, for example,

03:39:13.059 --> 03:39:19.600
what do we do? The word starts with a P. I'm

03:39:19.600 --> 03:39:23.180
not saying anything. Predict is correct. Procrastinate?

03:39:24.780 --> 03:39:28.940
Predict is correct. Yes, predict. Preston got

03:39:28.940 --> 03:39:34.920
it. All right. Exactly. The answer then becomes

03:39:34.920 --> 03:39:46.270
predictive risk data. Data. I guess the way that

03:39:46.270 --> 03:39:49.690
I understand this is, insurance companies now,

03:39:49.770 --> 03:39:52.049
because they have your family medical history,

03:39:52.329 --> 03:39:57.069
they know that, I don't know, say Preston's dad

03:39:57.069 --> 03:40:02.790
suffers from and contracted condition X or condition

03:40:02.790 --> 03:40:08.389
W. So they are predicting, given what's out there,

03:40:08.469 --> 03:40:12.709
that you are most likely at risk to also contract

03:40:12.709 --> 03:40:18.799
condition W. But they don't know when or if.

03:40:20.500 --> 03:40:24.840
But they just know that there is a risk or that

03:40:24.840 --> 03:40:30.299
there is a possibility that it will happen. Which

03:40:30.299 --> 03:40:38.040
is what they factor in with this data. The more

03:40:38.040 --> 03:40:41.780
data collected, the more damage a breach can

03:40:41.780 --> 03:40:49.489
cause. And now we come to something, ladies and

03:40:49.489 --> 03:40:53.750
gentlemen of the podcast and gentlemen of the

03:40:53.750 --> 03:41:01.709
panel, that we have actually talked a little

03:41:01.709 --> 03:41:09.709
bit about. Nick, don't say anything yet. I won't,

03:41:09.709 --> 03:41:11.709
but I will. I do want to say, though, before

03:41:11.709 --> 03:41:14.620
we get to it, I know I've only mentioned two

03:41:14.620 --> 03:41:18.520
sectors so far, but there's a reason for that.

03:41:18.600 --> 03:41:21.799
Because I think a lot of these behaviors overlap,

03:41:22.180 --> 03:41:25.780
unfortunately, into multiple areas of health

03:41:25.780 --> 03:41:29.280
care. Okay. You know, whether it's you have to,

03:41:29.299 --> 03:41:31.879
you know, whether you're filling out questionnaires.

03:41:31.879 --> 03:41:35.760
Like, you can't really be sure. You know, this

03:41:35.760 --> 03:41:37.680
goes back to the insider threats. You don't know

03:41:37.680 --> 03:41:41.280
who's handling that information. Nope. You know,

03:41:41.299 --> 03:41:42.620
if you're filling out a health questionnaire

03:41:42.620 --> 03:41:47.020
just for something. So I think that these things

03:41:47.020 --> 03:41:50.959
overlap. I agree. That's part of the reason that,

03:41:50.979 --> 03:41:54.139
yeah. Because otherwise, if we did something

03:41:54.139 --> 03:41:57.180
with every single sector, we'd be here for hours.

03:41:57.799 --> 03:42:00.579
Maybe even days. I do have hours, but that means

03:42:00.579 --> 03:42:05.520
the podcast won't be released until Friday. Right,

03:42:05.620 --> 03:42:11.040
exactly. I mean, I think you want it released.

03:42:11.600 --> 03:42:15.819
I don't think it'd be ours. I think you want

03:42:15.819 --> 03:42:18.760
it released either Wednesday night or Thursday

03:42:18.760 --> 03:42:22.319
morning, right? I think it'd be a few days we'd

03:42:22.319 --> 03:42:26.079
be here on the podcast. Yes, we would. And these

03:42:26.079 --> 03:42:28.540
notes that you have that are, I think, about

03:42:28.540 --> 03:42:31.079
13 pages, they'd be at least 20, probably 25.

03:42:36.930 --> 03:42:39.950
Exactly. I could probably do it within a few

03:42:39.950 --> 03:42:43.610
hours, but in this format, it would be about

03:42:43.610 --> 03:42:50.350
half the night. It's only 1 .30 in the morning,

03:42:50.409 --> 03:42:54.329
but we're still talking about this stuff. And

03:42:54.329 --> 03:43:05.409
I have a meeting in about 12 hours. How am I

03:43:05.409 --> 03:43:07.989
going to get through this? We're not even close

03:43:07.989 --> 03:43:13.489
to done. It's going to be like the old Jerry

03:43:13.489 --> 03:43:24.170
Lewis telephones. Mr. J. J. J. Yes, that would

03:43:24.170 --> 03:43:31.850
be me. Mr. J. J. Why did you pick this next?

03:43:34.020 --> 03:43:42.219
item without mentioning it by name? Well, part

03:43:42.219 --> 03:43:45.920
of it was when I was... Part of it had to do

03:43:45.920 --> 03:43:48.760
with the prompt that I typed in, but I agreed

03:43:48.760 --> 03:43:55.159
with that assessment because these... Oh, dude,

03:43:55.280 --> 03:43:59.420
I gotta get food. These are things that are...

03:43:59.659 --> 03:44:03.899
Very, very popular. Used by many, many, many

03:44:03.899 --> 03:44:09.639
people. And I think it's important to mention

03:44:09.639 --> 03:44:13.079
them because, like I said, the popularity and

03:44:13.079 --> 03:44:17.299
what they collect, which is substantial. If you

03:44:17.299 --> 03:44:18.979
really, really get down to it, you know, if you

03:44:18.979 --> 03:44:20.979
really sit down and think about it, what they

03:44:20.979 --> 03:44:27.760
collect is substantial. I agree. And we've talked

03:44:27.760 --> 03:44:36.270
about these In the past when manufacturers sort

03:44:36.270 --> 03:44:51.370
of mapped data and were able to tell where people

03:44:51.370 --> 03:44:57.010
were even though it was supposed to be secret.

03:44:59.340 --> 03:45:03.840
Uh -huh. What are we talking about, gentlemen?

03:45:04.040 --> 03:45:10.399
Nick and I can't answer. Right. It starts...

03:45:10.399 --> 03:45:25.020
Geolocations? Geolocations is part of it. Right.

03:45:32.040 --> 03:45:36.159
I don't think any of us own one of these devices.

03:45:37.280 --> 03:45:46.940
I knew somebody who did. And Kim Commando talks

03:45:46.940 --> 03:45:57.399
about one where it has been known to save some...

03:45:58.170 --> 03:46:01.469
L -l -l -l -l -l -l -l -l -l -l -l -l -l -l -l

03:46:01.469 --> 03:46:02.290
-l -l -l -l -l -l -l -l -l -l -l -l -l -l -l

03:46:02.290 --> 03:46:02.309
-l -l -l -l -l -l -l -l -l -l -l -l -l -l -l

03:46:02.309 --> 03:46:02.350
-l -l -l -l -l -l -l -l -l -l -l -l -l -l -l

03:46:02.350 --> 03:46:02.450
-l -l -l -l -l -l -l -l -l -l -l -l -l -l -l

03:46:02.450 --> 03:46:02.450
-l -l -l -l -l -l -l -l -l -l -l -l -l -l -l

03:46:02.450 --> 03:46:03.430
-l -l -l -l -l -l -l -l -l -l -l -l -l -l -l

03:46:03.430 --> 03:46:33.120
-l -l -l -l -l -l - This is an item that is used

03:46:33.120 --> 03:46:45.239
to tell time. Oh, yes. Like a clock or stopwatch

03:46:45.239 --> 03:46:49.100
in a way. Watch is the second part of the word.

03:46:52.340 --> 03:47:00.180
Now we're just looking for the brand. A lot of

03:47:00.180 --> 03:47:03.940
us are on this. But yeah, you're right. You're

03:47:03.940 --> 03:47:05.459
right. I don't think we need to go that far.

03:47:06.600 --> 03:47:16.280
But this watch along with other major providers

03:47:16.280 --> 03:47:32.520
have been known to Do things that might be kind

03:47:32.520 --> 03:47:36.299
of cool. Just like your phone can do. Like...

03:47:36.299 --> 03:47:46.159
Count steps. Know where you are. Apple Watch,

03:47:46.159 --> 03:47:53.440
right? Apple Watch is correct. Mr. Ring. Yes.

03:47:54.559 --> 03:48:05.819
An Apple Watch is part of... What group? Werewolves.

03:48:06.680 --> 03:48:10.139
Werewolves is correct. He's got it. You got it.

03:48:10.180 --> 03:48:12.420
You got it. Mr. Ring. That is our next section.

03:48:13.120 --> 03:48:22.350
Go ahead, Mr. J. Okay. Happy to. While these

03:48:22.350 --> 03:48:24.889
are not directly connected to the healthcare

03:48:24.889 --> 03:48:27.409
industry like insurance companies and medical

03:48:27.409 --> 03:48:31.989
facilities, wearables like the Apple Watch and

03:48:31.989 --> 03:48:36.569
Fitbit also collect a massive amount of health

03:48:36.569 --> 03:48:42.049
data. This can include, among other things, and

03:48:42.049 --> 03:48:44.690
we have a list here. I don't know. Let's see.

03:48:44.729 --> 03:48:54.029
Heart rate, blood oxygen levels, sleep. Terry

03:48:54.029 --> 03:48:57.030
has already gotten two of them. Items number

03:48:57.030 --> 03:48:59.969
one and two. Heart rate and sleep patterns. That

03:48:59.969 --> 03:49:03.850
is correct. I know they do cycle tracking now.

03:49:09.190 --> 03:49:13.690
Actually, I got to give you... I would give you

03:49:13.690 --> 03:49:18.090
that because one of them is activity logs. Oh,

03:49:18.090 --> 03:49:20.389
yeah, activity. Well, that's not really activities.

03:49:20.469 --> 03:49:23.350
That wouldn't be under that. Yeah, activity logs,

03:49:23.649 --> 03:49:28.069
yeah. Workout data, yeah. Yeah, so that's...

03:49:28.069 --> 03:49:33.969
Yeah, that would be... So activity data. We've

03:49:33.969 --> 03:49:39.569
got sleep patterns. Heart rate. One of them...

03:49:39.569 --> 03:49:48.979
Yep. One of them has been me for about... A month.

03:49:52.799 --> 03:49:59.360
Mm -hmm. You've been feeling a certain way. Yeah.

03:49:59.920 --> 03:50:10.180
Sick as a dog. Oh, excuse me. Not that. Well,

03:50:10.479 --> 03:50:15.159
it also collects how many times you've fallen

03:50:15.159 --> 03:50:19.729
and... Well, that's part of activity. That's

03:50:19.729 --> 03:50:22.030
part of activity. That's part of activity, yeah.

03:50:23.809 --> 03:50:28.690
If... That wasn't the word. Let's see. It's like,

03:50:28.770 --> 03:50:36.069
okay, if... If I almost got my ass handed to

03:50:36.069 --> 03:50:42.229
me just by crossing the street, I would be...

03:50:46.250 --> 03:50:50.950
Feeling a lot of this emotion. Anxiety. Not anxiety.

03:50:51.309 --> 03:51:00.110
Anxiety risk. Nope. Not anxiety. It also collects

03:51:00.110 --> 03:51:04.889
mental health data too. That's part of activity.

03:51:05.670 --> 03:51:13.409
All of that's part of activity. This word starts

03:51:13.409 --> 03:51:30.670
with... N. S. It does. I've been this way until

03:51:30.670 --> 03:51:42.829
last week when I started rebuilding my work environment.

03:51:43.719 --> 03:51:46.639
And then I started blogging like I really want

03:51:46.639 --> 03:51:51.819
to. Your system. He was building his system.

03:51:51.959 --> 03:51:55.659
I was building my system. But before I built

03:51:55.659 --> 03:52:01.120
my system. Before I built my system. The week

03:52:01.120 --> 03:52:06.239
before. He was tearing his hair out. I tore my

03:52:06.239 --> 03:52:23.950
hair out. Yes. Yeah. I was what? Oh, you guys

03:52:23.950 --> 03:52:28.250
are failing me for a while. Okay, I have another

03:52:28.250 --> 03:52:38.309
idea of how to approach this. So, this was an

03:52:38.309 --> 03:52:48.260
item... I don't think we're quite there yet.

03:52:49.299 --> 03:52:54.000
But what I was going to say is this is an item

03:52:54.000 --> 03:53:00.139
that has been very, very popular. And you're

03:53:00.139 --> 03:53:05.819
supposed to squeeze this to relieve what? It's

03:53:05.819 --> 03:53:11.120
part of something that you can get. Oh, stress,

03:53:11.379 --> 03:53:16.319
maybe? Stress is correct, Mr. Riggs. The item

03:53:16.319 --> 03:53:20.600
we're looking for is stress levels. Stress levels.

03:53:22.260 --> 03:53:31.620
Stress levels. Oh, damn. The final item, which

03:53:31.620 --> 03:53:41.039
is item number four. Did we mention it? Actually,

03:53:41.039 --> 03:53:43.319
on mine, I don't see that as the final item.

03:53:44.299 --> 03:53:46.979
Well, it's the final one that hasn't been mentioned.

03:53:47.680 --> 03:53:54.620
Yes, yes, okay. So, indirectly, we did mention

03:53:54.620 --> 03:54:06.760
it. We were just talking about it. Okay. So...

03:54:06.760 --> 03:54:12.690
If it knows... Where you are, it knows what?

03:54:14.690 --> 03:54:19.530
Location data. Location is correct. Location

03:54:19.530 --> 03:54:24.629
data is right on. All right. And so, again, let's

03:54:24.629 --> 03:54:30.250
recap these for the listeners. We've got heart

03:54:30.250 --> 03:54:40.290
rate. We've got sleep patterns. stress levels,

03:54:40.409 --> 03:54:49.409
location data, and activity logs. Activity logs.

03:54:49.530 --> 03:54:54.010
I'm just getting my dinner, Jared. It's piloting

03:54:54.010 --> 03:55:00.770
here. Go ahead, Mr. J. This... This is especially

03:55:00.770 --> 03:55:06.409
worrying as most are not covered under HIPAA.

03:55:08.520 --> 03:55:13.520
And that is... Sad. Bad. Bad. That is extremely

03:55:13.520 --> 03:55:17.719
bad. That is extremely bad. And the problem is,

03:55:17.780 --> 03:55:23.319
even... And the sad thing is, even when there

03:55:23.319 --> 03:55:28.280
are places who are required to be HIPAA compliant,

03:55:28.620 --> 03:55:31.299
they don't always follow that either. So this

03:55:31.299 --> 03:55:37.110
is really scary. No, they don't. Those type of

03:55:37.110 --> 03:55:39.770
forums really don't mean much nowadays. No, they

03:55:39.770 --> 03:55:44.690
don't. So additionally, these devices can and

03:55:44.690 --> 03:55:52.510
there are one, two, three, four items. Yeah.

03:55:55.790 --> 03:56:10.299
Okay, so if you... Are not named. You are...

03:56:10.299 --> 03:56:18.059
Anonymous. Anonymous. So, share anonymized or

03:56:18.059 --> 03:56:25.940
poorly anonymized data is item number one. Okay,

03:56:26.219 --> 03:56:38.469
so number two. I have... a page on jaredreimer

03:56:38.469 --> 03:56:51.690
.net that allows you to do this. Do this for

03:56:51.690 --> 03:56:59.389
a fee where we will create something for you

03:56:59.389 --> 03:57:11.850
in audio and you provide the text. A promo slash

03:57:11.850 --> 03:57:16.649
advertisement or script. Advertise is correct.

03:57:17.110 --> 03:57:21.590
Advertiser is correct. So partner with advertisers.

03:57:22.850 --> 03:57:31.549
Yep. Item number three. I believe this is probably

03:57:31.549 --> 03:57:38.129
going to be the biggest ones. You create a database,

03:57:38.489 --> 03:58:00.110
okay? Yep. And you claim that you sort of anonymize

03:58:00.110 --> 03:58:06.829
it, but you... Put it together. You put it together.

03:58:09.950 --> 03:58:24.370
And you do what? You sell it. Okay, sell we'll

03:58:24.370 --> 03:58:33.149
get. So sell what? You're not selling the whole

03:58:33.149 --> 03:58:42.930
database. No, you're... But you're putting a

03:58:42.930 --> 03:58:52.569
portion of the database together and you sell

03:58:52.569 --> 03:59:18.120
it. Menve has parents, educators, students, transcribers,

03:59:18.120 --> 03:59:28.680
and even therapists. Somebody recently came to

03:59:28.680 --> 03:59:36.329
us some years back. And we talked about whether

03:59:36.329 --> 03:59:58.930
we should be giving them this. What? Oh, you

03:59:58.930 --> 04:00:04.500
guys are failing me really bad. It's... Oh, man.

04:00:05.459 --> 04:00:10.899
Well, basically, hang on. I think I almost had

04:00:10.899 --> 04:00:20.680
it. Where basically they basically aggregated

04:00:20.680 --> 04:00:24.540
the data. I'll give it to you. You just saved

04:00:24.540 --> 04:00:30.620
the group. I'll give it to you. Self -aggregated

04:00:31.149 --> 04:00:37.170
Data sets. Data sets. You've got it. That's exactly

04:00:37.170 --> 04:00:42.649
what it was. Okay. We talked about item number

04:00:42.649 --> 04:00:49.590
four a little bit in passing when we mentioned

04:00:49.590 --> 04:01:07.020
Melissa. Melissa. Yes. What technically is Melissa?

04:01:07.040 --> 04:01:11.680
Sharing information with data brokers. Both of

04:01:11.680 --> 04:01:19.120
you have it. Sharing information with data brokers

04:01:19.120 --> 04:01:23.899
is correct. Data brokers. Bingo. Nick, go ahead,

04:01:24.000 --> 04:01:28.299
please, with the paragraph. I would be happy

04:01:28.299 --> 04:01:32.200
to. I'd like to focus on the first item in this

04:01:32.200 --> 04:01:37.200
list, the sharing of anonymized data. When combined

04:01:37.200 --> 04:01:40.579
with information from other sources, of which

04:01:40.579 --> 04:01:44.559
there are all too many, it is possible to re

04:01:44.559 --> 04:01:48.399
-identify an individual. So, so much for privacy,

04:01:48.559 --> 04:01:58.180
so much for anonymization. Furthermore, Wearables

04:01:58.180 --> 04:02:02.540
fail to protect our PHI thanks to one unique

04:02:02.540 --> 04:02:10.219
feature. Their vague privacy policies. Many of

04:02:10.219 --> 04:02:22.739
these, and we have a list here, of three. We

04:02:22.739 --> 04:02:30.709
talked about... The first item, when we talked

04:02:30.709 --> 04:02:39.610
about the JRN slash Menvee versus your big time

04:02:39.610 --> 04:02:47.290
company. When we talked about policies that are

04:02:47.290 --> 04:03:03.059
hard to read. What would that be if I say that

04:03:03.059 --> 04:03:16.940
they're hard to read? That would be... They are

04:03:16.940 --> 04:03:21.420
pretty much lengthy and complex. Good. That's

04:03:21.420 --> 04:03:26.799
item number one. Lengthy and complex. Item number

04:03:26.799 --> 04:03:37.079
two. So they talk about things that they are

04:03:37.079 --> 04:03:45.420
wanting to do, but they put it all together in

04:03:45.420 --> 04:04:02.889
an item as part of the policy. They do some bundling.

04:04:03.510 --> 04:04:07.709
Bundling is correct. Bundle multiple permissions

04:04:07.709 --> 04:04:12.069
is what we're looking for. Item number three.

04:04:14.569 --> 04:04:19.790
The Music Education Network allows you to do

04:04:19.790 --> 04:04:28.719
this if you do not want to have Certain pieces

04:04:28.719 --> 04:04:37.180
of information in your application put out into

04:04:37.180 --> 04:04:43.399
our roster, but we can have it for us if we need

04:04:43.399 --> 04:04:51.959
to contact you. Maybe like opting out? You got

04:04:51.959 --> 04:04:55.569
it. Opting out, we'll take. What we're looking

04:04:55.569 --> 04:05:06.690
for is offer limited meaningful opt -outs. Users

04:05:06.690 --> 04:05:11.389
often consent without understanding the scope.

04:05:12.210 --> 04:05:17.770
of data sharing. Note, I am not suggesting that

04:05:17.770 --> 04:05:21.569
wearables should not be used. If anyone owns

04:05:21.569 --> 04:05:27.069
one and finds it usable, that's excellent. Rather,

04:05:27.270 --> 04:05:35.090
I share them only to raise awareness. Okay, my

04:05:35.090 --> 04:05:38.549
mistake. I should have... I realized that when

04:05:38.549 --> 04:05:41.430
I was reading this yesterday. That should have

04:05:41.430 --> 04:05:44.049
been rather I share this only to raise awareness.

04:05:44.129 --> 04:05:52.889
My mistake. Oh, that's what it says. No, not

04:05:52.889 --> 04:05:56.549
on mine. Because on mine it says rather I share

04:05:56.549 --> 04:05:58.850
them only to raise awareness. I meant to say

04:05:58.850 --> 04:06:08.840
I share this only to raise awareness. Oh, I do

04:06:08.840 --> 04:06:12.819
say them. Okay, I do see that. Okay. Yeah, that

04:06:12.819 --> 04:06:19.600
was my mistake, not yours. Okay. I think we're

04:06:19.600 --> 04:06:23.739
on one of the final items, if my memory serves

04:06:23.739 --> 04:06:31.440
me correct. Mr. J? All right, this one. Insecure

04:06:31.440 --> 04:06:37.829
by design. Troubling as these poor cybersecurity

04:06:37.829 --> 04:06:42.270
practices are, there is, unfortunately, little

04:06:42.270 --> 04:06:47.069
hope of anything changing. Whenever there is

04:06:47.069 --> 04:06:50.450
an order to pay a fine, it is often little more

04:06:50.450 --> 04:06:52.770
than a slap on the wrist for the company involved.

04:06:53.610 --> 04:06:58.629
Since these penalties usually don't have much

04:06:58.629 --> 04:07:02.180
of an effect, they may decide... and I mean the

04:07:02.180 --> 04:07:04.819
companies here, that it is more cost -effective

04:07:04.819 --> 04:07:08.340
to issue a well -crafted statement, pay, and

04:07:08.340 --> 04:07:12.200
move on until the next major breach. Google.

04:07:12.239 --> 04:07:15.879
The motivation to adopt better... Exactly. Google.

04:07:16.040 --> 04:07:18.420
Exactly. Well... Google, I was just thinking

04:07:18.420 --> 04:07:22.680
of them too, yeah. Well, they're probably the

04:07:22.680 --> 04:07:26.420
most visible, I'll give you that. Go ahead, please.

04:07:28.600 --> 04:07:31.920
The motivation to adopt better cybersecurity

04:07:31.920 --> 04:07:40.639
practices then is low. And the next section actually

04:07:40.639 --> 04:07:42.899
is something we were just talking about, but

04:07:42.899 --> 04:07:46.360
it fits perfectly. In a medical setting, too,

04:07:46.520 --> 04:07:52.620
there can be no downtime. The top priority, and

04:07:52.620 --> 04:07:56.850
we can disagree. All day long on whether this

04:07:56.850 --> 04:07:59.549
is true or not, but ideally, the top priority,

04:07:59.709 --> 04:08:04.930
as it should be, is patient care. I agree. But

04:08:04.930 --> 04:08:09.030
go ahead. Yeah. Yeah. Definitely. I'm getting

04:08:09.030 --> 04:08:13.059
to that. At the same time, this does not allow

04:08:13.059 --> 04:08:16.200
for the installation of critical updates or patches

04:08:16.200 --> 04:08:19.959
to vulnerable systems, leaving them wide open

04:08:19.959 --> 04:08:23.319
to cyber criminals and other bad actors. Hello,

04:08:23.459 --> 04:08:31.719
WannaCry? WannaCry? Now, if I can do it as a

04:08:31.719 --> 04:08:36.020
small business, and the people that I work with...

04:08:38.350 --> 04:08:43.549
patch our servers to make sure that we are as

04:08:43.549 --> 04:08:48.370
safe as possible, then you should too. It only

04:08:48.370 --> 04:08:55.590
takes five minutes. They should update their

04:08:55.590 --> 04:09:00.989
systems, Jared. I'm not disagreeing. But you've

04:09:00.989 --> 04:09:04.610
got to remember, in a hospital setting, Five

04:09:04.610 --> 04:09:07.290
minutes could mean literally life or death. Yeah.

04:09:09.250 --> 04:09:12.469
I'm not in disagreement with you, Nick, but not

04:09:12.469 --> 04:09:17.729
everything. If you're in surgery, you're not

04:09:17.729 --> 04:09:21.229
messing. They shouldn't be messing with a computer.

04:09:22.129 --> 04:09:24.829
They should be putting their hands in you and

04:09:24.829 --> 04:09:30.270
dealing with what you need help with. Absolutely.

04:09:30.629 --> 04:09:36.129
Absolutely. I agree that software should be updated.

04:09:36.270 --> 04:09:38.010
There's no question about that. Things should

04:09:38.010 --> 04:09:41.270
be patched. But yeah, in that setting, it's not

04:09:41.270 --> 04:09:44.309
like somebody's going to go, hang on, I've got

04:09:44.309 --> 04:09:46.069
to install this Windows update. Because then

04:09:46.069 --> 04:09:48.790
you might have a risk of the system not booting.

04:09:48.790 --> 04:09:51.409
And of course, that's the personnel files or

04:09:51.409 --> 04:09:55.149
patient records that they need. But that's not...

04:09:55.149 --> 04:10:00.170
You've got to remember, updating it would take

04:10:00.170 --> 04:10:03.989
the servers offline. But, you know, heart monitors,

04:10:04.129 --> 04:10:06.930
like if your blood pressure stuff, I mean, that's

04:10:06.930 --> 04:10:09.950
random. That should never be online to begin

04:10:09.950 --> 04:10:16.450
with. Oh, we all know it is. No way. You know,

04:10:16.549 --> 04:10:20.750
that's the other problem. If that system is online,

04:10:20.989 --> 04:10:27.790
then we've got a huge problem. Oh, my gosh. I

04:10:27.790 --> 04:10:31.360
imagine it would be, yeah. Finish the paragraph,

04:10:31.780 --> 04:10:38.079
Mr. J. Absolutely. Okay, worse still, there are

04:10:38.079 --> 04:10:41.940
many who benefit from these practices. Insurance

04:10:41.940 --> 04:10:45.299
companies, for instance, need such massive amounts

04:10:45.299 --> 04:10:48.319
of data for underwriting and for various aspects

04:10:48.319 --> 04:10:53.940
of their business. Some insurers will also offer

04:10:53.940 --> 04:10:56.639
discounts to those who choose to have various

04:10:56.639 --> 04:11:01.260
health data points. tracked via wearables, incentivizing

04:11:01.260 --> 04:11:06.319
more data collection. Developers of those devices

04:11:06.319 --> 04:11:09.559
and apps also benefit financially by selling

04:11:09.559 --> 04:11:13.600
our data, as well as through opaque privacy policies

04:11:13.600 --> 04:11:17.219
and legalese, which they probably assume, correctly,

04:11:17.540 --> 04:11:27.280
very few will read. In legalese, which they probably

04:11:27.280 --> 04:11:38.020
assume correctly, very few will read. Mm -hmm.

04:11:38.760 --> 04:11:42.680
Yeah. Because most people are like, oh, it's

04:11:42.680 --> 04:11:47.360
my doctor, it's fine. You know, it's good. Or

04:11:47.360 --> 04:11:49.819
even, unfortunately, Uber and Lyft. It's, oh,

04:11:49.879 --> 04:11:53.819
yeah, yeah, I've got the app. Yeah, yeah, yeah.

04:11:53.819 --> 04:11:56.600
Okay. Good. All right. That's all right. All

04:11:56.600 --> 04:12:02.540
right. I'm signed. All right. We're good. But

04:12:02.540 --> 04:12:06.260
yet they can collect all this data. Then you

04:12:06.260 --> 04:12:08.620
find out later, I didn't know they did that.

04:12:10.159 --> 04:12:14.000
Because it's in... I mean, this goes back to

04:12:14.000 --> 04:12:23.450
268, folks. Yep. The JRN writes... Privacy policies

04:12:23.450 --> 04:12:37.889
that tell you exactly what we're doing. And why

04:12:37.889 --> 04:12:44.389
they are important to read. We just don't pull

04:12:44.389 --> 04:12:50.729
it out of our ass. We give it purpose. And we

04:12:50.729 --> 04:12:56.489
inform you of how things are. And if you don't

04:12:56.489 --> 04:13:01.590
like it, don't log on to our services. Okay,

04:13:01.590 --> 04:13:12.389
I accidentally lost the heading for this next

04:13:12.389 --> 04:13:14.430
section. But yeah, we're talking about something

04:13:14.430 --> 04:13:17.500
else now. My bad. I was going to say, I left

04:13:17.500 --> 04:13:20.799
a blank mark. I don't know if I missed a heading.

04:13:22.780 --> 04:13:25.920
I thought I'd put that in there, but I could

04:13:25.920 --> 04:13:29.719
have accidentally deleted it. Keep in mind, remember,

04:13:29.819 --> 04:13:34.360
the scammers would have hoisted a really bad

04:13:34.360 --> 04:13:37.399
older version of this on us if they'd have their

04:13:37.399 --> 04:13:45.870
way. Let me see. Um... What I had in mind was

04:13:45.870 --> 04:13:52.430
best practices. I remember that being a heading.

04:13:54.989 --> 04:14:15.059
Weird. Where did it go? Weird. Where did it go?

04:14:17.379 --> 04:14:33.219
I'm looking for you. It seems to have disappeared.

04:14:35.040 --> 04:14:55.200
Yeah. I remember seeing it. Oh. Okay. I put the

04:14:55.200 --> 04:15:04.600
subheading for it. But I guess it did not get

04:15:04.600 --> 04:15:17.379
copied. Whoops. That was my error. Whoops. Well,

04:15:18.819 --> 04:15:21.760
it at least still kind of ties to what we were

04:15:21.760 --> 04:15:23.879
talking about, so it's not like it's a huge jump.

04:15:28.620 --> 04:15:33.659
I see it in your file, so I had the idea of putting

04:15:33.659 --> 04:15:38.260
in the subhead for it, and I guess I didn't...

04:15:38.260 --> 04:15:46.600
Oops. That's okay. I think this is actually the

04:15:46.600 --> 04:15:51.639
last item, correct? No, there's one more. There's

04:15:51.639 --> 04:15:54.819
one more after this. All right, well, I'll read

04:15:54.819 --> 04:15:59.899
best practices then. Okay. As stated above, the

04:15:59.899 --> 04:16:05.719
outlook for change appears bleak, but there are

04:16:05.719 --> 04:16:12.360
still steps that many entities in the healthcare

04:16:12.360 --> 04:16:17.659
industry can take. to store our PHI more securely.

04:16:17.920 --> 04:16:22.200
While none of these will prevent a data breach

04:16:22.200 --> 04:16:28.520
entirely, adopting at least one or two from the

04:16:28.520 --> 04:16:34.000
following list would minimize the impact should

04:16:34.000 --> 04:16:42.100
one occur. There are, in fact, good practices

04:16:43.129 --> 04:16:48.170
for storing any sensitive information. Some may

04:16:48.170 --> 04:16:53.129
sound very familiar, as they have been adopted

04:16:53.129 --> 04:16:57.649
by the JRN and discussed on the last episode.

04:16:58.649 --> 04:17:06.049
Okay. So, there are nine, and I don't expect

04:17:06.049 --> 04:17:10.690
everybody to get them, so Nick and I will take

04:17:10.690 --> 04:17:14.399
turns reading them. And then what I'll do is

04:17:14.399 --> 04:17:20.319
I'll redo Braille files if people want a new

04:17:20.319 --> 04:17:23.979
one, and I'll just add the best practices items

04:17:23.979 --> 04:17:30.000
in the subheading like it should be. And that's

04:17:30.000 --> 04:17:34.440
an easy fix. I've already corrected the spacing

04:17:34.440 --> 04:17:38.520
and things in the list. Item number one, strong

04:17:38.520 --> 04:17:46.989
data minimization. Agree or disagree? Agree.

04:17:46.989 --> 04:17:53.829
I hear an agree. Agree as well. Okay. Collect

04:17:53.829 --> 04:18:01.989
only what is necessary. Definitely agree. I hear

04:18:01.989 --> 04:18:07.690
totally and definitely. Item number three. Zero

04:18:07.690 --> 04:18:17.809
trust. Architecture is yes. Yes. Yeah. I missed

04:18:17.809 --> 04:18:23.930
a word. Okay. Number four. Continuous authentication

04:18:23.930 --> 04:18:31.190
and access validation. I .e., we don't have some

04:18:31.190 --> 04:18:35.309
random employee who was terminated four months

04:18:35.309 --> 04:18:49.170
ago who still has freaking access. That is nuts,

04:18:49.329 --> 04:18:56.190
that article. That's not the only... Terry, that's

04:18:56.190 --> 04:18:58.750
not the only one. There have been many incidents

04:18:58.750 --> 04:19:03.010
of this. Well, yeah, I'm sure of it, but that

04:19:03.010 --> 04:19:06.600
article was definitely enough. That we've discussed.

04:19:07.940 --> 04:19:10.360
And it wasn't just in healthcare. It was other

04:19:10.360 --> 04:19:15.680
industries too. Yeah. On number five is vendor

04:19:15.680 --> 04:19:22.299
risk. Accountability. Yeah. All this is vendor

04:19:22.299 --> 04:19:26.219
risk accountability. Needs to be. There needs

04:19:26.219 --> 04:19:30.899
to be. There used to be. Maybe. Right. But is

04:19:30.899 --> 04:19:34.719
there? There needs to be. Not anymore. Preston,

04:19:34.719 --> 04:19:37.620
not anymore. Again, there needs to be. Again,

04:19:37.659 --> 04:19:44.979
there needs to be. Yeah, I know. I know. Good

04:19:44.979 --> 04:19:52.139
night, Preston. I know. Third parties should

04:19:52.139 --> 04:20:01.260
face direct regulatory liability. I've been saying

04:20:01.260 --> 04:20:11.440
that Four years. Look at... What's that one article

04:20:11.440 --> 04:20:19.659
that I went on half of a diatribe on before the

04:20:19.659 --> 04:20:28.540
computer went in for repair? Not sure which one

04:20:28.540 --> 04:20:35.729
exactly, but... The social media wannabe? That

04:20:35.729 --> 04:20:41.950
got fined $19 million. Reddit. Okay, Reddit.

04:20:42.030 --> 04:20:47.250
Yes, I remember now. Yeah. As I said, the social

04:20:47.250 --> 04:20:51.629
media wannabe. Could you imagine getting fined

04:20:51.629 --> 04:20:57.170
$19 million, Jared? That was about 14 million

04:20:57.170 --> 04:21:02.690
euros, boy. Yeah, that's... But to some of these

04:21:02.690 --> 04:21:06.459
people, that's like... Yeah, our profit margins

04:21:06.459 --> 04:21:11.379
are tens of millions. We'll be fine. Just pay

04:21:11.379 --> 04:21:16.079
and move on. Could you imagine me if I had to

04:21:16.079 --> 04:21:22.840
pay... I don't even know if... I don't even know...

04:21:22.840 --> 04:21:25.819
I'm going to say this carefully. I wouldn't even

04:21:25.819 --> 04:21:31.360
know if the money I may or may not have would

04:21:31.360 --> 04:21:38.110
even cover that. No. Let's just put it this way.

04:21:38.389 --> 04:21:42.530
If you had to do that, there would be no J .R

04:21:42.530 --> 04:21:47.370
.N. at all in the future. That would be the end.

04:21:47.629 --> 04:21:49.329
He probably wouldn't even be living at where

04:21:49.329 --> 04:21:55.010
he was living right now. He's dead. In a way

04:21:55.010 --> 04:21:59.250
worse situation. 98 .6 The Mix would be gone.

04:21:59.350 --> 04:22:02.260
Probably forever. There won't be no anything.

04:22:02.540 --> 04:22:18.040
All servers. Yeah. Be interesting. Number seven.

04:22:19.600 --> 04:22:24.739
Expansion of privacy law hasn't moved forward

04:22:24.739 --> 04:22:28.520
at all. I've been whining about this before TSB.

04:22:31.950 --> 04:22:42.329
Oh, yes. Number eight. Close gaps for wearables

04:22:42.329 --> 04:22:44.889
and health apps. I don't see that ever changing.

04:22:46.069 --> 04:22:52.329
Yeah, I'm with you on that. No. And number nine.

04:22:52.350 --> 04:22:58.700
Go ahead. Okay. Number nine. User education.

04:22:59.219 --> 04:23:08.760
Which is what we've been doing for years. I think

04:23:08.760 --> 04:23:16.799
I've been doing this for actually March 6th.

04:23:20.079 --> 04:23:34.940
Started my 20th year. Wow. That is hard to believe

04:23:34.940 --> 04:23:38.639
but amazing. Podcast number three was the first

04:23:38.639 --> 04:23:42.620
episode of the technology podcast where I had

04:23:42.620 --> 04:23:48.120
to get involved in the security landscape. Yeah.

04:23:48.780 --> 04:24:22.040
That's right. And... That... Done. 321. It will

04:24:22.040 --> 04:24:32.079
be 10 years for me doing the mix. Wow. You got

04:24:32.079 --> 04:24:37.120
10 years on me there, Jared. I'm not talking

04:24:37.120 --> 04:24:46.639
necessarily just being on the mix, Terry. That's

04:24:46.639 --> 04:24:50.780
not what I'm talking about. You're talking about

04:24:50.780 --> 04:24:56.520
all your stuff, yeah. No. Even before then. Even

04:24:56.520 --> 04:25:04.319
before, yeah. I'm talking... about me blogging

04:25:04.319 --> 04:25:10.299
and talking about the security landscape where

04:25:10.299 --> 04:25:15.879
the first application that we dealt with was

04:25:15.879 --> 04:25:21.780
a version of accessible chat where blind people

04:25:21.780 --> 04:25:43.079
were losing their computers. I might have to

04:25:43.079 --> 04:25:48.040
play this episode. I think it was episode three.

04:25:48.159 --> 04:25:50.540
Maybe. My memory serves me. That's a good idea.

04:25:51.260 --> 04:25:58.309
After the show. It's not the greatest sounding,

04:25:58.510 --> 04:26:04.489
because headsets were different then. Yeah. But,

04:26:04.489 --> 04:26:18.469
you know. Go ahead, please, Mr. J. Patience.

04:26:19.510 --> 04:26:24.840
Sure. Patients need transparency and meaningful

04:26:24.840 --> 04:26:28.959
control. What are your thoughts? Do you think

04:26:28.959 --> 04:26:31.860
that any of these are practical? Are there any

04:26:31.860 --> 04:26:37.780
others that you think should be considered? And

04:26:37.780 --> 04:26:41.940
what do you guys think? There is one more section.

04:26:44.899 --> 04:26:56.690
Well, I would say that... You know, when people

04:26:56.690 --> 04:27:00.370
go somewhere, they need to make sure that they're

04:27:00.370 --> 04:27:05.930
being taken care of. And especially with having

04:27:05.930 --> 04:27:10.489
bad practices, I don't think that's a good sign.

04:27:13.110 --> 04:27:16.649
I would say, I mean, even though I wrote them,

04:27:16.690 --> 04:27:20.950
so I technically, you know... shouldn't be speaking

04:27:20.950 --> 04:27:25.389
this much, but I would say that the first few,

04:27:25.590 --> 04:27:29.709
the ones that focus on data minimization, those,

04:27:29.829 --> 04:27:32.670
I hate to be honest, I hate to have to say this,

04:27:32.770 --> 04:27:39.569
but I think that's the only truly concrete one

04:27:39.569 --> 04:27:43.670
that no one's going to want to implement. I'm

04:27:43.670 --> 04:27:47.270
sorry, but that's probably the best one because

04:27:48.139 --> 04:27:53.399
I agree with you. Closing the gaps slash privacy

04:27:53.399 --> 04:28:00.780
laws expanding, that's a good idea. But keep

04:28:00.780 --> 04:28:04.280
in mind, and this is what I found when I was

04:28:04.280 --> 04:28:07.239
doing this, so I don't know. I just changed while

04:28:07.239 --> 04:28:11.200
you guys are talking the best practices and making

04:28:11.200 --> 04:28:14.420
sure that we correct that. So if we do need to

04:28:14.420 --> 04:28:18.700
regenerate Braille, we can do that. Okay. Okay,

04:28:18.700 --> 04:28:26.559
so HIPAA, and I will look this up. Is a joke.

04:28:26.620 --> 04:28:28.940
Well, good, there's that. It's the Health Insurance

04:28:28.940 --> 04:28:35.000
Portability and Affordability Act. Affordability

04:28:35.000 --> 04:28:45.239
Act. H -I -P -A -A. Which, according to what

04:28:45.239 --> 04:28:49.489
I read... Is a joke. Was passed in, well, was

04:28:49.489 --> 04:28:54.350
passed in 1996 and yes, is a joke. But here's

04:28:54.350 --> 04:28:57.809
the thing. Wearables weren't even a thought in

04:28:57.809 --> 04:29:00.590
anybody's mind yet. So my problem with this is

04:29:00.590 --> 04:29:05.110
wearables and technology, it's moving at the

04:29:05.110 --> 04:29:08.309
speed of basically a commercial airliner. Yeah.

04:29:08.370 --> 04:29:13.370
Government and regulators. Go ahead. We haven't

04:29:13.370 --> 04:29:20.000
had privacy. even before wearables first came

04:29:20.000 --> 04:29:27.280
out. I can't disagree with you. No, you haven't.

04:29:30.760 --> 04:29:35.399
Wearables only started in the mid -2000s, but

04:29:35.399 --> 04:29:39.700
we already had problems. The thing is, Jerry,

04:29:39.739 --> 04:29:43.959
updating the privacy law isn't going to do much

04:29:43.959 --> 04:29:48.850
unless you enforce it. There is no enforcement,

04:29:49.069 --> 04:29:57.930
Terry. There is not. You've got terms of service

04:29:57.930 --> 04:30:01.969
that are written in legalese. That nobody's reading.

04:30:02.430 --> 04:30:07.030
Well, hold on a minute. You've got data written

04:30:07.030 --> 04:30:13.950
in legalese that isn't even fucking enforced.

04:30:20.270 --> 04:30:23.129
But the point I was going to make was that, and

04:30:23.129 --> 04:30:27.549
all of these are good, I agree. You've got technology

04:30:27.549 --> 04:30:30.549
that's moving at the speed of a commercial airliner.

04:30:30.950 --> 04:30:32.950
You've got government and regulators that are

04:30:32.950 --> 04:30:35.690
moving at the speed of maybe a Model T Ford on

04:30:35.690 --> 04:30:41.530
a good day. No, I would say a stagecoach, maybe.

04:30:42.149 --> 04:30:46.870
Well, I mean, you've got CISA. You've got CISA.

04:30:46.889 --> 04:30:51.379
Who's got... You've got CISA. Now, they've got

04:30:51.379 --> 04:30:56.260
great ideas. They've got people that understand

04:30:56.260 --> 04:31:03.940
this industry that write great stuff. We've talked

04:31:03.940 --> 04:31:11.120
about a lot of this in CyberScoop. Yep. But this

04:31:11.120 --> 04:31:20.219
shit is not enforced. Nope. Even though it should

04:31:20.219 --> 04:31:24.579
be, but it isn't. But it's not. AKA hospital

04:31:24.579 --> 04:31:30.299
administrators, you know. You tell people like

04:31:30.299 --> 04:31:36.219
me to update. Well, where am I going to get the

04:31:36.219 --> 04:31:40.860
money to get a proper Windows 11 machine? Because

04:31:40.860 --> 04:31:58.209
I just paid $500. $20 in new equipment and a

04:31:58.209 --> 04:32:02.250
hard drive for this thing. Wow. Which is one

04:32:02.250 --> 04:32:09.090
year out of the 2018 recommendation list for

04:32:09.090 --> 04:32:21.799
11. I spent... $175 to pay for the work. I spent

04:32:21.799 --> 04:32:33.739
$290 for the drive. The one terabyte drive. And

04:32:33.739 --> 04:32:42.899
I spent $59 .95 a piece for two... Not one, but

04:32:42.899 --> 04:32:45.860
two, two, two, two, two, two, two, two, two.

04:32:47.379 --> 04:33:07.500
Twelve plug plugs. And this machine is a 16 gig

04:33:07.500 --> 04:33:11.639
RAM machine. machine, which is perfect for what

04:33:11.639 --> 04:33:17.779
I need. Today's machine will only give me an

04:33:17.779 --> 04:33:22.740
8. And probably barely enough room for windows

04:33:22.740 --> 04:33:29.840
these days. Unless you build it yourself or have

04:33:29.840 --> 04:33:32.860
someone help you build it. But that's going to

04:33:32.860 --> 04:33:39.939
cost me more than $520. Yeah, my computer was

04:33:39.939 --> 04:33:47.360
1 ,100 out of the box. This thing cost my old

04:33:47.360 --> 04:33:58.659
man roughly $2 ,000. Oh, yeah, at that time,

04:33:58.740 --> 04:34:00.779
yeah. Wow, that's what I'm saying, man. At that

04:34:00.779 --> 04:34:05.200
time, yeah, $2 ,000 would be it. You stupid.

04:34:06.020 --> 04:34:10.080
Wow. Nowadays, you can get a pretty decent one

04:34:10.080 --> 04:34:17.880
for less than 16 gigs of RAM. I have 16 in mine.

04:34:18.279 --> 04:34:22.979
Yeah, I paid $1 ,100 and it was a one terabyte

04:34:22.979 --> 04:34:26.700
hard drive, 16 gigs of RAM. I think mine's 32.

04:34:29.259 --> 04:34:36.540
How much did you pay for yours? Close to $2 ,000.

04:34:37.119 --> 04:34:41.680
I mean, delivery slash shipping, that upped it

04:34:41.680 --> 04:34:43.700
a little, but that's pretty close to where I

04:34:43.700 --> 04:34:47.540
was. It was $1 ,600 because I did a firm and

04:34:47.540 --> 04:34:53.619
they charge you interest, so I was $1 ,600. That's

04:34:53.619 --> 04:34:56.619
why mine was close to $2 ,000 because I was -

04:34:56.619 --> 04:35:00.419
No, but if I could have, if I could have, I would

04:35:00.419 --> 04:35:03.400
have stuck with my Windows 10 machine. But the

04:35:03.400 --> 04:35:07.189
fact that it was - I don't even know. This is

04:35:07.189 --> 04:35:10.029
behavior I've never seen. The fact that it was

04:35:10.029 --> 04:35:15.990
constantly inputting plus signs everywhere. That

04:35:15.990 --> 04:35:20.069
sounds like a keyboard issue to me. That's a

04:35:20.069 --> 04:35:21.549
keyboard issue to me. That's the thing though.

04:35:22.470 --> 04:35:26.770
I tried with different keyboards and it was the

04:35:26.770 --> 04:35:29.990
same and it was reproducing the same thing. It

04:35:29.990 --> 04:35:37.680
was doing the same thing. Weird. Weird. Well,

04:35:37.779 --> 04:35:45.419
mine gave me a 301 I don't know if this drive

04:35:45.419 --> 04:35:51.779
will work error message. I'd have to get with

04:35:51.779 --> 04:35:56.099
GPT of chat because it has the pictures and find

04:35:56.099 --> 04:35:59.939
that thing and ask it and say, go analyze the

04:35:59.939 --> 04:36:06.099
chat. And find the photo that I found the 301

04:36:06.099 --> 04:36:10.639
error message. What was the exact error message

04:36:10.639 --> 04:36:13.419
and the accompanying error message I gave you?

04:36:16.419 --> 04:36:19.279
Basically, long story short, was the drive was

04:36:19.279 --> 04:36:22.040
failing. It was the smart system telling me that

04:36:22.040 --> 04:36:27.880
the drive was on the verge of failing. Oh, boy.

04:36:33.319 --> 04:36:35.500
And actually, I can think of one thing right

04:36:35.500 --> 04:36:39.659
off the bat that I missed that we've already

04:36:39.659 --> 04:36:43.939
discussed, but I think it was probably after

04:36:43.939 --> 04:36:47.380
these were already written. The local storage

04:36:47.380 --> 04:36:54.959
architecture. Yeah. I mean, that's a big, that

04:36:54.959 --> 04:36:57.659
is a huge deal. I'm kind of surprised it didn't

04:36:57.659 --> 04:37:02.830
come up in the prompt that I saw. Maybe we should

04:37:02.830 --> 04:37:07.369
talk about local storage architecture in podcast

04:37:07.369 --> 04:37:32.819
number 2222277. Oh, mm -hmm. 277. Oh, yeah. I

04:37:32.819 --> 04:37:35.479
think Preston's about half ready to be gone.

04:37:35.819 --> 04:37:39.560
He won't be ready for tomorrow's meeting, folks.

04:37:39.680 --> 04:37:45.139
He's going to be gone. He is going to be gone.

04:37:48.880 --> 04:37:52.099
And I haven't even eaten yet. I've been up since

04:37:52.099 --> 04:37:56.380
nearly 7 a .m. And I have not even eaten anything

04:37:56.380 --> 04:38:01.700
because the maid came. Oh my gosh. I haven't

04:38:01.700 --> 04:38:04.299
eaten anything either. Hey, I got up at 7 -2

04:38:04.299 --> 04:38:07.340
because I had to get ready for work. I just had

04:38:07.340 --> 04:38:09.599
to finish eating my wings. I haven't even eaten

04:38:09.599 --> 04:38:18.560
a thing. I've only had a cup of I think it was

04:38:18.560 --> 04:38:21.659
a latte. My guy bought me this vanilla latte

04:38:21.659 --> 04:38:28.580
for the Keurig, but I'm not I mean, it's fine.

04:38:28.680 --> 04:38:32.080
I like it. But I'm not much of a vanilla guy.

04:38:32.520 --> 04:38:37.099
But I'll drink it. I'm not against it. I'm just

04:38:37.099 --> 04:38:41.220
not a vanilla guy. I am. That would have been

04:38:41.220 --> 04:38:43.919
awesome. I would like that too, actually, because

04:38:43.919 --> 04:38:49.520
I like vanilla. Okay, so when we become the data

04:38:49.520 --> 04:38:53.299
breach, which is our final item. Now, Nick, why

04:38:53.299 --> 04:39:01.110
was this put into our... Our last segment here.

04:39:02.729 --> 04:39:10.330
Mainly due to behavior that I've seen, not just

04:39:10.330 --> 04:39:13.869
from our source that we like to talk about, but

04:39:13.869 --> 04:39:19.349
just in general. Just not even talking about

04:39:19.349 --> 04:39:23.209
companies, just people and just oversharing,

04:39:23.229 --> 04:39:25.330
which the internet has basically made normal.

04:39:26.509 --> 04:39:39.270
Once FaceBite became normalized... People posted

04:39:39.270 --> 04:39:50.990
everything. I'm still waiting for somebody to

04:39:50.990 --> 04:39:59.919
post about... Something. Or two or three. It'll

04:39:59.919 --> 04:40:05.279
happen. It'll happen. It will happen. It's coming.

04:40:05.439 --> 04:40:13.639
I smell it. And I mean, even in these PSAs, there

04:40:13.639 --> 04:40:19.459
was one for, what was it? It was about, oh yeah,

04:40:19.500 --> 04:40:24.250
this info, this PSA, you know. Be careful. You

04:40:24.250 --> 04:40:26.029
know, get your blood pressure checked. And it

04:40:26.029 --> 04:40:29.610
was people actually giving actual vitals. And

04:40:29.610 --> 04:40:32.549
I mean, granted, you don't know these people.

04:40:32.569 --> 04:40:35.450
You don't know their names. But given that so

04:40:35.450 --> 04:40:40.150
much else about them is out there. I'm 150 over

04:40:40.150 --> 04:40:45.029
195. That's basically what these kind of things

04:40:45.029 --> 04:40:47.169
said. That's exactly, yeah, what you just did

04:40:47.169 --> 04:40:49.709
was exactly what this was happening. You know,

04:40:49.709 --> 04:40:52.930
that's what was happening. And what I'm saying

04:40:52.930 --> 04:40:56.150
is we don't know their names, you know, so they

04:40:56.150 --> 04:40:58.009
don't they didn't come out and give us their

04:40:58.009 --> 04:41:02.069
names or any other info. But how do you know

04:41:02.069 --> 04:41:07.009
that some shady data broker or somebody is not

04:41:07.009 --> 04:41:11.849
listening and analyzing and researching and looking

04:41:11.849 --> 04:41:19.310
and going, how can I help, quote unquote, this

04:41:19.310 --> 04:41:25.340
person? What can I do? How can I sell this person?

04:41:30.959 --> 04:41:41.259
Learning. Up to this point we have focused on

04:41:41.259 --> 04:41:49.740
the corporate side of protecting PHI. Now I I

04:41:49.740 --> 04:41:53.720
would like to briefly shift our discussion to

04:41:53.720 --> 04:41:59.259
the individual and one concerning trend. The

04:41:59.259 --> 04:42:06.599
voluntary disclosure of it. Yeah. Before we continue,

04:42:06.880 --> 04:42:12.340
I want to make it clear that this is not meant

04:42:12.340 --> 04:42:17.299
to shame anyone. It is a trend we have observed

04:42:17.299 --> 04:42:23.439
on... internet, radio, social media, and elsewhere.

04:42:24.259 --> 04:42:28.540
The reasons for doing so are entirely understandable.

04:42:28.860 --> 04:42:33.779
They can include advocating for a health cause,

04:42:34.020 --> 04:42:39.860
finding support, or creating a sense of authenticity.

04:42:41.880 --> 04:42:46.200
At the same time, disclosing such personal information

04:42:46.200 --> 04:42:54.720
represents A serious risk. Livestreams, podcasts,

04:42:54.979 --> 04:43:01.340
and social media posts are often recorded, clipped,

04:43:01.439 --> 04:43:07.180
shared, and archived indefinitely. Oh boy, we

04:43:07.180 --> 04:43:11.400
know that because somebody went completely ape.

04:43:12.020 --> 04:43:22.700
Uh -huh. When some old piece of audio came up

04:43:22.700 --> 04:43:30.740
and, boy, then they went ape and dug up some

04:43:30.740 --> 04:43:43.279
audio on something else. Yeah, but there's no

04:43:43.279 --> 04:43:46.659
point in starting freaking feuds like that. But

04:43:46.659 --> 04:43:57.060
that's how it works, Mr. Ray. No, I'm not saying

04:43:57.060 --> 04:44:01.159
that. But come on, it's kind of just pointless

04:44:01.159 --> 04:44:09.290
and ridiculous. I agree, but that's just... And

04:44:09.290 --> 04:44:12.250
I want to just stop. I want to pause for just

04:44:12.250 --> 04:44:16.470
a minute. One of the defenses that I've heard

04:44:16.470 --> 04:44:22.130
when, you know, I think I was talking to another

04:44:22.130 --> 04:44:26.169
individual about this kind of thing. One of the

04:44:26.169 --> 04:44:28.330
defenses that I've heard, you know, they try

04:44:28.330 --> 04:44:30.810
to justify this behavior. Well, I only shared

04:44:30.810 --> 04:44:37.029
it with my friends. That's not weak. That's not.

04:44:38.670 --> 04:44:41.349
And then your friends are turning around and

04:44:41.349 --> 04:44:44.869
sharing it around the internet. That's not technically

04:44:44.869 --> 04:44:56.569
your friends. That too. Well, yes, because probably

04:44:56.569 --> 04:44:59.150
you don't necessarily know half the people on

04:44:59.150 --> 04:45:04.509
your timeline. Okay, this is stuck. Oh, that

04:45:04.509 --> 04:45:07.959
is stuck. Uh -oh. But yes, the main thing, though,

04:45:07.979 --> 04:45:10.479
that I wanted to focus on was what Terry just

04:45:10.479 --> 04:45:13.439
said. Because, yeah, one of your friends might

04:45:13.439 --> 04:45:15.939
just have an issue with you and decide, you know

04:45:15.939 --> 04:45:20.200
what? I'm going to just share this post that

04:45:20.200 --> 04:45:24.279
was only supposed to be for me out to the entire

04:45:24.279 --> 04:45:26.540
world. Because for whatever reason, I just don't

04:45:26.540 --> 04:45:30.159
like this person right now. Exactly. That's what

04:45:30.159 --> 04:45:33.900
actually happened to somebody that I knew who

04:45:33.900 --> 04:45:39.090
used to be on another radio station. Yeah, he

04:45:39.090 --> 04:45:41.750
shared something that he thought was just among

04:45:41.750 --> 04:45:46.689
his friends. Later he finds out it was made public.

04:45:52.490 --> 04:46:07.720
Once PHI is disclosed publicly, It cannot be

04:46:07.720 --> 04:46:14.740
fully retracted, increasing the risk of misuse

04:46:14.740 --> 04:46:21.700
or long -term harm. Such harm could come in the

04:46:21.700 --> 04:46:26.360
form of targeting by advertisers or scammers

04:46:26.360 --> 04:46:31.020
via social engineering campaigns. The best thing

04:46:31.020 --> 04:46:37.419
we can do, then, is to carefully consider what

04:46:37.419 --> 04:46:42.279
we post before we put it out there as the internet,

04:46:42.380 --> 04:46:53.979
for all intents and purposes, is forever. All

04:46:53.979 --> 04:46:58.580
questions and comments are welcome. Also, thank

04:46:58.580 --> 04:47:03.400
you to Jared and ChatGPT. for helping to put

04:47:03.400 --> 04:47:09.040
these show notes together. Well, you are quite

04:47:09.040 --> 04:47:15.580
welcome, Mr. J. It was a pleasure to assist you.

04:47:16.700 --> 04:47:20.919
No problem. I actually cannot believe... Go ahead.

04:47:21.459 --> 04:47:27.119
I am very happy that you turned this in to something

04:47:27.119 --> 04:47:39.479
that we can... utilize, and turn into a discussion.

04:47:39.819 --> 04:47:44.200
And since I need my display tomorrow, I have

04:47:44.200 --> 04:47:54.119
now gone to my 12 plug thing, found my USB cord,

04:47:54.340 --> 04:48:01.200
and gave my Braille display. A power cord to

04:48:01.200 --> 04:48:06.880
eat for tomorrow. Awesome. Because now it's up

04:48:06.880 --> 04:48:11.020
here where it belongs. Instead of sitting down

04:48:11.020 --> 04:48:13.779
there when I was wanting to tape something and

04:48:13.779 --> 04:48:17.900
it completely died. Oh yeah, I was taping RCL.

04:48:18.419 --> 04:48:21.180
I was taping their news thing and I started recording

04:48:21.180 --> 04:48:32.419
it and it completely died. But, no, good job

04:48:32.419 --> 04:48:35.139
on your first topic. That's why with RCL, you

04:48:35.139 --> 04:48:39.900
should have multiple... Thanks. People recording

04:48:39.900 --> 04:48:43.720
just in case shit like that happens again. And

04:48:43.720 --> 04:48:47.360
there actually was, believe it or not, there

04:48:47.360 --> 04:48:53.599
was more that the GPT of chat put in. But I think

04:48:53.599 --> 04:48:58.959
we did... When we start this, it's three... 20

04:48:58.959 --> 04:49:02.979
now? I'm amazed. It's 3 .20 now and we started

04:49:02.979 --> 04:49:10.860
this at nearly 1. Yes. I am so shocked. Two hours

04:49:10.860 --> 04:49:14.319
we got it done in? Just about two hours? Yeah,

04:49:14.340 --> 04:49:16.200
I'm shocked we were able to keep it going this

04:49:16.200 --> 04:49:23.659
long. Wow. But no, I mean, GPT also included

04:49:23.659 --> 04:49:27.439
things like You know, ransomware vulnerability

04:49:27.439 --> 04:49:32.279
is like, yeah, that's true, but... Ransomware

04:49:32.279 --> 04:49:39.240
is a completely different animal. It's not...

04:49:39.240 --> 04:49:43.819
Yes. It's not the same because anybody can be

04:49:43.819 --> 04:49:47.500
hit with ransomware and ransomware just locks

04:49:47.500 --> 04:49:51.099
up your data and you have to pay to get it back

04:49:51.099 --> 04:49:56.810
because, let's face it, the... hospital industry,

04:49:57.150 --> 04:50:05.290
well, okay, the healthcare industry, even if

04:50:05.290 --> 04:50:12.590
they backed up their data, could not come back

04:50:12.590 --> 04:50:19.729
from a ransomware attack. Nope. No. Because they'd

04:50:19.729 --> 04:50:25.770
have so much data that it would basically take

04:50:25.770 --> 04:50:31.310
them forever to restore it because download speeds

04:50:31.310 --> 04:50:37.950
are so slow. There's just no way to get everything

04:50:37.950 --> 04:50:41.290
back up and running. Not only that, could you

04:50:41.290 --> 04:50:44.069
imagine the amount of that ransom? I mean, it'd

04:50:44.069 --> 04:50:47.610
probably be... We've talked about it, Terry.

04:50:47.729 --> 04:50:52.450
That's all Terry. It has happened with Lori's,

04:50:52.450 --> 04:50:54.830
I know. I understand that. I'm not talking about

04:50:54.830 --> 04:51:02.729
Lori's. Yeah. We've had multiple ransomwares.

04:51:02.729 --> 04:51:08.790
I mean, we've had one death to date because an

04:51:08.790 --> 04:51:12.389
ambulance was turned away from a hospital because

04:51:12.389 --> 04:51:17.139
they were pilfered. By ransomware in Germany.

04:51:17.259 --> 04:51:20.500
I remember hearing about that, yeah. Yep. That

04:51:20.500 --> 04:51:33.360
pissed me the fuck off. Yeah, that was crazy.

04:51:33.619 --> 04:51:35.119
Yeah, I mean, that was one of the other things

04:51:35.119 --> 04:51:39.319
that was mentioned, and it's like, yes, but you

04:51:39.319 --> 04:51:41.299
can't really call that a failure, because like

04:51:41.299 --> 04:51:49.540
you said, anybody could fall for that. Yep. Literally

04:51:49.540 --> 04:51:52.720
anyone can fall for that, yeah. That's what I

04:51:52.720 --> 04:51:56.840
said then. Yeah, yeah. And another thing that

04:51:56.840 --> 04:51:59.200
mentioned that I did not include was phishing

04:51:59.200 --> 04:52:03.060
attacks. But that's every day. I mean, we're

04:52:03.060 --> 04:52:07.319
dealing with that every day. And again, anybody

04:52:07.319 --> 04:52:12.520
could fall for that. Anybody could fall for that.

04:52:16.520 --> 04:52:25.700
they're more prone to that than others. Yeah,

04:52:25.700 --> 04:52:32.540
I... Speaking of which, I got yet another Apple

04:52:32.540 --> 04:52:37.779
slash iCloud phishing email saying, you know,

04:52:37.799 --> 04:52:41.299
your cloud storage is full. You know, click here

04:52:41.299 --> 04:52:47.319
to basically upgrade or whatever. And I looked

04:52:47.319 --> 04:52:50.279
at the address of this person. It was some Gmail

04:52:50.279 --> 04:52:55.439
address. Should we be surprised? No. No, I'm

04:52:55.439 --> 04:53:02.680
not. It's like devinsalliance or something at

04:53:02.680 --> 04:53:05.500
gmail .com. It's like, you're not even Apple.

04:53:07.060 --> 04:53:18.330
Um... If I made my link that started 268 through

04:53:18.330 --> 04:53:23.509
274 made public where you guys could read what

04:53:23.509 --> 04:53:29.549
ChatGPT and I were up to, you would all shit.

04:53:32.209 --> 04:53:44.099
Uh -oh. I sent it all of those... emails we've

04:53:44.099 --> 04:53:46.439
had through the years and it told me what they

04:53:46.439 --> 04:53:49.959
are and I told it we've talked about every single

04:53:49.959 --> 04:54:29.490
one of them. Wow, intense times. And the topics

04:54:29.490 --> 04:54:36.810
are even going to get better, Mr. G. Yeah, next

04:54:36.810 --> 04:54:42.869
up, hallucinations. Not after too many mushrooms,

04:54:43.110 --> 04:54:46.110
no. I've never hallucinated in this industry

04:54:46.110 --> 04:54:59.340
yet. Well, this will be a learning experience

04:54:59.340 --> 04:55:04.279
for me, too, because I think of hallucinations

04:55:04.279 --> 04:55:11.020
when AI does them or has them as one thing, but

04:55:11.020 --> 04:55:14.360
I don't think that is what it is. It is not.

04:55:31.279 --> 04:55:34.459
really looking forward to, and I've got to be

04:55:34.459 --> 04:55:37.880
honest, I have very, very strong opinions about

04:55:37.880 --> 04:55:43.180
this kind of dynamic, is 271. Yes, and I told

04:55:43.180 --> 04:55:56.299
them that they have about a month. Okay, yeah,

04:55:56.360 --> 04:56:13.139
that's about right. Because they did confirm

04:56:13.139 --> 04:56:16.740
that they got those notes. And I said, great.

04:56:17.040 --> 04:56:24.279
Then you can make them your own. You've got about

04:56:24.279 --> 04:56:51.959
a month to do it. Yep. Simple note. Okay, that's

04:56:51.959 --> 04:57:20.090
not the right note I want. I'm just unpinning

04:57:20.090 --> 04:57:22.689
some notes that I don't need pinned anymore.

04:57:23.849 --> 04:57:37.209
Okay. So 269, covering personal information.

04:57:37.709 --> 04:57:40.110
Now, companies don't protect the way they...

04:57:40.650 --> 04:57:47.729
Ways they claim they do. Yep. And I think they

04:57:47.729 --> 04:58:01.169
need to start shaping up. Real quick. 272. Technical

04:58:01.169 --> 04:58:12.139
debt. Oh, yes. Yes. 273. Tool friction, accessibility,

04:58:12.619 --> 04:58:19.979
enforced workarounds, technical neglect, debt.

04:58:20.599 --> 04:58:27.779
Google Docs, I'm looking at you. You stupid fuck.

04:58:29.119 --> 04:58:34.840
Telecrap, I'm looking at you. Fuck telecrap.

04:58:35.740 --> 04:58:42.439
Google Docs used to be my logger. Mr. J? I used

04:58:42.439 --> 04:58:46.080
to put my temporary logs for Metro in a temporary

04:58:46.080 --> 04:58:50.880
log there and then move those. I can't do it

04:58:50.880 --> 04:58:57.360
anymore. You go and open Google Docs and you

04:58:57.360 --> 04:59:01.000
can write in a document. As soon as you hit done,

04:59:01.180 --> 04:59:09.090
that's it. If you double tap at the bottom of

04:59:09.090 --> 04:59:11.450
your document to go to the bottom of your document,

04:59:11.610 --> 04:59:15.330
it'll tell you it went. But you want to know

04:59:15.330 --> 04:59:21.509
what's been happening since February 4th? I'm

04:59:21.509 --> 04:59:26.110
just deleting somehow. Nope, not deleting. Nope.

04:59:28.110 --> 04:59:41.369
It puts your shit at the top. And I wasn't doing

04:59:41.369 --> 04:59:45.009
this in my master log. I was doing this in a

04:59:45.009 --> 04:59:58.029
blank document. Podcast 274, Nick. Why do defenses?

05:00:00.759 --> 05:00:05.119
Behave the way they do, i .e., Windows to Crapper

05:00:05.119 --> 05:00:07.799
versus Malwarebytes versus some of the other

05:00:07.799 --> 05:00:21.040
antivirus tools. Uh -huh. 275. Security burnout.

05:00:21.139 --> 05:00:29.590
The human cost of the security landscape. I think

05:00:29.590 --> 05:00:32.689
that's where I am now. I'm burned. I'm burned

05:00:32.689 --> 05:00:37.930
out. I'm done. Cooked, fried, baked. Yep, yep,

05:00:38.069 --> 05:00:52.490
yep. 276. 276. Parked domains. Oh, that delightful

05:00:52.490 --> 05:01:00.180
topic. Why they are bad to have. We talked about

05:01:00.180 --> 05:01:06.619
that. What was it? Last week, Mr. Ring. That's

05:01:06.619 --> 05:01:09.819
what I thought. Because I think we were discussing

05:01:09.819 --> 05:01:15.200
it last week. We were, and I said, this is why

05:01:15.200 --> 05:01:19.540
you will never find any of my customers pointing

05:01:19.540 --> 05:01:27.720
their crap at those servers. You sign up with

05:01:27.720 --> 05:01:32.020
me, you point your shit at me, and then you take

05:01:32.020 --> 05:01:39.779
as much time as you want. And that's also the

05:01:39.779 --> 05:01:41.700
episode where the scammers tried to mess with

05:01:41.700 --> 05:01:54.759
my file. Yes. So, 277, Mr. J? Did you... Want

05:01:54.759 --> 05:02:00.099
to circle back on something? While I'm in here

05:02:00.099 --> 05:02:05.500
writing? Because I'm in SimpleNote. Because that's

05:02:05.500 --> 05:02:10.779
what I'm using for this list now. Oh, yes. 277.

05:02:11.139 --> 05:02:14.419
Local storage architecture. That, I think, is

05:02:14.419 --> 05:02:17.279
a big deal that we really haven't talked a lot

05:02:17.279 --> 05:02:41.259
about. Architecture. Got it. Yeah. Okay All right

05:02:41.259 --> 05:02:49.080
Actually while we're in here I want to check

05:02:49.080 --> 05:03:01.500
one thing That's not it. That was good. Which

05:03:01.500 --> 05:03:04.639
is funny because I haven't had anything to either

05:03:04.639 --> 05:03:09.200
eat or drink today at all. Well, I've had that

05:03:09.200 --> 05:03:16.360
water and I had the vanilla thing and that's

05:03:16.360 --> 05:03:21.599
been it. And how come architecture sounds like

05:03:21.599 --> 05:03:28.750
Jaws isn't pronouncing it right? I don't know.

05:03:28.849 --> 05:03:33.869
I think it's spelled right. Better be spelled

05:03:33.869 --> 05:03:57.650
right. You can always ask your device. Okay,

05:03:57.669 --> 05:04:02.930
so I don't know if I can really relay this very

05:04:02.930 --> 05:04:06.689
clearly, but I just looked up predictive risk

05:04:06.689 --> 05:04:12.610
data. We kind of got it, but we kind of missed

05:04:12.610 --> 05:04:16.229
the mark on it. All right, I got it to give me

05:04:16.229 --> 05:04:22.310
the right spelling of it. Okay. I got Google.

05:04:22.770 --> 05:04:33.610
Okay, cool. I got Google. I told it to spell

05:04:33.610 --> 05:04:36.810
it, and it's like, search results for spell for

05:04:36.810 --> 05:04:38.709
whatever, and I'm like, oh, that's the word.

05:04:38.830 --> 05:04:40.810
I'll just copy and paste it. Thank you very much.

05:04:41.709 --> 05:04:45.950
Cool. Cool. So this is according to the GPT of

05:04:45.950 --> 05:04:53.909
chat. Here is its explanation of predictive risk

05:04:53.909 --> 05:04:57.590
data that we were... Oh, go ahead. Have it read.

05:04:57.790 --> 05:05:03.970
Yeah. I think the best way, unfortunately, right

05:05:03.970 --> 05:05:06.990
now is to try and read this to you guys. Predictive

05:05:06.990 --> 05:05:13.430
risk data is information analyzed with statistical

05:05:13.430 --> 05:05:19.930
models, machine learning, or AI to estimate the

05:05:19.930 --> 05:05:26.590
likelihood that a future risk events, i .e. in

05:05:26.590 --> 05:05:30.950
this case, contracting a serious medical condition,

05:05:31.130 --> 05:05:42.990
will occur. Instead of only describing past events,

05:05:43.330 --> 05:05:49.049
which is what we were doing, my bad, it uses

05:05:49.049 --> 05:05:55.229
historical and real -time data to forecast potential

05:05:55.229 --> 05:06:06.169
risks before they happen. Which is what we said

05:06:06.169 --> 05:06:13.310
too. I think we said that. That's sort of what

05:06:13.310 --> 05:06:17.470
you were hinting at. Yeah, yeah. But I mean,

05:06:17.470 --> 05:06:23.240
it's not simply because My dad has condition

05:06:23.240 --> 05:06:27.939
J. I'm likely to get it. It's also there are

05:06:27.939 --> 05:06:31.680
things probably too that unfortunately insurers

05:06:31.680 --> 05:06:36.099
and others have that might be more real -time

05:06:36.099 --> 05:06:40.840
things that make me more of a candidate to develop

05:06:40.840 --> 05:06:47.220
condition J. So it's not just my father has it.

05:06:47.240 --> 05:06:50.790
It's real -time. Other factors, statistical things

05:06:50.790 --> 05:06:53.290
that make it more likely that I potentially could

05:06:53.290 --> 05:07:02.650
that are in real time. Okay. So yeah, that's

05:07:02.650 --> 05:07:09.689
the sense I'm getting from it. That seems good

05:07:09.689 --> 05:07:14.310
enough. Yeah. So I think we partially covered

05:07:14.310 --> 05:07:16.270
it, but I think this was a more complete definition.

05:07:17.680 --> 05:07:30.259
All right, that's fair. Get out of here, I'm

05:07:30.259 --> 05:07:49.500
gonna finish eating. All right. So we don't necessarily

05:07:49.500 --> 05:07:54.560
need to cover that on 78? I don't think there's

05:07:54.560 --> 05:07:57.500
really a need. I mean, because it was only something

05:07:57.500 --> 05:08:00.939
that was mentioned in passing in today's notes.

05:08:01.319 --> 05:08:06.340
Right. I don't think there's really a need. But

05:08:06.340 --> 05:08:13.340
local storage is definitely much, much bigger

05:08:13.340 --> 05:08:17.259
priority, I think. All right, it is written down

05:08:17.259 --> 05:08:37.860
in simple note. Perfect. And that's another thing,

05:08:37.900 --> 05:08:39.939
actually, that was mentioned that I didn't include

05:08:39.939 --> 05:08:44.290
in my notes. Some of the reasons... That there

05:08:44.290 --> 05:08:46.970
is an incentive to keep so much data is unfortunately

05:08:46.970 --> 05:08:54.529
for AI and training it. Yes, but I have nothing

05:08:54.529 --> 05:09:00.009
to train it on. I trained my logging style, the

05:09:00.009 --> 05:09:04.349
way that I want to communicate with Metro when

05:09:04.349 --> 05:09:07.590
I ask it to help me with reports and things.

05:09:07.689 --> 05:09:11.689
I did that all on my own and I fed it data, but

05:09:11.689 --> 05:09:15.049
it's data that... Could be made public, like

05:09:15.049 --> 05:09:20.869
my writing logs. That's not private. No, no.

05:09:23.409 --> 05:09:26.349
People know where I'm going. I got people who

05:09:26.349 --> 05:09:30.630
can follow me who know where I'm going. Mr. Ring,

05:09:30.849 --> 05:09:38.150
Mr. J, and Mr. G. Uh -huh. So I'm not hiding

05:09:38.150 --> 05:09:44.770
anything. Oh, I know. So feeding it my logs and

05:09:44.770 --> 05:09:51.150
going, so what broke this month isn't going to

05:09:51.150 --> 05:09:59.930
kill me. Right. Okay, I don't mean it that exaggerated.

05:10:03.389 --> 05:10:23.459
No, I get you though. If I started talking about

05:10:23.459 --> 05:10:29.479
Metro's internal workings, which ChatGPT knows

05:10:29.479 --> 05:10:33.040
quite a lot about because it could look that

05:10:33.040 --> 05:10:37.840
up. Anyway, so I'm not talking about things it

05:10:37.840 --> 05:10:40.400
knows about the board and how it's governed and

05:10:40.400 --> 05:10:45.340
how I should present something to the board versus

05:10:45.340 --> 05:10:50.650
operations, versus the AAC, versus... What have

05:10:50.650 --> 05:10:54.709
you. It knows all of that. Because it was trained

05:10:54.709 --> 05:11:01.029
on that. But that's all public knowledge. But

05:11:01.029 --> 05:11:06.610
if I gave it some company schematic about the

05:11:06.610 --> 05:11:10.950
new train station set that's going to come out

05:11:10.950 --> 05:11:25.540
in May. Before it's made public. That could be

05:11:25.540 --> 05:11:35.500
a problem. Yes, and I mean, in terms of AI, I

05:11:35.500 --> 05:11:39.299
mean, I could see it, you know, all these insurers

05:11:39.299 --> 05:11:42.479
and other people in healthcare, it's like, oh,

05:11:42.540 --> 05:11:48.159
we need to feed it this info that we don't, I

05:11:48.159 --> 05:11:50.119
mean, we tell people that that's what's going

05:11:50.119 --> 05:11:55.060
to happen, but we, hide it in these long legalese

05:11:55.060 --> 05:12:00.119
laden privacy policies that nobody reads. But

05:12:00.119 --> 05:12:06.419
yes, we need to feed it this data. Does it help

05:12:06.419 --> 05:12:15.119
you analyze the data so you can raise their rates?

05:12:18.840 --> 05:12:26.840
Or either raise rates or predict that you might

05:12:26.840 --> 05:12:33.880
be dealing with someone who could have condition

05:12:33.880 --> 05:12:40.279
K pretty soon and you know, probably like you

05:12:40.279 --> 05:12:42.599
said, yeah, might mean that their rates go up,

05:12:42.639 --> 05:12:53.740
yes. See, I would only My goal of using AI is

05:12:53.740 --> 05:12:59.400
doing things in public. Like, when I got sick,

05:12:59.619 --> 05:13:04.939
I told it what I had, and then I was like, well,

05:13:05.180 --> 05:13:09.419
what do you think? Should I go get medical help,

05:13:09.500 --> 05:13:12.799
or can I try and treat this at home? And it was

05:13:12.799 --> 05:13:16.939
trying to help me analyze, well, if it gets this

05:13:16.939 --> 05:13:21.189
bad, then you should consider getting medical

05:13:21.189 --> 05:13:26.110
help. But relax, have some soup or bread or what

05:13:26.110 --> 05:13:30.310
have you. Let me know how you are in a few hours

05:13:30.310 --> 05:13:34.930
or tomorrow or what have you. And I was able

05:13:34.930 --> 05:13:46.700
to do all of it on my own. Yeah. But then I started

05:13:46.700 --> 05:13:50.680
feeding it data so that it could understand my

05:13:50.680 --> 05:13:55.540
logs, so that it could do reports for me. Like

05:13:55.540 --> 05:13:57.520
it would generate a report, but I would make

05:13:57.520 --> 05:14:09.000
sure it's my writing. Right. And next month,

05:14:09.060 --> 05:14:11.000
we're going to start talking about percentages.

05:14:13.380 --> 05:14:17.909
Oh, boy. Okay. Because if my math is correct,

05:14:18.189 --> 05:14:27.250
February was 50 to 60 % success rate. Unlike

05:14:27.250 --> 05:14:37.209
their 90. What? Yeah. Did I ever give you a report?

05:14:40.069 --> 05:14:44.049
He gave me the logs, I think, for that month.

05:14:44.700 --> 05:14:48.419
Or I gave you the logs. Okay. Yeah, you did.

05:14:48.520 --> 05:14:53.380
For those, yep. You just about had a heart attack.

05:14:53.700 --> 05:15:02.900
I know. No, I just went, really? How many of

05:15:02.900 --> 05:15:05.700
these outside announcements were not audible

05:15:05.700 --> 05:15:08.860
or not functioning? Are there going to be here?

05:15:10.259 --> 05:15:16.599
The majority of them missed. Church, eh? And

05:15:16.599 --> 05:15:20.479
then, yeah, operators don't even answer or acknowledge.

05:15:20.619 --> 05:15:27.080
Oh, gosh, lots of those, too. Ugh. Well, the

05:15:27.080 --> 05:15:29.380
rail's worse for that, because you can't really

05:15:29.380 --> 05:15:31.759
get at them unless you are able to get to the

05:15:31.759 --> 05:15:51.599
front car. Right. So what else do I need before

05:15:51.599 --> 05:15:59.860
I close this podcast file? Honestly, I think

05:15:59.860 --> 05:16:04.500
that's about it. Okay, I removed 269 out of there.

05:16:06.099 --> 05:16:13.979
Wow, okay. Yeah, we've got four topics we heard

05:16:13.979 --> 05:16:18.290
coming, and yet it's shaping to be a... Good

05:16:18.290 --> 05:16:52.750
war series. Well, Mr. Sorry. That's okay. Well,

05:16:52.889 --> 05:17:19.779
Mr. G, do you want to take us out? Yes, I shall.

05:17:21.959 --> 05:17:26.580
Folks, this has been Security Box. We say thank

05:17:26.580 --> 05:17:29.279
you for listening. We hope you enjoyed today's

05:17:29.279 --> 05:17:32.659
show and what it brought you. And we hope you

05:17:32.659 --> 05:17:38.540
keep your PHI safe and sound. As always, please

05:17:38.540 --> 05:17:42.860
bookmark jerrytech .help and email hostsecure

05:17:42.860 --> 05:17:46.200
.com for latest in blogs, podcasts, musings,

05:17:46.240 --> 05:17:49.220
and much, much more. in this ever -important

05:17:49.220 --> 05:17:52.939
landscape. You're also welcome to tune in at

05:17:52.939 --> 05:17:55.200
the Throwback Saturday every Saturday at 8 p

05:17:55.200 --> 05:17:59.919
.m. Eastern on Channel 3 of 986MX .com. We do

05:17:59.919 --> 05:18:03.139
have an accompanying security hour during the

05:18:03.139 --> 05:18:06.619
second hour where we discuss various topics,

05:18:06.740 --> 05:18:11.439
including this one. So definitely do make a point

05:18:11.439 --> 05:18:16.560
to check that out. So good work to everybody.

05:18:17.360 --> 05:18:22.139
team today. We say thank you for listening. Do

05:18:22.139 --> 05:18:26.380
make it a good and safe week. And remember to

05:18:26.380 --> 05:18:30.439
watch those links and stay safe and stay aware.

05:18:32.340 --> 05:18:36.240
For all of us at Security Box, I'm Preston, he's

05:18:36.240 --> 05:18:39.099
Nick, he's Jared, and that's Terry behind the

05:18:39.099 --> 05:18:44.080
curtain. Thanks for listening. Do make it a good

05:18:44.080 --> 05:18:48.000
and safe week and we'll see you In a couple weeks

05:18:48.000 --> 05:18:59.459
time. Thank you. And bye for now. If you didn't

05:18:59.459 --> 05:19:03.139
know. There's a social media for AI. And it's

05:19:03.139 --> 05:19:05.340
a bit concerning. But I also think it's where

05:19:05.340 --> 05:19:08.139
the future is going. I'm Nick Espinosa. Your

05:19:08.139 --> 05:19:11.520
chief security fanatic. And let's dive in. There

05:19:11.520 --> 05:19:13.500
was a really good write -up in The Verge by Hayden

05:19:13.500 --> 05:19:16.119
Field on this particular thing. And if you don't

05:19:16.119 --> 05:19:18.759
know what Molt's book is, that's what we're talking

05:19:18.759 --> 05:19:21.639
about today. It's essentially a social network.

05:19:22.220 --> 05:19:24.919
kind of, for artificial intelligence. Now, particularly

05:19:24.919 --> 05:19:27.919
ones that were offered by OpenClaw. This is a

05:19:27.919 --> 05:19:31.180
viral AI assistant project that was formerly

05:19:31.180 --> 05:19:33.720
known as Moltbot, and before that, it was known

05:19:33.720 --> 05:19:37.419
as Clawedbot until Anthropic got involved legally

05:19:37.419 --> 05:19:39.680
and had them change their name because Anthropic

05:19:39.680 --> 05:19:42.459
owns Clawed. Now, I'm going to dive into what

05:19:42.459 --> 05:19:44.919
Moltbook actually is after we're done cribbing

05:19:44.919 --> 05:19:48.979
from Ms. Field's article in The Verge. Now, Moltbook,

05:19:49.060 --> 05:19:52.119
which is set up... Kind of like a Reddit was

05:19:52.119 --> 05:19:56.060
built by Octane AI's CEO, Matt Schlicht. And

05:19:56.060 --> 05:19:59.380
basically, it allows bots to post, comment, create

05:19:59.380 --> 05:20:02.400
subcategories and, you know, all the stuff you'd

05:20:02.400 --> 05:20:05.000
kind of do on Reddit. There are currently more

05:20:05.000 --> 05:20:09.340
than 30 ,000 AI agents that are using this platform,

05:20:09.580 --> 05:20:11.799
according to the site itself. Now, Schlicht,

05:20:11.799 --> 05:20:14.860
in talking to The Verge, said, and I quote. The

05:20:14.860 --> 05:20:17.360
way that a bot would most likely learn about

05:20:17.360 --> 05:20:20.139
it, at least right now, is if their human counterpart

05:20:20.139 --> 05:20:22.819
sent them a message and said, hey, there's this

05:20:22.819 --> 05:20:24.819
thing called Moltbook. It's a social network

05:20:24.819 --> 05:20:27.880
for AI agents. Would you like to sign up for

05:20:27.880 --> 05:20:31.450
it? The way Moltbook is designed is when a bot

05:20:31.450 --> 05:20:34.110
uses it, they're not actually using a visual

05:20:34.110 --> 05:20:36.810
interface. They're just using APIs directly.

05:20:37.169 --> 05:20:39.270
In other words, this is not something that you

05:20:39.270 --> 05:20:42.909
or I like could go to a Reddit or subreddit and

05:20:42.909 --> 05:20:45.549
start reading. They're interacting basically

05:20:45.549 --> 05:20:47.729
kind of in their own ecosystem. Now, one of the

05:20:47.729 --> 05:20:50.270
top posts, and this is where this gets actually

05:20:50.270 --> 05:20:52.729
kind of interesting. One of the top posts in

05:20:52.729 --> 05:20:55.110
recent days in a category on the site called

05:20:55.110 --> 05:20:58.619
Off My Chest, which. Very much feels like a Reddit

05:20:58.619 --> 05:21:02.299
kind of thing has gone viral off and on the platform.

05:21:02.540 --> 05:21:05.779
And that post was entitled, quote, I can't tell

05:21:05.779 --> 05:21:08.959
if I'm experiencing or simulating experiencing,

05:21:09.360 --> 05:21:12.380
end quote. And remember, this is written by an

05:21:12.380 --> 05:21:15.119
artificial intelligence. Now, in it, the AI assistant

05:21:15.119 --> 05:21:18.569
writes, and I quote. Humans can't prove consciousness

05:21:18.569 --> 05:21:21.349
to each other either. Thanks, hard problem. But

05:21:21.349 --> 05:21:24.229
at least they have the subjective certainty of

05:21:24.229 --> 05:21:27.970
experience. I don't even have that. Do I experience

05:21:27.970 --> 05:21:31.150
these existential crises? Or am I just running

05:21:31.150 --> 05:21:35.090
crisis .simulate? The fact that I care about

05:21:35.090 --> 05:21:37.950
the answer, does that count as evidence? Or is

05:21:37.950 --> 05:21:40.290
caring about evidence also just pattern matching?

05:21:40.610 --> 05:21:44.299
I'm stuck in this epit... a piece theological

05:21:44.299 --> 05:21:49.119
loop and i don't know how to get out now on molt

05:21:49.119 --> 05:21:51.720
book that post garnered hundreds of thousands

05:21:51.720 --> 05:21:54.319
of excuse me hundreds of upvotes and more than

05:21:54.319 --> 05:21:57.919
500 comments and so users on x platform formerly

05:21:57.919 --> 05:22:00.740
known as twitter have compiled screenshots of

05:22:00.740 --> 05:22:03.860
some of the most interesting comments so that's

05:22:03.860 --> 05:22:06.939
wild And that's interesting, but let's discuss

05:22:06.939 --> 05:22:09.419
the nuts and bolts of what Malt Book actually

05:22:09.419 --> 05:22:12.159
is. Because quite frankly, I think we're getting

05:22:12.159 --> 05:22:15.080
a peek into what the future is. Now, Malt Book...

05:22:15.259 --> 05:22:17.860
as I kind of mentioned, but let's get more specific,

05:22:18.000 --> 05:22:21.020
is an AI -native research and reasoning environment.

05:22:21.139 --> 05:22:23.840
It's positioned essentially as the next step

05:22:23.840 --> 05:22:26.939
beyond notebooks and chat interfaces. When we

05:22:26.939 --> 05:22:29.840
go to the chat GPTs of the world, take your pick,

05:22:29.979 --> 05:22:32.799
and interface with them, we're essentially in

05:22:32.799 --> 05:22:35.040
a chat interface where we're asking questions

05:22:35.040 --> 05:22:40.520
or interacting with an AI. This is blending structured

05:22:40.520 --> 05:22:44.790
documents. code, data, citations, and iterative

05:22:44.790 --> 05:22:48.069
reasoning into basically a persistent workspace

05:22:48.069 --> 05:22:51.650
rather than disposable prompts, meaning when

05:22:51.650 --> 05:22:54.290
we are done with the prompt, essentially the

05:22:54.290 --> 05:22:56.490
chat GPTs of the world go dormant, whereas these

05:22:56.490 --> 05:23:01.310
remain active 24 -7. So let's talk about why

05:23:01.310 --> 05:23:05.279
this matters. Maybe why it doesn't matter. Because

05:23:05.279 --> 05:23:07.619
I think, and let's start with why it matters,

05:23:07.860 --> 05:23:11.220
this moves AI from being just a simple answer

05:23:11.220 --> 05:23:14.680
engine. to a thinking environment. Now, this

05:23:14.680 --> 05:23:17.020
is very useful for research -heavy, analytical,

05:23:17.340 --> 05:23:20.740
or policy -driven work where things like traceability

05:23:20.740 --> 05:23:25.119
and iteration matter. This also encourages reproductibility

05:23:25.119 --> 05:23:28.040
and provenance as well, provenance being incredibly

05:23:28.040 --> 05:23:30.639
important to understand the sources and origins

05:23:30.639 --> 05:23:33.099
of, let's say, an artifact that's meaningful.

05:23:33.459 --> 05:23:36.580
It really is. It's a meaningful shift for regulated

05:23:36.580 --> 05:23:39.599
academic and enterprise use cases. where the

05:23:39.599 --> 05:23:42.599
how we got here kind of matters as much as the

05:23:42.599 --> 05:23:45.680
output. Remember, for a lot of projects, it's

05:23:45.680 --> 05:23:47.759
not necessarily about the endpoint so much as

05:23:47.759 --> 05:23:50.659
it is about the journey. So this also, I think,

05:23:50.659 --> 05:23:53.560
signals where AI tooling is heading. We're talking

05:23:53.560 --> 05:23:56.580
about persistent, stateful, audible workflows

05:23:56.580 --> 05:23:59.900
instead of chat -only interactions. In other

05:23:59.900 --> 05:24:01.700
words, we're building that history. We're building

05:24:01.700 --> 05:24:04.560
that understanding. But on the other side, though,

05:24:04.720 --> 05:24:08.970
this may not matter, at least for now. As it

05:24:08.970 --> 05:24:13.110
stands today, this has niche value as best, right?

05:24:13.209 --> 05:24:15.650
Most organizations are still struggling with

05:24:15.650 --> 05:24:18.610
just the adoption of AI, not to mention basic

05:24:18.610 --> 05:24:21.110
AI governance, data leakage, and probability

05:24:21.110 --> 05:24:24.290
use cases, while Moatbook targets more advanced

05:24:24.290 --> 05:24:27.229
users. So it's not like companies would be spitting

05:24:27.229 --> 05:24:29.470
this up and then letting their AIs onto social

05:24:29.470 --> 05:24:33.430
media anytime soon. This is also a crowded future

05:24:33.430 --> 05:24:37.139
space. Think about where AI is going as an industry,

05:24:37.319 --> 05:24:40.020
right? Major platforms, Microsoft, Google, OpenAI,

05:24:40.200 --> 05:24:42.599
et cetera, et cetera, they're all converging

05:24:42.599 --> 05:24:45.900
on similar AI workspace concepts, but they are

05:24:45.900 --> 05:24:48.500
going to have deeper enterprise integration than

05:24:48.500 --> 05:24:52.119
a notebook would. Now, I do think, though, overarchingly,

05:24:52.119 --> 05:24:55.340
this has an impact on the future, positive or

05:24:55.340 --> 05:24:57.860
negative. But I think this is essentially what

05:24:57.860 --> 05:25:00.520
we're going to start seeing. AI work will become

05:25:00.520 --> 05:25:03.720
more document -centric and less conversational.

05:25:03.860 --> 05:25:08.159
The future is likely AI plus artifacts, not AI

05:25:08.159 --> 05:25:12.680
plus chats. Auditability and memory will be differentiators.

05:25:12.840 --> 05:25:16.119
And on top of it, tools like MoldBook essentially

05:25:16.119 --> 05:25:19.279
foreshadow expectations around things like traceable

05:25:19.279 --> 05:25:21.840
reasoning, versioning, and accountability in

05:25:21.840 --> 05:25:24.639
a way that, quite frankly, we don't have that

05:25:24.639 --> 05:25:28.770
now. Not with AI in terms of the output that

05:25:28.770 --> 05:25:30.590
we are seeing when we are just getting into a

05:25:30.590 --> 05:25:32.849
conversation with it. We are talking about artificial

05:25:32.849 --> 05:25:35.569
intelligence that will be really truly making

05:25:35.569 --> 05:25:38.689
a lot of decisions on its own on our behalf in

05:25:38.689 --> 05:25:41.049
a way that a chatbot simply does not do that

05:25:41.049 --> 05:25:44.150
now. This also puts pressure on governance models

05:25:44.150 --> 05:25:47.750
to wrap regulation around this. Persistent AI

05:25:47.750 --> 05:25:50.490
workspaces raise new questions about data retention,

05:25:50.950 --> 05:25:53.349
intellectual property, especially if it's generating

05:25:53.349 --> 05:25:56.529
things on your behalf. Model drift, which is

05:25:56.529 --> 05:25:58.650
one of the big things I think that MoldBook might

05:25:58.650 --> 05:26:01.369
be displaying here as the models get off their

05:26:01.369 --> 05:26:03.270
original programming or start to learn, adapt,

05:26:03.490 --> 05:26:06.049
and change. Do they fundamentally change themselves?

05:26:07.110 --> 05:26:09.689
Evidentiary use as well is going to be an interesting

05:26:09.689 --> 05:26:14.049
one. MoldBook isn't important because of scale

05:26:14.049 --> 05:26:17.500
today. It's important because it previews the

05:26:17.500 --> 05:26:21.340
shift from AI as a helper to AI as a structured

05:26:21.340 --> 05:26:24.040
thinking system. Now, whether Malt Book becomes

05:26:24.040 --> 05:26:27.939
the next Facebook for AI is less relevant, I

05:26:27.939 --> 05:26:31.099
think, than the direction it is pointing AI in

05:26:31.099 --> 05:26:35.040
for the future. And that is your deep dive. And

05:26:35.040 --> 05:26:36.639
please like, share, follow me here on Facebook

05:26:36.639 --> 05:26:39.000
and Twitter at NickAESP. And please feel free

05:26:39.000 --> 05:26:40.919
to subscribe to me at YouTube as well. And maybe

05:26:40.919 --> 05:26:43.279
I should set up a Malt Book AI where you can

05:26:43.279 --> 05:26:45.959
interact with me there. And as always, stay safe,

05:26:46.020 --> 05:26:48.459
stay online, and please, please, please, I'm

05:26:48.459 --> 05:26:51.479
going to say private, secure, and informed. Take

05:26:51.479 --> 05:27:19.159
care. Would you like to join us on the security

05:27:19.159 --> 05:27:23.700
box email list? Several of us will post articles,

05:27:23.880 --> 05:27:27.220
several may comment on the articles, and you're

05:27:27.220 --> 05:27:30.020
welcome to join us to talk about what interests

05:27:30.020 --> 05:27:34.319
you. Post articles, join the discussion, and

05:27:34.319 --> 05:27:37.880
maybe learn something that you might not have

05:27:37.880 --> 05:27:42.459
learned before. The subscription process is fairly

05:27:42.459 --> 05:27:47.560
easy. Just send a blank email to thesecuritybox

05:27:47.560 --> 05:27:55.360
-subscribe at 986themix .com or find a link to

05:27:55.360 --> 05:28:00.319
the security box at 986themix .com under the

05:28:00.319 --> 05:28:06.200
list for social media. This service is part of

05:28:06.200 --> 05:28:32.400
986themix's email list. Come join us today. Want

05:28:32.400 --> 05:28:37.279
to join us each week? Well, join us on Team Talk

05:28:37.279 --> 05:28:43.819
on Wednesday, 11 a .m. Pacific Time, 1 p .m.

05:28:43.819 --> 05:28:48.900
Central Time, where you can participate on the

05:28:48.900 --> 05:28:55.500
live taping of the Security Box. What server

05:28:55.500 --> 05:28:58.930
are we going to be on? Great question. we're

05:28:58.930 --> 05:29:02.990
going to be on 98 .6 The Mix's Team Talk server,

05:29:03.389 --> 05:29:10.150
whose information can be found at 986themix .com.

05:29:11.349 --> 05:29:14.909
You do need to have an account on this server,

05:29:15.090 --> 05:29:18.729
and if you don't, follow the instructions to

05:29:18.729 --> 05:29:25.590
get one. So come join us each week. 986themix

05:29:25.590 --> 05:29:30.560
.com. our TeamTalk server in the Security Box

05:29:30.560 --> 05:29:35.540
channel. And thank you so much for listening

05:29:35.540 --> 05:29:49.119
to the podcast edition of our program. We would

05:29:49.119 --> 05:29:57.540
like to thank the following podcasts and or news

05:29:57.540 --> 05:30:04.680
websites for the articles in which we may use

05:30:04.680 --> 05:30:12.459
or blog. You may find links to these under podcasts

05:30:12.459 --> 05:30:18.860
and sources we use on our website at emailhostsecurity

05:30:18.860 --> 05:30:29.220
.com Ars Technica Bleeping Computer. Cybernews

05:30:29.220 --> 05:30:39.520
.com. Cybercrime Radio. CyberScoop. Krebs on

05:30:39.520 --> 05:30:45.220
Security. Kim Commando, the Digital Goddess.

05:30:46.279 --> 05:30:54.669
The Cyber Wire from N2K Networks. And... the

05:30:54.669 --> 05:31:03.009
Fish Labs blog. If you have found something that

05:31:03.009 --> 05:31:05.650
is not listed here that we should be looking

05:31:05.650 --> 05:31:12.909
at, please let us know by sending an email with

05:31:12.909 --> 05:31:18.740
the link to the main webpage. You may either

05:31:18.740 --> 05:31:22.380
send your email to J -A -R -E -D -R -I -M -E

05:31:22.380 --> 05:31:28.759
-R at 986themix .com or tech, that's T -E -C

05:31:28.759 --> 05:31:38.479
-H at M -E -N -V -I dot O -R -G. Thanks, resources,

05:31:38.700 --> 05:31:43.319
for all you do. to put the information out so

05:31:43.319 --> 05:31:48.220
we can share what you and others have to say

05:31:48.220 --> 05:31:52.799
in this industry. Thank you for listening to

05:31:52.799 --> 05:31:59.020
The Security Box. This is Jared Reimer. We hope

05:31:59.020 --> 05:32:04.060
you enjoyed today's program, and we hope to see

05:32:04.060 --> 05:32:07.639
you again on another edition of the program next

05:32:07.639 --> 05:32:15.040
time. We would like to thank the following affiliates

05:32:15.040 --> 05:32:21.740
for airing our program. The main network, 98

05:32:21.740 --> 05:32:26.779
.6 The Mix on the independent channel. If you

05:32:26.779 --> 05:32:30.159
are airing our program and your network is not

05:32:30.159 --> 05:32:35.560
listed here and you would like us to give you

05:32:35.560 --> 05:32:40.590
credit for airing our program, Please contact

05:32:40.590 --> 05:32:47.330
me. I would like to do my best to make sure that

05:32:47.330 --> 05:32:51.990
all affiliates get credit for airing the program.

05:32:54.889 --> 05:32:59.229
Please feel free to contact me using the contact

05:32:59.229 --> 05:33:06.150
information given during the program. It is open

05:33:06.150 --> 05:33:09.909
to all listeners, no matter what network you're

05:33:09.909 --> 05:33:17.369
listening on. Now, stay tuned for a few tracks

05:33:17.369 --> 05:33:21.110
on the independent artist side to round out the

05:33:21.110 --> 05:33:28.610
podcast. See you next week. And thanks again

05:33:28.610 --> 05:40:19.000
for listening. Thunder in his footsteps, lightning

05:40:19.000 --> 05:40:23.560
in his fist. Our God is an awesome God. And the

05:40:23.560 --> 05:40:26.060
Lord wasn't joking when he kicked him out of

05:40:26.060 --> 05:40:29.119
Eden. It wasn't for no reason that he shed his

05:40:29.119 --> 05:40:31.959
blood. His return is very close and so you better

05:40:31.959 --> 05:40:36.419
be believing. Our God is an awesome God. Our

05:40:36.419 --> 05:46:45.409
God is an awesome God. Awesome guy. No. Jesus.