In this episode of Across the Tech Pond, David Marshall, Anthony Savvas, and Neil C Hughes sit down with IGEL CEO Klaus Oestermann to examine a blind spot that many organizations still underestimate. Endpoint resilience. Recorded after the hosts attended IGEL’s major end-user computing events in Miami and Frankfurt, the conversation cuts through conference noise to focus on what actually fails when ransomware strikes and why recovery often stalls at the device level rather than in the data center.
Klaus explains how cloud-first strategies have quietly shifted workloads from traditional endpoints to VDI, DaaS, and SaaS environments, often accessed via secure browsers. Yet despite this shift, most security strategies still assume the endpoint will cope. Drawing on real-world examples and customer data, he outlines IGEL’s preventive security model. He explains why locking down the operating system changes the economics, risk profile, and operational reality of end-user computing.
The discussion also covers IGEL’s latest announcements, from adaptive secure desktops and business continuity options for Windows environments, to AI Armor and the growing role of endpoints in securing decentralized AI workloads.
The episode also explores the wider ecosystem behind IGEL’s approach. With a rapidly expanding network of technology alliance partners, Klaus describes why IGEL positions itself as a neutral platform that brings together application delivery, identity, security, and hardware vendors rather than trying to own the entire stack. The hosts challenge him on cost savings, analyst blind spots, and why endpoint resilience still receives so little attention relative to cloud and zero-trust narratives.
As organizations face the end of support for Windows 10, rising compliance pressures, and increasingly targeted attacks, this conversation offers a grounded look at what actually keeps people working when things go wrong. If endpoint security has been an afterthought in your strategy, is it time to rethink where resilience really begins, and what happens when the endpoint fails?