AI security insights, research, and product updates from the Humanbound team.
Promptfoo and Humanbound aren't competing for the same slot. Here's how Promptfoo's CI red teaming and Humanbound's continuous, compliance-mapped monitoring plug into each other, including how Promptfoo's scan results can train the Humanbound Firewall directly.
In 2017 I got a CVE for an unencrypted smart bulb. Nine years later, AI agents are shipping with the same gap: nobody tried to break them before launch. Here's how to break your own agent this afternoon, before someone else does.
A community library of agent attack scenarios, each mapped to the OWASP Top 10 for Agentic Applications and paired with the guardrail that closes it. Open, credited, and free to contribute to.
We released humanbound-firewall under Apache-2.0. A multi-tier runtime defense for AI agents, with each layer inspectable, escalating on uncertainty, and trainable on your own adversarial test data.
AI security maps to two different markets: AI for security (AI4Sec) and security for AI (Sec4AI). The Claude Mythos Preview made the distinction unmissable. Here is how to tell which one you are actually buying.
Moderation APIs catch harm and injection attempts but fail to enforce domain-specific policy. A cross-domain evaluation shows why production LLM systems need both moderation and policy reasoning layers.
The security industry is applying shift-left to AI agents. But AI agents aren't deterministic. The gap between testing on deploy and staying secure in production is where risk accumulates.
The AI agent security market is fragmenting into enforcement, identity, and control plane vendors. But the incident data tells a different story: most agents ship without any adversarial testing at all.
Agent security incidents keep sharing one root cause: agents deployed without adversarial testing. Enforcement is needed, but it is phase 3 of a lifecycle most organizations are entering at phase 1.
AI agent security won't be adopted through better dashboards. It'll be adopted when it disappears into existing workflows. Embed adversarial testing into your terminal via MCP - security becomes a conversation, not a context switch.
