Hyperledger Foundation Hyperledger Global Forum 2021, 11 Jun 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Auditing Enterprise Blockchain in an Efficient Way - Baohua Yang, Oracle America, Inc.

Description

Auditing Enterprise Blockchain in an Efficient Way - Baohua Yang, Oracle America, Inc.

Blockchain has been adopted in numerous enterprise scenarios, including supply chain, finance, healthcare, public sector and others to provide a foundation of trusted data and transactions across companies and business ecosystems. In addition to leveraging the algorithmic trust inherent in Hyperledger platforms, such as Oracle Blockchain Platform, some customers would like to audit the ledger data in real-time to verify that there’s been no tampering for internal reasons as well as to meet legal or regulatory requirements. This session proposes a ledger auditing framework for Hyperledger Fabric that’s been implemented in Oracle Blockchain. It enables users to audit the ledger in order to verify data integrity to meet varied business and regulatory needs as well as to get summary information about ledger size, transaction sizes, etc.

Sessions Details & Slides (if available)- https://sched.co/j3dB
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

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 #HyperledgerGlobalForum2021 #Blockchain

A

uh Welcome everyone. So today I'm going to talk about the how to audit the enterprise blockchain yeah efficiently, I'm bohayan from oracle and I'm the principal architect of the oracle blockchain team.

A

So today I will cover several topics: um the first one we will share. Why do we need to do the ultimate when you're, using the blockchain technologies in the enterprise environment and uh when you want to do the blockchain ultimate, why it's challenging and what problem you need to resolve and if you uh want to design or implement one auditing framework, how to do it uh efficiently and then the last I will show efficient design of the production framework.

A

We can see the components in the season and finally, I will show the evaluation results to demo how click and the performance will kind of achieve.

A

Okay, so why do we need the production called enterprise blockchain? I think I think there might be uh four major reasons. The first one is for the platform users and the operators.

A

We need to know what has happened with the platform, what operations have been taking and uh what transactions have been received by the platform, and the second major uh reason is sometimes you want to improve the performance of your blockchain system and you need to figure out. Where is the bottleneck and the third one is related to the security?

A

It's really when you find uh something is not normal in the system, you need to figure out what happened and the last one is related to the policy uh requirements.

A

Basically, there might be some uh compliance requirements or other requirements that need you to do. The auditing.

A

Okay, so when we do the auditing for the blockchain system, what exactly need to be added? um There might be uh members of resources when you want to do the policy now, but usually we can categorize them into three dimensions.

A

The first one is who is using the blockchain listeners, for example, who is using the the peer who is using the order which, in the fabric, for example, and the second one, is the transaction level.

A

So what transaction has been uh received by the platform in a specific date or how and how many and how many transactions happen, and the last one is, if you you may want to know, uh is everything okay with the system is there any um data or activity is not expected.

A

So all these things need to be audit. If we, if you want to do the auditing for the enterprise blockchain.

A

So, actually auditing is not a quite new feature for the information system.

A

Many other technologies have already are using the auditing features, including those websites, enterprise information system, careers and taking the websites, for example, um for these websites, the typically using the auditing widely for two major purposes, the first one the is that they want to replace the performance issue especially want to find the bottleneck for the performance.

A

How soon the page can be loaded and the housing the link can be jumped too, and the second one they want to have to achieve seo. You want to improve their ranking in the internet and from uh for our website auditing. uh The most used way to implement auditing uh is uh to insert some trees includes into every page when a user reads it to the page. The pc includes will record the information and the impact and the second one is: you can do it uh offline?

A

You need to analyze, build the service load files, especially for the load balancer or the web servers. You can see uh from what ip has visited. Our specific page.

A

So here is an example for the website: audition results from the page. You can see uh it recalls uh for last 14 days. How many sessions happen, how many users and new users, and how soon you can landing uh specific abilities and also when the user exits the page from one page and including the landing performance and the page depth and also the bounce rate.

A

All these metrics can give you some clue to understand what happened with your websites and uh how to improve it.

A

So if we want to adopt these uh mechanisms into blockchain auditing, we will find it kind of challenging. So basically, the blockchain system is different from today's website's ic.

A

The blockchain itself is always distributed and multi-party.

A

So it's uh actually, I agree to add some audience code into every component and what is worse, we all we all know that having trees include include the system will slow down the performance, which is not welcome today and the enterprise blockchain. Typically, when we use it in the production environment, we will enable the logging level, at least with the warning level.

A

So if you want to analyze the log files and to find the audit information, you will find a few. So all these factors will make the blockchain auditing challenging.

A

So, with all these challenges, um how to overcome them and implement uh efficient blockchain auditing, we need some observation. um The first one is we found that with the blockchain, actually uh the members of the network they will share. Typically, they will share the same lego data taking the hub letter of fabric, for example.

A

There there is a channel- and I remember in the channel you are having actually the scene, a larger detail. You can see all the activities inside of the channel and all the transactions in the later in the channel will be recorded into the ledger and it is explored in the blockchain here locally.

A

And we also know that, in order to generate the blockchain space, we only needed the legal data. So it's the the phenomenon to generate all the space.

A

So with these uh observations, we will see that if you want to analyze the later data directly, it is always difficult due to two reasons. The first one is the letter. Size is usually a lot. We have seen the letter side with a single channel over hundreds of gigabytes and water is what is worse, is uh with more and more incoming transaction. The ledger size is always growing.

