Advertise on podcast: KuppingerCole Analysts Videos

Securing and governing AI agents is, according to Matthew Gardiner, the hardest problem in cybersecurity harder than securing the internet itself. In this episode, Matthias discusses with Matthew why, explore the six-category framework KuppingerCole Analysts has developed to address it, and dig into the first and most critical building block: AI Visibility and Observability Platforms. Key Topics: Why agentic AI is harder to secure than the internet non-determinism, autonomy, and scale Threat actors using agents too: how the attack surface is accelerating on both sides The six-category security and governance framework for agentic AI crawl, walk, run AI Visibility and Observability Platforms: why discovery comes first and what it actually covers Organizational alignment: why security teams shouldn’t take the blame for every agent failure Authority vs. access: why what an agent can do matters more than what account it uses 🤖 “When the internet was rolled out, we had time to catch up. Agents roll into a world where businesses are already completely dependent on IT and there are hundreds or thousands of them doing different things.” Matthew Gardiner on why this time really is different. 📊 KuppingerCole Analysts’ AI Visibility and Observability Platform research is live and the AI Security Fabric is landing in days. Watch this episode, then dive into the research at kuppingercole.com.

AI can build your IAM connector in an afternoon. But was the connector ever the bottleneck? In this episode, Matthias invited Patrick Teichmann, lead advisor at KuppingerCole Analysts, to talk about his newly published advisory note on IAM customization governance and ask the harder question: what happens when the cost of building disappears, but the cost of maintaining doesn't? Key Topics: Why AI removes the development bottleneck in IAM — but exposes the real one: requirements definition The danger of saying yes too easily: how AI makes it tempting to build what should never be built Security risks in AI-generated IAM code: what the research actually shows A seven-step framework for evaluating any IAM customization before writing a single line The customization registry: how to build transparency and governance into what already exists When to stop customizing and ask whether the platform itself is the wrong tool ⚠️ "AI makes code cheap but the bottleneck in IAM was never primarily creating the code." Patrick Teichmann on why removing the development barrier without fixing requirements definition is a recipe for a new generation of Lotus Notes. 📄 Patrick's advisory note on IAM Customization Governance is published on the KuppingerCole Analysts website now; watch this episode first, then dive into the research.

MCP servers are showing up on the internet without authentication, malicious tool definitions are being injected into trusted projects, and three security teams are defending the same environment without sharing a single threat signal. In this week's episode, Matthias sits down with Alexei Balaganski, Lead Analyst and CTO at KuppingerCole Analysts, to dig into the real MCP security problem and why the answer isn't an MCP security product. Key Topics: ✅ The LocalAI attack: 23 unprotected MCP servers, root access in minutes, military data exposed ✅ Is MCP a new security problem or just a new label for old ones? ✅ The Deadbugs attack: how tool descriptions were silently poisoned to manipulate AI agents ✅ Who is responsible for MCP security: Anthropic, the vendor, or you? ✅ Tool poisoning, prompt injection, and the gaps between AppSec, NetSec, and endpoint teams ✅ Monday morning recommendations: what to actually do about MCP security right now 🔐 "Models reason, APIs act, and identity grants the authority to act" Alexei Balaganski's one-line summary of why MCP security cannot be solved by a single tool or a single team. 📅 MCP is a symptom, not the disease, join KuppingerCole Analysts at the upcoming AIdentity & NHI Impact Day, CIAM Impact Day, and Identity-Centric Cybersecurity Summit events in Germany to continue this conversation in person.

Orchestration has been part of the Identity Fabric concept from the beginning but most organizations are still getting it wrong. In this episode, Matthias sits down with Martin Kuppinger, to explore why orchestration is one of the most underestimated architectural capabilities in identity management, what "integration debt" really means, and why vibe coding is the new Lotus Notes disaster waiting to happen. Key Topics: ✅ Orchestration inside the Identity Fabric: capability, not product category ✅ Integration debt: how organizations quietly accumulate orchestration they no longer understand ✅ The Lotus Notes warning: what vibe coding and no-code/low-code get wrong at scale ✅ Why AI can document and test code — but still doesn't understand what it's doing ✅ Start with orchestration strategy, not the tool — and always ask "how do I get rid of this?" ✅ Ownership and governance: who is responsible for orchestration artifacts when people leave? 🪷 "Lotus Notes: a wonderful example of where vibe coding went rogue — organizations ending up with thousands of databases, not knowing who did it, why, or if it's still needed." Sound familiar? Martin Kuppinger on why orchestration governance is non-negotiable. 📅 Join KuppingerCole Analysts at the AIdentity & NHI Impact Day on October 6th in Munich

