FAS Case Against Apple Will Not Brick iPhones for Russian Users
The Russian Federal Antimonopoly Service has initiated proceedings against Apple over the company’s failure to comply with a prior warning, yet the case will have no impact on the functionality of iPhone and other iOS devices in Russia.
Deputy Chairman of the State Duma Committee on Information Policy Andrey Svintsov confirmed that gadgets will continue operating exactly as before. The regulator demanded that Apple pre-install a national messenger application and a Russian app store on devices running iOS. While the company implemented the choice of a domestic search engine, it did not fulfill the remaining requirements according to FAS.
Owners of iPhone devices have been assured that authorities will not block hardware, turn devices into expensive paperweights, or apply any other technical restrictions. Svintsov, quoted by TASS, explained that the efforts of FAS, Roskomnadzor and other agencies are focused solely on documenting violations and subsequently imposing fines.
Any court rulings will stay in effect until Apple chooses to return to the Russian market. Before resuming legal operations, the company must first settle all accumulated penalties. Svintsov described the strategy as appropriate, noting that future payments would go directly into the Russian state budget.
For the time being, the regulatory claims remain exclusively Apple’s problem. No remote technical measures against Russian iPhone users are planned.
Related articles
Roskomnadzor Deploys 2.27 Billion Ruble AI Traffic Filter: Known Facts and Expert Speculations
Russian regulator Roskomnadzor has integrated a machine learning-based traffic filtering system into the automated security infrastructure of the Russian internet segment. The system, valued at 2.27 billion rubles, operates on domestic models within the agency's own infrastructure and connects to TSPU equipment that performs DPI-based filtering. Publications including Forbes, Meduza, 3DNews and SecurityLab base their reporting on the 2026 digital transformation passport, which also allocates additional billions for TSPU upgrades and hardware. Experts suggest the model analyzes packet sizes, session durations, traffic ratios and server characteristics rather than relying solely on known signatures, though no official performance metrics have been released. The exact role of the model—real-time analysis versus signature generation—remains unconfirmed, as does its impact on VPN protocols and potential for false positives affecting corporate and cloud traffic.
MinTsifry Proposes Requiring Telecom Operators to Install SORM Equipment Before Obtaining Licenses
The Russian Ministry of Digital Development plans to introduce legislation obligating telecom operators to deploy SORM surveillance systems prior to receiving operating licenses. Under the proposed rules, companies will only be permitted to begin serving subscribers after the equipment has been installed and handed over to law enforcement agencies. Non-compliance could result in license revocation through an extrajudicial administrative process. Current regulations allow operators to obtain licenses with a network diagram that merely indicates planned or existing SORM components. The change aims to close loopholes exploited by unscrupulous providers that repeatedly register new legal entities to operate without surveillance capabilities. Industry experts note that the minimum cost of a basic SORM complex starts at 5 million rubles, which could disproportionately affect smaller local providers without a transition period or scaled requirements.
GOST R 57580 Compliance: Defining Assessment Scope to Verify Real Protection in Financial Organizations
Financial institutions often maintain extensive documentation on information security yet still fail GOST R 57580 assessments due to mismatches between documented processes and actual infrastructure. The standards GOST R 57580.1-2017 and GOST R 57580.2-2018 set distinct requirements for protection levels and evaluation methodology. Correct application begins with identifying the organization's regulatory category under Bank of Russia rules such as Regulation 851-P for credit institutions or Regulation 757-P for non-credit financial organizations. Defining the precise assessment boundary is critical, including systems, remote access channels, virtualization components, and third-party interactions. Organizations must also distinguish between the full assessment scope and the representative sample selected for verification. Evidence collection requires both policy review and technical confirmation that controls function as intended across the evaluated environment.
Evaluating Secure Development Maturity: Comparing BSIMM, DSOMM, SAMM and GOST R 56939-2024
A detailed analysis compares four methodologies for self-assessing secure software development maturity in Russian companies. The review covers BSIMM from Black Duck, OWASP DSOMM, OWASP SAMM and the updated Russian national standard GOST R 56939-2024. Each model was tested through a simulated audit on a fictional company called ООО «Лиса и лосЬ» that uses GitLab, Nexus and SonarQube. The evaluation scored the methodologies on criteria including ease of maturity calculation, recommendation generation, roadmap building, heat-map creation and SDLC coverage. GOST R 56939-2024 and SAMM received the highest total scores of 35 and 34 out of 47. The article concludes that no single methodology covers all needs and recommends combining approaches tailored to specific company contexts.