Providing Out-of-Band Connectivity to Mission-Critical IT Resources

A Guide to SD-WAN Deployment Models

SD-WAN

Software-defined wide area networking, or SD-WAN, uses software abstraction to create a virtual overlay network that sits on top of the underlying WAN infrastructure. This gives organizations greater control over distributed network architectures and enables a high degree of automation. SD-WAN can be deployed in a hub-and-spoke model or a variety of mesh topologies depending on the organization’s requirements and capabilities.

In this guide are the most common SD-WAN deployment models with diagrams, pros and cons, and best practices to help organizations choose the right topology.

Hub-and-spoke SD-WAN deployment models

In the hub-and-spoke model, large data centers serve as centralized hubs that all SD-WAN traffic must flow through. The spokes are the campuses, branch offices, and edge sites that connect to each hub in order to access the enterprise WAN.

Hub & Spoke

The hub-and-spoke SD-WAN deployment model can be executed in a couple of different ways:

Spoke-to-hub only

In this SD-WAN deployment model, the spokes for a particular hub are unable to communicate with each other, they can only interact with the central hub. The networking logic for this deployment model is relatively simple compared to the others. It’s also useful when spoke sites need to be isolated from each other for security, privacy, or regulatory reasons.

Spoke-to-spoke via hub

In this deployment, spoke sites can communicate with each other, but all of their traffic must pass through the central hub first. Again, this makes SD-WAN networking logic a little simpler than allowing direct communication between sites. It also allows spoke traffic to pass through a centralized firewall first so that traffic can be inspected and security policies can be applied without needing to deploy firewall appliances at each spoke site.

Hub-and-spoke pros and cons

The hub-and-spoke approach is relatively easy to deploy and manage because all SD-WAN traffic must flow through a limited number of hub data centers. There’s no need to configure, secure, and load-balance network traffic between the numerous spoke sites that comprise an enterprise network, so organizations that are adopting SD-WAN for the first time tend to favor this approach.

However, since all spoke traffic needs to pass through a centralized hub, this creates bottlenecks that can impact network performance for all connected sites. Centralized hubs also represent single points of failure for the spokes that rely on them for enterprise network access – if a hub goes down due to a cybersecurity breach, ISP outage, or equipment failure, then spokes will lose their ability to communicate with each other or access enterprise network resources. Plus, since all traffic and data are aggregated in centralized hubs, they present attractive targets to cybercriminals, who can easily get all the valuable data they want in a single location instead of needing to move around the network.

Hub-and-spoke best practices

If you’re considering the hub-and-spoke approach, it’s important to have a business continuity plan that accounts for hub failures. For example, you should have some sort of network failover option (such as cellular LTE) in case the ISP connection goes down. You should also be able to redirect traffic from one hub to another if the first hub gets overloaded or experiences a failure. In addition, hubs should be deployed with out-of-band (OOB) management so network admins have 24/7 management access even if the SD-WAN connection goes down.

Learn more about Out-of-band (OOB) management.

Mesh SD-WAN deployment models

In the mesh deployment model, campuses, branch offices, and edge sites have some ability to communicate with each other directly, without their traffic needing to pass through a hub first. The degree to which sites can interact with each other depends on the type of mesh topology that’s deployed.

Full mesh deployment

In a full mesh deployment, there is any-to-any communication between edge and branch sites using overlay tunnels. There are often still hub data centers to handle requests for centralized enterprise resources, but most other requests are handled by services deployed at the network edge (either at the sites themselves or in the cloud).

Mesh

Full mesh pros and cons

The full mesh topology enables faster communication between sites. It also allows organizations to deploy applications and services at the edge of the network where data is being generated and used, which is known as edge computing. There are also no single points of failure in the full mesh SD-WAN architecture, which reduces the risk of an outage and shortens the duration of outages that do occur. In addition, data and applications are distributed across many different locations, which can limit the damage caused by security breaches – instead of finding all your valuable data in a single server, cybercriminals have to jump around the network, increasing the chances they’ll be caught.

However, the full mesh topology is the most challenging to implement, manage, and optimize because there are so many moving parts involved. Each site needs a full stack of networking and security solutions because they aren’t relying on a centralized hub. Increasing the complexity of the SD-WAN architecture also increases the risk that mistakes will be made during configurations, deployments, and updates.

Partial mesh deployment

In this topology, some spokes can directly communicate with each other, and some services are deployed at the edge. However, there isn’t a full decentralization of applications and security, so some traffic still needs to pass through a hub.

Partial mesh pros and cons

