Can anyone share best practices/tips for implementing SASE with one vendor?

3.2k views2 Comments
Sort By:
Oldest
Director of IT7 months ago
This is very tricky question because it purely depends on requirement and purpose of SASE implementation-Cost control or ensuring Zero Trust, however SASE provides few capabilities like Authentication Gateway Distribution, Zero Trust Network Access(ZTNA), SD-WAN, SWG(Secure Web Gateway), Cloud Access Security Broker
Today, 
More user traffic is heading to cloud services than data centers, work is happening off the network, workloads are running more on cloud services than data centers
More SaaS applications, data is housed on cloud, Perimeter of network and security is shifting from enterprise to anywhere over the internet and cloud, Hence appropriate solution is required to move from hub and spoke network to wherever users.

There are vendors like Fortnet ForteSASE, ZScaler,   Paloalto Prisma SASE,  CATOSASE.

It is recommended to stick to vendor, go step by step enabling the capabilities as the phenomena of implementation of SASE is evolving and changing fast, it is impractical to have it implmented 1st time right.
lock icon

Please join or sign in to view more content.

By joining the Peer Community, you'll get:

  • Peer Discussions and Polls
  • One-Minute Insights
  • Connect with like-minded individuals
Director of Enablement4 months ago
Absolutely - but when you say ‘one vendor’, this can be interpreted many ways. Let’s quickly explore from hardest, to easiest.

1) Multi-product (or sometimes ‘unified’) SASE: this is where a vendor has multiple legacy pieces of software, and they have decided to push them together and call it SASE. This can sometimes happen through 3rd party integrations, or the software stack has been built through acquisitions.

2) True single-vendor SASE: this is where the vendor has a converged stack, with a consistent context across their entire backbone. This happens when the vendor has built everything themselves, and do not rely on old code bases (e.g the vendor originated as a SaaS SASE company, instead of previously selling on-prem firewalls).

Now as for best practices, this can be a very time consuming conversation; so here’s my quick suggestions:

- start with the user, before moving to an SD-WAN deployment. Use a single SDP client to test connectivity, validate policies and ensure that created security rules do not impact application performance. Don’t forget to include the wide gamut of ZTNA capabilities while you’re at it!
- Once happy, move to deploying your sites, as this can be a lot easier once you’ve tested your users!

A true SASE company barely differentiates between a site and a laptop, as the E in SASE stands for edge. It’s not a remote worker, it’s a branch office of 1 that poses a security risk to your network. So policies and configurations have to be consistent to follow your workforce without impeding their productivity.

If you want to talk specifics about best practise or tips, feel free to reach out to me (either here or other social channels) and I’ll happily discuss further
1

Content you might like

TCO19%

Pricing26%

Integrations21%

Alignment with Cloud Provider7%

Security10%

Alignment with Existing IT Skills4%

Product / Feature Set7%

Vendor Relationship / Reputation

Other (comment)

View Results
5.7k views3 Upvotes1 Comment
Director of IT in IT Services4 days ago
Implementation of Zero trust architecture, its modules across the organisation is a priority for us. So, we will be implementing zero trust strategies in IAM, inline with overall strategy.
1.4k views1 Comment
Head of Enterprise Architecture MERCK Group in Healthcare and Biotecha year ago
Strategy & Architecture
Read More Comments
39k views5 Upvotes34 Comments

Yes, and it is always followed22%

Yes, but it is rarely followed54%

Some departments do, but not across the business14%

No9%

View Results
1.8k views2 Upvotes