Jul 16, 2026 · 18 min · 9 segments
Hybrid threats are changing what it means to “handle an incident,” and this narrated episode walks through how that plays out when protests, outages, and digital campaigns collide. You’ll hear how…
Jason EdwardsHost
A march outside an office or data center is quickly paired with calls to expose executives, to publish internal documents, and to overwhelm customer-facing channels.
Videos and photos that appear on news feeds become raw material for narratives that travel globally within minutes.
Those narratives are often attached to specific targets, such as login pages, feedback forms, or employee profiles, and call on people to hit those points in whatever way they can.
Some participants are activists, some are opportunists, and some are outright criminals.
But from your side of the dashboard, the result is a surge of stress on people and systems at the same time.
Legal and communications teams start asking about defamation, privacy, and the boundaries of acceptable speech.
In parallel, you see odd spikes in traffic from new geographies or login attempts that do not match your usual user behavior.
Your marketing site, blog, and support channels become targets for defacement and abuse.
The majority of that traffic may still be legitimate users expressing anger, demanding answers, or organizing campaigns.
Mixed into that noise are people attempting real harm, from credential stuffing to data leaks.
This is where leadership judgment becomes more important than any specific tool.
If security treats every expression of anger as hostile, the organization may overreact, locking down channels, cutting off access, and confirming the narrative that it is hiding something.
If security underreacts, determined attackers can hide serious operations within the chaos.
A better framing is to treat protests and online pressure as amplifiers of stress, not as cyber incidents in themselves.
They are predictable sources of additional load on services, people, and decision processes.
When you adopt that framing, you can start deciding in advance what you will protect, what you will tolerate, and how you will distinguish harm to systems from harm to people when you cannot eliminate both.
A march outside an office or data center is quickly paired with calls to expose executives, to publish internal documents, and to overwhelm customer-facing channels.
Videos and photos that appear on news feeds become raw material for narratives that travel globally within minutes.
Those narratives are often attached to specific targets, such as login pages, feedback forms, or employee profiles, and call on people to hit those points in whatever way they can.
Some participants are activists, some are opportunists, and some are outright criminals.
But from your side of the dashboard, the result is a surge of stress on people and systems at the same time.
Legal and communications teams start asking about defamation, privacy, and the boundaries of acceptable speech.
In parallel, you see odd spikes in traffic from new geographies or login attempts that do not match your usual user behavior.
Your marketing site, blog, and support channels become targets for defacement and abuse.
The majority of that traffic may still be legitimate users expressing anger, demanding answers, or organizing campaigns.
Mixed into that noise are people attempting real harm, from credential stuffing to data leaks.
This is where leadership judgment becomes more important than any specific tool.
If security treats every expression of anger as hostile, the organization may overreact, locking down channels, cutting off access, and confirming the narrative that it is hiding something.
If security underreacts, determined attackers can hide serious operations within the chaos.
A better framing is to treat protests and online pressure as amplifiers of stress, not as cyber incidents in themselves.
They are predictable sources of additional load on services, people, and decision processes.
When you adopt that framing, you can start deciding in advance what you will protect, what you will tolerate, and how you will distinguish harm to systems from harm to people when you cannot eliminate both.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.