https://www.spreaker.com/podcast/effective-secure-coding--7459967Secure coding isn’t about memorizing vulnerabilities. It’s about building habits that make insecure code harder to write.

Based on Effective Secure Coding, this podcast explores 13 practical habits for designing and building safer software - from trust boundaries and validation to safer APIs, defensive design, and deterministic guardrails.

It’s made for software developers, tech leads, architects, AppSec engineers, and anyone building software with AI coding tools who wants security to become part of everyday engineering rather than a last-minute review.

Each episode turns one habit into practical engineering advice for modern development.

Because when AI can write the code, the real question is who designs the rules it has to follow.


NOTE: Podcasts are narrated by Gemini Notebook-LM]]>enTechnology(2026) Yariv Tal, Secure From Scratchhttps://d3wo5wojvuv7l.cloudfront.net/t_rss_itunes_square_1400/images.spreaker.com/original/1e6d19d1b31d497fec14e0434df9a73d.jpghttps://www.spreaker.com/podcast/effective-secure-coding--7459967Mon, 19 Oct 2026 15:35:04 +0000Yariv TalYariv Talyarivt@securefromscratch.comSecure coding isn’t about memorizing vulnerabilities. It’s about building habits that make insecure code harder to write. Based on Effective Secure Coding, this podcast explores 13 practical habits for designing and building safer software - from...Secure coding isn’t about memorizing vulnerabilities. It’s about building habits that make insecure code harder to write.

Based on Effective Secure Coding, this podcast explores 13 practical habits for designing and building safer software - from trust boundaries and validation to safer APIs, defensive design, and deterministic guardrails.

It’s made for software developers, tech leads, architects, AppSec engineers, and anyone building software with AI coding tools who wants security to become part of everyday engineering rather than a last-minute review.

Each episode turns one habit into practical engineering advice for modern development.

Because when AI can write the code, the real question is who designs the rules it has to follow.


NOTE: Podcasts are narrated by Gemini Notebook-LM]]>falsedb1ca11d-8ff2-5cba-9101-4a7c32f7cd03serialhttps://www.spreaker.com/episode/why-software-fails-at-trust-boundaries--75760204
This episode explores Habit 1 of the 13 habits from Effective Secure Coding: Think in Trust Boundaries.

Why do secure values become dangerous when they move between users, services, files, APIs, databases, or privilege levels? And what changes when AI is writing the code for you?

We look at how to spot trust boundaries, make them explicit in your design, and give AI coding tools concrete security constraints instead of vague instructions like “make it secure.”

Secure coding starts with one question: where does trust change?
]]>https://api.spreaker.com/episode/75760204Tue, 13 Oct 2026 16:23:03 +0000Yariv TalWhat happens when perfectly valid data crosses into the wrong place? This episode explores Habit 1 of the 13 habits from Effective Secure Coding: Think in Trust Boundaries. Why do secure values become dangerous when they move between users,...
This episode explores Habit 1 of the 13 habits from Effective Secure Coding: Think in Trust Boundaries.

Why do secure values become dangerous when they move between users, services, files, APIs, databases, or privilege levels? And what changes when AI is writing the code for you?

We look at how to spot trust boundaries, make them explicit in your design, and give AI coding tools concrete security constraints instead of vague instructions like “make it secure.”

Secure coding starts with one question: where does trust change?
]]>1325false1fullhttps://www.spreaker.com/episode/treat-all-external-input-as-hostile--75760201Your database can lie to you. Your frontend definitely can. And AI will happily trust both unless you tell it not to.

This episode explores a core secure-coding rule: treat data as untrusted whenever it crosses a trust boundary - regardless of where it came from.

We look at why validation must happen in context, why the server should reconstruct facts it owns instead of trusting client claims, and how self-validating types can make unsafe states harder to represent.

And with AI generating more application code, these rules matter even more: AI needs explicit boundaries and constraints, not assumptions about what can be trusted.]]>https://api.spreaker.com/episode/75760201Tue, 13 Oct 2026 16:27:21 +0000Yariv TalYour database can lie to you. Your frontend definitely can. And AI will happily trust both unless you tell it not to. This episode explores a core secure-coding rule: treat data as untrusted whenever it crosses a trust boundary - regardless of where...Your database can lie to you. Your frontend definitely can. And AI will happily trust both unless you tell it not to.

This episode explores a core secure-coding rule: treat data as untrusted whenever it crosses a trust boundary - regardless of where it came from.

We look at why validation must happen in context, why the server should reconstruct facts it owns instead of trusting client claims, and how self-validating types can make unsafe states harder to represent.

And with AI generating more application code, these rules matter even more: AI needs explicit boundaries and constraints, not assumptions about what can be trusted.]]>1188false1fullhttps://www.spreaker.com/episode/in-safety-segregation-is-not-a-dirty-word--75860823separating data contexts is fundamental to software defense.
From the IDHS data exposure story to opaque identifiers, PII masking classes, and automated build gates, learn how proper segregation prevents path traversal and data leaks.
All of this, in a beginner-friendly deep dive generated by Gemini's Notebook-LM.]]>https://api.spreaker.com/episode/75860823Mon, 19 Oct 2026 15:34:58 +0000Yariv TalExplore why separating data contexts is fundamental to software defense. From the IDHS data exposure story to opaque identifiers, PII masking classes, and automated build gates, learn how proper segregation prevents path traversal and data leaks. All...separating data contexts is fundamental to software defense.
From the IDHS data exposure story to opaque identifiers, PII masking classes, and automated build gates, learn how proper segregation prevents path traversal and data leaks.
All of this, in a beginner-friendly deep dive generated by Gemini's Notebook-LM.]]>1248falsefull