<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Compliance</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Compliance feed</description>
    <item>
      <title>Presentation: From Consumers to Builders: Turning 200 of our Team into Agent Creators in Two Weeks</title>
      <link>https://www.infoq.com/presentations/building-internal-ai-agents/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Compliance</link>
      <description>&lt;img src="https://res.infoq.com/presentations/building-internal-ai-agents/en/mediumimage/medium-1790246283432.jpeg"/&gt;&lt;p&gt;Ben Maraney shares how Forter demystified AI agent creation for technical and non-technical staff. He discusses leveraging custom MCP servers, combining no-code and code-based platforms, sidestepping complex RAG setups, and aligning security and legal teams to accelerate internal agent adoption across R&amp;D.&lt;/p&gt; &lt;i&gt;By Ben Maraney&lt;/i&gt;</description>
      <category>Model Context Protocol (MCP)</category>
      <category>Productivity</category>
      <category>QCon AI Boston 2026</category>
      <category>Large language models</category>
      <category>Compliance</category>
      <category>AI Security</category>
      <category>Transcripts</category>
      <category>Agents</category>
      <category>Governance</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>presentation</category>
      <pubDate>Mon, 28 Sep 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/building-internal-ai-agents/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Compliance</guid>
      <dc:creator>Ben Maraney</dc:creator>
      <dc:date>2026-09-28T11:00:00Z</dc:date>
      <dc:identifier>/presentations/building-internal-ai-agents/en</dc:identifier>
    </item>
  </channel>
</rss>
