2016-02-17 18:40:55 +01:00
# MISP modules
2016-04-11 12:18:56 +02:00
[![Build Status ](https://travis-ci.org/MISP/misp-modules.svg?branch=master )](https://travis-ci.org/MISP/misp-modules)
2016-08-12 14:51:26 +02:00
[![Coverage Status ](https://coveralls.io/repos/github/MISP/misp-modules/badge.svg?branch=master )](https://coveralls.io/github/MISP/misp-modules?branch=master)
[![codecov ](https://codecov.io/gh/MISP/misp-modules/branch/master/graph/badge.svg )](https://codecov.io/gh/MISP/misp-modules)
2016-04-11 12:18:56 +02:00
2016-02-17 18:40:55 +01:00
MISP modules are autonomous modules that can be used for expansion and other services in [MISP ](https://github.com/MISP/MISP ).
The modules are written in Python 3 following a simple API interface. The objective is to ease the extensions of MISP functionalities
2016-06-23 12:51:13 +02:00
without modifying core components. The API is available via a simple REST API which is independent from MISP installation or configuration.
2016-02-17 18:40:55 +01:00
2016-03-21 23:10:48 +01:00
MISP modules support is included in MISP starting from version 2.4.28.
2016-02-17 18:40:55 +01:00
2017-01-07 10:45:22 +01:00
For more information: [Extending MISP with Python modules ](https://www.circl.lu/assets/files/misp-training/switch2016/2-misp-modules.pdf ) slides from MISP training.
2016-03-27 21:57:07 +02:00
2016-02-17 18:40:55 +01:00
## Existing MISP modules
2016-08-12 13:48:02 +02:00
### Expansion modules
2016-06-23 12:51:13 +02:00
* [ASN History ](misp_modules/modules/expansion/asn_history.py ) - a hover and expansion module to expand an AS number with the ASN description and its history.
2016-06-24 02:15:25 +02:00
* [CIRCL Passive SSL ](misp_modules/modules/expansion/circl_passivessl.py ) - a hover and expansion module to expand IP addresses with the X.509 certificate seen.
2016-06-23 12:51:13 +02:00
* [CIRCL Passive DNS ](misp_modules/modules/expansion/circl_passivedns.py ) - a hover and expansion module to expand hostname and IP addresses with passive DNS information.
* [CVE ](misp_modules/modules/expansion/cve.py ) - a hover module to give more information about a vulnerability (CVE).
* [DNS ](misp_modules/modules/expansion/dns.py ) - a simple module to resolve MISP attributes like hostname and domain to expand IP addresses attributes.
2016-12-02 17:12:21 +01:00
* [DomainTools ](misp_modules/modules/expansion/domaintools.py ) - a hover and expansion module to get information from [DomainTools ](http://www.domaintools.com/ ) whois.
2016-06-23 12:51:13 +02:00
* [EUPI ](misp_modules/modules/expansion/eupi.py ) - a hover and expansion module to get information about an URL from the [Phishing Initiative project ](https://phishing-initiative.eu/?lang=en ).
2016-12-17 15:06:08 +01:00
* [GeoIP ](misp_modules/modules/expansion/geoip_country.py ) - a hover and expansion module to get GeoIP information from geolite/maxmind.
2016-06-23 12:51:13 +02:00
* [IPASN ](misp_modules/modules/expansion/ipasn.py ) - a hover and expansion to get the BGP ASN of an IP address.
2017-03-08 17:37:28 +01:00
* [iprep ](misp-modules/modules/expansion/iprep.py ) - an expansion module to get IP reputation from packetmail.net.
2016-06-23 12:51:13 +02:00
* [passivetotal ](misp_modules/modules/expansion/passivetotal.py ) - a [passivetotal ](https://www.passivetotal.org/ ) module that queries a number of different PassiveTotal datasets.
2017-03-08 17:37:28 +01:00
* [shodan ](misp_modules/modules/expansion/shodan.py ) - a minimal [shodan ](https://www.shodan.io/ ) expansion module.
2016-06-24 02:15:25 +02:00
* [sourcecache ](misp_modules/modules/expansion/sourcecache.py ) - a module to cache a specific link from a MISP instance.
2017-03-08 17:25:11 +01:00
* [threatminer ](misp_modules/modules/expansion/threatminer.py ) - an expansion module to expand from [ThreatMiner ](https://www.threatminer.org/ ).
2016-08-17 10:33:49 +02:00
* [countrycode ](misp_modules/modules/expansion/countrycode.py ) - a hover module to tell you what country a URL belongs to.
2016-08-17 10:46:13 +02:00
* [virustotal ](misp_modules/modules/expansion/virustotal.py ) - an expansion module to pull known resolutions and malware samples related with an IP/Domain from virusTotal (this modules require a VirusTotal private API key)
2017-03-08 17:37:28 +01:00
* [wikidata ](misp_modules/modules/expansion/wiki.py ) - a [wikidata ](https://www.wikidata.org ) expansion module.
* [xforce ](misp_modules/modules/expansion/xforceexchange.py ) - an IBM X-Force Exchange expansion module.
2016-02-17 18:40:55 +01:00
2016-09-01 20:30:23 +02:00
### Export modules
2016-09-01 20:35:18 +02:00
* [CEF ](misp_modules/modules/export_mod/cef_export.py ) module to export Common Event Format (CEF).
2017-02-24 15:09:18 +01:00
* [Lite Export ](/misp-modules/blob/master/misp_modules/modules/export_mod/liteexport.py ) module to export a lite event.
2016-09-01 20:30:23 +02:00
2016-08-12 13:48:02 +02:00
### Import modules
2017-01-07 10:45:22 +01:00
* [Cuckoo JSON ](misp_modules/modules/import_mod/cuckooimport.py ) Cuckoo JSON import.
2016-08-12 13:48:02 +02:00
* [OCR ](misp_modules/modules/import_mod/ocr.py ) Optical Character Recognition (OCR) module for MISP to import attributes from images, scan or faxes.
2017-02-27 14:10:11 +01:00
* [OpenIOC ](misp_modules/modules/import_mod/openiocimport.py ) OpenIOC import based on PyMISP library.
2017-01-07 10:45:22 +01:00
* [stiximport ](misp_modules/modules/import_mod/stiximport.py ) - An import module to process STIX xml/json.
2016-10-22 23:13:20 +02:00
* [Email Import ](misp_modules/modules/import_mod/email_import.py ) Email import module for MISP to import basic metadata.
2017-01-07 10:45:22 +01:00
* [VMRay ](misp_modules/modules/import_mod/vmray_import.py ) - An import module to process VMRay export.
2016-08-12 13:48:02 +02:00
2016-03-24 16:52:53 +01:00
## How to install and start MISP modules?
~~~~bash
2016-12-20 16:14:08 +01:00
sudo apt-get install python3-dev python3-pip libpq5 libjpeg-dev
2016-07-22 11:56:31 +02:00
cd /usr/local/src/
sudo git clone https://github.com/MISP/misp-modules.git
2016-03-24 16:52:53 +01:00
cd misp-modules
2016-11-29 13:49:00 +01:00
sudo pip3 install -I -r REQUIREMENTS
sudo pip3 install -I .
2016-09-02 11:15:39 +02:00
sudo vi /etc/rc.local, add this line: `sudo -u www-data misp-modules -s &`
2017-02-21 11:27:59 +01:00
misp-modules #to start the modules
2016-03-24 16:52:53 +01:00
~~~~
2016-02-17 18:40:55 +01:00
## How to add your own MISP modules?
2016-10-22 23:13:20 +02:00
Create your module in [misp_modules/modules/expansion/ ](misp_modules/modules/expansion/ ), [misp_modules/modules/export_mod/ ](misp_modules/modules/export_mod/ ), or [misp_modules/modules/import_mod/ ](misp_modules/modules/import_mod/ ). The module should have at minimum three functions:
2016-02-17 18:40:55 +01:00
2016-03-09 07:49:46 +01:00
* **introspection** function that returns a dict of the supported attributes (input and output) by your expansion module.
2016-02-17 18:40:55 +01:00
* **handler** function which accepts a JSON document to expand the values and return a dictionary of the expanded values.
2016-03-16 07:57:37 +01:00
* **version** function that returns a dict with the version and the associated meta-data including potential configurations required of the module.
2016-02-17 18:40:55 +01:00
2016-02-29 21:49:42 +01:00
Don't forget to return an error key and value if an error is raised to propagate it to the MISP user-interface.
2016-10-22 23:13:20 +02:00
~~~python
...
# Checking for required value
if not request.get('ip-src'):
# Return an error message
return {'error': "A source IP is required"}
...
~~~
### introspection
The function that returns a dict of the supported attributes (input and output) by your expansion module.
~~~python
mispattributes = {'input': ['link', 'url'],
'output': ['attachment', 'malware-sample']}
def introspection():
return mispattributes
~~~
### version
The function that returns a dict with the version and the associated meta-data including potential configurations required of the module.
2016-12-26 22:55:54 +01:00
### Additional Configuration Values
2016-10-22 23:13:20 +02:00
If your module requires additional configuration (to be exposed via the MISP user-interface), you can define those in the moduleconfig value returned by the version function.
~~~python
# config fields that your code expects from the site admin
moduleconfig = ["apikey", "event_limit"]
def version():
moduleinfo['config'] = moduleconfig
return moduleinfo
~~~
2016-12-26 22:55:54 +01:00
2016-10-22 23:13:20 +02:00
When you do this a config array is added to the meta-data output containing all the potential configuration values:
2016-03-03 07:18:51 +01:00
2016-03-16 07:57:37 +01:00
~~~
"meta": {
"description": "PassiveTotal expansion service to expand values with multiple Passive DNS sources",
"config": [
"username",
"password"
],
2016-03-20 19:54:32 +01:00
"module-type": [
"expansion",
"hover"
],
2016-03-16 07:57:37 +01:00
...
~~~
2016-03-03 07:18:51 +01:00
2016-12-26 22:55:54 +01:00
If you want to use the configuration values set in the web interface they are stored in the key `config` in the JSON object passed to the handler.
~~~
def handler(q=False):
# Check if we were given a configuration
config = q.get("config", {})
# Find out if there is a username field
username = config.get("username", None)
~~~
2016-10-22 23:13:20 +02:00
### handler
The function which accepts a JSON document to expand the values and return a dictionary of the expanded values.
~~~python
def handler(q=False):
"Fully functional rot-13 encoder"
if q is False:
return False
request = json.loads(q)
src = request.get('ip-src')
if src is None:
# Return an error message
return {'error': "A source IP is required"}
else:
return {'results':
codecs.encode(src, "rot-13")}
~~~
2016-12-26 22:55:54 +01:00
### Returning Binary Data
If you want to return a file or other data you need to add a data attribute.
~~~python
{"results": {"values": "filename.txt",
"types": "attachment",
"data" : base64.b64encode(< ByteIO > ) # base64 encode your data first
"comment": "This is an attachment"}}
~~~
If the binary file is malware you can use 'malware-sample' as the type. If you do this the malware sample will be automatically zipped and password protected ('infected') after being uploaded.
~~~python
{"results": {"values": "filename.txt",
"types": "malware-sample",
"data" : base64.b64encode(< ByteIO > ) # base64 encode your data first
"comment": "This is an attachment"}}
~~~
2016-12-26 23:09:21 +01:00
[To learn more about how data attributes are processed you can read the processing code here. ](https://github.com/MISP/PyMISP/blob/4f230c9299ad9d2d1c851148c629b61a94f3f117/pymisp/mispevent.py#L185-L200 )
2016-12-26 22:55:54 +01:00
2016-10-22 23:13:20 +02:00
2016-03-20 19:54:32 +01:00
### Module type
2016-12-26 23:17:20 +01:00
A MISP module can be of four types:
2016-03-20 19:54:32 +01:00
- **expansion** - service related to an attribute that can be used to extend and update an existing event.
- **hover** - service related to an attribute to provide additional information to the users without updating the event.
2016-10-22 23:13:20 +02:00
- **import** - service related to importing and parsing an external object that can be used to extend an existing event.
2016-12-26 23:17:20 +01:00
- **export** - service related to exporting an object, event, or data.
2016-03-20 19:54:32 +01:00
module-type is an array where the list of supported types can be added.
2016-02-17 18:40:55 +01:00
## Testing your modules?
MISP uses the **modules** function to discover the available MISP modules and their supported MISP attributes:
~~~
% curl -s http://127.0.0.1:6666/modules | jq .
[
{
2016-03-16 07:57:37 +01:00
"name": "passivetotal",
"type": "expansion",
2016-02-24 00:55:14 +01:00
"mispattributes": {
2016-03-09 07:25:54 +01:00
"input": [
"hostname",
"domain",
2016-02-24 00:55:14 +01:00
"ip-src",
2016-03-16 07:57:37 +01:00
"ip-dst"
2016-02-24 00:55:14 +01:00
],
2016-03-09 07:25:54 +01:00
"output": [
"ip-src",
"ip-dst",
"hostname",
"domain"
]
},
2016-03-09 08:59:12 +01:00
"meta": {
2016-03-16 07:57:37 +01:00
"description": "PassiveTotal expansion service to expand values with multiple Passive DNS sources",
"config": [
"username",
"password"
],
"author": "Alexandre Dulaunoy",
"version": "0.1"
}
},
{
"name": "sourcecache",
"type": "expansion",
"mispattributes": {
"input": [
"link"
],
"output": [
"link"
]
2016-03-09 08:59:12 +01:00
},
2016-03-16 07:57:37 +01:00
"meta": {
"description": "Module to cache web pages of analysis reports, OSINT sources. The module returns a link of the cached page.",
"author": "Alexandre Dulaunoy",
"version": "0.1"
}
2016-03-09 07:25:54 +01:00
},
{
2016-03-16 07:57:37 +01:00
"name": "dns",
"type": "expansion",
2016-03-09 07:25:54 +01:00
"mispattributes": {
2016-02-24 00:55:14 +01:00
"input": [
"hostname",
"domain"
2016-03-09 07:25:54 +01:00
],
"output": [
"ip-src",
"ip-dst"
2016-02-24 00:55:14 +01:00
]
},
2016-03-09 07:25:54 +01:00
"meta": {
2016-03-16 07:57:37 +01:00
"description": "Simple DNS expansion service to resolve IP address from MISP attributes",
"author": "Alexandre Dulaunoy",
"version": "0.1"
}
2016-02-17 18:40:55 +01:00
}
]
2016-03-16 07:57:37 +01:00
2016-02-17 18:40:55 +01:00
~~~
The MISP module service returns the available modules in a JSON array containing each module name along with their supported input attributes.
Based on this information, a query can be built in a JSON format and saved as body.json:
2016-03-16 07:57:37 +01:00
~~~json
{
"hostname": "www.foo.be",
"module": "dns"
}
~~~
Then you can POST this JSON format query towards the MISP object server:
2016-10-22 23:13:20 +02:00
~~~bash
2016-03-16 07:57:37 +01:00
curl -s http://127.0.0.1:6666/query -H "Content-Type: application/json" --data @body .json -X POST
~~~
The module should output the following JSON:
2016-02-17 18:40:55 +01:00
~~~json
2016-02-24 00:23:26 +01:00
{
"results": [
{
"types": [
"ip-src",
"ip-dst"
],
"values": [
"188.65.217.78"
]
}
]
}
2016-02-17 18:40:55 +01:00
~~~
2016-07-26 12:13:49 +02:00
It is also possible to restrict the category options of the resolved attributes by passing a list of categories along (optional):
~~~json
{
"results": [
{
"types": [
"ip-src",
"ip-dst"
],
"values": [
"188.65.217.78"
],
"categories": [
"Network activity",
"Payload delivery"
]
}
]
}
~~~
For both the type and the category lists, the first item in the list will be the default setting on the interface.
2016-10-22 23:13:20 +02:00
### Enable your module in the web interface
For a module to be activated in the MISP web interface it must be enabled in the "Plugin Settings.
Go to "Administration > Server Settings" in the top menu
- Go to "Plugin Settings" in the top "tab menu bar"
- Click on the name of the type of module you have created to expand the list of plugins to show your module.
- Find the name of your plugin's "enabled" value in the Setting Column.
"Plugin.[MODULE NAME]_enabled"
- Double click on its "Value" column
~~~
Priority Setting Value Description Error Message
Recommended Plugin.Import_ocr_enabled false Enable or disable the ocr module. Value not set.
~~~
- Use the drop-down to set the enabled value to 'true'
~~~
Priority Setting Value Description Error Message
Recommended Plugin.Import_ocr_enabled true Enable or disable the ocr module. Value not set.
~~~
### Set any other required settings for your module
In this same menu set any other plugin settings that are required for testing.
2017-02-24 15:09:18 +01:00
## Install misp-module on an offline instance.
First, you need to grab all necessery packages for example like this :
Use pip wheel to create an archive
~~~
mkdir misp-modules-offline
pip3 wheel -r REQUIREMENTS shodan --wheel-dir=./misp-modules-offline
tar -cjvf misp-module-bundeled.tar.bz2 ./misp-modules-offline/*
~~~
On offline machine :
~~~
mkdir misp-modules-bundle
tar xvf misp-module-bundeled.tar.bz2 -C misp-modules-bundle
cd misp-modules-bundle
ls -1|while read line; do sudo pip3 install --force-reinstall --ignore-installed --upgrade --no-index --no-deps ${line};done
~~~
Next you can follow standard install procedure.
2016-10-22 23:13:20 +02:00
2016-03-09 07:49:46 +01:00
## How to contribute your own module?
Fork the project, add your module, test it and make a pull-request. Modules can be also private as you can add a module in your own MISP installation.
2016-10-22 23:13:20 +02:00
## Tips for developers creating modules
Download a pre-built virtual image from the [MISP training materials ](https://www.circl.lu/services/misp-training-materials/ ).
- Create a Host-Only adapter in VirtualBox
2016-12-26 23:09:21 +01:00
- Set your Misp OVA to that Host-Only adapter
2016-10-22 23:13:20 +02:00
- Start the virtual machine
2016-12-26 23:09:21 +01:00
- Get the IP address of the virutal machine
- SSH into the machine (Login info on training page)
2016-10-22 23:13:20 +02:00
- Go into the misp-modules directory
~~~bash
cd /usr/local/src/misp-modules
~~~
Set the git repo to your fork and checkout your development branch. If you SSH'ed in as the misp user you will have to use sudo.
~~~bash
sudo git remote set-url origin https://github.com/YourRepo/misp-modules.git
sudo git pull
sudo git checkout MyModBranch
~~~
Remove the contents of the build directory and re-install misp-modules.
~~~python
sudo rm -fr build/*
sudo pip3 install --upgrade .
~~~
SSH in with a different terminal and run `misp-modules` with debugging enabled.
~~~python
2016-12-26 23:33:10 +01:00
sudo killall misp-modules
2016-10-22 23:13:20 +02:00
misp-modules -d
~~~
In your original terminal you can now run your tests manually and see any errors that arrive
~~~bash
cd tests/
curl -s http://127.0.0.1:6666/query -H "Content-Type: application/json" --data @MY_TEST_FILE .json -X POST
cd ../
~~~