Secure Access Service Edge Stop on the SASE-travel: a Plan and a Team
In this second part of a three-part series on the way to the Secure Access Service Edge (SASE) is the identification of team members and the development of a Plan that ensures the success of SASE in.
In the first article in the three-part mini-series around the topic of Secure Access Service Edge (SASE) was, that no SASE-is similar to travel a different and each company must determine what questions it should ask yourself when preparing for this Transition. SASE is a technology change and a usage model that changed the way how digital environments considered and how they are accessed, be it by data center-hosted Apps, or Apps and services in the Cloud.
The Team prepare for success
Most of the companies today employ one or multiple IT Teams for the safe operation of your local network. These Teams will be strong in the transition to SASE and far beyond into the topic involved.
Companies select new Tools or features based on their technology and efficiency. The impact on the Team are often lost sight of. This happens particularly often in the case of projects where the solution after its introduction, due to the rash of planning, a lack of Knowledge or creeping expansion had an impact on the production. SASE offers companies the unique opportunity to work with outdated policies and approaches to clean up and to examine how functions are integrated and work together. This supports the Transition to SASE as well as the secure Client-to-Cloud Workforce.
What should be the Team responsible for?
Part of the enthusiasm for SASE occurs because of the promise to integrate many different technologies in a Cloud-native environment, and to simplify the deployment and ongoing maintenance. The convergence of network and security more complex processes simpler and offers Teams a simple operating model, so that no time needs to be spent on the management and recruitment of multiple consoles.
SASE has the potential to be an ideal Setup to display as soon as the functions configured, the processes updated and work procedures are established and operational teams will be accepted. Even if the documentation is free of errors and organisations on a precise application, Client – and Service-inventory feature, requires planning and setup, however, time and patience.
The creation and the Charter of the project team must include processes, policies, and responsibilities for the management of product services. Some of the questions that should be taken into account, are: Are current employees from the operational area, part of the project team? Or it is a new Team tasked with the development of the Service architecture?
Successful Cloud and Distributed Services-projects require a high degree of planning, and continuous iterations and process improvements. This requires a qualified Team, in order to be successful together.
Do the Best you can until you know better. Then when you know better, do better.
According to the aim of defining the prioritization and allocation of skills to meet the objective of the company to follow. This process is one of the advantages of SASE, because it offers flexibility and the usage of Parts of the safety package on the basis of the business requirements.
Companies should keep track of the things that have worked in the past, and as a result of new information, and data points to improve. The operation teams begin their work with currently available information. Even if most of the documentation gaps and challenges occur, must be taken into account in the documentation accuracy and gaps in the planning stages. Only then will you help the project team to set specific priorities and identify where the operational requirements during the introduction and the initial production.
Make a Plan
The planning begins with what is already known and is carried out with the help of a decision tree or a project plan to continue. The setting of targets for the first Phase and their dependence is crucial. Questions that should be asked in this connection, the Team are for example: The objectives for the safety and performance of the Remote access are required? What is the secure Cloud access from branch offices and Remote workstations? What are the application requirements – today and in the next 24 to 36 months? Are larger platform – or function migrations? The answers to these key questions simplifies the definition of goals.
With the defined objectives, it is possible for the company to take the next decisions on the way to SASE. This helps the Team in the creation of a vendor Shortlist for contract negotiations. Service expectations, degree of coverage, the Break/Fix, fixes, SLAs, etc. are all negotiating factors, and arise from the requirements of the business and operations teams. It is quite possible that it will take one to three years, until SASE company is widely in use and, consequently, more staff is needed. Ultimately, SASE to reduce the work load of the operating team. There are numerous steps in between, even for less complex organizations that are not “born in the Cloud” were.
The conversion offers the perfect opportunity to check existing skills. What works well? What is not? It is time for a new feature to add or to migrate an existing Feature that no longer fulfills its task effectively? During SASE is able to address most of the functions through a Cloud-native deployment, effectively, there are on the way, many of the operational decision points to ensure business continuity. This helps companies to stay during the deployment of the new SASE Service is always online and ready for action. Also for applications in the local data center operational benefits resulting from the joint policy models, Workflow processes, and a well-documented operational response plan for the Team.
The journey continues
The industry is just beginning on your journey to SASE. Each company in the provision of security and infrastructure technologies to be operating a team to be dependent, which helps the company in the implementation.
There are many ways, but the best approach is to know where the company started, and to try to eliminate Surprises or to avoid. SASE has the potential to change company. This should prepare for it by including IT operations teams early in the process and the project, the success of this transition to ensure.
About the author
Mike Spanbauer is a Technology Evangelist Juniper Security.
Here you will find part 1 of the three-part SASE mini-series: