Topic starter
07/06/2026 8:13 pm
TL;DR: Cloud migration, security concerns, and legacy system costs are the main blockers to modernization, according to Okta’s survey of 100 IT and app development leaders. The real issue is not just infrastructure change, but whether identity and access controls can carry modern applications without preserving legacy trust assumptions.
Editorial analysis by NHI Mgmt Group, based on content published by Okta: “Modern Infrastructure and Development: Using Identity to Scale for Tomorrow’s Technology”.
By the numbers:
- 50% of respondents are worried about the security of their data as they migrate to the cloud.
- 32% of those polled said they’re struggling with security due to their aging, on-prem systems.
- 43% see these costs as a barrier to innovation.
Key questions
Q: How should teams modernize legacy infrastructure without carrying old access assumptions forward?
A: Start by making identity the control plane for the migration.
Q: Why do legacy security systems create more risk as organisations adopt cloud and mobile tools?
A: Legacy systems create risk because they are often patched poorly, configured insecurely, or forced to sit between older and newer environments.
Q: What breaks when legacy applications cannot support modern authentication methods?
A: Organisations often create permanent exceptions, alternate login paths, or password-based recovery for those systems.
Practitioner guidance
- Map inherited trust paths Inventory where legacy applications still rely on network location, static directory trust, or broad backend permissions.
- Prioritise API access management Apply policy-based grant and revoke logic to service and application APIs before expanding microservices or hybrid integrations.
- Separate modern and legacy access patterns Keep high-sensitivity systems on the tightest controls while migrating less sensitive applications or frequently accessed services into modern identity flows.
Bottom line: Legacy modernization is an identity governance problem as much as an infrastructure problem, because the old trust model can survive inside new architectures.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 3 days ago by NHI Mgmt Group
07/06/2026 10:02 pm
Legacy trust assumptions, not cloud migration itself, are the real modernization hazard. The article is strongest when it shows that the failure mode is inherited trust, not infrastructure change alone. Static perimeter thinking, long-lived application assumptions, and inconsistent policy enforcement all become weaker as systems move into hybrid cloud. Practitioners should treat modernization as a trust-model rewrite, not a lift-and-shift exercise.
A question worth separating out:
A: Migration moves the workload, while refactoring changes the way the application is built and governed. Refactoring into cloud-native services reduces monolithic dependencies, but it also requires stronger identity and API controls because the access surface becomes more distributed.
👉 Read our full editorial: Identity-first modernization needs fewer legacy trust assumptions
This post was modified 3 days ago by NHI Mgmt Group