• 39 minutes ago

Category

🗞
News
Transcript
00:00In this moment, as you are dealing with an AI incident that I referenced, and I know that you're not
00:06able to reveal the company yet, but can you tell us what you can about the attack?
00:11Yeah, Aaron. So I started working on an incident this morning with one of our customers that called in.
00:16Not one of the customers that we monitor 24-7, but they also approved me to talk about the basics
00:22of what had occurred during this period of time because they thought it was important because they've never seen anything
00:26kind of ripped through their systems this fast.
00:28And I think that's the overall message here is that, hey, this stuff is happening. It's happening quicker than we
00:33can typically respond to it.
00:34And so there's different ransomware groups that operate in different types of, I would say, knowledge.
00:40You have certain ransomware groups that try to phish and harvest credentials, usernames and passwords from companies, and then they
00:47will sell that to more sophisticated groups that can actually launch attacks against the system.
00:52What I started working on this morning, I actually was going to cancel the show today because I figured I'd
00:56be working all day on this, and I was able to step out to at least present some of this.
01:01But they were able to launch what we call an agent swarm.
01:05So we saw over 30 different types of agents probing their infrastructure at the exact same time, logged in with
01:11their usernames and passwords,
01:12and were able to find a flaw in their application on how they use what's called two-factor authentication, which
01:18is that second form of getting in to the system.
01:20It bypassed that.
01:22They got access to the system.
01:23They exfiltrated a substantial amount of data, and then they had a ransomware event, which encrypted in their entire file
01:30system.
01:30And this all took 14 minutes.
01:3214 minutes.
01:34Never seen anything that fast before.
01:35I mean, they didn't even detect it for about four and a half hours until the system, you know, was
01:40then knocked offline.
01:42So they encrypted everything.
01:43The system was still running.
01:44And eventually it errored out.
01:46The system restarted.
01:47And then they noticed they had an outage.
01:48It took about four and a half hours for them to actually identify that occurred.
01:51And they were already gone for, you know, over four hours.

Recommended