Many organizations arrive at a partial mesh deployment on their journey from a hub-and-spoke deployment to a full mesh. A partial mesh topology reduces some of the load on centralized hubs and firewalls by moving certain services to the edge and allowing some direct site-to-site communications, which can improve performance. The organization can still rely on some centralized security functionality, reducing the number of security appliances or cloud-based services needed to protect the edge.

However, a partial mesh doesn’t completely address the limitations of a more centralized hub-and-spoke deployment. Hubs still represent potential bottlenecks and points of failure in the SD-WAN architecture. Plus, there’s still a lot of data centralization, meaning that storage and data processing servers in hubs will make attractive targets to hackers.

Hybrid mesh deployment

In a hybrid mesh, many hubs are deployed in a mesh topology, which means there is frequent communication and a high level of redundancy. However, branch and edge sites are still deployed as spokes, which means all their traffic goes through the hub mesh.

Hybrid Mesh

Hybrid mesh pros and cons

A hybrid mesh deployment ensures that no single hub acts as a single point of failure, enabling a high degree of redundancy and load balancing. Spoke sites can’t directly interact with each other, which reduces the complexity of the SD-WAN topology and decreases the number of security appliances to purchase and manage. Bottlenecking is also less of an issue because traffic from spokes doesn’t have to pass through a single designated hub, and can instead be distributed across multiple hubs.

However, a hybrid mesh topology is still fairly centralized, so you don’t get all the security and performance benefits of a decentralized full mesh deployment. Hubs are still valuable targets for cybercriminals, edge sites still need to send data to hubs for processing, and spokes cannot access enterprise network resources without going through the hub mesh. If that hub mesh is unavailable for any reason, spoke sites will be completely cut off.

Regional mesh

A regional mesh allows organizations to implement different deployment models for different regions. For instance, one region may have a spoke-to-spoke deployment, while another has a partial mesh. When traffic from one region needs to go to another, it must pass through a regional hub first.

Regional mesh pros and cons

The regional mesh model gives large or highly distributed organizations the flexibility to use deployments that meet the specific requirements of each region. For example, there may be a cluster of branch offices that process classified data for the defense industry, so the organization uses the spoke-to-hub-only deployment to isolate those sites from the rest of the enterprise network. In another region, the org may run a lot of edge computing for machine learning applications and need there to be fast and seamless communication between edge data centers. In that case, they might deploy a full mesh topology in that specific region.

However, this flexibility can also create a lot of management complexity. Admins need to learn, manage, and troubleshoot different configurations, network logic, and security rules for different regions. Plus, each region is subject to the downsides and limitations of whichever deployment model is used there. In addition, regional hubs often still act as potential bottlenecks and points of failure between each region and the enterprise network.

Mesh best practices

All of the best practices for the hub-and-spoke model also apply to mesh SD-WAN deployments. There are a couple of additional considerations for organizations considering a more decentralized deployment, including:

Cloud-delivered security – Mesh deployments typically require security solutions deployed at the edge, so that traffic doesn’t need to pass through a centralized firewall. However, purchasing appliances for each location is expensive and adds to the complexity of the architecture. Solutions like SSE (Security Service Edge) allow you to use your SD-WAN technology to send edge traffic through security services in the cloud. SSE takes many of the capabilities of traditional security appliances and combines them into a cloud-delivered stack, so organizations can get enterprise-level protection without needing to deploy additional hardware or route traffic through a central bottleneck.

Network automation – Manually configuring and controlling a complex mesh network increases the risk of human error. Luckily, SD-WAN’s software abstraction makes it easier to use automated scripts and playbooks to handle a lot of the tedious, repetitive tasks that are prone to mistakes such as device configurations and ACL (access control list) updates. Automation also means that work can get done faster and without putting additional pressure on overworked network teams.

Centralized orchestration – Mesh topologies have so many moving parts, and needing to manage each one of them separately makes it impossible to holistically control, optimize, and secure the deployment. Centralized orchestration gives network teams a common interface they can use to create, organize, deploy, monitor, and troubleshoot automated and manual SD-WAN workflows. That means the orchestrator should be vendor-neutral so it can dig its hooks into every device, application, and service in every SD-WAN site in your deployment.

Vendor neutrality – On that note, vendor neutrality is also a best practice because of how it simplifies and strengthens automation infrastructure. Many vendors lock you into using specific tools, applications, and devices, which makes automation pipelines more complicated and brittle — if one component breaks, the whole infrastructure goes down. Using vendor-neutral tools and orchestration platforms means you don’t have to inflate your toolkit or overcomplicate your automation pipeline, improving resiliency.

Choosing the right SD-WAN deployment model

