<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Compliance on No Semicolons</title><link>https://nosemicolons.com/tags/ai-compliance/</link><description>Recent content in AI Compliance on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 09 Jul 2026 10:47:24 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/ai-compliance/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Enterprise Firewall: How to Build Internal AI Coding Tools That Actually Pass Security Audits</title><link>https://nosemicolons.com/posts/ai-code-generation-enterprise-firewall-security-audits/</link><pubDate>Thu, 09 Jul 2026 10:47:24 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-enterprise-firewall-security-audits/</guid><description>&lt;p>Ever tried explaining to your security team why you need Claude or GitHub Copilot to help write code? If you&amp;rsquo;ve worked in enterprise development, you&amp;rsquo;ve probably hit that familiar wall where your perfectly reasonable request to use AI coding tools gets buried under compliance forms, security reviews, and months of &amp;ldquo;we&amp;rsquo;ll get back to you.&amp;rdquo;&lt;/p>
&lt;p>Here&amp;rsquo;s the thing though – security teams aren&amp;rsquo;t the enemy. They&amp;rsquo;re trying to protect the company from legitimate risks like code leaks, compliance violations, and data breaches. The solution isn&amp;rsquo;t to sneak around these requirements or wage war with InfoSec. It&amp;rsquo;s to build AI coding workflows that actually satisfy their concerns while keeping developers productive.&lt;/p></description></item></channel></rss>