Innostage Completes Functional Testing of PT NGFW 1.10.3 Across 156 Criteria

Innostage has published the second part of its evaluation of PT NGFW version 1.10.3, focusing on functional capabilities rather than raw performance. The testing covered 156 individual checks grouped into categories such as basic technical features, firewalling, IDS/IPS, web filtering, malware protection, logging, routing, deployment, cryptographic controls and access management. Out of the total, 136 checks passed fully, seven passed with remarks, and 13 did not meet the predefined criteria. Key confirmed functions include high-availability clustering, centralized management via PT-MNGT, AD-based rule application, Site-to-Site VPN, TLS inspection, and Syslog integration with external security systems. Several advanced scenarios, including custom block pages, application risk classification, and centralized software distribution, were not confirmed under the test conditions. The report provides detailed protocol notes that help organizations map product capabilities against their specific infrastructure and regulatory requirements.

HabrTranslated from Russian

Read at source

Innostage has released the second installment of its evaluation of PT NGFW 1.10.3, shifting focus from performance metrics to a comprehensive functional assessment. The first part measured TCP connection rates, concurrent sessions and throughput under EMIX profiles with various feature combinations enabled. The second part examined whether the product can actually deliver the operational capabilities required in real-world deployments.

The testing protocol contained 156 individual checks divided into ten thematic groups: general technical requirements and resilience, firewalling functions, IDS/IPS mechanisms, web filtering and application identification, malware protection, logging and management, routing, deployment options, cryptographic protection and access control. Each check was evaluated against explicitly documented pass/fail criteria.

Overall results showed 136 checks marked “Test passed”, seven marked “Test passed with remarks” and 13 marked “Test not passed”. The majority of core functions were confirmed, yet several advanced or edge-case requirements revealed limitations or incomplete implementations that organizations must consider during procurement and design.

Core Technical Capabilities and Firewalling

Confirmed capabilities include creation of PT NGFW and PT-MNGT high-availability clusters, centralized management of multiple gateways, continued manageability under high load, router-mode operation and vWire transparent bridging. Integration via Syslog to third-party SIEM and SOAR platforms was also verified without any hard limit on the number of target servers.

Firewall policy checks passed for multi-layer filtering (including Layer 7), use of Active Directory identities in security rules, time-based restrictions and NAT. Site-to-Site VPN tunnels and rule hit counters were likewise confirmed.

IDS/IPS, Web Filtering and Application Control

Signature-based and anomaly-based intrusion detection and prevention modes, profile customization and signature management all met the test criteria. Web-filtering tests validated URL categorization (approximately 190 million addresses), custom block lists, HTTPS decryption via TLS proxy and application identification covering more than 3 500 applications.

Two requirements did not pass: display of a customizable block page and classification of applications by risk level and compliance posture. The absence of these specific features does not negate the positive results for basic URL and application filtering.

Management, Auditing and Automation

The management plane tests confirmed deployment of PT-MNGT on physical or virtual servers, policy synchronization, administrator audit logging, configuration backup/restore, object and rule import/export via API and NBI integration. Predefined roles including read-only were available, and separation of duties between administration, protection management and data-handling roles was demonstrated.

Checks that finished with remarks included policy change history presentation, multi-domain management and concurrent policy editing workflows. Centralized firmware distribution to gateways did not meet the acceptance criteria.

The full protocol and accompanying notes are intended to help security architects map confirmed capabilities against the concrete requirements of their networks, regulatory obligations and operational scenarios.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Other

Mail.ru Reduces Lifetime 1TB Cloud Storage Promo to Standard 8GB Quota for Select Users
Kimi K3 Open Model Surpasses Closed AI Leaders with Million-Token Context and 896 Experts
MITRE ATT&CK in Detective Settings: Avito Launches Cyberdetective Game for Security Awareness Training