<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Christopher dikesa</title>
    <description>The latest articles on DEV Community by Christopher dikesa (@christopher_dikesa).</description>
    <link>https://dev.to/christopher_dikesa</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3459295%2Ffd09f3ec-7578-410f-bd07-4a5d381a00e5.jpg</url>
      <title>DEV Community: Christopher dikesa</title>
      <link>https://dev.to/christopher_dikesa</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/christopher_dikesa"/>
    <language>en</language>
    <item>
      <title>I’m building **Cerbère-AG**, a security evidence layer for AI agents.</title>
      <dc:creator>Christopher dikesa</dc:creator>
      <pubDate>Sat, 26 Sep 2026 19:27:56 +0000</pubDate>
      <link>https://dev.to/christopher_dikesa/im-building-cerbere-ag-a-security-evidence-layer-for-ai-agents-fgh</link>
      <guid>https://dev.to/christopher_dikesa/im-building-cerbere-ag-a-security-evidence-layer-for-ai-agents-fgh</guid>
      <description>&lt;p&gt;&lt;a href="//app.cerbereag.site"&gt;&lt;/a&gt;I’m building &lt;strong&gt;Cerbère-AG&lt;/strong&gt;, a security evidence layer for AI agents.&lt;/p&gt;

&lt;p&gt;Most AI security tools focus on what goes &lt;strong&gt;into&lt;/strong&gt; the model: prompt injection, malicious inputs, jailbreaks, etc.&lt;/p&gt;

&lt;p&gt;I’m focusing on what happens &lt;strong&gt;after the model decides to act&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Cerbère-AG observes and controls agent actions across tool calls, including:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;tool-call monitoring and traces&lt;/li&gt;
&lt;li&gt;policy enforcement&lt;/li&gt;
&lt;li&gt;sensitive-action detection&lt;/li&gt;
&lt;li&gt;argument and capability checks&lt;/li&gt;
&lt;li&gt;budgets and execution limits&lt;/li&gt;
&lt;li&gt;trajectory-level risk detection&lt;/li&gt;
&lt;li&gt;human approval for sensitive actions&lt;/li&gt;
&lt;li&gt;security evidence for AI agent activity&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The idea is simple:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Don’t just ask whether an agent is safe to talk to. Ask whether it is safe to let it act.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I’m looking for developers and teams running AI agents in real or realistic environments to test Cerbère-AG and tell me where it fails.&lt;/p&gt;

&lt;p&gt;I’m especially interested in &lt;strong&gt;design partners&lt;/strong&gt; who can give real-world feedback on agent workflows, policies, approvals, and failure cases.&lt;/p&gt;

&lt;p&gt;If you build AI agents, security tooling, MCP integrations, or autonomous workflows:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Farne9bsa8xdp9rbxt0tn.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Farne9bsa8xdp9rbxt0tn.png" alt=" " width="798" height="106"&gt;&lt;/a&gt;&lt;br&gt;
→ Give me your feedback: what would you expect a production-grade agent security layer to catch that Cerbère currently doesn't?&lt;/p&gt;

&lt;p&gt;And if you find the project useful, a ⭐ on GitHub helps people discover it.&lt;/p&gt;

&lt;p&gt;I’m more interested in &lt;strong&gt;breaking it and finding its weaknesses&lt;/strong&gt; than in compliments.&lt;/p&gt;

&lt;p&gt;If you have an agent that you think could expose a real failure mode, send it my way.&lt;/p&gt;

&lt;p&gt;→ Test it: &lt;a href="//app.cerbereag.site/"&gt;&lt;/a&gt;&lt;br&gt;
→ GitHub: &lt;a href="//github.com/chrismsmr-celcom/cerbere-AG"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>buildinpublic</category>
      <category>security</category>
    </item>
    <item>
      <title>We benchmarked our prompt-injection detector against OWASP's LLM Top 10</title>
      <dc:creator>Christopher dikesa</dc:creator>
      <pubDate>Sat, 26 Sep 2026 19:11:17 +0000</pubDate>
      <link>https://dev.to/christopher_dikesa/we-benchmarked-our-prompt-injection-detector-against-owasps-llm-top-10-k9k</link>
      <guid>https://dev.to/christopher_dikesa/we-benchmarked-our-prompt-injection-detector-against-owasps-llm-top-10-k9k</guid>
      <description>&lt;p&gt;We just published our first public benchmark for AgentGuard, the runtime we're building to secure AI agents in production.&lt;br&gt;
The honest version: our deterministic (regex) layer alone catches 91.5% of prompt injection attempts with zero false positives, in under 2ms. Adding a ML layer pushes recall to 98.1% — but the trade-offs are real: ~450ms latency, and a 33% false-positive rate on benign prompts that were deliberately worded to look like attacks.&lt;br&gt;
We're publishing the numbers as they are, weaknesses included, and mapped everything to the OWASP Top 10 for LLM Applications so it's easy to compare.&lt;a href="https://www.cerbereag.site/blog/detecting-prompt-injection-in-production" rel="noopener noreferrer"&gt;&lt;/a&gt;&lt;a href="https://www.cerbereag.site/" rel="noopener noreferrer"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>cybersecurity</category>
      <category>llm</category>
      <category>security</category>
    </item>
  </channel>
</rss>
