Up Close and Personal with SASE

Security teams everywhere are struggling. They are struggling with the amount of data and information that they are presented with daily. SASE may be the converged solution that your security team has been looking for.

The Always On podcast series is here to help you understand the intersection of technology, security, and business. On this episode, Eyal Webber-Zvik from Cato Networks and Jonny Noble from Cisco are here to help you understand the intricacies of SASE. You’ll learn how SASE aligns with true cloud architecture, how SASE can help you keep an optimum security posture, and how to get started with SASE.

You will want to hear this episode if you are interested in…

• The SASE vision and journey  [1:22]
• Understanding the defined requirement of SASE architecture [4:08]
• The SASE architecture and service [10:08]
• Understanding true cloud architecture [15:45]
• Keeping an optimum security posture [23:16]
• Getting started with SASE [27:04]
• The future of SASE architecture [30:45]

What exactly is SASE?

SASE, pronounced sassy, stands for secure access service edge. SASE delivers multiple capabilities such as SD WAN, secure web gateway, CASB, next-generation firewall, and zero trust network access. SASE supports the newest generation of companies from the branch office to remote worker access. SASE is delivered as a service of the device and entity. Although SASE has a complex definition, at the end of its complicated journey lies simplification for customers and users.

Why SASE?

Legacy architecture that worked well in the past failed when the pandemic hit because it wasn’t flexible and able to change with the times. Remote workers were often using VPN’s to access company resources even if they were using a cloud-based network. SASE has been built to be future proof. SASE is delivered as a service of the device and entity.

What is the defined requirement for SASE architecture?

There are 4 pillars to SASE architecture

1. It has to be cloud-native which means it must be written and designed to be delivered as a cloud service.
2. It has to be global. The bigger the network the better.
3. It must support all the edges. It isn’t just created for branch offices, but also remote users from anywhere in the world.
4. It converges the networking and security elements of IT infrastructure.

Convergence is the keyword with SASE. Integration was the way of the past but with the convergence of SASE your networking and security solution are one in the same. Find out why you shouldn’t wait until your old security solution is ready to expire before making the switch to SASE. Check out this interview with industry experts, Eyal Webber-Zvik from Cato Networks and Jonny Noble from Cisco.