Every SD-WAN topology comes with its own advantages and limitations, so organizations must assess their requirements and capabilities to determine which one to deploy. For example, if your team doesn’t have any SD-WAN experience, then jumping right into a full mesh deployment may not be practical. If you need your edge sites to have real-time data processing abilities (for example, in healthcare applications), then you may want to consider a less centralized mesh topology.

  Pros Cons
Hub-and-spoke
  • Easy to deploy
  • Reduced management complexity
  • Creates bottlenecks
  • Hubs are single points of failure
  • Centralized data is a target for hackers
Full mesh
  • Enables edge computing
  • No single points of failure
  • Decentralized data limits the blast radius of breaches
  • Complex implementation and management
  • Increases risk of human error
  • Requires edge or cloud-delivered security solutions
Partial mesh
  • Reduces some load on centralized hubs
  • Easier to deploy than a full mesh
  • Enables edge computing
  • Hubs can still create bottlenecks
  • Hubs are still potential points of failure
  • There is still some data centralization
Hybrid mesh
  • Enables a high degree of redundancy among hubs
  • Not as complex as a full mesh
  • Reduces bottlenecks
  • There is still some data centralization
  • There is still some bottlenecking
  • Hub mesh is still a point of failure
Regional mesh
  • Flexible and customizable
  • Addresses specific needs of individual sites and regions
  • Each regional hub is a potential point of failure
  • Variety of topologies creates a lot of management complexity
  • Subject to the downsides and limitations of all the deployment models in use

Ready to learn more about SD-WAN deployment models?

For more guidance on how to choose and implement SD-WAN deployment models, contact the experts at ZPE Systems. Contact Us

How to build a secure isolated recovery environment (SIRE)

An illustration of someone paying a ransom for their encrypted data, showing what can happen if an organization does not implement an isolated recovery environment (IRE).

Ransomware is one of the biggest cybersecurity threats to enterprises. Sophos reports that in 2024, 59% of organizations suffered a ransomware attack, and the average cost to recover (excluding ransom payment) was $2.73 million. The frequency of ransomware attacks is so high that it’s no longer a question of ‘if,’ but ‘when’ an organization will be hit. Since ransomware encrypts critical data, applications, and systems, an attack can be extremely disruptive to business. During prolonged downtime, revenue slows or stops altogether, recovery costs skyrocket, and the company’s reputation and customers’ trust are severely damaged.

To reduce ransomware recovery times, companies must shift their focus away from prevention and detection and instead invest more time and money into recovery strategies. Ransomware recovery is especially challenging because of how easily its malicious code can spread from production into backup data and systems. What’s needed, according to the experts at Gartner, is a designated, secure isolated recovery environment (SIRE) that’s fully separated from the production infrastructure.

What is a secure isolated recovery environment (SIRE)?

A recovery environment is made up of systems and network resources that are dedicated to recovering from ransomware and other cybersecurity breaches. The recovery environment is where teams work to restore data and rebuild applications before they’re pushed back to the production network.

Many organizations implement a recovery environment by creating an isolated VLAN on the enterprise network. However, if the recovery environment has any dependencies on the production network, there’s a risk that ransomware will cut off access. For example, if malware infects authentication systems, routers, or switches, then admins might lose access to the recovery VLAN. In addition, production dependencies provide a way for ransomware to jump to the recovery environment, reinfecting systems and spoiling recovery efforts.

A secure isolated recovery environment (SIRE) uses a designated network infrastructure that’s completely separate from the production environment. The SIRE uses tools like Retention Lock, role-based access control (RBAC), and out-of-band (OOB) management to ensure that admins can quickly recover critical business services without the risk of reinfection. Let’s discuss these components in greater detail, as well as how to implement them to create an IRE.

How to build a secure isolated recovery environment

The ideal SIRE is built around three concepts: survivable data, separation and isolation, and designated infrastructure.

build an isolated recovery environment

Survivable data

Ransomware earned its name because it encrypts data and systems and demands a ransom (typically in the form of cryptocurrency) to get the decryption key. However, there’s no guarantee that the attackers will provide a valid decryption key upon receiving their bounty, so it’s best to avoid the cost and risk altogether by ensuring you have clean backup data. These backups are known as survivable data – data that can’t be removed or encrypted by attackers.

