The intention of this chapter is to support you in getting your own MISP instance up and running.
CIRCL maintains the image of a recent MISP virtual machine online.
This is a very easy out of the box solution, optimized for product evaluation and to support trainings hold by CIRCL staff.
The images is updated on a regular base. You should frequently re-visit the online resources to get the latest versions including bug fixes and new features.
The best place to get the latest version of the MISP virtual machine, as well as all the available training materials is the MISP training materials page on the CIRCL website.
If you do not remember the direct link to the MISP training materials here are the very easy to remember step you have to follow to reach the right place:
- Access the CIRCL homepage
- Navigate to the Training area
- Click MISP Malware Information Sharing Platform - Threat Sharing
- Follow the link to the Training materials freely available
Download the image of the virtual machine and validate the SHA512 fingerprint.
In VirtualBox use the "Import Appliance..." functionality to import the virtual machine.
The instructions in this manual covers VirtualBox only. If you prefer another virtualization solution like VMWare you can find some quick instruction on the MISP training materials page.
The MISP image is pre-configured to be reachable on the private IP address 192.168.56.50 by SSH. The GUI is reachable by http://192.168.56.50/.
- GUI User: firstname.lastname@example.org : Password1234
- GUI Admin: email@example.com : Password1234
- Shell/SSH: misp : Password1234
- MySQL User: misp : Password1234
- MySQL Root: root : Password1234
During life trainings we see in rare cases that some users could not reach the virtual machine over the virtual network.
Some investigations discover that this always happens with user whom already had VirtualBox in use before and had already one or more Host-only Adapter configured in advance.
The MISP image is pre-configured to use Host-only Adapter with the Name vboxnet0.
If this is already occupied by previous VirtualBox projects, try to attach the network adapter to the next available Host-only network.