Secure Multi-party Computation Audit Log for Data Leakage Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing secure multi-party computation algorithms are prone to data leakage due to incorrect or malicious implementations, making it difficult for users to audit the algorithms without disclosing the source code, especially when multiple parties participate in distributed computing networks.

Innovation Solution

A method and apparatus for secure multi-party computation that generates and transmits computing parameters, such as random numbers and ciphertext data, while creating an audit log with description information, allowing for privacy audits to determine potential data leakage risks without revealing the source code, enabling transparent and auditable secure multi-party computation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If secure multi-party computation algorithm is used to protect private data, then data security is improved, but the risk of data leakage due to incorrect or malicious implementation cannot be eliminated

Engineering Contradiction:
Improvedata securityVSAvoiddata leakage risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by generating audit logs that record computing parameters (such as random numbers and ciphertext data) before the actual secure multi-party computation is executed. This allows the computation process to be audited later to detect any incorrect or malicious implementations, thus preventing data leakage while maintaining the security benefits of the computation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by creating audit logs that capture computing parameters and making them available for verification. This feedback mechanism allows parties to verify that the secure multi-party computation algorithm was implemented correctly without revealing their private data, thereby detecting and preventing data leakage risks.

Inventive Principle:
Principle #23Feedback

2Reliability

If multiple parties independently develop their own secure multi-party computation software, then data security is improved, but the complexity of the system increases

Engineering Contradiction:
Improvedata securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary mechanism in the form of audit logs that record computing parameters. Instead of requiring multiple parties to independently develop and verify their own software implementations, the audit logs serve as a neutral intermediary that allows all parties to verify the correctness of the computation process without needing to trust each other's software, thus reducing system complexity while maintaining security.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If a single provider supplies secure multi-party computation software, then system complexity is reduced, but the risk of trust issues and data leakage increases

Engineering Contradiction:
Improvesystem complexityVSAvoidtrustworthiness
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent applies feedback by implementing audit log mechanisms that allow users to verify the trustworthiness of the provider's software. The audit logs record computing parameters such as random numbers and ciphertext data, enabling independent verification of the computation process. This feedback mechanism reduces trust issues while maintaining the simplicity of having a single software provider.

Inventive Principle:
Principle #23Feedback

4Reliability

If audit information is provided to verify algorithm transparency, then reliability is improved, but the amount of information that needs to be managed increases

Engineering Contradiction:
Improvealgorithm transparencyVSAvoidaudit information volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential computing parameters (such as random numbers and ciphertext data) needed for auditing and records them in audit logs. This selective extraction approach provides sufficient information for verifying algorithm transparency and detecting malicious implementations without requiring users to manage excessive amounts of data, thus balancing reliability with information manageability.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP3779751B1Multi-party security computing method and apparatus, and electronic device
Publication Date: 2023.05.10 ADVANCED NEW TECHNOLOGIES CO LTD
  • EP3779751B1 patent drawingFigure 1~2
  • EP3779751B1 patent drawingFigure 3
  • EP3779751B1 patent drawing

AI summary

A secure multi-party computation method, applicable to any computing node deployed in a distributed network. A plurality of computing nodes are deployed in the distributed network. The plurality of computing nodes jointly participate in a secure multi-party computation based on respectively held private data. The method includes: generating a computing parameter related to held private data based on a secure multi-party computation algorithm; transmitting the computing parameter to other computing nodes participating in the secure multi-party computation for the other computing nodes to perform the secure multi-party computation based on collected computing parameters transmitted by the computing nodes participating in the secure multi-party computation; and creating an audit log corresponding to the computing parameter, the audit log recording description information related to the computing parameter.