<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>umage — Security</title><description>Insights tagged &quot;Security&quot;</description><link>https://umage.ai/</link><language>en</language><atom:link href="https://umage.ai/expertise/security/rss.xml" rel="self" type="application/rss+xml"/><item><title>Agents Build Spaghetti Code Too — and Then They Get Stuck in It</title><link>https://umage.ai/insights/agents-build-spaghetti-code-too/</link><guid isPermaLink="true">https://umage.ai/insights/agents-build-spaghetti-code-too/</guid><description>AI coding agents are great at building new things and surprisingly fast at making the codebase unworkable for themselves. Catching it early requires measurement that doesn&apos;t change between runs.</description><pubDate>Wed, 06 May 2026 00:00:00 GMT</pubDate><author>Morten Aslo-Østergaard</author><enclosure url="https://umage.ai/_astro/agents-build-spaghetti-code-too.S2hExAua_8cfrs.webp" length="0" type="image/webp"/></item><item><title>AI Sovereignty Is Two Questions — Most Teams Only Answer One</title><link>https://umage.ai/insights/ai-sovereignty-is-a-continuity-problem/</link><guid isPermaLink="true">https://umage.ai/insights/ai-sovereignty-is-a-continuity-problem/</guid><description>AI sovereignty usually gets framed as a data-residency question. That half gets attention. The other half — whether the workflow you built today still runs next quarter — often doesn&apos;t. Here&apos;s how we think about both at umage, and how we actually run it.</description><pubDate>Sun, 19 Apr 2026 00:00:00 GMT</pubDate><author>Allan Thraen</author><enclosure url="https://umage.ai/_astro/ai-sovereignty-is-a-continuity-problem.DkkdwGdi_2aom52.webp" length="0" type="image/webp"/></item></channel></rss>