Google's Android Developer Verification Rollout: Implications for Russian Devices and MDM-Managed Phones
Google announced last summer that certified Android devices would eventually require applications to come only from verified developers. The change, formally called Android Developer Verification, has prompted questions from Russian organizations about the future of MDM-managed fleets and in-house software distribution.
Devices undergo Play Protect certification to receive Google services including the Play Store. Certified phones can be identified by the presence of the Play Store or by checking certification status inside the store settings. The new verification process is separate from Play Protect scanning; it validates developer identity through package-name association rather than scanning for malicious code.
The verification mechanism is delivered as the Android Developer Verifier system app, which will be pushed automatically via Google Play services to devices running Android 8 and higher beginning in June 2026. Developers sign builds with private keys that Google links to specific package names such as ru.niisokb.mcc used by the SafeMobile client.
Google is rolling out the feature gradually. Registration opens to all developers in March 2026, early API access arrives in July, and the first mandatory enforcement wave targets Brazil, Indonesia, Singapore, and Thailand on 30 September 2026. Russia is absent from the schedule because Google has stated that devices in sanctioned countries are excluded to preserve application availability.
Two registration tiers exist. Full registration for companies requires identity verification, a website, and a D-U-N-S number. Limited registration for students and hobbyists needs no verification but restricts installations to 20 devices. SafeMobile has already completed full registration, guaranteeing continued distribution of its client.
Devices without Google services, Russian and Chinese custom firmware, and pure AOSP builds are unaffected. On certified Russian devices the sanctions exemption likewise prevents enforcement. MDM-distributed applications are also exempt because the IT administrator is deemed to have performed the necessary safety review.
If verification were ever applied to managed devices, organizations would need verified developer status or fall back to ADB sideloading and the extended-risk installation mode, both of which are impractical at scale. The offline behavior of the verifier remains undocumented; Google has not clarified whether cached developer data will allow continued installation without network access.
Related articles
Compliant Telegram Mini App Authentication via Russian ID Providers in My Anti-Social Network Project
The project 'My Anti-Social Network' demonstrates a production-grade approach to Telegram Mini App authorization that meets Russian identification requirements by separating user identity from delivery channels. Instead of relying solely on Telegram initData verification, the system routes authentication through VK ID, Yandex ID, and MAX using OAuth 2.0 / 2.1 flows with PKCE. Sensitive tokens never reach the browser; the client receives only short-lived one-time codes exchanged for HttpOnly session cookies. The architecture supports multiple front-ends including PWA, browser extensions, and Home Assistant integration while maintaining cryptographic protections around state parameters and code verifiers. The solution was implemented for an aggregator delivering personalized news feeds through Telegram, MAX, VK bots, and voice assistants.
Asset Management as the Foundation of Vulnerability Management: Unknown Assets Cannot Be Protected
The article explains that asset management forms the essential base for any effective vulnerability management program, as organizations cannot protect systems they do not know exist. It details multiple data sources including SIEM, NTA/NDR, Active Directory, CMDB, virtualization platforms, and cloud APIs that must be combined to build a complete inventory. Key record fields such as asset criticality, responsible owner, and last successful scan date are highlighted as critical for prioritization and SLA compliance. The piece examines new Russian regulations including FSTEC Order No. 117 and Federal Law No. 58-FZ that mandate accurate asset inventories to meet monthly scanning and 24-hour critical patch requirements. International frameworks such as CIS Controls v8.1, NIST CSF 2.0, and ISO/IEC 27001:2022 are compared, emphasizing lifecycle management and reaction processes for unauthorized assets. Emerging asset types including cloud resources, SaaS services, AI systems, containers, and IoT devices are discussed as expanding the attack surface faster than organizations can track.
Ozon Data Security Team Details Audit Framework to Eliminate Paper-Only Compliance
Alena, head of the Data Security group at Ozon, describes how the company built an internal audit process that focuses on actual risk reduction instead of producing lengthy formal reports. The team examines personal data, financial records, and other sensitive information across hundreds of microservices while checking role-based access, logging, encryption, and data flows. They analyzed more than 84,000 user-role pairs in one review and identified overly broad permissions on product tagging that could cause major financial losses. A notable case led to the removal of customer names, phones, and addresses from delivery boxes even though the practice was formally allowed under Federal Law 152-FZ. The group uses a scoring model based on data sensitivity, business importance, user count, and potential monetary impact to prioritize which systems to audit first. Additional criteria such as past incidents and critical information infrastructure status can be added to the model. The approach emphasizes real implementation of recommendations, cross-team communication, and hiring analysts who care deeply about practical security outcomes.
Microsoft to Make Passkeys Default Authentication in Entra ID Starting September 2026
Microsoft will transition Entra ID users to passkeys as the standard authentication method beginning September 1, 2026. The change aims to eliminate reliance on phishing-prone SMS and voice call codes. Existing SMS and voice users will be prompted to register passkeys during their next multifactor authentication. Passkeys rely on public-key cryptography and avoid shared secrets, blocking phishing, interception, credential reuse, and SIM swapping attacks. Support includes synced passkeys via iCloud Keychain and Google Password Manager, plus device-bound options like Microsoft Authenticator, Windows, and FIDO2 hardware keys. Native SMS and voice services will be fully retired on February 1, 2027, forcing affected tenants to adopt passkeys with no opt-out option.