<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Edge-Ai on CuraSec</title><link>https://curasec.metacog.co.kr/tags/edge-ai/</link><description>Recent content in Edge-Ai on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 05 Sep 2026 13:51:48 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/edge-ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft guidance on securing edge AI in customer-owned environments</title><link>https://curasec.metacog.co.kr/insights/2026-09-05-how-to-secure-edge-ai-in-customer-owned-environments/</link><pubDate>Sat, 05 Sep 2026 13:51:48 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-05-how-to-secure-edge-ai-in-customer-owned-environments/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Covers trust verification patterns for AI assets deployed outside the corporate perimeter — worth reviewing if you&amp;rsquo;re designing attestation or supply-chain controls for edge ML workloads, but no patch or configuration action required.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> If your org is deploying AI models into customer-managed environments, schedule a policy review this quarter to define attestation, data-release, and credential-scoping requirements before those deployments scale.&lt;/li>
&lt;/ul></description></item></channel></rss>