Podcast
Root Causes 366: What Is eIDAS?


Hosted by
Tim Callan
Chief Compliance Officer
Jason Soroko
Fellow
Original broadcast date
March 4, 2024
eIDAS 2.0 has been making headlines recently with its proposed expansion to the European digital identity ecosystem. But what is eIDAS? What does it do, and why does it exist? In this episode we give you the basics.
Podcast Transcript
Lightly edited for flow and brevity.
Right. And this is really about governing electronic identification of trust services for transactions, it was passed in 2014, came into effect 2016/2018 parts of that regulation. And, Tim, it's gone through some changes. We're going to have eIDAS 2.0 in the next little while, which is reason why we're podcasting on this now, but we wanted to just recover old ground in terms of what this is all about.
Now, I love trying to oversimplify something and then stumbling and failing, but at least attempting to do it. And, Tim, if you are a trade agreement amongst a whole lot of disparate countries in a in a trade block, my goodness, what you need. Like within a country, you can take advantage of the Federation of laws, within, you know, amongst two countries, you can take advantage of what's essentially a contract, right? A North American Free Trade Agreement. Those kinds of things.
But when you're dealing with something as diverse as all of Europe, you've got to have a legal framework that basically states all right, well, if you're gonna have identity rules, you have to have common agreement amongst all these countries about how do you provision? And what's the definition of a digital identity. You know, if you're going to use a certificate, what's the definition of it, and you all have to agree on these things, but you also have to have the legal framework of what is the legal implementation, the legal, the definition of what's the strength of some of these ID objects and artifacts, eIDAS covers all this stuff.
Another thing that you just called out there that's worth talking about is, this is a law that attempts to cover not only the legal consequences of digital signatures - How can they be used? What do they mean? What do they mean in terms of identity and nonrepudiation and things along those lines, but also, the technical requirements, so that we know that a digital - - that the actual certificate, the mechanism, the cryptographic mechanism behind the digital certificate is secure, and predictable and interoperable, and all of those things. So right there, you got some pretty vast scope because you're trying to do both of those things.
Another implication of this and a real thing that's happening is these certificates do not need to be limited, right? This is something that's put in place by the government, but these certificates do not need to be limited to governmental functions. And in fact, the government wants them not to be, right. The government wants to encourage their use through private industry. They have a vision of Europeans just being able to have digital identities in all their various dealings and so that too means that you've got to be able to reach outside of the borders, not only of any European country but of the whole European Union. And so this becomes a thing with global consequences.
The other thing, the other main one is what we call a QWAC and a QWAC which is bound QWAC, by the way, not like a duck, a QWAC is basically - - it's a server certificate. It's a surrogate for TLS certificate. And in fact, browsers and supporting operating systems, what we call certificate consumers, in the parlance of the public CA world, certificate consumers almost entirely, if not entirely, treat QWACs and TLS certificates in the exact same way. So I literally, I don't actually need to put a TLS certificate on my server in order to get the lock and to get encryption. I could use a QWAC. And a QWAC isn't a TLS cert, but it accomplishes the same goal from the perspective of how the software treats it. And so that's a thing that is available for people to use internally, you know, Europeans to use on their web servers. And those are the two main ones.
Now there's a whole ecosystem of things around this to make this work. So for instance, there's time stamping. You've gotta have time stamping services. And then there's a whole bunch of rules and regulations around time stamping, right. And Etsy is the organization that works out these standards goes and spends a lot of cycles on time stamping and what are our rules for time stamping and what do you have to do to be compliant?
Another big one is what you call a TSP, or a trusted service provider and a trusted service provider is essentially a CA right? They don't call it a CA. They call it a TSP but it's more or less the same thing. It's the company that is allowed to issue and maintain these certificates and is allowed to have a trusted root. And so TSPs need to get audited. Instead of getting a web trust audit, you get an Etsy audit. And so a lot of this stuff is parallel to existing systems that private industry invented, right. And if you take it back far enough, all of these things were inventions of private industry and pretty much came out of North America in their origins and they have been taken as schemes that are pretty well proven, reliable, robust schemes and they have been shaped by the European Parliament or by Etsy as its delegated standards creator to fit into the specifics of what they are looking for, for this certificate ecosystem within Europe.
It really, it looks like the European Union wanted its own version of what was created from the commercial world in North America, in order to have recognition, legal recognition and legal transactional flow amongst all their trading partners in Europe.
They wanted also it to be, you know, bound by rules that are made by Europeans. In other words, things have to be GDPR, compliant, etc., and as well as other rules as well. In fact, Tim, I think there was a recent podcast where you and I talked about some of the verbiage that is buried deep within eIDAS 2.0, which also has some other really oddball and some controversial things that are put in there by the European Union. We will let you guys listen to that podcast separately but it's the European way of doing things that came naturally out of the commercial world in North America.
And so when you put all of those factors together, you wind up with creating what is essentially a parallel, extraordinarily similar but not identical, parallel and separate PKI and digital identity ecosystem that sits alongside and tracks within copies what the global private industry is releasing and putting into the market, but then also tries to put certain European, what I want to say, spin on it, right, in terms of, you know, aggressive, very aggressive citizen protections, and an enforced Pan European consistency, and things along those lines.
And so Tim, I think that's, you know, it's an entire topic unto itself and eIDAS 2.0 in itself deals with some of the rigidity of the first eIDAS legislation with respect to, you know, some of the things that just weren't codified well, to deal with identity wallets. They were perfectly fine for digital signatures and QWACs but when you had a wallet, you actually needed to rewrite certain parts of the legislation and I think that's another important part of understanding what eIDAS 2.0 is. That's why some of the laws have rewritten.
And then one of the differences between the CCPA and GDPR thing and the digital wallet is you want these things all to be interoperable. So yes, you could see, just by virtue of the degree of the platform, the number of citizens that fall under its control that this could be the critical mass you need to extend some kind of comprehensive digital wallet scheme that can grow beyond those borders, and perhaps eventually be a global thing.
I think Tim, there's just one other piece to eIDAS 2.0 that I want to touch on. We haven't yet but I think it's important. You know, it's a bit of an elephant in the room and that is blockchain.
And I want to talk about what the identity wallets. What they're prescribing is the usage of a self-sovereign identity.
Now, that gives you a lot of important things. And I'll call out one of the most important ones which is, let's say you are exposing an attribute about yourself to a bank or to a telecom company or to who knows - a florist down the street. And you know, with a lot of crude technologies, you might have to expose a lot of information about yourself, you know, your address, where you went to school, your full name, etc. And I think what's interesting about self-sovereign identities is that one of the things about them that's great it within a wallet context is you can minimize the amount of information you expose about yourself to the minimum that is needed for the transaction.

