Hyperledger Foundation Hyperledger Global Forum 2022, 6 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Solving the Internet of Things (IoT) Security Challenges with Self-sovereign Iden... Anatoli Pechkov

Description

Solving the Internet of Things (IoT) Security Challenges with Self-sovereign Identity - Anatoli Pechkov, DSR Corporation

Confidentiality is essential. With the continued market growth, IoT faces a number of challenges around security and privacy of devices and services.

In this session, DSR combines its extensive experience in SSI with over a decade working in the IoT to present use cases of how SSI can be utilized to keep IoT systems secure, while preserving privacy.

Sessions Details & Slides (if available): https://sched.co/1AriI
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
Hyperledger – Open Source Blockchain Technologies

Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use

Discord: https://discord.gg/rVCn4j7UFd
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory

Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter

Follow-us on Twitter @Hyperledger

Learn about Hyperledger Membership: https://www.hyperledger.org/about/join

#Hyperledger #Blockchain
License
Creative Commons Attribution license (reuse allowed)

A

uh Good morning uh we can start I. Guess thanks a lot for coming over to listen presentation. We have prepared for you I hope it will be somewhat interesting, um so my name is anatolo. Pierskov I represent a company, GSR Corporation. So uh the main topic of that presentation. There are a lot of technical details, but besides technical details, we would like to talk about a use case, some use case and some challenges on introducing new type of security or the way how we handle identity in iot.

A

So it feels a little bit about DSR. So you will get an idea why we are talking about that subject. So these are as a software company. We actually do a lot of work for different companies in the industry, different Industries, specifically in IIT, quite a bit, so these are as a part of hyperledger foundation. And besides that we are part of CSA. If you don't know what a CSA CSA it's a communication standard connectivity standard Alliance, you can find that information CSA hyphen iot.org.

A

So this is a pretty big organization uh contains about like I, don't remember, 350 companies so main mainly it's drivers in iot Industry, the big names I can just call out like Amazon, Google, Apple and Legrand other big companies who are Bosch, who are playing a huge role in ieg industry.

A

So GSR is a very active member of CSA, so we are working on standards defining standards. We have been at CSA for over 10 years, just as a kind of like reference CSA, it's a former zigbee Alliance. So it will maybe give you more background on what's going on here. So company itself, GSR is not huge again. It's a software company and we have almost like 300 Engineers. We have been around for 25 years, working with small companies and large corporations, Fortune 500, global 2000.

A

um and mainly three markets. Three regions, I, would say North, America, Europe and Japan. So these are like I, see, focuses for uh GSR.

A

Yes and headquarters in Colorado Denver, who came a little bit earlier, you saw the picture of a beautiful lake that is in Colorado, very nice one.

A

This is a short information company was founded in 98, so we have several divisions like have a pretty large iot Division and we have a business unit which is working in decentralized systems. So these are have been on contributor for India Aries and did come. You can see our names there and we have been working in several companies in the industry very closely as a partner.

A

So what we will talk about and again the main point we will discuss a use case uh and the challenges uh introducing SSI for iot, but um before we will touch that specific topic. I will just go over some challenges in iot Industry overall, regarding security, so security and iot are the ones who are actually working in iot here, I understand: what's the main base for security and iot or what kind of challenges. So there are some issues regarding confidentiality, it's it's very essential issue and so the way how to solve it.

A

There were several governing laws introduced jdpr. You know, and then SB California, SB 327, by the way that California has been 327, was specifically addressed to iot security issues um and a lot of companies and standards they had to adjust the approach in security that actually brought us to Neo standards. That means, as soon as the new standard is introduced, there is a new implementation has to come in place, certification and then release of the devices or Solutions on the market.

A

uh This is a little uh brief about gdpr uh what kind of requirements uh it introduces and California consumer Privacy Act. These are two main drivers in last. I would say three four years for iot for security I mean so. Let's talk about a little bit about digital identity, digital identity.

