<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Assistants on CuraSec</title><link>https://curasec.metacog.co.kr/tags/ai-assistants/</link><description>Recent content in Ai-Assistants on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Jul 2026 12:06:10 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/ai-assistants/index.xml" rel="self" type="application/rss+xml"/><item><title>EU mandates Android open sensor/mic/camera access to rival AI assistants</title><link>https://curasec.metacog.co.kr/insights/2026-07-17-e-u-orders-google-to-open-android-mic-camera-and-screen-to-r/</link><pubDate>Fri, 17 Jul 2026 12:06:10 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-17-e-u-orders-google-to-open-android-mic-camera-and-screen-to-r/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> This widens the Android attack surface by requiring deep sensor and UI-automation access for third-party AI assistants; worth tracking as it may affect mobile app threat models and permission assumptions in enterprise Android deployments.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Review enterprise mobile policy before the August 2027 Android 18 deadline — third-party AI assistants with mic, camera, and screen access on corporate devices will need explicit MDM governance and vendor vetting criteria.&lt;/li>
&lt;/ul></description></item></channel></rss>