Bottom line: eIDAS 2.0 requires CTOs to reassess fragmented identity systems into a consistent, regulatory-compliant architecture model.
The revised eIDAS regulation forces enterprises to fundamentally rethink their approaches to digital identity verification. Many organizations have implemented this functionality in a fragmented and ad-hoc manner rather than as an integral IT architecture component.
The situation is widespread in practice: digital identity verification exists in many enterprises as a conglomerate of historical individual decisions rather than as a cohesive system. Legacy systems, grown-in integrations, and isolated solutions for different use cases form a fragmented landscape that is neither maintainable nor future-proof.
eIDAS 2.0 creates clear regulatory frameworks that break up these ad-hoc structures. The regulation requires enterprises to design identity management as a continuous, controlled process — with defined assurance levels, transparent audit trails, and interoperability with European identity ecosystems. This is not just a compliance requirement, but an architectural realignment.
For CTOs, this means concretely: inventory audits of their own identity infrastructure, evaluation of centralized solutions (such as an IAM consolidation project), definition of standards for authentication and credential handling, and planning for integration with government eIDAS infrastructures. Enterprises that conduct this assessment now gain two years of planning buffer before stricter compliance deadlines while simultaneously reducing technical debt in this critical area.
Source: www.computerweekly.com · Published June 2, 2026
Lumi AI News — AI-assisted curation pursuant to Art. 50 EU AI Act. Paraphrase and classification by Lumi News Pipeline v1.2.9.