A

So if we want to do the blockchain auditing based on those network data, we need to design a efficient algorithm and also we need to design a efficient system to make it uh high performance.

A

So this is the basic view of the proposed auditing system.

A

You can see, uh we have clients, we have api handler later wi-fi db and the ledgers, so the client and the ledgers is out of the auditing framework flow, so majorly focus on the api's api handler and the ledger verifier and the tp here.

A

So the first one is the api handler api handler. Typically, it provides those auditing restful apis to the clients. This on our story, we found that today, mostly user, would like to use the restful highs to get the auditing information.

A

So when the constant, uh what is the rest for hr request to the hr handler the hr handler here? uh It has two options to do the response, so the first one is the hi hundred bit. It can directly read the slaughter result from the db directly.

A

This is a recommended way because it's allowed to allow a very quick response, and it also allows you to decouple the api handler from the later wifi and the second way is the api. If there is no such db storage, then you can let the api handler directly uh called the ledger wi-fi here, and the little glorifier will get the audition results on the slide.

A

So in in this case, if the ledger uh volume is large, then the response might be slow.

A

So here's some examples of our in our auditing apis, the first with the first you can see with the first api. um We return to the auditing information for a specific panel and the followings that we can return. The house leaders for the nodes and the resource usage, and also the invocations and the number of billable transactions, and also those statics, are in terms of blocks and more with all these information returned from the auditing api.

A

You will know everything with the blockchain service.

A

So the second major component is the ledger wi-fi.

A

This is the core component of the entire system, because it is real, directly process. The local ledger to check whether the data is integrated according to a specific criteria here, so the criteria is, we can have a very flexible criteria.

A

For example, we can simply check if the ledger file is messaged correctly and we can holding check the data hash and we can also check the hash is changed. The previous hashism is matched with the previous block and we can check more data here and in terms to uh improve, uh provide a high performance uh processing speed.

A

We can have two processing models here. The first one is a for processing. It means we will process the letter from the very beginning, so it may take a long longer time. If the letter size is big and the second one is we what we call the incremental processing?

A

That's. We do not uh process the latter from the very beginning, but from the position that last time we have- and we can also record uh the processor position into the external database.

A

So this incremental processing is very friendly for high performance requirements.

A

The third component is the what we call the tp: it will solve the results by the negative verifier and also you can store other necessary metadata information.

A

For example, you can make the framework in a distribute or clustered deployment, and someone may uh have a question: uh that's how we can protect the db data for or avoid multiple modifications from uh health guys. So in this case, we always recommend you can deploy the db in a safe environment.

A

You can use a self-verified tv like the blockchain people and even you can go to the tv in another blockchain.

A

So here's an example: audition results, the results see it shows a valid on the blockchain ledger. You can see the timestamp uh how soon it is being processed and the letter file, ledger height and those block numbers and the transaction number uh config block index and also the hash values.

A

This example shows the: if the returned message is invalid, you can see using the tool we have identified.

A

The previous hash mismatch at the blockchain block 2, it's a there is a expected value, but the three highest value stored in product2 does not message, and now we also return to the failure letter file. With all this information, you can have some operator to check what has happened.

A

So, in order to find more details about the audi blockchain auditing, we also provide through the statistics within a single block. Basically, it's those hash value, previous hash value and the data hash and the number of transactions, and also the size.

A

So uh we have several uh performance evaluations. The first one is to test the system throughput the transaction per. Second, you can see there's uh two curves uh on the chart, the top one is. We only do the analysis.

A

We do not do the verification and the below one is we do the analysis and also we do replication uh and the x x axis is the number of cpu calls you can see with one cpu call, we can receive a 50 out of the tps, with the verification enabled and without the verification we can achieve around 150 000 tps, and I also want to mention that this firmware can take advantage of concurrency with the more cpu cost. Definitely the speed will increase you may notice. The trend of the curve is not linear.

A

After three cpu calls, and because with the mode and three cpu cost me our test environment, the I o will become the block net.

A

So the second performance evaluation is related to the memory allocated, and here we test with different numbers of blocks from 1000 to 128 000. You can see the allocated memory is always stable around 60 megabytes, so it means the auditing framework is very stable in the memory usage.

A

We also collected the data with the total cumulative hip device. That means that the memory has been allocated during the processing. You can see it's nearly linear with the number of blocks. That also means that the memory usage of the framework is very stable.

A

And this chart shows the the number of dc times with the number of blocks you can see. The code here is also linear. That means the the latency behavior of the framework will be stable.

A

Okay, uh so that's all uh our presentation, thank you and uh let's see whether there's the.

A

Questions, let me see the qa.

A

So the first uh question is from raphael.

A

uh The question is the chain code to automatic, execute audit. We have tried this. Do you think this methodology is available? uh He gives a link. Let me open the link.

A

Oh, it's uh it's a paper uh titled towards secure decentralized and automatic orders with the blockchain. But sorry I haven't read this paper before so I need some time to read it before. I can also on this question.

A

The second question is, it looks like an overall goal is to capture the ledger state. So then analysts could make sense of the data, but could we analyze this data in real time? In your opinion, I believe we used yes, yes, actually, we, our tool, is doing it in the real time, but in terms with very large uh ledger size, we need to do some optimization, for example, to do the incremental processing here.

A

In this case, we can always return the response on the api request in real time.