CyberWire Daily - Solution Spotlight: Rebuilding trust in the wake of tech calamities. [Special Edition]

Episode Date: November 10, 2024

In this special edition of our podcast, Simone Petrella sits down with cybersecurity luminary Alex Stamos, Chief Information Security Officer at SentinelOne, to delve into one of the most challenging ...years in tech history. 2024 has seen unprecedented breaches of multinational corporations, high-stakes attacks from state actors, massive data leaks, and the largest global IT failure on record. As both a seasoned security executive and respected thought leader, Stamos offers a firsthand perspective on how the security landscape is evolving under these pressures. In this exclusive keynote discussion, Stamos draws from his extensive experience to share hard-won lessons from the upheavals of 2024, discussing how companies can build — and rebuild — trust amidst this environment of constant threat. What new responsibilities do organizations have to their customers, employees, shareholders, and society? And what major shifts can we expect across cybersecurity and IT practices in response to these cascading challenges? Tune in for a deep dive into how security professionals are rising to meet their roles in a world brimming with motivated and capable adversaries. Learn more about your ad choices. Visit megaphone.fm/adchoices

Transcript
Discussion (0)
Starting point is 00:00:00 You're listening to the Cyber Wire Network, powered by N2K. Air Transat presents two friends traveling in Europe for the first time and feeling some pretty big emotions. This coffee is so good. How do they make it so rich and tasty? Those paintings we saw today weren't prints. They were the actual paintings. I have never seen tomatoes like this. How are they so red? With flight deals starting at just $589, it's time for you to see what Europe has to offer.
Starting point is 00:00:31 Don't worry. You can handle it. Visit airtransat.com for details. Conditions apply. AirTransat. Travel moves us. Hey, everybody. Dave here.
Starting point is 00:00:44 Have you ever wondered where your personal information is lurking online? Like many of you, I was concerned about my data being sold by data brokers. So I decided to try Delete.me. I have to say, Delete.me is a game changer. Within days of signing up, they started removing my personal information from hundreds of data brokers. I finally have peace of mind knowing my data privacy is protected. Delete.me's team does all the work for you with detailed reports so you know exactly what's been done. Take control of your data and keep your private life private by signing up for Delete.me.
Starting point is 00:01:22 Now at a special discount for our listeners. private by signing up for Delete Me. Now at a special discount for our listeners, today get 20% off your Delete Me plan when you go to joindeleteme.com slash n2k and use promo code n2k at checkout. The only way to get 20% off is to go to joindeleteme.com slash n2k and enter code n2k at checkout. That's joindeleteme.com slash n2k code n2k. And now, a message from our sponsor, Zscaler, the leader in cloud security. Enterprises have spent billions of dollars on firewalls and VPNs, Thank you. that are exploited by bad actors more easily than ever with AI tools. It's time to rethink your security. Zscaler Zero Trust Plus AI stops attackers by hiding your attack surface, making apps and IPs invisible, eliminating lateral movement,
Starting point is 00:02:41 connecting users only to specific apps, not the entire network, continuously verifying every request based on identity and context, Thank you. organization with Zscaler, Zero Trust, and AI. Learn more at for this N2K CyberWire special edition. In today's Solution Spotlight, N2K's Simone Petrella interviews Alex Stamos, CISO at Sentinel-1. They got together at the ISC2 Security Congress 2024 to discuss lessons learned in 2024 and what it could mean for 2025. So we're here at the ISC2 Security Congress for 2024, and I know you are going to be chatting with the audience, both in person and virtually here in a bit. But one of the things I wanted to start with was, you know, 2024, where the landscape kind of started. And what, in your opinion, were some of the more significant breaches or attacks of 2024 that are shaping the way that we think about the cybersecurity industry? Yeah, we've had kind of a crazy year.
Starting point is 00:04:24 So the keynote today is I'm pulling three incidents out. being the way that we think about the cybersecurity industry. Yeah, we've had kind of a crazy year. So the keynote today is I'm pulling three incidents out. Not all kind of traditional breaches, you know, one of them is. But three incidents I think has really shaped the cybersecurity landscape and I'm pulling different lessons out. So those three things are I'm talking about the Cyber Safety Review Board's report of the Chinese intrusion into Microsoft and the follow-on Russian intrusion into Microsoft. But especially the lessons to learn of what happened with China and Microsoft, which actually happened last year. But the report came out this year and has a lot of lessons for us. The multiple security incidents that came out of the Snowflake multiple breaches,
Starting point is 00:05:10 not of Snowflake themselves, but other customers. And then the massive CrowdStrike outage, which has had real massive repercussions for the security industry and for CISOs that deploy security products. Well, I think it's a great segue because as a CISO, now on vendor side, but also having been within the corporate side as well, what are some of the things that you think you're taking away as a CISO when you think about those events?
Starting point is 00:05:39 Yeah, so I'll take those in order. So the, you know, the Microsoft one, I mean that, you know, so the, I recommend all CISOs to read if you haven't yet, the Cyber Safety Review Board's report about Microsoft. Now, you know, the technical specifics are very specific to Microsoft, right? These are bugs that are specific to how did Microsoft build their authentication system for Office Online and how were their keys stored and stolen by the Chinese and then eventually used to read the email of people who worked for the U.S. government. It was eventually, you know, this is not a breach that was discovered by Microsoft.
Starting point is 00:06:11 It was discovered by folks who worked for the government and then told Microsoft that it happened. But the lessons that everybody can learn, even though the bugs are specific to Microsoft, are a couple. One, half-finished security projects will kill you, right? If you look at, like, step-by-step of what happened inside of Microsoft,
Starting point is 00:06:32 almost everything in there, Microsoft knew about, and they were working on it. They just weren't done yet, right? And, you know, one of the things I'm going to have do, you know, for a little audience participation in the keynote today, is I'm going to have everybody raise their hand if they don't have partially finished projects on their risk register. Right. And I expect nobody to raise their hand. Um,
Starting point is 00:06:53 this is just true for any CISO is we have things that we, we know are weaknesses that we've been working on and perhaps for years, right? It's, it's sometimes it's easy to get to 80% done, 90% done. It's like a windows progress bar. You's easy to get to 80% done, 90% done. It's like a Windows progress bar. You can get to 99%, but actually finishing, turning off that last server, getting rid of that last key
Starting point is 00:07:13 is impossible because you have some dangling dependency. And one of the lessons there is like, the attackers don't care if you're 99% done. If that key works, if that server's up, they'll use it, right? And so that's one of the lessons I think that's really important there
Starting point is 00:07:29 is like sometimes you have to push through that last 1% because that residual risk is so big. I'm sure Microsoft wishes that they had pushed through whatever it is that last little bit that kept them from turning off that old 2016 encryption key would have saved a lot of pain for them. It sounds like the adage,
Starting point is 00:07:48 like kind of if everything's a priority, then nothing is a priority. Yeah, exactly. Another lesson there is like, we've built really flat, homogenous networks, right? You know, cloud computing is great in a lot of ways, but what's happened is the, you know, the biggest beneficiary has been Wall Street, right?
Starting point is 00:08:05 Is that Wall Street has forced CIOs to kind of squeeze out all of the excess cost of running IT. And so you have IT budgets at public companies. They've gotten rid of all the fat. And now you have a small number of people providing services to a huge number of internal customers. And the ratios of the number of system ends or dev op engineers versus the number of containers or end systems is spectacular. Thousands and thousands of machines per admin. And that's great until a bad guy gets their hand on one of those systems, right? And so, like, one of the
Starting point is 00:08:45 things we'll be talking about in the keynote is, like, friction is not necessarily a bad thing, especially at the administrative level, is that we got to embrace friction a little bit more. You know, Microsoft, in this situation, built keys that worked across every single one of their customers. And so, if they had built a little less of a homogenous system, they would have had natural firebreaks in there, and it would have cost them more. It would have been a little less of a homogenous system, they would have had natural firebreaks in there and it would have cost them more. It would have been a little more difficult in some ways, but it also would have meant that it would not have been so easy
Starting point is 00:09:11 for the Chinese government to penetrate their systems. And again, there's specifics that are specific to Microsoft, but you see the same pattern at every company of, well, why not just make everything flat and easy because it's so much easier and simpler for us. And I think that's a natural progression of where cloud has taken IT architectures. But the reality is we just got to see
Starting point is 00:09:35 that there is a natural benefit to friction, especially at the administrative level. I know you also are going to talk about Snowflake, but do you think that that's a friction that we also should be embracing as a cybersecurity community and industry too? Because your third example is CrowdStrike, and that's an example where it behooves a frictionless environment to have one primary provider, but when it's tied to something that it's so fundamental to what we actually rely
Starting point is 00:10:01 on. Yeah, I mean, that's a great example of, you know, the fact that it is very likely for a company to have one EDR product means that if it breaks, if it either fails because it misses something, it misses it everywhere. And if it breaks, it breaks all your systems at once. Now, you know, CrowdStrike in particular made specific, you know, they made specific architectural decisions that were extremely risky.
Starting point is 00:10:21 And I think, you know, they certainly are not going to make the same mistake again. And I think most companies would not make that mistake, but you still could see failures from products where you can have, you know, every EDR product is at some kind of conflict or something. And certainly they all miss things, right? And I do think that has raised up the question for people
Starting point is 00:10:44 of like, hey, should we, you know we maybe go 50-50 with security products? Certainly, a number of companies have decided, great, our primary and our business continuity sites are going to run different security features. I know like one of those airlines that was involved, they had like an operation center that was this beautiful operation center that had, you know, rows and rows of computers where these professionals work very, very tirelessly to, you know, move airplanes around and move crews around and like deal with, oh no, there's a hurricane coming. So we've got to reroute everything. And, you know, they work incredibly hard to do that. And they had CrowdStrike on all the machines. And then they have an identical operation center 30 miles away, and has its own generators, its own power grid, but they're also running CrowdStrike.
Starting point is 00:11:27 So it doesn't matter that everything was physically separate. Within seconds of this entire building blue-screening, the second operation center blue-screened, they will not make that mistake again, right? That second operation center is going to have different security products, different firewalls, different switches.
Starting point is 00:11:42 Now, you can't get rid of Windows. Microsoft has a monopoly there. But what you can do is you can run on a different Azure tenant. You have a different Intune tenant. You can run N-1 patching for Windows. And so I think this is, again, we're having non-homogenous networks of embracing friction, of having your primary and your BCP site be quite different from an IT perspective. It's a big pain. This is where system integrators might come into handy, where you end up paying a system integrator to run your BCP site for you
Starting point is 00:12:08 and to make it as different as possible is going to be worthwhile. We'll be right back. Do you know the status of your compliance controls right now? Like, right now. We know that real-time visibility is critical for security, but when it comes to our GRC programs, we rely on point-in-time checks. have continuous visibility into their controls with Vanta. Here's the gist. Vanta brings automation to evidence collection across 30 frameworks, like SOC 2 and ISO 27001. They also centralize key workflows like policies, access reviews, and reporting,
Starting point is 00:13:03 and helps you get security questionnaires done five times faster with AI. Now that's a new way to GRC. Get $1,000 off Vanta when you go to vanta.com slash cyber. That's vanta.com slash cyber for $1,000 off. And now, a message from Black Cloak. Did you know the easiest way for cybercriminals to bypass your company's defenses is by targeting your executives and their families at home? Black Cloak's award-winning digital executive protection platform secures their personal devices, home networks, and connected lives. Because when executives are compromised at home,
Starting point is 00:13:56 your company is at risk. In fact, over one-third of new members discover they've already been breached. Protect your executives and their families 24-7, 365 with Black Cloak. Learn more at blackcloak.io. It's hard for me to think about this conversation and not think about the impact that this kind of has on the workforce for 2024, 2025. So ISC2 has released their workforce study. It's kind of the first year that things have stagnated from a cybersecurity professionals globally standpoint. It's actually been decreasing a bit in the United States. Are we getting to the point that a lot of these friction points should also kind of be a reminder to get back to the principles of we also need to spend enough time having redundancy in the humans that we
Starting point is 00:14:49 actually have performing this work. Right. Yeah, no, I think so. And I think the CrowdStrike outage proved that. I mean, that's one of the things all these people learned was it's great to have one admin per 10,000 boxes until you have to reboot 10,000 machines. Like, you know, some of those airlines, you know, weeks later, I was still seeing blue screens in airports. And it's because they don't have the people to go out there with USB keys. Yeah, we'll leave the burnout conversation for another day. Yes, right.
Starting point is 00:15:14 But it's, I mean, it is a legitimate issue of like when things go wrong. Yes, one to 10,000 is a ratio that totally works and everything's working perfectly. And when it hits the fan, you know, not having that kind of slack space is a problem. And I do think we have cut too quickly. People have, I think, made assumptions around automation and hyper automation and orchestration systems and such that aren't necessarily accurate. And I do see this all the time with companies that in, you know, before I took the CISO role at SentinelOne, I was supervising the DFR team and working with companies from a consulting perspective. And I would deal with breaches all the time where they did not just have the right security people. They didn't have the it capacity to deal with a breach, right? It's like, Oh, we've got to
Starting point is 00:15:57 rebuild laptops. We don't have the people we've got to rebuild our, uh, you know, our Oracle database and our production systems. We don't have the people because we barely have enough people to keep things ticking over normally because we've cut to the bone. And so I do think, and you will pay out the nose when you call PwC or Deloitte on a Friday evening at 6 p.m. to help you recover from a ransomware incident. They will charge you the maximum amount possible. And in the end, the CFO will not see that savings over the five-year period that they thought they would get from cutting all those IT folks. So I do think CIOs need to be thinking, looking at the big picture of what it is like when you go down to having 95% of the people necessary to run during normal operations,
Starting point is 00:16:37 because over a five-year period, nobody just has normal operations. Something bad will happen every six months, and you need to have the slack space to be able to handle that. Yeah. Hard to keep that long-term perspective in mind sometimes. So when you're trying to justify your budget in front of the CFO, who's like, well, it's been two years, nothing's happened. So you're like, oh, well, you're going to penalize me for doing a good job. Yeah. Yeah. I mean, I can make something happen, right? Like it's definitely not the kind of, yeah. It'll be interesting to see what happens when you do that. Yes, exactly. Okay. What changes do you anticipate in the cybersecurity field as we look towards 2025 as a result of some of the challenges we did face this year? Do you see anything changing
Starting point is 00:17:13 as a result? Are we going to make headway on some of the barriers we've had? Yeah. So, I mean, I think for security vendors like ourselves, there's a lot more questions being asked about how are we not blowing things up. So, you know, one of the things I talk about in the keynote, I actually throw up a screenshot from a still from the Bridge River River Kwai, which is a screenshot I actually use in class. I teach at Stanford on Fridays, and my students don't know what that picture is, right? So it's great. There's a lot of more. I don't have the only gray hair in this audience. Yeah, there's generational kind of commentary to be had.
Starting point is 00:17:50 So it's good. So there's people here who know what the movie is, right? People will know. Yeah, and people who listen to the podcast know about that movie. So I'd have to explain that, you know, this is a picture of the bridge. And so it's like Sir Al Guinness
Starting point is 00:18:00 and his very sweaty khakis in front of the bridge and talk about like, you know, CIOs built this beautiful bridge of architecture, of IT architecture. It's supposed to be incredibly reliable. And then security teams, our job is we rig this bridge of C4 and we blow up the bridge in case,
Starting point is 00:18:16 you know, the moment we see an enemy train coming over it, right? Like what we do as security teams is innately destructive. I mean, you just listen to the language we use, right? Like we block things, we isolate, we kill processes. We build systems that break the normal flow of IT to stop bad guys from doing things. And that's fine. I mean, that's what it's supposed to be. But I think post CrowdStrike, what's happened is CIOs have been like, wait a second,
Starting point is 00:18:43 I build this beautiful, super redundant system and all these clouds and all these availability zones. And then I give SOC analysts to this huge red button that says destroy all enterprise value. Right. Yeah. Why? Why do I do that? And so I think one of the things that's changed is that security vendors and security teams themselves now have to justify to the CIO and the CEO and boards, why do we have this power? And I think that's actually a good thing.
Starting point is 00:19:10 It's a good thing for vendors to say, okay, well, yes, we're actually much more careful than CrowdStrike in how we architect our kernel module. We're much more careful in how we test. We're much more careful in how we deploy. That was always true, but now we have to document it. So that's good. We're documenting that better. We're proving that better to folks. But it's also then we have to build our product
Starting point is 00:19:32 to help teams operationalize that better. So I think this is one of the things that you're going to start to see security products in 25 and 26 and going forward is it's going to be a lot easier to build a product so that SOC analysts too can do their job without having the destroy enterprise value button because traditionally it's been you get on board in one of these products and right next to do your job normally is the kill everything button and it's not super easy to build things in a default secure it's not super easy to
Starting point is 00:20:00 build it so that there's two keys to launch the nuclear missile, right? And those are the kinds of things that companies have built, but it had to be extra. You had to build a bunch of frameworks to do that and such, and that should become the default. I think it should become the default in IT in a lot of ways, not just on the security side. Do you think that that's something that is a lesson that also will be applied on the corporate side where they're evaluating vendors and actually having to make decisions? Yes, I hope so. And I hope like what happens is corporate teams think about,
Starting point is 00:20:29 okay, what is our workflow here? How are we going to, because like I said, EDR, security products break company. CrowdStrike's the only people to break the entire world, but security products break companies all the time. It's almost never the product's fault. It's almost always somebody inside the company uses the product to shoot the company into the time. It's almost never the product's fault. It's almost always somebody inside the company uses the product to shoot the company into the foot. And then they blame the
Starting point is 00:20:49 company. And this is not, no offense to any SentinelOne customers who are listening to this. I'm not talking about you. You're not the ones who I know blamed us because you did something. It's not you. I'm talking about somebody else, right? Clearly not in consulting where I used to come from, where it was like, no, actually, how do we tell you the problem is you? Yes, exactly. Yes, yes. But like, it's possible I have been on phone calls where I'm like, you know, okay, you want to blame us. You're clearly paying us for our job is to take the heat from you guys. But you're the guys who pushed the button that actually did this. And that happens all the time.
Starting point is 00:21:24 guys who pushed the button that actually did this. And that happens all the time. And so I think like companies need to think through, okay, what is our normal flow here of a piece of malware comes down, we, you know, it is communicating up to an IP address, we're going to decide that that IP address is malicious. How do we decide that that IP address really is the command and control server, and that is not the corporate proxy server, or the corporate DNS server, which it happens. And that once you block that corporate proxy server, you cut off all the computers in the network from the corporate proxy server and you break the entire network, right? Those are the kinds of process things that aren't appropriately thought out of. They have to be thought out of, and then products like ours and other security products need to support that and make that easy
Starting point is 00:22:02 for that kind of flow to be supported in the company so that like somebody says, I want to block this and then it goes to their manager, right? Or, you know, with AI now, it gets smart enough to be like, it looks like you want to block the corporate proxy server. Have you, you know, Clippy pops up and says,
Starting point is 00:22:17 I think Clippy itself is probably copyrighted, but we can have like our own Clippy, right? Like, you know. I guess, you're the first person in many, many years who have actually referred to Clippy in a positive way, so. Yeah, well, like our own Clippy, right? I guess. You're the first person in many, many years who have actually referred to Clippy in a positive way. Yeah, well, like positive security Clippy, like pops up and says, it looks like you're trying to destroy the entire enterprise.
Starting point is 00:22:33 You know, maybe I can help you by saying like, you shouldn't do that. And so I do think there are going to be some positive changes there. And I do think Gen AI has some real positive opportunities here to speed up defensive cycles. Right now it's being used in positive ways to make queries faster, right? And so like for us, we call it Purple, where you can, instead of, you could always ask, show me all the
Starting point is 00:22:56 laptops that downloaded a new piece of software from a Russian IP address, right? You could always ask that. But you'd have to write this huge query with a bunch of quotation marks and you'd have to know exactly what you're doing. It'll take you 20 minutes, right? Now you just write that in English and you hit enter and it does it for you. And that's great. But taking that data and doing something with it's a whole nother step. So we've gotten that first part down. And I think that that's the next phase too, is then turning of like, okay, great. Now you give me that list, isolate all those computers and being able to type in, in English, isolate all the computers you just gave me a list for, and then making that implement in three or four minutes would be incredibly powerful. And that is something I'm excited about because that turns what used to be a multi-hour project
Starting point is 00:23:39 during which during those multiple hours, bad guys were totally active going East West. They know that they're in a fight with you. They're putting more backdoors in place. They're creating more ways for them to maintain persistence. And so if you can turn that from a multi-hour process into a couple of minutes, then that gives defenders the advantage again. Well, I think it's a great ending point to make because it's a little bit more of a boost to get us from those 88 to 89 to 99% completed projects, maybe, you know, more towards 100. So we don't have those often like awful risk registers. Alex, thank you so much for taking the time.
Starting point is 00:24:16 I think it's going to be a fantastic talk and appreciate you sharing your knowledge with everyone here in the ISC2 community. Thank you so much, Alex. Thank you. That's N2K's Simone Petrella speaking with Alex Stamos from SentinelOne. We appreciate Alex taking the time to speak with us, and we appreciate you listening to our show. Thanks. Your business needs AI solutions that are not only ambitious, but also practical and adaptable.
Starting point is 00:25:09 That's where Domo's AI and data products platform comes in. With Domo, you can channel AI and data into innovative uses that deliver measurable impact. Secure AI agents connect, prepare, and automate your data workflows, helping you gain insights, receive alerts, and act with ease through guided apps tailored to

There aren't comments yet for this episode. Click on any sentence in the transcript to leave a comment.