Topic starter
14/09/2026 10:09 am
TL;DR: Inline LLM judges are accurate but too expensive and slow to inspect every prompt, retrieval, and tool call at agent scale, according to Lasso Security, while its CPU-based LEAP architecture claims GPU-class detection with far higher throughput and lower latency. The key issue is not model quality, but whether security guardrails can be affordably run on every AI action without becoming the bottleneck.
Editorial analysis by NHI Mgmt Group, based on content published by Lasso Security: “Introducing LEAP: CPU-based AI Security Guardrails with GPU-Class Accuracy”.
Key questions
Q: What breaks when AI agent guardrails exist only in policy documents?
A: Policy-only guardrails fail when an agent can act at machine speed and the control cannot interrupt the action.
Q: When should security teams prioritise lightweight guardrails over LLM judges?
A: Prioritise lightweight guardrails when most traffic is low-ambiguity and the security decision is closer to classification than reasoning.
Q: How do security teams know runtime AI guardrails are actually working?
A: Look for blocked poisoned inputs, flagged anomalous outputs, and traceable enforcement before responses reach users or downstream systems.
Practitioner guidance
- Map guardrail placement to risk tiers Use lightweight first-pass inspection for low-ambiguity prompts, retrievals, and tool calls, and reserve reasoning-heavy checks for the subset that is genuinely uncertain.
- Measure the real cost per decision Track latency, throughput, queueing, and per-request spend for every guardrail path so the team knows whether the control can stay inline as traffic grows.
- Preserve full agent trace context Avoid truncating or splitting prompts, retrieved documents, and prior actions in ways that remove the relationships a security decision depends on.
Bottom line: GPU-backed or API-based LLM judges can be accurate, but production agentic AI makes cost, latency, and throughput part of the security problem itself.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/09/2026 10:10 am
AI security is becoming a throughput problem, not just a model-quality problem. The article correctly shifts attention away from whether a judge can reason and toward whether it can run inline on every prompt, retrieval, and tool call. That is the right lens for production agentic AI, where the control that cannot keep up is effectively absent. Practitioners should treat guardrail capacity as a first-order security requirement.
A few things that frame the scale:
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: What should practitioners do when agentic AI inspection depends on conversation context?
A: They should preserve the relationships among prompts, retrieved documents, permissions, and prior actions before making a safety decision. If inspection breaks those links through truncation or split processing, the control can miss attacks that only become visible across the full trace. That is a governance problem as much as a technical one.
👉 Read our full editorial: CPU-based AI guardrails may outscale GPU judges in production