Ransomware attacks typically don't care about memory safety and dependency scanning, they often target old, unpatched vulns and too often they succeed. Rob Allen shares some of the biggest cases he's seen, what they have in common, and what appsec teams could do better to help them. Too much software still requires custom configuration to make it more secure. And too few software makers are embracing secure by default, let alone secure by design. In the news, passively monitoring geosynchronous satellite communications on the cheap, successful LLM poisoning of any size model with a single size dose, security engineering lessons from Signal's post-quantum crypto work, improving security for JavaScript in the browser, and more! This segment is sponsored by ThreatLocker. Visit <a rel= "noopener" target="_blank" href= "https://securityweekly.com/threatlocker">https://securityweekly.com/threatlocker</a> to learn more! Visit <a rel="noopener" target="_blank" href= "https://www.securityweekly.com/asw">https://www.securityweekly.com/asw</a> for all the latest episodes! Show Notes: <a rel="noopener" target="_blank" href= "https://securityweekly.com/asw-353">https://securityweekly.com/asw-353</a>

Podurama

Home

Trending

Personal

Your Podcasts

New Episodes

My Files

Favourite Episodes

Tags (Folders)

Recently Played

Bookmarks

Followed Playlists

Reacting to Ransomware and Setting Secure Defaults - Rob Allen - ASW #353

Application Security Weekly (Audio)

AI Chapters

AI Insights

Reviews