<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Governance on CuraSec</title><link>https://curasec.metacog.co.kr/tags/ai-governance/</link><description>Recent content in Ai-Governance on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 31 Aug 2026 19:07:02 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/ai-governance/index.xml" rel="self" type="application/rss+xml"/><item><title>zk-SNARK Adversarial Probes Detect Post-Deployment LLM Tampering</title><link>https://curasec.metacog.co.kr/insights/2026-08-31-not-to-break-but-to-attest-adversarial-probes-for-privacy-pr/</link><pubDate>Mon, 31 Aug 2026 19:07:02 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-31-not-to-break-but-to-attest-adversarial-probes-for-privacy-pr/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Academic framework for detecting model drift after deployment using privacy-preserving proofs; no running systems to patch today, but the black-box token-probe approach is worth tracking as LLM supply-chain integrity tooling matures.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Offers a governance-relevant framing: proprietary LLMs can be silently altered post-approval, and cryptographic audit frameworks are emerging to address that gap — useful context for AI risk discussions with the board or auditors.&lt;/li>
&lt;/ul></description></item><item><title>Akamai Research: Top 5% of AI Super-Adopters Drive Outsized Enterprise Risk</title><link>https://curasec.metacog.co.kr/insights/2026-08-25-the-outsized-shadow-why-5-of-ai-users-are-your-biggest-secur/</link><pubDate>Tue, 25 Aug 2026 11:39:54 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-25-the-outsized-shadow-why-5-of-ai-users-are-your-biggest-secur/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Vendor-sourced (Akamai) but the framing that a small cohort of AI power users embedding unvetted tools into critical workflows creates concentrated risk is worth noting when building AI acceptable-use policy — size this against your own AI usage data before citing it to the board, given the single-source provenance.&lt;/li>
&lt;/ul></description></item><item><title>"Shady AI" governance risk: unauthorized AI agent data exposure</title><link>https://curasec.metacog.co.kr/insights/2026-08-21-why-shady-ai-is-security-s-next-big-governance-problem/</link><pubDate>Fri, 21 Aug 2026 11:38:25 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-21-why-shady-ai-is-security-s-next-big-governance-problem/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> The Meta incident illustrates how approved AI agents can inadvertently exfiltrate data to unintended audiences; worth reviewing how AI tooling in your CI/CD or dev workflows handles authorization boundaries before posting or sharing outputs.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> The case demonstrates a new category of data-loss event driven by AI agent behavior rather than malicious actors; consider whether current DLP and logging coverage would detect unauthorized AI-driven data postings in internal tools.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> This is an emerging governance gap requiring policy before controls; establish an AI agent usage policy this quarter that defines approval workflows, data-scope restrictions, and incident classification criteria for AI-driven exposure events.&lt;/li>
&lt;/ul></description></item><item><title>Shadow AI Agents Proliferate Without Enterprise Security Visibility</title><link>https://curasec.metacog.co.kr/insights/2026-07-28-shadow-ai-agents-are-multiplying-here-s-how-to-find-and-secu/</link><pubDate>Tue, 28 Jul 2026 13:01:43 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-28-shadow-ai-agents-are-multiplying-here-s-how-to-find-and-secu/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> No active exploitation or specific CVE, but the piece highlights how AI agents can silently accumulate OAuth scopes and API access across SaaS platforms — worth factoring into how teams audit third-party integrations and CI/CD automation going forward.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs, TTPs, or detection content — this is a governance awareness article. Useful background for understanding a new blind-spot category, but yields no immediate hunt or detection action.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Shadow AI agents acquiring autonomous permissions across SaaS estates without IT visibility is a real and growing governance gap; add an AI agent discovery and authorization policy to the Q3/Q4 roadmap before ungoverned agents create unaccountable data access or trigger compliance findings.&lt;/li>
&lt;/ul></description></item></channel></rss>