Ideco NGFW Novum Earns Highest Customer Rating in Quadrant Technologies Import Substitution Study
Ideco NGFW Novum received the highest customer evaluation in the Matrix of Import Substitution 2026: NGFW study conducted by Quadrant Technologies, scoring 6.9 out of 10 against a market average of 6.3 and outperforming all seven other participants.
The research marks a shift in how Russian next-generation firewalls are assessed, moving beyond formal compliance with import substitution requirements toward real-world performance in production networks. Evaluations incorporated vendor specialized revenue and scores across 18 criteria focused on quality and functionality, with input from specialists who independently implement and operate the solutions.
Ideco achieved scores above seven points in 11 parameters. Customers rated administration convenience highest at 7.9, followed by technical support and partner network at 7.6, Zero Trust segmentation at 7.3, and integration capabilities together with core NGFW functionality at 7.2 each.
Despite these results, the product remains in the Development quadrant rather than Leadership, primarily due to the volume of specialized revenue rather than any deficiency in the solution itself. Analysts view Ideco as one of the strongest candidates for transition into the Leadership group as sales grow and the number of large deployments increases.
The findings align with independent testing performed by the Infosystems Jet laboratory. Ideco NGFW Novum passed 189 of 242 checks according to Methodology 3.0 and was the only participant to withstand an eight-hour stress test.
The Russian NGFW market is exiting the emergency import substitution phase. Customers now prioritize stability under load, update quality, documentation, support, and operational convenience over the mere presence of Russian software. Product cost remains a significant barrier, cited as the reason for rejection by 37.5 percent of surveyed organizations.
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.