AntiMalwareJuly 28, 2026🇷🇺Translated from Russian

Russian Ministry Clarifies No Plans to Disable Apple iPhones Despite New Device Registry

The Ministry of Digital Development of Russia has officially dismissed rumors that iPhones in the country could be remotely turned into useless bricks. The statement came in response to a formal request from deputy Vladimir Plyakin, who sought clarification on the future of Apple devices amid reports of possible restrictions if the company does not meet Russian legal requirements.

According to the ministry, neither the agency itself, other state bodies, nor telecom operators possess any legal powers to terminate service for devices of a particular brand. The response stressed that existing legislation does not allow authorities to disable specific equipment models with a single command.

Nevertheless, recent amendments to the law “On Communications” do provide for the creation of a national registry of user equipment identifiers. These provisions are scheduled to take effect on March 1, 2027. The final rules governing the system, including the types of data to be stored, the entities responsible for populating the database, and the agencies granted access, have yet to be approved.

The ministry is currently preparing the necessary draft regulations. Officials noted that while the registry will be established, it is premature to equate its launch with any scenario involving widespread disabling of iOS devices. Current laws simply do not support such measures.

Related articles

AntiMalwarePolicy & Regulation

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.

HabrPolicy & Regulation

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.

AntiMalwarePolicy & Regulation

Aladdin Obtains New FSB Certificate for CryptoFlash Encrypted USB Drive Valid Until 2029

Aladdin has received a new FSB Russia certificate for its Aladdin CryptoFlash hardware-encrypted USB drive. The certificate number СФ/124-5574 confirms compliance with cryptographic protection requirements for classes KS1 and KS2 and remains valid until 16 July 2029. The device now supports additional Russian Linux distributions including RED OS 7.3 and 8, Alt 8 SP Workstation, Alt Workstation 10, and the OS of the Moscow Electronic School. Read and write speeds have been increased to 11 MB/s while the graphical interface received improvements. The product uses the Magma encryption algorithm in hardware and operates as a clientless solution that requires no additional drivers or software. The previous certificate remains active until December 2028, allowing both versions of the device to be used in parallel for storing and transferring official and confidential information marked DSP.

AntiMalwarePolicy & Regulation

Microsoft Tightens Corporate Windows Activation with TPM-Bound KMS Servers

Microsoft is strengthening its corporate Windows licensing controls by introducing new requirements for KMS servers used in volume activation. The changes will bind KMS hosts to TPM hardware attestation, preventing cloned or fake servers from issuing licenses to unlicensed devices. Warnings will begin appearing in Windows Server 2025 in August 2026, with mandatory enforcement planned for the next LTSC release. Existing KMS systems will continue operating normally until the new rules take effect. The update targets enterprise environments with on-premises KMS infrastructure and does not affect individual consumer devices or common non-KMS activation bypass methods. Administrators can already verify TPM support on physical servers using the Get-TpmSupportedFeature command.