4 Key Attributes of SASE Every CIO Should Know

4 Key Attributes of SASE Every CIO Should Know

Enterprise Networking Mag | Monday, July 13, 2020

SASE architecture transitions from network design that centers around identity and user-context based model.

FREMONT, CA: Software-defined WAN instantly became synonymous with WAN transformation, when it was first introduced. However, the truth is that SD-WAN ignores many networking and security issues that face the digital business.

Some analysts aim at solving these issues with the creation of a new architecture: the Secure Access Service Edge (SASE) model. This platform connects and secures entities based on their real-time situation in accordance with the organization's policies.

Top SDN Consulting/Services Companies

Major attributes of SASE

1. Policy enforcement and distributed inspection

SASE not only connects devices but also does the job of protecting them. Inline traffic decryption and encryption scale are table stakes. SASE services inspect traffic with various engines that function in parallel. Inspection engines comprise sandboxing and malware scanning. SASE also offers other services like DNS-based protection and distributes DoS protection. Local regulations like GDPR should be enforceable in the routing and security policies of SASE.

2. Identity-driven

SASE architecture provisions services are based on the context and identity of the connection source. Identity examines a variety of factors, including the initiating user, the gadget being utilized, and real-time factors like the time of the day and location of the device.

3. Global SD-WAN footprint

The goal of SADE is to deliver the optimal possible network performance for all the applications everywhere. To that end, SASE involves a universal SD-WAN service that operates over a private backbone. Utilizing a private network helps in combating the latency issues of the global internet. The backbone should link distributed PoPs that run the security and networking software of the company. Enterprise traffic should hardly touch the internet. It does this only to reach the SASE backbone.

4. Cloud-native architecture

Ideally, a SASE service will be utilizing a cloud-native architecture that no has particular hardware dependencies. Appliances ought not to be service-chained together. The SASE service, like software, can scale as required, is multi-tenant for max cost savings, and can be incorporated quickly for fast service expansion.

On-premises, client premises equipment deployments options are available; however, these SASE endpoints ought to be turnkey black boxes where the users can turn it on and forget about it.

According to Gartner, SASE is a market in flux with vendors that are coming at it from various angles. Many SD-WAN players are shifting to the SASE space. One example is Cato Networks. However, there is still more to see.

Check out: Top Networking Solution Companies

Weekly Brief

Read Also