EU Forces Google to Open Android Microphone, Camera and Screen Access for Rival AI Assistants
The European Union has directed Google to grant competing AI assistants equivalent access to sensitive Android resources, including the microphone, camera, and screen content. The decision aims to ensure that third-party services receive the same capabilities currently available to Gemini.
The measures encompass eleven core system functions such as voice-command activation, home-button invocation, background execution, and direct access to on-device AI models. Alternative assistants will be able to use these resources without being set as the default service.
Environmental data access will provide real-time streams from the microphone, camera, screen, and speakers. All releases must follow the same consent and notification standards that apply to Google’s own services.
AI tools will also be permitted to interact with other applications, send messages, schedule appointments, adjust device settings, and execute multi-step tasks. Screen automation will enable assistants to open applications inside a virtual window and simulate taps and typing while the user continues other activities.
The majority of these changes are required to ship in Android 18 by 1 August 2027. Simultaneous activation of multiple assistants via voice keywords will be implemented in Android 19, with a final deadline of 1 August 2028.
Every function will remain subject to explicit user authorization. For particularly sensitive operations such as screen automation, system integration, and centralized app-data queries, Google may impose objective security and certification requirements.
Related articles
Ideco NGFW Novum Earns Highest Customer Rating in Quadrant Technologies Import Substitution Study
Ideco NGFW Novum achieved the top customer score of 6.9 out of 10 in the Matrix of Import Substitution 2026: NGFW research conducted by Quadrant Technologies, surpassing the market average of 6.3 and outperforming seven competing Russian solutions. The study evaluated vendors based on specialized revenue alongside 18 criteria covering product quality and functionality, with ratings provided directly by specialists who deploy and operate the firewalls in production environments. Ideco excelled in 11 parameters above seven points, including administration convenience at 7.9, technical support and partner network at 7.6, Zero Trust segmentation at 7.3, and both integration capabilities and core NGFW functionality at 7.2. Despite strong product scores, Ideco remains in the Development quadrant rather than Leadership due to lower profile revenue volume, positioning the company as a prime candidate for advancement with increased sales and large-scale deployments. Complementary testing by Infosystems Jet laboratory showed Ideco NGFW Novum passing 189 of 242 checks under Methodology 3.0 and becoming the sole participant to complete an eight-hour stress test. The broader Russian NGFW market is shifting away from emergency import substitution toward demands for real-world stability, updates, documentation, support, and usability, with product cost cited as a rejection factor by 37.5 percent of respondents.
Kubernetes Audit Policy Review: Checklist Targets Common Blind Spots in Rules
An experienced Kubernetes administrator shared a detailed review process for audit policies that often remain untouched for years after initial deployment. The 580-line policy was rebuilt using the Kubernetes Threat Matrix from RedGuard as the primary reference. The author highlights recurring issues such as outdated exceptions, missing coverage for new components, and legacy comments that obscure actual security intent. The resulting checklist focuses on principles rather than cluster-specific findings to help other teams perform effective policy audits. Key recommendations address rule completeness, exception management, and periodic full-scale reviews instead of incremental patching. The approach aims to restore audit policies as active security controls rather than accumulated technical debt.
Avoiding a Leaky Kubernetes Audit Policy: Real-World Configuration Breakdown
Kubernetes Audit Policy is typically configured once during cluster setup and then left untouched for years while accumulating exceptions for new components. Over time the policy stops functioning as a security control and instead becomes an archaeological layer of outdated comments such as "# temporary, TODO remove" that date back three years or more. The author recently reviewed their own 580-line configuration file that had been assembled from multiple sources. Primary reference was the Kubernetes Threat Matrix, which explains why many rules are designed to detect security-relevant actions rather than simply reduce log noise. Examples include targeted monitoring of RBAC modifications and deletion of events. The article emphasizes the need for periodic full reviews instead of incremental patching to maintain effective detection coverage.
CryptoPro Develops CryptoPro-Browser with Russian Cryptography for FSB Compliance
CryptoPro is creating its own browser called CryptoPro-Browser as part of the CryptoPro CSP 6.0 cryptographic information protection system. The product will include built-in cryptographic tools, support for the company's plugin, and TLS connections using Russian cryptographic algorithms. The development follows Google's removal of the CryptoPro extension from the Chrome Web Store in February 2025, which left new users without an easy installation method. The project has been coordinated with the FSB of Russia and targets scenarios requiring compliance with Russian information security regulations. CryptoPro plans to incorporate experience from its earlier Chromium-Gost project started in 2017, while also recommending Yandex Browser as an alternative. Analysts estimate the development cost at several tens of millions of rubles, with the main focus on corporate customers needing certificate management and specialized support.