MISP Docker (XME edition)
 
 
 
 
Go to file
Jason Kendall 33d55638f9 Fix docker image location 2020-02-24 20:23:37 -05:00
modules Add faup to modules see #26 and #30 2020-02-24 20:14:24 -05:00
server Add procps for ps and kill 2020-02-24 20:14:47 -05:00
server-configs
.env
.gitignore
.travis.yml
LICENSE
README.md Fix docker image location 2020-02-24 20:23:37 -05:00
docker-compose.yml

README.md

CoolAcid's MISP Docker images

Codacy Badge CodeFactor Build Status

A (nearly) production ready Dockered MISP

This is based on some of the work from the DSCO docker build, nearly all of the details have been rewritten.

  • Components are split out where possible, currently this is only the MISP modules
  • Over writable configuration files
  • Allows volumes for file store
  • Cron job runs updates, pushes, and pulls - Logs go to docker logs
  • Docker-Compose uses off the shelf images for Redis and MySQL
  • Images directly from docker hub, no build required
  • Slimmed down images by using build stages and slim parent image, removes unnecessary files from images

Docker Tags

Docker hub builds the images automatically based on git tags. I try and tag using the following details

v[MISP Version][Our build version]

  • MISP version is the MISP tag we're building
  • Our build version is the iteration for our changes with the same MISP version

Getting Started

Development/Test

  • Grab the docker-compose.yml file and the server-configs directory

  • Optional] Copy the "default" configs removing "default" and edit the files in `server-configs`
    -   Note: A dry run without this step will try and make sane DEV configs
    
    
  • docker-compose up

  • Login to https://localhost

    • User: admin@admin.test
    • Password: admin
  • Profit

Using the image for development

Once you have the docker container up you can access the container by running docker-compose exec misp /bin/bash. This will provide you with a root shell. You can use apt update and then install any tools you wish to use. Finally, copy any changes you make outside of the container for commiting to your branch. git diff -- [dir with changes] could be used to reduce the number of changes in a patch file, however, becareful when using the git diff command.

Production

  • Use docker-compose, or some other config management tool

  • Directory volume mount SSL Certs ./ssl: /etc/ssl

    • Certificate File: cert.pem
    • Certificate Key File: key.pem
  • Directory volume mount and create configs: /var/www/MISP/app/Config/

  • Additional directory volume mounts:

    • /var/www/MISP/app/files
    • /var/www/MISP/.gnupg
    • /var/www/MISP/.smime

Image file sizes

  • Core server(Saved: 2.5GB)

    • Original Image: 3.17GB
    • First attempt: 2.24GB
    • Remove chown: 1.56GB
    • PreBuild python modules, and only pull submodules we need: 800MB
    • PreBuild PHP modules: 664MB
  • Modules (Saved: 640MB)

    • Original: 1.36GB
    • Pre-build modules: 750MB