Listen to post:
SASE adoption requires business and technological planning. By properly preparing for the transition, you will be able to successfully move your business-critical networking and security capabilities to a vendor-delivered service. You will also have the answers to any board and leadership questions.
What does a good SASE adoption plan look like? Below we list six steps that will take you from start to finish. By following them, you can ensure a frictionless transition. (Please note that some of these steps can be executed simultaneously). For more details about each step and how to execute them, read our complete guide, here.
Step 1: Preparation
The first step is to understand what problems you are trying to solve. Do you want to eliminate appliances? Migrate from MPLS to secure SD-WAN? Maybe you need to secure your hybrid cloud or multi-cloud? By determining your drivers you will be able to prioritize functions, allocate the required budget and evaluate vendors and architectures. Once you have your list of use cases, map out which capabilities you need for each one. This will help you identify the right vendor for you, since capabilities vary among them.
Finally, determine your required security coverage. It is recommended to choose a vendor with NGFW, SWG and NextGen anti-malware capabilities. Additional capabilities that will improve your security posture are IPS, DLP, CASB and zero-day/polymorphic threat prevention.How to Adopt SASE in 6 Easy Steps | Download this eBook
Step 2: Planning and Timeline
Once your use cases and required capabilities are mapped out, you can create a plan for implementing them. Adjust the plan to realistic timelines. Make sure to include considerations like contractual obligations, national holidays, how quickly you wish to deploy and the geographical dispersion of your network.
Step 3: RFI/RFP
Step 4: Budget and Board Approval
After planning, it’s also time to get leadership approval for the project. Be sure to include a complete business case that maps technical capabilities to drivers and cost savings. You can also add quantifiable metrics that are relevant to your specific business context.
Step 5: PoC
After slimming down your vendor list to one or two recommended ones, you can move forward with a proof of concept. Formulate a clear proof of concept plan in advance, to set clear expectations with vendors. It’s recommended to cap the PoC timeline at thirty days.
Make sure your PoC has the capabilities and the presence that matter to you, including geographical locations, performance and optimization, security coverage and platform cohesiveness.
Step 6: Implementation
You made it! You can now move forward with your front-runner vendor and complete the purchase process. Plan the implementation together with them, since you two are partners now, working together for future success.
Ready to Get Started?
SASE has eliminated the need to perform expensive, time-consuming hardware refreshes, while also ensuring seamless performance, feature enhancements and daily security updates. To learn more about how to get started, review the entire SASE adoption plan, here.