Translated with AI from the Russian original.

The new generation of ViPNet SafeBoot trusted boot module can be integrated into ARM-based systems. The module is certified in accordance with the requirements of the FSB of Russia and the FSTEC of Russia.

According to InfoTeKS, special attention was paid to the integration of ViPNet SafeBoot 3 specifically into ARM platforms during the development of the new version. The requirements of customers who previously refused to use such platforms due to the impossibility of certifying workplaces without neutralizing threats related to OS loading were taken into account.

The company emphasized:

ViPNet SafeBoot 3.2 supports ARM platforms from various manufacturers and allows you to meet the requirements of such customers and create points of trust in the platform and its components, as well as in the loaded operating system.

To integrate ViPNet SafeBoot 3.2 into ARM platforms, a UEFI environment is required, which can be implemented on ARM platforms with EDK II (EFI Development Kit II). This is an open source project that is a set of tools and libraries for developing UEFI bootloaders and frameworks.

In ViPNet SafeBoot version 3.2, an environment has been prepared for ARM platforms built on Broadcom 2711/2837 and RockChip 3566/3568 chips. In addition, the new version implements support for "Foros", Esmart Gost tokens and smart cards.

Now on the front page

Articles

Why even a PC case should be branded

In Russian conditions, the popularity of PCs assembled by small local companies or in-house corporate IT departments continues to grow rapidly. Such solutions have historically been more popular in Russia than in other developed markets, but today new nuances have emerged in the segment's evolution, which we discussed with Karim LASKRI, Business Director of FSP Group in the CIS region.

News

Storage you can trust in the background: Basis SDS 2.3 released with scheduled diagnostics and an observer role

A storage system is the only infrastructure layer where an error cannot be “rolled back”: neither a reboot nor a configuration rollback will restore lost data. That is why users expect predictability from software-defined storage rather than just new features—ensuring background processes finish what they started, and administrators can see the cluster status not only “right now,” but also over time.