InfoWatch has released the second installment of its technical interview series covering the development of ARMA Wall, the company’s next-generation firewall designed specifically for industrial automation and critical infrastructure networks.
The discussion addresses the use of artificial intelligence, migration challenges from foreign vendors, reliance on Russian hardware, certification processes, and the rationale for choosing NGFW technology over data diodes in OT environments.
Engineers confirmed that all data processing occurs on-premise. No cloud services or third-party agents are used because customer security policies and certification requirements explicitly prohibit such approaches. Internal AI agents are also avoided; only limited research-oriented services assist with vulnerability discovery and configuration analysis, with final decisions always made by human engineers.
The product incorporates both proprietary detection models and a curated mix of external threat feeds. Signatures are continuously optimized for performance while legacy rules remain active, including those protecting against exploits targeting Siemens controllers discovered in the 2000s.
Migration from foreign NGFW solutions is supported through detailed pre-project surveys that capture existing security policies. Automatic migration tools are planned but not yet implemented; manual configuration by experienced engineers is currently preferred to preserve context-specific filtering rules.
Regarding import substitution, InfoWatch noted that border firewalls have largely moved to domestic platforms in line with regulator requirements. However, full replacement inside ICS remains gradual because the typical lifecycle of industrial control systems is approximately 15 years. The company is deepening integration with Russian SCADA and controller vendors to enable native NGFW deployment within these long-lived environments.
Certified builds maintain fixed checksums, yet the regulator permits rapid updates for critical vulnerabilities without invalidating the certificate. This capability proved essential as the threat landscape evolved dramatically between the 2021 certification of the earlier Industrial Firewall product and 2026.
Detection feeds are delivered both online and offline for air-gapped networks. Administrators can also import indicators of compromise directly from NKCKI regulator letters; the system parses these indicators and automatically incorporates them into IDPS rules.
All development is performed by an internal team. Every component undergoes static and dynamic analysis before security specialists approve release. The company is implementing secure software development lifecycle processes and is preparing for relevant certification. Even embedded modules from other Russian vendors are tested to ensure they cannot become single points of compromise.
Testing of Russian processors such as Baikal has been completed, although production deployments still rely on imported platforms. Hardware is supplied through Kraftway, a state corporation subsidiary, with an average lead time of 60 days.
The product originated from industrial security requirements identified between 2017 and 2019. Its first commercial release, Industrial Firewall, targeted scenarios where foreign solutions from Hirschmann, Moxa, and Cisco were tightly coupled to specific verticals. ARMA Wall aims to provide unified protection across petrochemical, energy, and mining sectors while emphasizing security of critical information infrastructure over maximum throughput.
Deep packet inspection covers both legacy and modern industrial protocols, enabling command-level filtering at boundaries between corporate and OT networks as well as inside SCADA and PLC segments. In 2022 the solution blocked an attempt to deactivate licenses on Siemens controllers at a major Russian industrial site, preventing a full production stoppage.
Compared with data diodes, ARMA Wall offers lower total cost of ownership while providing equivalent one-way traffic enforcement plus bidirectional command inspection when needed. Virtual contexts are planned but not yet available; current segmentation requires multiple appliances. A KVM virtual machine image exists, and support for domestic hypervisors is in progress.
Pricing is influenced by hardware costs and the degree of import substitution. Reference deployments include the certified installation at RKK Energia (Roscosmos). The product integrates with third-party sandboxes and antivirus solutions using open protocols rather than attempting to create a closed ecosystem.
Pilot programs typically last one month, with equipment provided for up to three months. The recommended process includes two weeks of passive traffic analysis, two weeks of testing on an isolated segment, and two weeks of scaled rollout across the infrastructure.