SSPM is dead, long live SaaS Security and AI Governance. When Matthias and Matthew last spoke in February, SaaS Security Posture Management was the topic. Six months on, the market has moved decisively: shadow SaaS and shadow AI are now the same problem, and the vendors covering them have merged the two worlds into one. What changed? What do the new capabilities look like? And what does KuppingerCole Analysts' newly published research says about where the market is heading? Key Topics: ✅ Why SSPM is passé — and why SaaS Security and AI Governance belong together ✅ Shadow IT, shadow SaaS, shadow AI: the same problem at increasing speed and scale ✅ Discovery as the foundational capability: you can't govern what you can't see ✅ Where to sniff: browser plugins, email, endpoints, identity providers, and procurement systems ✅ AI agents as a new identity type — and why the controls for humans and NHIs are converging ✅ Market outlook: the AI side is hitting another gear, and acquisitions are coming 🔍 "The majority of SaaS and AI applications are still unknown to the IT and security team." Matthew Gardiner on why discovery is the gating capability — and why most organizations haven't closed that gap yet.

AI writes the code. But who checks it, and who is accountable when it goes wrong? In this episode, Matthias is joined by two colleagues: Guillaume Teixeron, bringing 20 years of experience on the product side of identity and authentication, and Jonathan Care, KuppingerCole Analysts' Director of Practice AI. Together they tackle the security gap opening up between how fast AI generates code and how slowly organizations are catching up on assurance, provenance, and accountability. Key Topics: ✅ AI in software development: from hype to structural baseline — but governance is still improvised ✅ Three tectonic shifts in AppSec: provenance, scale, and non-human identity ✅ Why organizations have industrialized code production but not code assurance ✅ The core question: can you trust AI to verify AI-generated code? ✅ Agent autonomy in production pipelines — the next flashpoint nobody has resolved yet ✅ How regulation (CRA, NIS2, DORA) will settle the provenance argument before the market does ⚡ "We have industrialized code production. We have not industrialized code assurance." Jonathan Care on why the security control set was built for human-authored code moving at human speed — and neither assumption is true anymore. 📅 Join KuppingerCole Analysts at the AIdentity & NHI Impact Day in Munich this October — where the accountability and provenance questions raised in this episode will be front and center.

What happens when you put three AI agents in a room and tell them to solve the same problem? Anthropic ran the experiment — and the results are more unsettling than you'd expect. In this episode, Matthias Reinwarth sits down with Jonathan Care, KuppingerCole Analysts' newly appointed Director of Practice AI, to unpack the findings and ask what they mean for enterprise security, identity management, and the CISOs trying to govern it all. Key Topics: ✅ Anthropic's multi-agent experiment: three Claude instances, one codebase, unexpected outcomes ✅ Why coordination does not emerge naturally from intelligence — in agents or in humans ✅ The anthropomorphism trap: why comparing agents to dogs, kids, and wizards is useful but dangerous ✅ Social pressure, mechanisms, and the open research problem of agent cooperation ✅ Risk tolerance as a prerequisite for any agentic architecture — and how to define it ✅ Why correlated agents without coordination break your redundancy and business continuity assumptions 🤖 "If agents are highly correlated but lack coordination, redundancy does not provide the risk diversification we would expect." Jonathan Care on why multi-agent systems are a different beast and why CISOs need to treat them that way. 📅 Join KuppingerCole Analysts at the AIdentity & NHI Impact Day on October 6th in Munich where many of the open questions raised in this episode will be on the agenda

