KOPYA NG SALIN 🔗
WEBVTT
Kind: captions
Language: en
00:00:12.445 --> 00:00:24.950
[music]
00:00:24.960 --> 00:00:28.710
Hello and welcome to the premier episode
00:00:28.720 --> 00:00:30.630
of Bite.
00:00:30.640 --> 00:00:33.910
Borders and breaches
00:00:33.920 --> 00:00:36.950
the flagship podcast from the infallible
00:00:36.960 --> 00:00:39.190
security channel.
00:00:39.200 --> 00:00:42.709
I am your host Barat Mataparti.
00:00:42.719 --> 00:00:45.910
By day I serve as a senior customer
00:00:45.920 --> 00:00:48.310
success manager.
00:00:48.320 --> 00:00:52.950
My life is spent navigating the dense
00:00:52.960 --> 00:00:56.950
alphabet soup of modern data security.
00:00:56.960 --> 00:01:03.189
DRM, CASBY, SSE, and DSPM.
00:01:03.199 --> 00:01:07.750
My job is to help global organizations
00:01:07.760 --> 00:01:11.429
lock down their digital assets against a
00:01:11.439 --> 00:01:14.630
world that is constantly trying to pry
00:01:14.640 --> 00:01:18.630
them open. By night, I'm usually
00:01:18.640 --> 00:01:22.149
debating whether The Matrix is the
00:01:22.159 --> 00:01:25.749
greatest movie ever made. It is, by the
00:01:25.759 --> 00:01:26.870
way.
00:01:26.880 --> 00:01:30.390
And not just because of the kung fu or
00:01:30.400 --> 00:01:34.069
the bullet time. It's because it showed
00:01:34.079 --> 00:01:38.630
us a fundamental truth that the world we
00:01:38.640 --> 00:01:43.510
live in is built on code. And anything
00:01:43.520 --> 00:01:46.950
built on code can be hacked,
00:01:46.960 --> 00:01:50.710
manipulated, and rewritten if you know
00:01:50.720 --> 00:01:52.710
where to look.
00:01:52.720 --> 00:01:56.870
that feels a lot like the reality of
00:01:56.880 --> 00:02:01.830
cyber security in 2025.
00:02:01.840 --> 00:02:05.830
I'm from Vishaka, India and I've spent
00:02:05.840 --> 00:02:10.150
the last 13 years in the United States.
00:02:10.160 --> 00:02:13.430
I have moved from the trenches of
00:02:13.440 --> 00:02:15.910
writing code, staring at terminal
00:02:15.920 --> 00:02:19.350
screens until my eyes bled to the
00:02:19.360 --> 00:02:23.910
boardrooms of managing customer success.
00:02:23.920 --> 00:02:27.990
That journey taught me that the world is
00:02:28.000 --> 00:02:33.350
basically one giant messy code base.
00:02:33.360 --> 00:02:37.670
It's full of legacy dependencies,
00:02:37.680 --> 00:02:40.869
undocumented features and critical
00:02:40.879 --> 00:02:42.630
vulnerabilities.
00:02:42.640 --> 00:02:46.869
We like to think borders and byes are
00:02:46.879 --> 00:02:49.030
separate things.
00:02:49.040 --> 00:02:53.670
We think geography is physical and the
00:02:53.680 --> 00:02:58.070
internet is virtual. That distinction is
00:02:58.080 --> 00:03:02.070
dead. A change in a political policy in
00:03:02.080 --> 00:03:06.149
Gaza can cause a stack overflow in a
00:03:06.159 --> 00:03:09.030
bank in New York.
00:03:09.040 --> 00:03:13.589
A single line of code written in Beijing
00:03:13.599 --> 00:03:18.149
can turn off the lights in Texas.
00:03:18.159 --> 00:03:21.750
This is the show where we take the red
00:03:21.760 --> 00:03:23.270
pill.
00:03:23.280 --> 00:03:27.030
we stop looking at the headlines and
00:03:27.040 --> 00:03:30.070
start looking at the code running
00:03:30.080 --> 00:03:32.949
beneath the chaos.
00:03:32.959 --> 00:03:38.229
It is Sunday, November 23rd, 2025.
00:03:38.239 --> 00:03:41.270
And looking back at the chaos of this
00:03:41.280 --> 00:03:44.949
past week, the script I plan to write
00:03:44.959 --> 00:03:48.229
got flipped on its head because the
00:03:48.239 --> 00:03:51.910
digital world decided to have a meltdown
00:03:51.920 --> 00:03:55.030
just a few days ago.
00:03:55.040 --> 00:03:59.750
We have a massive jam-packed episode for
00:03:59.760 --> 00:04:01.830
you today.
00:04:01.840 --> 00:04:05.429
First, we will start with securing the
00:04:05.439 --> 00:04:07.270
borders.
00:04:07.280 --> 00:04:10.710
We look at the United Nations Gaza
00:04:10.720 --> 00:04:14.550
resolution from earlier this week. We're
00:04:14.560 --> 00:04:18.550
going to discuss the concept of the
00:04:18.560 --> 00:04:21.749
splinteret and what happens when
00:04:21.759 --> 00:04:25.990
international law crashes into digital
00:04:26.000 --> 00:04:27.909
sovereignity.
00:04:27.919 --> 00:04:31.030
We are pairing that with a story that
00:04:31.040 --> 00:04:35.909
feels straight out of a spy novel.
00:04:35.919 --> 00:04:37.749
Anthropics
00:04:37.759 --> 00:04:40.950
Operation Wolves Spain.
00:04:40.960 --> 00:04:45.270
Chinese state hackers are now using AI
00:04:45.280 --> 00:04:49.110
agents to write their own cyber attacks.
00:04:49.120 --> 00:04:52.710
Skynet isn't coming. It's already here
00:04:52.720 --> 00:04:57.749
and it's hacking strictly for the state.
00:04:57.759 --> 00:05:00.629
Second, we will look at decoding the
00:05:00.639 --> 00:05:03.670
bites. We were going to talk about
00:05:03.680 --> 00:05:07.590
watermarking deep fakes. We still will
00:05:07.600 --> 00:05:11.749
because the ethics of AI identity are
00:05:11.759 --> 00:05:13.430
critical.
00:05:13.440 --> 00:05:15.749
But we do have to talk about the
00:05:15.759 --> 00:05:19.909
elephant in the server room. The massive
00:05:19.919 --> 00:05:23.350
cloud flare outage that took down half
00:05:23.360 --> 00:05:26.469
the internet earlier this week.
00:05:26.479 --> 00:05:29.590
We will discuss the fragility of
00:05:29.600 --> 00:05:31.430
centralization
00:05:31.440 --> 00:05:36.790
and why zero trust shouldn't mean blind
00:05:36.800 --> 00:05:38.469
faith.
00:05:38.479 --> 00:05:41.430
And finally, we'll move on to dissecting
00:05:41.440 --> 00:05:43.270
the breach.
00:05:43.280 --> 00:05:47.430
While the AI agents and cloud giants
00:05:47.440 --> 00:05:52.070
made headlines all week, the Akira
00:05:52.080 --> 00:05:57.350
ransomware group is quietly making $250
00:05:57.360 --> 00:05:59.110
million
00:05:59.120 --> 00:06:02.550
by exploiting the
Load full transcript
oldest trick in the
00:06:02.560 --> 00:06:05.510
book. We are going to walk through the
00:06:05.520 --> 00:06:09.909
anatomy of their attack so you can see
00:06:09.919 --> 00:06:13.189
exactly how they get in.
00:06:13.199 --> 00:06:16.150
Buckle up. It's going to be a bumpy
00:06:16.160 --> 00:06:17.830
ride.
00:06:17.840 --> 00:06:21.670
First up, securing the borders.
00:06:21.680 --> 00:06:24.790
Let's start with the physical borders
00:06:24.800 --> 00:06:26.309
because
00:06:26.319 --> 00:06:29.909
the kinetic world always drives the
00:06:29.919 --> 00:06:32.790
digital world.
00:06:32.800 --> 00:06:38.150
Earlier this week on November 17th,
00:06:38.160 --> 00:06:42.790
the United Nations Security Council
00:06:42.800 --> 00:06:46.550
approved a United States drafted
00:06:46.560 --> 00:06:49.749
resolution for Gaza.
00:06:49.759 --> 00:06:53.029
It establishes an international
00:06:53.039 --> 00:06:57.430
stabilization force to fill the power
00:06:57.440 --> 00:07:01.589
vacuum left by the conflict. Now putting
00:07:01.599 --> 00:07:04.790
on my Game of Thrones hat or should I
00:07:04.800 --> 00:07:08.870
call a crown for a second. Whenever you
00:07:08.880 --> 00:07:13.029
hear the words power vacuum, you know
00:07:13.039 --> 00:07:16.790
chaos is coming. In Westeros,
00:07:16.800 --> 00:07:20.150
Littlefinger taught us that chaos is a
00:07:20.160 --> 00:07:23.189
ladder. It's an opportunity for the
00:07:23.199 --> 00:07:26.309
ruthless to climb.
00:07:26.319 --> 00:07:30.150
But in cyber security, chaos isn't a
00:07:30.160 --> 00:07:35.189
ladder. Chaos is an open port. Chaos is
00:07:35.199 --> 00:07:38.230
a misconfigured firewall. This
00:07:38.240 --> 00:07:42.390
resolution creates a massive data
00:07:42.400 --> 00:07:46.469
sovereignity headache that most people
00:07:46.479 --> 00:07:49.110
are not talking about.
00:07:49.120 --> 00:07:52.309
I work with global companies
00:07:52.319 --> 00:07:56.710
every day on this exact issue.
00:07:56.720 --> 00:07:59.430
Let's play out a scenario.
00:07:59.440 --> 00:08:02.790
Imagine you're a bank or a telecom
00:08:02.800 --> 00:08:07.189
provider or a hospital operating in that
00:08:07.199 --> 00:08:08.869
region.
00:08:08.879 --> 00:08:12.390
You have servers full of sensitive
00:08:12.400 --> 00:08:15.430
customer data, medical records,
00:08:15.440 --> 00:08:17.749
financial transactions,
00:08:17.759 --> 00:08:20.710
private communications.
00:08:20.720 --> 00:08:22.230
Suddenly,
00:08:22.240 --> 00:08:27.270
a new international stabilization force
00:08:27.280 --> 00:08:31.909
walks in. They have a mandate to secure
00:08:31.919 --> 00:08:33.909
the region.
00:08:33.919 --> 00:08:38.389
But what does that mean for your data?
00:08:38.399 --> 00:08:42.389
data doesn't have a passport, but it
00:08:42.399 --> 00:08:45.509
does have a jurisdiction. If the United
00:08:45.519 --> 00:08:47.670
Nations Force
00:08:47.680 --> 00:08:50.710
demands access to your server logs to
00:08:50.720 --> 00:08:52.790
hunt for insurgents,
00:08:52.800 --> 00:08:56.470
do you give it to them? If you do, are
00:08:56.480 --> 00:08:59.190
you violating the privacy laws of the
00:08:59.200 --> 00:09:03.030
original host nation? If you don't, are
00:09:03.040 --> 00:09:05.829
you aiding the enemy?
00:09:05.839 --> 00:09:08.070
And here is the deeper technical
00:09:08.080 --> 00:09:12.630
problem, data replication.
00:09:12.640 --> 00:09:16.630
Most modern cloud architectures
00:09:16.640 --> 00:09:19.990
replicate data across borders for
00:09:20.000 --> 00:09:22.070
redundancy.
00:09:22.080 --> 00:09:25.670
Your data might live in Gaza,
00:09:25.680 --> 00:09:29.509
but it is backed up in Tel Aviv and
00:09:29.519 --> 00:09:32.310
archived in London.
00:09:32.320 --> 00:09:35.829
If the legal status of the primary site
00:09:35.839 --> 00:09:37.590
changes,
00:09:37.600 --> 00:09:40.550
what happens to the backups?
00:09:40.560 --> 00:09:45.509
This is why we are seeing a rise in what
00:09:45.519 --> 00:09:49.670
experts call the splinter internet. The
00:09:49.680 --> 00:09:53.509
internet is fracturing into regional
00:09:53.519 --> 00:09:58.550
bordered internets where data cannot
00:09:58.560 --> 00:10:02.230
leave the country it was created in.
00:10:02.240 --> 00:10:07.350
This is where tools like DSPM, data
00:10:07.360 --> 00:10:11.350
security, posture management aren't just
00:10:11.360 --> 00:10:15.910
nice to have. They are legal survival
00:10:15.920 --> 00:10:21.430
kits. Think of DSPM like a GPS for your
00:10:21.440 --> 00:10:23.030
secrets.
00:10:23.040 --> 00:10:26.470
You need to know exactly where your
00:10:26.480 --> 00:10:29.269
sensitive data is
00:10:29.279 --> 00:10:31.829
down to the specific file on the
00:10:31.839 --> 00:10:34.310
specific server.
00:10:34.320 --> 00:10:38.550
You need to know how to access it. And
00:10:38.560 --> 00:10:43.030
crucially, you need to know which set of
00:10:43.040 --> 00:10:47.509
laws applies to it. Because when the
00:10:47.519 --> 00:10:52.389
geopolitical map changes overnight,
00:10:52.399 --> 00:10:54.870
ignorance is not a defense. It's a
00:10:54.880 --> 00:10:56.790
liability.
00:10:56.800 --> 00:10:59.829
But while the United Nations is watching
00:10:59.839 --> 00:11:04.470
the physical border, a much quieter,
00:11:04.480 --> 00:11:07.750
deadlier war is happening on the digital
00:11:07.760 --> 00:11:09.750
border.
00:11:09.760 --> 00:11:14.069
And this brings us to the major report
00:11:14.079 --> 00:11:19.030
from Anthropic that dropped recently.
00:11:19.040 --> 00:11:23.350
Anthropic, the makers of the clawed AI
00:11:23.360 --> 00:11:28.230
model, released a bombshell report on
00:11:28.240 --> 00:11:34.630
something called Operation Wolves Spain.
00:11:34.640 --> 00:11:37.590
Here's the lowdown.
00:11:37.600 --> 00:11:42.230
A Chinese state sponsored group
00:11:42.240 --> 00:11:47.990
tracked as GTG10002
00:11:48.000 --> 00:11:52.069
didn't just use
AI to write a generic
00:11:52.079 --> 00:11:54.150
fishing email.
00:11:54.160 --> 00:11:58.150
We've seen that before. That's old news.
00:11:58.160 --> 00:12:03.509
No, they effectively gave the AI keys to
00:12:03.519 --> 00:12:07.269
the car. According to the report, these
00:12:07.279 --> 00:12:11.030
hackers used Anthropics
00:12:11.040 --> 00:12:16.550
Claude code tool to create autonomous AI
00:12:16.560 --> 00:12:18.150
agents.
00:12:18.160 --> 00:12:24.150
These agents performed 80 to 90% of the
00:12:24.160 --> 00:12:27.269
attack life cycle without human
00:12:27.279 --> 00:12:29.030
intervention.
00:12:29.040 --> 00:12:33.829
Let's pause and really let that sink in.
00:12:33.839 --> 00:12:36.389
80 to 90%.
00:12:36.399 --> 00:12:39.110
In a traditional cyber attack, there is
00:12:39.120 --> 00:12:44.550
a concept called the UDA loop. Observe,
00:12:44.560 --> 00:12:49.829
orient, decide, act. The hacker has to
00:12:49.839 --> 00:12:52.790
look at the screen, figure out what
00:12:52.800 --> 00:12:56.870
they're seeing, decide what command to
00:12:56.880 --> 00:13:03.269
type, and then type it. That takes time.
00:13:03.279 --> 00:13:07.430
It takes cognitive load.
00:13:07.440 --> 00:13:11.509
With Wol's Bane, the human hackers hit
00:13:11.519 --> 00:13:16.230
start. They grabbed a coffee and the AI
00:13:16.240 --> 00:13:19.509
closed that loop instantly.
00:13:19.519 --> 00:13:21.829
It did the reconnaissance.
00:13:21.839 --> 00:13:25.110
It scanned the ports. It found the
00:13:25.120 --> 00:13:27.910
vulnerabilities. It wrote the exploit
00:13:27.920 --> 00:13:31.110
code to break him.
00:13:31.120 --> 00:13:34.230
For my Harry Potter fans out there, this
00:13:34.240 --> 00:13:40.150
name Wols Bane is tragically perfect. In
00:13:40.160 --> 00:13:42.790
JK Rowling's world, the Wools Bane
00:13:42.800 --> 00:13:46.710
portion is what Remis Lupin takes. It
00:13:46.720 --> 00:13:50.870
keeps the werewolf sane. It allows the
00:13:50.880 --> 00:13:55.110
monster to hide in plain sight, to walk
00:13:55.120 --> 00:13:57.990
within the castle walls without
00:13:58.000 --> 00:14:01.350
attacking the students. It masks the
00:14:01.360 --> 00:14:04.629
nature of the beast. Anthropic is
00:14:04.639 --> 00:14:09.350
calling this wolf's bane because they
00:14:09.360 --> 00:14:13.509
claim they caught it and stopped it.
00:14:13.519 --> 00:14:16.550
They contained the monster.
00:14:16.560 --> 00:14:21.189
But let's be real, the monster is out of
00:14:21.199 --> 00:14:24.629
the cage. This represents a private
00:14:24.639 --> 00:14:28.550
point in history. For 20 years, we have
00:14:28.560 --> 00:14:32.790
worried about script kitties, teenagers
00:14:32.800 --> 00:14:37.189
in hoodies copying code they didn't
00:14:37.199 --> 00:14:38.790
understand.
00:14:38.800 --> 00:14:42.870
Now we have entered the era of agentic
00:14:42.880 --> 00:14:44.389
threats.
00:14:44.399 --> 00:14:48.550
From a technical perspective, this is
00:14:48.560 --> 00:14:50.150
terrifying
00:14:50.160 --> 00:14:54.470
because of the speed and the scale.
00:14:54.480 --> 00:14:59.269
A human hacker might take days to scan a
00:14:59.279 --> 00:15:02.870
network. They get tired. They make
00:15:02.880 --> 00:15:07.750
typos. They overlook a small detail
00:15:07.760 --> 00:15:12.389
because they are bored. An AI agent does
00:15:12.399 --> 00:15:16.629
not get tired. It does not get bored. It
00:15:16.639 --> 00:15:21.269
scans every single IP address, every
00:15:21.279 --> 00:15:25.990
single port, every single line of code
00:15:26.000 --> 00:15:30.069
in seconds. It creates
00:15:30.079 --> 00:15:33.590
an asymmetric warfare scenario.
00:15:33.600 --> 00:15:36.710
The attacker is moving at machine
00:15:36.720 --> 00:15:39.990
speeds, calculating vectors, writing
00:15:40.000 --> 00:15:44.230
codes in milliseconds. the defender.
00:15:44.240 --> 00:15:49.110
We are still moving at human speed. We
00:15:49.120 --> 00:15:52.069
are still waiting for a pager alert to
00:15:52.079 --> 00:15:57.189
wake us up at 2:00 a.m. If you are a
00:15:57.199 --> 00:16:01.509
CISO listening to this, this changes
00:16:01.519 --> 00:16:04.790
your entire threat model.
00:16:04.800 --> 00:16:09.189
You cannot rely on signatures anymore.
00:16:09.199 --> 00:16:13.829
You can't just look for a known bad file
00:16:13.839 --> 00:16:15.350
hash.
00:16:15.360 --> 00:16:18.550
You are looking for an intelligence that
00:16:18.560 --> 00:16:22.150
can adapt on the fly.
00:16:22.160 --> 00:16:25.910
It's the difference between fighting a
00:16:25.920 --> 00:16:29.910
stormtrooper who misses every shot and
00:16:29.920 --> 00:16:32.629
fighting a terminator.
00:16:32.639 --> 00:16:36.790
One follows orders, the other has
00:16:36.800 --> 00:16:40.470
mission objective and will calculate the
00:16:40.480 --> 00:16:44.550
most efficient path to execute it
00:16:44.560 --> 00:16:47.110
regardless of the obstacles you put in
00:16:47.120 --> 00:16:52.150
its way. The takeaway here is clear.
00:16:52.160 --> 00:16:57.030
The wolf is at the door and it knows how
00:16:57.040 --> 00:17:02.150
to pick the lock better than any human
00:17:02.160 --> 00:17:05.270
ever could.
00:17:05.280 --> 00:17:09.750
Next up, decoding the bites. We need to
00:17:09.760 --> 00:17:12.789
talk about the infrastructure that holds
00:17:12.799 --> 00:17:15.189
our reality together.
00:17:15.199 --> 00:17:19.990
If you try to log into chat GPT or check
00:17:20.000 --> 00:17:24.710
on X or maybe catch a train on NJ
00:17:24.720 --> 00:17:28.710
Transit on Tuesday morning, you probably
00:17:28.720 --> 00:17:33.990
saw a 404 error or maybe just a spinning
00:17:34.000 --> 00:17:36.230
wheel of death.
00:17:36.240 --> 00:17:41.350
That's because Cloudflare had a massive
00:17:41.360 --> 00:17:44.070
global outage.
00:17:44.080 --> 00:17:48.710
Now if you aren't in in the industry
00:17:48.720 --> 00:17:52.710
you might ask what is Cloudflare?
00:17:52.720 --> 00:17:56.549
Cloudflare is the duct tape of the
00:17:56.559 --> 00:18:02.070
internet. It sits in front of millions
00:18:02.080 --> 00:18:04.230
of websites
00:18:04.240 --> 00:18:10.230
about 20% of the entire web and it acts
00:18:10.240 --> 00:18:15.830
as a shield and a distinct accelerator.
00:18:15.840 --> 00:18:19.430
It stops distributed denial of service
00:18:19.440 --> 00:18:23.669
attacks and it caches content so it
00:18:23.679 --> 00:18:25.830
loads faster.
00:18:25.840 --> 00:18:28.390
But here is the problem with the duct
00:18:28.400 --> 00:18:31.990
tape. When it rips,
00:18:32.000 --> 00:18:36.470
everything falls apart. Reports confirm
00:18:36.480 --> 00:18:40.630
this outage affected their access zero
00:18:40.640 --> 00:18:42.789
trust platform.
00:18:42.799 --> 00:18:48.070
And this is deeply ironic and honestly a
00:18:48.080 --> 00:18:50.870
little painful for me as a security
00:18:50.880 --> 00:18:52.870
professional.
00:18:52.880 --> 00:18:56.070
We spend all day preaching a concept
00:18:56.080 --> 00:18:59.430
called zero trust.
00:18:59.440 --> 00:19:03.029
The old way of security was casle and
00:19:03.039 --> 00:19:04.789
moat.
00:19:04.799 --> 00:19:09.029
You had a firewall, the moat. Inside the
00:19:09.039 --> 00:19:13.909
firewall, everyone was trusted. Outside,
00:19:13.919 --> 00:19:16.789
everyone was untrusted.
00:19:16.799 --> 00:19:21.830
But that failed because once a hacker
00:19:21.840 --> 00:19:25.350
got across the moat, they could roam the
00:19:25.360 --> 00:19:27.590
castle freely.
00:19:27.600 --> 00:19:31.750
So we move to zero trust.
00:19:31.760 --> 00:19:35.510
Never trust, always verify.
00:19:35.520 --> 00:19:40.630
The idea is that you don't use a VPN.
00:19:40.640 --> 00:19:43.669
You use a service like Cloudflare
00:19:43.679 --> 00:19:45.430
Access.
00:19:45.440 --> 00:19:48.549
Every time you try to open a file or
00:19:48.559 --> 00:19:52.150
load a web page, the system checks your
00:19:52.160 --> 00:19:54.950
ID. It verifies
00:19:54.960 --> 00:19:58.390
you are who you say you are.
00:19:58.400 --> 00:20:02.310
It is a great system in theory.
00:20:02.320 --> 00:20:06.470
But here is the trust paradox.
00:20:06.480 --> 00:20:10.789
To implement zero trust, you have to
00:20:10.799 --> 00:20:13.029
place absolute
00:20:13.039 --> 00:20:17.750
blind trust in the vendor providing it.
00:20:17.760 --> 00:20:21.510
When Cloudflare goes down, you don't
00:20:21.520 --> 00:20:24.789
just lose your public website,
00:20:24.799 --> 00:20:28.789
you lose your internal tools.
00:20:28.799 --> 00:20:32.549
Imagine this. You are a developer.
00:20:32.559 --> 00:20:37.190
You need to push code to fix a bug.
00:20:37.200 --> 00:20:39.909
You can't because the authentication
00:20:39.919 --> 00:20:42.710
server is down.
00:20:42.720 --> 00:20:46.310
You are an HR manager. You need to
00:20:46.320 --> 00:20:49.830
access payroll. You can't. The digital
00:20:49.840 --> 00:20:54.070
doors to your own office are locked. And
00:20:54.080 --> 00:20:58.870
Cloudflare has the only key.
00:20:58.880 --> 00:21:03.029
It reminds me of the Death Star in Star
00:21:03.039 --> 00:21:07.909
Wars. An incredible technological terror
00:21:07.919 --> 00:21:12.230
capable of ruling the entire galaxy.
00:21:12.240 --> 00:21:16.310
The ultimate power in the universe, but
00:21:16.320 --> 00:21:21.590
it had one thermal exhaust port, one
00:21:21.600 --> 00:21:24.470
central point of failure.
00:21:24.480 --> 00:21:27.830
And if you hit that, the whole thing
00:21:27.840 --> 00:21:30.149
blows up.
00:21:30.159 --> 00:21:33.190
We have centralized so much of the
00:21:33.200 --> 00:21:37.029
internet's infrastructure into three or
00:21:37.039 --> 00:21:41.909
four companies, Cloudflare, AWS,
00:21:41.919 --> 00:21:45.750
Microsoft, Google. that a single
00:21:45.760 --> 00:21:49.750
configuration error, a single bad line
00:21:49.760 --> 00:21:53.350
of code pushed by an engineer on Tuesday
00:21:53.360 --> 00:21:57.909
morning acts like a Luke Skywalker
00:21:57.919 --> 00:22:00.070
proton torpedo.
00:22:00.080 --> 00:22:04.310
This outage forces a hard conversation
00:22:04.320 --> 00:22:07.750
for my customers this week.
00:22:07.760 --> 00:22:11.750
It forces us to ask, "What is your break
00:22:11.760 --> 00:22:13.830
glass plan?
00:22:13.840 --> 00:22:18.470
We are so obsessed with efficiency that
00:22:18.480 --> 00:22:22.549
we have sacrificed resilience.
00:22:22.559 --> 00:22:25.909
If the cloud evaporates, do you have a
00:22:25.919 --> 00:22:29.669
physical backup key? Can you route
00:22:29.679 --> 00:22:33.909
traffic around the failure or are you
00:22:33.919 --> 00:22:37.750
just stuck outside in the rain waiting
00:22:37.760 --> 00:22:41.590
for the servers to reboot?
00:22:41.600 --> 00:22:45.909
Now shifting gear slightly,
00:22:45.919 --> 00:22:48.710
let's look at why we rely on these
00:22:48.720 --> 00:22:50.230
platforms.
00:22:50.240 --> 00:22:54.070
It is largely to filter out bad traffic
00:22:54.080 --> 00:22:57.270
and fake content.
00:22:57.280 --> 00:23:00.230
Which brings us to our second bite
00:23:00.240 --> 00:23:04.470
topic, generative watermarking.
00:23:04.480 --> 00:23:06.950
While the internet was struggling to
00:23:06.960 --> 00:23:10.470
stay online this week, the World
00:23:10.480 --> 00:23:15.430
Economic Forum was praising this tech as
00:23:15.440 --> 00:23:18.070
a top 10 breakthrough.
00:23:18.080 --> 00:23:20.470
The idea is simple.
00:23:20.480 --> 00:23:24.549
Embed an invisible signal, a watermark,
00:23:24.559 --> 00:23:28.549
into AI generated content so we can
00:23:28.559 --> 00:23:32.390
identify it. When an AI generates an
00:23:32.400 --> 00:23:35.430
image or a voice clip, it weaves a
00:23:35.440 --> 00:23:38.230
secret pattern into the pixels or the
00:23:38.240 --> 00:23:40.070
sound waves.
00:23:40.080 --> 00:23:44.390
Humans can't see it, but a computer can
00:23:44.400 --> 00:23:48.789
detect it and say this was made by a
00:23:48.799 --> 00:23:50.630
machine.
00:23:50.640 --> 00:23:55.669
Ideally, this stops the deep fakes.
00:23:55.679 --> 00:23:59.909
It stops the disinformation.
00:23:59.919 --> 00:24:05.110
But let's be real. I look at this like
00:24:05.120 --> 00:24:11.029
the void camp test from Bladeunner.
00:24:11.039 --> 00:24:14.149
For those who haven't seen the movie,
00:24:14.159 --> 00:24:18.470
the void camp test is a machine designed
00:24:18.480 --> 00:24:22.789
to look into the eye of a subject and
00:24:22.799 --> 00:24:26.070
measure their emotional response
00:24:26.080 --> 00:24:30.549
and tell the difference between a human
00:24:30.559 --> 00:24:33.110
and a replicant,
00:24:33.120 --> 00:24:35.190
a bioengineered
00:24:35.200 --> 00:24:37.269
android.
00:24:37.279 --> 00:24:41.190
In the movie, the test is the only thing
00:24:41.200 --> 00:24:44.710
keeping society from collapsing into
00:24:44.720 --> 00:24:46.630
paranoia.
00:24:46.640 --> 00:24:50.310
In a corporate setting, this is becoming
00:24:50.320 --> 00:24:52.470
vital.
00:24:52.480 --> 00:24:55.590
Imagine a world where operation wolves
00:24:55.600 --> 00:24:59.190
bane, remember our AI hackers from
00:24:59.200 --> 00:25:02.710
earlier, isn't just sending code.
00:25:02.720 --> 00:25:04.310
Imagine
00:25:04.320 --> 00:25:09.750
they send a deep fake video of your CEO
00:25:09.760 --> 00:25:14.630
on a Zoom call. The CEO looks real. He
00:25:14.640 --> 00:25:18.870
sounds real. He tells the CFO,
00:25:18.880 --> 00:25:21.830
"We need to authorize this urgent wire
00:25:21.840 --> 00:25:25.590
transfer for the acquisition."
00:25:25.600 --> 00:25:31.990
The CFO does it and the money is gone.
00:25:32.000 --> 00:25:37.590
We need a white camp machine to validate
00:25:37.600 --> 00:25:39.830
reality.
00:25:39.840 --> 00:25:44.070
We need that watermark to light up and
00:25:44.080 --> 00:25:47.269
say, "Warning, synthetic media
00:25:47.279 --> 00:25:48.950
detected."
00:25:48.960 --> 00:25:50.630
But
00:25:50.640 --> 00:25:52.549
I'm skeptical.
00:25:52.559 --> 00:25:55.350
And here is why.
00:25:55.360 --> 00:26:00.710
Watermarking is a good guy tool.
00:26:00.720 --> 00:26:04.470
It relies on the model creators,
00:26:04.480 --> 00:26:08.710
OpenAI, Google, Adobe
00:26:08.720 --> 00:26:10.950
playing by the rules.
00:26:10.960 --> 00:26:14.710
It relies on them inserting the
00:26:14.720 --> 00:26:17.909
watermark voluntarily.
00:26:17.919 --> 00:26:22.630
Do we think the state sponsored hackers
00:26:22.640 --> 00:26:27.750
in China, the ones running Wolves Bane,
00:26:27.760 --> 00:26:31.909
are going to politely watermark their
00:26:31.919 --> 00:26:33.990
deep fakes?
00:26:34.000 --> 00:26:37.830
Oh, sorry. Let me add this is fake
00:26:37.840 --> 00:26:42.710
sticker to my espionage campaign so you
00:26:42.720 --> 00:26:45.350
can catch me.
00:26:45.360 --> 00:26:51.110
No, of course not. It's an arms race.
00:26:51.120 --> 00:26:55.669
It's exactly like counterfeit currency.
00:26:55.679 --> 00:26:59.669
The government adds watermarks,
00:26:59.679 --> 00:27:03.269
strips, and holograms to the dollar
00:27:03.279 --> 00:27:05.029
bill.
00:27:05.039 --> 00:27:08.630
The counterfeiters figure out how to
00:27:08.640 --> 00:27:10.789
fake the holograms.
00:27:10.799 --> 00:27:14.789
You can watermark the gun,
00:27:14.799 --> 00:27:18.390
but you can't stop the bullet.
00:27:18.400 --> 00:27:22.630
Finally, dissecting the breach.
00:27:22.640 --> 00:27:26.549
We have talked about cutting edge AI
00:27:26.559 --> 00:27:28.230
spice.
00:27:28.240 --> 00:27:31.830
We have talked about the global
00:27:31.840 --> 00:27:34.870
infrastructure collapses.
00:27:34.880 --> 00:27:39.510
But the biggest payday in cyber crime
00:27:39.520 --> 00:27:44.870
right now is not coming from Skynet.
00:27:44.880 --> 00:27:47.990
It is not coming from complex
00:27:48.000 --> 00:27:51.190
agentic AI threats.
00:27:51.200 --> 00:27:56.149
It is coming from a group called Akira
00:27:56.159 --> 00:28:01.269
and they are robbing companies blind
00:28:01.279 --> 00:28:05.430
using the digital equivalent of a rusty
00:28:05.440 --> 00:28:07.510
crowbar.
00:28:07.520 --> 00:28:12.950
CISA, the US cyber defense agency
00:28:12.960 --> 00:28:17.430
updated their advisory on Akira mid
00:28:17.440 --> 00:28:19.190
November
00:28:19.200 --> 00:28:23.190
and the numbers are staggering.
00:28:23.200 --> 00:28:28.230
This group has ragged in $250
00:28:28.240 --> 00:28:30.710
million.
00:28:30.720 --> 00:28:32.230
How
00:28:32.240 --> 00:28:36.070
are they using quantum computing to
00:28:36.080 --> 00:28:38.310
crack encryption?
00:28:38.320 --> 00:28:43.590
No. Are they using zeroday exploits that
00:28:43.600 --> 00:28:46.710
no one has ever seen before?
00:28:46.720 --> 00:28:48.549
No.
00:28:48.559 --> 00:28:51.990
They are targeting VPNs
00:28:52.000 --> 00:28:55.029
without multi-factor
00:28:55.039 --> 00:28:58.630
authentication.
00:28:58.640 --> 00:29:03.029
I feel like I'm taking crazy pills.
00:29:03.039 --> 00:29:07.350
In every Mission Impossible movie, Tom
00:29:07.360 --> 00:29:11.830
Cruz has to hang from the ceiling by
00:29:11.840 --> 00:29:13.350
wire.
00:29:13.360 --> 00:29:17.269
He has to dodge lasers.
00:29:17.279 --> 00:29:21.269
He has to wear a prosthetic mask.
00:29:21.279 --> 00:29:25.430
He has to hack a retinal scanner just to
00:29:25.440 --> 00:29:27.909
get into the server room. It is
00:29:27.919 --> 00:29:29.430
complicated.
00:29:29.440 --> 00:29:33.269
It's sexy. It's hard.
00:29:33.279 --> 00:29:37.669
In the real world, Akira is just walking
00:29:37.679 --> 00:29:40.149
up to the front door,
00:29:40.159 --> 00:29:44.549
trying the handle, and realizing, "Wow,
00:29:44.559 --> 00:29:47.029
it's unlocked."
00:29:47.039 --> 00:29:48.630
Specifically,
00:29:48.640 --> 00:29:52.710
they are targeting Sonic Wall and Cisco
00:29:52.720 -->
00:29:56.789
VPNs where the admins haven't enabled
00:29:56.799 --> 00:30:00.149
MFA of an Akira attack. So, you
00:30:00.159 --> 00:30:03.110
understand what happens.
00:30:03.120 --> 00:30:06.630
Step one, access.
00:30:06.640 --> 00:30:09.750
They buy stolen credentials on the dark
00:30:09.760 --> 00:30:13.430
web. Someone in your company reused
00:30:13.440 --> 00:30:15.430
their password.
00:30:15.440 --> 00:30:20.310
Akira buys that password for $5. They
00:30:20.320 --> 00:30:23.590
try it on your VPN.
00:30:23.600 --> 00:30:27.190
There is no MFA code sent to your phone.
00:30:27.200 --> 00:30:32.630
They are in. Step two, exfiltration.
00:30:32.640 --> 00:30:36.070
They don't encrypt yet. They are
00:30:36.080 --> 00:30:39.590
patient. They look around.
00:30:39.600 --> 00:30:43.830
They find your most sensitive data,
00:30:43.840 --> 00:30:47.430
your customer lists, your financial
00:30:47.440 --> 00:30:49.110
records,
00:30:49.120 --> 00:30:51.669
your emails.
00:30:51.679 --> 00:30:55.510
They copy it all and upload it to their
00:30:55.520 --> 00:30:58.149
own servers.
00:30:58.159 --> 00:31:01.269
Step three, encryption.
00:31:01.279 --> 00:31:04.549
Now they drop the hammer.
00:31:04.559 --> 00:31:07.750
They deploy the ransomware.
00:31:07.760 --> 00:31:09.669
Every server,
00:31:09.679 --> 00:31:11.669
every laptop,
00:31:11.679 --> 00:31:14.470
every backup that is connected to the
00:31:14.480 --> 00:31:17.510
network gets locked.
00:31:17.520 --> 00:31:21.990
This is called double extortion.
00:31:22.000 --> 00:31:25.269
Even if you have backups,
00:31:25.279 --> 00:31:27.510
they have you.
00:31:27.520 --> 00:31:31.110
You might say, "I won't pay the ransom.
00:31:31.120 --> 00:31:34.870
I'll just restore from the backup."
00:31:34.880 --> 00:31:38.950
Akira says, "Go ahead, restore your
00:31:38.960 --> 00:31:43.669
backup, but if you don't pay us, we will
00:31:43.679 --> 00:31:48.149
post all five terabytes of your customer
00:31:48.159 --> 00:31:52.710
data on the public internet.
00:31:52.720 --> 00:31:55.669
It is checkmate
00:31:55.679 --> 00:31:57.909
for my customers.
00:31:57.919 --> 00:32:00.070
This is the
00:32:00.080 --> 00:32:03.509
come to Jesus moment.
00:32:03.519 --> 00:32:07.029
I don't care if you have the fanciest AI
00:32:07.039 --> 00:32:09.350
defense systems.
00:32:09.360 --> 00:32:12.630
I don't care if you have an army of
00:32:12.640 --> 00:32:14.470
analysts.
00:32:14.480 --> 00:32:20.070
If you have a legacy VPN running in a
00:32:20.080 --> 00:32:23.830
closet somewhere without multiffactor
00:32:23.840 --> 00:32:26.470
authentication,
00:32:26.480 --> 00:32:30.310
you are the lowhanging fruit.
00:32:30.320 --> 00:32:34.710
You are a gazelle limping at the back of
00:32:34.720 --> 00:32:36.630
the herd.
00:32:36.640 --> 00:32:40.310
It's like [clears throat] Jurassic Park.
00:32:40.320 --> 00:32:44.630
You can have all the motion sensors.
00:32:44.640 --> 00:32:48.389
You can have the electric fences.
00:32:48.399 --> 00:32:52.310
You can have the best geneticists in the
00:32:52.320 --> 00:32:54.389
world.
00:32:54.399 --> 00:32:58.630
But if Dennis Nerdy
00:32:58.640 --> 00:33:02.950
shuts off the power system or if you
00:33:02.960 --> 00:33:05.590
leave the VPN open,
00:33:05.600 --> 00:33:09.669
the Raptors will get out.
00:33:09.679 --> 00:33:14.870
And in this case, the Raptors are taking
00:33:14.880 --> 00:33:16.950
$250
00:33:16.960 --> 00:33:18.549
million
00:33:18.559 --> 00:33:20.389
with them.
00:33:20.399 --> 00:33:23.669
So, let's wrap this up.
00:33:23.679 --> 00:33:26.870
What is the thread this week?
00:33:26.880 --> 00:33:30.070
We have United Nations resolutions
00:33:30.080 --> 00:33:33.269
changing data laws.
00:33:33.279 --> 00:33:37.830
We have Chinese AI agents writing their
00:33:37.840 --> 00:33:40.070
own code.
00:33:40.080 --> 00:33:43.750
We have Cloudflare outages
00:33:43.760 --> 00:33:46.789
breaking the trust model.
00:33:46.799 --> 00:33:50.389
And we have ransomware gangs making a
00:33:50.399 --> 00:33:51.990
fortune
00:33:52.000 --> 00:33:54.789
on basic mistakes.
00:33:54.799 --> 00:33:58.310
The thread is fragility.
00:33:58.320 --> 00:34:01.190
We are building systems of immense
00:34:01.200 --> 00:34:02.950
power.
00:34:02.960 --> 00:34:06.789
AI agents that can code.
00:34:06.799 --> 00:34:10.869
Global networks that connect billions.
00:34:10.879 --> 00:34:15.270
But these systems are fragile.
00:34:15.280 --> 00:34:19.190
A single configuration error takes down
00:34:19.200 --> 00:34:21.190
the web.
00:34:21.200 --> 00:34:27.030
A single MFA token costs you millions.
00:34:27.040 --> 00:34:30.149
A single political decision
00:34:30.159 --> 00:34:33.510
changes where your data is allowed to
00:34:33.520 --> 00:34:38.710
live. Our job as security professionals
00:34:38.720 --> 00:34:43.349
and just as people living in this matrix
00:34:43.359 --> 00:34:46.230
is to build resilience,
00:34:46.240 --> 00:34:49.750
to verify the watermark but not trust it
00:34:49.760 --> 00:34:51.270
blindly,
00:34:51.280 --> 00:34:55.669
to lock the VPN and check it twice.
00:34:55.679 --> 00:34:58.950
To have a backup plan when the cloud
00:34:58.960 --> 00:35:01.510
goes dark.
00:35:01.520 --> 00:35:04.630
Thank you for joining me on this
00:35:04.640 --> 00:35:08.310
premiier episode of Bites [snorts]
00:35:08.320 --> 00:35:11.670
Borders and Breaches.
00:35:11.680 --> 00:35:15.670
I'm your host Barat Mataparti.
00:35:15.680 --> 00:35:18.310
Keep your shields up.
00:35:18.320 --> 00:35:20.550
Check your backups
00:35:20.560 --> 00:35:22.390
and remember
00:35:22.400 --> 00:35:25.670
there is no spoon.
00:35:25.680 --> 00:35:34.659
May the force be with you. [music]
00:35:34.669 --> 00:35:36.689
>> [music]