Legacy insurance modernization exposes the identity governance gap

At a glance

What this is: This is Comarch's account of an insurance modernization project that replaced legacy systems, integrated more than 12 external platforms, migrated the full portfolio, and moved the workload to cloud deployment.

Why it matters: It matters because insurer modernization changes access paths, operational dependencies, and control boundaries at the same time, so IAM, IGA, and platform teams need to govern the transition as a security and lifecycle change, not only a technology refresh.

By the numbers:

• The new platform integrates with more than 12 external industry or national platforms, including Berichtenbox and Pondres.

Context

Insurance modernization is not only a core systems replacement problem. When a legacy policy, claims, or benefits platform is rebuilt, the identity governance model changes with it because user entitlements, workflow ownership, and system integration paths all shift at once.

In this case, elipsLife Netherlands was replacing outdated systems that were tied to high license fees and rising operational risk. The article also shows that modernization was aimed at automation, user experience, data migration, cloud deployment, and integration across a broader ecosystem, which makes access governance part of the transformation rather than a separate workstream.

For IAM and IGA teams, the important lesson is that operational redesign can outpace control redesign. That is typical in insurer transformation programmes, especially when multiple external platforms and cloud-hosted services are brought into the same operating model.

Key questions

Q: What breaks when an insurance legacy platform is modernised without rewriting access governance?

A: The common failure is that old approval paths, exception roles, and ownership assumptions stay embedded while the business process moves to a new platform. That creates entitlement drift, unclear accountability, and audit gaps. In practice, the migration can succeed technically while governance fails operationally because nobody reauthorised the new control model.

Q: Why do external platform integrations increase identity governance risk in insurer transformation projects?

A: Because each integration extends the trust boundary beyond the core application. If ownership, authentication, and revocation rules are not explicit, partner access can outlive the workflow it was created for. The risk is not just exposure at the connector layer. It is uncontrolled persistence of access across systems that no longer share the same operational context.

Q: How do IAM teams know whether a modernization programme is ready for cutover?

A: They know it is ready when access ownership, approval flows, and offboarding rules have been rebuilt for the target platform and tested against real business scenarios. If the new system still depends on legacy exceptions or manual workarounds, the programme is not ready. Technical readiness without governance readiness is only a partial transition.

Q: Who should own access governance during an insurer's cloud migration?

A: Ownership should sit with the business process and identity governance stakeholders together, not with infrastructure alone. The cloud team can operate the environment, but business owners must validate who can do what, and IGA teams must ensure those decisions are reviewable and revocable. Shared ownership is the only way to keep the control model aligned with the new operating model.

Technical breakdown

Why legacy insurance platforms create governance drift

Legacy insurance platforms often accumulate entitlements, workflow exceptions, and manual handoffs over time. Once a business depends on those systems, the real control model lives in process workarounds as much as in formal IAM rules. When the platform is replaced, those hidden dependencies do not disappear. They have to be re-expressed in the new system, or access becomes misaligned with current business ownership, approval paths, and audit expectations. In insurance, that matters because policy administration, claims, finance, and document generation are tightly coupled. A modern platform changes all four at once.

Practical implication: map legacy approval and entitlement flows before migration so the new platform does not inherit invisible access exceptions.

How integration across external platforms changes identity boundaries

Modern insurance stacks rarely stay inside one administrative perimeter. Integration with external platforms means the identity boundary extends across APIs, shared data flows, and partner-owned processes. Each connection creates a place where ownership, authentication, and entitlement scope must be explicit. If those boundaries are informal, the organisation cannot reliably tell which access belongs to internal operations, which belongs to a partner workflow, and which must be retired after a process change. That is why integration projects are also lifecycle projects: every connector introduces a governance dependency that has to be tracked, reviewed, and revoked when it is no longer needed.

Practical implication: treat every third-party integration as a governed identity relationship with an owner, scope, and offboarding path.

Why cloud deployment changes the control plane for insurance operations

Moving an insurance application to cloud infrastructure changes where control lives. Instead of relying on static on-premises boundaries, teams have to govern access through the application layer, the cloud environment, and the surrounding identity fabric. That affects who can configure the platform, who can read operational data, and how service-to-service trust is established. In practice, cloud deployment compresses infrastructure, application, and identity decisions into the same operating model. For insurers, that makes operational resilience, data integrity, and compliance dependent on identity discipline across every layer, not just on the application itself.

Practical implication: align cloud access controls, service identity ownership, and operational approvals before shifting core insurance workloads into a hosted environment.

NHI Mgmt Group analysis

Legacy modernization exposes an identity governance gap because the control model changes after the business process already has. The article shows that insurer transformation is not just about replacing old software, but about rebuilding the operational fabric around it. That creates a period where access, approvals, and system ownership can lag behind the new platform design. Practitioners should treat modernization as a governance re-baselining exercise, not a lift-and-shift event.

Insurance platforms fail when workflow ownership and entitlement ownership are not rewritten together. Policy administration, claims handling, finance, and document control are all touched by the same platform change, so access decisions cannot be managed as isolated tickets. When those functions are integrated into one system, the identity model has to be integrated as well. The implication is that IGA and application teams need a shared design checkpoint before production cutover, not after it.

More than 12 external platform integrations turn modernization into an identity boundary problem. Every external connection introduces another trust relationship, another lifecycle dependency, and another revocation event that can be missed. That is especially true in regulated insurance environments where local compliance and partner connectivity intersect. Practitioners should regard external integration sprawl as a control design issue, not simply an architecture count.

Cloud-hosted core systems move security accountability closer to runtime identity than to infrastructure ownership. Once the platform runs on Comarch Infrastructure Cloud, the practical question is who controls access, reviews it, and retires it across the application and service layers. That shifts emphasis from the old perimeter to governed identities, traceable approvals, and operational accountability. The named concept here is identity-governed modernization: migration only succeeds when access governance moves in step with the platform.

The real benchmark for modernization is whether operations can be reauthorised at the same speed they are reengineered. The article's performance claims show that business throughput improves quickly once legacy friction is removed. The governance question is whether access, review, and accountability mechanisms can keep pace with that acceleration. Practitioners should measure transformation success by whether control ownership scales with operational change, not just by user experience or processing speed.

What this signals

Identity-governed modernization is the right lens for insurance transformation because the entitlement model, workflow ownership, and platform architecture all change together. If governance is rebuilt after migration, the organisation inherits a new system with an old access model, which is exactly how drift enters core operations.

Insurance teams should watch for integration sprawl as a governance signal, not just a technical milestone. Each new external platform widens the scope of who can trigger business activity, who can see operational data, and who must be offboarded when the relationship ends.

The practical test is whether the modernised platform can be reauthorised as cleanly as it can be scaled. If access reviews, approval paths, and service ownership cannot follow the new operating model, the programme has modernised the technology faster than it modernised control.

For practitioners

• Map legacy access dependencies before cutover Inventory who approves, uses, and supports each legacy insurance workflow so entitlement changes can be rebuilt inside the target platform rather than carried forward informally.
• Rebaseline third-party integration ownership Assign an owner, scope, and offboarding trigger to every external platform connection so partner access does not survive after a workflow or contract changes.
• Separate application roles from operational roles Redefine who can administer products, claims, finance, and reporting in the modernised system so business function ownership does not blur into technical access.
• Align cloud access reviews to the new operating model Review application, service, and cloud privileges together after migration so the hosted environment does not create a second, unmanaged control plane.
• Validate migration against audit and compliance needs Test whether the new platform preserves historical portfolio data, document outputs, and approval evidence in a form that auditors and business owners can trace.

Key takeaways

• Legacy system replacement in insurance is also an identity governance event because workflow ownership and access boundaries shift during the same transformation.
• The article shows that modernization can unify policy, claims, finance, and reporting, but that same unification requires sharper ownership and entitlement control.
• Practitioners should rebuild access governance alongside migration, cloud deployment, and partner integration rather than treating it as a separate post-project task.

Key terms

• Identity-governed modernization: A transformation approach that treats access, ownership, approval flow, and offboarding as part of the modernization design. In practice, the platform change and the control change must happen together, or the new system inherits old governance assumptions that no longer match how work is performed.
• Entitlement Drift: Entitlement drift is the slow accumulation of permissions that no longer match the original purpose, role, or workload. In cloud-native and NHI-heavy environments, it usually happens because access changes faster than review cycles, leaving organizations with more privilege than they intended.
• Third-party identity boundary: The practical line where internal access ends and externally governed access begins across partners, platforms, or hosted services. In modern insurance environments, this boundary has to be explicit because integrations create new identity dependencies that must be owned, reviewed, and retired on a lifecycle basis.
• Cloud Control Plane Integration: The ability for a security platform to connect directly to cloud provider management interfaces and read operational data without installing software on every workload. This approach improves coverage in cloud environments by using native infrastructure visibility instead of relying only on host-level tooling.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.