To ensure your backup data is survivable, you should implement:

  • Immutability: Something is considered immutable if it can’t be changed in any way, such as immutable infrastructure. Immutable data backups can’t be modified once they’re in place, which makes it impossible for ransomware and other malware to encrypt or corrupt the files. Data immutability can be enforced with tools such as Retention Lock.
  • Encryption: For backup data to be survivable, it must be encrypted both in transit and at rest. This is sort of like fighting fire with fire – if your data is already encrypted, it will be much harder for ransomware to apply its own encryption. Plus, encrypting data in transit makes it harder for attackers to intercept and steal it as it’s moving between your production, backup, and recovery environments.
  • RBAC: Role-based access control, or RBAC, refers to policies that restrict access based on an account’s role or function (e.g., ‘administrators,’ or ‘human resources’). Ideally, only the key personnel involved in recovery operations (their role may be ‘recovery engineers,’ for example) will have access to backup systems, which limits the risk that over-privileged accounts will be compromised and used to exfiltrate data.
  • MFA: Multi-factor authentication, or MFA, forces users to prove their identity in multiple ways before they can access a system or application. For example, an admin may need to provide their username and password, plus a six-digit code sent to their authorized mobile device or email address, to prove that they are who they say they are. If an attacker steals an admin’s username and password, MFA prevents them from being able to access, steal, or encrypt backup systems.

Separation and isolation

Recovery efforts need to take place in an isolated environment so there’s no risk that malware will cross over from the production network. Newly recovered systems, applications, and data also need to be scanned and verified to ensure they’re clean before they’re reintegrated into production. The only way to achieve this is by building a completely isolated environment using a designated network infrastructure.

Designated infrastructure

The SIRE needs to be both physically and logically separated from the production network to ensure there’s a completely clean environment in which to perform system, application, and data restoration. That means the SIRE should have its own routers, switches, storage devices, compute options, and power. In addition, the SIRE needs its own out-of-band (OOB) control plane that’s accessible via a dedicated network interface (such as 4G or 5G cellular). This will ensure that admins have continuous remote access to the SIRE even if the LAN or WAN goes down due to configuration errors or other problems.

How the Nodegrid Net SR isolates and protects the management network.

Image: Deploying a SIRE is only possible through the use of a dedicated control plane, or Isolated Management Infrastructure shown here.

Teams will also need access to their security and build tools in the SIRE, so these need to be configured and ready to go before an attack occurs. Organizations also must ensure the secure isolated recovery environment has enough storage to handle all of the backup data and server rebuilds.

Additional resources for building a secure isolated recovery environment (SIRE)

A secure isolated recovery environment (SIRE) ensures that admins have a dedicated environment in which to rebuild and restore critical business services during a ransomware attack. Survivable data backups, complete isolation, and designated infrastructure are needed to maintain the integrity of recovery operations and prevent reinfection.

For more information about how to recover from ransomware using a secure isolated recovery environment, download our whitepaper, 3 Steps to Ransomware Recovery.

Implementing and using a SIRE requires Isolated Management Infrastructure. IMI provides the management foundation and is a best practice recommended by CISA, because it fully separates admin access from relying on production infrastructure. Through IMI, teams gain a host of capabilities including out-of-band management and remote access, which not only help with ransomware recovery, but also for break/fix troubleshooting, device monitoring, and outage recovery. The ZPE Systems team created the blueprint that organizations can use to implement this crucial IMI foundation.

To get the blueprint for building Isolated Management Infrastructure, download the Network Automation Blueprint.

Want to see the Secure Isolated Recovery Environment in action?

Our engineers are ready to show you what it takes to recover from ransomware. Click the button to get in touch, and we’ll walk you through IMI, out-of-band, and the Secure Isolated Recovery Environment.

Contact Us

Simplifying Retail Network Management

Retail network management is visualized with interconnecting icons of networked retail services displayed in front of a retail warehouse

Fast and reliable networks are critical to the success of retail operations. Without network access, stores can’t process payments, handle customer data, or update inventory, which makes outages highly disruptive. According to a recent study, downtime could cost over $300,000 per hour in lost business, which is why it’s crucial that admins have the necessary tools to effectively monitor, manage, and optimize retail networks. This blog discusses some of the specific challenges involved in retail network management and how the right edge gateway solution can help overcome these difficulties.

Retail network management challenges

