Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Diving into Secure Access Service Edge
  • Table Of Contents Toc
  • Feedback & Rating feedback
Diving into Secure Access Service Edge

Diving into Secure Access Service Edge

By : Jeremiah , Jeremiah Ginn
4.7 (3)
close
close
Diving into Secure Access Service Edge

Diving into Secure Access Service Edge

4.7 (3)
By: Jeremiah , Jeremiah Ginn

Overview of this book

The SASE concept was coined by Gartner after seeing a pattern emerge in cloud and SD-WAN projects where full security integration was needed. The market behavior lately has sparked something like a "space race" for all technology manufacturers and cloud service providers to offer a "SASE" solution. The current training available in the market is minimal and manufacturer-oriented, with new services being released every few weeks. Professional architects and engineers trying to implement SASE need to take a manufacturer-neutral approach. This guide provides a foundation for understanding SASE, but it also has a lasting impact because it not only addresses the problems that existed at the time of publication, but also provides a continual learning approach to successfully lead in a market that evolves every few weeks. Technology teams need a tool that provides a model to keep up with new information as it becomes available and stay ahead of market hype. With this book, you’ll learn about crucial models for SASE success in designing, building, deploying, and supporting operations to ensure the most positive user experience (UX). In addition to SASE, you’ll gain insight into SD-WAN design, DevOps, zero trust, and next-generation technical education methods.
Table of Contents (28 chapters)
close
close
1
Part 1 – SASE Market Perspective
7
Part 2 – SASE Technical Perspective
15
Part 3 – SASE Success Perspective
20
Part 4 – SASE Bonus Perspective
Appendix: SASE Terms

SASE DevOps

DevOps plays a significant role in SASE as a doctrinal practice to ensure security throughout the software development life cycle. The primary differences between legacy software development practice and DevOps are a focus on Continuous Integration/Continual Delivery (CI/CD) and the integration of the operations component. Instead of developing software and handing it off to someone else to operate it, the DevOps team develops with the operations team as their key customer. It is more common today for a software support team and the software development team to be one comprehensive team. That one team performs all processes from cradle to grave for the application that they are responsible for.

SASE DevOps is realized when purchasing SASE services from a service provider that is also the developer and the operator of those services. Occasionally, the model involves all contributors being from one company or organization. More commonly, the contributors to the DevOps...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY