Kaspersky Container Security Earns FSTEC Russia Certification as Antivirus Protection Tool
Kaspersky Container Security has obtained a new certification from FSTEC Russia that strengthens its position with customers who require formal regulatory approval. The solution for protecting containerized environments received certificate № 5122 dated 23 October 2026 and was confirmed compliant as an antivirus protection tool.
The certification covers the fourth level of trust requirements, the technical specifications for antivirus protection tools, and the protection profile of type Б (B) of the fourth class — IT.SAVZ.B4.PZ. Full details of the product and its capabilities are available on the vendor’s official product page.
According to Kaspersky, the certificate opens the possibility to use Kaspersky Container Security in government information systems, systems processing personal data, critical information infrastructure objects, and industrial automation and control systems. Any concrete implementation must still take into account the specific requirements of the target system and the limitations listed in the certificate.
The news is primarily relevant to government institutions, large businesses, and industrial enterprises that operate containerized applications inside regulated environments. Since 2023 the solution has already been included in the registry of domestic software maintained by the Ministry of Digital Development.
Related articles
Russian Lawmaker Clarifies Apple and Microsoft ORI Registry Listing Does Not Ban Products
State Duma deputy Anton Nemkin stated that the inclusion of Apple and Microsoft in Russia's ORI registry imposes standard data retention obligations without automatically prohibiting their products. The registry entry requires companies to store user information and message exchange records in Russia for three years and message content for up to six months. Nemkin emphasized that these rules apply equally to Russian and foreign digital market participants regardless of business scale or country of registration. The companies were added on October 2, 2026, while Google Meet has been listed since January 26. Although the status mandates data provision to authorized bodies in legally defined cases, the listing itself does not confirm that corporations will share Russian users' correspondence with the state. Non-compliance may trigger separate regulatory measures, but the deputy urged against exaggerating consequences through sensational headlines.
Russia Hands Out 2.2 Million Rubles in Data Leak Fines During First Half of 2026
Russian companies received 13 fines totaling 2.195 million rubles for personal data leaks between January and June 2026, according to new research from InfoWatch. This amount represents a 1.6-fold increase compared to the entire previous year, when total fines reached only 1.385 million rubles. The study shows that Russian penalties accounted for roughly 11 percent of the 115 global fines recorded during the same period. Approximately one quarter of the Russian cases involved violations caused by employee negligence. Organizations in the IT and information security, industrial, and trade sectors were fined most frequently. InfoWatch notes that turnover-based fines have not yet been applied and expects broader enforcement to begin in 2027.
Fines for Telegram Advertising May Be Delayed Beyond Transition Period
Russian authorities are reportedly considering delaying enforcement of new fines targeting advertisers in Telegram after the end of the announced transition period. According to sources cited by the Post- outlet, the government has not yet reached a clear decision on practical application of the advertising ban. Law enforcement agencies are also said to have stepped back from demanding strict punitive measures. Without official confirmation, advertisers and channel owners continue to operate under existing rules. The Federal Antimonopoly Service (FAS) had previously signaled stricter oversight starting in 2027, but current indications point to a possible extension of the status quo. Industry participants are advised to monitor developments closely as the situation remains fluid.
TLS Encrypted Client Hello Officially Standardized as RFC 9849
In March 2026 the IETF published RFC 9849, formally adopting TLS Encrypted Client Hello (ECH) as an official standard for protecting the Server Name Indication field during TLS handshakes. The specification replaces the earlier Encrypted SNI proposal and uses Hybrid Public Key Encryption (HPKE) as defined in RFC 9180 to encrypt the inner ClientHello. Major browsers including Chrome, Edge, Firefox, and Brave now enable ECH by default when Encrypted DNS (DoT or DoH) is active, while Safari remains an exception. Adoption on the server side remains limited; Cloudflare continues to be the only major CDN offering production ECH support, and real-world usage hovers around 0.06 percent of connections despite 20 percent of devices using encrypted DNS. The change breaks SNI-based traffic filtering, proxy inspection, and host-name-driven security analytics, prompting organizations to reassess monitoring architectures. OpenSSL added ECH support immediately after standardization, and Nginx introduced configuration options in version 1.29.4.