Managing a retail network comes with unique challenges, especially as the size and geographical distribution of the organization grows. Examples of these challenges include:

  1. Extending fast, reliable connectivity to the entire store for payment processing machines, inventory scanners, and other crucial devices. This is especially challenging in big box stores and other locations with large footprints as well as service-based chains with mechanics’ bays, drive-thrus, and other outdoor or semi-outdoor devices.
    .
  2. Maintaining optimal environmental conditions for networking equipment that’s often installed in closets, storage rooms, warehouses, and other out-of-the-way locations. The priority is typically to keep these devices hidden from customers, so they’re kept in areas that may not be climate controlled and may not have staff physically checking them every day. This increases the risk of environmental issues (like heat and humidity) causing a device failure and means no one is likely to notice the issue until it’s too late.
    .
  3. Remotely troubleshooting and recovering from issues without any on-site technicians. If the ISP connection, WAN, or LAN go down, there’s often no way to remotely access on-site equipment to diagnose and fix the problem. That means network outages require truck rolls to solve, with stores losing money waiting for technicians to travel on-site.
    .
  4. Efficiently monitoring and managing a distributed retail network architecture made up of many different network solutions and platforms. The lack of centralized management increases the risk of human error and makes it difficult to preemptively address potential problems or optimize the speed and performance of the network.

Retail network management teams need a robust solution that addresses these particular challenges. For example, they need small and powerful network devices that use centralized management to reduce management complexity. They also need a way to monitor environmental conditions and recover from outages without having to be on-site.

Simplifying retail network management

Now, let’s discuss how a robust branch gateway solution can help organizations address these challenges.

Compact, all-in-one networking

The layout of a retail store is carefully planned to ensure an optimal experience for customers, which means networking devices need to be as unobtrusive as possible. The ideal branch gateway for retail is compact and combines multiple networking functions, reducing the number of devices that need to be installed. Retail notoriously operates on a small profit margin, so the branch gateway also needs to be affordable without sacrificing performance.

Environmental monitoring

Environmental monitoring sensors collect data on conditions like temperature, humidity, and air quality in the location where networking equipment is installed. These sensors typically connect to the retail branch gateway via USB and report back to the management platform, giving admins the ability to remotely monitor the environment. This is crucial when most retail networks are managed by admins in a centralized office which may be hundreds or thousands of miles away from the stores themselves. Environmental monitoring allows them to identify and resolve potential problems before they cause device failures and outages. For example, if environmental sensors detect high temperatures, admins can get on-site personnel to turn up the air conditioning or call in an HVAC repair before devices overheat and bring down the network.

Out-of-band (OOB) management

Out-of-band (OOB) management uses redundant network interfaces (often cellular) to provide an alternative path to remote infrastructure. A branch gateway with OOB allows admins to remotely connect to devices in the store without relying on an IP address from the LAN, which means they’ll always have access even if the production network goes down. Without OOB management, the retail location goes offline for hours or even days waiting for a technician to arrive on-site, diagnose, and repair the issue. With OOB, admins can remotely access the infrastructure to restore services, often so fast that customers don’t even notice. That means they can remotely recover from more outages without truck rolls, saving time and money.

Vendor-neutral orchestration

A vendor-neutral branch gateway can interface with all the other devices in a retail network infrastructure, even if they’re from a different vendor’s ecosystem. This gives admins a single platform from which to monitor and manage every device in the store. Even better is when all of the branch gateways in the entire retail network architecture hook into a single, centralized, cloud-based orchestration platform. Admins can then monitor, control, and optimize network infrastructure for all the retail locations from one place for ultimate efficiency.

In addition, a vendor-neutral retail network management platform enables the use of third-party automation solutions. Automation reduces the risk of human error and makes it easier for teams to effectively manage and optimize even complex retail network architectures.

Retail network management with Nodegrid

Compact, all-in-one branch gateways like Nodegrid use environmental monitoring, OOB management, and vendor-neutral platforms to simplify retail network management. The Nodegrid Mini SR, for example, is an inexpensive retail branch gateway that’s roughly the size of an iPhone, so you can easily deploy them anywhere in your store without disrupting the customer experience. Despite its small size and low price point, the MSR still delivers Gen 3 OOB management capabilities while supporting Nodegrid environmental monitoring sensors and third-party automation. The Nodegrid platform is also completely vendor-neutral, giving retail network admins a single pane of glass from which to monitor, orchestrate, and optimize the entire distributed network architecture.

Ready to learn more about Nodegrid?

To learn more about about simplifying retail network management with Nodegrid, click here to download the Mini SR datasheet, or contact ZPE Systems today.

Contact Us

The Importance of Remote Site Monitoring for Network Resilience

remote site monitoring

Enterprise networks are huge and complex, with infrastructure hosted in many different facilities across a wide geographic area. Though most network infrastructure isn’t housed in the same location as the core business, it’s still vital to the business’s continual operation. Remote site monitoring gives network admins a virtual presence in remote sites like data centers, manufacturing facilities, electrical substations, water treatment plants, and oil pipelines.

