MISP
/
misp-bump
mirror of https://github.com/MISP/misp-bump
2
0
Fork 0
Code Issues Releases Wiki Activity
142 Commits
3 Branches
0 Tags
51 MiB
Java 98.2%
Gradle 1.3%
Kotlin 0.5%
 
 
 
Go to file
Felix Prahl-Kamps 21af9e1307 add material preference switch to detail view 
update gradle
add animations
remove expandable card view
 		2019-10-04 17:42:16 +02:00
.idea cleanup 2019-08-22 16:58:50 +02:00
app add material preference switch to detail view 2019-10-04 17:42:16 +02:00
expandablecardview cleanup 2019-08-22 16:58:50 +02:00
gradle/wrapper cleanup 2019-08-22 16:58:50 +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 add badge 2019-08-23 17:30:21 +02:00
build.gradle add material preference switch to detail view 2019-10-04 17:42:16 +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 add material preference switch to detail view 2019-10-04 17:42:16 +02:00

README.md

MISPbump

Codacy Badge

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 admins profile and the linked organisation information will be downloaded automatically.
This information can be updated at any time in the profile screen.

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

The synchronisation process consists of 3 steps:

  1. Key Exchange
    To provide a secure chanel for data exchange, the first step is to generate a shared secret with Diffie–Hellman key exchange (Elliptic Curve).

    Public keys are exchanged via QR code.

  2. Synchronisation Information Exchange
    Contains the following information:

    • Own Organisation: Name, UUID, description, nationality, sector, type and contacts
    • Own User: Email
    • Own MISP instance: base URL
    • Generated: sync user authkey, sync user password
      (your partner will create a sync user with these credentials)

    The synchronisation information is encrypted with AES using the shared secret (from step 1).

    The sync process information will be saved securely on the device, that means the upload can be started any time in the future.

  3. Upload information to own 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