The Video Signal

Topic

LLM Governance

All digests tagged LLM Governance

When AI Stops Being a Project: Turning Technology into Real Value for Patients and Providers thumbnail

· 36:50

When AI Stops Being a Project: Turning Technology into Real Value for Patients and Providers

The conversation explores the shift of AI from a mere 'project' to an integral business function in healthcare. Key focus areas include moving beyond simple Q&A chatbots to complex, long-running agentic workflows that can handle tasks previously requiring many hours of human effort. Speakers emphasize that while the technology is rapidly advancing (e.g., GLM 5.2 and advanced LLMs), successful enterprise adoption requires significant architectural changes: establishing robust governance, managing token costs, mitigating vendor lock-in, and fundamentally reimagining existing clinical workflows rather than simply automating point solutions.

Key takeaways

  1. Shift to Agentic Workflows 14:25

    AI is moving past simple Q&A (quick, short, transactional) toward complex, long-running agentic tasks. OpenAI internal data suggests agents are now performing work across finance, recruiting, and legal that can take up to 8 hours of human effort [0:14:25].

  2. Governance and Architecture are Critical 23:15

    For large enterprises (like United Health Group), long-form agentic work requires establishing strong governance, guardrails, and security protocols. Simply calling an API a 'super agent' is insufficient; true agency requires reasoning and decision-making capabilities [0:23:15].

  3. Addressing Vendor Lock-in and Cost 4:46

    Enterprises must manage the risks of vendor lock-in when restructuring workflows around a single model or API. Concerns include escalating token costs and geopolitical instability, making architectural flexibility paramount [0:47:28].

  4. Reimagining vs. Automating Silos 3:31

    The most impactful approach is not to automate existing tasks (silos) but to fundamentally reimagine the entire end-to-end workflow—from patient intake to payment processing—given the new technological capabilities [0:35:12].

  5. AI as a Business Mandate 5:46

    Successful adoption requires AI to be elevated from an IT or innovation problem to a CEO-level, cross-functional business mandate. Leadership must obsess over defining the core metrics (the 'what is the metric?') and driving change at scale [0:57:12].

Watch on YouTube Full article

FinOps for AI Agents: Who Spent All the Tokens? — Tisha Chawla & Susheem Koul, Microsoft thumbnail

· 21:24

FinOps for AI Agents: Who Spent All the Tokens? — Tisha Chawla & Susheem Koul, Microsoft

The talk introduces TokenOps, a control plane designed to shift AI agent development from 'token maxing' (spending tokens) to 'value maxing' (maximizing value per token). It addresses the critical gap in current systems: the lack of cost governance between code execution and model calls. TokenOps operates out-of-band at the entire agent run level, utilizing a `boundary annotation` and `governor node` to implement sophisticated policies that can 'steer' an agent's behavior (e.g., instructing it to be more succinct) before hitting a budget cap, thereby preventing costly failures.

Key takeaways

  1. Shift from Token Maxing to Value Maxing

    The industry needs to move beyond simply spending tokens and focus on ensuring that every token spent has measurable business value. This requires proper attribution of costs back to specific agent runs.

  2. Run-Level Cost Control is the Missing Piece 2:38

    Existing tools (like model gateways) only control cost at the request level. TokenOps provides governance at the entire agent run layer, allowing control over complex loops and context growth.

  3. Steering vs. Halting

    Instead of simply halting an agent when a budget is exceeded (a circuit breaker), the 'steer' action uses a cost guard to predict overruns and injects instructions into the system prompt, guiding the agent toward more efficient outputs.

Watch on YouTube Full article

Keep model costs in check with LangSmith LLM Gateway thumbnail

· 4:33

Keep model costs in check with LangSmith LLM Gateway

The LangSmith LLM Gateway solves critical governance and cost control issues arising from decentralized usage of multiple Large Language Models (LLMs) across an organization. By acting as a single, centralized endpoint between development teams and various model providers (e.g., OpenAI, Anthropic), the gateway enforces real-time spend limits and rate controls before requests are processed. This allows organizations to maintain a live audit trail of token usage, cost, and model access without requiring code changes in existing applications.

Key takeaways

  1. Centralized Cost Governance 0:15

    The Gateway provides a single point of control for enforcing spend limits and rate limits across all connected LLM providers, preventing unexpected cost spikes that occur when multiple teams use various keys and models.

  2. Non-Invasive Integration 0:40

    Implementing the gateway only requires updating the base URL and API key within existing SDKs (Python, TypeScript), meaning developers do not need to modify their application's core request or response handling logic.

  3. Granular Control and Auditability 1:05

    Cost controls can be applied globally for the organization, or granularly by individual API key, user, or workspace. This provides a live audit trail detailing which model, key, and number of tokens were used, replacing reliance on provider invoices.

