20 KiB
MISP modules documentation
Expansion Modules
asn_history
Query an ASN description history service (https://github.com/CIRCL/ASN-Description-History.git).
- requirements:
asnhistory
btc
An expansion hover module to get a blockchain balance from a BTC address in MISP.
circl_passivedns
Module to access CIRCL Passive DNS.
circl_passivessl
Modules to access CIRCL Passive SSL.
countrycode
Module to expand country codes.
crowdstrike_falcon
Module to query Crowdstrike Falcon.
cve
An expansion hover module to expand information about CVE id.
dbl_spamhaus
Module to check Spamhaus DBL for a domain name.
dns
A simple DNS expansion service to resolve IP address from MISP attributes.
domaintools
DomainTools MISP expansion module.
eupi
A module to query the Phishing Initiative service (https://phishing-initiative.lu).
farsight_passivedns
Module to access Farsight DNSDB Passive DNS.
geoip_country
Module to query a local copy of Maxminds Geolite database.
intelmq_eventdb
Module to access intelmqs eventdb.
ipasn
Module to query an IP ASN history service (https://github.com/CIRCL/IP-ASN-history.git).
iprep
Module to query IPRep data for IP addresses.
onyphe
Module to process a query on Onyphe.
onyphe_full
Module to process a full query on Onyphe.
otx
Module to get information from AlienVault OTX.
passivetotal
The PassiveTotal MISP expansion module brings the datasets derived from Internet scanning directly into your MISP instance. This module supports passive DNS, historic SSL, WHOIS, and host attributes. In order to use the module, you must have a valid PassiveTotal account username and API key. Registration is free and can be done by visiting https://www.passivetotal.org/register
rbl
Module to check an IPv4 address against known RBLs.
- requirements:
dnspython3
reversedns
Simple Reverse DNS expansion service to resolve reverse DNS from MISP attributes.
shodan
Module to query on Shodan.
sourcecache
Module to cache web pages of analysis reports, OSINT sources. The module returns a link of the cached page.
threatcrowd
Module to get information from ThreatCrowd.
threatminer
Module to get information from ThreatMiner.
virustotal
Module to get information from virustotal.
vmray_submit
Module to submit a sample to VMRay.
vulndb
Module to query VulnDB (RiskBasedSecurity.com).
whois
Module to query a local instance of uwhois (https://github.com/rafiot/uwhoisd).
- requirements:
uwhois
wiki
An expansion hover module to extract information from Wikidata to have additional information about particular term for analysis.
xforceexchange
An expansion module for IBM X-Force Exchange.
yara_query
An expansion & hover module to translate any hash attribute into a yara rule.
- features:
The module takes a hash attribute (md5, sha1, sha256, imphash) as input, and is returning a YARA rule from it. This YARA rule is also validated using the same method as in 'yara_syntax_validator' module. Both hover and expansion functionalities are supported with this module, where the hover part is displaying the resulting YARA rule and the expansion part allows you to add the rule as a new attribute, as usual with expansion modules.
- input:
MISP Hash attribute (md5, sha1, sha256, imphash, or any of the composite attribute with filename and one of the previous hash type).
- output:
YARA rule.
- references:
https://virustotal.github.io/yara/, https://github.com/virustotal/yara-python
- requirements:
yara-python python library
yara_syntax_validator
An expansion hover module to perform a syntax check on if yara rules are valid or not.
- features:
This modules simply takes a YARA rule as input, and checks its syntax. It returns then a confirmation if the syntax is valid, otherwise the syntax error is displayed.
- input:
YARA rule attribute.
- output:
Text to inform users if their rule is valid.
- references:
- requirements:
yara_python python library
Export Modules
cef_export
Module to export a MISP event in CEF format.
- features:
The module takes a MISP event in input, to look every attribute. Each attribute matching with some predefined types is then exported in Common Event Format. Thus, there is no particular feature concerning MISP Events since any event can be exported. However, 4 configuration parameters recognized by CEF format are required and should be provided by users before exporting data: the device vendor, product and version, as well as the default severity of data.
- input:
MISP Event attributes
- output:
Common Event Format file
- references:
goamlexport
This module is used to export MISP events containing transaction objects into GoAML format.
- features:
The module works as long as there is at least one transaction object in the Event.
Then in order to have a valid GoAML document, please follow these guidelines:
- For each transaction object, use either a bank-account, person, or legal-entity object to describe the origin of the transaction, and again one of them to describe the target of the transaction.
- Create an object reference for both origin and target objects of the transaction.
- A bank-account object needs a signatory, which is a person object, put as object reference of the bank-account.
- A person can have an address, which is a geolocation object, put as object reference of the person.
Supported relation types for object references that are recommended for each object are the folowing:
- transaction:
- 'from', 'from_my_client': Origin of the transaction - at least one of them is required.
- 'to', 'to_my_client': Target of the transaction - at least one of them is required.
- 'address': Location of the transaction - optional.
- bank-account:
- 'signatory': Signatory of a bank-account - the reference from bank-account to a signatory is required, but the relation-type is optional at the moment since this reference will always describe a signatory.
- 'entity': Entity owning the bank account - optional.
- person:
- 'address': Address of a person - optional.
- input:
MISP objects (transaction, bank-account, person, legal-entity, geolocation), with references, describing financial transactions and their origin and target.
- output:
GoAML format file, describing financial transactions, with their origin and target (bank accounts, persons or entities).
- references:
- requirements:
PyMISP, MISP objects
liteexport
Lite export of a MISP event.
- features:
This module is simply producing a json MISP event format file, but exporting only Attributes from the Event. Thus, MISP Events exported with this module should have attributes that are not internal references, otherwise the resulting event would be empty.
- input:
MISP Event attributes
- output:
Lite MISP Event
osqueryexport
OSQuery export of a MISP event.
- features:
This module export an event as osquery queries that can be used in packs or in fleet management solution like Kolide.
- input:
MISP Event attributes
- output:
osquery SQL queries
pdfexport
Simple export of a MISP event to PDF.
- features:
The module takes care of the PDF file building, and work with any MISP Event. Except the requirement of asciidoctor, used to create the file, there is no special feature concerning the Event.
- input:
MISP Event
- output:
MISP Event in a PDF file.
- references:
https://acrobat.adobe.com/us/en/acrobat/about-adobe-pdf.html
- requirements:
PyMISP, asciidoctor
testexport
Skeleton export module.
threatStream_misp_export
Module to export a structured CSV file for uploading to threatStream.
- features:
The module takes a MISP event in input, to look every attribute. Each attribute matching with some predefined types is then exported in a CSV format recognized by ThreatStream.
- input:
MISP Event attributes
- output:
ThreatStream CSV format file
- references:
https://www.anomali.com/platform/threatstream, https://github.com/threatstream
- requirements:
csv
threat_connect_export
Module to export a structured CSV file for uploading to ThreatConnect.
- features:
The module takes a MISP event in input, to look every attribute. Each attribute matching with some predefined types is then exported in a CSV format recognized by ThreatConnect. Users should then provide, as module configuration, the source of data they export, because it is required by the output format.
- input:
MISP Event attributes
- output:
ThreatConnect CSV format file
- references:
- requirements:
csv
Import Modules
csvimport
Module to import MISP attributes from a csv file.
- features:
In order to parse data from a csv file, a header is required to let the module know which column is matching with known attribute fields / MISP types. This header is part of the configuration of the module and should be filled out in MISP plugin settings, each field separated by COMMAS. Fields that do not match with any type known in MISP can be ignored in import, using a space or simply nothing between two separators (example: 'ip-src, , comment, '). There is also one type that is confused and can be either a MISP attribute type or an attribute field: 'comment'. In this case, using 'attrComment' specifies that the attribute field 'comment' should be considered, otherwise it will be considered as the MISP attribute type.
For each MISP attribute type, an attribute is created. Attribute fields that are imported are the following: value, type, category, to-ids, distribution, comment, tag.
- input:
CSV format file.
- output:
MISP Event attributes
- references:
https://tools.ietf.org/html/rfc4180, https://tools.ietf.org/html/rfc7111
- requirements:
PyMISP
cuckooimport
Module to import Cuckoo JSON.
- features:
The module simply imports MISP Attributes from a Cuckoo JSON format file. There is thus no special feature to make it work.
- input:
Cuckoo JSON file
- output:
MISP Event attributes
- references:
https://cuckoosandbox.org/, https://github.com/cuckoosandbox/cuckoo
email_import
Module to import emails in MISP.
- features:
This module can be used to import e-mail text as well as attachments and urls. 3 configuration parameters are then used to unzip attachments, guess zip attachment passwords, and extract urls: set each one of them to True or False to process or not the respective corresponding actions.
- input:
E-mail file
- output:
MISP Event attributes
goamlimport
Module to import MISP objects about financial transactions from GoAML files.
- features:
Unlike the GoAML export module, there is here no special feature to import data from GoAML external files, since the module will import MISP Objects with their References on its own, as it is required for the export module to rebuild a valid GoAML document.
- input:
GoAML format file, describing financial transactions, with their origin and target (bank accounts, persons or entities).
- output:
MISP objects (transaction, bank-account, person, legal-entity, geolocation), with references, describing financial transactions and their origin and target.
- references:
- requirements:
PyMISP
mispjson
Module to import MISP JSON format for merging MISP events.
- features:
The module simply imports MISP Attributes from an other MISP Event in order to merge events together. There is thus no special feature to make it work.
- input:
MISP Event
- output:
MISP Event attributes
ocr
Optical Character Recognition (OCR) module for MISP.
- features:
The module tries to recognize some text from an image and import the result as a freetext attribute, there is then no special feature asked to users to make it work.
- input:
Image
- output:
freetext MISP attribute
openiocimport
Module to import OpenIOC packages.
- features:
The module imports MISP Attributes from OpenIOC packages, there is then no special feature for users to make it work.
- input:
OpenIOC packages
- output:
MISP Event attributes
- references:
https://www.fireeye.com/blog/threat-research/2013/10/openioc-basics.html
- requirements:
PyMISP
threatanalyzer_import
Module to import ThreatAnalyzer archive.zip / analysis.json files.
- features:
The module imports MISP Attributes from a ThreatAnalyzer format file. This file can be either ZIP, or JSON format. There is by the way no special feature for users to make the module work.
- input:
ThreatAnalyzer format file
- output:
MISP Event attributes
- references:
vmray_import
Module to import VMRay (VTI) results.
- features:
The module imports MISP Attributes from VMRay format, using the VMRay api. Users should then provide as the module configuration the API Key as well as the server url in order to fetch their data to import.
- input:
VMRay format
- output:
MISP Event attributes
- references:
- requirements:
vmray_rest_api