Russia is starting to develop GOST, a formal standards framework for what it considers trusted electronic components, a fundamental shift in how technological sovereignty is being understood. The aim is no longer just to replace an imported microchip with a domestic one. Instead, the new system tries to identify whether a component can be trusted over its full lifecycle, from design and manufacturing through supply, modification, testing, and long-term operation.
This problem was the focus of attention at the pre-conference meeting in Moscow of the Russian Microelectronics 2026 Forum. Developers, industrial customers, and standards professionals explored how Russia could build a uniform regulatory framework for trusted electronics, especially for equipment used in vital infrastructure.
The basic question is simple but hard: Who can assure you what a microchip really performs, how it was made, and that its essential features can be preserved over its lifetime in operation?
What is GOST for Trusted Electronics?
GOST is the national standards system of Russia. In the trusted-electronics context, the suggested GOST framework aims at establishing formal standards for processes and evidence to prove that an electronic component can be trusted.
The focus shifts away from the final inspection of a finished chip. A trusted component requires evidence for its creation, verification, manufacture, and supply chain.
PNST 911-2024 has already been adopted in Russia, and GOST R 72507-2026, setting broad requirements related to the manufacture of trusted integrated circuits, has come into force in July 2026. At the same time, further standards are being established, which contain general provisions, technical conditions, requirements for the lifetime, development, delivery, storage, and aspects that can weaken trust.
The goal is therefore to develop not one isolated standard, but a wider family of standards for trusted electronics.
Why Source Code Isn’t the Whole Story
A major element of the new approach is that owning source code alone does not necessarily equate to technological independence.
MCST software director Alexey Mukhin summed up the situation at the Moscow conference, saying that source code can be transferred quickly, while the ability to take responsibility for the resulting product cannot be transferred so easily.
A complicated processor design may consist of hundreds of thousands or perhaps over a million lines of hardware-description code. To understand such a system, reproduce it, validate its performance, make changes, and support the resulting product requires extensive engineering skills.
The new Russian standards approach is therefore not just about whether documentation or source code exists but whether an organization is able to reproduce, validate, alter, maintain, and support the product.
From Chip to Full Cycle
This is one of the most important characteristics of the planned GOST architecture. Trust is now more and more seen as a property of the lifetime, not just something you check when a finished chip comes off the factory line.
The developing standards cover such areas as development techniques, manufacture, delivery, storage, and revisions to the product. The idea being that if a component is part of essential infrastructure, it should be controllable and predictable across its whole service life.
That involves taking on the supply chain too. A component may be technically secure but nonetheless constitute a strategic risk if its production depends on an uncontrolled foreign source, a specialized manufacturing process, or a vital tool that cannot be replaced.
The very availability of technology becomes part of the greater concept of trust for Russia.
Industry Divided Over New Rules
The creation of such standards caused a lot of disputes in the Russian electronics industry. The involved groups commented on the draft materials hundreds of times.
One draft on general provisions attracted 207 responses from 23 organizations. The draft on general technical conditions received 162 comments, and the document on the product life cycle received 181 comments.
The debates are important since the standards will eventually decide responsibility. Industry players have disputed whether some rules should be made more stringent, simplified, or deleted.
Such ideas call for additional mandatory language, while others say such rules could impose unneeded expenses or restrictions on businesses.
This demonstrates the tough balancing act the Russian standards system is faced with. The requirements must be stringent enough to provide significant assurance but not be so expensive or complex as to make trusted electronics unfeasible for household supply.
GOST Cannot Solve Everything
Another significant thing is that the GOST standard alone cannot build the whole certification and regulatory structure.
The technical standards could be used to set the development and life cycle management requirements. However, decisions on who conducts audits, who carries out testing, which bodies can undertake conformity assessments, and when particular standards become necessary must be laid down in government legislation and sector-specific rules.
This creates a separation of responsibilities between engineers, manufacturers, customers, testing organizations, regulators, and the state.
The developing model is thus more than a traditional technical standard. It is becoming part of a larger industrial and regulatory architecture.
Hardware Roots of Trust
Russia is also working on standards for trusted security components, which would give a hardware root of trust within bigger systems.
This approach is crucial, as vital security cannot rely only on software. Trusted hardware can provide the basis for verification of firmware, configuration data, cryptographic keys, and other vital data.
The proposed design effectively establishes a chain of trust that begins with the trusted electrical component, extends to the security component and the platform, encompasses the entire hardware-software system, and culminates in the critical infrastructure where it is deployed.
A New Definition of Technological Sovereignty
Russia’s growing GOST system thus embodies a broader idea of technological sovereignty. The goal is not just to develop a local substitute for an imported chip.
The emerging system is seeking answers to the question of whether Russia can design, verify, manufacture, supply, maintain, and ultimately take responsibility for key electronics throughout their operational life.
The task now is to translate these standards into a functioning ecosystem linking certification, procurement, industrial regulation, and domestic manufacturing.
The result might be a new class of regulated trusted electronics for vital civilian infrastructure, where trust is not just promised on a datasheet but shown across the whole lifecycle of the product.