Russian Ministry Proposes Mandatory Phone-Number Authentication for Foreign Websites and Apps
The Russian Ministry of Digital Development (MinTsifry) has put forward a proposal that would force foreign websites and mobile applications to authenticate users inside Russia solely by mobile-phone number. Traditional login methods such as email or social-network accounts could be removed under the new rules.
The requirement appears in the draft third package of anti-fraud measures titled Antifraud 3.0, according to business daily Vedomosti. In addition to phone-based authentication, owners of overseas resources would have to store registration data, login records and account-deletion information for three years and supply these records to Russian law-enforcement bodies on request.
The changes are intended to be introduced into Article 8 of the federal law On Information. The draft is currently undergoing inter-agency coordination; the government aims to submit the full legislative package to the State Duma in autumn 2026.
Industry observers note that international companies may be reluctant to redesign their authentication systems for a single market. They would need to identify Russian users and implement a separate login flow, an effort some services may decide is not worth the cost. As a result, certain platforms could withdraw from Russia, while some users may choose not to register at all if a phone number is mandatory.
A further complication concerns the definition of a foreign resource operating in Russia. Services such as Facebook and Instagram, both owned by Meta, have already been blocked and declared extremist organisations; their legal operation in the country has ceased, making enforcement of the new obligations practically difficult.
Antifraud 3.0 contains additional provisions, including a ban on disclosing the recipient’s personal data in SMS messages and an expansion of the data sets that telecommunications operators must retain for three years and disclose to special services.
Related articles
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.
Yandex 360 Email Archive Documentation Shows Search Snapshots and Former Employee Log Filters
The Yandex 360 administrator guide describes the email archive as a tool that stores copies of all messages sent and received by employees on the organization's domain. Two specific statements in the documentation indicate that each saved search returns a static snapshot that does not update automatically when new mail arrives, requiring manual cloning or recreation of the search to obtain current results. The same documentation states that the action log records every operation performed in the archive, yet the employee filter in the log interface only displays currently active accounts, making it impossible to select a former administrator by name. API 360 currently provides no documented endpoints for creating, executing, or retrieving archive searches, leaving all operations dependent on the web console. Additional notes clarify that messages remain available after an account is blocked but disappear once the account is deleted, and that messages removed before the archive was enabled cannot be recovered. These documented behaviors directly affect incident response and offboarding procedures that rely on historical email retrieval and audit trails.
Global AI Regulation: From Strict School Bans to Unregulated AI Havens
Countries are adopting sharply different approaches to AI oversight, ranging from comprehensive risk-based frameworks to outright prohibitions on generative tools in education. The United States relies on a patchwork of state laws and presidential actions, including Texas TRAIGA restrictions on high-risk AI systems and New York’s moratorium on generative AI in grades 2–8. The European Union enforces the AI Act with four risk categories, while Italy adds criminal liability and human oversight requirements in critical sectors. Norway and China have implemented some of the strictest classroom and content-authenticity rules, and Russia introduced its first baseline AI law defining sovereign models effective September 2026. Several nations have also blocked popular chatbots such as ChatGPT, DeepSeek, and Grok. Meanwhile, commercial platforms like FinamX continue integrating multiple AI models into financial workflows despite the regulatory tightening.