A zero-hacking protocol for secure multiparty computation using multiple TTP

Abstract

We present a solution to the Secure Multi-party Computation (SMC) problem in the form of a protocol that ensures zero-hacking. The solution comprises of a protocol with several trusted third parties (TTPs) where there is a possibility of threat to the security. Our protocol unanimously selects one TTP among all TTPs in the SMC architecture that owns the responsibility of all the computation in the system. This TTP is called the master TTP and it is different at different times. The procedure of selecting master TTP could be non-deterministic but it is made deterministic by randomization technique. This ensures that no single TTP controls the entire system all the times. At the same time, this also ensures that no TTP knows where the computation is taking place. This approach is having merit over the other one where only one TTP is given the responsibility to hold entire data of the system. Hence, the chances of corruption can be reduce to negligible when we randomize the selection of one TTP instead of having unknown TTP. Our algorithm works on the concepts of multiple TTP to provide zero-hacking for the entire system owing to the situation that it becomes almost impossible for any party to break the security. Formally it is achieved by imposing high computational complexity on the parties.

A Secured MultiParty Computational Protocol to Protect Cyber Space

“…So, it is difficult to disclose data through TTP. Also, the minimum number of TTP must be three (Mishra, 2008). After this, to minimize risk we use encryption before sending the data to the anonymizer (Mishra, 2007a).…”

“…The probability of reaching all the packets of any party i to any one anonymizer is Equation (1) (Mishra et al, 2008). X i is the total data of a party i.…”

Secure Multiparty Computation during Privacy Preserving Data Mining: Inscrutability Aided Protocol for Indian Healthcare Sector

“…This approach is having merit over the other one where only one TTP is given the responsibility to hold entire data of the system. Gaps in [20] are multiple TTPs are given the input but computation is performed by master TTP only. So even if this protocol defines multi TTP environment, but efficiency of TTP in the protocol is not utilized properly.…”

“…So even if this protocol defines multi TTP environment, but efficiency of TTP in the protocol is not utilized properly. The second gap in [20] is introducing packet layer. The responsibility of packet layer could be handled by parties itself and a virtual party can be used to make identity of party ambiguous.…”

Behavioral Identification of Trusted Third Party in Secure Multiparty Computing Protocol

“…[18] Presented a hybrid-secure MPC protocol that provides an optimal trade-off between IT robustness and computational privacy. [19] Presented a solution to the Secure Multi-party Computation (SMC) problem in the form of a protocol that ensures zero-hacking. The solution comprises of a protocol with several trusted third parties (TTPs) where there is a possibility of threat to the security.…”