Most organizations already have some form of remote infrastructure monitoring, but traditional solutions come with major limitations that make it difficult for networking teams to maintain 24/7 uptime. In this blog, we’ll discuss the importance of remote site monitoring, analyze the limitations of traditional solutions, and explain how the ideal remote monitoring platform improves network resilience.

The importance of remote site monitoring

Many organizations have reduced their IT staff due to the economic recession, leaving networking and infrastructure teams stretched too thin. When there aren’t enough eyes on remote infrastructure, enterprise networks are more vulnerable to breaches, hardware failures, and other major causes of network outages. With the average cost of downtime rising above $100k in 2022, and cyberattacks causing major disruptions to oil pipelines in recent years, this is a problem that’s too expensive to ignore.

The limitations of traditional remote site monitoring solutions

Many organizations rely on remote site monitoring solutions that are fragmented and vendor-specific. Admins have to log in to one platform to view monitoring data for a remote site’s wireless access points, for example, and a different platform to monitor IoT devices in the warehouse. These complex and repetitive tasks can lead to fatigue and negligence, especially for overworked and understaffed networking teams. At an even higher level, this makes it difficult to see the relationships between different systems and solutions or get a complete picture of the overall health of the enterprise network.

Another limitation of traditional solutions is that they’re often affected by the same issues as the infrastructure they’re monitoring. For example, if the LAN goes down in a remote office and the on-premises security appliance can’t get an IP address, then admins won’t be able to remotely access that appliance to view the monitoring logs. This can significantly delay or even prevent remote diagnostic and recovery efforts, leading to expensive truck rolls.

The problem gets even worse if the remote site is inaccessible due to natural disasters, conflicts, or other external factors. Network teams need a way to get eyes on the problem, diagnose the root cause, and deploy fixes without physically seeing or touching the affected infrastructure.

The ideal remote site monitoring solution

To avoid these limitations and ensure network resilience, the ideal remote site monitoring solution should consider the following factors:

Vendor-neutral and centralized

A vendor-neutral monitoring platform can collect and analyze logs from every component of your infrastructure. This gives admins complete coverage, so nothing falls between the cracks.

Another benefit of vendor neutrality is that it enables unified, centralized monitoring. That means networking teams only need to log in to a single portal to observe the entire distributed enterprise architecture.

Out-of-band

Deploying remote site monitoring on an out-of-band (OOB) network means that it won’t rely on production LAN, WAN, or ISP infrastructure. This ensures that admins always have access to vital monitoring data even during an outage, making it easier to remotely diagnose the issue.

Plus, using an OOB management solution for monitoring improves network resilience even further by giving admins a direct connection to remote infrastructure that doesn’t require an IP address. That means they can still access and fix remote devices during an outage.

Automated

Automated monitoring solutions help to ensure that admins are quickly notified of potential issues and that possible remediation steps are taken even if nobody is available right away. Some solutions can, for example, automatically refresh DHCP on a device that lost its IP address or re-direct traffic to a secondary resource when the primary server stops responding.

Automated monitoring solutions help to reduce the workload on understaffed networking teams without sacrificing resilience.

Building network resilience with ZPE Systems

A centralized, vendor-neutral remote site monitoring solution with out-of-band management and automation support helps to ensure network resilience even when IT staff is reduced or remote sites become inaccessible. The Network Automation Blueprint from ZPE Systems provides a reference architecture for achieving network resilience with OOB, automation, monitoring, and more.

Ready to learn more?

To learn more about remote site monitoring and network resilience, contact ZPE Systems today.

Contact Us

White Box Networking: Making the Switch

A close up of fingers plugging an Ethernet cable into a white box networking switch
Vendor lock-in is risky to corporate revenue and security. Enterprise technology ends up on rails, so to speak. Organizations lose the ability to choose the best features, pricing, and functionality for their use cases and instead must go along with their vendor’s roadmap. This is leading executives to take a hard look at their existing networking tech stacks so they can break out of their closed ecosystems. White box networking solutions, which are designed around completely open and customizable hardware components, offer an escape from vendor lock-in. In this blog, we’ll discuss how white box networking works, what the benefits and challenges are, and how to build the best solution.

Table of Contents

  1. White box networking explained
  2. The benefits of white box networking
  3. The problem with white box networking
  4. The solution: White box networking with ZPE Systems

To see an example of white box networking in action, request a

free Nodegrid demo

White box networking explained

White box networking involves the use of hardware – like switches and routers – that are built with commodity parts and can run any software. These solutions are highly customizable, enabling organizations to mix and match parts from different suppliers to get exactly the features they need, like port configurations, storage capacity, and computational power. In addition, white box devices can run operating systems and software that’s been custom-made or heavily modified, allowing even greater flexibility.

