Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Diving into Secure Access Service Edge

You're reading from   Diving into Secure Access Service Edge A technical leadership guide to achieving success with SASE at market speed

Arrow left icon
Product type Paperback
Published in Nov 2022
Publisher Packt
ISBN-13 9781803242170
Length 192 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Jeremiah Ginn Jeremiah Ginn
Author Profile Icon Jeremiah Ginn
Jeremiah Ginn
Arrow right icon
View More author details
Toc

Table of Contents (28) Chapters Close

Preface 1. Part 1 – SASE Market Perspective
2. Chapter 1: SASE Introduction FREE CHAPTER 3. Chapter 2: SASE Human 4. Chapter 3: SASE Managed 5. Chapter 4: SASE Orchestration 6. Chapter 5: SASE SD-WAN 7. Part 2 – SASE Technical Perspective
8. Chapter 6: SASE Detail 9. Chapter 7: SASE Session 10. Chapter 8: SASE Policy 11. Chapter 9: SASE Identity 12. Chapter 10: SASE Security 13. Chapter 11: SASE Services 14. Chapter 12: SASE Management 15. Part 3 – SASE Success Perspective
16. Chapter 13: SASE Stakeholders 17. Chapter 14: SASE Case 18. Chapter 15: SASE Design 19. Chapter 16: SASE Trust 20. Part 4 – SASE Bonus Perspective
21. Chapter 17: SASE Learn 22. Chapter 18: SASE DevOps 23. Chapter 19: SASE Forward 24. Chapter 20: SASE Bonus 25. Index 26. Other Books You May Enjoy Appendix: SASE Terms

Management Systems

Orchestration is a requirement for SASE, as human intervention to security threats or active attacks is not possible. It is not possible for the IT staff of an organization to both detect an attack and stop it within 2 milliseconds. The actual goal should be for attacks to be stopped within one tenth of a millisecond. Effective SASE design can achieve this goal.

The master orchestration platform should be something that will consolidate and collect telemetry from downstream orchestration, while interacting in a push/pull relationship with subordinate orchestration platforms. The master orchestrator must be able to share all collected knowledge with the SIEM as well as all other integrated service components with their respective tools.

API management should go beyond catalog services and provide policy compliance with permanent API backbone services. The API backbone should be a permanent construction that provides constant access to all available APIs for...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime