Habr•September 18, 2026•🇷🇺Translated from Russian

Alfa-Bank Balances Cloud Trust and Zero Trust Models During Migration to Yandex Cloud

Alfa-Bank has described how it migrated regulated on-premises workloads into Yandex Cloud while maintaining its existing Zero Trust posture alongside a new Cloud Trust model of shared responsibility.

The bank began with a classic perimeter-based architecture that enforced strict network segmentation and default-deny policies. When teams requested access to external cloud resources, traditional controls proved insufficient because Yandex Cloud exposes public APIs protected primarily by RBAC, policies, and ACLs rather than network firewalls.

Network Access

Engineers established a dedicated interconnect consisting of dark fiber between the bank and the cloud provider, encrypted with GOST algorithms. All management, integration, and data-plane traffic traverses this link. On-premises network objects were replicated in the cloud: each system maps to a cloud, each environment to a folder, and each folder contains isolated networks protected by Security Groups. IP address pools are announced across the interconnect so cloud subnets appear as additional data-center segments within the bank’s existing IP-address management system.

User Access

Authentication remains anchored in on-premises Active Directory and KeyCloak instances that are federated with Yandex Cloud IAM. Authorization is delegated to cloud-native service roles that map directly to Active Directory groups, preserving least-privilege principles while allowing teams to continue using familiar approval workflows.

Configuration Control

Every cloud project must produce architecture documentation that is reviewed before resources are provisioned through an internal platform integrated with the cloud API. The bank maintains an allow-list of approved managed services and enforces configuration standards through custom Cloud Security Posture Management checks written in code. Where internal expertise is limited, the team supplements its scanner with Yandex Security Deck modules.

SOC and Logging

Because the bank cannot collect every log type directly, it uses the provider’s YCDR service for detection and response while retaining full control over on-premises logs. This hybrid monitoring approach covers both control-plane and data-plane events generated inside Yandex Cloud.

The resulting environment currently runs 1,500 virtual machines, 100 managed services, and supports 1,000 identities. Alfa-Bank concludes that security in hybrid infrastructure requires deliberate decisions about where to retain control and where to accept Cloud Trust delegation, rather than attempting to enforce either model exclusively.

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.