The benefits of white box networking
.

→ Cost savings: Network Operating Systems (NOS) are often the most expensive component of a networking solution, involving recurring licensing fees, support contracts, and periodic update costs. Plus, the vendor may decide to overhaul or replace their software platform, requiring expensive network hardware replacements and licensing upsells to maintain support. White box networking decouples the hardware and software, giving organizations complete control over their NOS and allowing the use of open source or in-house operating systems. By eliminating their reliance on commercial NOS, companies can reduce both their upfront software costs and their recurring licensing fees.

→ Hardware and software freedom: Even if an off-the-shelf networking solution comes with the necessary features and functionality right now, that’s no guarantee that the feature roadmap will always align with an enterprise’s goals and future growth. A white box solution can be changed at any time by installing new software or replacing hardware components, so it can grow and evolve with an organization. This also means that companies can take advantage of new and emerging technologies like SD-WAN or AIOps as quickly as they want without needing to completely replace the underlying infrastructure – they can simply add the required hardware and software to their existing white box solutions.

→ Easy management and interoperability: The biggest benefit of white box networking is that it can be managed by any platform and integrated with any third-party solutions. This makes it easier for an organization to create a fully unified environment with centralized orchestration, end-to-end network automation, and complete visibility. Network teams get holistic control over the entire white box infrastructure from a single pane of glass, using their preferred automation scripts and orchestration tools, which ensures greater performance, reliability, and efficiency.
.

The problem with white box networking

Though white box networking has many advantages in theory, a lot of companies find it hard to achieve these benefits in practice. For one thing, many white box vendors focus simply on the hardware and don’t provide a default NOS. That means organizations need to spend additional time purchasing, customizing, or writing their own NOS as well as deploying that NOS to all new white box devices.

In addition, white box hardware is often sold in bulk and can become prohibitively expensive if bought in smaller quantities. An organization might end up buying a lot of extra parts they don’t need just to avoid outrageous shipping fees, and then they’re left with the hassle of storing or reselling that hardware.

White box networking also requires a lot of extra work to configure, deploy, and manage compared to a commercial off-the-shelf (COTS) solution. For many companies, the complexity of enterprise networks and the tech talent shortage make white box networking too much of a headache. Plus, white box manufacturers typically don’t provide ongoing support in the form of NOS updates and security patches, which means the enterprise must take on this responsibility themselves.

Plus, white box devices can also increase the security attack surface of the enterprise network. A poorly configured and unpatched NOS is a tempting target for cybercriminals, who can use a compromised white box device to access sensitive network resources.

The solution: White box networking with ZPE Systems

To use white box networking effectively while avoiding these challenges, you need a complete solution, not just disparate parts to assemble on your own. That solution should combine the open ecosystem approach of white box hardware, the centralized management and security patch advantages of point solutions, and pre-validated applications that don’t require a professional coder to deploy.

For example, the Nodegrid platform from ZPE Systems turns white box networking into a complete enterprise solution. Nodegrid devices are highly customizable, inexpensive, and arrive fully assembled. These devices come pre-installed with the Nodegrid OS, which is built on an x86-64 bit Linux kernel to ensure easy setup and interoperability. ZPE Systems can even manage Nodegrid OS updates and security patches for you, helping to reduce your attack surface and close the tech talent gap. Plus, you can directly host or integrate your choice of networking applications (including Docker containers and SASE solutions) for greater functionality, security, and ease of use.

The Nodegrid solution addresses every major challenge of white box networking so you get complete vendor freedom and simplified management in a single, affordable platform.

Ready to learn more?

To learn more about white box networking with Nodegrid,contact ZPE Systems today. Contact Us

Why You Need an Out-of-Band Cybersecurity Platform

out of band cyber security
As enterprise networks continue to grow in size and complexity, many organizations struggle to defend their expanding attack surface. The cost of failure also continues to grow – according to IBM’s 2022 Cost of a Data Breach report, the average cost of a successful ransomware attack reached $4.54 million. Koroush Saraf, VP of Product Management at ZPE Systems, identified the top five cybersecurity gaps that must be closed to achieve holistic cybersecurity, which include:

  • Unnecessary exposure of management ports
  • Credential theft
  • Unpatched infrastructure
  • Inability to deploy the right security tools
  • Human error

Closing these gaps requires a three-pronged approach – out-of-band infrastructure, an open platform from which to deploy and manage security tools, and end-to-end automation (aka, hyperautomation). In this blog, we’ll explain how an out-of-band cybersecurity platform combines these three key features into a single, holistic network security solution. Want to see an out-of-band cybersecurity platform in action? Request a free demo of the Nodegrid solution.

