Russia's MinTsifry to Begin Issuing Official Code Signing Certificates in 2027

The Russian Ministry of Digital Development plans to start issuing state-backed code signing certificates for software developers in 2027, with corporate security certificates following in 2028. The initiative aims to help operating systems identify publishers and verify that code has not been altered after release. A draft government decree would grant MinTsifry the powers of a National Certification Authority, allowing it to set certificate requirements, issue and revoke certificates, define validity periods, and maintain a public registry. While the signature confirms origin and integrity, it does not guarantee the absence of vulnerabilities in the software. The law permits charging fees for certificates, but no decision on pricing has been made yet. Full recognition by operating systems, browsers, and app stores will be required, and foreign platforms are not obligated to trust the Russian certificates automatically.

AntiMalwareTranslated from Russian

Read at source

The Russian Ministry of Digital Development (MinTsifry) is preparing to issue official state certificates for signing software code. According to plans reported to Vedomosti, issuance of these certificates is scheduled to begin in 2027, while corporate security certificates are expected to follow in 2028.

The new digital signatures will allow operating systems to identify the publisher of an executable file and verify whether the code has been modified after its original release. This measure is intended to increase transparency for users when installing software from Russian developers.

A draft government resolution proposes granting MinTsifry the authority of the National Certification Authority. The ministry would define technical requirements for the certificates, issue and revoke them, establish validity periods, and maintain an official registry of issued certificates.

For end users, the practical benefit lies in the ability of the operating system to recognize the software publisher and display warnings about unknown developers. However, the presence of a valid signature does not mean the program is free of vulnerabilities; it only confirms the origin and integrity of the code.

The legislation allows the introduction of fees for obtaining certificates, but does not mandate them. Decisions regarding pricing and tariffs have not yet been finalized.

Technical acceptance of the new certificates by operating systems, browsers, and application stores will also be necessary. Outside Russia, automatic trust is not guaranteed, as foreign platform owners will make their own decisions. Developers targeting multiple markets may therefore need to obtain several different code signatures.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Policy & Regulation

Who Pays When AI Agents Err: Insurance for AI Risks in Russia and the West
Rostelecom Explores Underground Data Centers in Partnership With Norilsk Nickel for Stronger Physical Protection
How EVRAZ Built Effective Information Security Processes Without Draconian Restrictions