eIDAS regulation explained: what eIDAS 2 (2024/1183) changes
Blog post from Didit
Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.
Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.
This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.
Regulation (EU) 2024/1183, known as eIDAS 2, amends the EU’s existing eIDAS framework to establish the European Digital Identity (EUDI) Wallet and broaden rules for electronic identification and trust services. Every EU Member State must offer at least one high-assurance, free digital wallet for natural persons by 24 December 2026, while certain private organizations required to use strong user authentication must accept it upon user request by 24 December 2027, except for micro and small enterprises. Wallet use remains voluntary, with protections requiring user control over data, limiting tracking and data combination, and preserving alternative access methods. Businesses relying on wallets must register their intended data requests and validate received information, while very large online platforms and public bodies also face wallet-acceptance obligations in specified circumstances. The reform creates or formalizes qualified trust services for electronic attribute attestations, archiving, ledgers, and remote signing or sealing, giving qualifying services stronger legal presumptions and effects. It also requires browsers to recognize qualified website authentication certificates, establishes security, certification, and breach-response requirements, and sets minimum maximum fines for trust service providers, while leaving most enforcement penalties to Member States.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.