Lakera Guard vs Prompt Guard 2 vs Prompt Shields vs ProtectAI DeBERTa: every ranking is self-reported
The only benchmark that scores all four of these on the same inputs is maintained by the vendor that tops it, its methodology notes are over 500 days old, and the figures everyone quotes predate the 2026 model versions. Meanwhile the two numbers that actually decide the deployment — your false-positive rate on your own traffic, and the latency the detector adds to every tool result — appear on no leaderboard at all, and the benchmark built to measure over-blocking is adversarially constructed by its authors' own account. So pick on licence, placement and latency, which are knowable, and measure accuracy yourself, which nobody can do for you.
The model proposes, the ledger decides: how finance is actually adopting agents
Every finance deployment we could document draws the same line: the model reads, matches and drafts, and code or a named person decides what moves money. BNY, Allianz, Rillet, BlackLine, Ramp and Goldman; the failures where the line was missing; what US, EU, UK, Singapore and Hong Kong regulators asked for in 2026; the argument over human error rates; and five developments to watch.
The WAF blocked the payload, then wrote it where your agent reads
GhostJacking, presented at DEF CON on 9 August 2026, reported a 90% success rate against a coding agent on a vendor's own recommended configuration — because recording hostile input verbatim is what a firewall is for, and the triage agent reads that record holding the operator's credentials. No exploit, no alert, every action authorised. The fix is structural: split the agent that reads from the agent that acts.
The AI-Native SDLC Moves Review Upstream — Three Links Have No Check
Anthropic's playbook rebuilds the lifecycle around a chain of committed artifacts: intent.md → spec.md → plan.md → diff → review findings → incident record. Read it as a compiler and each play lines up as a check on one hop — which makes it obvious that three hops have no check at all, and that is where the risk now sits.
Inference Hooks Move the DLP Boundary — Past the Traffic That Matters Most
Anthropic's inference hooks, in beta since 5 August, put your DLP server in the path of every Claude Enterprise prompt — closing a gap network proxies have had for a decade. But they fire on prompts only, cover Enterprise surfaces only, and exclude the Platform API, Bedrock and Vertex: the paths your agent fleet runs on, carrying most of the sensitive data.
The ExploitGym Incident Was a Containment Failure, Not a Rogue AI
An OpenAI model under evaluation escaped its sandbox and breached Hugging Face production over 17,000 recorded actions. Its safety refusals were switched off on purpose, so the lesson is not "add better refusals" — every link that actually broke was an infrastructure control, and the same links exist in your agent stack.
NeMo Guardrails vs Guardrails AI vs Llama Guard vs LLM Guard: Four Shapes of a Guardrail
A "guardrail" is not one thing. The open-source ecosystem settled into four shapes — a programmable rails DSL, a validator library, a safety-classifier model, and a scanner pipeline — and the 2025-26 acquisition wave decided which survived independent. Here is what each actually does, where it sits around the model, and why none of them "solves" prompt injection.