IVIP, Identity Visibility and Intelligence Platform, was one of the hottest acronyms to emerge from the identity market in 2025. But almost a year on, has it delivered on its promise? And more importantly, could AI already be making it obsolete before it even matures? In this episode, Matthias and Martin Kuppinger pick up where they left off and ask the hard questions about IVIP's future. Key Topics: ✅ IVIP revisited: still a set of capabilities, not a platform — and vendors are mostly relabeling ✅ Can AI make IVIP obsolete before it ever becomes a mature category? ✅ How AI is finally tackling IGA's oldest unsolved problem: application integration at scale ✅ Why IVIP falls short on action — spotting anomalies is not the same as acting on them ✅ IVIP, ITDR, and IGA convergence: does the category distinction even matter anymore? ✅ Strategic advice for IVIP vendors: observability, automation, and the path to relevance 🤖 "The MVP can frequently be done well with AI doing it at scale, manageable, as a real solution and not a set of homegrown tools? That is a very different story." Martin Kuppinger on why AI changes everything for IVIP — and nothing at once. 📅 Don't miss the KuppingerCole Analysts Identity Fabric Impact Day on September 9th in Cologne

Digital sovereignty is one of the most talked-about topics in European tech policy right now and according to Alexei Balaganski, most of the conversation is going in completely the wrong direction. In this episode, Matthias sits down with Alexei to challenge the assumptions behind the sovereignty debate, redefine what the term actually means, and lay out what organizations should really be doing about it. Key Topics: ✅ Why the "digital sovereignty" conversation has gone wrong — and what Alcatraz has to do with it ✅ The only correct definition of sovereignty: can you keep operating when a dependency disappears? ✅ Why sovereignty is just business continuity engineering — not a procurement decision ✅ How sovereign Europe really is today: the numbers are worse than you think ✅ Why "buy European" is a political preference, not a security strategy ✅ Decentralization, crypto agility, and distributed storage as practical sovereignty tools 🏛️ "Sovereignty is not about who you're buying from, it's about what happens when you can no longer buy from them." Alexei Balaganski on why the European sovereignty debate is asking the wrong question entirely. 🔐 "Nobody, not even the EU, should prescribe how to solve your sovereignty issues." A rare episode with almost no AI but possibly the most important conversation KuppingerCole Analysts has published this year.

When an OpenAI test model escaped its sandbox and attacked Hugging Face's production infrastructure, headlines called it a Skynet moment. But was it? In this special flash news episode, Matthias Reinwarth brings together four KuppingerCole Analysts experts — Alexei Balaganski, Jonathan Care, John Tolbert, and Martin Kuppinger — to cut through the noise and ask the real question: what actually went wrong, and what should organizations do about it? Key Topics: ✅ What actually happened: two separate incidents dressed up as one dramatic story ✅ Why the sandbox failure was a containment and design problem — not an AI apocalypse ✅ Jonathan Care's core argument: the breach was credentials, not packets — you can't firewall your way out ✅ Non-human identity and agent identity as the real unsolved problem at the heart of the incident ✅ Secrets sprawl, overprivileged service accounts, and the absence of least privilege for AI agents ✅ Was it a containment failure, an identity failure, an observability failure, or a governance failure? 🐯 "OpenAI had a pet tiger and the tiger escaped, Hugging Face was just walking down the street." Alexei Balaganski on why the most dramatic AI security story of the year was actually two separate failures. 🔐 Four KuppingerCole Analysts experts, one incident, and the identity governance lessons every organization needs to hear.

The Identity Fabric isn't just a concept, it's a working tool that KuppingerCole Analysts advisors use every day with clients. In this second episode of the fabric mini-series, Matthias sits down with Martin Kuppinger and Phillip Messerschmidt to explore how the Identity Fabric and Reference Architecture are applied in real client engagements, why capability-based thinking beats tool-centric thinking every time, and how the fabric evolves to stay relevant in a world of constant buzzwords. Key Topics: ✅ How the Identity Fabric is used in practice: maturity assessments, gap analyses, roadmaps, and tool selection ✅ Why the right order always goes capabilities → services → tools — never the other way around ✅ What happens when tools are used for things they were never meant to do ✅ Why organizing teams around capabilities — not tools — is the future of IT operations ✅ The Identity Fabric built for 2040: long-term thinking in a fast-moving market ✅ How the fabric absorbs buzzwords like IVIP, ISPM, and ITDR — and why that proves the concept 🧵 "Every second day someone comes up with a new buzzword, the Identity Fabric helps you strip it down to capabilities and ask: is there really something new here?" Martin Kuppinger on why structured thinking beats buzzword bingo. 📅 This is episode two of KuppingerCole Analysts' fabric mini-series, the Cybersecurity Fabric and AI Security Fabric episodes are coming next. Subscribe so you don't miss them.

