Latest / Encrypted Ambition: Where Ambition Meets Encryption - Inside The Minds Of Disruptors. / 03-23-22_Why You Should Pay Attention to the Oauth Hack

Transcript

03-23-22_Why You Should Pay Attention to the Oauth Hack · Encrypted Ambition: Where Ambition Meets Encryption - Inside The Minds Of Disruptors.

• 0:14
  Erin: Welcome to today's PTG podcast, where we talk about the latest breaking cyber news.
• 0:20
  Erin: And.
• 0:21
  Erin: I was just reading where it says that, it looks like Russia.
• 0:25
  Erin: Is laying the groundwork for cyber attacks on us infrastructure.
• 0:29
  Craig: yup.
• 0:29
  Erin: So I know yesterday we were talking, I was like, oh, I wonder if they're going to hit small companies but really, again, looking at colonial pipeline, they could hit just about anything
• 0:39
  Craig: I don't know if you saw this, but there was already.
• 0:41
  Craig: Some evidence of scans.
• 0:44
  Craig: Against, I think the top five energy companies in the United States.
• 0:48
  Erin: No, I didn't see that.
• 0:49
  BJ: Yep.
• 0:50
  BJ: The FBI reported that they literally have proof that they scan the systems for software vulnerabilities, which again is why we so strongly suggest using the right tool.
• 1:00
  BJ: Because even when vulnerabilities are found in software there's tools that can help to prevent, exploit even in the presence of vulnerability.
• 1:07
  BJ: Cause some of these software tools are very intelligent.
• 1:10
  Craig: Yup.
• 1:10
  BJ: It's really astonishing.
• 1:11
  BJ: while we do know that right now, there's not a silver bullet, although we may be getting close to it.
• 1:15
  BJ: There's so many advancements happening in quantum computing last night, I was up just literally dropped to the floor.
• 1:21
  BJ: Some of these advancements are just groundbreaking, but while we don't have a silver bullet right now, It's really shocking to see that such critical places as our power grids and it's things like that, that our nation relies so heavily upon not using the best tools available.
• 1:35
  BJ: That is really shocking, the best tools available right now.
• 1:38
  BJ: We know what they are and they're not using them.
• 1:40
  Erin: I feel like a lot of it is relationships versus common sense almost.
• 1:45
  Erin: So it's if they have existing relationships with vendors, even if it's not the right choice we've worked with some people too that were maybe a little behind the times.
• 1:54
  Erin: It seems like a lot of things that are government related are really behind
• 1:59
  BJ: You started tracking all the red tape and all that.
• 2:01
  BJ: And then you don't have the swift ability to act the mobility and the agility that's required to stay aligned with the cutting edge and keep yourself protected, you start to fall behind
• 2:11
  Craig: I think it's similar to medical too, where a lot of those systems are they have big control systems and they're probably using outdated.
• 2:18
  Craig: Sadly, probably Microsoft's windows operating systems that are outdated.
• 2:22
  Craig: Gosh, they're probably still using windows XP in certain situations.
• 2:25
  Craig: you'd be surprised the statistics of people still using ancient operating systems like that.
• 2:30
  Craig: And I think the big picture here is that you just can't connect those things to the internet, give them free reign.
• 2:36
  Craig: When there are so many security holes there.
• 2:39
  Craig: And that's why like BJ was saying what the XDR, that's a nice layer.
• 2:43
  Craig: Not going to protect against everything, but at least it's more effective solution at detecting exploitation of some of these weaknesses and visibility.
• 2:51
  Craig: And then, certain situations, you might not be able to patch a scatter system for example, but.
• 2:55
  Craig: At least you have that sock.
• 2:57
  Craig: And first of all, you have the technology and then you have a sock, a 24 7 security operation center US-based background checks, cybersecurity engineers watching over everything, 24 7, at least you ha if you have that type of.
• 3:10
  Craig: in place.
• 3:11
  Craig: That's going to significantly reduce the odds of a breach.
• 3:14
  Craig: It's not going to protect against everything or all situations, but like I saw yesterday, there was Microsoft reported a huge OAuth breach It's called OAuth.
• 3:24
  Craig: Oh, Off.
• 3:25
  Craig: And basically, have you ever logged into a website and it says.
• 3:29
  Craig: Instead of creating an account log in with Google or Facebook or something like that,
• 3:32
  BJ: yes,
• 3:33
  Craig: yeah.
• 3:33
  Craig: So that's what OAuth.
• 3:34
  Craig: is.
• 3:34
  Craig: That middleware that allows you to skip the account creation process.
• 3:40
  Craig: by granting access to one of the things, your username password for one of the other platforms, and then authorizing it by API.
• 3:47
  BJ: Okay.
• 3:48
  Craig: So that was breached.
• 3:49
  Craig: And that was confirmed yesterday.
• 3:51
  Craig: this is a perfect example of something like XDR, this would be out of scope, right?
• 3:55
  Craig: So that's on a cloud hosted, probably a big provider like micro.
• 3:58
  Craig: You and I are not going to have access to their security, right?
• 4:01
  BJ: explain that for a second though, please, Craig, because that's becoming very prevalent on the way.
• 4:05
  BJ: I've you see that with a lot of sites now where you can log in with Google or Facebook or apple even.
• 4:10
  BJ: And so whose technology is that?
• 4:12
  BJ: And is it centralized?
• 4:13
  BJ: What is the vulnerability.
• 4:14
  Craig: no, I think it's an open source middleware.
• 4:17
  Craig: layer that typically uses what's called API technology to link two systems together.
• 4:23
  Craig: And it basically more rapidly allows for user creation and onboarding.
• 4:28
  Craig: of you creating A unique username and password, you would reuse your Facebook login or your Gmail login, for
• 4:35
  BJ: But is that technology owned by the same place and reused by all these different apps that use it?
• 4:40
  BJ: Or is it different?
• 4:41
  BJ: Although places it's used or.
• 4:43
  Craig: No, I think it is centralized.
• 4:45
  Craig: I'd have to research it to know for sure, but I'm pretty sure that it's a centralized layer.
• 4:49
  Craig: almost like a Microsoft that.
• 4:50
  Craig: out with it.
• 4:51
  Craig: It might be open source though.
• 4:53
  Craig: I'd have to research it.
• 4:54
  Craig: All I know is that it's a middleware kind of software that allows the user to bypass the unique credential creation on the site.
• 5:01
  Craig: By leveraging.
• 5:02
  Craig: I never used to like it, to be honest with you.
• 5:04
  Craig: I've really not used that function before, because I always thought if they get breached, then.
• 5:09
  Craig: You know that's a problem.
• 5:10
  Craig: And then here we are, they got breached yesterday.
• 5:13
  BJ: Wow.
• 5:13
  BJ: I've been seeing an uptick in the presence of that API.
• 5:17
  BJ: I used to see it once in a while.
• 5:19
  BJ: And now I see it on almost every platform I use almost every platform offers me to log in that way.
• 5:24
  Erin: I've thought about that.
• 5:25
  Erin: I'm like, Do you and then You can change You want this to use Facebook or whatever.
• 5:30
  Erin: And I'm like, yeah.
• 5:30
  Erin: Then I'm like how does this work?
• 5:32
  Erin: I've never actually looked into it.
• 5:33
  BJ: I use it all the time personally.
• 5:35
  BJ: Cause I've been seeing it so much lately and it's so convenient, because gosh, that account creation step is such a hassle it's just so tiresome to do it over and over again.
• 5:43
  BJ: But here we go with the convenience versus security thing, we'll have to do some research and see who's technology.
• 5:48
  BJ: Is it, and is it one piece of technology that's being used over and over again by lots of different platforms?
• 5:54
  Craig: Yeah.
• 5:54
  Craig: again, I'd have to research it to know for sure.
• 5:56
  Craig: I don't know if the breach was associated with just the OAuth layer itself or was it.
• 6:02
  Craig: O auth with Microsoft or OAuth with Google.
• 6:05
  Craig: I don't know if all of the systems were breached.
• 6:07
  Craig: I just know that.
• 6:09
  Craig: Prior to yesterday.
• 6:10
  Craig: I knew there were some vulnerabilities and risks there.
• 6:12
  Craig: But then I saw the news yesterday that there was a breach.
• 6:15
  Craig: So, let me see here.
• 6:17
  Craig: Lapsis L a P S U S dollar sign.
• 6:20
  Craig: Lapses hacking group.
• 6:22
  Craig: Breached Microsoft and an authentication from Okta.
• 6:25
  Craig: Is called Okta.
• 6:26
  Craig: So it looks like that's one single company.
• 6:29
  Craig: it must be centralized one centralized company.
• 6:31
  BJ: So also big news yesterday was the Greek public postal system was hit with ransomware and their services were offline.
• 6:39
  BJ: So literally people were not getting mail, I guess their public postal service was offering.
• 6:44
  Craig: Yeah, I saw that.
• 6:45
  Craig: I'm going to share my screen here and I'll show you.
• 6:47
  Craig: Can you see that?
• 6:48
  BJ: Yes.
• 6:48
  Craig: So this is right on okta.com website.
• 6:50
  Craig: This is their statement.
• 6:52
  Craig: They're looking to do a thorough investigation.
• 6:54
  Craig: About the hacker group.
• 6:55
  Craig: So it says that a small percentage of customers, approximately 2.5% have been impacted.
• 7:00
  Craig: And their data may have been viewed or acted upon.
• 7:03
  Craig: So they have a breach.
• 7:04
  Craig: It looks like their initial investigation says it's 2.5%, they'll have to do their forensics to figure out if it was really more than that or not.
• 7:11
  BJ: we know just from how breaches work, that what the initial picture looks like is not always accurate
• 7:16
  Craig: what's strange though, It's they go over here and say, Octa service has not been breached.
• 7:21
  Craig: fully operational.
• 7:23
  Craig: So it's confusing.
• 7:24
  Craig: So was it preached or not?
• 7:25
  BJ: So it sounds like they're saying that a small portion of customers got breached, but not their technology somehow.
• 7:31
  Craig: Yeah, I don't know I have to study this some more.
• 7:33
  Craig: I think what they're saying is Only 2.5% of their customers were affected.
• 7:39
  Craig: but what's weird is they don't use the word breach there and then they say here, That it wasn't breached down here.
• 7:45
  Craig: So it's confusing.
• 7:47
  Craig: we'll have to just wait and see what the final.
• 7:49
  Craig: Report says.
• 7:50
  Craig: but other websites were saying that it was breached.
• 7:52
  Craig: So I don't know.
• 7:53
  Craig: It's early to tell
• 7:54
  BJ: Yeah
• 7:55
  Erin: I'm taking away from this, and I could be wrong of course, but it sounds to me almost like they were breached, but they don't necessarily know the extent of the breach, because it says that they're looking into the claims that.
• 8:07
  Erin: the hacker group breach them.
• 8:10
  Erin: So to me, it sounds like.
• 8:11
  Erin: they.
• 8:11
  Erin: don't know yet.
• 8:12
  Erin: They can probably say this with honesty, but it seems like it might be a little misleading and maybe I'm being a little bit cynical, But that's kinda what it sounds like to me.
• 8:21
  Craig: So if you pull up another website, like here, CNN.
• 8:25
  Craig: It says Octa concedes, hundreds of clients could be affected by breach.
• 8:29
  Craig: And then it says here on wall street journal, this was an hour ago.
• 8:32
  Craig: Okta says hundreds
• 8:33
  Erin: Yeah.
• 8:33
  Craig: customers may have been caught in a hack.
• 8:35
  Craig: Or in hack.
• 8:36
  BJ: Yeah, it says Octa has over 15,000 customers.
• 8:39
  BJ: So I'm guessing that's a lot of the platforms that we see that technology on.
• 8:43
  BJ: it seems very clear that they're scrambling to clarify what's going on.
• 8:46
  BJ: So there's not really a clear answer right now.
• 8:49
  Erin: okay.
• 8:49
  Erin: So if you think about it, they have hundreds of customers.
• 8:52
  Erin: How many.
• 8:53
  Erin: Credentials did all those hundreds of customers have.
• 8:56
  Erin: It's almost like they're trying to minimize the so if one of those is or or whatever, that It could be millions.
• 9:03
  BJ: That's a good point.
• 9:04
  BJ: Cause there are mentioning 15,000 customers so a lateral movement on a system like that when you have 50,000.
• 9:10
  BJ: Platforms that have millions of customers, the lateral movements that we know are so common in, breaches now.
• 9:17
  BJ: I'm no mathematician, but that sounds exponential to me.
• 9:20
  BJ: Microsoft confirmed that the lapses extortion focused hacking crew has gained limited access to it.
• 9:27
  BJ: Systems as authentication services provider, Octa revealed that nearly 2.5% of its customers have potentially been breached.
• 9:35
  BJ: And it sounds like Microsoft was one of them.
• 9:37
  BJ: Hacky crew has gained limited access to its systems.
• 9:40
  Erin: That's huge.
• 9:41
  Craig: Yeah.
• 9:42
  BJ: That's so interesting because not all things just seem to go in tandem because when I was talking, when we first started today about the jaw dropping advancements in quantum computing lately, they sent around the weaker.
• 9:53
  BJ: Microsoft has partnered with ion Q, they're really leading things in the contract computing space with their trapped ion technology.
• 9:59
  BJ: that's, what's going on Microsoft Azure, but also Microsoft has released groundbreaking breakthrough that their team has made in regards to topological cubits.
• 10:08
  BJ: And that's really significant.
• 10:10
  BJ: And so it's interesting that now Microsoft their systems have at least partially been breached, like how interesting, how it goes in tandem.
• 10:16
  Craig: Isn't it also interesting that these big providers like Microsoft and obviously they're in the cross hairs of the hackers.
• 10:24
  Craig: Cause there's the bigger payday, isn't it also interesting how people over to these platforms for, cloud services, right?
• 10:31
  Craig: So a lot of customers, small, medium and large enterprise have moved to the cloud and moved their information and their data to the cloud.
• 10:38
  Craig: And then now there's all these breaches that are happening.
• 10:42
  Craig: it'd be interesting to learn and understand if there's going to be a push backwards, to bring things back in house for businesses, on premise, opposed to cloud.
• 10:50
  Craig: And, I always recommend that use encryption, even when using a cloud service, because at least if you encrypt your data in the cloud and hackers breach defenses of Microsoft, for example, then at least again, it's a layered approach, right?
• 11:04
  Craig: So at least they would hit a encrypted payload.
• 11:06
  Craig: it's just interesting that.
• 11:07
  Craig: We're in this kind of dynamic where lots of companies for past decade or so have moved to the cloud because grass is greener in the cloud.
• 11:15
  Craig: Utility cost it's cheaper.
• 11:17
  Craig: I don't have to buy expensive servers anymore.
• 11:19
  Craig: And then now I think you're going to see.
• 11:21
  Craig: I've already saw some data on this, where companies are actually bringing the stuff back in house now, and they're not doing cloud anymore.
• 11:28
  BJ: That's so interesting.
• 11:29
  BJ: And here's this guys, this was buried in an article, way down deep.
• 11:32
  BJ: I find so many interesting things buried, right?
• 11:35
  BJ: Craig taught us with the settings the other day, the interesting tidbits are always buried.
• 11:39
  BJ: So I found an article last night.
• 11:40
  BJ: I have to mention that to you guys.
• 11:41
  BJ: But listen to this, it's buried in this article.
• 11:43
  BJ: This.
• 11:44
  BJ: From CloudFlare is saying this of particular concern is that the breach hadn't been reported for the last two months.
• 11:50
  BJ: So this is not new.
• 11:51
  BJ: This is only being talked about now it happened two months ago.
• 11:54
  BJ: So they've had two months of dwell time.
• 11:55
  BJ: Now this lap lapses and of particular concern to me reading this is that it says Microsoft described lots of us as a group following pure extortion and destruction model without deploying ransomware payloads.
• 12:07
  BJ: So this sounds more an attack.
• 12:09
  BJ: Seeking to destroy.
• 12:11
  BJ: They're not asking for ransoms, they're just trying to destroy.