A

um Overall, we all understand what does it mean uh for people? uh It means yes, we have. We can have our traditional identity like passport or ID, and so on. However, uh the new identity we are getting uh in place, it's related to digital identity and um well it's it's very interesting that uh we are as humans. Yes, we have to have an identity, but in the same time, if you think about let's say a device device, it's a proxy for us as humans, and they have devices they have a lot of data.

A

It means there is a right away. The issues around privacy, uh how the data is stored, who has access to the data and it means every device- has to have an identity.

A

If you think about how many devices are right now deployed on the market on a planet, that's a huge number really huge, like a wireless communication like sensors, like even in this room. If you start counting I, I'm sure we'll we can count like about 200 devices, at least including, of course, your cell phones, your laptops, different kind of motion, motion, sensors, video cameras, smoke, alarm devices and so on and so forth, and all these devices they have to have an identity.

A

So and again we are talking about challenges for digital identity. The main is a trust and privacy.

A

There are some standards already in place, but we need to really improve it and work on it. um So, let's uh check what kind of identity models are available on the market at first, a very traditional sellot identities, and you know SSL based TLS SSL SSL. This is, uh you can see it case, number one. So when you send some information confirmation and it's directly confirmed by organization, so then there is a second type of identity.

A

Confirmation, that's a third party and we all can see it's in place in play when we when, um for instance, like we, are trying to register yourself on some website, it's offering you like face using Facebook Identity or your Google identity. So this is all and again all the information is stored in those storages of those providers.

A

Of course there is a deficiency here, because we cannot control our identity and now it's all controlled by Third parties and it's not necessarily Evil by the way, because it's just a convenience for right now so, but we need to evolve those methods and uh very uh important uh protocol on x.509.

A

It's in place heavily used in iot. A lot of money is already invested into support for that protocol in iot a lot of companies. They spend millions and millions of dollars for the infrastructure, and we will talk a little bit later about what does it mean, but if you think about overall, it's great, there is some infrastructure in place. However, this is a huge obstacle for moving forward with new methods for introducing new security and identity methods on the market. Why?

A

Because a lot of money is already in place in invested, and when you are making new decision like moving to a new methods, then it means all this money will go to nowhere and it means every person who made a decision to invest into this kind of infrastructure will be I would not say exactly personally responsible. However, it's a career uh related decision, so so it means we are having more interesting obstacles to um for implementation of new methods.

A

So the new method is a SSI self-sovereign identity. uh Most of you quite familiar with that, this is a new method which we are trying to introduce in iot, but in order to introduce it, we need to have main players being at first interested in new methods. There should be a reason why it should be introduced, and, secondly, we need to get those companies on board, so they will start pushing a new approach on the market and that's quite a task.

A

Now, let's talk about iot in general, um specifics of the security in IUD- oh so! Yes, there are several specifics, uh however, uh the main ones. Of course we need to make communication secure, that's particular very simple, uh but um if you will think about iot, there is a lot of um wireless communication involved here and a lot of embedded devices, and this is a completely different world and usually like developers like I, don't know people who are working like on hyperledger, blockchain and so on.

A

They don't understand that exactly why, because well, here's a computer, you just designed the code and who cares how much you know: memory takes how much resources, CPU and so on. Actually people, of course, care. I'm simplifying it. However, not the way how embedded software Engineers care, because here is everybody, every cycle CPU should be counted and every system should be strictly budgeted.

A

So in that case we have a quite a challenge. It means all the methods we are talking about. They have to be implemented strictly and focused towards um embedded devices.

A

Okay, let's, let's talk a little bit about 509.

A

And again, I don't want to kind of like go over in details, because this is all public information you can. There is no innovation here. We are talking about. I just want to make a reference. What exactly happening, and um so 509 been uh have been quite a traditional approach in iot for digital identity for devices, and it's really. uh There were a lot of efforts to make uh 509 working for iot devices. Some are okay for some ecosystems. Some are really not very successful.

