Why Microsoft, Google, Banks, and 911 All Went Down in 10 Days | UnHacked Ep. 112
Justin Shelley (00:11)
I still hate dancing, but I I do it because we were told that you're more nerdy if you don't. ⁓ guys, welcome to episode 112, I think we're at. Although the numbers have gotten a little bit fuzzy. We've started doing some breaking news releases here and there. And today, gentlemen, we are going to do a roll-up breaking news episode because we'd have to be like basically releasing a breaking news episode about every 15 minutes to stay on top of everything. Because
my god is shit hitting the fan. apocalypse, hackers, AI, Russians, Chinese, I don't know, but but stuff's going down. ⁓ first the good news. Does anybody know what today is? On a positive note, if you're a ⁓ I don't know, an astronaut, a space junkie. No? Today Voyager one hits one light day in distance from planet Earth.
Joshua Holloway (01:03)
No, I'm at a loss. Sorry, man.
Justin Shelley (01:10)
You know the probe that was sent out 50 years ago, I think, designed to last five years. Stuck out another 45 years, still alive, still sending data, and one light day in each direction. So when we send a radio signal to it, we don't get an answer back for two days. Today's the day. I've been following this stupid thing for quite a while. They've been ⁓ us nerdy dudes are excited about this.
Joshua Holloway (01:18)
Still ticking.
Mario Zaki (01:18)
Okay.
Joshua Holloway (01:38)
For fifty fifty fifty years you've been following it?
Justin Shelley (01:41)
Well, not quite fifty years, but ⁓ they've been talking about this one light day milestone. ⁓ I've been following that for like a year at least. Like, it's gonna be a light day. Nothing's ever been that far away. Well, I mean, I think it broke a lot of records along the way, but this is a this is a pretty cool milestone. That's it. That's all I got on the good news. Mario hit us with the bad news because we did our little breaking news on Microsoft went down, and I'm like, my god, this is huge. And like that was.
Mario Zaki (01:42)
Mm.
Joshua Holloway (01:57)
yeah.
Mario Zaki (02:09)
Yes. Yeah, that was just what everybody, you know, millions of people, three point nine million people have reported ⁓ in the US, seven point four million reported that worldwide. So that was the biggest one that everybody felt. ⁓ but just within the last ten days, ⁓ there has been dozens of different outages. Most of them are reported as
Justin Shelley (02:10)
That was a tip of the iceberg.
Yeah.
Mario Zaki (02:38)
Upgrades that ha or updates that have gone wrong, but it kind of just seems weird that they're all updating at the same time and getting, you know, issues like this. ⁓ I mean I did a quick search and and I looked for just the last 10 days the top 10. So this isn't the entire list. This is just 10 days, the top 10. You know, obviously number one was the Microsoft that I that I mentioned.
Justin Shelley (02:56)
Right. Right.
Mario Zaki (03:04)
Number two was the Federal Aviation Administration. That was on November 13th. ⁓ JP Morgan Chase and major US banks. ⁓ Software bug ⁓ on the 16th. Apple services. ⁓ you know, ⁓ that they reported an issue on the 17th, United Airlines, ⁓ Workday. ⁓ Workday is a human resource and payroll platform.
over 3,000 people had issues with their system. Charles Schwab, ⁓ the emergency 911 called dispatch. ⁓ that affected hundreds of users, Marriott International, and ⁓ the NSA Internal ⁓ Internal Communications. And again, these are just 10 within the last 10 minutes.
Justin Shelley (03:56)
And the and the common thread of every single one is that with no probing question, they all come right out and say it was not AI, it was not a data breach, it was not a state sponsored hack. It's just an update. Don't worry, these are not the droids you're looking for.
Joshua Holloway (04:17)
Well the one one other one that you forgot there, Mario, was Google. Google went down. So their their their workspace went down. I think it was today. As w as ⁓ yeah, as we're recording today.
Justin Shelley (04:22)
What? I did not hear that.
⁓ not the search, the goo.
God. Okay. So here's here's the topic of the day, guys. This is what we're gonna discuss. ⁓ it's old news. This is all like minutes old, so it's like not even worth talking about now because it's so ancient. ⁓ but what we have not resolved yet is what in the hell is really going on? Is this really just everybody upgrading their systems all at the same time? Is this some sort of a coordinated attack?
Joshua Holloway (04:33)
Hey, Google went down.
Justin Shelley (04:58)
Is it some government conspiracy? Are the aliens after like these are all theories that are getting thrown around. I want to hear you guys' take on it. What is up?
Joshua Holloway (05:10)
Not everybody speak at once.
Mario Zaki (05:11)
I mean I mean the thing is i and the no surprise, nobody's being honest. You know, you know, even when there was almost confirmed breaches, you know, nobody was admitting it until they really had to admit it. And now it it is almost like the news is get you know how like it's something on the when the news hits, it's all it's a big topic until s the something something else bigger hits. That's what's happening. Everything is just getting
Justin Shelley (05:12)
Yeah.
Yeah.
Joshua Holloway (05:38)
Mm-hmm.
Mario Zaki (05:41)
you know, frustrating and everything's getting flushed out because nobody, you know, i in a week when Microsoft and Google, you know, received major down, you know, issues, you know it's not just something that these guys have accidentally pushed update and and the whole system came down. And they're going down for for a long period of time. You know, banks and nine one one services, you know, there's definitely something going on and just nobody's admitting it. You know?
Nobody can tell.
Justin Shelley (06:13)
Josh, what do you think?
Joshua Holloway (06:16)
I think one of the other issues that it might be is they're starting to see the writing on the wall where zero days are coming out faster and faster and faster. So they're having to do these updates and they're scurrying. Typically when we patch, right, we we plan for it, you know, we try and do everything we can to cover it to make sure that when we do it live, it doesn't take down the entire network. I think those days are gone where we almost have to be patching the moment things are coming out. We had we had PHP for Shell that came out. That was a couple weeks ago, right? Well we
Justin Shelley (06:40)
Yeah.
Mm-hmm.
Joshua Holloway (06:47)
As of right now, we have a new one that just came out like yesterday, which is the Java for shell critical RCE. So we have we have a new CVE that came out. We they attacked PHP or a known vulnerability. Now we have a Java one that's coming out. So if you look up if you look at it, we have even more vulnerabilities that are coming up on our web apps or our our things that we're developing. ⁓
And they're holes, they're gaps, right? And these are zero day threats. So now people are rushing to go and close PHP. Now they have to go and close Java for shell and do the updates, the Oracle update, every update that comes with Java and and get those done and over with. I think they're just getting overloaded and they just don't know how to do it. ⁓ or or handle the workload. Because all of our stuff is written to you know, we have change management. We have like we set up these labs to do these updates to see what affects our systems, to then apply these updates.
Justin Shelley (07:28)
Yeah.
Joshua Holloway (07:42)
You know, red team the whole thing and figure it out.
Justin Shelley (07:42)
Conventional wisdom is don't do don't do updates, don't be the first one. Hold off for a week or two, right? Even a month. my God, we cannot do that anymore.
Joshua Holloway (07:47)
Great. Yep. Absolutely. Yep. Mm-mm. One thing I will point out, and it seems kind of weird to me, or maybe it's not weird. ⁓ you had PHP for shell. Now all of a sudden we have Java for shell. And if anybody's vibe coding, what are predominantly a lot of the tools that we write in or use, right? It's gonna be written in PHP, it's gonna have Java backend, you have like Node and you know.js and you have everything else in
More and more gaps, holes, and things are being found out through that. So were these bigger corporations vibe coding long before we were vibe coding and they were deploying these systems unpatched, unmitigated, you know, and they're opening these doors, and and all these AI agents are now starting to open them and figure them out because they didn't vibe code properly.
Justin Shelley (08:39)
Maybe. I heard this was a a little reel or whatever it's called, the little video clips. It depends on which platform you're on, what it's called. It's a TikTok to most of the younger guys and gals. ⁓ Vive coding's been going on forever. A manager walks into the developer and says, Hey, I want it to do this, this, this, and this. And they need it done fast. And then he walks away and then comes back. The the developer says, Here it is.
And the manager never goes and looks at the code. He never understands what's going on and never even considers security implications. Just throws it out there into the wild. ⁓ guys, we've been vibe coding since the beginning of time. It's just that we went from humans to AI, but it's the same thing. But it's the same thing. So, all right, that was just a dumb little.
Joshua Holloway (09:20)
And we can do it so much faster.
Mario Zaki (09:26)
So Josh, you you so you think that it because of these ⁓ zero days that are coming out, like these guys are actually trying to update. So are you saying there's truth behind what they're saying, that these are all just updates gone wrong?
Joshua Holloway (09:41)
I think there's a possibility. also think that there's a possibility. ⁓ I mean, how often have in the past, think of like companies like Sony, right? They were warned that they had these big gaping holes and they did nothing about it. Or they they didn't act upon it and they act or they act upon it, you know, too too late or slowly, right? I think this is what we're seeing is is we're getting zero days faster. We we can exploit them faster, and these companies have not caught up.
Justin Shelley (09:59)
Slowly.
Joshua Holloway (10:11)
To close the doors fast enough, or or do they just, I don't know, maybe it's the old adage, we're not a target, or it's not our systems, we're we're automatically being updated. You know, or what what are the old adages that you know it's my IT guy is handling it. There we go. How about we put it like that? My IT guy is handling it, we don't have worry about it. But when the IT guy comes back, even at a major corporation says, Hey, we need two million dollars to do this major upgrade to close these doors, they get denied. You know, I think it's a it's a culmination of things like that where
Justin Shelley (10:24)
Mm-hmm, mm-hmm.
Joshua Holloway (10:40)
We've gone so long being able to skirt by the skin of our teeth and just do I hate to say we're doing the bare minimum, but the companies are driving the technology at the bare minimum. And and these doors are just getting blown off with these issues now.
Justin Shelley (10:55)
No, listen, let's rat on the industry because that is one of the things I I do want this show to accomplish is to let people know what goes on behind the scenes. You write a check and you think you're secure, business owner, prove it. How do you know? Make your IT guy prove it. I because you're right, Josh, like we used to be able to have ⁓ you both have mentioned it, there used to be time to apply these updates and these patches.
There is not time anymore. And you know, like it was a roll of the dice. If you were gonna get attacked, breached, whatever word we're gonna use, it was one in two hundred, one in three hundred. Those were your odds. And and it we are moving towards, this is my crystal ball coming out again. We are moving towards a world though the you can't see that for reels. Like it's here. Okay, well it's here. Trust me. ⁓ don't verify.
Joshua Holloway (11:37)
Mm-hmm.
Mario Zaki (11:41)
Mm-hmm.
Joshua Holloway (11:42)
The one we can't see. Yeah, sorry, man. Sorry.
Justin Shelley (11:53)
We are moving towards a world where it's it is truly zero day. Like you don't have time. When the vulnerability is discovered, it's exploited immediately. In fact, that's what AI is doing. It's going out and finding new ones and exploiting them in the same process. Right? That that's what we're moving towards. We don't have time. And and not only can we not sit here and wait days, weeks, months, years after a C VE is issued or a patch is is issued.
Like we've got to go out and start fighting them ourselves. I believe we've got to start fighting fire with fire. If we're gonna if we're gonna survive this war, we have to be using AI to fight the, you know, the good AI to fight the bad AI. And the difference is guardrails. I don't know. That's that's what I think we're up against right now.
Mario Zaki (12:43)
Yeah, and unfortunately, ⁓ and we've always been against this, you know, from for years, is, you know, we always want to be proactive, not reactive. Unfortunately, some of the stuff y end up having to be reactive, you know, because something comes out, we had no way of n you know being proactive knowing this stuff because it was just never there was never a source to go in there and and and get that information then go go and do it or
Justin Shelley (12:54)
Mm-hmm.
Mario Zaki (13:12)
know about it be f ahead of time. Now news is just hitting and these vulnerabilities are just hitting faster, you know, than we could even discover it.
Joshua Holloway (13:23)
You have a valid point there, Mario. And I and it goes back to ⁓ when you said proactive and reactive. And I always think about this one thing, like when somebody's internet connection goes down, right, we're looking at the servers. We're monitoring the servers. If they go offline, the firewall goes offline. That's when we know, right? And I can remember ⁓ I know we all have received this call. Client A calls in and says, Hey, we're down.
Mario Zaki (13:40)
Mm-hmm.
Joshua Holloway (13:48)
And we're like, yeah, we we know we s we see that. And they're well, why didn't you call us and tell us? Well, and it's it's it's because our systems are monitoring you and they have to make a call, and we're mon like we're using systems to monitor you, and they have to make that call that you've gone down and there's time, right? So we're finding out the same time they're finding out because of the type of outage, right? Like like if a server starts to ball up and slowly decay or die, yeah, we may receive some notifications.
High CPU, high memory, high disk usage, things like that. We can act upon those. Those are proactive, right? We see the problem building up. We can take care of it. But when you get a hard hit, like internet goes down, power goes off. Like we're all finding out at the same time. And I can remember some clients going, well, why didn't you know it was going down? And I'm like, well, it's not like it slowly decays every time into oblivion. You know, it's like the power going off. It's not often that power slowly goes out.
Right. It's more it's a hard hit, right? And ⁓ you know, clients need to understand that sometimes it looks like we're being reactive because we're all acting at the same time. They're finding out the same time, we're finding out, ⁓ and then we're reacting to the issue. There are certain things that we can do proactive, and then there are certain things that are proactive and reactive at the same time. I guess is there a way to explain that way?
Justin Shelley (15:11)
I think what you're saying, Josh, is that listen, we learn by being reactive most of the time. W something bad happens, we learn from it, we implement proactive controls to prevent that issue from happening again. What's happening right now though is that we're finding these reactive issues so fast that we don't have time to implement them as standards to be proactive yet.
Mario Zaki (15:24)
Exactly.
Joshua Holloway (15:37)
Mm-hmm.
Justin Shelley (15:37)
In in a lot of these cases, if that makes any sense. Now I don't know if I just butchered that, but ⁓
Mario Zaki (15:42)
No, no, you're both right, yeah.
Justin Shelley (15:45)
So it it's just God, I I don't know how many times I've said these are interesting times, but it's in interesting times, gentlemen. ⁓ I want to throw one more thing out. So what we haven't talked about yet, there there is just this hysteria, the panic that we're, you know, we're being lied to. ⁓ you know, is it just coincidental that these all went down? Is it true that none of this has to do with the cyber attack and it's all updates or patches or copper can't talk to glass? my.
God, did you guys hear that one? That was that ⁓ Jesus. When when the FAA ground stop first hit and and you've got some guy, I won't I don't remember his name, I wouldn't say it if I did, trying to explain this. Really what he was trying to do is like deflect and smoke and mirrors. And he's like, What we've got is these little tiny copper lines, and they're really super old, and we're putting in glass lines, and I don't know if you know this, but copper lines can't talk to glass lines. Like, dude, just shut up and go home.
Joshua Holloway (16:16)
No, I haven't.
Justin Shelley (16:44)
You don't know what you're talking about at all. ⁓ but but all they need to fix it is $50 billion. ⁓ okay, random number. But anyways, okay, so are we being lied to? Is there any i is there truth to what they're saying? And the the fact is we won't know. The government is not known for being transparent. ⁓ businesses who get
Joshua Holloway (16:46)
Yeah, he should not be given airtime. Can can can we t can we take his airtime away because damn.
Mario Zaki (16:46)
That's just the Yeah, th that was that's probably the dumbest thing I've ever heard.
Justin Shelley (17:13)
attacked, breached, whatever you want to call it, are not known for being transparent for valid reasons. a lot of correct. Yeah. ⁓ the best we get is insurance reports. Like that's that's the information I love to get is ⁓ the insurance companies sometimes will feed us information. But what I think is wildly interesting is that right at kind of the peak of all of these, the FAA comes out.
Joshua Holloway (17:20)
The lawyers won't let be.
Justin Shelley (17:43)
⁓ I'm sorry, the FBI, not the FAA. We've already beat up the FAA. The FBI comes out with an alert. Are you guys familiar with this one? Okay. So RTEX is ⁓ an AI model that's being it was out there, it was public, it was it was for the good guys, but then the of course the bad guys get a hold of it and they tweak it and and and make bad stuff with it. ⁓ I really think we needed to keep it online so that the good guys could use it as well, but
Different conversation. So the FAA warns about this and then they come up with what you should do, right? What the FBI recommends. And I'm gonna take a minute to kind of blow our own horn here, maybe a little self shameless self-plug for the the portal we're building, and the standards that we keep talking about week after week after week after week, because while all of this stuff is new-ish, it really comes down to exploiting a lot of things that are.
We we've been talking about forever. So priority is critical. Recommendation by the FBI, not the FAA. Inventory every internet-facing application and administrative interface. See episode 77 of Unhacked. Critical priority. Recommendation by the FBI. Restrict remote administration, hypervisors, backup systems, and cloud management interfaces. See episode 78, 81, and 84.
Audit your privileged Microsoft 365 applications, service principles, and consent grants. See Episode 81. Monitor unusual sign-ins, credential additions, and privilege changes. See episode 82. All right. The system, the threats, the problems are not necessarily new. I'm not gonna say that none of it is, but for the most part, guys, we've got to get back to the basics. I keep saying that, and it keeps holding.
To be true. What are your thoughts?
Mario Zaki (19:41)
My thoughts is if you guys were w next to me, I'd be patting you guys on the back.
Justin Shelley (19:46)
Yeah.
Joshua Holloway (19:47)
Also at the same time, see episode one through one twelve covering that every time we talk about
Justin Shelley (19:50)
Correct. Yeah. So I'm I'm gonna we're gonna kinda wrap up. I wanted today to be a little bit short. Do you guys have anything that you feel we've missed? ⁓ if not, I'm gonna kinda bring this thing home.
Joshua Holloway (20:06)
I think the only thing I would I would say and add it, it's the same thing we're talking about, right? Work with your IT guy, understand what's going on, or w work with your IT company, your IT department, whatever it is. If you can't figure it out, there's a couple of guys here on this podcast that would be more than welcome to talk to you about it. But work with them to better understand your technological footprint and what's being done to protect you. Because at the end of the day, everybody's a target, no matter how big or small, and these doors are are being found through all of these scanning and
And work with company like ours who's taking the time, the effort, and putting the blood, sweat, and tears into what it takes to truly lock down your systems, to truly protect you as much as possible and and and get you in a good cyber security footprint and and and and standing, right? You're you're being updated regularly, your doors are being closed, they're auditing what's going on, and they have a good understanding. Because if your guy
or your person or your gal, whoever it is comes back to you and they hesitate, they stutter, or they just don't know. It's not the person to be working with.
Justin Shelley (21:12)
Well that's that's your answer. If if they can't give you a detailed answer, that is your answer. Mario, any any final thoughts on this?
Joshua Holloway (21:17)
A soft person.
Mario Zaki (21:20)
Yeah, I mean, for years now we would always hear when we ask somebody like, Yeah, w you know, our IT guys on top of it, you know? And a way to people have judged that is because they didn't go down. You know, they didn't have issues, you know, they weren't, you know, compromised. You know, those days now are are kind of long gone. You you need to be able to see what though what these guys are doing because if you can't see it
Justin Shelley (21:35)
Mm-hmm.
Mario Zaki (21:48)
Then there's a problem. Before it's like no news is good news, everything was, you know, as long as everything was running, everything was closed, everything was updated. Now you you need to know what what have you done? You know, like every every vendor, every employee is always held accountable for their work. This does this is not an exception. You know, just because it it you didn't have an issue doesn't mean that the it tomorrow is gonna be the same way.
Joshua Holloway (21:53)
Mm-hmm.
Mario Zaki (22:17)
Or on Friday is gonna be the same way, or next week is gonna be the same thing. Because it is now beyond just having MFA on on your 365. It is now all these other things that have been piling up. I mean, I I read a list of 10 things that happened, and it actually I wrote within 10 days, but most of the stuff was within within the last five days. Okay. ⁓ it is if these guys
Joshua Holloway (22:42)
Mm-hmm.
Mario Zaki (22:46)
Are having issues, I guarantee you there's a million other people that are having very similar issues. They're just not big enough to the
Joshua Holloway (22:54)
Mario, I actually I'm gonna cut I'm gonna cut in for one quick second. To Mario's point, there's one other one other thing I want to add. In my or in our industry, when somebody is so tight to the cuff, holding data away from anybody, management that asks, if you have a an employee or a MSP or somebody that you work with, and we I refer to this as Dungeon Master Sendrum.
Justin Shelley (22:55)
And ⁓ go ahead. Yep.
Joshua Holloway (23:20)
They hold the keys to the castle. They hold all of the data so close to their skirt or so close to their chest that they won't share that information. Those days are gone. Those guys need to be replaced. They, they, you need a more transparent IT department that you can work with because Dungeon Master Syndrome, I think, has gotten us to this problem where they're holding on to everything. They don't want to give up information because they think it's job security. And I think it's the fastest way to get fired. And and and we've replaced people, it should be.
Justin Shelley (23:45)
Yeah. Should be, yeah.
Joshua Holloway (23:50)
And we've replaced companies and and and departments because of Dungeon Master Syndrome, because they won't share information. And sorry, I just wanted to add to that because Mario hit it on the head, Justin. Go go ahead.
Justin Shelley (24:01)
Yeah, Dungeon Master Syndrome. I'm gonna have to figure out a word how to work that into the marketing. ⁓ but no, that was that was a perfect commercial, Josh. And now we're gonna break to ⁓ the the the the device. Yeah, our our sponsor today is the security appliance we're building that will sit on your desk, Mr. and Mrs. Executive, and will show you your company's score as reported by
Mario Zaki (24:13)
Sponsor.
Joshua Holloway (24:16)
Yeah.
Justin Shelley (24:29)
The responsible party, whether that's you, your IT team internal, your outsourced IT team. And that's not good enough because the final level is to have a third party verification of everything that ⁓ the first person you're writing check to ⁓ promises. So when somebody says, Hey, how do you know you're secure? You can just pick this thing up and show them.
And you can scroll through the frameworks and you can show them what's signed off and what's not signed off and where your risks are. And if you see something that's not right, you just tap that screen and it schedules an appointment with the person in charge. ⁓ and we start closing those gaps for you. So ⁓ that is what ⁓ what is on the horizon. I've kind of been teasing this thing for a while, but it is time for our industry to be more transparent. It is time for us to up our game. Guys, we have to elevate this industry because it's a mess.
And and and it's not just us, it's in house, it's government. Like I I don't wanna like really kick salt in the wounds or or whatever, beat a dead horse, whatever you wanna say. But Jesus Christ, FAA, you're replacing equipment that is twenty to thirty years old. Come on. Like that's all we need to know. Come on.
Joshua Holloway (25:41)
Yeah. Yeah.
Mario Zaki (25:44)
Yeah. Yeah.
Justin Shelley (25:45)
There's no excuse for that. This this industry is a disaster ⁓ inside and out, and we gotta fix it. That's that's my personal mission. So I'm just gonna keep pounding that drum until we put everybody else out of business and we're the only ones left. ⁓ anyways. No, I listen, I ⁓ it's why I keep opening this up to other MSPs as well. This is not something that I'm trying to keep my cards to my chest.
Joshua Holloway (26:00)
Yeah.
Mario Zaki (26:01)
Mm.
Justin Shelley (26:10)
I want this industry wide. I want the transparency to be something that becomes the standard. That's what I think we should be going for. All right, guys. Yeah.
Mario Zaki (26:18)
Yeah, and that's what we're working on. We're we're working on making the the a new standard, you know, and a more elevated standard, not just do you have enough air?
Joshua Holloway (26:18)
Absolutely.
Justin Shelley (26:24)
Yes, absolutely.
Peer reviewed and peer verified. So that's what's coming. Guys, as always, thank you for being here. I think we're gonna wrap up only to you know get back on here and record tomorrow. This one will publish, ⁓ I'm not even gonna try to jump in the time machine today. ⁓ but we we're we're a little bit behind schedule due to FAA groundstop because I was flying when we were supposed to record. ⁓ that's why this week's late.
Joshua Holloway (26:32)
Yep, absolutely.
Justin Shelley (26:55)
But we're gonna get back on track. We've got holidays coming up. ⁓ but we're gonna keep bringing you content because there's no days off, unfortunately, in this world. Say goodbye, gentlemen. ⁓ if you missed anything, say it now. I'm gonna play some music and we're gonna get the hell out of here.
Joshua Holloway (27:09)
Goodbye, everybody.
Mario Zaki (27:10)
Bye guys.
Justin Shelley (27:12)
I thought it would be deeper than that.
Joshua Holloway (27:14)
Unhacked.
Mario Zaki (27:14)
Unhacked.
Creators and Guests