• 12:14
  BJ: So when that happens, then when we start being state actors and things of that nature, but listen to this, I read an article last night and the headlines were totally misleading.
• 12:22
  BJ: The headlines of the article said that hackers and especially foreign threat hackers are now focusing on and the financial system and the AIS and the financial system.
• 12:31
  BJ: But when you dig into the article and start reading it, there's actually a term for it.
• 12:34
  BJ: Now it's called machine learning security, because I guess some of the AI machine learning, models that especially are used in the financial sector, those models are very bold.
• 12:45
  BJ: 'cause this is a evolving field.
• 12:46
  BJ: And so the machine learning models are vulnerable to cyber attack.
• 12:50
  BJ: And so I guess some of the state actors are actively looking to exploit the machine learning models used in the financial sector.
• 12:57
  BJ: And here's the tidbit that was hidden at the bottom.
• 12:59
  BJ: The real concern here is that they're worried that they can't.
• 13:03
  BJ: Exploit vulnerabilities in these financial machine learning models and cause them to believe certain things to be true and cause it to affect pricing on the stock markets.
• 13:11
  BJ: the algorithms that decide the pricing models.
• 13:14
  Craig: I think kind of sheds more light on is the need for code review of the coding layer of the machine learning in this case.
• 13:21
  Craig: There needs to be annual or quarterly code review.
• 13:24
  Craig: The language that's chosen Python, for example, is popular at AI and ML.
• 13:28
  Craig: But the point is that.
• 13:29
  Craig: you're not vetting and testing the code, how do you know what's really in there?
• 13:32
  Craig: It's what I've said for a long time.
• 13:34
  Craig: Like when you buy products off the shelf, you don't know if there's hidden back doors
• 13:38
  BJ: And there are techniques that they use, those heavy DVOs techniques and we know, that they became very good at social media profiles, mass amounts of fake profiles.
• 13:46
  BJ: That's the concern with the financial machine learning models that they can produce these high level.
• 13:52
  BJ: Inaccurate profiles and information and they can cause the actual machine learning algorithms models to make decisions contrary to what the financial system wants them to make based on their coding.
• 14:04
  BJ: But they're making these decisions based on the high level of inaccurate information they're being fed by the hacking teams.
• 14:11
  BJ: And so literally we're talking about.
• 14:13
  BJ: A possible upheaval of a financial system, because if the stock markets were to be affected by these machine learning models, what is the ramifications of that?
• 14:22
  BJ: Wow.
• 14:23
  BJ: We're talking about groundbreaking potential here.
• 14:25
  BJ: This is a possible upheaval of a whole system possibly.
• 14:29
  BJ: That is huge.
• 14:30
  Erin: That's definitely crazy to think about for sure.
• 14:33
  Craig: Could you imagine if some hackers changed the price to Microsoft or Google stock to a dollar, even if it was just for an hour and then if people bought it at that price, now they have supporting evidence that they paid a dollar for it or whatever.
• 14:45
  Craig: you fix that?
• 14:46
  BJ: Yeah, right?
• 14:47
  BJ: The algorithm, didn't go down.
• 14:48
  BJ: It just made a decision.
• 14:50
  Craig: I think it was six months ago where it was a glitch in the crypto system.
• 14:54
  Craig: I think it was on Coinbase And it said that I was a, truly an error or something.
• 14:58
  BJ: Yesterday, my baby, it started playing this game on his fire tablet.
• 15:01
  BJ: He's two years old.
• 15:02
  BJ: He's going to be three.
• 15:03
  BJ: And this is the one that calls himself.com dragon.
• 15:06
  BJ: He was playing this game called subway surfer.
• 15:08
  BJ: And you guys probably heard of it.
• 15:09
  BJ: I'm not a gamer, but it's a very popular game and you have to buy tokens with actual cash, you buy tokens.
• 15:14
  BJ: Some glitch happened in his tablet and he has 10 trillion tokens.
• 15:18
  BJ: My daughter She's beside herself.
• 15:20
  BJ: She's Oh, my God.
• 15:21
  BJ: And she won't give his tablet back.
