From Zero to Hero at the Edge
summary
Argues that adopting a SASE platform and a Zero Trust first priority cuts vendor sprawl (cites examples like 500 vendors and a 63‑person shop) by consolidating identity, DDoS/DNS scrubbing, CASB, Secure Web Gateway, and WAF/API controls; lays out a roadmap: map as‑is to target, fix technical debt, pick phased priorities (identity then infra then SaaS), balance resiliency versus segmentation, and use on‑demand vendor staffing to reduce latency, audit risk, and engineer bloat.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:23Goals of a framework vs strategy
- 3:20Sample frameworks
- 5:08Secure Access Service Edge (SASE) Framework
- 6:39The framework to leverage for an EDGE strategy
- 8:17Define the edge before you build a strategy
- 9:51Sample cloud edge architectures
- 12:14Operational models
- 16:13List of critical factors to consider to build out a program
- 19:45Sample checklist of critical capabilities
- 22:13Practical process to conduct a Gap Analysis
- 24:30Prioritize your transition to SASE by phase
- 29:59Questions
related talks
51mTaking Advantage of a Recession to Push a Program to World Class
11mCybersecurity for an Inclusive Future
18mRedefining Cybersecurity: Harnessing Zero Trust Architecture for a Resilient Future
51mIt’s All Geek to Me: Communicating The Business Value of Zero Trust
31mEmbracing Zero Trust When You Aren't the World's Largest Internet Company
51mCloudSec Hero to Zero: Self-Obsolescing Through Prolific Efficiency
51mSecurity 101: A Beginner’s Guide to Cybersecurity and Zero Trust for Developers
57mMaking Security Priority Zero