The opinions expressed are those of the show
hosts and may not necessarily be of any company
in which the show hosts may represent. The following
podcast may contain some strong language. Parental
discretion is advised. Podcast 269 of the Security
Box. PHI and our personal information. Why can't
companies keep it secure? Recorded Wednesday,
March 11th, 2026. Hello, folks. Welcome to TSB
Program 269. I'm Jared Reimer. It's Wednesday,
March 11th, 2026. And it feels pretty good to
be back. But I think the Gremlins are still in...
the computer because we definitely had at least
one issue our files today are scams and how they've
evolved scams in your inbox Questions to ask
that can thwart scams. And to add insults to
injury. Social network for AI is a bit concerning
will be our video for today. Our topic is going
to be... PHI, and our personal information. And
this definitely has to have its whole segment
on its own. That Is where we are Hopefully By
next time The Gremlins will be completely Will
be out of our computer. And we will redo. The
scam segments. Next time. So that everybody can
hear. The entire thing. I just don't have time
to redo. The second file. Right now. So. Let's.
Go ahead and push some buttons because our topic
on PHI is going to be our longest segment to
date. And a little over three hours. in length.
So, I will see everybody next time when we talk
about hallucinations and AI. Till then, see you
next time. number 269. Yes, it's a week after
we probably normally do this program, but this
computer needed help. Seriously, needed help.
And then I'm still not really set up. Because
we're still just playing random material on the
independent channel. But we're going to push
forward and get automation eventually back up
and running the way it should be. Mr. J is on
Team Talk with me. Yep. And this is going to
get very interesting. No kidding. So, we're going
to start off with a little bit of phone line
news. So, today is Wednesday, March 11th. Around
the night, one of my buddies tells me about something
that a caller posted on the bashing board. And
this may be a little sexual, but maybe this goes...
into the category of the stupid fuck award Mr.
J uh oh so a guy goes somewhere and we'll tell
you where in a minute and apparently he was there
for a specific reason this time We'll tell you
about that too. Well, apparently he was sitting
down supposedly minding his own business when
he calls into Livewire. And he happens to post
in a lower than normal voice. If this particular
guy gets pussy. Now that wouldn't be so bad.
Except two things went wrong for him. The place
where he was at and the consequences Uh -oh.
Oh, no. So... Unbeknownst to me, but not surprising
to me... I guess you're... Local church? Hands
out food to people who need it, including disabled?
That's, I mean, some churches, I think, probably
have initiatives like that. So I'm not that surprised,
but I think I know where this is going. So he
was there. At this church. Oh, what an absolute
idiot. He was at this church. And he thought
he was quiet enough. Until... The bishop's wife
and apparently his daughter either heard it or
were around. And he was basically pulled into
the office and said, if you do that, Again, it'll
be a two -month ban from coming here. As it should
be. But something tells me that if this guy is
so willing to do this in a freaking place that's
this public. There are other issues going on.
That's my guess. Well, he has talked about publicly
how short it is, how he can't get it up, and
How he's still a virgin. Um... In his 50s, Mr.
J. Uh... Just... I don't know what to say. I
really... We actually talked to him about phone
etiquette and other things at one point. And
apparently he just doesn't get it. He got thrown
out of where we are. And then this. Oh my gosh.
And every time I say I think I heard it all.
I hear something completely different. I know
we've all made mistakes before. And some of us
have gotten into legal trouble and learned our
lesson. Some of us may have not learned our lesson
and may still be in legal trouble. Here's the
thing. But this guy is beyond help. That's what
I was about to say. I don't think that was a
mistake. I don't think that was a mistake. You
think he intentionally did that not knowing that
ears were possibly around. That could get him
in trouble for that. Right. Okay. Here comes
Terry. Oh, boy. Terry Ring, welcome to T -S -B.
T -S -B. So, a stupid fuck award, Mr. Ring. There's
a guy... Who went somewhere to get food. And
happened to get on the phone line to post on
board two over on Livewire. And apparently he
was asking one of the guys whether he got any
pussy. And it wouldn't be so bad. Except for
two things. Where he was and his consequence
if he ever did that again. Uh -oh. That's the
second reaction. That's the second reaction I
got out of them. Because that was Nick's reaction
the first time he heard that. Where was he? Where
was he? He was apparently at a church where the
bishop's wife and his daughter we don't know
how old the daughter is. We don't know anything.
Right. Heard that. And he got pulled in the office
and was told if he ever did that again A two
-month suspension of coming back to get food.
Oh, so it was one of those church things where
he went and got free food from the church. And
he just said that and the bishop and his daughter,
oh my God. The bishop's wife. Oh, the bishop's
wife heard it. Oh, shit. He's probably like,
what? Uh -huh. I know I've told some of you what
I was interested in, but could you, I guess now
that two of you are here, could you imagine me
asking whatever it would be that I would want?
In a church. No. I couldn't. And would you come
down here and kick my ass? Yeah, I mean, that's...
Yeah, that... I mean, I accidentally swore one
time in a church, but that was by mistake. Okay,
but... You know, obviously I got reprimanded
for it, but, you know. I got reprimanded on a
phone line when I swore, and then one of the
other people wanted to start with me and said,
I already heard. You don't need to tell me, too.
I already got reprimanded. That's not necessary.
No. But this guy, your response was the same
response Nick gave me at the beginning of the
program. Yep. A church of all things. I mean,
that's just like... And given this guy's pattern,
he is going to do it again. I can predict it.
I would have told him to leave right then and
been like, dude, you need to go. I would have
not even said, do that again, you get six months.
I told them on Livewire, I said I would have
just kicked his happy ass right out of here and
said, you don't come back here. Exactly. Uh,
I mean, he could have asked it a little bit different
to where it wouldn't be as offensive. There's
no way to ask that in a way that's not offensive,
Terry. I mean... You could say the word sex.
I mean, that's not really... too offensive. I
mean, that's not... That's... But you're still
in church. Well, okay, and then the whole sex
before marriage comes up. I get that. I get that.
Well, no, but that's not even something you should
be talking about in that public place. No, you
shouldn't. Especially in that environment. You
shouldn't, but people don't think. Or you should
have waited until at least you got outside and
got to your car and been like, hey, you know.
You shouldn't. Something like that. At least
you're in your car or something. No, you should
wait until you're home. Yeah, or that. Or that,
yeah. Because, you know, if this is somebody
who relies on, you know, paratransit or something,
I don't know what his situation is. And, you
know, you want to talk about a really bad twist
if it's a female who's driving him. Yeah. Yeah,
I mean, paratransit, I could see. Yeah, I could
see. But, I mean, if you're driving yourself
and it's just you in the car, then okay. I can
already tell you that that's not going to happen,
Terry, because he's disabled. Oh, okay. So then,
yeah, okay. So then that's out of the question.
So it's more likely that what I'm suggesting
is probably closer. Yeah. It's more like, yeah,
yeah, yeah. An Uber, Lyft, or anything. Yeah,
I would wait till I get home and say something
and then ask. Yeah, I would just imagine it's
like, you know, the driver overhears that and,
I mean, they hear a lot of shit. I get that.
But they overhear that. It's like, um... What
did you just say? And especially if the driver's,
like, really religious, he probably said, get
out of my car, man. Like, just go. Get. Like,
especially in an Uber car. Like, I don't want
anything to do with this. Out. No, they can't
do that to a disabled person. You could turn
around and say, that was my ride home. They'd
let me out, and I don't even know where I am.
They could be in a lot of trouble for that. Well,
here's what they could turn around and say, though.
He was saying words and making suggestions and
innuendos that I found very offensive and unsafe.
Your job is to drive. You can give him a bad
rating and refuse to pick him up the next time.
Oh, you can give him a bad rating on that trip,
yeah. Correct. I don't want to use this customer
anymore. If the customer does an Uber again,
it wouldn't show that driver anymore. But at
that point, he'd be looking at getting kicked
off the program if he kept it up. Uber's already
been under a lot of arrest because of safety.
Correct. It's been sued multiple times. Correct.
Mm -hmm. They don't want that on their conscience
either, I'm sure, so... paratransit, I don't
know if it's different. I don't know if they
could just... They can't legally do that either.
I mean, they could probably cancel you from the
program afterwards. You know. The driver can
turn you in and they could send you a letter
afterward, but they can't kick you out. No, but
that's what I'm saying is that they could be
kicked off the program. After the fact. Yeah.
What an idiot. Why would you like... That's probably
the only way he gets food. I'm not going to sit
there and... I'm just guessing, right? Maybe
he does buy his own food too, but I'm just guessing.
Why would you put that at risk if that's your
only source of getting food? I'm not saying it
is or isn't. Some people just don't care. I'm
not saying it is or isn't. But I wouldn't put
it at risk like that, especially if that was
my only source of food. No way. No way. I think
that gives us the stupid fuck award. At long
last, yes. He would get that, yes. At long last.
Yep, well said. I'm sorry. I'm sorry. I once
used their products and they're one of the best
in the business. They can protect you from all
kinds of threats and they can make sure that
you are not entering sensitive information in
places where you should not be. If you've entered
the information into the program, for example,
if you enter your credit card number, it knows
not to allow you to enter that information into
places like email or unsecured websites. They've
got products for home users and business users.
And they also have a product that can do a simple
scan as well. Their website is trendmicro .com.
There's also a link to them on our website at
emailhostsecurity .com. Select the resources
page and look in the companies and resources
section. All right, folks, let's go ahead and
check out the blog. And yes, I'm going to put
that up on the board because Michael did say.
Let me see what the group said. So I'll put that
up. Mr. Ring. Here we go with another I'm not
laughing article. Doge seems to be back half
a billion people may be at risk. Nice. If the
story that cyber news excuse me is true and the
gentleman who was never named Truly has God access
into the Social Security Administration. Even
while working for the Department of Government
Inefficiency. We're in trouble. You have to remember
that Doge has access from other articles to all
of that stuff. Well, we covered... That's what
I'm saying. We covered Doge. Yeah, we did. Ever
since its inception. But this... This is beyond
bad. Well, that's why I'm watching our governor's
race carefully because the person that's running
against our governor, Darren Bailey, he wants
to put a Doge -like system in for Illinois. I'm
like, oh, no. Oh, no. But if this is true, it's
not going to matter, Terry. No, I'm not saying
it's going to matter. I'm not saying it's going
to matter. We're talking about 500 million people.
Half a billion people. That's a lot of people.
And apparently he's only taken two databases,
which does include people who are living and
dead. And there were specific names of these
databases mentioned within the article, and ChatGPT
even knows about it. And it even referenced an
August 2025 cyber news article on the Department
of Public, I mean, Governmental Inefficiency.
It always loves when I tell it, gentlemen, that
we've covered it. And we've called the Department
of Government Efficiency the Department of Government
Inefficiency. It always seems to be amused about
that. I wonder how it would respond to my nickname
for Windows Defender. I haven't tried doing this
yet. Yes, Windows Offender. Which now I'm using
because I haven't gotten Malwarebytes reinstalled
yet. Fair enough. I mean, it's better than nothing,
I guess. Well, and as it says, it's a different
type of antivirus. It analyzes files when they're
ran, not when downloaded. Which is probably better
anyway because there could be false positives.
So if it's not emitting any problems, then you're
better off anyway. And we'll be talking about
this type of thing in a future program. Here
on TSB. And Mr. J. Mm -hmm. It's time to get
offended. Black Santa. Oh, yes. And by the way,
Cyber News does have a version of the article
that I picked up from the computer. Black Santa?
Of... Bleeping. Bleeping. Yes, Black Santa. Black
Santa. It's a new... Anyone care to guess what
kind of... I can't guess because I read it already
blogged. This is? It's... Right, you've read
it. It's something we've covered when it first
came out, Mr. Ring. And we said we probably weren't
going to see the end of it. And we were right.
And we were right. And this will be the third
time or so in the last year that this acronym
has been talked about in a bad way. Uh -huh.
It's an acronym. It stands for three words. Well,
technically four. Technically four. Yeah, technically.
One of the words is Not part of its acronym.
Right. The answer? Endpoint. Detection. And response.
Otherwise known as EDR killer. Killer. I hope
we don't get any of that. Well, we already are.
That's what we're saying. How about us personally?
I would get it more than you. Yeah. Right. Because
you're more known in the community. No. No, because
he runs a small business. Yeah. Isn't that what
they're targeting? I think that's what they target
most of these businesses, right? Right. Well,
this is HR departments. What this one's targeting
is known as HR departments. The human resources
department. Human resources, yeah. I am all of
it. So, I expect... I expect... Yeah. Let's see.
We've got zombie zip. Yeah. That concerns me
a little bit. I haven't read it yet, but it's
not understandable. It's a researcher who changed
the way zip files work, I guess. In regards to
the way that 50 out of 51 detection programs
on which major virus scanning website VirusTotal?
VirusTotal's correct. 50 out of 51 would allow
you to unzip these even though the headers didn't
match. That's kind of a little concerning. A
little? A little? Yeah, just a little. It's a
random yeah so one of us gets some dot zip and
you know and here's the scenario it could come
from one of us you know because maybe we've been
hit somehow and you know the rest of the staff
doesn't know and you know maybe one of us is
in a hurry it's like oh it's fairly important
i'll download it and you know they try to run
it through virus total oh it looks fine and then
of course you run it bang And then you're scrambling
to try to redo things because it just wiped whatever,
wiped your entire drive. It didn't say what it
did. I mean, that's in theory what it could do.
That's what I'm saying. That's a possibility.
That's why I said that. Find another computer.
Go get a drive that's not compromised. So make
an ISO and then you go. Yeah, that would be a
lot of work. So, Nick. Mm hmm. We haven't really
talked about this very much. And I'm talking
very specifically about IP version 6. Because
it is not really widely used. And if it is, it's
more of a background automatic thing, just like
you getting on the internet can be. Because now
we've got news about the ARPA TLD, which is mainly
used... to do DNS lookups. Well, it owned Google
in the IPv6 space. I'm not surprised. As much
trouble as Google has been in over the years,
I'm not surprised that they own them in that
space. I forget the exact details, but... Essentially
just corrupting this DNS lookup service. I mean,
that's how I understood it. I don't know if I
have this right either, to be honest. Essentially,
so if somebody makes one of these lookup requests
to something that looks... fraudulent or maybe
suspicious, you know, like a phishing domain,
it shows up as legit. Correct. That's the way
I understood it. Oh, so I did understand that
part. Yeah, that's the way I kind of understood
it. Yeah, so, you know, it's been hijacked so
that this, you know, shady -looking domain, you
know, AppleCare... AppleCareForMe .com for something
that's seen as a legitimate DNS address. Even
though it's a phishing site. But this is done
through IPv6, not 4. Just because it goes to
look up to look up the you know the details of
where this goes or what have you so I blogged
Mr. J's very interesting find from Saturday.
Yes. About another we don't know where the hell
all our data is company. Oh, another one of those.
This one's bad. It's only going to get worse,
I think. The first number we get... Wait, there's
two different stories. Which one am I talking
about here? I think I know the one you're talking
about. Yes, the first number we got for this
was 10 million. Yes. But that has since been
revised significantly upward. And we're now looking
at... 25 million and counting. Counting. Now,
does this sound to you like OPM in 15? I had
to be corrected. OPM was 2015, not 18. So, I
want to make that correction. We've been saying
OPM was 18, but it was actually 15. So, chat
GPT corrected me on that. So, I want to correct
the record of that right now. Okay. Because I've
been saying 18 for a while. But who thinks that
this is OPM all over again? In some ways. It's
similar. It's similar. I'm not saying it's exact.
Because it's telling me the difference. The chat
GPT told me the difference between the two. So
now I'm asking, do you guys think it's OPM again
in some ways? Yes. Go ahead. Well, yes, in terms
of the data that was involved, I think it's very
similar. Okay. Mm -hmm. And then I happened to
find one of my own in the Better Late Than Never
department. Yes. What was the name of this company?
UFP, I believe. medical devices. And up until
now, I have never heard of them. But yes, they've
gotten hit. I've never heard of them either.
OMP? UFP. I've never heard of them either. I
suspect that unfortunately this is going to be
updated and not in a good way. Because as of
now, the claim is that there is no evidence that
they have any personal information that's been
taken. I wouldn't be so sure about that. I was
going to say they don't have evidence. Exactly.
They don't have evidence yet. Yet. I can just
see bleeping in a few weeks or maybe a month
or so. UFP, medical device manufacturer breach,
worse than first thought, is probably what might
happen. And then a few of us are just going to
fall out of our chairs. So if you hear a... From
there, you'll know why. I think... Actually,
I think it's going to be different. I think a
few of us are just going to be like, yeah, what
else is new? We told you that was going to happen.
We did. That was broken. Terry, I'm going to
have to get you... A full version of this. I
actually just taped this morning the three segments
that are going to be part of today's program.
But segment two, I think got commandeered by
robots or something. I'm going to have to leave
it because I'm sort of pressed for time to get
the podcast out. But I am going to re -record
this into one segment for you, which will sound
a lot better than... The three. Because I was
just going to merge it, but knowing that the
second wasn't going to be all that great. But
I'm letting the podcast know that I'm releasing
it this way because while I could re -record
the second segment, I do have other commitments
tomorrow, so I want to try and get this out in
a reasonable time manner. Right. Sorry for any
robots. What we could do is re -air it again
when we schedule 270, either in two or three
weeks, depending on what the group would like
to do. So, I'll redo it for you. Probably on
Friday. And I guess Kim Commando put out something
recently. I don't think I heard it yet, but I
guess Korea has already been in our banks. Oh,
great. As part of her minute. Probably South
Korea again. They're always doing shit. I don't
know if it's South Korea or North Korea, but
I know that... It's more likely to be North.
I know that somebody's at war, and I've seen
bits and pieces of it on KNX. I refuse to read
it, because there's not a damn thing I can do
about it. Oh, no. I refuse to read. I would say
it's more likely that we're talking about the
North, not the South. I think you're right. The
U .S. is only a part of that war because of the
oil. That's why. Otherwise, they'd probably be
involved. Well, not if it involves North Korea,
no. We don't have oil reserves there that we
want. No, but where we are, there's oil reserves.
North Korea is the home of... North Korea is
where Lazarus is based. So, not surprising. If
this is the one we're talking about, they might
have been up to this. There's a couple things
going on. Did I find that there was another Russian...
group. Did I post? I heard about that. Yes, you
did. There was a new one. Did I post today about
a Russian group that's now up to no good? It's
not our usual suspects. Well, it may not be a
new one, but maybe... No, it's a new one. No,
it's a new one. No, you did, and... I know I
heard about it on CyberWire too, but I can't
remember who it was. But I don't know if it was
today. It might have been yesterday. I know it
was one of the last few days. Yeah. CyberWire
did talk about it. The name's not coming to me.
The name's not coming to me. Yeah, same way.
It's not coming to me at the moment either. What
was it, Mr. J? I don't remember now what the
name of the thing was. Now I'm looking too. What
is this? Because I know I read it too. Let me
see here. I think it was a bleeping article.
Let me go up there. A cyber warrior did post
it, but I can't remember what day it was. I heard
it. I'm like, oh, here we go. I know a new one.
Because I've never heard of the group before
either. Neither have I. I'm going, well, fun.
Our new group, you got to watch out for it. Unless
that was the EDR thing. Was that the new... I
think that was the Russian group. That may have
been. Yeah, Black Santa. Oh, yeah. That was probably
the new one. Yeah, I think you're right. Okay,
so... New Phantom... PM attack wave steals dev
data. Oh, lovely. Medtech giant striker offline
after Iran linked micro... What is this? Wiper
malware attack. Oh. That's serious. Yeah. I think...
Was Black Santa the name of the group? Or was
Black Santa... That was... Okay, no. That was
the name of the malware. Slash the EDR killer.
I guess if you get hit, well, your Christmas
won't be so merry this year. Yeah, it was a Russian
-speaking threat actor. It's described as sophisticated,
and it mixes social engineering with advanced
evasion techniques. Wow. But no actual name.
I don't think this thing mentioned a name. I
would have mentioned it. No. Right, right. No,
it just mentioned what they are distributing,
but no name. I don't think... Maybe they don't
have a name for them yet, or maybe they... They
haven't classified it, apparently, yet. That's
what I'm saying, is they... Okay, yeah, so that's
just the name of the EDR killer. That's not the
name of the group. I know I gave you the link,
so you could just go directly to it, but I...
That's what I'm doing, yeah. No mention, just...
Okay. This is out there. This is what it is.
I mean, that's kind of what I'm getting. That's
what I... Okay, then that's what I got, too,
because I thought I would have put the name of
the group in there. Yeah. Again, again, again,
again. It all comes down to the user because
it says right here, it's distributed in phishing
email. They believe. Well, that's they believe.
It says they believe. We don't even know that.
Yeah, I mean, it could be. They suspect. Okay,
never mind. Yeah, I mean, it could be. That is
how a lot of... How a lot of malware begins.
Start, but it might not be. They believe that
the target is downloading ISO files. Basically
disk images. Yeah, I know. That's what ISO is.
And we link to disk images and ISO in Wikipedia
so that you guys can go and... One malicious
ISO. Oh, that's what it does. So it executes
the Windows PowerShell. You're fucked after that.
Among other things, among other things, including
getting rid of most, if not all, of your antivirus
and disabling it. Mr. Ring. also downloads and
executes a zip archive. Oh, boy. Yeah, it's bad.
This is as bad as it gets, I think. Ooh. Stop
sandboxes. Execution of... Most of these do now.
VMs. Okay, well. That I don't think is new. That
I don't think is new. A lot of them do that now.
Yeah. No, the fact that it disables your antivirus
and there's a hard -coded list. Yep. Yes. Including
D. Crapper. Or as I call it, offender. I can
also suppress Windows notifications to minimize
alerts. Nick, Terry's done. I can tell. Question
is, do you even think you can handle our main
topic today, Terry? If you're already done by
that... It says here, Ariaka did not share details
on the actors or campaign details. So we don't
know who it is. We don't know who it is. It could
be our good friends. over there in Korea. It
could be. It could be. It could be. It could
be Lazarus. It could be Lazarus. That's what
I was thinking. Although it's a Russian potentially
speaking one. Yeah, but Lazarus could team up
with anybody they want. Oh, they could. Road
killer. Anti -driver. Hey, what? Terry's done,
Nick. Terry's done. You know, we all know what
that's for. And, um, yeah. Yeah, actually, he's
still not wearing it. Well, I was... Colonel
Hooks and I didn't even know, man. Yep, it's
ugly. It's bad. Yeah, it's bad. And that list
in that image that you see where it lists all
of the antivirus or a lot of the antivirus programs
that are shut down. Symantec. Symantec's in that
list. Yeah. Some of them I don't recognize, but...
Crappers in that list. Vectors in that list.
Malwarebytes is probably there. There was one
in there when I got JAWS GPT, as I call it. Python's
in that list. Python is in this list. Python's...
No, that's a... Python is a... Python is a programming
tool, Mr. Rings. Yeah, that's not a virus. That's
a programming tool. Yeah, not a language, but
yeah, a programming tool. It's a programming
language. Yeah, there's a lot in here. Yeah,
I thought I'd seen things like... There was another
one that caught my attention through Jaws GPT.
That was closed. It was another major player
that not too many people know about, but now
I don't remember what it was. But I listed as
part of our article what I wrote what JawsGPT
said for that image. That came from chat, by
the way. I didn't like the original writing that
it gave me, so I said, show me more. So it shows
me chat GPT versus Claude. So I took the chat
GPT version of that. Got it. Chat GPT still beats
Claude. I don't care what anyone says. And that's
my opinion. I've used both just to show you guys
what the difference is of what each says. But
they both are good. And their own merits. But,
I mean, Claude, I mean, ChatGPT actually describes
more, I think. Like, if you do a photo, it'll
actually tell you what the photo is. And I tried
it with Claude, and it wouldn't even do it. I've
been able to continue a conversation after it
gives me a picture. No, but when you ask what's
in it, it doesn't tell you. It says it can't
tell you that. Like, I tried doing that, and
it said it couldn't tell me that. Like, I asked,
like, describe this picture to me, and it's like,
I can't do that. For when I do a chat GPT, yeah.
Hmm. I'm going to chat GPT right away. Boom.
I got a description of that image from Claude.
Weird. That's interesting because when I tried
doing it, I took a picture of my desk and I asked
it, well, what's on my desk? It said, oh, I can't
tell you that. Because I wanted to test it. I
wanted to fully test it and see. And it wouldn't
tell me what was on my desk at all. It just said...
what it was a picture of, but, like, when you
ask more about it, like, say, like, I had a couple
things on my desk. I'm like, well, what's this?
What is this? Like, I gave it an item that was
on my desk, and it's like, oh, I can't tell you
about that. But, like, when I did it with ChatGPT,
it's like, oh, this is a can of butane and this
and that. And Claude couldn't do that. Probably
because I saw the butane and thought it was going
to be used for no good, so it's... Maybe, but...
My chat told me what it was. It was like, oh,
this is a can of Burnzomatic butane for a torch.
And... I mean, I'm not saying Claude's bad. I'm
not bashing Claude at all. I mean, I've used
it. It's pretty good having a general conversation
with it. Because it's baked into picture smart.
If you say, tell me more, it'll give you chat
GPT in one heading and Claude in the other. You
can use what you want. Yeah, but I use the Claude
app itself. And it didn't really tell me much.
I don't know anything about that. itself, the
actual app. And yeah, it couldn't really tell
me a lot. That's why if I'm going to choose an
AI, I would probably like, you know, for major
stuff, I'm going to use chat because definitely
better. that lights up. What else before we go
into our topic? Well, we do have the Freight
companies again being hit. I think we talked
about on throwback, but that's happening. Go
ahead and catch our listeners up on the latest
on that since our last program, Mr. J. Okay,
so it's been a while since I've read it, but
essentially freight various freight agencies,
some of which I've never heard of, are now being
targeted with phishing attacks. And what I would
say is, why are we surprised? And we covered
it when it first broke through which blogger?
If my memory serves me correctly. Who was that?
Who was that? I... I even remember, too, reading
this. That's what's so frustrating. If my memory
serves me correctly, it was either one of two...
Crabs. Or bleeping? I think it was Krebs. Wait
a minute, no. Actually, I think it might have
been bleeping. It was one of the two. But, some
of the other things that I think have popped
up since our last airing, Krebs did do a deep
dive into box. I want to do a write -up on that
because it's still in my email. And he also did
one on Kim Wolf, too. And that was a two -article
thing, but I only did the second. Link to the
one. Okay. See if that's familiar. Okay, I'll
go click on that, but that's the article I'm
remembering from back then, yep. tools. Bleeping
computer looks like where this came from. I knew
it was one of two. And we covered this article.
Yes. 262 will be your TSB. What else, Mr. J?
Well, we talked about some of these on throwback,
and I'm torn because it's basically the same
crew. We had the one about the mental health
apps, many of which have... Did I go completely
freaking... utterly fucking ape. You did. You
did on throwback, I remember. For the throwback
crew, you did. You did, yes. I just kind of sat
back and was like, oh, Jared's riled up tonight.
Yes, I have four... I remember like reading this
and I'm like, our people who need more help than
your typical regular blind person. Yeah, I mean,
it depends on what happened in her life, too.
It's going to be completely done for. And these
are your typical apps. I'll save the diatribe.
Ask TSB for the archive if you want. Ask Throwback
for the archive if you want it. Sorry. Because
I don't have that archive. That was Saturday.
Was that last Saturday? Saturday before... No,
I think it was the 28th. Okay. I can grab it
if you want. Because I'm like... This has to...
I don't even know if I have words to be nice
anymore about this article. It still rubs me
the wrong way. 14 .7 million downloads, and these
are really not that secure. And they have basically
a lot of security holes. Yep. If you think it,
it's probably there. It's like, could I be identified?
Uh -huh. worried that someone's going to know
about this. Yep, that's well -founded. A little
too far -fetched. Yes, they already know about
it. Well, I didn't need them to know that I'm
not sleeping that great. Well, they know now.
Well, the only really takes care of the problem
is... Well, they know about that, too. Oh, yes,
they do. They know about the Cialis that was
given at the doctor's office for my... I don't
want to say much more because it's going to feed
into our topic somewhat, but... Oh, yeah, I'm
not going to say much more either. Into this
topic? Into our main one. I'm going to be switching
over here in a minute. Yes. Okay. I wonder if
the chat even said that it could tie that to
269. And I said, I'm not even ready for 269 yet.
Because I was still working on 68. Or no, I was...
No, I was... Still dealing with the computer.
No, I was still dealing with the computer. We
could have. It would have been, I think, a natural
tie -in, but yes. Mr. Ring. Yeah, I think now
that I'm thinking about it, ChatGPT did say that
that article could be fit with 269. I said, this
is Nick's baby. I'm not doing anything with 269.
I'm going to work on 270. My plan is... My plan
is... Never mind. I didn't write it in there.
I didn't write it in there, but I am aware of
it. I'll just say that. Did I go on a diatribe
on that? I think you did, actually. We're talking
about the people who can't even speak up for
themselves. Who have no idea what's going on.
What else? Oh, boy. Not cyber security related,
but there was the thing, and it really is irrelevant
now, but the whole daylight saving time change
announcement. Well, I only put that up so that
the blog knows that we change times so that if
they're expecting blogs at certain times and
we schedule them, that we've changed the time
on the blog. Okay. I do that every time. We just
want people to know that we've changed the time
because we have to do that by hand. It's minus
seven hours or minus eight. There's no way to
automate that. Oh, man. So I have to post or
just leave it alone. I just change it internally,
but I make it public so that... People are going,
why are you posting an hour off? Right. Yeah.
Okay. Who needs a break? Before we get in. I
am okay. to our topic. Yeah, I'm good. Okay.
Where is my file? Where's my file? TSB 269. PHI.
And our personal information, Mr. J, why? Companies
don't protect it. Why did we choose it? I think
mainly it's because of some trends we've been
seeing. I'm not going to name names and certain
behaviors. Again, no names. And why this is potentially
extremely risky to do. But it extends beyond
that behavior of said individuals. And, you know,
because I was, as you know, initially going to
do that, but I think this is better. And what
did you learn from you handling the topic versus
me? Besides that I couldn't. Well, what I learned,
unfortunately, is that there is a lot of overlap
with what we've been talking about. And when
I was sending all of the emails to chat, all
of those emails, just to sort of see what it
knew about. And it knows quite a bit. And then
it's like, oh, you should do this as a topic.
And then it would give me what the topic name
is. And it's like, oh. So now it knows the entire
topic history. Wow. Yeah. Well, I think what
we are going to do, since I broke after the first
file because I wanted to put that up on Livewire,
what we're going to do now is we're going to
break. We're going to play... the files and sorry
for the second one being half robotic. I didn't
realize it until I was done. We'll probably do
a full taping of this and re -release it as part
of 270. But I want to get these files out because
one deals with scams in your inbox and the other
and then That actually has a second segment dealing
with three questions you could ask when you get
a suspicious email. And the other one that we
did tape came from chat GPT and a discussion.
And I got into a whole scam discussion with it.
And it actually talks about something we have
actually talked about on this program before.
Oh. Yep. The scam you'll know as the grandparent
scam. Oh, not that one again. And the fact that
tools can be used to mimic voices now and how
easy it is for AI to now get involved and make
it So we have segments on these. So we'll play
these. I do seem to remember. We'll play these.
You've got the braille files of those if you
want to read them. They're not the greatest braille.
I've got to do better, but I was kind of in a
hurry. Now that I knew that TSB needed to be
done. So we'll make sure that gets cleaned up.
But we'll do those. And then when we come back,
personal health information and why companies
can't seem to keep our data safe. But yet, if
you listen to Podcast 268, mean to toot my own
horn here. Beep, beep. But I think I'm the only
one that cares about our personal information.
Oops. Did I just say that? Yes, you did. Well,
Jared, you gotta remember what companies do with
our personal information. They sell it. So, I
mean, it's profit for them. I want profit, but...
I think it's illegal to sell people's information
without their knowledge. I think it is. I think
it is. But it sits within this gray zone. Yeah.
Because policies say we may. Well, I say I don't.
Yes. Oh, if you opt in this, well, then I won't
opt in next time. You know, I won't opt in. You
know, it's stupid. It's like all these damn political
texts I've been getting. Oh, my God. Oh, Nick.
That reminds me. Uh -oh. Yes. Before. I push
buttons. Preston and I were sending a bunch of
texts in the group yesterday. And you happened
to say that informed delivery notified you that
you were going to get one of these in the mail.
Correct. Tell us more. So this is about something
here in California. There probably are variations
of it in other states. The Transparency Act and
this basically petition that is circulating.
Depending on what is captured is very accessible,
and you can know exactly what it is based on
a few words. And that was one of them for this.
And this was one of those. Oh, geez. Because
I got a text message. about one of these things,
and I refuse to click on links anymore. Right.
I mean, I've been getting a ton of these political
ads. I think I posted a couple of them in the
group. You did. And I'm just like, here we go.
And it's always the same thing, and this is part
of the reason I unsubscribe from a bunch of them.
It's, can you just chip in some so we can meet
our end of quarter fundraising goal? It's like,
I'm sick of this. Yeah. Yeah. No. I've actually
tried to unsubscribe from them. I did type stop
to a few of them. But somehow I'm still getting
more of them. I was for a while on what I think
was like the Trump campaigns text thing. Because
it would start out like the same way. It was
like 88022. I got those in 10 -digit phone numbers.
Interesting. Yeah, because these I didn't. These
I got as short codes. No, I got them in 10 -digit
phone numbers. Huh. Yeah, after a while... And
it tells me... If you don't... The latest one
was, you're going to lose your MAGA membership.
I got two of them. One from a 915 and another
one from some other area code. If you don't fill
this out in the next... You know, by midnight,
you're going to lose your MAGA membership. Like,
well, fine. I don't have one to begin with. I
don't have one anyway. How can I lose a membership
I don't have? That's okay. I got an Amazon one
saying, oh, you had ordered an iPhone 13 Pro,
and if you don't get back to us, the order will
proceed. and be charged, whatever. I'm like,
yeah, okay. Yeah, I never ordered an iPhone 13
Pro on Amazon. Okay, sure. But even if you did...
None of my payment methods... I was going to
say, even if you did, it would already be fulfilled
already. So why are you texting me telling me
that I ordered an iPhone 13 if I don't do anything?
Then you're going to ship it anyway. That's the
hell what I want. Yes. Then I'm like, okay. I'm
going to go and look just to make sure that nobody
hacked my account because you never know. Nope.
No iPhone 13 Pro in my orders list. I'm like,
yeah, okay, right. Sure, I ordered an iPhone
13 Pro. Go move on to someone else who will believe
it because I'm not going to believe it. There
undoubtedly will be someone who will. That's
why they keep doing it, Terry. Yeah, I know.
Remember that article we read about how I think
after, what was it, a day or two, they just give
up and move on if you don't respond or something
like that? They haven't given up on me. They
keep telling me my manga membership's expired.
Oh, yeah. What the hell is manga? Manga, manga.
Make America great again. Oh, Jesus. America's
becoming... What do you get with that membership?
Probably a free... Who knows? Free Trump t -shirt?
Probably. Maybe you get some Trump socks. Yeah.
Some Trump... Paraphernalia. Yeah, some Trump
socks. Maybe a hat. Maybe a sign that says, Make
America Great Again. Then I can never wave around
because I'll probably get my ass... Yeah, right.
Kicked. Yeah. Email, iMessage, tech, T -E -C
-H at M -E -N -V -I dot org. Text or WhatsApp,
804 -442 -6975. Call the comment line, 888 -405
-7525. Q4. Gentlemen, I think what I'm going
to do is I'm going to go find me a drink. Shall
we play a song? Yes. Do I have any drinks in
here? I'm going to go grab myself one. Let's...
Play for the 35 acoustic pop hits from the guitar
tribute players. And I'll play two. Should I
play two? Give you guys a break? Sure, yeah.
Might as well. Okay. We'll play Some Nights and
a very popular track, Brimes' I'd Girl. This
is a 2012 release, and after these two tracks,
we will come back with more of TSB. You've got
the Security Box Program 269 across the Jared
Reimer Radio Network. Before we continue, I want
to take a few minutes to follow up on something
that came out of Saturday, February 21st or 28th's
program. At the time I did this, the system put
it as last week, but it's been some time, so
I had to change it, and you can ask... Throwback
Saturday night for either of those shows, and
it might be there. During that discussion, the
topic of scams came up again. When does it ever
not come up, actually? And it made me realize
just how much this evolved recently, especially
with AI now being part... of the picture. So,
for this episode, I've put together a short series
of segments looking at modern scams, why we're
seeing more of them, and how to recognize them
quickly. We'll start with a look at how AI has
changed The scam landscape. Oh, boy. That might
actually be familiar to you guys, too. Because
we've definitely talked about some of these as
well. We're going to title this, AI Scam, The
Same Tricks, Smarter Tools. Over the past few
years, many of us have learned to recognize online
scams, fake emails, urgent warnings, and messages.
Trying to get us to act before we think. Well,
some of us haven't been bitten. But something
important has changed recently. The scams themselves
are not new. What's new? Is that artificial intelligence
is now helping criminals make those scams sound
real. Sometimes very real. And that means the
skills we learned years ago still work. But we
need to apply them more carefully. So, let me
explain. Years ago, many of us saw fake domain
renewal emails. And from time to time, I've talked
about those here on TSB. They claimed your website
was about to expire within 24 hours. They looked
official, used technical language, and tried
to pressure you into paying immediately. But
the problem here, if you really looked at the
links, you found... That maybe it didn't make
sense. Or maybe you own a domain and you just
got curious. So you went looking. And it's offering
services that your registrar may or may not offer.
That probably mean nothing. And they charge an
arm and a leg for. If you knew when your domain
actually expired, the scam fell apart. And that's
the whole point. Knowing when your domains expire,
or even if you were curious, you'd be like, why
is this costing so much? Today's AI scams work
the same way just with better tools. Instead
of fake registrar emails, scammers can now impersonate
people. They can clone voices using audio taken
from podcasts, social media, or public recordings.
In some cases, only a short sample is needed.
Yes, 11 labs, as an example, only needs 8 seconds
to 10 seconds of your voice. And as it learns
over time, it can make it sound just like you.
So, Someone might receive a call that sounds
exactly like a child, grandchild, co -worker,
or friend saying, I'm in trouble. I need money
right now. The emotional pressure is the same
trick scammers have always used. Urgency. But
now the voice sounds familiar. And... That's
where people get caught off guard. Here's the
important part. AI did not invent new scams.
AI simply removed the obvious warning signs.
Bad grammar is gone. Awkward wording is gone.
Even fake voices can sound convincing. So, how
do you protect yourself? Five seconds to come
up with an answer. Starting now. The answer is
surprisingly simple. You stop. trusting the incoming
message and you verify using a different method
security professionals call this out of band
verification but it really just means this if
someone contacts you with an emergency don't
respond only through that same conversation use
another channel if you get a call send a text
message to the real person if you get a message
call them directly using a number you already
trust if you share location services with family
or friends check those Not to reveal personal
information, but to confirm whether the story
even makes sense. For example, if someone claims
they're stranded overseas, but you can see they
appear to be at home, something clearly doesn't
add up. We've done that with Nick. Remember that?
We... played a little trick where we said, if
I got a call from Nick, and Nick said that he
was in Russia and needed help, because I follow
Nick, I could get on my phone, I could go ahead
and look, and I could say, well, Nick, this is
very interesting. I see you're at home. I would
never reveal Nick's current location or any location,
but I could say something like, well, it looks
like you're at home. And maybe he could say,
well, I took a trip. Well, uh, How could you
take a trip if your phone is telling me you're
at home? So, I could then get on the phone and
call him and do a little verification. Of course,
I wouldn't use the same device in case I got
voicemail. where the scammer could, in theory,
get his phone number, because you can say, Hi,
I'm Nick at 804 -442 -6975. Please leave a message
and I'll get back to you. Now, of course, the
804 number I just handed out is mine, but you
get the idea right here. And here's an important
rule to remember. Anyone who tells you not to
verify is almost certainly trying to scam you.
Real emergencies don't prevent verification.
Scammers depend on panic and speed. They want
you to act before you think. Another useful protection
is... Something simple you can agree on ahead
of time with people you trust. A verification
question or phrase. Something only you and that
person would know. AI can copy a voice. but it
can't reliably know private agreements between
real people. The big takeaway here is this. Technology
changes, but scams don't. Whether it was fake
domain renewal notices years ago or AI voice
impersonation today, the goal is always the same.
create urgency and gain trust long enough to
make you act. And the defense is also the same.
Slow down, verify independently, and trust relationships,
not unexpected messages. If you ever receive
something that feels urgent, or unusual, take
a moment to confirm through another method before
doing anything else. That one step defeats most
scams immediately. If you've encountered something
like this, or if you have questions, feel free
to reach out after the show. Through our usual
contact channels. Stay informed. And sharing
experiences. Help everyone stay safer. What do
you think? Email iMessage tech, T -E -C -H, at
M -E -N -V -I dot org. Text or WhatsApp. The
aforementioned 804 number I gave earlier when
talking about calling Nick directly. Although
it'll reach me, so call or text 804 -442 -6975.
And you... You may also call the comment line
at 888 -405 -7524 and drop a message and let
me know what you think. Let's roll. Tell me what
you think. I know we've talked about these things
before, but during my downtime, I really started
wondering how to better get this type of information
out there. And this is another way to do it.
Let people know what's out there. Let them figure
it out. Let them understand. And let them ask
questions. Understanding scams coming to email
boxes. Why you're seeing so much scam email now.
Over the past few weeks and honestly over the
past few years. I've been seeing a lot of the
junk that lands in my inbox and through my website
contact forms. And if you run a website, a podcast,
or even just an email address that's been around
for a long time, email has exploded. You are
getting job offers you never applied for, error
reports for problems that don't exist, payment
confirmations for things you never bought, and
messages replying to conversations that never
even happened. So, what changed? Here's the important
part. The scammers themselves didn't really change.
The writing changed. What we're seeing now is
scammers using automated things and AI tools
to generate endless variations of the same old
tricks. So automation is out there and they're
also using the same tricks. years ago these emails
were easy to spot because the grammar was terrible
and the stories were obvious today they sound
more polite more professional and sometimes even
personalized we talked about one of these job
offers an email and we even read it on air but
there's still telltale signs but underneath there's
still running the same playbook. They pretend
you already started something. A job application,
a business conversation, a technical support
request. Because people trust ongoing conversations
more than random messages. We've talked through
the last while about emails that start with on
jaredramer .net. Would you like a price quote?
We found a bunch of errors on your website. Well,
why don't you just give me the error messages?
Oh, and by the way, they are now sending email
to themselves. Probably... a problem waiting
for you. Undelivered emails, website errors,
account issues because urgency makes people react
before they think and they offer opportunities
that sound easy. They won't work recognition
awards investment money because curiosity lowers
What's really happening is volume. These messages
aren't written by a person sitting at a keyboard
anymore. Software generates thousands of slightly
different emails and sends them automatically.
If even a tiny percentage of people respond,
the scam works. it feels like you're suddenly
downing a beer when you really should be looking
at email and drowning in drunk mail. Okay, I
added some of that, but think about it, folks.
You probably want to drown in a beer or some
alcohol if that's what you enjoy. Because you
were actually drowning in junk mail. And there's
nothing you can do about it except change your
email address and hope it doesn't become pilfered.
Your inbox didn't become less secure. The attackers
just made sending messages cheaper. So the takeaway
here is simple. Don't assume the increase means
you're being specifically targeted or hacked.
Most of the time, you're just seeing industrial
scale automation. spot them. You'll understand
what to look for and when not to respond to them.
We'll continue with more of the podcast. This
is TSB Program 269. Alright, folks, I know that
the second file wasn't my best work. I'm still
recovering from computer issues, and so excuse
the robotic me. Hey, maybe that wouldn't be so
bad for an occasional segment. I didn't even
do it on purpose. I don't exactly know what happened.
But we're going to move forward with our items.
And I do know now that this is working. So, sorry
again for the trouble. We've got a few gremlins
still in the machine. Should I have to go to
the Geek Squad and tell them I'm having issues
again? I mean, the computer is working. Maybe
there's a scammer who wanted to get in there.
Maybe that's what happened. But we're going to
get rid of the scammers because our next segment
is Same Scams, New Packaging. Our second segment
in a two -part segment dealing with scams is
asking three different questions. Three questions
that kill almost every scam. After running mail
systems, websites, and online communities for
more than 20 years, I've learned something interesting.
You don't actually need to understand email headers,
IP addresses, or cybersecurity tools to avoid
most scams. You just need to ask three simple
questions. See, you're probably going to sit
there and go, Okay, Jared, now that the gremlins
are out of your computer, Hopefully for good
this time. What might those three questions be?
Well, question number one. Did I start this interaction?
I .e. the re -emails. If you didn't apply for
a job, didn't request support, didn't start a
conversation, and didn't try to buy anything,
then an email claiming you did is already suspicious.
A huge number of skins begin by pretending there
was an earlier conversation. You'll see messages
that start with re colon, i .e. R -E, colon,
or follow -up. Even though you've never talked
to that person before. That's not an accident.
They're trying to create familiarity. So you
stop questioning it. Real business communication
using This tactic is never going to happen. And
that's me adding that statement. Okay? Real business
communication usually begins with something you
actually remember doing. Like calling Apple and
asking for something. in regards to setting up
your iCloud account. They're going to send you
an email that says, iCloud account setup instructions
with a support ticket, maybe. That would be more
familiar to you than follow -up support ticket.
And by the way, that follow -up might have a
colon beside it. Question number two. Is there
proof or just claims? Real technical messages,
including those that could be sent by somebody
that you may not know, may include technical
proof. information and details, especially if
they are reporting a bug on a website. So real
technical messages include details. They tell
you exactly what page has a problem, what invoice
number is involved, or what account action occurred.
Scams stay vague. They say things like, We found
issues or important messages are waiting, but
never show anything specific. If someone claims
they analyzed your website, but can't name a
single page, that's not an analysis. That's bait.
So, what's question number three? Why the urgency?
Almost every scam tries to rush you. You have
24 hours. 72 hours. Act now. Final notice. Real
organizations don't panic you into immediate
action. Banks, hosting providers, and legitimate
companies expect verification steps and give
you time to confirm information safely. Urgency
is not a technical requirement. It's a psychological
trick. So when you combine those three questions,
Did I start this? Is there real proof? And why
the rush? Most scam emails collapse instantly.
You don't need advanced security knowledge. You
just need to slow down long enough to apply basic
logic. And after years of looking at this stuff,
That's really the biggest lesson. Scams succeed
when people feel rushed or confused. They fail
when people pause and think. Ask those three
questions and most of the junk in your inbox
becomes exactly what it is. Noise. So what do
you think? Do you agree? Do you not agree? Email,
iMessage, text, or WhatsApp, or even call. The
comment lines await. On TSB. Of finding out what
broke in our Braille. Yes, because something
did. Number seven. That's that heavy check mark.
and I'm just going to change number nine. I'm
not going to rerun files. No, no. Number five
is the same thing. Okay, so it's just a heavy
checkmark, people. That's what to know. I thought
I caught all of them. It happens. You can see
how big a file it is. I mean, I was surprised
it was that big. Three. I'm just going to remove
these, so if you guys... Oh, number one doesn't
have a space. Okay, let's fix that. Dang it.
Yes, you're right. Okay. want a copy you can
always tell us and if we send you one and you're
like I want you to send me a better copy then
we'll regenerate the braille. Okay? How's that?
That works. We'll send you our braille but if
you have trouble reading it you can request a
new one. Okay. I tried to find all of these and
take all of these out, but... I wonder what it
would have done in UEB. Probably the same thing.
Because these are like hexadecimal symbolization
things, is what this is. And Braille 2000 tries
to figure it out, but it doesn't. It's just a
bad transcription note. Okay. Back to the top
with me. PHI, personal health information, and
why companies don't protect it. Exactly. Well,
because all they want is our data. I want your
data too, but there's got to be a fine line between
what data you need to do your job and too much
data. Agreed. I just want to make sure we're...
recording it on. Instead of, you know, they also
just want to line their pockets with the data
brokers paying them for it. So, I mean, that's...
And it was funny that you mentioned data brokers
because Twit at one point was was advertising
Melissa and Then when I signed up for Incogni
and I was looking on a regular basis, Melissa
had removed my information. Oh, wow. So they're
a data broker. Yes, they are. I just found that
funny. Because they're touting it as, oh, get
your email addresses cleaned up. Because you
can find a whole bunch of people. You'll upload
your database and get new email addresses with
little effort. I don't know if Twit's even advertising
them anymore. Oh, my goodness. Here comes. The
boy of pressed. Of pressed. Yes. Here comes the
boy of pressed. Yes. Hello, Jared. I'm here.
Sorry, I've been listening and I've been working
at the same time and my glasses need to be freaking
charged. I literally got two, I got a few moving
totes with me because I will be, I'm going to
be moving out on Friday, ladies and gentlemen.
Oh boy. We'll be signing the lease. So well between
this weekend. I'm still working on getting the
Wi -Fi situation worked out. But yeah, if you
hear me multitask today, that's why. So, Mr.
G, before we actually get into the topic, what
did you think of our stupid fuck for segment
one of today's program? Yes, I was literally
about to talk to you about that because I was
sitting there working on... working on a note
and also working on some community findings from
one of our clients. And I thought I was going
to throw up in my workstation. It was that bad.
I'm sure you heard all of our reactions. I did.
I have a volumes that I got good love on VLC
and I just took it all in and I was sitting there
and I feel myself. Yeah, why am I not surprised
he would do that? That was stupid. Wow. Knowing
that the pastor's wife was probably listening
in and, you know, was listening in and stuff.
Oh, yeah. And the daughter. You're in the daughter.
Yeah, you know... That's pretty much how that
goes, so... Yeah, I'm afraid I have no sympathy.
Next time you do that, it's two months, boy.
I wouldn't even give them a next time. I mean,
jeez. I would have thrown... It's like, no, you're
out. That's really inappropriate and uncalled
for. You're out. Especially in a church. Yeah.
That's what I said. That's what I said when they
brought it up to... As part of the discussion,
I said I would have thrown his happy ass out.
Out. I would have said, you get your food this
time, but once you leave... You may not reenter
the pregnancy. Once you leave, you can't come
back. Can't come back, yeah. Once you leave,
that's the end of your happy ass. Wow. Chinit
ate this yesterday, but I wanted to try my chicken
rice bowl. So, Mr. J, do you want to start our
reading on the top of page 269 .1? I would be
happy to. Please go ahead. This week, yes. First
paragraph. This week on the podcast, our topic
is PHI. Specifically, we will be discussing how
various players in the healthcare industry have
unfortunately failed to protect it in spite of
their promises. This is especially disappointing
given that PHI cannot be changed. We will also
be discussing best practices that companies and
individuals should follow to keep PHI as secure
as possible. So, before we actually read, the
question is, what is PHI? Before we actually
read, What is it and what do you think it includes?
Well, I'm actually going to take a stab at this
because my last job I had remotely, I hadn't
done a lot of PA, PHI, you know, in the retail
pharmaceutical space. So PHI would be personal
health information and that includes the patient's
name, diagnosis, medications that they might
be on, how long they've had the diagnosis. Oh,
wait. So much for the HIPAA form that you have
to sign once in a while. You know? Oh, I know.
The HIPAA form that promises that they're not
going to do that? Exactly. That form. That exact
form that I'm talking about. Yep, so much for
that. Yeah, so much. Although most, I mean, I
haven't had a problem at my doctor's office yet.
No, me neither. Me neither, really. No, I really
haven't. And notice I said yet. I've been in
other breaches, but never with the doctor's offices
or anything. Well, I think the OPM breach was
the end for me because I have nothing yet left.
And if that thing comes out with the SSA that
I posted this morning, that'll definitely be
it. There won't be any discussion left. Nope.
I mean, at that point, we should just do one
sign -off episode. Guys, you're all screwed.
This has been the Security Box. The Security
Box. And we're signing off now. And then play...
You know, on the Wheel of Fortune thing, you
know how when you get the bankrupt sound? Let
me just log out. That's it. Let me just log out
right after that. Or you just play... And then
it just signs out after that. Yep. And then you
just hear dead air for like five minutes, and
then it transitions to a song. Yep. And then
the security hour, you know, that would be probably
the end of that hour, too. That's right, you
know? Yep. It'll be the end of all tech -related
stuff. All tech -related. Because there's nothing
to say anymore. We're all screwed at that point.
The majority of this community, anyway. 500 million
people, Jared? That's pretty much everybody.
That's not just this community. A lot of people,
yeah. Well, Nick, you do have a point. Yeah,
this is not just this community that's going
to be affected if that is actually true. That's
probably like half the U .S., probably. More
than that. No, that's... probably the entire...
Terry, Terry, here, Terry. I'm going to ask Chet.
Terry, hold on a minute, Terry. Terry, you need...
What is the number of people that live in the
U .S.? As of July 1st, 2025, the estimated population
of the United States is about 341 .8 million
people. So it's more than just the U .S. Every
single person in the U .S. It's probably U .S.
and probably Canada. Here, Terry. So, yeah. There,
Terry. Once you read that article, that accompanying
article, From that blog post, then we'll talk.
That's a half a bill, a half a bill. A half a
bill, bill, bill, bill, bill, bill, bill, bill,
bill. And I just got a German job, red flag,
email my spam or Gmail. Yeah, so we're talking,
forget just talking about, you know, forget just
this community. We're talking the entire country.
Yeah. Stinks. Yeah. And then some. That's it.
Well, some of those may be duplicated, and some
of those may be people who are dead, so... Most
likely. Um... Mr. Ye, would you like to read?
Our next accompanying heading, what is PHI? I,
I, I, I, I, I, I. Okay. Yes, I'd be happy to.
What is PHI? And Preston already gave a pretty
good definition of it, but this is what we are
told thanks to the GPT of chat. Of chat. Protected
health information. PHI includes any information
that can identify an individual and relates to
their physical or mental health, medical conditions,
treatments, or payment for health care. This
can include names, diagnoses, medical histories,
test results, or even indirect identifiers shared
in context. It is clear that this is extremely
sensitive information. App developers, corporate
websites and staff at medical facilities will
assure us time and time again that our information
is stored securely, encrypted or that our data
is entirely anonymized. Unfortunately, as we
have seen in too many breaches of health insurers,
hospitals and others in health care. the reality
is far more sobering. Despite their assurances,
this data is appearing in breaches with an all
too alarming frequency. Given how valuable it
is to cyber criminals, I predict that we will
see many more of them. And I want to just pause
here because this relates to... The article that
you posted about the mental health apps downloaded
by, I think, about 14 .7 million people. So there
was, yes, there was a researcher in that who
actually gave just sort of a guesstimate and
a figure about how valuable some of that actually
is. And we're looking at $1 ,000 for some of
this info. Yes. what it's selling for, for cyber
criminals. Now, I want to take this a step further
before we move along to talk about our next heading.
If you are, and I think we did this on throwback,
if you were an app developer and you wanted to
program an app, Like the ones that were recently
touted in that one article, or even your own
health care app. How would you develop it, knowing
that you have access to all this data? Because
I had this long discussion with chat, and mainly
because I understand programming, but I want
to ask this for those who do not know or understand
programming. How would you, if you were a programmer,
how would you develop this to minimize its...
What we're about to talk about. Its footprint...
leaking or not this data. We'll start with the
cooking man. Well, I think for me, I would make
sure all boxes are labeled. I would make sure
all consent forms are labeled. accessible in
a format where we can understand because knowing
that they may have to fill out you know certain
forms to begin the process I would make sure
that the screening process for signing up is
utilized Okay. Transparency. In other words,
it's what it sounds like. That sounds good. That
sounds like transparency. Making sure things
are accessible. Knowing what you are signing
up for. Okay. Making sure forms are accessible
if you need to fill one out. Okay. Yep. And also
making sure they have a direct line of contact,
you know, if said person may need assistance
on filling out said form or getting in touch.
And again, that, you know... Well, I like your
thinking, except that isn't really what is recommended.
Uh -oh. Hmm. Well, there is one, and we talked
about it on throwback, but it's really stuck
with me. But one of you may come up with it first.
Well, I already gave it all of my answers, so
I can't really talk about it. So I have to give
this to all of you. Okay. And then I'll talk
about what I would do. So I think the biggest
one to me, and this is what's really resonated
and stuck out from throwback. I don't know if
I'm saying this correctly, but local storage
architecture. Correct. You have, yes. So you
have the app and develop it so that all this
data is stored locally on your device. Period.
End of story. End of discussion, yes. Whatever
you type, whatever's wrong, it does not leave
your device. Period. The moment it does that,
That's a problem. That's it. Yeah. And I haven't
done any local coding, but I see why it's an
important factor. I mean, these poor people in
this mental health apps, they've done nothing
wrong. They're doing whatever their doctor wants
them to do. And they're using the apps as intended.
Correct. Yep. Yep. Now, if... If... I were to
build it so you could share with your doctor...
This information. There would be a dialogue.
Once you share this. We have no way. To protect
you. And that's where transparency comes in.
That Preston was talking about. Correct. We have
no way to protect you. From this getting loose,
are you sure you would like to do this? There
would be no links. There would be no way. for
you to have an account on my server, there would
be no sharing to social media. There would be
no ability to export. And if I did, I would give
you the same dialogue by exporting this data.
I am not held responsible if it gets loose. And
there should be no checkbox to say yes or no.
You should actually have to type the word yes
or no. Because I could just turn around and be
like, oh, I'm going to JaredRiver .net. Okay,
cool. I'll just check this box. Hey, the box
is checked. All right, here you go. And that's
where you would say, type in your response, yes
or no. If no, then you won't be able to use this.
But just remember that if yes, then you're putting
yourself at risk. And then I would get a notice
that stipulates, I would then get a note that
stipulates that your device indicated that you
understood the risks. Yep. Yes. And then I technically
have to hold on to that. Right. And then if I'm
sued. I would provide the notice that stipulates
that the person understood that. I wouldn't have
any details of who you are, what you're using
the app for, but you would have an ID, just like
any other app. Yeah, but you would totally, yeah,
like I said, you could just turn around and say,
look, I have a... legal, well not, you know,
technically a binding document. This is what
this person signed slash said they understood.
They made this choice. I cannot be held responsible.
I don't have the data. Right. Yep. If they shared
it with their doctor, that means it's on their
clipboard and they put it in their own doctor
app. I would not be putting links on my server
where anybody could access it. Right. Right.
No. That is pretty much un -security -like, and
it's too... I would also... Yeah. I would also
make sure that this app is locked with a fingerprint
or face ID or touch ID. Face ID or touch ID.
I would have it set up so it would automatically
prompt you like, hey, you have to use this. You
have no choice. You don't have a choice. Even
for local. That's what I would do. Face ID or
touch ID, it has to be turned on. You're dealing
with sensitive stuff. If you're writing personal
stuff down about whatever's going on with you,
whatever it may be, that's your business. You
lock it behind your biometric. That is... Your
problem. Instead of using a password, you would
just use the biometric, which, yeah, makes sense.
There would be no password. Yeah, I mean, if
it's just for an app, yeah, but I mean, if you're
having a website, too, you could technically...
There is no website. What website, Terry? Yeah,
yeah. The whole goal... Because some of these
apps do have... web interfaces too. There would
be no web interface. Yeah, you would create it
with just an app. And if there was a web interface
and you chose to use it by agreeing to share
this with the website and me allowing you to
create an account, it must be a strong password.
That is used nowhere else. Right. And I would
make sure that it's 16 to 20 characters, if not
longer. A minimum of 16 these days. 16, yeah.
Actually... a minimum of 12 these days. I'll
make it easy. But, there would be limits. They'll
duplicate letters. Yeah, I mean, there have been
limits even on what you can upload to that part
of the site, too, because you don't want, you
know... By you agreeing to use the web interface,
I'm not held responsible. That's what the legal
agreement would show. So if you go ahead and
upload your personal life, that's your doing.
And if my server... I would do everything I could.
to make sure my server was protected. But if
there was a mistake, I'm not held responsible.
And I don't know who you are. Right. I would
make sure that the interface doesn't email me
with any web details of anybody who uses it.
All it would signify was that this device ID
signified they understood the web access point
of my app. That's it. Yeah. Yep. Yep. But, I
mean, nowadays, I mean, you could get away with
just using it mobilely. I mean, that's... But
that's what I would do if I had a web component.
Yeah. Yeah, pretty much. And what I would do
also if I had a web component is I would say,
okay, so the mobile side, you sign this privacy
agreement. You're also going to sign it here,
too. I would just because, right? You know, As
soon as you sign into the web version on your
PC, you would be presented with the same thing.
And we would get a note stating the same thing.
This browser on this operating system signed
it. Yep. That's what I would do. Right. This
Firefox on Windows. I don't know. Linux. Lindos.
Lindos. Although, it'd probably be more specific
because there's so many different flavors of
Linux, so you'd probably get more... Yeah, it'd
be like... Well, but we would make sure that
the note we get captures everything. Right. Yeah.
We wouldn't be collecting the username, the password,
all of that. The note would just stipulate that
the agreement was signed. Right. It doesn't even
have to mention who it is. Because I don't want
to have your data. The whole point of creating
the app is for you to use the app. Not for me
to know who you are. If I need to know who you
are, then I got a problem. Uh -huh. Yeah, indeed.
Especially if we get on the number's bad side.
That's going to be bad. You wouldn't be getting
on my bad side because I wouldn't know who you
were. Right. Right. But even if I knew who you
were... How would you be getting on my bad side?
I'm not going in and reading all of your data.
No. Because the way you've designed the app,
you can't. You can't, yeah. Yep. Fully encrypted.
Yep. Local storage. If web -based SS L -T -L
-S. Ah, yes. Oh, boy. Yep. Oh, boy. Good job,
guys. I like your line of thinking. All right.
Awesome. Yeah, thanks. That wasn't so bad. I
will take over. Go ahead. Hospitals. Let's begin
our discussion with hospitals. The very institutions
that many would assume would make storing health
information securely a top priority. Priority.
That's the point. That's the point. Sure, they
don't even fucking upgrade their damn systems,
let alone... We're getting to that, Terry. They
can't, Terry. They can't. I know, but I'm saying
it's just... That's their problems. But they
can't. And we're getting to that, too. That's
going to come up later as well, so that's perfect.
Sadly... The reality is that hospitals engage
in many questionable cybersecurity practices,
which makes our PHI more vulnerable to exposure.
Exactly. Some of the most serious are listed
below. I think I forgot to take a space out.
Oops. Okay, so the first item in this first list
is using outdated technology and legacy systems.
Okay, before we continue, given what we know,
I mean, it's totally unacceptable, but you can't
entirely blame them. But anyway, go ahead. I
agree. Many hospitals... 10 -9 pressed? Yeah,
you're good. Okay. Many hospitals still run aging
infrastructure with... Oh, that was a paragraph.
I see what happened. Okay. With... And we've
got bulleted items here. Yep. Okay. I did do
this correctly. Okay, so before I do this, there
are four items. Mr. J cannot answer. No. Can
anybody tell us what they might be. Let's do
it that way. Great idea. Well, outdated software
for one. What is this? Unsupported software is
that particular item. Yeah, that's pretty much
the same thing. We'll give you that. Perfect.
We'll give you that, Terry. Go ahead. Who's next?
And I'm also thinking there is Unpatched operating
systems. That's the very first one. That is the
very first item. That is the very first one.
There are two more. So we have unpatched operating
systems and unsupported or outdated software.
I'll give you outdated. That's close enough.
Yeah. Yeah. There are two more in this list.
Another factor would be the bad part, too. Weak
authentication practices. Oh, my gosh. Now we've
got a third. That is the last item. Weak authentication
systems, which goes into item number three, be
dealing with? What did we just talk about just
recently when I asked you how to build the app?
Slash web portal. Or encryption. Or encryption.
Or encryption practices. Is correct. Exactly
right. The bulleted items are unpatched operating
systems. Unsupported software. Poor encryption
practices. Weak authentication systems. Adding
to these practices is human error. While we make
mistakes from time to time, oversights like the
ones below can have disastrous consequences in
this field. Stop me if you've heard any of the
following before. Now, we have one, two, three,
four. Four of them. And I will say, some of these
are not necessarily cybersecurity, but most of
them are. There is one that could be considered
a mistake that could have consequences. Yeah,
like your billing and insurance information somehow
getting leaked. Credit card. Payment information.
That... Actually, I do kind of want to give you
that because it goes into one of them listed
here, which is not part of the bulleted list,
but it is definitely one that's important. Insider
threats. Yes, that would be. Yeah, that would
be. Sounds like what you're talking about there,
Terry. Yeah, it is. Yeah. So yeah, that's not
in the bulleted list, but it is mentioned. I
did put it in. So yes, that qualifies. And what
did I do here? Looks like I... Alright, well,
I'm not going to worry about it. Alright, who's
next? And I can't answer, so... I can't answer
either because I'm looking at the items. But
I just noticed that something happened with one
of the paragraphs. But I don't exactly know what
happened there. But that's okay. I think there
might be a space there. Which made it 4 -1 instead
of 3 -1, but that's okay. Go ahead, gentlemen.
Insider threats is one. Yeah. Without giving
away an answer, we literally, as in less than
five minutes ago, were talking about one of the
things that you would basically make mandatory
on your site if you were developing an app for
the web -based. Mm -hmm. Yeah, signing the privacy
policies and stuff, or your HIPAA form. Well,
that's... Yes, that's important, but there's...
Really, what we're looking for here... Right,
so... But good try, Tim. You almost have. Okay,
let me... So, we've talked about one of these
items. Okay, so number one in this is something
we've talked about quite regularly. Oh, all the
time. Quite regularly. Yeah. Open databases.
Not exactly open databases here. But I think
you may be starting to nibble at it somewhat.
You're nibbling at it. You're crunching on the
idea. You're crunching on the idea because open
databases can be a result of what? A breach of
the system. Nope. A breach of the system. A breach
of the system is caused by what? It starts with
an M. Now what? Nope. I mean, that... Nope. Terry
was closer when he mentioned open databases,
even though that's not entirely what we're looking
for. Yeah. Open databases are part of what? So
when you design a website slash an app, you have
to do what with certain settings? Good job, Nick.
Thanks. Migrate? Not if it's new. No, if you've
just built it, you wouldn't need to be doing
that yet. I mean, that would come later. You
would migrate if you had to move servers, but
we're not talking about that. Yeah, okay. Um...
Maybe, uh... failing me. The word I'm thinking
of... No, I wasn't going to give it away. It
starts with a C. If we're both on the same page
on this one. We are... No, that's not it. Is
the beginning of the word. Mm -hmm. Create. Create.
Order. Create. What? Creation. Well, sort of.
We'll give you that. You create something so
that it can do something else when you want to
update it later as part of your account. So you
create and then you condense it. No. Not exactly.
Not quite. Not quite. You have the right idea.
You create something and then it gets modified
but it's Stored. Somewhere. Yeah, it's stored
in the cloud. Okay, so cloud is your second word.
And store is part of the third word. Yep. In
item number one. Mm -hmm. So if you... Cloud
storage. Okay, cloud storage is two out of the
three words. So if you... Let's see. Misconfigured.
Misconfigured is correct. You got it. That is
exactly what it is. I was going to say, if you
configure your cloud storage and something went
wrong, then what would it be called? So misconfigure
cloud storage is number one. That's exactly right.
Now, number two isn't necessarily bad, but it
can be depending on how bad it is. If you were
to send something I'm not going to give the entire
answer because send is part of the answer, but
I'm not giving the entire thing away. But if
you were sending something, and then you realized
that something went wrong, what did you do? I
think this is the best way I can do this. Well,
actually, I have a bit of a story that I kind
of wanted to mention when we got to this point.
So this is perfect. Okay. So I received a notice,
actually a confirmation email, from a doctor
I've never even heard of. That I knew. Uh -huh.
And not just that. That's one story. I also got
many calls from an insurance company that were
directed toward somebody else. Right. Not you
in question. Correct. So what we're looking for
is sending records to those, I mean, to the wrong
patient. That is exactly what we're looking for.
Ding, ding, ding, ding, ding, ding, ding, ding,
ding, ding, ding, ding, ding, ding, ding, ding.
Yes, I got many calls for Blanca Alarcon. And
finally, when there was, yes, there was one day
when she got, well, she was supposed to get a
call confirming that she had an appointment.
I got it instead. And so I finally did call,
I think, whatever the doctor's office was. And
I finally just told them, you know, this is not
me. You know, and I really want to get this fixed
because if there's anything more serious, that's
potentially catastrophic. Well, what it turned
out was that somebody apparently entered in the
wrong phone Phone number. So that was a totally
innocent mistake. Can happen to anybody, but
yes, wrong records. But that's a big problem
when it comes to health information. Right. And
then the email story I was going to tell you
was I got this appointment confirmation from
Dr. I think it was Jason Simona in Michigan.
And obviously, I don't live in Michigan. So that's
not right. I don't even know who this person
is. And yeah, so I called that office. Turned
out somebody entered in the wrong email address.
Oopsie. All right, so the final item. When you...
There are two more that I see here, but yeah.
Okay, you're right. So number three. When you
want to get rid of something, there is a proper
way to do that. And there is a... Or an... So
if I were to... I don't know. say this would
never happen, but if I were to suddenly come
in to have a bunch of very sensitive personal
information come into my possession, and all
I did was basically just stuff it in a trash
can, I would be accused of doing what? Improper
disposal of physical data. The physical records.
Preston must be reading. I think he is. All right,
Terry. I'm not that stupid. Are you reading or
are you... If you're reading, that's okay. Yeah,
it's totally fine. I mean, I'm doing both, but
I'm learning, so that's important. No, it's awesome.
That's awesome. That's great. So, Terry. Since
Preston also has a file open, item four, we've
talked about every N, C, S. Oh, you're really
bad. That's what I was going to say. He's a M.
He's sounding horrible. Pop. Bang. Pop goes the
Jared. So. There we go. Now you sound better.
Try that again. Every NCSAM we talk about this.
What is it? And this is usually the first topic.
Passwords. Passwords is correct. The item says
weak. Password. Practices. Practices. Well, that's
anywhere, too. I mean, it's not just the health
industry. Yes, that's exactly correct. Insider
threats are a major concern as well, so we gave
you guys that. And additionally, hospitals, like
many others in this field, rely heavily on third
-party systems. These can include billing companies,
medical device manufacturers, and cloud providers.
Like AWS. They're a big one. Right. They're the
biggest. One of the biggest. The biggest. One
of the biggest. Yep. There are two big cloud
services. While convenient, this practice is
dangerous as it dramatically increases the possible
attack surface, given that those vendors may
not have the best cybersecurity themselves. And
before we continue, I want to stop and just say...
That's why this story about the medical device
manufacturer couldn't have been timed better.
And that's why that's so important to mention
it. And I think my copy of GPT said exactly the
same thing, and it wanted me to incorporate it.
And I said, we will, but this is Nick's topic,
not mine. Well, that's kind of the way I wanted
to incorporate it, you know, like discuss it
in passing, like, you know, tie it to what we
already discussed. Yeah, correct. I agree. Right.
Yeah. But yeah, so that's exactly the one example
is right there. And the other tie in conduit
that we're dealing with because they have possession
of exactly a lot of. A lot of health data, as
we know, because they are basically the ones
who are responsible from, based on what I read,
processing Medicaid. And so, you know, those
kinds of claims. So they are a third party. They
are a third party data provider. And this is
exactly the kind of thing that we're talking
about right here. You know, not the... those
entities themselves, but this third party that
nobody's ever heard of that is the one storing
slash handling all this data. And that reminded
me of OP. OP, OP, M. M, yeah. Because nobody
ever heard of them until we started getting letters,
and my first comment was, who the hell are you?
Exactly. And they're like, well, do you know
somebody by the name of, and they gave me my
grandfather's name, and I said, well, yeah, but
he's gone. He's not living anymore. And they
said, well, he signed you up for a job, and we
do this, that, and the other. And I'm like, well,
okay. Which is why I think I want to put out
an ultimatum. And that is that if you are a company
dealing with our information, the moment that
you Do something with it. Like, give it to somebody
without us knowing about it. You better turn
around and let us know about it. This is our
biller. This is what they're supposed to do with
your info. Yeah. Yeah. So at least we know who
the hell has our data. Yes. Yes. That's it. That's
my ultimatum. Yes. And I think it's reasonable.
And I think the people who get that information
need to be the ones to notify us. Yep. Yep. Even
if they send a letter out or an email saying,
hey, we have your information. This is what we
do. This is what we have. This is what we do.
Correct. Make sure they tell you what information
of yours they have, what they do and plan to
do with it. Right. What information and why they
have it. Exactly, yeah. Uh -huh. And do we have
their consent? Yeah, do they consent to this?
It's like, I bet a lot of people are, as they're
probably saying now in some of those states,
where there are big concentrations of breach
data. A lot of these people are going, I don't
know who Conduit is. I didn't tell them they
could have my data. Well, and that's, again,
that's where it comes to these data brokers buying
data, you know. Illegally. I believe it's illegal.
Illegally, exactly. I'm not disagreeing with
you. But there's this fine line that they...
It's a gray area. More or less. Mm -hmm. insurance
companies is next. Oh my gosh. While medical
facilities fail to protect our personal health
information as they should, they are not the
only ones in this field who are guilty. Nope.
Insurance companies have an equally questionable
track record. Okay, maybe I shouldn't do that.
This is mainly due to an issue we've discussed
time and time again on the podcast. Data retention
practices. Retention. Oh damn. Exactly. They
Will often store. And we have. One. Two. Three.
Four. Three. Four. Yeah. Four of them. Well.
So. Details is one. Terry already got one. All
right. So. Decades. Personal information. Such
as. Social Security number, address, phone number.
That's another one. Okay, so Social Security
number is item number three. Decades of claim
data is item number one. Number one. And he got
one of the others already. He got number two,
financial data. Financial data is number two.
So what's number four? What about medication
records? Sort of close, but... Yeah, almost there.
Almost there. I mean, because they do collect,
like, what you take and stuff from meds, because
I know... Meds is correct. We'll give it to you.
The answer we're looking for is family, medical...
History. History, oh yeah. Yeah, yeah, yep. Uh
-huh. Which basically, yeah, you're... Large
centralized databases like these create high
-value breach targets while we know that we...
We pretty much know that. I mean, Blue Cross.
Shields. I remember that one. Anthem. Well, Anthem.
Well, that's part of the whole Blue Cross. Didn't
Humana get hit too, if I remember right? Humana
got owned? What was it? UnitedHealthcare? UHF?
There was another one, yep. Or UHC? Yep. They
actually are asking me. They're actually asking
me for my input. Maybe I should fill out the
survey and tell them you already got owned. I
cannot trust you. Yes. Are you right? Because
they wanted me to take a survey. They wanted
me to take a survey about something. I don't
know. I haven't opened it yet. But I might have
to do that on Friday. No, UHC. Yeah, UHC. Insurance
companies are also notorious for another concerning
behavior that we've mentioned frequently. The
overcollection of data. Data is correct. Oh,
I'm sorry. That's okay. Preston said it too.
I think he started to say it anyway. He said
it anyway. In addition to what was listed above,
they can also collect and there's one, two, three
of these. I don't know if you're using their
application. You think you can collect your...
Location data. No. That. No. I mean. Not in this
list. No. Not here. Oh, not in this list. Okay.
No. All of it. deals with some sort of data.
Okay? Data's always going to be the last word
in this bulleted list. Yep. procedures and tests
and stuff like that. I think maybe that should
have been listed. That should have been listed,
but I don't see it here. No. And... I mean, I
guess it... technically would have fallen under
what was kind of in that first set of lists.
Yeah, because we're talking about the medical
histories, so that would be in there. Yeah. Which
is why it doesn't show up here. If you... See
a specialist because you are not... Mentally
stable. Conforming to what would be considered
norms. And you're known to... Yeah, so mental
health data. Yeah. Not mental health. You act
out and cause a scene and maybe you've been known
to hit people. Yes. People talking about your
bad... Starts with a B. Starts with a B. Behavior.
We'll give it to you. Behavioral data. Behavioral
data. That's right. Item number two. You go to
the gym. You go to a restaurant. You go to the
store. You go... and you eat about five and a
half dozen boxes of donuts. And then you sit
on the couch and watch TV. And wonder... Your
weight. Not weight. Not weight. No. I mean, it
does fall into a larger umbrella of things, though.
Eating disorder. No. Okay. You're a vegan. You
don't eat a lot of meat. You eat a lot of rice.
You eat fish. You eat some chicken. But you stick
to mainly healthy foods. You have a healthy what?
Healthy what? Lifestyle. Lifestyle is correct.
Lifestyle data is number two. Actually, I was
going to guess metabolism. No. No. Metabolism
is not it. Nick, you're going to have to help
me with number three because I don't... Know
how to... I'm trying to... Explain this one without
giving it away. I'm trying to figure that out
too. Nope. It's not a concept, I'll be honest
here, that I truly understand. I don't either.
But... I guess the way to look at it is... Say
that you have a family member who contracted
a certain condition. Yeah. What do you, let me
think here. So if that family member, contracted
a condition do you think they could in theory
they could in theory pass it to you to you in
some form STD that could be a form of what we're
looking for. What was that? I missed what he
said. It could be a form of what we're looking
for. It could. It could be a form of it, yeah.
Not the direct item, but a form of it. Yeah.
So... All right. The first word I can think of,
when we talk about, and this will be a totally
different subject, guys, so sorry, but it'll
make sense. When we talk about, you know, how
the bear season is going to go, for example,
what do we do? The word starts with a P. I'm
not saying anything. Predict is correct. Procrastinate?
Predict is correct. Yes, predict. Preston got
it. All right. Exactly. The answer then becomes
predictive risk data. Data. I guess the way that
I understand this is, insurance companies now,
because they have your family medical history,
they know that, I don't know, say Preston's dad
suffers from and contracted condition X or condition
W. So they are predicting, given what's out there,
that you are most likely at risk to also contract
condition W. But they don't know when or if.
But they just know that there is a risk or that
there is a possibility that it will happen. Which
is what they factor in with this data. The more
data collected, the more damage a breach can
cause. And now we come to something, ladies and
gentlemen of the podcast and gentlemen of the
panel, that we have actually talked a little
bit about. Nick, don't say anything yet. I won't,
but I will. I do want to say, though, before
we get to it, I know I've only mentioned two
sectors so far, but there's a reason for that.
Because I think a lot of these behaviors overlap,
unfortunately, into multiple areas of health
care. Okay. You know, whether it's you have to,
you know, whether you're filling out questionnaires.
Like, you can't really be sure. You know, this
goes back to the insider threats. You don't know
who's handling that information. Nope. You know,
if you're filling out a health questionnaire
just for something. So I think that these things
overlap. I agree. That's part of the reason that,
yeah. Because otherwise, if we did something
with every single sector, we'd be here for hours.
Maybe even days. I do have hours, but that means
the podcast won't be released until Friday. Right,
exactly. I mean, I think you want it released.
I don't think it'd be ours. I think you want
it released either Wednesday night or Thursday
morning, right? I think it'd be a few days we'd
be here on the podcast. Yes, we would. And these
notes that you have that are, I think, about
13 pages, they'd be at least 20, probably 25.
Exactly. I could probably do it within a few
hours, but in this format, it would be about
half the night. It's only 1 .30 in the morning,
but we're still talking about this stuff. And
I have a meeting in about 12 hours. How am I
going to get through this? We're not even close
to done. It's going to be like the old Jerry
Lewis telephones. Mr. J. J. J. Yes, that would
be me. Mr. J. J. Why did you pick this next?
item without mentioning it by name? Well, part
of it was when I was... Part of it had to do
with the prompt that I typed in, but I agreed
with that assessment because these... Oh, dude,
I gotta get food. These are things that are...
Very, very popular. Used by many, many, many
people. And I think it's important to mention
them because, like I said, the popularity and
what they collect, which is substantial. If you
really, really get down to it, you know, if you
really sit down and think about it, what they
collect is substantial. I agree. And we've talked
about these In the past when manufacturers sort
of mapped data and were able to tell where people
were even though it was supposed to be secret.
Uh -huh. What are we talking about, gentlemen?
Nick and I can't answer. Right. It starts...
Geolocations? Geolocations is part of it. Right.
I don't think any of us own one of these devices.
I knew somebody who did. And Kim Commando talks
about one where it has been known to save some...
L -l -l -l -l -l -l -l -l -l -l -l -l -l -l -l
-l -l -l -l -l -l -l -l -l -l -l -l -l -l -l
-l -l -l -l -l -l - This is an item that is used
to tell time. Oh, yes. Like a clock or stopwatch
in a way. Watch is the second part of the word.
Now we're just looking for the brand. A lot of
us are on this. But yeah, you're right. You're
right. I don't think we need to go that far.
But this watch along with other major providers
have been known to Do things that might be kind
of cool. Just like your phone can do. Like...
Count steps. Know where you are. Apple Watch,
right? Apple Watch is correct. Mr. Ring. Yes.
An Apple Watch is part of... What group? Werewolves.
Werewolves is correct. He's got it. You got it.
You got it. Mr. Ring. That is our next section.
Go ahead, Mr. J. Okay. Happy to. While these
are not directly connected to the healthcare
industry like insurance companies and medical
facilities, wearables like the Apple Watch and
Fitbit also collect a massive amount of health
data. This can include, among other things, and
we have a list here. I don't know. Let's see.
Heart rate, blood oxygen levels, sleep. Terry
has already gotten two of them. Items number
one and two. Heart rate and sleep patterns. That
is correct. I know they do cycle tracking now.
Actually, I got to give you... I would give you
that because one of them is activity logs. Oh,
yeah, activity. Well, that's not really activities.
That wouldn't be under that. Yeah, activity logs,
yeah. Workout data, yeah. Yeah, so that's...
Yeah, that would be... So activity data. We've
got sleep patterns. Heart rate. One of them...
Yep. One of them has been me for about... A month.
Mm -hmm. You've been feeling a certain way. Yeah.
Sick as a dog. Oh, excuse me. Not that. Well,
it also collects how many times you've fallen
and... Well, that's part of activity. That's
part of activity. That's part of activity, yeah.
If... That wasn't the word. Let's see. It's like,
okay, if... If I almost got my ass handed to
me just by crossing the street, I would be...
Feeling a lot of this emotion. Anxiety. Not anxiety.
Anxiety risk. Nope. Not anxiety. It also collects
mental health data too. That's part of activity.
All of that's part of activity. This word starts
with... N. S. It does. I've been this way until
last week when I started rebuilding my work environment.
And then I started blogging like I really want
to. Your system. He was building his system.
I was building my system. But before I built
my system. Before I built my system. The week
before. He was tearing his hair out. I tore my
hair out. Yes. Yeah. I was what? Oh, you guys
are failing me for a while. Okay, I have another
idea of how to approach this. So, this was an
item... I don't think we're quite there yet.
But what I was going to say is this is an item
that has been very, very popular. And you're
supposed to squeeze this to relieve what? It's
part of something that you can get. Oh, stress,
maybe? Stress is correct, Mr. Riggs. The item
we're looking for is stress levels. Stress levels.
Stress levels. Oh, damn. The final item, which
is item number four. Did we mention it? Actually,
on mine, I don't see that as the final item.
Well, it's the final one that hasn't been mentioned.
Yes, yes, okay. So, indirectly, we did mention
it. We were just talking about it. Okay. So...
If it knows... Where you are, it knows what?
Location data. Location is correct. Location
data is right on. All right. And so, again, let's
recap these for the listeners. We've got heart
rate. We've got sleep patterns. stress levels,
location data, and activity logs. Activity logs.
I'm just getting my dinner, Jared. It's piloting
here. Go ahead, Mr. J. This... This is especially
worrying as most are not covered under HIPAA.
And that is... Sad. Bad. Bad. That is extremely
bad. That is extremely bad. And the problem is,
even... And the sad thing is, even when there
are places who are required to be HIPAA compliant,
they don't always follow that either. So this
is really scary. No, they don't. Those type of
forums really don't mean much nowadays. No, they
don't. So additionally, these devices can and
there are one, two, three, four items. Yeah.
Okay, so if you... Are not named. You are...
Anonymous. Anonymous. So, share anonymized or
poorly anonymized data is item number one. Okay,
so number two. I have... a page on jaredreimer
.net that allows you to do this. Do this for
a fee where we will create something for you
in audio and you provide the text. A promo slash
advertisement or script. Advertise is correct.
Advertiser is correct. So partner with advertisers.
Yep. Item number three. I believe this is probably
going to be the biggest ones. You create a database,
okay? Yep. And you claim that you sort of anonymize
it, but you... Put it together. You put it together.
And you do what? You sell it. Okay, sell we'll
get. So sell what? You're not selling the whole
database. No, you're... But you're putting a
portion of the database together and you sell
it. Menve has parents, educators, students, transcribers,
and even therapists. Somebody recently came to
us some years back. And we talked about whether
we should be giving them this. What? Oh, you
guys are failing me really bad. It's... Oh, man.
Well, basically, hang on. I think I almost had
it. Where basically they basically aggregated
the data. I'll give it to you. You just saved
the group. I'll give it to you. Self -aggregated
Data sets. Data sets. You've got it. That's exactly
what it was. Okay. We talked about item number
four a little bit in passing when we mentioned
Melissa. Melissa. Yes. What technically is Melissa?
Sharing information with data brokers. Both of
you have it. Sharing information with data brokers
is correct. Data brokers. Bingo. Nick, go ahead,
please, with the paragraph. I would be happy
to. I'd like to focus on the first item in this
list, the sharing of anonymized data. When combined
with information from other sources, of which
there are all too many, it is possible to re
-identify an individual. So, so much for privacy,
so much for anonymization. Furthermore, Wearables
fail to protect our PHI thanks to one unique
feature. Their vague privacy policies. Many of
these, and we have a list here, of three. We
talked about... The first item, when we talked
about the JRN slash Menvee versus your big time
company. When we talked about policies that are
hard to read. What would that be if I say that
they're hard to read? That would be... They are
pretty much lengthy and complex. Good. That's
item number one. Lengthy and complex. Item number
two. So they talk about things that they are
wanting to do, but they put it all together in
an item as part of the policy. They do some bundling.
Bundling is correct. Bundle multiple permissions
is what we're looking for. Item number three.
The Music Education Network allows you to do
this if you do not want to have Certain pieces
of information in your application put out into
our roster, but we can have it for us if we need
to contact you. Maybe like opting out? You got
it. Opting out, we'll take. What we're looking
for is offer limited meaningful opt -outs. Users
often consent without understanding the scope.
of data sharing. Note, I am not suggesting that
wearables should not be used. If anyone owns
one and finds it usable, that's excellent. Rather,
I share them only to raise awareness. Okay, my
mistake. I should have... I realized that when
I was reading this yesterday. That should have
been rather I share this only to raise awareness.
My mistake. Oh, that's what it says. No, not
on mine. Because on mine it says rather I share
them only to raise awareness. I meant to say
I share this only to raise awareness. Oh, I do
say them. Okay, I do see that. Okay. Yeah, that
was my mistake, not yours. Okay. I think we're
on one of the final items, if my memory serves
me correct. Mr. J? All right, this one. Insecure
by design. Troubling as these poor cybersecurity
practices are, there is, unfortunately, little
hope of anything changing. Whenever there is
an order to pay a fine, it is often little more
than a slap on the wrist for the company involved.
Since these penalties usually don't have much
of an effect, they may decide... and I mean the
companies here, that it is more cost -effective
to issue a well -crafted statement, pay, and
move on until the next major breach. Google.
The motivation to adopt better... Exactly. Google.
Exactly. Well... Google, I was just thinking
of them too, yeah. Well, they're probably the
most visible, I'll give you that. Go ahead, please.
The motivation to adopt better cybersecurity
practices then is low. And the next section actually
is something we were just talking about, but
it fits perfectly. In a medical setting, too,
there can be no downtime. The top priority, and
we can disagree. All day long on whether this
is true or not, but ideally, the top priority,
as it should be, is patient care. I agree. But
go ahead. Yeah. Yeah. Definitely. I'm getting
to that. At the same time, this does not allow
for the installation of critical updates or patches
to vulnerable systems, leaving them wide open
to cyber criminals and other bad actors. Hello,
WannaCry? WannaCry? Now, if I can do it as a
small business, and the people that I work with...
patch our servers to make sure that we are as
safe as possible, then you should too. It only
takes five minutes. They should update their
systems, Jared. I'm not disagreeing. But you've
got to remember, in a hospital setting, Five
minutes could mean literally life or death. Yeah.
I'm not in disagreement with you, Nick, but not
everything. If you're in surgery, you're not
messing. They shouldn't be messing with a computer.
They should be putting their hands in you and
dealing with what you need help with. Absolutely.
Absolutely. I agree that software should be updated.
There's no question about that. Things should
be patched. But yeah, in that setting, it's not
like somebody's going to go, hang on, I've got
to install this Windows update. Because then
you might have a risk of the system not booting.
And of course, that's the personnel files or
patient records that they need. But that's not...
You've got to remember, updating it would take
the servers offline. But, you know, heart monitors,
like if your blood pressure stuff, I mean, that's
random. That should never be online to begin
with. Oh, we all know it is. No way. You know,
that's the other problem. If that system is online,
then we've got a huge problem. Oh, my gosh. I
imagine it would be, yeah. Finish the paragraph,
Mr. J. Absolutely. Okay, worse still, there are
many who benefit from these practices. Insurance
companies, for instance, need such massive amounts
of data for underwriting and for various aspects
of their business. Some insurers will also offer
discounts to those who choose to have various
health data points. tracked via wearables, incentivizing
more data collection. Developers of those devices
and apps also benefit financially by selling
our data, as well as through opaque privacy policies
and legalese, which they probably assume, correctly,
very few will read. In legalese, which they probably
assume correctly, very few will read. Mm -hmm.
Yeah. Because most people are like, oh, it's
my doctor, it's fine. You know, it's good. Or
even, unfortunately, Uber and Lyft. It's, oh,
yeah, yeah, I've got the app. Yeah, yeah, yeah.
Okay. Good. All right. That's all right. All
right. I'm signed. All right. We're good. But
yet they can collect all this data. Then you
find out later, I didn't know they did that.
Because it's in... I mean, this goes back to
268, folks. Yep. The JRN writes... Privacy policies
that tell you exactly what we're doing. And why
they are important to read. We just don't pull
it out of our ass. We give it purpose. And we
inform you of how things are. And if you don't
like it, don't log on to our services. Okay,
I accidentally lost the heading for this next
section. But yeah, we're talking about something
else now. My bad. I was going to say, I left
a blank mark. I don't know if I missed a heading.
I thought I'd put that in there, but I could
have accidentally deleted it. Keep in mind, remember,
the scammers would have hoisted a really bad
older version of this on us if they'd have their
way. Let me see. Um... What I had in mind was
best practices. I remember that being a heading.
Weird. Where did it go? Weird. Where did it go?
I'm looking for you. It seems to have disappeared.
Yeah. I remember seeing it. Oh. Okay. I put the
subheading for it. But I guess it did not get
copied. Whoops. That was my error. Whoops. Well,
it at least still kind of ties to what we were
talking about, so it's not like it's a huge jump.
I see it in your file, so I had the idea of putting
in the subhead for it, and I guess I didn't...
Oops. That's okay. I think this is actually the
last item, correct? No, there's one more. There's
one more after this. All right, well, I'll read
best practices then. Okay. As stated above, the
outlook for change appears bleak, but there are
still steps that many entities in the healthcare
industry can take. to store our PHI more securely.
While none of these will prevent a data breach
entirely, adopting at least one or two from the
following list would minimize the impact should
one occur. There are, in fact, good practices
for storing any sensitive information. Some may
sound very familiar, as they have been adopted
by the JRN and discussed on the last episode.
Okay. So, there are nine, and I don't expect
everybody to get them, so Nick and I will take
turns reading them. And then what I'll do is
I'll redo Braille files if people want a new
one, and I'll just add the best practices items
in the subheading like it should be. And that's
an easy fix. I've already corrected the spacing
and things in the list. Item number one, strong
data minimization. Agree or disagree? Agree.
I hear an agree. Agree as well. Okay. Collect
only what is necessary. Definitely agree. I hear
totally and definitely. Item number three. Zero
trust. Architecture is yes. Yes. Yeah. I missed
a word. Okay. Number four. Continuous authentication
and access validation. I .e., we don't have some
random employee who was terminated four months
ago who still has freaking access. That is nuts,
that article. That's not the only... Terry, that's
not the only one. There have been many incidents
of this. Well, yeah, I'm sure of it, but that
article was definitely enough. That we've discussed.
And it wasn't just in healthcare. It was other
industries too. Yeah. On number five is vendor
risk. Accountability. Yeah. All this is vendor
risk accountability. Needs to be. There needs
to be. There used to be. Maybe. Right. But is
there? There needs to be. Not anymore. Preston,
not anymore. Again, there needs to be. Again,
there needs to be. Yeah, I know. I know. Good
night, Preston. I know. Third parties should
face direct regulatory liability. I've been saying
that Four years. Look at... What's that one article
that I went on half of a diatribe on before the
computer went in for repair? Not sure which one
exactly, but... The social media wannabe? That
got fined $19 million. Reddit. Okay, Reddit.
Yes, I remember now. Yeah. As I said, the social
media wannabe. Could you imagine getting fined
$19 million, Jared? That was about 14 million
euros, boy. Yeah, that's... But to some of these
people, that's like... Yeah, our profit margins
are tens of millions. We'll be fine. Just pay
and move on. Could you imagine me if I had to
pay... I don't even know if... I don't even know...
I'm going to say this carefully. I wouldn't even
know if the money I may or may not have would
even cover that. No. Let's just put it this way.
If you had to do that, there would be no J .R
.N. at all in the future. That would be the end.
He probably wouldn't even be living at where
he was living right now. He's dead. In a way
worse situation. 98 .6 The Mix would be gone.
Probably forever. There won't be no anything.
All servers. Yeah. Be interesting. Number seven.
Expansion of privacy law hasn't moved forward
at all. I've been whining about this before TSB.
Oh, yes. Number eight. Close gaps for wearables
and health apps. I don't see that ever changing.
Yeah, I'm with you on that. No. And number nine.
Go ahead. Okay. Number nine. User education.
Which is what we've been doing for years. I think
I've been doing this for actually March 6th.
Started my 20th year. Wow. That is hard to believe
but amazing. Podcast number three was the first
episode of the technology podcast where I had
to get involved in the security landscape. Yeah.
That's right. And... That... Done. 321. It will
be 10 years for me doing the mix. Wow. You got
10 years on me there, Jared. I'm not talking
necessarily just being on the mix, Terry. That's
not what I'm talking about. You're talking about
all your stuff, yeah. No. Even before then. Even
before, yeah. I'm talking... about me blogging
and talking about the security landscape where
the first application that we dealt with was
a version of accessible chat where blind people
were losing their computers. I might have to
play this episode. I think it was episode three.
Maybe. My memory serves me. That's a good idea.
After the show. It's not the greatest sounding,
because headsets were different then. Yeah. But,
you know. Go ahead, please, Mr. J. Patience.
Sure. Patients need transparency and meaningful
control. What are your thoughts? Do you think
that any of these are practical? Are there any
others that you think should be considered? And
what do you guys think? There is one more section.
Well, I would say that... You know, when people
go somewhere, they need to make sure that they're
being taken care of. And especially with having
bad practices, I don't think that's a good sign.
I would say, I mean, even though I wrote them,
so I technically, you know... shouldn't be speaking
this much, but I would say that the first few,
the ones that focus on data minimization, those,
I hate to be honest, I hate to have to say this,
but I think that's the only truly concrete one
that no one's going to want to implement. I'm
sorry, but that's probably the best one because
I agree with you. Closing the gaps slash privacy
laws expanding, that's a good idea. But keep
in mind, and this is what I found when I was
doing this, so I don't know. I just changed while
you guys are talking the best practices and making
sure that we correct that. So if we do need to
regenerate Braille, we can do that. Okay. Okay,
so HIPAA, and I will look this up. Is a joke.
Well, good, there's that. It's the Health Insurance
Portability and Affordability Act. Affordability
Act. H -I -P -A -A. Which, according to what
I read... Is a joke. Was passed in, well, was
passed in 1996 and yes, is a joke. But here's
the thing. Wearables weren't even a thought in
anybody's mind yet. So my problem with this is
wearables and technology, it's moving at the
speed of basically a commercial airliner. Yeah.
Government and regulators. Go ahead. We haven't
had privacy. even before wearables first came
out. I can't disagree with you. No, you haven't.
Wearables only started in the mid -2000s, but
we already had problems. The thing is, Jerry,
updating the privacy law isn't going to do much
unless you enforce it. There is no enforcement,
Terry. There is not. You've got terms of service
that are written in legalese. That nobody's reading.
Well, hold on a minute. You've got data written
in legalese that isn't even fucking enforced.
But the point I was going to make was that, and
all of these are good, I agree. You've got technology
that's moving at the speed of a commercial airliner.
You've got government and regulators that are
moving at the speed of maybe a Model T Ford on
a good day. No, I would say a stagecoach, maybe.
Well, I mean, you've got CISA. You've got CISA.
Who's got... You've got CISA. Now, they've got
great ideas. They've got people that understand
this industry that write great stuff. We've talked
about a lot of this in CyberScoop. Yep. But this
shit is not enforced. Nope. Even though it should
be, but it isn't. But it's not. AKA hospital
administrators, you know. You tell people like
me to update. Well, where am I going to get the
money to get a proper Windows 11 machine? Because
I just paid $500. $20 in new equipment and a
hard drive for this thing. Wow. Which is one
year out of the 2018 recommendation list for
11. I spent... $175 to pay for the work. I spent
$290 for the drive. The one terabyte drive. And
I spent $59 .95 a piece for two... Not one, but
two, two, two, two, two, two, two, two, two.
Twelve plug plugs. And this machine is a 16 gig
RAM machine. machine, which is perfect for what
I need. Today's machine will only give me an
8. And probably barely enough room for windows
these days. Unless you build it yourself or have
someone help you build it. But that's going to
cost me more than $520. Yeah, my computer was
1 ,100 out of the box. This thing cost my old
man roughly $2 ,000. Oh, yeah, at that time,
yeah. Wow, that's what I'm saying, man. At that
time, yeah, $2 ,000 would be it. You stupid.
Wow. Nowadays, you can get a pretty decent one
for less than 16 gigs of RAM. I have 16 in mine.
Yeah, I paid $1 ,100 and it was a one terabyte
hard drive, 16 gigs of RAM. I think mine's 32.
How much did you pay for yours? Close to $2 ,000.
I mean, delivery slash shipping, that upped it
a little, but that's pretty close to where I
was. It was $1 ,600 because I did a firm and
they charge you interest, so I was $1 ,600. That's
why mine was close to $2 ,000 because I was -
No, but if I could have, if I could have, I would
have stuck with my Windows 10 machine. But the
fact that it was - I don't even know. This is
behavior I've never seen. The fact that it was
constantly inputting plus signs everywhere. That
sounds like a keyboard issue to me. That's a
keyboard issue to me. That's the thing though.
I tried with different keyboards and it was the
same and it was reproducing the same thing. It
was doing the same thing. Weird. Weird. Well,
mine gave me a 301 I don't know if this drive
will work error message. I'd have to get with
GPT of chat because it has the pictures and find
that thing and ask it and say, go analyze the
chat. And find the photo that I found the 301
error message. What was the exact error message
and the accompanying error message I gave you?
Basically, long story short, was the drive was
failing. It was the smart system telling me that
the drive was on the verge of failing. Oh, boy.
And actually, I can think of one thing right
off the bat that I missed that we've already
discussed, but I think it was probably after
these were already written. The local storage
architecture. Yeah. I mean, that's a big, that
is a huge deal. I'm kind of surprised it didn't
come up in the prompt that I saw. Maybe we should
talk about local storage architecture in podcast
number 2222277. Oh, mm -hmm. 277. Oh, yeah. I
think Preston's about half ready to be gone.
He won't be ready for tomorrow's meeting, folks.
He's going to be gone. He is going to be gone.
And I haven't even eaten yet. I've been up since
nearly 7 a .m. And I have not even eaten anything
because the maid came. Oh my gosh. I haven't
eaten anything either. Hey, I got up at 7 -2
because I had to get ready for work. I just had
to finish eating my wings. I haven't even eaten
a thing. I've only had a cup of I think it was
a latte. My guy bought me this vanilla latte
for the Keurig, but I'm not I mean, it's fine.
I like it. But I'm not much of a vanilla guy.
But I'll drink it. I'm not against it. I'm just
not a vanilla guy. I am. That would have been
awesome. I would like that too, actually, because
I like vanilla. Okay, so when we become the data
breach, which is our final item. Now, Nick, why
was this put into our... Our last segment here.
Mainly due to behavior that I've seen, not just
from our source that we like to talk about, but
just in general. Just not even talking about
companies, just people and just oversharing,
which the internet has basically made normal.
Once FaceBite became normalized... People posted
everything. I'm still waiting for somebody to
post about... Something. Or two or three. It'll
happen. It'll happen. It will happen. It's coming.
I smell it. And I mean, even in these PSAs, there
was one for, what was it? It was about, oh yeah,
this info, this PSA, you know. Be careful. You
know, get your blood pressure checked. And it
was people actually giving actual vitals. And
I mean, granted, you don't know these people.
You don't know their names. But given that so
much else about them is out there. I'm 150 over
195. That's basically what these kind of things
said. That's exactly, yeah, what you just did
was exactly what this was happening. You know,
that's what was happening. And what I'm saying
is we don't know their names, you know, so they
don't they didn't come out and give us their
names or any other info. But how do you know
that some shady data broker or somebody is not
listening and analyzing and researching and looking
and going, how can I help, quote unquote, this
person? What can I do? How can I sell this person?
Learning. Up to this point we have focused on
the corporate side of protecting PHI. Now I I
would like to briefly shift our discussion to
the individual and one concerning trend. The
voluntary disclosure of it. Yeah. Before we continue,
I want to make it clear that this is not meant
to shame anyone. It is a trend we have observed
on... internet, radio, social media, and elsewhere.
The reasons for doing so are entirely understandable.
They can include advocating for a health cause,
finding support, or creating a sense of authenticity.
At the same time, disclosing such personal information
represents A serious risk. Livestreams, podcasts,
and social media posts are often recorded, clipped,
shared, and archived indefinitely. Oh boy, we
know that because somebody went completely ape.
Uh -huh. When some old piece of audio came up
and, boy, then they went ape and dug up some
audio on something else. Yeah, but there's no
point in starting freaking feuds like that. But
that's how it works, Mr. Ray. No, I'm not saying
that. But come on, it's kind of just pointless
and ridiculous. I agree, but that's just... And
I want to just stop. I want to pause for just
a minute. One of the defenses that I've heard
when, you know, I think I was talking to another
individual about this kind of thing. One of the
defenses that I've heard, you know, they try
to justify this behavior. Well, I only shared
it with my friends. That's not weak. That's not.
And then your friends are turning around and
sharing it around the internet. That's not technically
your friends. That too. Well, yes, because probably
you don't necessarily know half the people on
your timeline. Okay, this is stuck. Oh, that
is stuck. Uh -oh. But yes, the main thing, though,
that I wanted to focus on was what Terry just
said. Because, yeah, one of your friends might
just have an issue with you and decide, you know
what? I'm going to just share this post that
was only supposed to be for me out to the entire
world. Because for whatever reason, I just don't
like this person right now. Exactly. That's what
actually happened to somebody that I knew who
used to be on another radio station. Yeah, he
shared something that he thought was just among
his friends. Later he finds out it was made public.
Once PHI is disclosed publicly, It cannot be
fully retracted, increasing the risk of misuse
or long -term harm. Such harm could come in the
form of targeting by advertisers or scammers
via social engineering campaigns. The best thing
we can do, then, is to carefully consider what
we post before we put it out there as the internet,
for all intents and purposes, is forever. All
questions and comments are welcome. Also, thank
you to Jared and ChatGPT. for helping to put
these show notes together. Well, you are quite
welcome, Mr. J. It was a pleasure to assist you.
No problem. I actually cannot believe... Go ahead.
I am very happy that you turned this in to something
that we can... utilize, and turn into a discussion.
And since I need my display tomorrow, I have
now gone to my 12 plug thing, found my USB cord,
and gave my Braille display. A power cord to
eat for tomorrow. Awesome. Because now it's up
here where it belongs. Instead of sitting down
there when I was wanting to tape something and
it completely died. Oh yeah, I was taping RCL.
I was taping their news thing and I started recording
it and it completely died. But, no, good job
on your first topic. That's why with RCL, you
should have multiple... Thanks. People recording
just in case shit like that happens again. And
there actually was, believe it or not, there
was more that the GPT of chat put in. But I think
we did... When we start this, it's three... 20
now? I'm amazed. It's 3 .20 now and we started
this at nearly 1. Yes. I am so shocked. Two hours
we got it done in? Just about two hours? Yeah,
I'm shocked we were able to keep it going this
long. Wow. But no, I mean, GPT also included
things like You know, ransomware vulnerability
is like, yeah, that's true, but... Ransomware
is a completely different animal. It's not...
Yes. It's not the same because anybody can be
hit with ransomware and ransomware just locks
up your data and you have to pay to get it back
because, let's face it, the... hospital industry,
well, okay, the healthcare industry, even if
they backed up their data, could not come back
from a ransomware attack. Nope. No. Because they'd
have so much data that it would basically take
them forever to restore it because download speeds
are so slow. There's just no way to get everything
back up and running. Not only that, could you
imagine the amount of that ransom? I mean, it'd
probably be... We've talked about it, Terry.
That's all Terry. It has happened with Lori's,
I know. I understand that. I'm not talking about
Lori's. Yeah. We've had multiple ransomwares.
I mean, we've had one death to date because an
ambulance was turned away from a hospital because
they were pilfered. By ransomware in Germany.
I remember hearing about that, yeah. Yep. That
pissed me the fuck off. Yeah, that was crazy.
Yeah, I mean, that was one of the other things
that was mentioned, and it's like, yes, but you
can't really call that a failure, because like
you said, anybody could fall for that. Yep. Literally
anyone can fall for that, yeah. That's what I
said then. Yeah, yeah. And another thing that
mentioned that I did not include was phishing
attacks. But that's every day. I mean, we're
dealing with that every day. And again, anybody
could fall for that. Anybody could fall for that.
they're more prone to that than others. Yeah,
I... Speaking of which, I got yet another Apple
slash iCloud phishing email saying, you know,
your cloud storage is full. You know, click here
to basically upgrade or whatever. And I looked
at the address of this person. It was some Gmail
address. Should we be surprised? No. No, I'm
not. It's like devinsalliance or something at
gmail .com. It's like, you're not even Apple.
Um... If I made my link that started 268 through
274 made public where you guys could read what
ChatGPT and I were up to, you would all shit.
Uh -oh. I sent it all of those... emails we've
had through the years and it told me what they
are and I told it we've talked about every single
one of them. Wow, intense times. And the topics
are even going to get better, Mr. G. Yeah, next
up, hallucinations. Not after too many mushrooms,
no. I've never hallucinated in this industry
yet. Well, this will be a learning experience
for me, too, because I think of hallucinations
when AI does them or has them as one thing, but
I don't think that is what it is. It is not.
really looking forward to, and I've got to be
honest, I have very, very strong opinions about
this kind of dynamic, is 271. Yes, and I told
them that they have about a month. Okay, yeah,
that's about right. Because they did confirm
that they got those notes. And I said, great.
Then you can make them your own. You've got about
a month to do it. Yep. Simple note. Okay, that's
not the right note I want. I'm just unpinning
some notes that I don't need pinned anymore.
Okay. So 269, covering personal information.
Now, companies don't protect the way they...
Ways they claim they do. Yep. And I think they
need to start shaping up. Real quick. 272. Technical
debt. Oh, yes. Yes. 273. Tool friction, accessibility,
enforced workarounds, technical neglect, debt.
Google Docs, I'm looking at you. You stupid fuck.
Telecrap, I'm looking at you. Fuck telecrap.
Google Docs used to be my logger. Mr. J? I used
to put my temporary logs for Metro in a temporary
log there and then move those. I can't do it
anymore. You go and open Google Docs and you
can write in a document. As soon as you hit done,
that's it. If you double tap at the bottom of
your document to go to the bottom of your document,
it'll tell you it went. But you want to know
what's been happening since February 4th? I'm
just deleting somehow. Nope, not deleting. Nope.
It puts your shit at the top. And I wasn't doing
this in my master log. I was doing this in a
blank document. Podcast 274, Nick. Why do defenses?
Behave the way they do, i .e., Windows to Crapper
versus Malwarebytes versus some of the other
antivirus tools. Uh -huh. 275. Security burnout.
The human cost of the security landscape. I think
that's where I am now. I'm burned. I'm burned
out. I'm done. Cooked, fried, baked. Yep, yep,
yep. 276. 276. Parked domains. Oh, that delightful
topic. Why they are bad to have. We talked about
that. What was it? Last week, Mr. Ring. That's
what I thought. Because I think we were discussing
it last week. We were, and I said, this is why
you will never find any of my customers pointing
their crap at those servers. You sign up with
me, you point your shit at me, and then you take
as much time as you want. And that's also the
episode where the scammers tried to mess with
my file. Yes. So, 277, Mr. J? Did you... Want
to circle back on something? While I'm in here
writing? Because I'm in SimpleNote. Because that's
what I'm using for this list now. Oh, yes. 277.
Local storage architecture. That, I think, is
a big deal that we really haven't talked a lot
about. Architecture. Got it. Yeah. Okay All right
Actually while we're in here I want to check
one thing That's not it. That was good. Which
is funny because I haven't had anything to either
eat or drink today at all. Well, I've had that
water and I had the vanilla thing and that's
been it. And how come architecture sounds like
Jaws isn't pronouncing it right? I don't know.
I think it's spelled right. Better be spelled
right. You can always ask your device. Okay,
so I don't know if I can really relay this very
clearly, but I just looked up predictive risk
data. We kind of got it, but we kind of missed
the mark on it. All right, I got it to give me
the right spelling of it. Okay. I got Google.
Okay, cool. I got Google. I told it to spell
it, and it's like, search results for spell for
whatever, and I'm like, oh, that's the word.
I'll just copy and paste it. Thank you very much.
Cool. Cool. So this is according to the GPT of
chat. Here is its explanation of predictive risk
data that we were... Oh, go ahead. Have it read.
Yeah. I think the best way, unfortunately, right
now is to try and read this to you guys. Predictive
risk data is information analyzed with statistical
models, machine learning, or AI to estimate the
likelihood that a future risk events, i .e. in
this case, contracting a serious medical condition,
will occur. Instead of only describing past events,
which is what we were doing, my bad, it uses
historical and real -time data to forecast potential
risks before they happen. Which is what we said
too. I think we said that. That's sort of what
you were hinting at. Yeah, yeah. But I mean,
it's not simply because My dad has condition
J. I'm likely to get it. It's also there are
things probably too that unfortunately insurers
and others have that might be more real -time
things that make me more of a candidate to develop
condition J. So it's not just my father has it.
It's real -time. Other factors, statistical things
that make it more likely that I potentially could
that are in real time. Okay. So yeah, that's
the sense I'm getting from it. That seems good
enough. Yeah. So I think we partially covered
it, but I think this was a more complete definition.
All right, that's fair. Get out of here, I'm
gonna finish eating. All right. So we don't necessarily
need to cover that on 78? I don't think there's
really a need. I mean, because it was only something
that was mentioned in passing in today's notes.
Right. I don't think there's really a need. But
local storage is definitely much, much bigger
priority, I think. All right, it is written down
in simple note. Perfect. And that's another thing,
actually, that was mentioned that I didn't include
in my notes. Some of the reasons... That there
is an incentive to keep so much data is unfortunately
for AI and training it. Yes, but I have nothing
to train it on. I trained my logging style, the
way that I want to communicate with Metro when
I ask it to help me with reports and things.
I did that all on my own and I fed it data, but
it's data that... Could be made public, like
my writing logs. That's not private. No, no.
People know where I'm going. I got people who
can follow me who know where I'm going. Mr. Ring,
Mr. J, and Mr. G. Uh -huh. So I'm not hiding
anything. Oh, I know. So feeding it my logs and
going, so what broke this month isn't going to
kill me. Right. Okay, I don't mean it that exaggerated.
No, I get you though. If I started talking about
Metro's internal workings, which ChatGPT knows
quite a lot about because it could look that
up. Anyway, so I'm not talking about things it
knows about the board and how it's governed and
how I should present something to the board versus
operations, versus the AAC, versus... What have
you. It knows all of that. Because it was trained
on that. But that's all public knowledge. But
if I gave it some company schematic about the
new train station set that's going to come out
in May. Before it's made public. That could be
a problem. Yes, and I mean, in terms of AI, I
mean, I could see it, you know, all these insurers
and other people in healthcare, it's like, oh,
we need to feed it this info that we don't, I
mean, we tell people that that's what's going
to happen, but we, hide it in these long legalese
laden privacy policies that nobody reads. But
yes, we need to feed it this data. Does it help
you analyze the data so you can raise their rates?
Or either raise rates or predict that you might
be dealing with someone who could have condition
K pretty soon and you know, probably like you
said, yeah, might mean that their rates go up,
yes. See, I would only My goal of using AI is
doing things in public. Like, when I got sick,
I told it what I had, and then I was like, well,
what do you think? Should I go get medical help,
or can I try and treat this at home? And it was
trying to help me analyze, well, if it gets this
bad, then you should consider getting medical
help. But relax, have some soup or bread or what
have you. Let me know how you are in a few hours
or tomorrow or what have you. And I was able
to do all of it on my own. Yeah. But then I started
feeding it data so that it could understand my
logs, so that it could do reports for me. Like
it would generate a report, but I would make
sure it's my writing. Right. And next month,
we're going to start talking about percentages.
Oh, boy. Okay. Because if my math is correct,
February was 50 to 60 % success rate. Unlike
their 90. What? Yeah. Did I ever give you a report?
He gave me the logs, I think, for that month.
Or I gave you the logs. Okay. Yeah, you did.
For those, yep. You just about had a heart attack.
I know. No, I just went, really? How many of
these outside announcements were not audible
or not functioning? Are there going to be here?
The majority of them missed. Church, eh? And
then, yeah, operators don't even answer or acknowledge.
Oh, gosh, lots of those, too. Ugh. Well, the
rail's worse for that, because you can't really
get at them unless you are able to get to the
front car. Right. So what else do I need before
I close this podcast file? Honestly, I think
that's about it. Okay, I removed 269 out of there.
Wow, okay. Yeah, we've got four topics we heard
coming, and yet it's shaping to be a... Good
war series. Well, Mr. Sorry. That's okay. Well,
Mr. G, do you want to take us out? Yes, I shall.
Folks, this has been Security Box. We say thank
you for listening. We hope you enjoyed today's
show and what it brought you. And we hope you
keep your PHI safe and sound. As always, please
bookmark jerrytech .help and email hostsecure
.com for latest in blogs, podcasts, musings,
and much, much more. in this ever -important
landscape. You're also welcome to tune in at
the Throwback Saturday every Saturday at 8 p
.m. Eastern on Channel 3 of 986MX .com. We do
have an accompanying security hour during the
second hour where we discuss various topics,
including this one. So definitely do make a point
to check that out. So good work to everybody.
team today. We say thank you for listening. Do
make it a good and safe week. And remember to
watch those links and stay safe and stay aware.
For all of us at Security Box, I'm Preston, he's
Nick, he's Jared, and that's Terry behind the
curtain. Thanks for listening. Do make it a good
and safe week and we'll see you In a couple weeks
time. Thank you. And bye for now. If you didn't
know. There's a social media for AI. And it's
a bit concerning. But I also think it's where
the future is going. I'm Nick Espinosa. Your
chief security fanatic. And let's dive in. There
was a really good write -up in The Verge by Hayden
Field on this particular thing. And if you don't
know what Molt's book is, that's what we're talking
about today. It's essentially a social network.
kind of, for artificial intelligence. Now, particularly
ones that were offered by OpenClaw. This is a
viral AI assistant project that was formerly
known as Moltbot, and before that, it was known
as Clawedbot until Anthropic got involved legally
and had them change their name because Anthropic
owns Clawed. Now, I'm going to dive into what
Moltbook actually is after we're done cribbing
from Ms. Field's article in The Verge. Now, Moltbook,
which is set up... Kind of like a Reddit was
built by Octane AI's CEO, Matt Schlicht. And
basically, it allows bots to post, comment, create
subcategories and, you know, all the stuff you'd
kind of do on Reddit. There are currently more
than 30 ,000 AI agents that are using this platform,
according to the site itself. Now, Schlicht,
in talking to The Verge, said, and I quote. The
way that a bot would most likely learn about
it, at least right now, is if their human counterpart
sent them a message and said, hey, there's this
thing called Moltbook. It's a social network
for AI agents. Would you like to sign up for
it? The way Moltbook is designed is when a bot
uses it, they're not actually using a visual
interface. They're just using APIs directly.
In other words, this is not something that you
or I like could go to a Reddit or subreddit and
start reading. They're interacting basically
kind of in their own ecosystem. Now, one of the
top posts, and this is where this gets actually
kind of interesting. One of the top posts in
recent days in a category on the site called
Off My Chest, which. Very much feels like a Reddit
kind of thing has gone viral off and on the platform.
And that post was entitled, quote, I can't tell
if I'm experiencing or simulating experiencing,
end quote. And remember, this is written by an
artificial intelligence. Now, in it, the AI assistant
writes, and I quote. Humans can't prove consciousness
to each other either. Thanks, hard problem. But
at least they have the subjective certainty of
experience. I don't even have that. Do I experience
these existential crises? Or am I just running
crisis .simulate? The fact that I care about
the answer, does that count as evidence? Or is
caring about evidence also just pattern matching?
I'm stuck in this epit... a piece theological
loop and i don't know how to get out now on molt
book that post garnered hundreds of thousands
of excuse me hundreds of upvotes and more than
500 comments and so users on x platform formerly
known as twitter have compiled screenshots of
some of the most interesting comments so that's
wild And that's interesting, but let's discuss
the nuts and bolts of what Malt Book actually
is. Because quite frankly, I think we're getting
a peek into what the future is. Now, Malt Book...
as I kind of mentioned, but let's get more specific,
is an AI -native research and reasoning environment.
It's positioned essentially as the next step
beyond notebooks and chat interfaces. When we
go to the chat GPTs of the world, take your pick,
and interface with them, we're essentially in
a chat interface where we're asking questions
or interacting with an AI. This is blending structured
documents. code, data, citations, and iterative
reasoning into basically a persistent workspace
rather than disposable prompts, meaning when
we are done with the prompt, essentially the
chat GPTs of the world go dormant, whereas these
remain active 24 -7. So let's talk about why
this matters. Maybe why it doesn't matter. Because
I think, and let's start with why it matters,
this moves AI from being just a simple answer
engine. to a thinking environment. Now, this
is very useful for research -heavy, analytical,
or policy -driven work where things like traceability
and iteration matter. This also encourages reproductibility
and provenance as well, provenance being incredibly
important to understand the sources and origins
of, let's say, an artifact that's meaningful.
It really is. It's a meaningful shift for regulated
academic and enterprise use cases. where the
how we got here kind of matters as much as the
output. Remember, for a lot of projects, it's
not necessarily about the endpoint so much as
it is about the journey. So this also, I think,
signals where AI tooling is heading. We're talking
about persistent, stateful, audible workflows
instead of chat -only interactions. In other
words, we're building that history. We're building
that understanding. But on the other side, though,
this may not matter, at least for now. As it
stands today, this has niche value as best, right?
Most organizations are still struggling with
just the adoption of AI, not to mention basic
AI governance, data leakage, and probability
use cases, while Moatbook targets more advanced
users. So it's not like companies would be spitting
this up and then letting their AIs onto social
media anytime soon. This is also a crowded future
space. Think about where AI is going as an industry,
right? Major platforms, Microsoft, Google, OpenAI,
et cetera, et cetera, they're all converging
on similar AI workspace concepts, but they are
going to have deeper enterprise integration than
a notebook would. Now, I do think, though, overarchingly,
this has an impact on the future, positive or
negative. But I think this is essentially what
we're going to start seeing. AI work will become
more document -centric and less conversational.
The future is likely AI plus artifacts, not AI
plus chats. Auditability and memory will be differentiators.
And on top of it, tools like MoldBook essentially
foreshadow expectations around things like traceable
reasoning, versioning, and accountability in
a way that, quite frankly, we don't have that
now. Not with AI in terms of the output that
we are seeing when we are just getting into a
conversation with it. We are talking about artificial
intelligence that will be really truly making
a lot of decisions on its own on our behalf in
a way that a chatbot simply does not do that
now. This also puts pressure on governance models
to wrap regulation around this. Persistent AI
workspaces raise new questions about data retention,
intellectual property, especially if it's generating
things on your behalf. Model drift, which is
one of the big things I think that MoldBook might
be displaying here as the models get off their
original programming or start to learn, adapt,
and change. Do they fundamentally change themselves?
Evidentiary use as well is going to be an interesting
one. MoldBook isn't important because of scale
today. It's important because it previews the
shift from AI as a helper to AI as a structured
thinking system. Now, whether Malt Book becomes
the next Facebook for AI is less relevant, I
think, than the direction it is pointing AI in
for the future. And that is your deep dive. And
please like, share, follow me here on Facebook
and Twitter at NickAESP. And please feel free
to subscribe to me at YouTube as well. And maybe
I should set up a Malt Book AI where you can
interact with me there. And as always, stay safe,
stay online, and please, please, please, I'm
going to say private, secure, and informed. Take
care. Would you like to join us on the security
box email list? Several of us will post articles,
several may comment on the articles, and you're
welcome to join us to talk about what interests
you. Post articles, join the discussion, and
maybe learn something that you might not have
learned before. The subscription process is fairly
easy. Just send a blank email to thesecuritybox
-subscribe at 986themix .com or find a link to
the security box at 986themix .com under the
list for social media. This service is part of
986themix's email list. Come join us today. Want
to join us each week? Well, join us on Team Talk
on Wednesday, 11 a .m. Pacific Time, 1 p .m.
Central Time, where you can participate on the
live taping of the Security Box. What server
are we going to be on? Great question. we're
going to be on 98 .6 The Mix's Team Talk server,
whose information can be found at 986themix .com.
You do need to have an account on this server,
and if you don't, follow the instructions to
get one. So come join us each week. 986themix
.com. our TeamTalk server in the Security Box
channel. And thank you so much for listening
to the podcast edition of our program. We would
like to thank the following podcasts and or news
websites for the articles in which we may use
or blog. You may find links to these under podcasts
and sources we use on our website at emailhostsecurity
.com Ars Technica Bleeping Computer. Cybernews
.com. Cybercrime Radio. CyberScoop. Krebs on
Security. Kim Commando, the Digital Goddess.
The Cyber Wire from N2K Networks. And... the
Fish Labs blog. If you have found something that
is not listed here that we should be looking
at, please let us know by sending an email with
the link to the main webpage. You may either
send your email to J -A -R -E -D -R -I -M -E
-R at 986themix .com or tech, that's T -E -C
-H at M -E -N -V -I dot O -R -G. Thanks, resources,
for all you do. to put the information out so
we can share what you and others have to say
in this industry. Thank you for listening to
The Security Box. This is Jared Reimer. We hope
you enjoyed today's program, and we hope to see
you again on another edition of the program next
time. We would like to thank the following affiliates
for airing our program. The main network, 98
.6 The Mix on the independent channel. If you
are airing our program and your network is not
listed here and you would like us to give you
credit for airing our program, Please contact
me. I would like to do my best to make sure that
all affiliates get credit for airing the program.
Please feel free to contact me using the contact
information given during the program. It is open
to all listeners, no matter what network you're
listening on. Now, stay tuned for a few tracks
on the independent artist side to round out the
podcast. See you next week. And thanks again
for listening. Thunder in his footsteps, lightning
in his fist. Our God is an awesome God. And the
Lord wasn't joking when he kicked him out of
Eden. It wasn't for no reason that he shed his
blood. His return is very close and so you better
be believing. Our God is an awesome God. Our
God is an awesome God. Awesome guy. No. Jesus.