Positive Technologies Discontinues Active Development of PT AF 3, Shifts Focus to PT AF PRO and PT Cloud AF
Positive Technologies is winding down active development of PT Application Firewall 3 and reallocating its main engineering resources to PT AF PRO and the cloud-native PT Cloud AF.
Current customers of the older WAF solution will continue to receive technical support, but the product is unlikely to gain major new features going forward.
Why the strategy is changing
Over the past decade, corporate web infrastructure has expanded dramatically. Organizations that once managed a handful of websites now operate hundreds of applications, APIs, and microservices distributed across on-premises data centers, multiple clouds, branch offices, and subsidiary networks.
At the same time, the threat landscape has evolved. Compromising a web application is frequently no longer the attacker’s final objective but rather a foothold for deeper penetration into internal corporate networks.
According to Positive Technologies data, exploitation of vulnerabilities in internet-accessible web applications remains the most common initial access technique, responsible for 36% of successful attacks against corporate environments.
New flagship: PT AF PRO
The company’s primary focus is now PT AF PRO, a solution developed from scratch over more than six years. It is designed to protect hundreds of applications in highly distributed infrastructures and offers centralized security policy management, remote site connectivity via external agents, and the ability to apply updates without interrupting traffic processing.
Protected applications can be segmented into isolated spaces with dedicated compute resources and granular access controls for security events. This architecture targets large enterprises and holding companies that operate multiple security teams with differing service requirements.
Cloud offering gains priority
The second strategic priority is PT Cloud AF, a cloud-delivered WAF for applications and APIs that eliminates the need to purchase and maintain hardware. Customers can manage the service themselves or delegate configuration and ongoing operations to a partner.
Over the past year, the customer base for PT AF PRO has doubled, reflecting growing demand for scalable, distributed web application protection.
Related articles
Home Lab Overhaul: Securing Proxmox Infrastructure After Discovering 63,000 Forgejo Spam Accounts
A home lab administrator migrated Docker stacks to new LXC containers on Proxmox and uncovered multiple security misconfigurations. The setup relied on Cloudflare proxying, MikroTik port forwarding to NPMplus with CrowdSec, and Cloudflare Tunnels for admin panels. After fixing IP address logging in the WAF, logs revealed 63,021 spam accounts created on a Forgejo instance that had open registration. The operator disabled registrations, recreated the instance from verified Git mirrors, and eliminated direct internet exposure by routing all traffic through Cloudflare Tunnel. Additional controls included Zero Trust policies, device enrollment restrictions, and TOTP on Guacamole. The changes removed open ports, enforced proper client IP visibility for CrowdSec, and segmented public, limited, and admin access paths.
Benchmarking AES-GCM and Ascon AEAD Performance on ESP32 and ESP8266 for Industrial Telemetry
Researchers conducted detailed experiments measuring the real-world costs of three AEAD implementations on ESP32 and ESP8266 microcontrollers used in industrial telemetry scenarios. The study compared mbedTLS AES-128-GCM, legacy Ascon-128 via CryptoLW, and a portable C++ port of NIST Ascon-AEAD128 across three load profiles ranging from stable low-frequency packets to maximum-rate 10 ms intervals. Key metrics included AEAD execution time, CPU cycles, memory usage, UDP transmission success rates, and power consumption captured via TC66C. Initial tests revealed significant UDP packet loss on ESP32 under MAX load due to ENOMEM and ENOBUFS errors in the lwIP stack, which were largely resolved after network handling improvements. Results showed AES-GCM completing in roughly 618 µs on ESP32 versus 803 µs for legacy Ascon-128, while the reverse held on the slower ESP8266 where legacy Ascon outperformed AES by a factor of approximately 3.5. The work highlights that network stack limitations often dominate over cryptographic overhead in high-throughput industrial sensor deployments.
ARinteg Earns Golden Partner Status from Ideco for NGFW Security Projects
ARinteg has been awarded Golden Partner status by Ideco following successful joint projects in network security. The integrator supplies and implements the Ideco NGFW Novum next-generation firewall for perimeter protection and secure remote access. Collaboration also covers customer migrations from foreign NGFW solutions to the Russian vendor’s product. Commercial Director Dmitry Slobodenyuk stated the new status will allow ARinteg to deliver fuller support across all implementation stages. Ideco’s Partner Relations Head Sergey Markin highlighted ARinteg’s technical expertise in large-scale deployments. The partnership supports import substitution and hybrid infrastructure requirements.
Zero Trust in Practice: Avoiding YAML Pitfalls with Kubernetes NetworkPolicy and Istio
A detailed case study demonstrates how a single misplaced hyphen in a Kubernetes NetworkPolicy YAML file can unintentionally grant cluster-wide access instead of restricting it to a single client Pod. The example uses a shop namespace API connecting to an orders service in the backend namespace over TCP/8080, showing the correct use of namespaceSelector and podSelector together within the same from element. Tests on K3s with four vCPU and 4 GB RAM confirmed that only the intended client succeeds while others receive Connection refused. The implementation then extends to Istio with PeerAuthentication in STRICT mode and an AuthorizationPolicy limiting requests to GET /orders/* from the orders-api ServiceAccount. Additional checks cover RBAC permissions for creating Pods with specific ServiceAccounts and the need to verify DNS routes and existing allow-all policies. The article stresses maintaining an explicit list of required connections, testing both success and denial cases, and preserving rollback manifests before applying changes in production.