What are the different types of SASE vendors and which one is perfect for you?

You've probably heard a lot about SASE lately, as tons of vendors (including us) are jumping on the bandwagon. But here's the thing - not every SASE is the same. They're like snowflakes, each unique in their own way. So, why don't we compare these architectures?

1. The One-Stop-Shop SASE Single-vendor SASE: Imagine having everything you need, all under one roof. That's what a single-vendor SASE offers. It's like a Swiss Army knife for your network and security needs, all wrapped up in one neat cloud service. What are the pros to this type of vendor? Well, you don’t have to deal with a bunch of different tools and focus on one that does it all. Plus, it keeps your policies consistent and makes managing everything a breeze. The disadvantage could be that it takes a while to choose a single vendor who fits all your needs.
2. The Dynamic Duo of SASE Then there's the Multi-vendor SASE, which is like a tag team. Two vendors come together – one's all about the network, the other's a security pro. They need to work in harmony, though, so integration is key. This setup's a bit more complex, and while it tries to do what the one-stop shop can do, sometimes it's like juggling too many balls at once.
3. The Custom Blend SASE Portfolio-vendor SASE: Think of it as a buffet. A service provider mixes and matches different solutions to give you a tailored SASE experience. They even throw in a dashboard to keep things in check. It's less hands-on for you, but remember, with variety comes complexity. And sometimes, that means waiting a bit longer for changes and support.
4. The Old-School SASE Lastly, there's Appliance-based SASE. This one's a bit old-fashioned, routing everything through a physical appliance. Sure, it combines network and security, but it can be a bit rigid and slow you down.

Picking the Perfect SASE for Your Business

Choosing the right SASE can be like finding a needle in a haystack. It always helps to look at your current networking team and infrastructure and see how you can potentially move to SASE. While your ideal solution would be a single vendor SASE, you have to ask your team whether you are ready for it.

‍