MultiHub Forum

Full Version: Early zero-trust rollout challenges: legacy integration, granular policy design, and
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
My company is beginning a phased migration to a zero trust architecture, and I'm on the team responsible for implementing the initial network segmentation and identity-aware proxy for our web applications. While the high-level principles are clear, we're grappling with the practical complexities of legacy system integration and defining granular access policies without crippling user productivity. For security engineers who have managed this transition, what were the most significant technical hurdles you encountered during the early phases, and how did you approach user education and change management to mitigate pushback against the new authentication requirements?
You're tackling a tough transition. Start by inventorying all critical apps, data stores, and users; then build a minimal viable segmentation plan that blocks by default and tests safe paths. Pick a single business unit for a 6–8 week pilot, measure latency, ticket volume, and business impact before scaling.