Clusters and elements to attach to MISP events or attributes (like threat actors) https://www.misp-project.org/galaxy.html
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Alexandre Dulaunoy c98093e6fe
Merge pull request #513 from danielplohmann/patch-20
5 days ago
clusters Merge pull request #513 from danielplohmann/patch-20 5 days ago
doc/images MISP galaxy screenshot 3 years ago
galaxies Merge pull request #488 from Delta-Sierra/master 2 months ago
misp Mapping triples/machine tags with galaxy, clusters and so on 3 years ago
tools fix: [attack] fixes old MITRE relationships not being removed 3 months ago
vocabularies Update cert-eu-motive.json 1 year ago
.gitignore Add test for empty strings 5 months ago
.travis.yml chg: [travis] pip3 5 days ago
CONTRIBUTE.md add: [doc] contribution doc added 1 year ago
LICENSE.md chg: [licensing] 2-clause BSD added in addition to CC0 1 year ago
README.md add: [dark-pattern] updates the README 2 months ago
jq_all_the_things.sh fix: automatically fix missing uuids 1 year ago
schema_clusters.json fix-tentative 2 months ago
schema_galaxies.json chg: [schema] optional kill_chain_order field added 1 year ago
schema_misp.json Add validators for vocabularies and misp 2 years ago
schema_vocabularies.json Add validators for vocabularies and misp 2 years ago
validate_all.sh Add test for empty strings 5 months ago

README.md

misp-galaxy

Build Status

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.

Vocabularies are from existing standards (like STIX, Veris, MISP and so on) or custom ones.

The objective is to have a comment set of clusters for organizations starting analysis but that can be expanded to localized information (which is not shared) or additional information (that can be shared).

Available clusters

Available Vocabularies

A readable PDF overview of the MISP galaxy is available or HTML and generated from the JSON.

Common

Threat Actor

MISP Integration

Starting from MISP 2.4.56, galaxy is integrated within the MISP threat sharing platform and users can directly benefit from the available clusters to attach them to the MISP event.

MISP Integration of the MISP galaxy

How to contribute?

License

The MISP galaxy (JSON files) are dual-licensed under:

or

~~~~ Copyright © 2015-2019 Alexandre Dulaunoy - a@foo.be Copyright © 2015-2019 CIRCL - Computer Incident Response Center Luxembourg Copyright © 2015-2019 Andras Iklody Copyright © 2015-2019 Raphael Vinot Copyright © 2015-2019 Deborah Servili Copyright © 2016-2019 Various contributors to MISP Project

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice,
   this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ~~~~~