Go to file
Felix Prahl-Kamps dd374300f1 improve readme 2019-07-15 18:01:42 +02:00
.idea improve exchange activity layout and functionality 2019-07-14 19:17:32 +02:00
app fix sync information encryption 2019-07-15 17:46:37 +02:00
gradle/wrapper initial commit 2019-05-27 16:06:07 +02:00
poster Upload poster englisch 2019-03-12 08:19:29 +01:00
screenshots improve readme 2019-07-15 18:01:42 +02:00
.gitignore .gitignore fix 2019-05-27 16:19:37 +02:00
README.md improve readme 2019-07-15 18:01:42 +02:00
_config.yml Set theme jekyll-theme-minimal 2019-07-05 00:04:48 +02:00
build.gradle add new exchange activity 2019-07-11 16:22:58 +02:00
gradle.properties done convert to androidx 2019-06-17 09:49:09 +02:00
gradlew .gitignore fix 2019-05-27 16:19:37 +02:00
gradlew.bat .gitignore fix 2019-05-27 16:19:37 +02:00
settings.gradle Completely ported to IntelliJ Idea 2018-06-10 16:23:33 +02:00

README.md

MISPbump

Simple and secure synchronisation of MISP instances

What is MISPbump?

With MISPbump admins can easily synchronize MISP instances by exchanging relevant information via encrypted QR codes.

Note: only use case 1 from the documentation is supported.

How does MISPbump work?

First of all: MISP admins login by providing the base URL of their instance and their authkey (automationkey).

On a successfull login the users profile and the linked organisation information will be downloaded automatically. This information can be updated at any time from the profile view.

From the main screen you can start a synchronisation process by pressing the dedicated button.

The synchronisation process consists of 3 steps:

  1. Key Exchange (unencrypted QR code)
  2. Synchronisation Information Exchange (with shared secret encrypted QR code)
  3. Upload information to own MISP instance

1. Key Exchange

DiffieHellman key exchange (Elliptic Curve), where the public part is exchanged via a QR code. The result is a shared secret which will be used to encrypt the information passed via QR code in step 2.

2. Synchronisation Information Exchange

Local information like Organisation name, UUID, description and User information is encrypted with a from step 1 derived key. The information can now be securely exchanged via QR code.

3. Upload information to MISP instance

Uploading the information to the MISP instance is accomplished with MISP's REST API.

Uploading consists of the following steps:

  1. Create organisation
  2. Create Sync User & add to organisation
  3. Create Sync Server & populate with information above

After that the two MISP instances are connected.

Dependencies