Habr•October 9, 2026•🇷🇺Translated from Russian

Troubleshooting Erroneous TSPU Blocks: How Admins Can Collaborate with Russian Regulators

A portion of Moneta clients recently lost connectivity to company servers due to filtering on the TSPU segment of the network. Initial checks of firewalls and bidirectional traces ruled out internal causes, while client sites and Pay URL payment notifications also became unreachable.

Eugene, a DevOps engineer at Moneta, documented the full diagnostic path using curl, traceroute, nping, and a custom Python script for post-handshake tracing. Basic tests showed timeouts on TLS Client Hello packets, with responses stopping after operator routers and BRAS equipment.

When payload-specific filtering was suspected, hexadecimal TCP data was extracted from Wireshark and replayed via nping and netcat to reproduce retransmissions. A dedicated script allowed TTL-controlled probes after completing the TCP handshake to isolate the exact hop where drops occurred.

Verification from multiple Russian nodes via globalping helped exclude routing faults. Once TSPU involvement was confirmed, a request was filed through the VTS personal account using organization credentials from Gosuslugi, specifying source and destination ranges, ports, protocol, and traffic justification.

After the request received “Partially Accepted” status without restoration, escalation to DCOA via support_asbi@dcoa.ru or support_asbi@noc.gov.ru was required. Obtaining the four-digit TSPU site identifier (e.g., 4XXX) proved difficult until direct contact with SSOP at supervising@noc.gov.ru succeeded.

The final diagnostic package sent to DCOA included DNS results, ICMP and TCP traces, curl output, and confirmation of ongoing traffic from the source IP. The article stresses that active traffic must be present during DCOA analysis and that the process applies only to legitimate information resources of legal entities.

Related articles

AntiMalware•Policy & Regulation

Russian Ombudsman Proposes Eurasian Code of Ethics to Regulate Destructive Online Content

Russian human rights commissioner Yana Lantratova has urged the Eurasian Alliance of Ombudsmen to develop a shared code of ethics for handling destructive digital content that targets children and adolescents. The proposal, presented on 16 November at the alliance's eleventh meeting in Moscow, addresses the absence of a formal definition of destructive content in Russian law, which currently hinders effective blocking of harmful materials. Lantratova highlighted seven key categories of destructive content, including normalization of violence, incitement to suicide, cyberbullying, fraud, and recruitment into terrorist or extremist groups. She cited a sharp rise in terrorism-related criminal cases involving minors, from 86 in 2024 to 239 in 2025 according to the Investigative Committee. The ombudsman also warned about the growing use of deepfakes for child extortion and advocated a platform-engagement model over outright bans, which she said risk increasing curiosity among young users. Representatives from Bahrain, Iran, Kazakhstan, Kyrgyzstan, Mongolia, Tajikistan, Uzbekistan, Sri Lanka, Serbia, and Armenia participated in the discussions.

AntiMalware•Policy & Regulation

Unconfirmed Reports of Steam Blockade in Russia: Valve Faces User Data Demands and Tax Scrutiny

On November 16, media outlets and Telegram channels reported that Russian authorities are demanding user data from Valve's Steam platform, including accounts registered in Kazakhstan, while threatening to block the service. The claims also suggested plans to track undeclared income from high-value in-game skins, but no official statements or documents have confirmed these assertions. The original source was an analytical piece by ProFinance that cited unnamed sources without specifying any government agency, official, or legal document. Roskomnadzor, the Federal Tax Service, and other agencies have made no such announcements, and Valve has not confirmed receiving any requests. Confirmed information is limited to tax payments: Kazakhstan's Committee of State Revenues reported that Valve paid approximately 2 billion rubles in VAT for the first half of 2026, the highest among foreign internet companies. This amount more than doubled compared to the same period in 2025, attributed to Russian users relocating their accounts to the Kazakh region after Visa and Mastercard exited Russia. Vice Speaker of the State Duma Vladislav Davankov opposed any potential blockade, comparing it to freezing bank deposits, and pledged to raise the issue at the Duma session on November 17.

AntiMalware•Policy & Regulation

Russia's MinTsifry Mandates Qualified Electronic Signatures for Remote eSIM Registration to Combat Fraud

Russia's Ministry of Digital Development has directed telecom operators to allow remote eSIM issuance and contract signing exclusively through enhanced qualified electronic signatures (UKEP). The use of enhanced unqualified electronic signatures (UNEP) via the GosKlyuch system will be prohibited starting December 1. Operators must re-integrate with GosKlyuch exclusively through the SMEV interagency system and verify all remotely issued eSIMs registered before November 15. The measures address widespread fraud involving unauthorized number porting to attacker-controlled eSIMs, enabling interception of SMS codes for banking and messenger access. Independent experts note that UNEP certificates require only a verified Gosuslugi account, making them vulnerable to account takeover, while UKEP demands stricter identity verification. Over 15.7 million UNEP certificates were issued through GosKlyuch in the first eight months of 2026.

Habr•Policy & Regulation

Employee Data Transfers Within Russian Holdings: Why Affiliates Count as Third Parties Under 152-FZ

Russian data protection law treats companies within the same holding as separate operators, requiring written employee consent for any transfer of personal data during internal job moves. The analysis examines five practical routes for handling transfers between legal entities such as ООО «Торговый дом» and ООО «Логистика» while complying with both 152-FZ and the Labor Code. Direct exchange of documents is generally prohibited without consent under Article 88 of the Labor Code, but routes through the employee, separate consent forms, or data processing agreements with a central HR entity can reduce risk. Storage of records after termination remains lawful for statutory accounting and archival periods without additional consent. The article provides detailed decision trees, consent templates, and warnings about fines ranging from 150,000 to 700,000 rubles for non-compliance. Roskomnadzor guidance and recent amendments to Article 9 of 152-FZ are also addressed.