A

If you think, like latest Protocols, are coming to the market about iot if you're familiar, there is a new protocol matter which will be released in December. That's a new protocol for IP based devices based on like it can be based on like Ethernet or it can be based on um thread if you know thread it's a wireless communication protocol uh kind of like um successful 206, open.

A

So 509 is really kind of a real base for these protocols.

A

However, uh that classic approach doesn't allow us to move forward. There are some drawbacks and deficiencies in this protocol. For instance, as I talked about like footprint footprint of devices. It's it's really big deal. Why? Because, uh when you are releasing a device like I, don't know, let's say: motion sensor: ah the device can be released like a 100 million devices.

A

I'm just talking about scale, it means when you are adding more memory. The price is going up and overall, the cost of that investment and uh solution is is huge. So 509 uh has a like a lot of deficiency here. Why? Because the key itself is very long and uh storing it on a device can be too expensive.

A

This is the way um how it works. Usually, so we are considered talking about shear, Two, uh personas, um Alice and Bob. So and all the verification is going through um a root authority of the root public certificate uh by the way just for reference I'm, not exactly a specialist in security. So I can answer some questions, but not all of them.

A

So I'm, just representing the topic but I, know a little bit more about iot, so uh what's happening here, uh you can see so it's always involved root and that's that's kind of very critical point because it brings um if root will be compromised. uh So if the implementation is not really strong, it means all the certificates for all the devices will be compromised and the entire system, that's a huge security Bridge. So it means that approach.

A

It still works, but in this case we'll have an issue.

A

And 509 doesn't give us a lot of privacy. What does it mean? Because when we are changing all the information to um verifier, we are basically sending all the information about device, and that's not good good? Actually, because you understand like there is some information not related to a verification process at all. I can give you like a real example of life, so I live in Colorado and but there are different states the way how they handle like your access to alcohol, for instance, in a bar.

A

So you know how it's happening: uh the waiter or waitress. They check your ID and they check idea. They can see your database, so they know exactly how old are you and they can check? For instance, in some cases, social security number. There is some additional information which is not exactly related to the case, because what waiter should be worried about I'm over 21 right, but in some states I, don't want to name it, but in some states even worse, they take your ID.

A

They go into some room and send them that information to the state government and it's. uh This is the kind of demonstration and that your information is leaked to some third party, and you have no control on this, so SSI idea so to make a privacy conventionality work in more granularly. That's that's the idea.

A

So that's I was talking actually about already that case.

A

So there are several more issues here related to 509. I, don't want to like talk more because there are definitely that solution has to be improved, and this is why uh we believe that SSI approach will give us a chance to improve it dramatically.

A

So there are several issues as I said: non-sealactic disclosure, no authorization, and besides that I talked about overhead.

A

And single point of failure, so again, so let's talk about what SSI saw a self-sovereign identity provides us and what kind of Advantage will give us. So we can improve our security for devices not only for people but overall for devices as well.

A

uh We believe that SSI approach will help to create more robust and more um reliable security and help us to control our identity of devices, which is very important, and this is the way how it works it's slightly different than in case of 509, but um well there are some actually similarities. There is an article very nice one if you want to check the difference between 509 and SSI. I can give you a reference to that article. That explains like very much in details. What is the essential difference.

A

So what SSI provides SSI provides security, of course, private privacy and verifiable relationship.

A

So verifiable credentials we all know. Yes, there are some already examples of digital passports on device certificates, access, tokens and bank accounts. So we are talking about what are the key terms for SSI.

A

I'm, just giving you time to read, Because I can read it for you.

A

This is the way how the SSI verifiable credentials uh work. It's a workflow uh on the left side. You can see each year uh if you're issuing a credential. This goes to colder and holder in our case device or a person stores the data on their in their memory or on their device, and there is a verifier verifier and then there is a decentralized network. It can be blockchain for creating a storing some public information by the way. It's not exactly it can be, not a blockchain at all. It can be.

