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

Understanding GOST Cryptography Standards: A Practical Guide for Russian Developers

The article explains GOST cryptography standards in accessible language for developers who encounter requirements to implement electronic signatures through CryptoPro. It begins by clarifying that modern secure systems rely on three distinct cryptographic primitives rather than a single bundled technology.

Three Pillars of Cryptography

The first pillar is hashing, implemented in GOST R 34.11-2012 (Stribog), which produces a fixed-length digest from any input size while making reversal impossible. The second pillar is asymmetric digital signatures under GOST R 34.10-2012, which uses a private key on a hardware token to sign the hash and an X.509 certificate containing the public key for verification. The third pillar is symmetric block encryption via GOST R 34.12-2015 algorithms Magma and Kuznechik, which protect data confidentiality using the same key for both encryption and decryption.

Generations of Russian Standards

The text outlines three generations of domestic cryptography. The 1990s generation based on GOST R 34.10-94 and GOST 28147-89 is now obsolete. The 2000s generation introduced elliptic-curve signatures in GOST R 34.10-2001 but certificate issuance was discontinued in 2019. The current 2012+ generation combines strengthened elliptic curves, the Stribog hash function, and the Magma and Kuznechik ciphers that remain mandatory today.

Western Equivalents and Packaging Standards

Direct mappings are provided to international algorithms: Stribog corresponds to SHA-256, GOST R 34.10-2012 to ECDSA or RSA-2048, and Kuznechik to AES-256. Practical interoperability is achieved through the PKCS family and X.509 standards. PKCS#11 supplies the driver interface for accessing private keys stored on tokens such as Rutoken without exposing them to system memory. Certificate requests follow PKCS#10, while protected containers use PKCS#12. Final signatures are wrapped in PKCS#7 / CMS structures and enhanced with CAdES, XAdES, or PAdES profiles to include trusted timestamps and support different document formats.

The guide concludes that once the separate roles of each standard are understood, working with Russian cryptography becomes a predictable engineering task rather than an opaque process.

Related articles

Habr•Policy & Regulation

I Know but Cannot Tell: The Forensic Expert's Struggle to Share Real Cases Under NDA Constraints

A cybersecurity journalist reflects on the inherent difficulties of writing about digital and financial forensics while bound by strict confidentiality agreements. The article explores how verifying financial documents involves far more than spotting Photoshop alterations, raising questions about data origin, accuracy, interpretation, and the validity of conclusions drawn by examiners. Automated verification systems often produce conflicting results because they assess different aspects of a document, yet lack transparent justification for their verdicts. Attempts to anonymize cases, obtain client consent, or use synthetic data each carry limitations that can still lead to identification or fail to demonstrate actual expertise. The author recounts collaborating with an AI to draft the piece, only to realize the meta-discussion about the inability to publish real cases itself became the only publishable story. Ultimately, the piece highlights the tension between the professional desire to share knowledge and the contractual and ethical barriers that prevent meaningful disclosure in the field of forensic analysis.

Habr•Policy & Regulation

Three Hypotheses on Information Security Risk Assessment: Where Automation Truly Saves Time at Avito

Avito expert Irina Sozinova details how the company tested automation in its risk assessment process after scaling issues emerged with thousands of risks in the GRC system. The team formulated and piloted three hypotheses focused on automating typical risks, eliminating manual team preparation, and validating data to reduce InfoSec workload. Results showed a 16% drop in total risks registered, zero preparation time for teams, and improved coverage and context quality, though overall expert time savings were partially offset by new post-processing tasks. The pilot confirmed that automation works best on repeatable scenarios with stable data sources rather than promising immediate proportional time cuts. Avito plans to complete automation of context collection and finding classification this year to expand risk assessments across the company next year.

Habr•Policy & Regulation

Integrating OAuth 2.0 with PDP Architectures Without Modifying Core Authorization Engines

The article explores how to combine OAuth 2.0 delegated access with traditional PEP/PDP authorization systems. It proposes an OAuth-aware PDP layer that translates access tokens into standard PDP checks while preserving the original PDP implementation. Three main use cases are analyzed: stored user grants, tenant-level administrative grants, and scopes carried directly inside tokens. The design relies on synthetic subjects such as u+c and t+c pairs, ephemeral policies for token-embedded scopes, and optional OAuth-aware PAP components. Special attention is given to token contents, policy storage via PAP, and the need for deterministic subject identifiers. The approach supports both classic scope models and structured RAR-style authorizations while maintaining separation between OAuth grants and subject permissions.

Habr•Policy & Regulation

Russian Businesses Face 50-Ruble Fee per MVD Query for Passport and Residence Checks

The Russian government has backed a proposal requiring businesses to pay 50 rubles for each completed session querying Ministry of Internal Affairs databases. The fee covers checks on Russian passport validity, residence registration, residence permits, and foreign citizen migration records. Projected annual budget revenue reaches 120 billion rubles. Companies must still perform client identification under Federal Law 115-FZ and the Law on Communications, with fines up to 0.1 percent of own funds for banks or 500,000 rubles for telecom operators. Smart Engines highlights its Sherlock anti-fraud platform as a local alternative that detects over 600 forgery indicators, including deepfakes and NFC chip tampering, without repeated paid queries. The company cites a June 2026 legal opinion from the National Council of Financial Markets confirming that such tools can satisfy compliance requirements.