mirror of https://github.com/MISP/misp-bump
Felix PK
GitHub
commit
36a2b73d8c
90
README.md
90
README.md
|
|
@ -1,68 +1,48 @@
|
|||
# Screenshots
|
||||
# MISPbump
|
||||
Simple and secure synchronisation of MISP instances
|
||||
|
||||
## Login
|
||||
# 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](https://www.circl.lu/doc/misp/sharing/) is supported.
|
||||
|
||||
## Home
|
||||
# How does MISPbump work?
|
||||
First of all: MISP admins login by providing the base URL of their instance and their authkey (automationkey).
|
||||
|
||||
Actions: **Profile View** (Menubar) and **New Sync** (Floating Action Button)
|
||||
On a successfull login the admins 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.
|
||||
|
||||
## Profile
|
||||
Organisation information loaded automatically from your MISP instance
|
||||
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](https://en.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_exchange) ([Elliptic Curve](https://en.wikipedia.org/wiki/Elliptic-curve_Diffie%E2%80%93Hellman)).
|
||||
|
||||
Actions: **Delete and logout** (Menubar) and **Update Info** (Floating Action Button)
|
||||
Public keys are exchanged via QR code.
|
||||
|
||||
|
||||
1. **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)
|
||||
|
||||
## Sync
|
||||
The Synchronisation information is encrypted with AES using the shared secret (from step 1).
|
||||
|
||||
Core functionality of MISPbump.
|
||||
|
||||
**First Step:** Exchange keys to derive a shared secret
|
||||
|
||||
|
||||
|
||||
|
||||
**Second Step:** Exchange encrypted sync information
|
||||
|
||||
|
||||
|
||||
|
||||
## Sync information
|
||||
|
||||
After a successfull exchange an entry for this organisation will appear.
|
||||
|
||||
Actions: **Delete Sync information** (Menubar) and **Upload** (Floating Action Button in settings tab)
|
||||
|
||||
**Credentials:** With these credentials you will be able to log in on the other MISP instance (SyncUser)
|
||||
|
||||
|
||||
|
||||
**Settings:** These are typical settings which are also available from the MISP web interface.
|
||||
|
||||
|
||||
|
||||
## Upload
|
||||
|
||||
Shows the status of the upload to your MISP instance.
|
||||
If errors occure they will be displayed and the user can restart the process.
|
||||
|
||||
|
||||
|
||||
|
||||
## Home with successfull sync
|
||||
|
||||
|
||||
The sync process information will be saved securely on the device, that means the upload can be started any time in the future.
|
||||
|
||||
|
||||
# What does this app?
|
||||
1. Exchange public keys to make following communication private (via QR code)
|
||||
+ Diffie Hellman key exchange
|
||||
2. Exchange encrypted information needed to sync two MISP instances
|
||||
3. Upload information to MISP instance.
|
||||
1. **Upload information to own MISP instance**
|
||||
Uploading the information to the MISP instance is accomplished with MISP's REST API.
|
||||
|
||||
# MISPBump
|
||||
|
||||
Uploading consists of the following steps:
|
||||
1. Create organisation
|
||||
1. Create Sync User & add to organisation
|
||||
1. Create Sync Server & populate with information above
|
||||
|
||||
After that the two MISP instances are connected.
|
||||
|
||||
# Dependencies
|
||||
+ [Retrofit](https://github.com/square/retrofit)
|
||||
+ [ZXing](https://github.com/zxing/zxing)
|
||||
|
|
@ -0,0 +1,58 @@
|
|||
# Screenshots
|
||||
|
||||
## Login
|
||||
|
||||
|
||||
|
||||
## Home
|
||||
|
||||
Actions: **Profile View** (Menubar) and **New Sync** (Floating Action Button)
|
||||
|
||||
|
||||
|
||||
## Profile
|
||||
Organisation information loaded automatically from your MISP instance
|
||||
|
||||
Actions: **Delete and logout** (Menubar) and **Update Info** (Floating Action Button)
|
||||
|
||||
|
||||
|
||||
## Sync
|
||||
|
||||
Core functionality of MISPbump.
|
||||
|
||||
**First Step:** Exchange keys to derive a shared secret
|
||||
|
||||
|
||||
|
||||
|
||||
**Second Step:** Exchange encrypted sync information
|
||||
|
||||
|
||||
|
||||
|
||||
## Sync information
|
||||
|
||||
After a successfull exchange an entry for this organisation will appear.
|
||||
|
||||
Actions: **Delete Sync information** (Menubar) and **Upload** (Floating Action Button in settings tab)
|
||||
|
||||
**Credentials:** With these credentials you will be able to log in on the other MISP instance (SyncUser)
|
||||
|
||||
|
||||
|
||||
**Settings:** These are typical settings which are also available from the MISP web interface.
|
||||
|
||||
|
||||
|
||||
## Upload
|
||||
|
||||
Shows the status of the upload to your MISP instance.
|
||||
If errors occure they will be displayed and the user can restart the process.
|
||||
|
||||
|
||||
|
||||
|
||||
## Home with successfull sync
|
||||
|
||||
|
||||
Loading…
Reference in New Issue