• 15:22
  BJ: Cause she's bought everything.
• 15:25
  BJ: Get some goods has awarded my baby 10 trillion tokens on this game.
• 15:29
  BJ: And she's a big gainer and she's that's impossible.
• 15:31
  BJ: I've never seen that before.
• 15:32
  BJ: He's got everything you can possibly have in this game now.
• 15:36
  Erin: You better check and make sure that he didn't accidentally find a way to buy all
• 15:40
  BJ: my bank account, it would have been denied.
• 15:42
  BJ: Now I'm just hoping the same blitz happens to my crypto wallet.
• 15:45
  BJ: Sorry.
• 15:45
  Erin: Or maybe the AI will get into the stock market.
• 15:48
  Erin: Everything will go down and we'll be all be trillionaires.
• 15:51
  BJ: Yeah.
• 15:51
  BJ: I posted an article to you guys in the chat this morning about some big crypto analysts are predicting that.
• 15:56
  BJ: That crypto Bitcoin and altcoins is going to go parabolic in April.
• 16:00
  BJ: When you really look at all this, they're worried about the financial models being manipulated, and then you have a possible crypto bull run come in.
• 16:08
  BJ: Cause we've been expecting it everybody thought it was coming last summer and definitely by the winter, it didn't come.
• 16:13
  BJ: Maybe there was, who knows what was going on behind the scenes.
• 16:16
  BJ: But it seems like now there's a lot of chatter about it.
• 16:18
  BJ: And then you have the inflation, you have all this stuff, even Tesla raised their prices on their satellite internet recently space X, because of inflation and we've seen evidence of this happening with cash.
• 16:29
  BJ: And then now you have talked with the bull run with crypto and you have risk of financial models, making decisions based off whatever data they're being fed by bad actors.
• 16:37
  BJ: Are we on the verge of a perfect storm here?
• 16:40
  BJ: Oh my gosh.
• 16:40
  BJ: If I can find it quick enough, I'll read to you what Microsoft didn't post this very publicly, but they sure did put it on their research blog about this advancement, right?
• 16:50
  BJ: Okay.
• 16:50
  BJ: Here it is about their topological cubits.
• 16:52
  BJ: This is a major breakthrough and they say on their books.
• 16:54
  BJ: From Microsoft and we believe ultimately it will power a fully scalable quantum machine in the future, which will in turn, enable us to realize the full promise of quantum to solve the most complex and pressing challenges.
• 17:07
  BJ: Our society faces.
• 17:09
  BJ: This is major it's very interesting, but it sounds like they might need the help of their quantum machine to deal with their possible has happened with the AP, because I guess there's no time like the present for the machine to rise up and help.
• 17:21
  Erin: And Craig, I told BJ when we talked a little bit this morning and I told her.
• 17:25
  Erin: That if Bitcoin or crypto did take off and I do become a millionaire, I'll stay working for you.
• 17:31
  Craig: Oh, thanks.
• 17:32
  Erin: If we can do podcasts every day, we can keep doing this every day.
• 17:36
  Erin: And my boyfriend can just go build a boat somewhere.
• 17:39
  Erin: Life would be great.
• 17:40
  BJ: Last year, Craig and I spent a lot of time researching altcoins and I, to this day firmly believe that some of the decisions that were made were very smart.
• 17:50
  BJ: And even though they haven't been fruitful yet, I don't think that changes the fact that they were very smart decisions because of.
• 17:56
  BJ: Power and research and digging deep into things yields good results.
• 18:00
  BJ: There was an article popped up this morning and it says that basically, and maybe this has something to do with people talking about crypto going parabolic next month, but there was this quiet article saying that internet computers.
• 18:12
  BJ: is possibly the final layer to web three because it takes the reliance off of web two tech away because this internet, computer blockchain, it ties all the web three blockchains together and makes them interoperable.
• 18:25
  BJ: And that's the internet computer.
• 18:26
  BJ: And we know that there's the CYA coin that, has the decentralized storage and it's actually running the most transactions of any blockchain per day.
• 18:34
  BJ: And.
• 18:35
  BJ: I find that internet technology on it.