A

Some of the solutions can be used without blockchain. So it's not necessarily like blockchain is involved. Blockchain just helps to store that information publicly and being decentralized.

A

Okay, uh well, that's um uh that slide, uh showing like a magic officer side. Of course, there are a lot of technical details here, uh very important ones, which distinguishes a new approach against uh the previous ones. But this is kind of like overall, um a dream. I would say.

A

So, privacy again talking about privacy, it's a big deal and uh SSI approach completely provides a mechanism so the way how our privacy and device privacy can be preserved.

A

So here we have several actors, I would say Ellis and Bob and the way how Alex deals with uh sure information and presents it to Bob about Banks and hospitals and police. It's very interesting.

A

So that is the case we have a demo I will I will show you a little video. Actually uh it's an actual iot demo of the implementation, uh the way how SSI could work for iot?

A

Well, you probably know there are several companies trying to implement SSI already for iot. But again there are a lot of obstacles here and like real good implementation. I mean true. Implementation, as we know, doesn't exist yet because it we still need to work on a lot of technology side, details.

A

Repeatability, that's one of the um issues here and 509, for us, for instance, are always non-reputable. uh So here we have a case, then SSI completely solves it.

A

And it's very important that uh SSI helps us to um provide not all the informations which provide the only information which is required for specific case and 509 in this case, of course, will disclose everything which is not even related to the case. uh There is an anonymous revocation mechanism.

A

That's very important as well part of the deal, and this is the way how the asterization is happening.

A

Whatever that presentation is, will be available as a part of all materials for conference, and so you can check it. Of course you can ask questions and send it personally, questions happy to answer.

A

So SSI actually provides a delegation for Authority. This is a kind of like a regular case. If you think about I, know, I have a question for you who has like home automation at home, like system, how many like I know garage or a door or you held okay, several people- and you know like if you're going for vacation, sometimes like it depends on what kind of neighbors you have like.

A

I have very nice, neighbor and uh I like him to like open my garage, and uh you know like swing the package I received uh to uh under the garage door and that's, but uh you know some of the systems now they like on the application Level allowing doing it like, for instance, I, can delegate some of the rights, but SSI actually helps in delegation quite a bit. It provides additional mechanism and security. For instance, you can say okay, that person can access my home like five to six in the morning or I.

A

Don't know during uh uh like two to three pm to fix some electrical issues and so on uh most important, zero knowledge, iot clouds. That is a big deal. Why? Because every iot system stores a lot of data about us like when you coming home when you are leaving home, what is the temperature? How are you using electricity and all this kind of stuff?

A

And uh but SSI helps us to make all this data basically not personalized, so it means, if even if you will have an access to the data, it will be difficult to connect to a specific person. That's very important, so it's a zero knowledge. Iot clouds.

A

Here we are talking about distributed source of trust, so there is no single point of failure, which is important. It means if the network will be compromised. It will be only kind of on a very, very much localized.

A

And you can see one of the several approaches how it can be done.

A

This is kind of more technical, um so talking about compact evocation, so it can be done in very efficient way. Again. We are very much up to using SSI against 509, so we would like to push it and by the way, if you are interested in exploring that approach, please talk to us I'm, happy to find partners and people who really or organizations who really like to have it deployed on the market.

A

uh Now uh I will talk a little bit about hyper, Ledger, Indie and Aries. Why? Because our company was one of the maintainers and contributors to India and to uh Eris. So overall, um this is very generic information. You must, you might know that, so indeed, it's an independent identity. Basically, this is an open source software, which is it's an active project which is part of hyper Ledger and Linux Foundation.

A

Everyone can access it and download and contribute, and so on.

A

