A New Approach to Private Connectivity with Graphiant

A New Approach to Private Connectivity with Graphiant

Graphiant is a Network as a Service company with the goal of providing private connectivity to customers in an as-a-service platform. Historically, private connectivity has been handled with technologies such as MPLS, metro Ethernet, and more recently, SD-WAN. With SD-WAN being one of the newest iterations of private connectivity and having the ability to use different types of network connections and providers, why is something different needed? I gathered two major reasons why from Graphiant's #NFD33 presenation. Graphiant describes that due to the number of tunnels that SD-WAN creates, the complexity can become high, and SD-WAN does not provide true end-to-end encryption, due to decryption happening at each hop.

Graphiant solves the complexity issue by implementing less tunnels. This is achieved by their implementation of the Graphiant Stateless Core which is deployed in their own private cloud with multiple locations around the world. Customer edge devices, running Graphiant software only create tunnels to the Graphiant Stateless Core. This means that customers can maintain a full mesh network of sites, without maintaining a full mesh set of tunnels at each edge, which reduces complexity.

As far as end-to-end encryption, the Graphiant edge devices encapsulate a packet in an ESP header, then add a Graphiant label to each packet (there is also an IPSec header added is well, but that is only to handle confidentiality across public networks from the edge to core). The Graphiant Stateless Core then only forwards the packets based on that Graphiant label so the packet itself is not decrypted in the core.


Policy Control

While customers natively achieve any-to-any connectivity they can implement policy leveraging the Graphiant labels to control which edge nodes are able to communicate with each other. This allows customers to implement route policy and control without having to effect the underlying network topology.

Use Cases

Graphiant describes three major use cases to their solution: edge, cloud, and B2B. I liken the edge use case to basic private connectivity. This is the act of creating that any-to-any connectivity across the private infrastructure. The cloud use case is around providing that jump point from the private infrastructure into the public cloud using their Gateway service. Lastly, the B2B use case covers the ability to create connectivity to partners and third party providers such as security use cases like SASE platforms.

Private Connectivity, the New Way

Graphiant provides what I see as a new method to deploy private connectivity, consumed in an as-a-service model. They aim to reduce complextity by implementing less tunnels and providing end-to-end encryption by not decrypting packets in their core. I see implementing Graphiant's solution as being a less complex method to both connecting the private enterprise as well as customer implementations into the public cloud.

Nouman Ahmed Khan

Product Leader & Architect | CCDE, CCIE x5, CISSP | Delivering Profitable MSSP Products from Concept to Commercialization

1 年

要查看或添加评论,请登录

Tim Bertino的更多文章

  • AI Workload Networking with Intel

    AI Workload Networking with Intel

    It is difficult for me to fathom the scale needed especially in relation to networking to support AI workloads…

  • Getting SASE with Fortinet

    Getting SASE with Fortinet

    From a general IT perspective, security is a concept that should not be an afterthought. Cybersecurity should be a…

  • Lab as Code with Nokia and Containerlab

    Lab as Code with Nokia and Containerlab

    I think it is safe to say that the concept of labbing is near and dear to the hearts of network administrators and…

    6 条评论
  • Centralizing Network Services with RG Nets

    Centralizing Network Services with RG Nets

    An issue that exists in both large and small networks is tool and service sprawl. Enterprises may have one solution for…

  • Meraki and Catalyst Living in Harmony

    Meraki and Catalyst Living in Harmony

    Since the Cisco acquistion of Cisco Meraki, I had seen them as separate entities from a standpoint of the products they…

    4 条评论

社区洞察

其他会员也浏览了