<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secrets-Sprawl on CuraSec</title><link>https://curasec.metacog.co.kr/tags/secrets-sprawl/</link><description>Recent content in Secrets-Sprawl on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 24 Sep 2026 15:49:46 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/secrets-sprawl/index.xml" rel="self" type="application/rss+xml"/><item><title>AI-Assisted Code Leaks Secrets at 2x Rate of Human-Written Code</title><link>https://curasec.metacog.co.kr/insights/2026-09-24-secrets-sprawl-is-an-identity-problem-that-ai-just-made-impo/</link><pubDate>Thu, 24 Sep 2026 15:49:46 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-24-secrets-sprawl-is-an-identity-problem-that-ai-just-made-impo/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> GitGuardian&amp;rsquo;s 2026 data showing AI-assisted commits leak secrets at twice the rate of human-written code is worth internalizing; audit whether your CI/CD pipelines have automated secret scanning enabled on AI-heavy repos before this statistic becomes your incident.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> If your engineering teams are adopting AI coding assistants, this report&amp;rsquo;s doubling of credential exposure rates warrants establishing or tightening AI tool policies and mandatory secrets-scanning requirements this quarter before an exposed credential becomes a breach.&lt;/li>
&lt;/ul></description></item></channel></rss>