This is a state right now, it's uh Indian to the moment. There are several components which written in Rust python node.js java.net, uh but so it's very interesting like can you use one of those components like for IET?

A

It's not applicable like yes, you can use it like on a Gateway which is pretty powerful device can be, but on a actual, like a very much restricted device, that's not possible, so it means we have to create additional software, which will Target um a specific range of devices, and you know the challenges we are talking about are substantial.

A

uh Let's talk about like what kind of devices we are dealing. Let's say there is a gateway gateway. It can be like Linux or free artos or Amazon, whatever it is the operating system uh and there's a lot. There are a lot of resources uh to handle SSI.

A

However, if we will move uh like to sensors, in that case, you will have an a challenge. Why? Because the devices are very much very much restricted, not only on a like a Ram size or a ROM size.

A

uh They are restricted on amount of energy because if you will move like one step up or depends on down, uh let's, let's talk about green power devices if you are familiar with green power devices, these are really um super restrictive uh devices, for instance like when you are using, you can be using switch, which is a can be better or less switch. It means what's happening, light switch.

A

We are pushing the button and there is some mechanism which generates enough memory enough energy for CPU to process like a certain, very small amount of operations and all the security certification. Verification so should be able to fit into a usage of that amount of memory. So we are it's pretty challenging task and make it secure. We need to understand how far we want to go with that security approach.

A

Well, um some of you know there is um so. It is I would say like um not exactly a new generation of India, it's a more decoupled uh architecture than India itself, so this Arc has been working uh on Aries as well, but besides I want to tell you that these are itself. We have been working Fabric and ethereum, so we have been using a lot of components in our development depends on customers and so on. Here we are talking specifically about Indian areas, because the GMO is based on India.

A

Okay, uh so what is the difference between Indian elders and Aries? There are a lot of differences, but that's more like components. So it's more decoupled and less I would say more solid, outside uh more flexible architecture than India.

A

And again, the diamond I'm going to show you uh it's based on India, but here we have a comparison between engine and Tennis, so you can see uh the difference. Let's talk about iot use cases for SSI, um okay, the main challenge for in iot when the most of the security breaches is happening. This is the moment when we are commissioning device, because, when you're a commissioning device, it means that device has to provide like a security authentication to appear where it's connecting to the network so making sure.

A

If the device will be included into the network, it has to be secure. It's locked, it's not a device which is not authorized, should not be connected and at that moment, actually is a very important moment because most of the breaches, if you will see uh happening on the market, it's at the moment when the commission of the devices happening uh by the way, I don't know. If you try to connect I, don't know, let's say homecoming feature of your car like opening the garage door.

A

uh Actually I had an incident and I was commissioning the device and, in the same time my neighbor opened the garage and my device got connected to his garage. That's that's really unacceptable. So it means that moment is a very I'll say, intimate and very important one. So addressing the device authentication, uh it's a very critical step, and this is the way um how the SSI can help solving that.

A

So this is the continuous device authentication. There are some little details here, of course, in real life, if we would implement it as a part of the standard there are more, details has to be worked out and a lot of, of course, review and Security Site excuse me have to be done.

A

uh Well now we are talking about the smart, uh the uh the use case itself, so the idea is um so Alice. uh She wants to delegate access to her Smart Lock to the neighbor. This is a delegation basically and uh to Bob, and this is the way how it um uh can be done for using SSI.

A

Okay and here's the case uh how the revocation could happen in this case.

A

And this use case, it's number three uh showing how to preserve privacy, not sharing a lot of information about private information. This uh third party, so basically Alice she wants to access a door and she has to be over 18 years old. Let's, let's talk about like she wants to access a bar and she wants to get in so she's just using her credential, and in that case the credential will send a message, uh confirmation that she's over 18, but it will not specify how old is she so that is really very important.

A

