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
Building Information Security Culture: How Welcome Training Turned Rules into Engaging Dialogue
A large software development company transformed its approach to information security awareness by replacing formal policy sign-offs and portal documents with an interactive Welcome Training program. The 45-minute in-person sessions target developers, analysts, testers, product managers, and designers, focusing on real-world context, attack mechanics, and personal relevance rather than prohibitions. Training covers global and local threat landscapes, password policies, corporate email usage, sensitive data storage with VeraCrypt, secure credential sharing via pbin, file verification with VirusTotal, and social engineering defense. It also highlights existing corporate tools including Kaspersky Endpoint Security, Kaspersky Secure Mail Gateway, and SIEM systems to emphasize layered protection. The format has increased engagement, improved retention of guidelines, fostered conscious compliance, and noticeably reduced incidents stemming from human error. The company stresses that technology alone fails without employee understanding of why rules matter.
Russian Ministry Clarifies No Plans to Disable Apple iPhones Despite New Device Registry
The Russian Ministry of Digital Development has officially stated that no government body or telecom operator has the authority to remotely disable iPhones or other devices from specific manufacturers. The clarification was issued in response to an inquiry from deputy Vladimir Plyakin regarding rumors of potential restrictions if Apple fails to comply with Russian legislation. Current laws do not permit turning user devices into non-functional bricks through any centralized mechanism. However, amendments to the law On Communications will introduce a national registry of user equipment identifiers starting March 1, 2027. The ministry is still developing the regulatory framework for this database, including what data will be collected and which agencies will have access. Officials emphasized that the existence of the registry does not imply any capability for mass device deactivation at this stage.
Russia's Top Investigator Proposes AI, VPN and Other Technologies as Aggravating Circumstances in Criminal Code
Alexander Bastrykin, head of Russia's Investigative Committee, has put forward a bill that would treat the use of artificial intelligence, VPN services and other information technologies as an aggravating factor when sentencing offenders. The proposal aims to address the growing role of digital tools in crimes ranging from fraud and data trafficking to terrorism, murder and sexual offences. Current Russian law lacks a universal provision allowing courts to factor in the deployment of such technologies during punishment decisions. Bastrykin argued that embedding specific technologies into dozens of Criminal Code articles would be inefficient because the IT landscape evolves too rapidly for static legal language. Instead, the committee advocates a systemic approach that recognises technology as a distinct aggravating circumstance when it serves as the primary instrument of the crime or significantly amplifies the harm caused. The measure would not criminalise the mere possession or activation of a VPN, smartphone or AI model; it would apply only when these tools materially enable or scale criminal activity. The bill has already been prepared by the Investigative Committee and was outlined in an interview with Interfax.
Bank of Russia Publishes Methodological Recommendations No. 3-MR on AI Security for Financial Market Participants
The Bank of Russia has released methodological recommendations No. 3-MR dated 16 June 2026, providing detailed guidance on ensuring information security during the development and use of artificial intelligence systems in the financial sector. The document builds on the earlier Code of Ethics for AI in finance and integrates with existing risk management, operational resilience, and data protection frameworks already familiar to credit institutions and other market participants. It introduces standardized terminology for AI-specific threats such as hallucinations, data drift, and poisoned datasets while outlining six risk categories and a four-stage AI system lifecycle model. Organizations are advised to apply threat modeling based on FSTEC methodology, implement proportional controls across data preparation, development, training, and operation phases, and maintain human oversight for high-risk automated processes. Special attention is given to supply chain risks involving third-party vendors and open-source components, requiring due diligence, provenance tracking, and contractual safeguards aligned with existing outsourcing standards. The recommendations remain non-binding yet signal clear regulatory expectations that are likely to influence future compliance checks and audits.