MISP is not only a software but also a series of data models created by the MISP community. MISP includes a simple and practical information sharing format expressed in JSON that can be used with MISP software or by any other software. The MISP formats are now standards handled by the [MISP standard body](https://www.misp-standard.org).
The MISP core format is a simple JSON format used by MISP and other tools to exchange events and attributes. The JSON schema 2.4 is described on the MISP core software and many sample files are available in the OSINT feed.
The MISP format is described as Internet-Draft in [misp-rfc](https://github.com/MISP/MISP-rfc). The MISP format are described to support the developer or organisation willing to build your own tool supporting the MISP format (as import or export). The standard is built from practical use-cases and the implementation references within the MISP project. The standard is quickly evolving following the MISP implementation.
***Targeting data**: Targeting information to include recipient email, infected machines, department, and or locations.
***Antivirus detection**: List of anti-virus vendors detecting the malware or information on detection performance (e.g. 13/43 or 67%). Attachment with list of detection or link to VirusTotal could be placed here as well.
***Payload delivery**: Information about the way the malware payload is initially delivered, for example information about the email or web-site, vulnerability used, originating IP etc. Malware sample itself should be attached here.
***Artifacts dropped**: Any artifact (files, registry keys etc.) dropped by the malware or other modifications to the system
***Payload installation**: Location where the payload was placed in the system and the way it was installed. For example, a filename|md5 type attribute can be added here like this: c:\windows\system32\malicious.exe|41d8cd98f00b204e9800998ecf8427e.
***Persistence mechanism**: Mechanisms used by the malware to start at boot. This could be a registry key, legitimate driver modification, LNK file in startup
***Payload type**: Information about the final payload(s). Can contain a function of the payload, e.g. keylogger, RAT, or a name if identified, such as Poison Ivy.
***Attribution**: Identification of the group, organisation, or country behind the attack
***External analysis**: Any other result from additional analysis of the malware like tools output Examples: pdf-parser output, automated sandbox analysis, reverse engineering report.
***Financial fraud**: Financial Fraud indicators, for example: IBAN Numbers, BIC codes, Credit card numbers, etc.
***md5**: You are encouraged to use filename|md5 instead. A checksum in md5 format, only use this if you don't know the correct filename
***sha1**: You are encouraged to use filename|sha1 instead. A checksum in sha1 format, only use this if you don't know the correct filename
***sha256**: You are encouraged to use filename|sha256 instead. A checksum in sha256 format, only use this if you don't know the correct filename
***filename**: Filename
***pdb**: Microsoft Program database (PDB) path information
***filename|md5**: A filename and an md5 hash separated by a | (no spaces)
***filename|sha1**: A filename and an sha1 hash separated by a | (no spaces)
***filename|sha256**: A filename and an sha256 hash separated by a | (no spaces)
***ip-src**: A source IP address of the attacker
***ip-dst**: A destination IP address of the attacker or C&C server. Also set the IDS flag on when this IP is hardcoded in malware
***hostname**: A full host/dnsname of an attacker. Also set the IDS flag on when this hostname is hardcoded in malware
***domain**: A domain name used in the malware. Use this instead of hostname when the upper domain is important or can be used to create links between events.
***domain|ip**: A domain name and its IP address (as found in DNS lookup) separated by a | (no spaces)
***eppn**: eduPersonPrincipalName - eppn - the NetId of the person for the purposes of inter-institutional authentication. Should be stored in the form of user@univ.edu, where univ.edu is the name of the local security domain.
***ja3-fingerprint-md5**: JA3 is a method for creating SSL/TLS client fingerprints that should be easy to produce on any platform and can be easily shared for threat intelligence.
***favicon-mmh3**: favicon-mmh3 is the murmur3 hash of a favicon as used in Shodan.
***hassh-md5**: hassh is a network fingerprinting standard which can be used to identify specific Client SSH implementations. The fingerprints can be easily stored, searched and shared in the form of an MD5 fingerprint.
***hasshserver-md5**: hasshServer is a network fingerprinting standard which can be used to identify specific Server SSH implementations. The fingerprints can be easily stored, searched and shared in the form of an MD5 fingerprint.
***regkey**: Registry key or value
***regkey|value**: Registry value + data separated by |
***AS**: Autonomous system
***snort**: An IDS rule in Snort rule-format. This rule will be automatically rewritten in the NIDS exports.
***bro**: An NIDS rule in the Bro rule-format.
***zeek**: An NIDS rule in the Zeek rule-format.
***community-id**: a community ID flow hashing algorithm to map multiple traffic monitors into common flow id
***sigma**: Sigma - Generic Signature Format for SIEM Systems
***gene**: GENE - Go Evtx sigNature Engine
***kusto-query**: Kusto query - Kusto from Microsoft Azure is a service for storing and running interactive analytics over Big Data.
***mime-type**: A media type (also MIME type and content type) is a two-part identifier for file formats and format contents transmitted on the Internet
***identity-card-number**: Identity card number
***cookie**: HTTP cookie as often stored on the user web client. This can include authentication cookie or session cookie.
***vulnerability**: A reference to the vulnerability used in the exploit
***cpe**: Common Platform Enumeration - structured naming scheme for information technology systems, software, and packages.
***weakness**: A reference to the weakness used in the exploit
***attachment**: Please upload files using the <em>Upload Attachment</em> button.
***malware-sample**: Please upload files using the <em>Upload Attachment</em> button.
***link**: Link to an external information
***comment**: Comment or description in a human language. This will not be correlated with other attributes
***text**: Name, ID or a reference
***hex**: A value in hexadecimal format
***other**: Other attribute
***named pipe**: Named pipe, use the format \.\pipe\<PipeName>
***mutex**: Mutex, use the format \BaseNamedObjects\<Mutex>
***authentihash**: You are encouraged to use filename|authentihash instead. Authenticode executable signature hash, only use this if you don't know the correct filename
***vhash**: You are encouraged to use filename|vhash instead. A checksum from VirusTotal, only use this if you don't know the correct filename
***ssdeep**: You are encouraged to use filename|ssdeep instead. A checksum in the SSDeep format, only use this if you don't know the correct filename
***imphash**: You are encouraged to use filename|imphash instead. A hash created based on the imports in the sample, only use this if you don't know the correct filename
***telfhash**: You are encouraged to use a file object with telfash
***pehash**: PEhash - a hash calculated based of certain pieces of a PE executable file
***impfuzzy**: You are encouraged to use filename|impfuzzy instead. A fuzzy hash created based on the imports in the sample, only use this if you don't know the correct filename
***sha224**: You are encouraged to use filename|sha224 instead. A checksum in sha224 format, only use this if you don't know the correct filename
***sha384**: You are encouraged to use filename|sha384 instead. A checksum in sha384 format, only use this if you don't know the correct filename
***sha512**: You are encouraged to use filename|sha512 instead. A checksum in sha512 format, only use this if you don't know the correct filename
***sha512/224**: You are encouraged to use filename|sha512/224 instead. A checksum in sha512/224 format, only use this if you don't know the correct filename
***sha512/256**: You are encouraged to use filename|sha512/256 instead. A checksum in sha512/256 format, only use this if you don't know the correct filename
***sha3-224**: You are encouraged to use filename|sha3-224 instead. A checksum in sha3-224 format, only use this if you don't know the correct filename
***sha3-256**: You are encouraged to use filename|sha3-256 instead. A checksum in sha3-256 format, only use this if you don't know the correct filename
***sha3-384**: You are encouraged to use filename|sha3-384 instead. A checksum in sha3-384 format, only use this if you don't know the correct filename
***sha3-512**: You are encouraged to use filename|sha3-512 instead. A checksum in sha3-512 format, only use this if you don't know the correct filename
***tlsh**: You are encouraged to use filename|tlsh instead. A checksum in the Trend Micro Locality Sensitive Hash format, only use this if you don't know the correct filename
***cdhash**: An Apple Code Directory Hash, identifying a code-signed Mach-O executable file
***filename|authentihash**: A checksum in md5 format
***filename|vhash**: A filename and a VirusTotal hash separated by a |
***filename|ssdeep**: A checksum in ssdeep format
***filename|imphash**: Import hash - a hash created based on the imports in the sample.
***filename|impfuzzy**: Import fuzzy hash - a fuzzy hash created based on the imports in the sample.
***filename|pehash**: A filename and a PEhash separated by a |
***filename|sha224**: A filename and a sha-224 hash separated by a |
***filename|sha384**: A filename and a sha-384 hash separated by a |
***filename|sha512**: A filename and a sha-512 hash separated by a |
***filename|sha512/224**: A filename and a sha-512/224 hash separated by a |
***filename|sha512/256**: A filename and a sha-512/256 hash separated by a |
***filename|sha3-224**: A filename and an sha3-224 hash separated by a |
***filename|sha3-256**: A filename and an sha3-256 hash separated by a |
***filename|sha3-384**: A filename and an sha3-384 hash separated by a |
***filename|sha3-512**: A filename and an sha3-512 hash separated by a |
***filename|tlsh**: A filename and a Trend Micro Locality Sensitive Hash separated by a |
***windows-scheduled-task**: A scheduled task in windows
***windows-service-name**: A windows service name. This is the name used internally by windows. Not to be confused with the windows-service-displayname.
***windows-service-displayname**: A windows service's displayname, not to be confused with the windows-service-name. This is the name that applications will generally display as the service's name in applications.
***dns-soa-email**: RFC1035 mandates that DNS zones should have a SOA (Statement Of Authority) record that contains an email address where a PoC for the domain could be contacted. This can sometimes be used for attribution/linkage between different domains even if protected by whois privacy
***size-in-bytes**: Size expressed in bytes
***counter**: An integer counter, generally to be used in objects
***datetime**: Datetime in the ISO 8601 format
***port**: Port number
***ip-dst|port**: IP destination and port number separated by a |
***ip-src|port**: IP source and port number separated by a |
***hostname|port**: Hostname and port number separated by a |
***mac-address**: Mac address
***mac-eui-64**: Mac EUI-64 address
***email-dst-display-name**: Email destination display name
***email-src-display-name**: Email source display name
***email-header**: Email header
***email-reply-to**: Email reply to header
***email-x-mailer**: Email x-mailer header
***email-mime-boundary**: The email mime boundary separating parts in a multipart email
***email-thread-index**: The email thread index header
***email-message-id**: The email message ID
***github-username**: A github user name
***github-repository**: A github repository
***github-organisation**: A github organisation
***jabber-id**: Jabber ID
***twitter-id**: Twitter ID
***dkim**: DKIM public key
***dkim-signature**: DKIM signature
***first-name**: First name of a natural person
***middle-name**: Middle name of a natural person
***last-name**: Last name of a natural person
***date-of-birth**: Date of birth of a natural person (in YYYY-MM-DD format)
***place-of-birth**: Place of birth of a natural person
***gender**: The gender of a natural person (Male, Female, Other, Prefer not to say)
***passport-number**: The passport number of a natural person
***passport-country**: The country in which the passport was issued
***passport-expiration**: The expiration date of a passport
***redress-number**: The Redress Control Number is the record identifier for people who apply for redress through the DHS Travel Redress Inquiry Program (DHS TRIP). DHS TRIP is for travelers who have been repeatedly identified for additional screening and who want to file an inquiry to have erroneous information corrected in DHS systems
***nationality**: The nationality of a natural person
***visa-number**: Visa number
***issue-date-of-the-visa**: The date on which the visa was issued
***primary-residence**: The primary residence of a natural person
***country-of-residence**: The country of residence of a natural person
***special-service-request**: A Special Service Request is a function to an airline to provide a particular facility for A Passenger or passengers.
***frequent-flyer-number**: The frequent flyer number of a passenger
***travel-details**: Travel details
***payment-details**: Payment details
***place-port-of-original-embarkation**: The orignal port of embarkation
***place-port-of-clearance**: The port of clearance
***place-port-of-onward-foreign-destination**: A Port where the passenger is transiting to
***passenger-name-record-locator-number**: The Passenger Name Record Locator is a key under which the reservation for a trip is stored in the system. The PNR contains, among other data, the name, flight segments and address of the passenger. It is defined by a combination of five or six letters and numbers.
***mobile-application-id**: The application id of a mobile application
***chrome-extension-id**: Chrome extension id
***cortex**: Cortex analysis result
***boolean**: Boolean value - to be used in objects
***anonymised**: Anonymised value - described with the anonymisation object via a relationship.
Along with the core format, [MISP taxonomies](https://www.github.com/MISP/misp-taxonomies/) provide a set of already defined classifications modeling estimative language, CSIRTs/CERTs classifications, national classifications or threat model classification. The fixed taxonomies provide a practical method to tag efficiently events and attributes within a set of MISP instances where taxonomies can be easily cherry-picked or extended to meet the local requirements of an organization or a specific sharing community. When using MISP, the MISP taxonomies are available and can be freely used based on the community practises.
: The Detection Maturity Level (DML) model is a capability maturity model for referencing ones maturity in detecting cyber attacks. It's designed for organizations who perform intel-driven detection and response and who put an emphasis on having a mature detection program.[HTML](https://www.misp-project.org/taxonomies.html#_DML)
: The Permissible Actions Protocol - or short: PAP - was designed to indicate how the received information can be used.[HTML](https://www.misp-project.org/taxonomies.html#_PAP)
: Access Now classification to classify an issue (such as security, human rights, youth rights).[HTML](https://www.misp-project.org/taxonomies.html#_accessnow)
: The Admiralty Scale (also called the NATO System) is used to rank the reliability of a source and the credibility of an information.[HTML](https://www.misp-project.org/taxonomies.html#_admiralty_scale)
: AIS Marking Schema implementation is maintained by the National Cybersecurity and Communication Integration Center (NCCIC) of the U.S. Department of Homeland Security (DHS)[HTML](https://www.misp-project.org/taxonomies.html#_ais_marking)
: A series of assessment predicates describing the analyst capabilities to perform analysis. These assessment can be assigned by the analyst him/herself or by another party evaluating the analyst.[HTML](https://www.misp-project.org/taxonomies.html#_analyst_assessment)
: A pre-approved category of action for indicators being shared with partners (MIMIC).[HTML](https://www.misp-project.org/taxonomies.html#_approved_category_of_action)
: CIRCL Taxonomy is a simple scheme for incident classification and area topic where the incident took place.[HTML](https://www.misp-project.org/taxonomies.html#_circl)
: Collaborative intelligence support language is a common language to support analysts to perform their analysis to get crowdsourced support when using threat intelligence sharing platform like MISP.[HTML](https://www.misp-project.org/taxonomies.html#_collaborative_intelligence)
: The Common Taxonomy for Law Enforcement and The National Network of CSIRTs bridges the gap between the CSIRTs and international Law Enforcement communities by adding a legislative framework to facilitate the harmonisation of incident reporting to competent authorities, the development of useful statistics and sharing information within the entire cybercrime ecosystem.[HTML](https://www.misp-project.org/taxonomies.html#_common_taxonomy)
: The COPINE Scale is a rating system created in Ireland and used in the United Kingdom to categorise the severity of images of child sex abuse.[HTML](https://www.misp-project.org/taxonomies.html#_copine_scale)
: Cyber Threat Framework was developed by the US Government to enable consistent characterization and categorization of cyber threat events, and to identify trends or changes in the activities of cyber adversaries. https://www.dni.gov/index.php/cyber-threat-framework[HTML](https://www.misp-project.org/taxonomies.html#_cyber_threat_framework)
: Criminal motivation on the dark web: A categorisation model for law enforcement. ref: Janis Dalins, Campbell Wilson, Mark Carman. Taxonomy updated by MISP Project.[HTML](https://www.misp-project.org/taxonomies.html#_dark_web)
: Data classification for data potentially at risk of exfiltration based on table 2.1 of Solving Cyber Risk book.[HTML](https://www.misp-project.org/taxonomies.html#_data_classification)
: DCSO Sharing Taxonomy to classify certain types of MISP events using the DCSO Event Guide[HTML](https://www.misp-project.org/taxonomies.html#_dcso_sharing)
: Distributed Denial of Service - or short: DDoS - taxonomy supports the description of Denial of Service attacks and especially the types they belong too.[HTML](https://www.misp-project.org/taxonomies.html#_ddos)
: Taxonomy for the handling of protectively marked information in MISP with German (DE) Government classification markings (VS)[HTML](https://www.misp-project.org/taxonomies.html#_de_vs)
: DHS critical sectors as described in https://www.dhs.gov/critical-infrastructure-sectors.[HTML](https://www.misp-project.org/taxonomies.html#_dhs_ciip_sectors)
: The Diamond Model for Intrusion Analysis, a phase-based model developed by Lockheed Martin, aims to help categorise and identify the stage of an attack.[HTML](https://www.misp-project.org/taxonomies.html#_diamond_model)
: ISM (Information Security Marking Metadata) V13 as described by DNI.gov (Director of National Intelligence - US).[HTML](https://www.misp-project.org/taxonomies.html#_dni_ism)
: A taxonomy based on the superclass and class of drugs, based on https://www.drugbank.ca/releases/latest[HTML](https://www.misp-project.org/taxonomies.html#_drugs)
: Economical impact is a taxonomy to describe the financial impact as positive or negative gain to the tagged information.[HTML](https://www.misp-project.org/taxonomies.html#_economical_impact)
: eCSIRT incident classification Appendix C of the eCSIRT EU project including IntelMQ updates.[HTML](https://www.misp-project.org/taxonomies.html#_ecsirt)
: ENISA Threat Taxonomy - A tool for structuring threat information as published in https://www.enisa.europa.eu/topics/threat-risk-management/threats-and-trends/enisa-threat-landscape/etl2015/enisa-threat-taxonomy-a-tool-for-structuring-threat-information[HTML](https://www.misp-project.org/taxonomies.html#_enisa)
: Estimative language - including likelihood or probability of event based on the Intelligence Community Directive 203 (ICD 203) (6.2.(a)) and JP 2-0, Joint Intelligence.[HTML](https://www.misp-project.org/taxonomies.html#_estimative_language)
: Market operators and public administrations that must comply to some notifications requirements under EU NIS directive.[HTML](https://www.misp-project.org/taxonomies.html#_eu_marketop_and_publicadmin)
: EU classified information (EUCI) means any information or material designated by a EU security classification, the unauthorised disclosure of which could cause varying degrees of prejudice to the interests of the European Union or of one or more of the Member States as described in COUNCIL DECISION of 23 September 2013 on the security rules for protecting EU classified information[HTML](https://www.misp-project.org/taxonomies.html#_euci)
: A series of assessment predicates describing the event assessment performed to make judgement(s) under a certain level of uncertainty.[HTML](https://www.misp-project.org/taxonomies.html#_event_assessment)
: Exercise is a taxonomy to describe if the information is part of one or more cyber or crisis exercise.[HTML](https://www.misp-project.org/taxonomies.html#_exercise)
: Flesch Reading Ease is a revised system for determining the comprehension difficulty of written material. The scoring of the flesh score can have a maximum of 121.22 and there is no limit on how low a score can be (negative score are valid).[HTML](https://www.misp-project.org/taxonomies.html#_flesch_reading_ease)
: The Future of Privacy Forum (FPF) [visual guide to practical de-identification](https://fpf.org/2016/04/25/a-visual-guide-to-practical-data-de-identification/) taxonomy is used to evaluate the degree of identifiability of personal data and the types of pseudonymous data, de-identified data and anonymous data. The work of FPF is licensed under a creative commons attribution 4.0 international license.[HTML](https://www.misp-project.org/taxonomies.html#_fpf)
: Taxonomy related to the REGULATION (EU) 2016/679 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation)[HTML](https://www.misp-project.org/taxonomies.html#_gdpr)
: Taxonomy used by GSMA for their information sharing program with telco describing the attack categories[HTML](https://www.misp-project.org/taxonomies.html#_gsma_attack_category)
: Taxonomy used by GSMA for their information sharing program with telco describing the various aspects of fraud[HTML](https://www.misp-project.org/taxonomies.html#_gsma_fraud)
: Taxonomy used by GSMA for their information sharing program with telco describing the types of infrastructure. WiP[HTML](https://www.misp-project.org/taxonomies.html#_gsma_network_technology)
: Christian Seifert, Ian Welch, Peter Komisarczuk, ‘Taxonomy of Honeypots’, Technical Report CS-TR-06/12, VICTORIA UNIVERSITY OF WELLINGTON, School of Mathematical and Computing Sciences, June 2006, http://www.mcs.vuw.ac.nz/comp/Publications/archive/CS-TR-06/CS-TR-06-12.pdf[HTML](https://www.misp-project.org/taxonomies.html#_honeypot_basic)
: Forum of Incident Response and Security Teams (FIRST) Information Exchange Policy (IEP) framework.[HTML](https://www.misp-project.org/taxonomies.html#_iep)
: The IFX taxonomy is used to categorise information (MISP events and attributes) to aid in the intelligence vetting process[HTML](https://www.misp-project.org/taxonomies.html#_ifx_vetting)
: How an incident is classified in its process to be resolved. The taxonomy is inspired from NASA Incident Response and Management Handbook.[HTML](https://www.misp-project.org/taxonomies.html#_incident_disposition)
: A taxonomy describing information leaks and especially information classified as being potentially leaked.[HTML](https://www.misp-project.org/taxonomies.html#_infoleak)
: Information security indicators have been standardized by the ETSI Industrial Specification Group (ISG) ISI. These indicators provide the basis to switch from a qualitative to a quantitative culture in IT Security Scope of measurements: External and internal threats (attempt and success), user's deviant behaviours, nonconformities and/or vulnerabilities (software, configuration, behavioural, general security framework). ETSI GS ISI 001-1 (V1.1.2): ISI Indicators[HTML](https://www.misp-project.org/taxonomies.html#_information_security_indicators)
: Cyber Kill Chain from Lockheed Martin as described in Intelligence-Driven Computer Network Defense Informed by Analysis of Adversary Campaigns and Intrusion Kill Chains.[HTML](https://www.misp-project.org/taxonomies.html#_kill_chain)
: Malware Type and Platform classification based on Microsoft's implementation of the Computer Antivirus Research Organization (CARO) Naming Scheme and Malware Terminology.[HTML](https://www.misp-project.org/taxonomies.html#_ms_caro_malware)
: Malware Type and Platform classification based on Microsoft's implementation of the Computer Antivirus Research Organization (CARO) Naming Scheme and Malware Terminology.[HTML](https://www.misp-project.org/taxonomies.html#_ms_caro_malware_full)
: Marking of Classified and Unclassified materials as described by the North Atlantic Treaty Organization, NATO.[HTML](https://www.misp-project.org/taxonomies.html#_nato)
: Open Threat Taxonomy v1.1 base on James Tarala of SANS ref. - http://www.auditscripts.com/resources/open_threat_taxonomy_v1.1a.pdf[HTML](https://www.misp-project.org/taxonomies.html#_open_threat)
: After an incident is scored, it is assigned a priority level. The six levels listed below are aligned with NCCIC, DHS, and the CISS to help provide a common lexicon when discussing incidents. This priority assignment drives NCCIC urgency, pre-approved incident response offerings, reporting requirements, and recommendations for leadership escalation. Generally, incident priority distribution should follow a similar pattern to the graph below. Based on https://www.us-cert.gov/NCCIC-Cyber-Incident-Scoring-System.[HTML](https://www.misp-project.org/taxonomies.html#_priority_level)
: Runtime or software packer used to combine compressed data with the decompression code. The decompression code can add additional obfuscations mechanisms including polymorphic-packer or other obfuscation techniques. This taxonomy lists all the known or official packer used for legitimate use or for packing malicious binaries.[HTML](https://www.misp-project.org/taxonomies.html#_runtime_packer)
: Representation of the behavior or modus operandi of cyber adversaries (a.k.a TTP) as normalized in STIX[HTML](https://www.misp-project.org/taxonomies.html#_stix_ttp)
: The Targeted Threat Index is a metric for assigning an overall threat ranking score to email messages that deliver malware to a victim’s computer. The TTI metric was first introduced at SecTor 2013 by Seth Hardy as part of the talk “RATastrophe: Monitoring a Malware Menagerie” along with Katie Kleemola and Greg Wiseman.[HTML](https://www.misp-project.org/taxonomies.html#_targeted_threat_index)
: An overview of some of the known attacks related to DNS as described by Torabi, S., Boukhtouta, A., Assi, C., & Debbabi, M. (2018) in Detecting Internet Abuse by Analyzing Passive DNS Traffic: A Survey of Implemented Systems. IEEE Communications Surveys & Tutorials, 1–1. doi:10.1109/comst.2018.2849614[HTML](https://www.misp-project.org/taxonomies.html#_threats_to_dns)
: The Traffic Light Protocol - or short: TLP - was designed with the objective to create a favorable classification scheme for sharing sensitive information while keeping the control over its distribution at the same time. Extended with TLP:EX:CHR.[HTML](https://www.misp-project.org/taxonomies.html#_tlp)
: Taxonomy to describe different types of intelligence gathering discipline which can be described the origin of intelligence.[HTML](https://www.misp-project.org/taxonomies.html#_type)
: The Use Case Applicability categories reflect standard resolution categories, to clearly display alerting rule configuration problems.[HTML](https://www.misp-project.org/taxonomies.html#_use_case_applicability)
: Workflow support language is a common language to support intelligence analysts to perform their analysis on data and information.[HTML](https://www.misp-project.org/taxonomies.html#_workflow)
MISP galaxy is a simple method to express a large object called cluster that can be attached to MISP events or attributes. A cluster can be composed of one or more elements. Elements are expressed as key-values. There are default vocabularies available in MISP galaxy but those can be overwritten, replaced or updated as you wish. Existing clusters and vocabularies can be used as-is or as a template. MISP distribution can be applied to each cluster to permit a limited or broader distribution scheme. Many MISP galaxy clusters are already available like Exploit-Kit, Microsoft Activity Group actor, Preventive Measure,
Ransomware, TDS, Threat actor or Tool used by adversaries.