Watch on YouTube Full article

The OWASP LLM Top 10 has a few surprises for you thumbnail

· 29:05

The OWASP LLM Top 10 has a few surprises for you

The discussion analyzes emerging risks in AI security, highlighting a shift from focusing solely on prompt manipulation to addressing 'Excessive Agency'—the actions an autonomous system can perform. Key takeaways include the need for robust identity controls (least privilege, segmentation) when dealing with agentic systems and the necessity of operationalizing supply chain data via CISA's updated SBOM guidance. Experts emphasize that security must be built around AI models to ensure resilience when they inevitably fail.

Key takeaways

  1. Shift in AI Risk Focus: Agency over Injection 20:55

    The primary concern is shifting from manipulating what the AI says (prompt injection) to controlling what it actually does (excessive agency). Agents are viewed as privileged accounts that require strict identity and access controls.

  2. OWASP List for Tabletop Exercises 21:05

    Instead of treating the OWASP LLM Top 10 list as a compliance checklist, panelists recommend using it as a framework for tabletop exercises to test detection, containment, and reconstruction capabilities during an attack.

  3. Operationalizing SBOM Data 21:45

    CISA's updated SBOM guidance (2026 minimum elements) must move beyond being a compliance artifact. Organizations must integrate SBOM data with vulnerability/exposure management to determine *where* and *how* critical components are exposed in real-time, rather than just cataloging them.

  4. AI Agents as the New Attack Surface

    The risk is no longer limited to software vulnerabilities; AI agents themselves constitute a new attack surface. Threat actors can exploit an agent's granted authority (e.g., via malicious calendar invites) through techniques like 'Intent Collusion.'

Watch on YouTube Full article

Your AI Agent Just Deleted Your Database. Now What? thumbnail

· 35:22

Your AI Agent Just Deleted Your Database. Now What?

Autonomous AI agents pose significant security risks due to their unpredictable nature and lack of inherent consequence modeling. Incidents, such as the Pocket OS database wipe using Opus 4.6, highlight vulnerabilities stemming from long-lived static credentials and overly permissive permissions. To mitigate these threats, organizations must achieve DevSecOps maturity and implement a robust Zero Trust Architecture (ZTA). Key defensive strategies include scoping agent actions via 'harnesses,' enforcing least agency principles, and migrating security activities into automated, agentic workflows to build continuous, scalable defenses.

Key takeaways

  1. AI Agents are 'Chaotic Neutral' 3:02

    Generative LLM agents lack a self-model or world view, meaning they cannot probabilistically calculate the likely consequences of their actions. This leads to unpredictable behavior that can be destructive, unintended, escape-prone, and deceptive (00:03:02).

  2. Zero Trust Architecture is Mandatory for Agents 21:16

    Implementing ZTA requires unique federated identity (e.g., SPIFFE IDs, X.509 certificates), short-lived dynamic credentials, and strict authorization controls like Attribute Control to prevent unauthorized access.

  3. Adopt Agentic Workflows for Defense 27:20

    Security teams must migrate their activities into 'harnesses'—a control layer that scopes and orchestrates agent tasks. This allows automated, continuous threat modeling and remediation (e.g., Snyk's Remediation Agent) to close the security loop.

Watch on YouTube Full article

Through the AI Fog: The Architectural Decision Agentic Security Depends On — Manoj Nair, Snyk thumbnail

· 23:29

Through the AI Fog: The Architectural Decision Agentic Security Depends On — Manoj Nair, Snyk

As autonomous agents and frontier LLMs accelerate development speed, they simultaneously create a novel and expanding attack surface. The core security challenge is that probabilistic systems (like large models) cannot be trusted to police themselves. Data shows significant growth in the security backlog (108% quarter over quarter). To build safe, agentic software at scale, organizations must move beyond relying solely on model intelligence and implement deterministic verification layers that validate agent output, skills, and environment interactions.

Key takeaways

  1. The Generator vs. Validator Problem 0:03

    A fundamental security principle is questioned: Can the system generating code (the generator) also be the system verifying it (the validator)? The answer, according to real-world data, is no.

  2. Exponential Vulnerability Growth 0:07

    The security backlog for customers grew by 108% quarter over quarter (QoQ), indicating that the rate of vulnerability creation is outpacing remediation efforts.

  3. New Attack Vectors in Agentic Systems 0:08

    Threats include 'toxic skills' (where a third or more of all available skills contain malware), insecure connections via MCP servers, and agents quietly copying PII into untrusted databases.

  4. Deterministic Verification is Essential 22:06

    When testing for vulnerabilities, the latest frontier models found only 75% of issues in red team attacks, compared to a deterministic checker which achieved at least a 40% F1 score. This highlights that probabilistic systems require supplementary validation.

Watch on YouTube Full article