HabrAugust 7, 2026🇷🇺Translated from Russian

Web Certificate Trust Chains and State Access Risks Explained Amid Russian Banking Sanctions

The hierarchical model of X.509 web certificates has long been the foundation of HTTPS authentication and encryption. A tightly guarded root certificate, whose private key is protected by physical isolation and Shamir’s secret-sharing scheme among multiple guardians, signs intermediate certificates. These in turn sign the leaf certificates actually presented by websites.

Because ordinary users cannot independently verify every root, browsers and operating systems maintain curated lists of trusted roots. Adding a custom root, such as one operated by a corporation or an individual, is possible but leaves that entity solely responsible for the security of every site it vouches for.

Russian banks have recently begun issuing certificates signed by the MinTsifry root after major Western and later Chinese certificate authorities declined to issue or renew certificates because of sanctions. The author stresses that the technical security of the MinTsifry root is comparable to other roots provided its private key remains well protected; the real question is who can authorize new subordinate certificates.

Access by intelligence services is a central concern. The text notes that the FSB is presumed to hold influence over the MinTsifry root, while the NSA is widely believed to possess similar capabilities with U.S. commercial roots. The same logic applies to other agencies such as Mossad or Iran’s KSIR.

A fundamental limitation of current X.509 implementations is the inability to require signatures from multiple independent roots for a single site. The author describes a hypothetical multi-signature model in which a site would be simultaneously validated by roots from different geopolitical spheres, making undetected man-in-the-middle attacks by any single agency far more difficult.

Until such changes are adopted, users seeking to limit exposure are advised to maintain separate browsing environments, such as a dedicated smartphone or a browser running inside a virtual machine, when accessing Russian government or banking domains.

Related articles

AntiMalwarePolicy & Regulation

MAX Messenger to Open Source Code and Launch Developer Program for Alternative Clients

The Russian messenger MAX is preparing to open its platform to third-party developers by launching a dedicated developer program and providing API access. Approved participants will receive the official client's source code, design system, technical documentation, and access tokens to integrate with the platform infrastructure. The initiative targets IT companies from Russia and friendly countries that demonstrate experience with large-scale projects and adherence to strict security standards. All selected developers must implement secure development practices, robust encryption mechanisms, and undergo code audits to protect user data. The program supplies ready-made user registration and anti-fraud tools, while alternative clients remain bound by API usage terms focused on security compliance. Applications will be accepted via the official developer portal, although exact launch dates have not yet been disclosed.

HabrPolicy & Regulation

InfoWatch Details ARMA Wall NGFW Development for Industrial Systems Under Russian Import Substitution Rules

InfoWatch has published the second part of its interview series describing the ongoing development of the ARMA Wall next-generation firewall for industrial control systems. The product prioritizes on-premise processing without cloud agents to meet strict customer security policies and certification requirements. Engineers combine proprietary detection feeds with external sources, including indicators from NKCKI, while maintaining hundreds of thousands of signatures without disabling legacy rules for older Siemens controllers. Migration support relies on manual pre-project audits rather than automated tools, and the company works closely with domestic SCADA vendors to embed NGFW capabilities inside long-lifecycle OT environments. ARMA Wall is positioned as a more flexible and cost-effective alternative to data diodes because it allows granular command-level filtering and can emulate one-way traffic when required. The solution is already deployed at Roscosmos subsidiary RKK Energia after full certification and categorization.

AntiMalwarePolicy & Regulation

WhatsApp Developing AI Content Labeling Feature for Channel Admins to Meet EU Transparency Rules

WhatsApp, owned by Meta, is rolling out a new function that allows channel administrators to mark posts containing AI-generated or AI-edited media. The feature appears in the latest Android beta and stems directly from European Union requirements for transparency around artificial intelligence content. Administrators can long-press a message after publication and select an option to add an AI content label, which then displays a visible tag informing subscribers that the material was created or modified by neural network tools. The requirement applies specifically to images, videos, and other media files, while generated text remains exempt from mandatory labeling. WABetaInfo researchers spotted the change, noting that the label may become permanent once applied and that the rollout could initially target only jurisdictions with relevant legislation. Broader availability for iOS users and global deployment remain under consideration.

HabrPolicy & Regulation

Developer Builds Decentralized Messenger to Navigate Russian Laws 149-FZ and 152-FZ

A solo developer has created a lightweight messenger called Gram using the $mol framework and HyperBaza technology, designed to operate without collecting personal data or requiring logins. The project specifically examines compliance with Russian Federal Laws 149-FZ and 152-FZ, which regulate instant messaging services and personal data processing. The application supports encrypted peer-to-peer messaging, group chats via registries, and proof-of-work spam protection, while running primarily offline with optional decentralized nodes. Because messages remain encrypted on servers and no user identification occurs, the developer argues that obligations under the laws do not apply to private or home use. Public nodes must be shut down to avoid legal requirements such as phone-based identification and six-month message storage. The full source code is available on GitHub, and the service can be forked for deployment outside Russian jurisdiction.