• 18:36
  BJ: And when you factor that with internet computer, that all the blockchains together, you can see yesterday, we were talking about the current tech.
• 18:43
  BJ: If you were to picture it as one, entity was a patched, a monster walking around on crutches.
• 18:47
  BJ: But then you look at what I just described there and you see something different.
• 18:50
  BJ: More like a quantum machine, possibly.
• 18:53
  BJ: So maybe it's all, at the same hour.
• 18:55
  BJ: We have a possible crypto bull run because we have that final layer with the internet company.
• 18:59
  BJ: Which is, currently down 98%, just so everyone knows FYI, we don't give financial advice, but it is down 98%
• 19:07
  Erin: I just want to ask, do you have any advice that we can give our listeners as to what to do to protect against this OAuth right now?
• 19:16
  Craig: Yeah.
• 19:16
  Craig: what I would do is I would log in to any websites that you're using.
• 19:21
  Craig: And change it, you can change it so that you can your password and, maybe create an account or set up a different email.
• 19:28
  Craig: That's secondary that's one way to mitigate the risk.
• 19:31
  Craig: So it's not affecting you.
• 19:33
  Craig: there's so much more investigation that has to happen to see, it could be too late, meaning you could be one of the 2.5%,
• 19:39
  BJ: have to be one of the 2.5% cause Microsoft was, and who's not connected to Microsoft.
• 19:44
  BJ: That's where the numbers get tricky.
• 19:45
  BJ: Because Microsoft was part of the 2.5%, but everyone's part of Microsoft.
• 19:49
  Erin: I guess too, though if that is the case, if their data is already stolen, that sucks, but maybe it's a good time to go.
• 19:56
  Erin: And like you said, update passwords.
• 19:59
  Erin: Change, the email addresses, things like that, because if they steal your credentials, you're reusing the same password and login information.
• 20:06
  Erin: They can get into whatever they want.
• 20:08
  BJ: again, a perfect time to look at the right tools.
• 20:10
  BJ: XDR cause like you pointed out Craig, it doesn't have a protection for something like this, but what it does have is the ability to change its code.
• 20:16
  BJ: Every.
• 20:17
  BJ: And be coded to look for certain things.
• 20:19
  BJ: so once we know what this breach is doing, that algorithm will be coded to look for those things.
• 20:25
  BJ: Again, the XDR is the right way to go for this kind of.
• 20:28
  Craig: Yeah.
• 20:28
  Craig: This is why I don't usually use something like That because let's give you an example.
• 20:33
  Craig: Let's say I go to a website I don't create an account, maybe I use Gmail and I click on okay.
• 20:38
  Craig: Use Gmail and skip the account creation process because it's faster and easier.
• 20:42
  Craig: The reason why I've never done it is if they have a breach, they have my Gmail username and password.
• 20:47
  Craig: So I have multi-factor set up on all my properties.
• 20:51
  Craig: So even if they got the username password, they're going to get stopped by that layer.
• 20:54
  Craig: But it's still though, like you're trusting.
• 20:57
  Craig: It goes about much do you trust each of the vendors that, you're doing business with, or if you're not even doing business and you just use their service, you still have to give them a certain amount of trust.
• 21:06
  Craig: And quite frankly, with the world that we live in now and the threat.
• 21:09
  Craig: I think we should move to more of a zero trust or a trustless, methodology where create an account on your own.
• 21:16
  Craig: Go through the extra hoops and layers, use a unique and password.
• 21:20
  Craig: Apple has recently took it a step further.
• 21:22
  Craig: they even create what's called burner emails.
• 21:24
  Craig: so, you can actually never disclose your email address create fake emails that are associated with yours.
• 21:30
  Craig: Okay.
• 21:30
  Craig: You can, as a consumer, be more stingy about the information that you give out and that'll better protect you too.
• 21:36
  Erin: Thank you for that.
• 21:38
  Craig: yeah.
• 21:38
  Craig: Let's wrap up here for today.
• 21:40
  Craig: And then we can continue on tomorrow.
• 21:42
  Erin: Sounds good.
• 21:42
  Erin: Do you guys have a great day?
• 21:44
  Craig: you too.