Ideco has released Ideco NGFW Novum 24 — the third major release of the product line in 2026. The practical change is not just in throughput: the firewall can now provide tools to AI agents, while authorization for large networks and web application publishing have also received dedicated improvements.

The most notable new feature is an MCP server, through which an agent can connect to the NGFW using the Model Context Protocol and call available operations. For an engineer, this means being able to ask an agent to collect the necessary data from logs and policy tables instead of manually copying it into a chat. But the mere arrival of MCP does not make every kind of automated management safe.

MCP gives an agent tools, not magical access

MCP describes tools so that a client can get their names, purposes, and parameter schemas without separately parsing a REST API. In the developers’ vision, an agent will be able to gather context, compare it with a hypothesis about a problem, suggest a change, and check the result after it has been approved. Exactly which steps are available depends on the set of MCP server operations and the capabilities of the particular agent.

For ordinary integration, the REST API remains in place; its description in Novum 24 has been converted to the OpenAPI format. So the new interface does not require abandoning existing automation workflows. MCP adds another way to give an agent the available functions and their parameters; it does not replace the familiar API.

The critical part here is access control. Ideco recommends starting with diagnostics and data reading, restricting the agent’s permissions, and making policy changes only after explicit approval from the responsible specialist. Logging of tool use is enabled by default; the MCP specification also provides for rejecting calls and confirming sensitive operations.

This is an important distinction between “the agent can see a tool” and “the agent can change the network policy on its own.” Access to the NGFW really can eliminate manual copying of diagnostic data, but the boundaries of automation are set by permissions and the approval process. Otherwise, the new interface will merely move an old mistake from the console into an agent workflow.

Authorization: aiming for tens of thousands of devices

The release’s second major focus is speeding up authorization. In Ideco, it links network traffic to a specific user or group so that rules and restrictions can be applied; one account can have multiple sessions. At large sites, average performance is not the only thing that matters: peak loads after connectivity is restored, at the start of the workday, or after scheduled maintenance matter too.

Novum 24 has optimized session creation and Active Directory operations. According to the company, session creation under a large number of connections is now an order of magnitude faster and requires less CPU time. The NGFW also retrieves information about users and security groups from AD faster and reads the domain controller security log; a noticeable improvement is claimed, in particular, for authorization through this log.

The company gives an example of scale: restoring 300 000 sessions in 40 seconds requires an average rate of 7 500 sessions per second. According to Ideco, version 24 sustained that rate during tests on test benches. This is not a universal guarantee for every installation: the NGFW and, if Active Directory is used, the domain controller must be able to handle the load.

A license is no longer required for integration with Active Directory, ALD Pro, and FreeIPA. AD users can now be searched and filtered by domain, security group, LDAP filter, or login. These are useful changes for administrators of large directories, although by themselves they do not remove the need to check the configuration and resources at a particular site.

Reverse proxy and WAF for applications at the perimeter

The third group of changes concerns publishing web applications through a reverse proxy and protecting them with a WAF. In Novum 24, you can set a separate domain for the Host header and, for HTTPS, a Server Name Indication value. This helps when the application’s external name differs from the name expected by the internal server.

Session affinity has also been added: requests from the same client IP address are routed to the same web server. This mode is needed for applications that store a user session in the memory of a specific node. Another setting allows non-standard HTTP headers to be passed through, including ones with underscores, dots, or non-ASCII characters in the name; the example from the source is X_Auth_Token.

The reverse proxy can also be used to route requests to external resources: Ideco’s material gives the Claude and ChatGPT APIs as examples. Internal applications send requests to an address at the perimeter, and the NGFW supplies the required Host and SNI values and routes the requests as configured. With this setup, requests to external LLMs pass through a single controlled point, but describing the capability does not replace configuring access policies.

In version 24, WAF profiles can be assigned when publishing the NGFW web interface, personal account, and webmail. Previously, only DoS protection was available for these services. WAF signatures can be used together with allow and deny lists of IP addresses and GeoIP restrictions; access to the management interface still needs to be restricted separately.

The material also mentions that the previous minor release, 23.4, introduced WAF rules enabled by default against PHP2Shell vulnerabilities CVE-2026-109618 and CVE-2026-109619. Such rules can buy time to update an application, but they do not replace the update. For support teams, this is a fundamental difference: compensating protection is not a fix for vulnerable code.

Resources, metrics, and release cadence

Other changes include managing the allocation of logical cores for VCE virtual contexts with NUMA nodes taken into account. In a high-performance context, cores can be allocated separately between the Control Plane and Data Plane. Graphs for swap, disks, and network errors have also been added, along with SNMP metrics for cluster and VCE status — data that helps you monitor resources instead of just guessing based on overall load.

According to Ideco, from the beginning of 2026 through 11 November, 22 Novum releases came out: three major and 19 minor ones. Customers can stay on a supported major branch or move to a new one. Version 24 was developed over 2,5 months; the company’s internal statistics for that period record 423,5 billion tokens and 2 030 075 requests to local and cloud models.

These figures describe the use of AI in the development process, not NGFW performance or release quality. The practical criteria for deployment remain down to earth: check the MCP integration’s permissions, approval of changes, hardware capacity for the required session rate, and application compatibility with the proxy settings. That is where you find out whether a new feature makes the work easier or just adds another item to the configuration.