Pros and Cons of SASE (Secure Access Service Edge)

0:00 Jamison Cush: SASE is the networking and security

0:01 buzzword of the year. Let's look at the pros and

0:03 cons. Secure Access service edge or SASE. It's a

0:12 relatively new approach to networking insecurity

0:14 that organizations are turning to as remote work

0:17 demands increase. We'll talk about SASE pros and

0:20 cons in this video. And once you're up to speed,

0:22 you can click on the link above to learn what not

0:25 to do when implementing it. SASE is a cloud

0:30 architecture model that bundles network and

0:32 security as a service functions together into one

0:34 cloud service, alleviating security burdens on the

0:37 data center. Benefits of SASE include enhanced

0:41 network security, protecting data from malicious

0:43 traffic, spoofing, and man in the middle attacks.

0:47 A distributed architecture allowing apps to live

0:49 anywhere, including any public cloud, corporate

0:52 data center or software as a service offering

0:55 without sacrificing security or performance,

0:58 centralized management, efficiently routing

1:00 network traffic and improving latency. Role based

1:03 policies with security dynamically applied based

1:06 on the role of the entity trying to gain network

1:08 access. Integrated Security and routing offering

1:12 simpler deployment and lowered LAN costs reducing

1:15 or eliminating expensive circuits in favor of VPN

1:18 connectivity over the internet. As with all

1:21 technologies, SASE has its share of drawbacks and

1:24 limitations. some challenges include, an IT

1:27 culture change, networking and security teams are

1:30 traditionally siloed with competing interests, and

1:33 may have to start working together. Market

1:37 confusion around SASE, many vendors claim they

1:40 offer sassy architecture when it's not the

1:42 complete picture. No more multi sourcing from

1:45 vendors. Traditionally, enterprises prefer to pick

1:48 and choose functions from different vendors. But

1:51 the idealistic SASE model uses a single vendor

1:54 losing some customizations and increasing vendor

1:57 risk. And single point of failure, risking entire

2:01 system shutdowns if the provider has a technical

2:03 issue. So what do you think are the risks worth

2:06 the convenience and flexibility? Share your

2:08 thoughts in the comments below and be sure to hit

2:10 that like button