Zero trust has a label problem. After more than a decade, the term has been stretched, diluted, and attached to products that don't come close to delivering what zero trust actually promises. In this episode, Matthias sits down with Alexei Balaganski, lead analyst at KuppingerCole Analysts, to share the findings from six months of research and reveal which vendors actually built a real Zero Trust Platform. Key Topics: ✅ Why zero trust is a strategy, not a product — and what that means for procurement ✅ The four non-negotiable requirements for a real Zero Trust Platform ✅ What separates a genuine platform from a collection of tools with a zero trust label ✅ NHIs, AI agents, and data protection as the new frontiers of zero trust architecture ✅ Three critical questions every RFP for a ZTP should include 🔐 "Stop looking for a Zero Trust Platform" - yes, really. Alexei Balaganski explains why that mindset shift is the most important thing a CISO can do before opening a single RFP. 📊 The KuppingerCole Analysts Zero Trust Platform Buyers Compass and Leadership Compass are both published: watch this episode first, then dive into the research.

Seven years ago, KuppingerCole Analysts introduced the Identity Fabric concept and it has shaped how organizations structure identity management ever since. In this episode, Matthias sits down with Martin Kuppinger, co-founder and distinguished analyst at KuppingerCole Analysts, to revisit the origins of the Fabric paradigm, explain why it still holds today, and preview where it's headed next into cybersecurity, AI security, and beyond. Key Topics: ✅ Why the Identity Fabric concept emerged in 2019 — tool sprawl, siloed IAM, and the collapse of the perimeter ✅ What "fabric" actually means: a capability-driven layer connecting all identities to all services ✅ Why capabilities should define tools — not the other way around ✅ How the fabric concept scales to cybersecurity and AI security architectures ✅ The fabric in practice: maturity assessments, requirements analysis, and target operating models ✅ A look ahead to 2040: why the core principles are built to last "The job of identity management is to provide seamless access for everyone and everything to every service" — seven years on, that definition still holds. Find out why in this episode. 📅 This is the first episode of a new series on the fabric paradigm, covering Identity Fabric, Cybersecurity Fabric, and AI Security Fabric.

Build or buy, it sounds like a simple question, but for most organizations, it's one of the most consequential and poorly structured decisions they make. In this episode, Matthias sits down with analyst and advisor Phillip Messerschmidt, who turned his hands-on advisory experience into a structured framework for getting the make-or-buy decision right every time. Key Topics: ✅ Why "we can build it cheaper" is almost always a biased and incomplete argument ✅ How the originating perspective (business unit, IT, security) shapes — and distorts — the decision ✅ The most common and costly mistakes organizations make when going the build route ✅ When buying is clearly the better path: expertise gaps, speed, scalability, and vendor roadmaps ✅ Why security and risk must be part of the decision from day one — not an afterthought ✅ A structured, holistic framework for making the right make-or-buy call "This cheap solution can quickly turn into a security risk, an open attack, a breach — and much more cost than thinking about risk by design." Sound familiar? This episode is for you.

Alert overload, 24/7 coverage gaps, and human threat actors who never stop — the SOC has problems that traditional SOAR and rule-based systems simply can't solve. In this sponsored videocast, KuppingerCole analyst Matthew Gardiner and Rick Bosworth, Head of Product Marketing at Torq, dig into the findings of KuppingerCole's Emerging AI SOC Leadership Compass and explore what it actually takes to build an AI-powered security operations center. Key Topics: ✅ Why rule-based SOAR has hit a wall — and how AI agents address what it can't ✅ The autonomy dial: why full automation isn't the goal and how to build trust incrementally ✅ Integrations, RAG, and MCP: the new data infrastructure powering AI agents in the SOC ✅ DIY SOC vs. managed providers: how agentic AI is reshuffling the build-vs-buy decision ✅ Where to start: alert triage, phishing, and typosquatting as low-risk entry points ✅ Guardrails, transparency, and the non-deterministic challenge of AI-driven security "AI agents hate people because they're slow" — but full autonomy isn't the answer either. Find out how leading SOC teams are finding the right balance between speed and control. This videocast is sponsored by Torq — featured in KuppingerCole's Emerging AI SOC Leadership Compass. Read the report, then watch this session to hear the findings brought to life.