Jeep, Gateways and the Myth of Clean Isolation

In this episode, we dive into why the infamous Jeep hack is not just nostalgia, but a live architectural problem that the automotive sector still wrestles with today.

While connected features demand reach and product teams crave convenience, we explore how modern vehicle architectures struggle to neatly isolate trust boundaries in the real world.In theory, gateways, domain controllers, and embedded firewalls should separate critical functions.

In practice, however, diagnostics, telematics, backend services, and over-the-air update paths keep creating privileged bridges across those very boundaries.

The core challenge isn't simply about better CAN bus segmentation; it’s about whether a vehicle platform, already frozen across suppliers, validation cycles, and cost targets, can remain cleanly isolated as remote services and lifecycle updates continue to expand.

The real risk is a security boundary that only exists on paper and gets looser with every program year.

Join us as we unpack why the trust problem never truly left, but simply moved, and how emerging frameworks like UN R155, UN R156, and ISO/SAE 21434 are attempting to address these critical vulnerabilities