QuWAN Orchestrator 2.9 | 출시 정보
여기에서 모든 QNAP 운영체제 출시 정보를 확인할 수 있습니다
QuWAN Orchestrator 2.9
2026-02-26
QuWAN 2.9 introduces important new features to enable NAS integration and enhance security policy management. You can now join a QNAP NAS to your QuWAN environment via QuWAN Express, establish encrypted connections between NAS devices, and apply firewall rules and whitelists more effectively.
QuWAN Orchestrator now supports QuWAN Express, enabling QNAP NAS to join the QuWAN environment directly via QVPN Service. This allows for high-efficiency interconnection and data access across multi-site devices. With this update, users can establish encrypted IPSec VPN tunnels without the need for additional physical routers or vRouter deployment, which significantly lowers the barriers and hardware costs for cross-site data backup and transmission.
To address connectivity challenges where NAS devices are behind firewalls or lack public IPs, this update introduces Super Node, a cloud relay service. This technology allows users to quickly establish encrypted connections between NAS devices at different locations, even in environments without QNAP physical routers or an existing QuWAN architecture.
The service supports up to 3 NAS units per organization for point-to-point data transmission, making it ideal for regional data exchange and off-site backup. Each organization receives 15 GB of free monthly traffic, while flexible subscription plans ranging from 200 GB to 2 TB are available on the QNAP Software Store to meet expanding needs.
To improve management flexibility, QuWAN Orchestrator has enhanced its Intrusion Prevention System (IPS) configuration. It now supports applying firewall rules and whitelists at the Segment level, allowing administrators to rapidly deploy consistent security policies to all devices within a specific segment.
This update also permits batch-adding to whitelists based on Signature ID or Threat Severity, such as Critical or High, which significantly boosts administrative efficiency. Furthermore, the system rule priority is structured so that Custom device-level rules take precedence over Segment rules, ensuring a balance between centralized management and individual device flexibility.
