FSB Russia Certifies Rutoken Chip 3127 with Five-Year Cryptographic Key Validity
Aktiv has obtained an FSB Russia certificate for its embedded microcontroller Rutoken Chip 3127 under security classes KS1 and KS2. Following additional research, the validity period of the device's private cryptographic keys has been extended to five years.
The chip forms part of the Rutoken ECP 3.0 3127 product line and is designed for equipment that requires long-term cryptographic protection. Target platforms include servers, ATMs, workstations, tablets, biometric systems, industrial equipment, and IoT devices that must independently verify trust relationships while human operators focus on other tasks.
Rutoken Chip 3127 stores cryptographic keys in non-extractable form, authenticates users and devices, checks the integrity of system components, and enables trusted boot. At every stage it can validate executable code to prevent unauthorized modifications. The microcontroller also supports data encryption, derivation of session and derived keys, secure software updates, and protected TLS and VPN connections.
For data exchange over open channels the chip implements the CRISP protocol that complies with GOST R 71252-2024. Hardware-level protections include continuous monitoring of supply voltage and the integrity of the protective layer covering the die. Any detected physical tampering attempt triggers immediate blocking of operations. A dummy branch execution mechanism performs false commands to mask power consumption and timing information against side-channel attacks.
The company reports that Rutoken Chip 3127 has already completed pilot deployments. One project integrated the microcontroller into the OVISION biometric access control systems. Completion of the certification process is expected to enable serial production use in devices deployed within critical information infrastructure.
Related articles
Kubernetes Audit Policy Review: Checklist Targets Common Blind Spots in Rules
An experienced Kubernetes administrator shared a detailed review process for audit policies that often remain untouched for years after initial deployment. The 580-line policy was rebuilt using the Kubernetes Threat Matrix from RedGuard as the primary reference. The author highlights recurring issues such as outdated exceptions, missing coverage for new components, and legacy comments that obscure actual security intent. The resulting checklist focuses on principles rather than cluster-specific findings to help other teams perform effective policy audits. Key recommendations address rule completeness, exception management, and periodic full-scale reviews instead of incremental patching. The approach aims to restore audit policies as active security controls rather than accumulated technical debt.
Avoiding a Leaky Kubernetes Audit Policy: Real-World Configuration Breakdown
Kubernetes Audit Policy is typically configured once during cluster setup and then left untouched for years while accumulating exceptions for new components. Over time the policy stops functioning as a security control and instead becomes an archaeological layer of outdated comments such as "# temporary, TODO remove" that date back three years or more. The author recently reviewed their own 580-line configuration file that had been assembled from multiple sources. Primary reference was the Kubernetes Threat Matrix, which explains why many rules are designed to detect security-relevant actions rather than simply reduce log noise. Examples include targeted monitoring of RBAC modifications and deletion of events. The article emphasizes the need for periodic full reviews instead of incremental patching to maintain effective detection coverage.
CryptoPro Develops CryptoPro-Browser with Russian Cryptography for FSB Compliance
CryptoPro is creating its own browser called CryptoPro-Browser as part of the CryptoPro CSP 6.0 cryptographic information protection system. The product will include built-in cryptographic tools, support for the company's plugin, and TLS connections using Russian cryptographic algorithms. The development follows Google's removal of the CryptoPro extension from the Chrome Web Store in February 2025, which left new users without an easy installation method. The project has been coordinated with the FSB of Russia and targets scenarios requiring compliance with Russian information security regulations. CryptoPro plans to incorporate experience from its earlier Chromium-Gost project started in 2017, while also recommending Yandex Browser as an alternative. Analysts estimate the development cost at several tens of millions of rubles, with the main focus on corporate customers needing certificate management and specialized support.
Yandex 360 Email Archive Documentation Shows Search Snapshots and Former Employee Log Filters
The Yandex 360 administrator guide describes the email archive as a tool that stores copies of all messages sent and received by employees on the organization's domain. Two specific statements in the documentation indicate that each saved search returns a static snapshot that does not update automatically when new mail arrives, requiring manual cloning or recreation of the search to obtain current results. The same documentation states that the action log records every operation performed in the archive, yet the employee filter in the log interface only displays currently active accounts, making it impossible to select a former administrator by name. API 360 currently provides no documented endpoints for creating, executing, or retrieving archive searches, leaving all operations dependent on the web console. Additional notes clarify that messages remain available after an account is blocked but disappear once the account is deleted, and that messages removed before the archive was enabled cannot be recovered. These documented behaviors directly affect incident response and offboarding procedures that rely on historical email retrieval and audit trails.