This page is for study. Please confirm important details against the original standards and vendor documents.
Study reference
SDN, SD-WAN and SASE Cheat Sheet
What SDN, SD-WAN and SASE mean, in plain language, with the Cisco SD-WAN component names.
1. What is SDN?
Software-defined networking (SDN) separates the part of a network that decides where traffic goes from the part that moves it, and lets software control the decisions centrally.
| Plane | Job | Example |
|---|---|---|
| Management plane | Configure, monitor and manage devices | SSH, SNMP, NETCONF, a management dashboard |
| Control plane | Decide where traffic should go | Routing protocols (OSPF, BGP), spanning tree, an SDN controller |
| Data plane (forwarding) | Move packets according to those decisions | Switching and routing hardware |
In a traditional network every device runs its own control plane. In SDN the control plane is moved (logically) to a controller, and the devices mainly forward.
| Term | Meaning |
|---|---|
| Northbound API | How applications and people talk to the controller (often REST over HTTPS). |
| Southbound API | How the controller talks to network devices (for example OpenFlow, NETCONF, RESTCONF). |
| Underlay | The physical and routed network that carries traffic. |
| Overlay | Virtual network built on top of the underlay, often using tunnels. |
| Fabric | The underlay and overlay together, managed as one system. |
| Intent-based networking | You state the outcome you want; software works out and applies the configuration. |
Cisco examples: Cisco Catalyst Center (earlier called Cisco DNA Center) manages campus networks. Cisco SD-Access builds a campus fabric using VXLAN for the data plane, LISP for the control plane and security group tags for policy.
2. What is SD-WAN?
SD-WAN applies SDN ideas to wide-area links. A central controller sets policy, and the branch devices use several links (MPLS, broadband, 4G or 5G) together, choosing the best path for each application and encrypting traffic between sites.
Cisco Catalyst SD-WAN components
| Current name | Earlier name | Role |
|---|---|---|
| SD-WAN Manager | vManage | Central place to configure, monitor and troubleshoot the fabric. |
| SD-WAN Controller | vSmart | Control plane. Distributes routing and policy to edge devices. Carries no customer traffic. |
| SD-WAN Validator | vBond | Authenticates devices, introduces edges to controllers and helps with NAT traversal. |
| WAN Edge device | Edge router | Router at a site that connects it to the fabric and enforces policy. |
| Term | Meaning |
|---|---|
| OMP | Overlay Management Protocol. Runs between controllers and edges to share overlay routes, TLOCs, services and policy. |
| TLOC | Transport Locator. Identifies where an edge attaches to a transport, shown as system IP, colour and encapsulation. |
| Transport | The link used to reach other sites, such as MPLS or internet. |
| BFD | Bidirectional Forwarding Detection. Used to measure link quality and detect failures quickly. |
| Centralised and localised policy | Centralised policy is set on the controller; localised policy applies on one edge device. |
3. What is SASE?
Secure Access Service Edge (SASE) is, in Cisco's words, a cloud-delivered architecture that combines software-defined wide area networking with security services. Gartner introduced the term in 2019. SASE joins the network side (SD-WAN) with the security side, which is often called Security Service Edge (SSE).
| Security function | Plain meaning |
|---|---|
| SWG (Secure Web Gateway) | Filters and inspects web traffic so users cannot reach harmful sites. |
| CASB (Cloud Access Security Broker) | Controls and watches how people use cloud applications. |
| ZTNA (Zero Trust Network Access) | Gives a user access to one application at a time, after checking identity and device, instead of to a whole network. |
| FWaaS (Firewall as a Service) | Firewall functions delivered from the cloud. |
| DNS-layer security | Blocks bad destinations at the DNS lookup stage. |
Many providers include more than this core set.
4. Side by side
| Traditional WAN | SD-WAN | SASE | |
|---|---|---|---|
| Main idea | Private links (such as MPLS) to a head office | Use several links with central policy | SD-WAN plus cloud-delivered security |
| Control | Device by device | Central controller | Central, including security policy |
| Internet traffic | Often sent back to head office | Can leave directly at the branch | Inspected by cloud security close to the user |
| Good for | Stable, predictable sites | Many branches and cloud applications | Remote users, branches and cloud together |