remove leftovers of expandablecardview
|4 years ago|
|.idea||4 years ago|
|app||4 years ago|
|gradle/wrapper||4 years ago|
|poster||4 years ago|
|screenshots||4 years ago|
|.gitignore||4 years ago|
|README.md||4 years ago|
|build.gradle||4 years ago|
|gradle.properties||4 years ago|
|gradlew||4 years ago|
|gradlew.bat||4 years ago|
|settings.gradle||4 years ago|
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 that only use case 1 from the documentation is supported.
How does MISPbump work?
MISP admins log in by providing the base URL of their instance and their authkey.
After a successfull login the admin's profile and the linked organisation information will be downloaded.
In the main screen you can start a synchronisation process by pressing the dedicated button.
The synchronisation process consists of 3 steps:
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.
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 for you)
The synchronisation information is encrypted with AES using the shared secret (from step 1).
The synchronisation process information will be saved securely on the device.
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:
- Create organisation
- Create sync user & add to organisation
- Create sync server & populate with information above
After that the two MISP instances are able to share Events based on their permissions.