So today we wanna talk a little bit about how to put SSI into practice and the lessons learned from our approach from Theia as well as the SSI from Germany consortium. So if we take a look at our next slide, we first want as set the stage with rather European focus. So I recently watched an interview between Migrator as well, Asana OV, and there, she said a simple thing could be to make sure we have identity, which comes from our state that we are not happy with, oh, I can use my Google or Facebook account, but I have my own identity that is independent from whatever business out there.
And I think her point here is not that we ha that we as individuals rely on the government in terms of digital identity, but that instead we are empowered to have different alternatives and that we as user can decide what kind of identity framework we want to use.
And that's also what we see here in the next slide with AI does. So AI does, we talked a bit about it already, but I wanna just give a small explanation for people who might not aware of it. Basically it's a mutual recognition of national a I D means with within the European union.
So if I take my German ID card to, to another member state and want to access a public service, they can access my, my, or can actually receive the information from my national ID card and can accept it. And they have an, the E I E D AI does incep inception impact assessment. And one sentence I found particularly interesting in there is that anonymity of the internet should be insured at all times by allowing solutions for anonymous authentication anonymously, where user identification is not required for the provision of the service.
And I think that's pretty in line with, with the principles of our, of our community, that we say that only if we really need identification of the user, for example, issuing over diploma. And we heard other examples before that we need the identification and otherwise we should go for anonymous solution whenever possible.
And for, to, to, to talk a little bit about identity, it's really difficult to find, to define identity. And I think the best way to, to illustrate this is to use the five mental models of identity, which were best described in a, in a paper by the reboot web of trust. Unfortunately, you don't really see the explanation of the, the other ones here, basically one mental, the first mental model is space time, which means that your identity is built over the past. It lives in the present, and it will be extend and useful in the future.
And how can we make sure that we, that we, that we can solve or that we enable this mental model is through the backup. Obviously there are different options, how we enable the backup. I'm not gonna go into detail here, but that's something which, which we enable.
Another mental model is a presentation. So what I'm able to present as an individual, let it be in a university degree, let it be a certain membership which enables me to go somewhere or something like that. But in that regard, we also need to consider that we have different social circles.
For example, my private social circles or my family circle. It's completely different for my work environment. And obviously I adjust my, my, myself according to the environment. So that's something which we need to consider when enabling identity for individuals. Another identity model is attributes. That's the only thing which is standardized actually in ISO 2, 4, 7, 6, and is rather an engineering perspective.
So basically it, it classifies what kind of attributes you have in a, in a credential, for example, a driver license includes the date of issuance, the name of the, of the, of the holder of the credential.
And so on another one, probably the most important aspect is, or the most important mental model is relationship. So may for you, for example, if you working at a company as an intern or as a CEO, that's obviously a very, quite a important difference, and it enables you to represent the company a completely different manner.
Therefore, the relationship is key to enabling identity in general, and last but not least, we have capability. I, for example, I'm not allowed to, to perform a surgery, but obviously somebody who went to medical school for several years, they can perform it because they got the qualification for it and they can therefore the capability. And that can be, for example, be connected with somebody, press information, apply for participate in.
So we need to think about these mental models when enabling identity for, for individuals and not only have like this rather closed mindset, but rather think big in terms of what we want to enable for the individual and the following slide I want to, oh, here they come up in the following slide.
I wanna talk a little bit about evolution of identity. Probably most of the listeners are familiar with SSI, but still we should now take it for credit. So I wanna provide a little bit of background.
And first we have had siloed identity, meaning that all the companies had their own identity and access management systems, which obviously was very cumbersome for individuals. They needed different username, different passwords, and which led to the rather complicated environment which we observed today. Then we had federated identity systems, meaning that a lot of companies get together and offer the services with one unified login credential for the user, but this offers more convenience, but still it still lacks control for the individual.
And we still have the honeypot basically that you have one database containing a lot of personal identifiable information of a lot of individuals, which leads to data breaches, which we quite observe quite frequently, as well as the correlation of, of user data.
And then the third stage is the user centric identity management, which we currently observe with single sign on services provided by big tech companies, for example, login with Facebook, logging with Google.
And there we have more convenience for the user, but still we have, for example, no data portability offered by these companies. We have still honeypots. And obviously we have the establishment of user profiles, which we obviously want to avoid. So we think there's the fourth generation is necessary as a new evolution of identity systems and self-sovereign identity. Is there the promising concept, which enables all of the dimension aspects.
And for those who are, might be first, her first today here about this concept, if you go to the next slide, you see a kind of simple illustration, how this works from a perspective. So we don't put the identity provider or the business or the government agency in the middle, but rather put the individual into center to, to manage his or her own credential and his whole digital identity and everything which is around needs to, to be around the individual.
And obviously in order to explain that a little bit more detail, another more important aspect of that is the trust triangle, which you see in the next slide, which is a very important aspect, how a issuer, a holder, and a verifier relate to each other. So basically the information is issued by an issuer with, to a holder. The holder can be a subject, but can also be a guardian for, for another subject, for example, a pet or a child. And then this can be proved independently to a and via verified presentation.
And the verifier can then verify this presentation that it not has been tempered with. But something I want to mention here is that we don't solve trust. Trust is up to the individual or, or to the individual company institution in question, and that cannot be solved with, with technology, but we, we provide verifiability.
So the, the Verifi in question can decide on its own if they want to trust the issuing party or not. And for that verification, a lot of, as I implementation use decentralized networks or distributed lectures, rather to say, which are based on decentralized public key infrastructure, and obviously therefore we need standardization, which you have as an overview in the next slide, because we as SSI for Germany coor, we, we have a rather European perspective.
We are born from a innovation competition in Germany, which I would talk in a minute, but first we need international standards to, to be interoperable with other solutions from other countries and other regions. And therefore we follow different governance and technical standardizations in terms of the governance.
We follow the European blockchain service infrastructure, or which we already heard about as well as the technical governance and governance tech from trust IPS foundation, which recently launched and, and facilitates the, the governance aspect and is organized within the Linux foundation.
In terms of the technical components.
We use verify credentials, which are standardized by the world, the, the worldwide rep consortium decentralized identifiers, which are always also organized within the w three C for the, the communication between the agents or the wallet, so to speak, which is peer to peer. We use the DICOM protocol, which is standardized by the decentralized identity foundation, as well as the di off protocol and distributed key management systems from Oasis. And as I already mentioned in the next slide, you see a little bit more about the, the German innovation competition. So we were lucky.
We first started li as a research initiative to, to explore what kind of benefits this technology offers and what kind of use cases are very interesting. And that regard, and we have came together with a lot of other industry stakeholders, mainly from the German market to collaborate on that.
And we are fostered by the federal ministry of economic economy and energy in Germany, and are one of the 11 projects currently in a so to speak competition phase, where we implement this technology and further do research on how we get this to the market. And this is interesting aspect.
So in the next slide, you see the different stakeholders which we brought together. We as main incubator, we, we lead the, as well as the SSI for Germany project.
However, that's obviously a team effort. This can only be done with a diverse set of industry stakeholders, which needs to include stakeholders from a private, from a private market, as well as from the public sector. So it's a public private partnership, and that's, that's something which we see as really valuable as something where all, all necessary stakeholders get together and have a say on how this technology should work for our society.
And other very important partners are then the Bund talk as the photo printing office in Germany, the technic technical university in Berlin as well, ASTO, which we already hear from entre as well as Bosch as our main partners, but we also have other strong partners as associated partners, which help us in implementing different use cases.
So the next slide, you see a little bit about the ecosystem. I already talked about the top level governance standardization, as well as the statutory law.
And these are all factors, which, which influence the governance of such a network, but we also need to consider the identity issuers, the verifiers, as well as the different user groups, the customers, the government representatives, the businesses as well as machines and all of these different stakeholders need to get together in order to, to establish a governance framework, and then which, which provides the rules for the network in question, which is basically the backbone infrastructure for the peer to peer communication. And there we are still in the works.
We, we put a lot of effort in that and we will have an announcement soon. So, so yeah, it's, it's, it's interesting. And in the next slide, I wanna talk a little bit about our use cases.
So we, we take a lot of different use cases, for example, on security and access management about single asylum services, which we want to enable to factor authentication as well, obviously as security implementation. But we also are talks with the trust service provider bank for lock to use a qualified digital signature, which is the legal Porwal to, or digital Porwal to the handwritten signature, so that you can sign legal binding contracts, but also have other cases like password you reset, or physical access management to buildings.
But we, as, as main incubator, we obviously take also a deep look into financial use cases. For example, the reusability of KYC credentials. So know your customer credentials, which is necessary for financial institutions, or to enable the, the consumers to hold their own proof of credit version as if they want to apply for, for a credit. They don't need to, to ask the credit bureau all over again, but can store once and then provide it if necessary in the next slide.
You see some other use cases about, for example, public services.
There, we collaborate very closely with the state of north re failure to enable access to, to public services. But we also have educational use cases where led by the technical university Berlin and also mobility use case cases, cases by BMW or DOK and other use cases include industry. Where's mainly driven by Siemens and Bosch where they, which is in the next slide, which they take a deeper look in their supplier onboarding as well as ticket management and some other use cases I want to, I want to use this moment for the last few seconds to talk about Lisia briefly.
So basically we provide a, we provide a tool for you for institutions companies end users, which is user-centric enabled control and establishment of direct customer relationships and to enable data so variety for different stakeholders, which is privacy enhancing.
And there we have two different software, software components, which we provide one's one for institutions and one for end consumers on the smartphone.
And basically the, the institutional agent, which is seen the next side enables establishment of connections to issuance of credentials, as well as requests of proof requests and, and a general a conversation tool to other stakeholders when it comes to the wallet itself, the wallet, which is see in the next slide, it is a convenient wallet where you can store your credentials and manage your identity on one central platform. And you as a user, you can control meaning that you store your data locally, and there's no vendor lock in.
So if you want to, to use the Atos wallet, intrinsic wallet, connect me from avenue or whatever, then you're free to, to export your data and use another vendor. And that's obviously a very important for, for us as well as the community. And obviously we also am have privacy features and app is already on the market. So on app store, feel free to test our demo. We have also a website, which you can visit also as li.id. And thank you so much for your attention. I'm really looking forward to collaborate more with the industry. Thank you very much.