So there are several more additional use cases we have kind of um uh listed here you can see, but of course the number of use cases is huge uh in ieg and uh if you are using at home ieg devices, you need to think about your privacy quite a bit. There is a by the way uh Alliance iuxt Alliance in the United States that ixt Alliance is working all about security, and one of the members actually did a check at his house very interesting.

A

He has many devices and he checked how much traffic is going out of his house and he found out that the amount of traffic was huge really so. Yes, there is traffic income and that's initiated by him, but the amount of traffic generated by some Wi-Fi Road router was so huge. He actually had to join it off because he didn't know what kind of information was translated to the net. So it means security is really a big deal, and especially um so so you need to be in control of your security.

A

Thank you. ah Mrs Jama, by the way is available on internet. You can download the presentation, and there is a link to YouTube video I will run. I will try to run that video here. Just a second, that's a very short one. Basically, a couple minutes.

A

Okay, here we are.

B

This is a demo showcasing a blockchain iot security use case using the zigbee iot stack. This process is widely applicable to security and Hospitality applications and increases the efficiency and security of Access Control, while also maintaining the total privacy of the user or guests.

B

So, let's walk through the process and a simple use case. First, we have to start with credentials. Credentials are initially created by an authority such as the government. The credential in this example consists of basic information such as a name and birth date, think of it as a license or passport upon issuance. This credential is signed by the authority using a key that is rooted on the blockchain.

B

This allows us to use the blockchain as a source of trust later on, for storing public information, such as the issuer's public keys.

B

Here you can see the initial credentials issuance process notice, how fast and simple it is to create a new set of credentials and to create a secure connection between devices using a simple barcode.

B

Then, in order to gain access to something in this case, our hotel minibar, the approver, connects to the Gateway or verifier via a public key. The gateway then requests a proof from the prover who sends back a zero knowledge proof.

B

For instance, the proof verifies that the person is old enough to access the mini bar, but does not tell you their age here. You can see the whole system. The small white box is the Gateway. The black box is the lock we will be operating and an indicator light bulb is on the left.

B

First, we create a connection between the prover and verifier. The proofer gets a public key from the Gateway and fulfills. The proof requests from the verifier.

B

You can now see from our indicator light that the user's proof has been verified and the Box will unlock.

B

In a situation such as our mini bar example, it is likely that we would want to Grant repeat access to the user. You can see here that the user can use their existing credential to unlock the midi bar without repeating the issuance process, just as you would with a real world ID or passport.

B

If the credential doesn't match the proof request in this case, if the user is too young, the app will generate no proof and the user will simply see an error message.

B

It is important to remember that the zero knowledge proof is not the same as the user's credential, and it does not disclose all of the information about the prover, but only the required information. In this case, it's sufficient to prove that the user is old enough to access the mini bar, but their exact age, name and birthday will not be disclosed. This system allows for access control without interface between the prover and Authority. The zero knowledge proof can be verified by the verifier.

B

In this case, the menu bar via the blockchain without direct communication with the issuer, the issuer or authority can even be offline and the verification will still work. This way, the user can be granted secure access without ever disclosing any of their private information visit our website today and let us know how DSR can help you come up with a solution for your product or company.

B

A

um Just for the reference, what kind of tools used here you can see like two iPhones and there is a gateway. The Gateway itself is on Raspberry Pi, so it means we had to implement SSI on a Raspberry Pi and we did. Some of the implementation is done on a door lock itself, it's a ziggle door lock.

A

um So that's the we are using zigbee protocol for this demo.

A

Okay! Well, let's.

A

That's all actually.

A

Thank you appreciate it.

A

uh Well, that's a link. uh Oops yeah, no, no worries, it's all good teamwork. So that's a link. You can get that link uh from the presentation.

A

um Well, we have sorry like two minutes left for questions, but you can ask me questions after um the presentation itself. So again, my name is anatolo pierskov I'm, a CEO and founder for DSR Corporation, a company out of Colorado Denver. Please talk to me if you have questions or ideas.

A

Okay, thank you.