Data

Tools

Indexes

Applications

Experiments

Open Source Science

tno.mpc.protocols.risk-propagation

TNO PET Lab - secure Multi-Party Computation (MPC) - Protocols - Secure Risk Propagation

https://github.com/tno-mpc/protocols.risk_propagation

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • ○
    CITATION.cff file
  • ✓
    codemeta.json file
    Found codemeta.json file
  • ✓
    .zenodo.json file
    Found .zenodo.json file
  • ○
    DOI references
  • ○
    Academic publication links
  • ○
    Academic email domains
  • ○
    Institutional organization owner
  • ○
    JOSS paper metadata
  • ○
    Scientific vocabulary similarity
    Low similarity (11.9%) to scientific vocabulary

Keywords

anti-money-laundering distributed-key-generation follow-the-money homomorphic-encryption mpc mpc-lab multi-party-computation paillier paillier-cryptosystem pet-lab risk-propagation tno
Last synced: 6 months ago · JSON representation

Repository

TNO PET Lab - secure Multi-Party Computation (MPC) - Protocols - Secure Risk Propagation

Basic Info
Statistics
  • Stars: 9
  • Watchers: 4
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Topics
anti-money-laundering distributed-key-generation follow-the-money homomorphic-encryption mpc mpc-lab multi-party-computation paillier paillier-cryptosystem pet-lab risk-propagation tno
Created almost 5 years ago · Last pushed 11 months ago
Metadata Files
Readme License Citation

README.md

TNO PET Lab - secure Multi-Party Computation (MPC) - Protocols - Risk Propagation

Secure Risk Propagation initially developed within the MPC4AML project.

PET Lab

The TNO PET Lab consists of generic software components, procedures, and functionalities developed and maintained on a regular basis to facilitate and aid in the development of PET solutions. The lab is a cross-project initiative allowing us to integrate and reuse previously developed PET functionalities to boost the development of new protocols and solutions.

The package tno.mpc.protocols.risk_propagation is part of the TNO Python Toolbox.

Limitations in (end-)use: the content of this software package may solely be used for applications that comply with international export control laws.
This implementation of cryptographic software has not been audited. Use at your own risk.

Documentation

Documentation of the tno.mpc.protocols.risk_propagation package can be found here.

Install

Easily install the tno.mpc.protocols.risk_propagation package using pip:

console $ python -m pip install tno.mpc.protocols.risk_propagation

Note: If you are cloning the repository and wish to edit the source code, be sure to install the package in editable mode:

console $ python -m pip install -e 'tno.mpc.protocols.risk_propagation'

If you wish to run the tests you can use:

console $ python -m pip install 'tno.mpc.protocols.risk_propagation[tests]'

Note: A significant performance improvement can be achieved by installing the GMPY2 library.

console $ python -m pip install 'tno.mpc.protocols.risk_propagation[gmpy]'

Protocol description

Risk propagation is an algorithm that propagates risk scores through a (transaction) network. Using distributed partial homomorphic encryption, the secure risk propagation implementation performs this algorithm on a network that is distributed among multiple parties. As input of the algorithm, every party possesses a list of nodes (i.e. bank accounts) with initial risk scores and has a list of transactions (weighted, directed edges) from and to its bank accounts. Using encrypted incoming risk scores scores from other parties, every party can securely update its risk scores using the formula for risk propagation. After a set number of iterations, the eventual risk scores are revealed to the parties that own the accounts, using the distributed private key.

In ERCIM News 126 (July 2021), we presented a more elaborate protocol descriptions. Figure 1 demonstrates a high-level overview of the idea behind the protocol. Figure 2 visualizes the decentralized approach.

Risk Propagation High Level Overview
**Figure 1.** _We consider a three-bank scenario (Orange, Blue, and Purple). In this scenario the first (left) account at bank Orange is classified as high risk (due to e.g., large cash deposits) by bank Orange. This account wishes to launder its resources. To stay under the radar, the resources are funnelled through multiple accounts, at various banks, before arriving at their eventual destination, e.g., the account at bank Purple (right). To detect money laundering, we wish to follow (propagate) the risky money and classify the endpoint as high risk too. Full (global) knowledge of the network enables us to propagate the risk. However, how can we achieve something similar when there is only partial (local) knowledge of the entire network available? This is where MPC comes into play._
Risk Propagation Decentralized Approach
**Figure 2.** _In our approach, the data is analyzed in a decentralized manner. From left-to-right, we visualize encryption, propagation and decryption. The parties encrypt their data using the additive homomorphic encryption scheme, no communication takes place. Once the data is encrypted locally, the distributed propagation (computation) over the encrypted data takes place. During this computation the data remains encrypted, the parties communicate intermediate (encrypted) results, and there is no central party. During the decryption phase, we need to decrypt the encrypted values with every party's key. We view the decryption from the green party's perspective. The lock on the risk scores belonging to the green party is opened part-by-part and the final opening happens by the green party. This ensures that only the green party gets to see the decrypted, propagated risk scores of his own bank accounts._

Usage

The protocol is symmetric. For determining a secure set of parameters for the distributed keygen we refer to protocols.distributed_keygen.

Input

For the input two numpy arrays are expected. The structure and types are given in the tables below:

Input of the accounts:

| id | risk_score | | ------ | ---------- | | string | float 64 |

Input of the transactions:

| idsource | banksource | iddestination | bankdestination | amount | | --------- | ----------- | -------------- | ---------------- | ------ | | string | string | string | string | int32 |

A string is expected to consist out of at most 100 unicode characters.

For an example of how to setup and run the protocol, see scripts/example_usage.py.

Owner

  • Name: TNO - MPC Lab
  • Login: TNO-MPC
  • Kind: organization
  • Email: mpclab@tno.nl
  • Location: Anna van Buerenplein 1, 2595 DA Den Haag, The Netherlands

TNO - MPC Lab

GitHub Events

Total
  • Issues event: 2
  • Watch event: 1
  • Issue comment event: 1
  • Push event: 2
Last Year
  • Issues event: 2
  • Watch event: 1
  • Issue comment event: 1
  • Push event: 2

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 1
  • Total pull requests: 0
  • Average time to close issues: 16 days
  • Average time to close pull requests: N/A
  • Total issue authors: 1
  • Total pull request authors: 0
  • Average comments per issue: 1.0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 1
  • Pull requests: 0
  • Average time to close issues: 16 days
  • Average time to close pull requests: N/A
  • Issue authors: 1
  • Pull request authors: 0
  • Average comments per issue: 1.0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
View more stats
Top Authors
Issue Authors
  • franciscobecerra97 (1)
Pull Request Authors
Top Labels
Issue Labels
Pull Request Labels

Packages

  • Total packages: 1
  • Total downloads:
    • pypi 85 last-month
  • Total dependent packages: 0
  • Total dependent repositories: 0
  • Total versions: 8
  • Total maintainers: 1
pypi.org: tno.mpc.protocols.risk-propagation

Secure risk propagation using distributed Paillier

  • Versions: 8
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Downloads: 85 Last month
Rankings
Dependent packages count: 6.6%
Average: 20.9%
Forks count: 23.2%
Stargazers count: 23.3%
Dependent repos count: 30.6%
Maintainers (1)
PETLab
Last synced: 6 months ago

Dependencies

pyproject.toml pypi
  • numpy >=1.24,<3
  • tno.mpc.communication ~=4.8,>=4.8.1
  • tno.mpc.encryption_schemes.paillier *
  • tno.mpc.protocols.distributed_keygen ~=4.0