Why you need an out-of-band cybersecurity platform

An out-of-band (OOB) cybersecurity platform provides a single, unified interface from which to:

  • View and manage network infrastructure
  • Deploy and control all of the various security policies and applications needed to protect that infrastructure, and
  • Orchestrate network, infrastructure, and security automation.

This platform resides and operates on an out-of-band network running parallel to the production network, which ensures 24/7 availability even if there’s a LAN failure or ISP outage. All network, infrastructure, and security management occur OOB, which prevents resource-intensive orchestration workflows from negatively impacting performance. This vendor-neutral, automation-friendly, out-of-band approach to cybersecurity helps you in several areas.

Reduce your attack surface

The management ports on devices like servers and switches are frequently targeted by cybercriminals because they can be used to gain access to valuable data and resources on the production network. With an out-of-band cybersecurity platform, all infrastructure and network management occurs on the OOB network, which means you no longer need to expose management ports on the production network. Isolating management and orchestration workflows to the OOB network helps reduce the attack surface by making it much more difficult for attackers to find and access those open management ports. Vendor-neutral OOB cybersecurity platforms can also help companies reduce the number of individual devices and solutions on their network, which decreases the attack surface even more. An open OOB serial console like the Nodegrid Serial Console Plus (NSCP) can host other vendors’ applications and solutions and seamlessly integrate them into the cybersecurity platform, so there are fewer devices to patch and defend, and fewer vectors through which cybercriminals can attack.

Understand your attack surface

A centralized, vendor-neutral cybersecurity platform is able to dig its hooks into every component of an enterprise network, providing a complete overview of the entire architecture. With this holistic view, security analysts gain a better understanding of the attack surface and what’s needed to protect each vulnerability. For example, a cybersecurity platform can provide information about software versioning to help with security patch management or help identify which ports are open in various applications and why. Armed with this knowledge, an organization can then deploy granular policies, tools, and controls that are custom-tailored to provide the best defense.

Mitigate human error

Even the best network engineer, working in the ideal environment, will occasionally make mistakes. For example, a recent FAA outage that delayed thousands of flights was caused by a contractor mistakenly deleting some files. And unfortunately, the combination of a tech industry recession and a tech talent gap has meant that many IT teams are overworked and understaffed – far from an ideal situation. Human error is a leading cause of successful breaches, so network automation can reduce human error by letting scripts and playbooks handle many of the tedious and repetitive workflows involved in network management. An out-of-band cybersecurity platform can host or integrate with all the leading automation solutions and scripting languages, giving overworked admins the freedom to use the tools they’re most comfortable with. The centralized platform consolidates automated workflows in a single place for streamlined deployments and efficient management. Organizations can even achieve hyperautomation – automating every task and workflow across the network and security architecture – using the cybersecurity platform as an orchestration hub. This empowers understaffed teams to optimize network performance and security while reducing manual interventions, mitigating the risk of human error.

Ensure 24/7 coverage and availability

An out-of-band cybersecurity platform uses a dedicated network interface – such as a 5G cellular modem – to ensure continuous management access even when there’s an outage on the production network. That means admins have 24/7 access to the cybersecurity platform itself, as well as the devices and systems being protected by that platform. And, crucially, all of the security policies and tools will continue to protect production network infrastructure during that downtime. This continuous availability makes it possible for IT teams to remotely recover from device and network failures without the need for costly and time-consuming truck rolls. Or, in the event of a successful attack such as ransomware, admins can conduct recovery operations on the OOB network, creating an isolated recovery environment (IRE) that’s inaccessible to attackers.

Why choose Nodegrid as your OOB cybersecurity platform

An out-of-band cybersecurity platform uses OOB infrastructure, vendor-neutral management software, and end-to-end automation to provide holistic network security. The Nodegrid platform from ZPE Systems delivers all of this functionality in a single package. Using Gen 3 out-of-band serial consoles and integrated services routers, Nodegrid can dig its orchestration hooks into every system, device, and solution in your infrastructure for complete control. Nodegrid can host or integrate with your choice of automation tools (such as Chef, Ansible, and Puppet) and security applications (such as NGFWs and SSE) for seamless and unified network security management. Plus, with fast and reliable OOB network interface options – including 5G cellular and Wi-Fi – you can maintain 24/7 security coverage and management availability.

Ready to learn more?

To learn more about the Nodegrid out-of-band cybersecurity platform, contact ZPE Systems today. Contact Us