6. Skip to content

6. Features Overview

Each feature’s major use cases and important additional information are provided on separate pages in this section. Here is a brief overview that may be useful in determining whether ChiefNET meets your organization’s needs.

6.1 ChiefNET Centralized Network Orchestrator and Monitoring

The entire ChiefNET solution is managed through the Web user interface of the ChiefNET Network Orchestrator, which is accessible to all customers. It is used to manage all the features of the ChiefNET solution, including ChiefNET branch devices (configuration, monitoring, servicing, troubleshooting) and networks.

There is no direct access to the ChiefNET edge devices installed at any location, which prevents unnecessary and unauthorized access to the devices.

All features are implemented and accessible on the WebUI. To manage a ChiefNET device, access the WebUI, or receive alerts, contact your organization’s system administrator. One or more people in your organization must have 'customer administrator' privileges. They can set up an account for you with either 'administrator' or 'user' privileges. Try to keep all users at the 'user' level unless absolutely necessary. Your organization can have multiple emails with administrator privileges. Ensure that more than one administrator is designated so that if one contact becomes unavailable, there is a backup.

6.2 ChiefNET Monitoring and Analytics System

All ChiefNET data is monitored through an advanced timescale database system used by our partners to provide customer support and managed services.

  • A repository of all status and statistics of network devices
  • Graphing, querying, and filtering of data for interactive analytics
  • Report generation
  • Configurable retention period

6.3 Secure Cloud WAN

The primary feature of ChiefNET is its cloud WAN, to which all branch and HQ devices are connected. It functions as a hub-and-spoke data network. All data between branches is fully encrypted and authenticated, with each device having its own identity and dedicated certificate for data transfer.

SD-WAN tunnels can also be created directly between branches.

6.4 Local Internet Breakout

ChiefNET’s Local Internet Breakout feature optimizes network performance by routing critical traffic (e.g., CCTV and enterprise databases) through SD-WAN tunnels while sending cloud-based traffic, like Microsoft Office 365, directly to the internet. This approach reduces latency, conserves SD-WAN bandwidth, and enhances security by isolating malicious traffic from the enterprise network. Cloud-bound traffic can bypass the HQ, streamlining data flow and improving efficiency.

6.5 WAN Network Monitoring

All WAN ports are continuously monitored for packet loss, round-trip delay/latency, and jitter. Monitoring is used for the following purposes: - Automatic switchover of internet traffic - Configurable thresholds for determining when to switchover and switchback - Continual monitoring and repositioning Application traffic over the best available WAN that meets the Application's QoS - Application-Aware QoS

6.6 WAN Failover and WAN Optimal ISP Selection

WAN failover and optimal ISP selection is automatic. There is a default policy in place that selects the ISP based on the packet loss values.

Each application may be configured with its set of desired network quality parameters. ChiefNET matches the application with the best available WAN port and ensures that the failover policies apply automatically.

6.7 WAN Load Balancing

If there are multiple ISPs between two locations or between a site and Local Internet Access, load-balancing may be configured using the traffic engineering feature. In addition, we also recommend that the certain traffic be discarded on those ISPs with expensive links by using the "Sensitive Traffic Exclusive Forwarding' feature.

6.8 ISP SLA Monitoring and Report

Customers can monitor their ISP network quality through a report generated by ChiefNET's WAN Network Monitoring system.

This information may be used to reconcile the SLA agreement between the customer and their ISP. It is important to note that this report clearly splits the network downtime between - chiefNET downtime (e.g. ChiefNET device failure) - ISP network downtime (including the nexthop systems that may be under customer's management outside of ChiefNET control)

6.9 Enterprise Network Security and Network Firewall

As mentioned above ChiefNET is a Network Firewall. It does not monitor or manage the content of the packets. However, it accomplishes almost all of the enterprise security needs through the following features

  • Exclusive forwarding of secure traffic and discarding over specific ISP
  • Advanced and global databases of malicious DNS domains that doubles as URL filtering
  • Advanced application-level QoS to mitigate the impacts of DoS attacks if any
  • No open ports on the WAN ports. All connections are initiated only by ChiefNET.
  • All traffic is secured with AES-256 for confidentiality and authentication
  • All management/monitoring/troubleshooting is secured with TLS/HTTPS with AES-256.
  • Each branch device has its own dedicated certificate based identity for use with enterprise SDWAN tunnels.

6.10 Application-Aware Firewall, QoS and WAN Failover Policy

Through the use of Traffic Engineering features, Applications and Application-Grouping may be configured so that - unwanted applicaiton traffic may be discarded. - apply a specific QoS profile (minimum bw, maximum bw, real-time latency) - apply a switchover policy on the WAN - configure unique thresholds for WAN Quality (packet loss, RTT, jitter) for choice on the best available ISP that meets the needs of the application - load-balancing over multiple WAN ports simultaneously

6.11 Policy Based Forwarding

This is a feature by which traffic from certain systems, LAN ports, subnets or a specific traffic be forwarded over a specific ISP. This may be configured with ChiefNET's advanced traffic engineering feature.

  • Configure the criteria of the traffic (a port, a subnet, an application, a specific system) and configure the ISP to be used for transit,
  • optionally also configure a desired QoS, load-balancing, failover policies

6.12 High Availability

All ChiefNET components (CPE, backend services) support redundancy and high availability.

In addition to the HA/redundancy features, ChiefNET increases the overall high availability of customer connectivity, by supporting the following features - WAN interface/ISP network monitoring for failures, QoS, and SLA - Automatic WAN failover - SDWAN Tunnel monitoring and failover of the enterprise network through the best available ISP - Multiple simultaneous tunnels, including cloud tunnels, and on-premises tunnels - Redundant installation of the Orchestrator - Autonomous operation of each branch network - Advanced traffic steering rules to facililate Application Traffic Load-balancing and failover

6.13 ChiefNET Network Firewall vs Content Firewall

The goal of ChiefNET is to meet customer use cases related to networking and security. At present, ChiefNET focuses on meeting the secure networking needs of modern organizations.

ChiefNET is a NETWORK FIREWALL. ChiefNET is not a CONTENT-firewall product. The following are examples of firewall features that are not supported by ChiefNET: - SASE (Secure Access Service Edge) - Zero Trust Networking, Web Proxy - Deep Packet Inspection, Malware/Ransomware Blocking - Zero Trust Network Access - Antivirus, URL Filtering

ChiefNET has successfully interoperated with Palo Alto Networks' Prisma Cloud product, which supports all of the above features. Customers may acquire Prisma Cloud or similar products from other firewall vendors to complement ChiefNET.

Many of our customers use ChiefNET for all their networking needs and deploy a firewall only at the corporate HQ. ChiefNET's Local Internet Breakout provides substantial security, sufficient to meet the needs of branch networks.