Analyst Chat #277: Mastering IT Governance - Strategy, Compliance & the 1.5 Line of Defense

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

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.