Merge pull request #215 from Delta-Sierra/master

New taxonomies based on Cyber Taxi

.github/workflows/nosetests.yml

@@ -0,0 +1,40 @@
+name: Python application
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: [3.6, 3.7, 3.8, 3.9]
+
+    steps:
+
+    - uses: actions/checkout@v2
+
+    - name: Set up Python ${{matrix.python-version}}
+      uses: actions/setup-python@v2
+      with:
+        python-version: ${{matrix.python-version}}
+
+    - name: Initialize submodules
+      run: git submodule update --init --recursive
+
+    - name: Install system dependencies
+      run: |
+        sudo apt install jq moreutils
+
+    - name: Install Python dependencies
+      run: |
+        python -m pip install --upgrade jsonschema pytaxonomies
+
+    - name: Test
+      run: |
+        ./validate_all.sh
+        pytaxonomies -l MANIFEST.json -a

MANIFEST.json

@@ -46,7 +46,7 @@
     {
       "description": "An overview and description of the adversary infrastructure",
       "name": "adversary",
-      "version": 4
+      "version": 6
     },
     {
       "description": "The AIS Marking Schema implementation is maintained by the National Cybersecurity and Communication Integration Center (NCCIC) of the U.S. Department of Homeland Security (DHS)",
@@ -76,7 +76,7 @@
     {
       "description": "CIRCL Taxonomy - Schemes of Classification in Incident Response and Detection",
       "name": "circl",
-      "version": 4
+      "version": 5
     },
     {
       "description": "Course of action taken within organization to discover, detect, deny, disrupt, degrade, deceive and/or destroy an attack.",
@@ -101,7 +101,7 @@
     {
       "description": "A Course Of Action analysis considers six potential courses of action for the development of a cyber security capability.",
       "name": "course-of-action",
-      "version": 1
+      "version": 2
     },
     {
       "description": "Threats targetting cryptocurrency, based on CipherTrace report.",
@@ -123,6 +123,11 @@
       "name": "cssa",
       "version": 8
     },
+    {
+      "description": "Cyber Threat Intelligence cycle to control workflow state of your process.",
+      "name": "cti",
+      "version": 1
+    },
     {
       "description": "Current events - Schemes of Classification in Incident Response and Detection",
       "name": "current-event",
@@ -133,6 +138,11 @@
       "name": "cyber-threat-framework",
       "version": 2
     },
+    {
+      "description": "Taxonomy used by CyCAT, the Universal Cybersecurity Resource Catalogue, to categorize the namespaces it supports and uses.",
+      "name": "cycat",
+      "version": 1
+    },
     {
       "description": "Taxonomy to describe desired actions for Cytomic Orion",
       "name": "cytomic-orion",
@@ -179,9 +189,9 @@
       "version": 3
     },
     {
-      "description": "Domain Name Abuse - taxonomy to tag domain names used for cybercrime. Use europol-incident to tag abuse-activity",
+      "description": "Domain Name Abuse - taxonomy to tag domain names used for cybercrime.",
       "name": "domain-abuse",
-      "version": 1
+      "version": 2
     },
     {
       "description": "A taxonomy based on the superclass and class of drugs. Based on https://www.drugbank.ca/releases/latest",
@@ -214,7 +224,7 @@
       "version": 1
     },
     {
-      "description": "Sectors and sub sectors as identified by the NIS Directive",
+      "description": "Sectors, subsectors, and digital services as identified by the NIS Directive",
       "name": "eu-nis-sector-and-subsectors",
       "version": 1
     },
@@ -373,6 +383,11 @@
       "name": "interception-method",
       "version": 1
     },
+    {
+      "description": "An IOC classification to facilitate automation of malicious and non malicious artifacts",
+      "name": "ioc",
+      "version": 2
+    },
     {
       "description": "Internet of Things taxonomy, based on IOT UK report https://iotuk.org.uk/wp-content/uploads/2017/01/IOT-Taxonomy-Report.pdf",
       "name": "iot",
@@ -409,14 +424,14 @@
       "version": 2
     },
     {
-      "description": "classification for the identification of type of misinformation among websites. Source:False, Misleading, Clickbait-y, and/or Satirical 'News' Sources by Melissa Zimdars 2019",
+      "description": "classification for the identification of type of misinformation among websites. Source:False, Misleading, Clickbait-y, and/or Satirical News Sources by Melissa Zimdars 2019",
       "name": "misinformation-website-label",
-      "version": "1"
+      "version": 1
     },
     {
       "description": "MISP taxonomy to infer with MISP behavior or operation.",
       "name": "misp",
-      "version": 11
+      "version": 12
     },
     {
       "description": "MONARC Threats Taxonomy",
@@ -486,7 +501,7 @@
     {
       "description": "Ransomware is used to define ransomware types and the elements that compose them.",
       "name": "ransomware",
-      "version": 4
+      "version": 6
     },
     {
       "description": "Add a retenion time to events to automatically remove the IDS-flag on ip-dst or ip-src attributes. We calculate the time elapsed based on the date of the event. Supported time units are: d(ays), w(eeks), m(onths), y(ears). The numerical_value is just for sorting in the web-interface and is not used for calculations.",
@@ -496,7 +511,7 @@
     {
       "description": "Reference Security Incident Classification Taxonomy",
       "name": "rsit",
-      "version": 3
+      "version": 1002
     },
     {
       "description": "Status of events used in Request Tracker.",
@@ -543,6 +558,16 @@
       "name": "targeted-threat-index",
       "version": 3
     },
+    {
+      "description": "Thales Group Taxonomy - was designed with the aim of enabling desired sharing and preventing unwanted sharing between Thales Group security communities.",
+      "name": "thales_group",
+      "version": 2
+    },
+    {
+      "description": "The ThreatMatch Sectors, Incident types, Malware types and Alert types are applicable for any ThreatMatch instances and should be used for all CIISI and TIBER Projects.",
+      "name": "threatmatch",
+      "version": 3
+    },
     {
       "description": "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",
       "name": "threats-to-dns",
@@ -578,6 +603,11 @@
       "name": "veris",
       "version": 2
     },
+    {
+      "description": "VMRay taxonomies to map VMRay Thread Identifier scores and artifacts.",
+      "name": "vmray",
+      "version": 1
+    },
     {
       "description": "Ce vocabulaire attribue des valeurs en pourcentage à certains énoncés de probabilité",
       "name": "vocabulaire-des-probabilites-estimatives",
@@ -589,6 +619,6 @@
       "version": 10
     }
   ],
-  "url": "https://raw.githubusercontent.com/MISP/misp-taxonomies/master/",
-  "version": "20200612"
+  "url": "https://raw.githubusercontent.com/MISP/misp-taxonomies/main/",
+  "version": "20210621"
 }

README.md

@@ -1,6 +1,6 @@
 # MISP Taxonomies
 
-[![Build Status](https://travis-ci.org/MISP/misp-taxonomies.svg?branch=master)](https://travis-ci.org/MISP/misp-taxonomies)
+![Python application](https://github.com/MISP/misp-taxonomies/workflows/Python%20application/badge.svg)
 
 MISP Taxonomies is a set of common classification libraries to tag, classify and organise information. Taxonomy allows to express the same vocabulary among a distributed set of users and organisations.
 
@@ -10,184 +10,622 @@ Taxonomies that can be used in [MISP](https://github.com/MISP/MISP) (2.4) and ot
 
 The following taxonomies can be used in MISP (as local or distributed tags) or in other tools and software willing to share common taxonomies among security information sharing tools.
 
-The following taxonomies are described:
+## List of available taxonomies
 
-- [access-method](./access-method)
-- [action-taken](./action-taken)
-- [Admiralty Scale](./admiralty-scale)
-- [adversary](./adversary) - description of an adversary infrastructure
-- [ais-marking](./ais-marking)
-- [analyst-assessment](./analyst-assessment)
-- [binary-class](./binary-class)
-- [CERT-XLM](./CERT-XLM)
-- CIRCL [Taxonomy - Schemes of Classification in Incident Response and Detection](./circl)
-- [The CSSA agreed sharing taxonomy](./cssa)
-- [Collaborative intelligence](./collaborative-intelligence) - 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. The objective of this language is to advance collaborative analysis and to share earlier than later.
-- [Cryptocurrency Threat](./cryptocurrency-threat) - Threats targetting cryptocurrency, based on CipherTrace report.
-- [Cyber Kill Chain](./kill-chain) from Lockheed Martin
-- [The Cyber Threat Framework](./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.
-- [Current Events](./current-events) - List of current events ranging from political to medical matters.
-- DE German (DE) [Government classification markings (VS)](./de-vs)
-- [DCSO Sharing Taxonomy](./dcso-sharing) - DCSO Sharing Taxonomy  to classify certain types of MISP events using the DCSO Event Guide
-- [DHS CIIP Sectors](./dhs-ciip-sectors)
-- [Diamond Model for Intrusion Analysis](./diamond-model)
-- [Detection Maturity Level](./DML)
-- [Domain Name Abuse](./domain-abuse)
-- [eCSIRT](./ecsirt) and IntelMQ incident classification
-- [ENISA](./enisa) ENISA Threat Taxonomy
-- [Estimative Language](./estimative-language) Estimative Language (ICD 203)
-- [EU NIS Critical Infrastructure Operators](./eu-marketop-and-publicadmin) - EU NIS Critical Infrastructure Operators
-- [EUCI](./euci) - EU classified information marking
-- [Europol Incident](./europol-incident) - Europol class of incident taxonomy
-- [Europol Events](./europol-event) - Europol type of events taxonomy
-- [FIRST CSIRT Case](./csirt_case_classification) classification
-- [FIRST Information Exchange Policy (IEP)](./iep) framework
-- [Information Security Indicators](./information-security-indicators) -  ETSI GS ISI 001-1 (V1.1.2): ISI Indicators
-- [Information Security Marking Metadata](./dni-ism) from DNI (Director of National Intelligence - US)
-- [Malware](./malware_classification) classification based on a SANS document
-- [ms-caro-malware](./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.
-- [NATO Classification Marking](./nato)
-- [Open Threat Taxonomy v1.1 (SANS)](./open_threat)
-- [OSINT Open Source Intelligence - Classification](./osint)
-- [Pandemic](./pandemic) - Pandemic events
-- [Ransomware](./ransomware)
-- [runtime-packer](./runtime-packer) - 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 o
-bfuscation techniques. This taxonomy lists all the known or official packer used for legitimate use or for packing malicious binaries.
-- [STIX-TTP](./stix-ttp) - Represents the behavior or modus operandi of cyber adversaries as normalized in STIX
-- [Stealth Malware Taxonomy as defined by Joanna Rutkowska](./stealth-malware)
-- [The Permissible Actions Protocol - or short: PAP - was designed to indicate how the received information can be used.](./PAP)
-- [Targeted Threat Index is a metric for assigning an overall threat ranking score to email messages that deliver malware to a victim’s computer.](./targeted-threat-index)
-- [TLP - Traffic Light Protocol](./tlp)
-- [Trust - Indicators of Trust](./trust)
-- [Type](./type)
-- [Vocabulaire des probabilités estimatives](./vocabulaire-des-probabilites-estimatives)
-- Vocabulary for Event Recording and Incident Sharing [VERIS](./veris)
-- [Binary Classification](./binary-class) safe/malicious binary tagging
-- [Workflow](./workflow) support language is a common language to support intelligence analysts to perform their analysis on data and information.
-- [file-type](./file-type) - List of known file types.
-- [iot](./iot) - Interbet of Things Taxonomy
+### CERT-XLM
 
-### [Admiralty Scale](./admiralty-scale)
+[CERT-XLM](https://github.com/MISP/misp-taxonomies/tree/main/CERT-XLM) :
+CERT-XLM Security Incident Classification. [Overview](https://www.misp-project.org/taxonomies.html#_CERT_XLM)
 
-The Admiralty Scale (also called the NATO System) is used to rank the reliability of a source and the credibility of an information.
+### DFRLab-dichotomies-of-disinformation
 
-### [Adversary](./adversary)
+[DFRLab-dichotomies-of-disinformation](https://github.com/MISP/misp-taxonomies/tree/main/DFRLab-dichotomies-of-disinformation) :
+DFRLab Dichotomies of Disinformation. [Overview](https://www.misp-project.org/taxonomies.html#_DFRLab_dichotomies_of_disinformation)
 
-An overview and description of the adversary infrastructure.
+### DML
 
-### CIRCL [Taxonomy - Schemes of Classification in Incident Response and Detection](./circl)
+[DML](https://github.com/MISP/misp-taxonomies/tree/main/DML) :
+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. [Overview](https://www.misp-project.org/taxonomies.html#_DML)
 
-CIRCL Taxonomy is a simple scheme for incident classification and area topic where the incident took place.
+### PAP
 
-### [Cyber Kill Chain](./kill-chain) from Lockheed Martin
+[PAP](https://github.com/MISP/misp-taxonomies/tree/main/PAP) :
+The Permissible Actions Protocol - or short: PAP - was designed to indicate how the received information can be used. [Overview](https://www.misp-project.org/taxonomies.html#_PAP)
 
-Cyber Kill Chain from Lockheed Martin as described in [Intelligence-Driven Computer Network Defense Informed by Analysis of Adversary Campaigns and Intrusion Kill Chains](http://www.lockheedmartin.com/content/dam/lockheed/data/corporate/documents/LM-White-Paper-Intel-Driven-Defense.pdf).
+### access-method
 
-### [Cyber Threat Framework](./cyber-threat-framework) from DNI.gov
+[access-method](https://github.com/MISP/misp-taxonomies/tree/main/access-method) :
+The access method used to remotely access a system. [Overview](https://www.misp-project.org/taxonomies.html#_access_method)
 
-[The Cyber Threat Framework was developed](https://www.dni.gov/index.php/cyber-threat-framework) 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.
+### accessnow
 
-### DE German (DE) [Government classification markings (VS)](./de-vs)
+[accessnow](https://github.com/MISP/misp-taxonomies/tree/main/accessnow) :
+Access Now classification to classify an issue (such as security, human rights, youth rights). [Overview](https://www.misp-project.org/taxonomies.html#_accessnow)
 
-Taxonomy for the handling of protectively marked information in MISP with German (DE) Government classification markings (VS).
+### action-taken
 
-### [DHS CIIP Sectors](./dhs-ciip-sectors)
+[action-taken](https://github.com/MISP/misp-taxonomies/tree/main/action-taken) :
+Action taken in the case of a security incident (CSIRT perspective). [Overview](https://www.misp-project.org/taxonomies.html#_action_taken)
 
-DHS critical sectors as described in https://www.dhs.gov/critical-infrastructure-sectors.
+### admiralty-scale
 
-### [Diamond Model for Intrusion Analysis](./diamond-model)
+[admiralty-scale](https://github.com/MISP/misp-taxonomies/tree/main/admiralty-scale) :
+The Admiralty Scale or Ranking (also called the NATO System) is used to rank the reliability of a source and the credibility of an information. Reference based on FM 2-22.3 (FM 34-52) HUMAN INTELLIGENCE COLLECTOR OPERATIONS and NATO documents. [Overview](https://www.misp-project.org/taxonomies.html#_admiralty_scale)
 
-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
-as described in [http://www.activeresponse.org/wp-content/uploads/2013/07/diamond.pdf](http://www.activeresponse.org/wp-content/uploads/2013/07/diamond.pdf).
+### adversary
 
-### [Detection Maturity Level](./DML)
+[adversary](https://github.com/MISP/misp-taxonomies/tree/main/adversary) :
+An overview and description of the adversary infrastructure [Overview](https://www.misp-project.org/taxonomies.html#_adversary)
 
-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.
+### ais-marking
 
-### [Domain Name Abuse](./domain-abuse)
+[ais-marking](https://github.com/MISP/misp-taxonomies/tree/main/ais-marking) :
+The AIS Marking Schema implementation is maintained by the National Cybersecurity and Communication Integration Center (NCCIC) of the U.S. Department of Homeland Security (DHS) [Overview](https://www.misp-project.org/taxonomies.html#_ais_marking)
 
-Taxonomy to tag domain names used for cybercrime.
-We suggest to use europol-incident(./europol-incident) to tag abuse-activity.
+### analyst-assessment
 
-### [eCSIRT](./ecsirt) and IntelMQ incident classification
+[analyst-assessment](https://github.com/MISP/misp-taxonomies/tree/main/analyst-assessment) :
+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. [Overview](https://www.misp-project.org/taxonomies.html#_analyst_assessment)
 
-eCSIRT incident classification Appendix C of the eCSIRT EU project including IntelMQ updates.
+### approved-category-of-action
 
-### [ENISA](./enisa) ENISA Threat Taxonomy
+[approved-category-of-action](https://github.com/MISP/misp-taxonomies/tree/main/approved-category-of-action) :
+A pre-approved category of action for indicators being shared with partners (MIMIC). [Overview](https://www.misp-project.org/taxonomies.html#_approved_category_of_action)
 
-ENISA Threat Taxonomy - A tool for structuring threat information [as published](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)
+### binary-class
 
-### [Estimative Language](./estimative-language) Estimative Language (ICD 203)
+[binary-class](https://github.com/MISP/misp-taxonomies/tree/main/binary-class) :
+Custom taxonomy for types of binary file. [Overview](https://www.misp-project.org/taxonomies.html#_binary_class)
 
-Estimative language - including likelihood or probability of event based on the Intelligence Community Directive 203 (ICD 203) (6.2.(a)).
+### cccs
 
-### [EU NIS Critical Infrastructure Operators](./eu-marketop-and-publicadmin)
+[cccs](https://github.com/MISP/misp-taxonomies/tree/main/cccs) :
+Internal taxonomy for CCCS. [Overview](https://www.misp-project.org/taxonomies.html#_cccs)
 
-Market operators and public administrations that must comply to some notifications requirements under EU NIS directive.
+### circl
 
-### [EUCI](./euci) classification
+[circl](https://github.com/MISP/misp-taxonomies/tree/main/circl) :
+CIRCL Taxonomy - Schemes of Classification in Incident Response and Detection [Overview](https://www.misp-project.org/taxonomies.html#_circl)
 
-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](http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32013D0488&from=EN).
+### coa
 
-### [Europol Incident](./europol-incident)
+[coa](https://github.com/MISP/misp-taxonomies/tree/main/coa) :
+Course of action taken within organization to discover, detect, deny, disrupt, degrade, deceive and/or destroy an attack. [Overview](https://www.misp-project.org/taxonomies.html#_coa)
 
-EUROPOL class of incident taxonomy
+### collaborative-intelligence
 
-### [Europol Events](./europol-event)
+[collaborative-intelligence](https://github.com/MISP/misp-taxonomies/tree/main/collaborative-intelligence) :
+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. The objective of this language is to advance collaborative analysis and to share earlier than later. [Overview](https://www.misp-project.org/taxonomies.html#_collaborative_intelligence)
 
-EUROPOL type of events taxonomy
+### common-taxonomy
 
-### [FIRST CSIRT Case](./csirt_case_classification) classification
+[common-taxonomy](https://github.com/MISP/misp-taxonomies/tree/main/common-taxonomy) :
+Common Taxonomy for Law enforcement and CSIRTs [Overview](https://www.misp-project.org/taxonomies.html#_common_taxonomy)
 
-FIRST CSIRT Case Classification.
+### copine-scale
 
-### [FIRST Information Exchange Policy (IEP)](./iep) framework
+[copine-scale](https://github.com/MISP/misp-taxonomies/tree/main/copine-scale) :
+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. The scale was developed by staff at the COPINE (Combating Paedophile Information Networks in Europe) project. The COPINE Project was founded in 1997, and is based in the Department of Applied Psychology, University College Cork, Ireland. [Overview](https://www.misp-project.org/taxonomies.html#_copine_scale)
 
-### [Information Security Indicators](./information-security-indicators) -  ETSI GS ISI 001-1 (V1.1.2): ISI Indicators
+### course-of-action
 
-Information security indicators have been standardized by the [ETSI Industrial Specification Group (ISG) ISI](http://www.etsi.org/technologies-clusters/technologies/information-security-indicators). 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).
+[course-of-action](https://github.com/MISP/misp-taxonomies/tree/main/course-of-action) :
+A Course Of Action analysis considers six potential courses of action for the development of a cyber security capability. [Overview](https://www.misp-project.org/taxonomies.html#_course_of_action)
 
-### [Information Security Marking Metadata](./dni-ism) DNI (Director of National Intelligence - US)
+### cryptocurrency-threat
 
-ISM (Information Security Marking Metadata) [V13](http://www.dni.gov/index.php/about/organization/chief-information-officer/information-security-marking-metadata) as described by DNI.gov.
+[cryptocurrency-threat](https://github.com/MISP/misp-taxonomies/tree/main/cryptocurrency-threat) :
+Threats targetting cryptocurrency, based on CipherTrace report. [Overview](https://www.misp-project.org/taxonomies.html#_cryptocurrency_threat)
 
-### [Malware](./malware_classification) classification
+### csirt-americas
 
-Malware classification based on a [SANS whitepaper about malware](https://www.sans.org/reading-room/whitepapers/incident/malware-101-viruses-32848).
+[csirt-americas](https://github.com/MISP/misp-taxonomies/tree/main/csirt-americas) :
+Taxonomía CSIRT Américas. [Overview](https://www.misp-project.org/taxonomies.html#_csirt_americas)
 
-### [ms-caro-malware](./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.
+### csirt_case_classification
 
-### [NATO Classification Marking](./nato)
+[csirt_case_classification](https://github.com/MISP/misp-taxonomies/tree/main/csirt_case_classification) :
+It is critical that the CSIRT provide consistent and timely response to the customer, and that sensitive information is handled appropriately.  This document provides the guidelines needed for CSIRT Incident Managers (IM) to classify the case category, criticality level, and sensitivity level for each CSIRT case.  This information will be entered into the Incident Tracking System (ITS) when a case is created.  Consistent case classification is required for the CSIRT to provide accurate reporting to management on a regular basis.  In addition, the classifications will provide CSIRT IM’s with proper case handling procedures and will form the basis of SLA’s between the CSIRT and other Company departments. [Overview](https://www.misp-project.org/taxonomies.html#_csirt_case_classification)
 
-Marking of Classified and Unclassified materials as described by the North Atlantic Treaty Organization, NATO.
+### cssa
 
-### [Open Threat Taxonomy v1.1](./open_threat)
+[cssa](https://github.com/MISP/misp-taxonomies/tree/main/cssa) :
+The CSSA agreed sharing taxonomy. [Overview](https://www.misp-project.org/taxonomies.html#_cssa)
 
-Open Threat Taxonomy v1.1 base on James Tarala of SANS [ref](http://www.auditscripts.com/resources/open_threat_taxonomy_v1.1a.pdf).
+### cti
 
-### [STIX-TTP](./stix-ttp)
+[cti](https://github.com/MISP/misp-taxonomies/tree/main/cti) :
+Cyber Threat Intelligence cycle to control workflow state of your process. [Overview](https://www.misp-project.org/taxonomies.html#_cti)
 
-STIX-TTP exposes a set classification tools that represents the behavior or modus operandi of cyber adversaries as normalized in STIX. TTPs consist of the specific adversary behavior (attack patterns, malware, exploits) exhibited, resources leveraged (tools, infrastructure, personas), information on the victims targeted (who, what or where), relevant ExploitTargets being targeted, intended effects, relevant kill chain phases, handling guidance, source of the TTP information, etc.
+### current-event
 
-### [Targeted Threat Index is a metric for assigning an overall threat ranking score to email messages that deliver malware to a victim’s computer.](./targeted-threat-index)
+[current-event](https://github.com/MISP/misp-taxonomies/tree/main/current-event) :
+Current events - Schemes of Classification in Incident Response and Detection [Overview](https://www.misp-project.org/taxonomies.html#_current_event)
 
-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. [More info about TTI](https://citizenlab.org/2013/10/targeted-threat-index/).
+### cyber-threat-framework
 
-### [The Permissible Actions Protocol - or short: PAP - was designed to indicate how the received information can be used.](./PAP)
+[cyber-threat-framework](https://github.com/MISP/misp-taxonomies/tree/main/cyber-threat-framework) :
+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 [Overview](https://www.misp-project.org/taxonomies.html#_cyber_threat_framework)
 
-The Permissible Actions Protocol - or short: PAP - was designed to indicate how the received information can be used. It's a protocol/taxonomy similar to TLP informing the recipients of information what they can do with the received information.
+### cycat
 
-### [TLP - Traffic Light Protocol](./tlp)
+[cycat](https://github.com/MISP/misp-taxonomies/tree/main/cycat) :
+Taxonomy used by CyCAT, the Universal Cybersecurity Resource Catalogue, to categorize the namespaces it supports and uses. [Overview](https://www.misp-project.org/taxonomies.html#_cycat)
 
-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.
+### cytomic-orion
 
-### [Trust - Indicators of Trust](./trust)
+[cytomic-orion](https://github.com/MISP/misp-taxonomies/tree/main/cytomic-orion) :
+Taxonomy to describe desired actions for Cytomic Orion [Overview](https://www.misp-project.org/taxonomies.html#_cytomic_orion)
 
-The Trust Taxonomy provides a way to use Indicators of Trust within MISP to get insight on data about what can be trusted. Similar to a whitelist but on steroids, leveraging MISP features one would use with Inidicators of Compromise, but to filter out what is known to be good.
+### dark-web
 
-### Vocabulary for Event Recording and Incident Sharing [VERIS](./veris)
+[dark-web](https://github.com/MISP/misp-taxonomies/tree/main/dark-web) :
+Criminal motivation on the dark web: A categorisation model for law enforcement. ref: Janis Dalins, Campbell Wilson, Mark Carman. Taxonomy updated by MISP Project [Overview](https://www.misp-project.org/taxonomies.html#_dark_web)
 
-Vocabulary for Event Recording and Incident Sharing is a format created by the [VERIS community](http://veriscommunity.net/).
+### data-classification
+
+[data-classification](https://github.com/MISP/misp-taxonomies/tree/main/data-classification) :
+Data classification for data potentially at risk of exfiltration based on table 2.1 of Solving Cyber Risk book. [Overview](https://www.misp-project.org/taxonomies.html#_data_classification)
+
+### dcso-sharing
+
+[dcso-sharing](https://github.com/MISP/misp-taxonomies/tree/main/dcso-sharing) :
+Taxonomy defined in the DCSO MISP Event Guide. It provides guidance for the creation and consumption of MISP events in a way that minimises the extra effort for the sending party, while enhancing the usefulness for receiving parties. [Overview](https://www.misp-project.org/taxonomies.html#_dcso_sharing)
+
+### ddos
+
+[ddos](https://github.com/MISP/misp-taxonomies/tree/main/ddos) :
+Distributed Denial of Service - or short: DDoS - taxonomy supports the description of Denial of Service attacks and especially the types they belong too. [Overview](https://www.misp-project.org/taxonomies.html#_ddos)
+
+### de-vs
+
+[de-vs](https://github.com/MISP/misp-taxonomies/tree/main/de-vs) :
+German (DE) Government classification markings (VS). [Overview](https://www.misp-project.org/taxonomies.html#_de_vs)
+
+### dhs-ciip-sectors
+
+[dhs-ciip-sectors](https://github.com/MISP/misp-taxonomies/tree/main/dhs-ciip-sectors) :
+DHS critical sectors as in https://www.dhs.gov/critical-infrastructure-sectors [Overview](https://www.misp-project.org/taxonomies.html#_dhs_ciip_sectors)
+
+### diamond-model
+
+[diamond-model](https://github.com/MISP/misp-taxonomies/tree/main/diamond-model) :
+The Diamond Model for Intrusion Analysis establishes the basic atomic element of any intrusion activity, the event, composed of four core features: adversary, infrastructure, capability, and victim. [Overview](https://www.misp-project.org/taxonomies.html#_diamond_model)
+
+### dni-ism
+
+[dni-ism](https://github.com/MISP/misp-taxonomies/tree/main/dni-ism) :
+A subset of Information Security Marking Metadata ISM as required by Executive Order (EO) 13526. As described by DNI.gov as Data Encoding Specifications for Information Security Marking Metadata in Controlled Vocabulary Enumeration Values for ISM [Overview](https://www.misp-project.org/taxonomies.html#_dni_ism)
+
+### domain-abuse
+
+[domain-abuse](https://github.com/MISP/misp-taxonomies/tree/main/domain-abuse) :
+Domain Name Abuse - taxonomy to tag domain names used for cybercrime. [Overview](https://www.misp-project.org/taxonomies.html#_domain_abuse)
+
+### drugs
+
+[drugs](https://github.com/MISP/misp-taxonomies/tree/main/drugs) :
+A taxonomy based on the superclass and class of drugs. Based on https://www.drugbank.ca/releases/latest [Overview](https://www.misp-project.org/taxonomies.html#_drugs)
+
+### economical-impact
+
+[economical-impact](https://github.com/MISP/misp-taxonomies/tree/main/economical-impact) :
+Economical impact is a taxonomy to describe the financial impact as positive or negative gain to the tagged information (e.g. data exfiltration loss, a positive gain for an adversary). [Overview](https://www.misp-project.org/taxonomies.html#_economical_impact)
+
+### ecsirt
+
+[ecsirt](https://github.com/MISP/misp-taxonomies/tree/main/ecsirt) :
+Incident Classification by the ecsirt.net version mkVI of 31 March 2015 enriched with IntelMQ taxonomy-type mapping. [Overview](https://www.misp-project.org/taxonomies.html#_ecsirt)
+
+### enisa
+
+[enisa](https://github.com/MISP/misp-taxonomies/tree/main/enisa) :
+The present threat taxonomy is an initial version that has been developed on the basis of available ENISA material. This material has been used as an ENISA-internal structuring aid for information collection and threat consolidation purposes. It emerged in the time period 2012-2015. [Overview](https://www.misp-project.org/taxonomies.html#_enisa)
+
+### estimative-language
+
+[estimative-language](https://github.com/MISP/misp-taxonomies/tree/main/estimative-language) :
+Estimative language to describe quality and credibility of underlying sources, data, and methodologies based Intelligence Community Directive 203 (ICD 203) and JP 2-0, Joint Intelligence [Overview](https://www.misp-project.org/taxonomies.html#_estimative_language)
+
+### eu-marketop-and-publicadmin
+
+[eu-marketop-and-publicadmin](https://github.com/MISP/misp-taxonomies/tree/main/eu-marketop-and-publicadmin) :
+Market operators and public administrations that must comply to some notifications requirements under EU NIS directive [Overview](https://www.misp-project.org/taxonomies.html#_eu_marketop_and_publicadmin)
+
+### eu-nis-sector-and-subsectors
+
+[eu-nis-sector-and-subsectors](https://github.com/MISP/misp-taxonomies/tree/main/eu-nis-sector-and-subsectors) :
+Sectors, subsectors, and digital services as identified by the NIS Directive [Overview](https://www.misp-project.org/taxonomies.html#_eu_nis_sector_and_subsectors)
+
+### euci
+
+[euci](https://github.com/MISP/misp-taxonomies/tree/main/euci) :
+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. [Overview](https://www.misp-project.org/taxonomies.html#_euci)
+
+### europol-event
+
+[europol-event](https://github.com/MISP/misp-taxonomies/tree/main/europol-event) :
+This taxonomy was designed to describe the type of events [Overview](https://www.misp-project.org/taxonomies.html#_europol_event)
+
+### europol-incident
+
+[europol-incident](https://github.com/MISP/misp-taxonomies/tree/main/europol-incident) :
+This taxonomy was designed to describe the type of incidents by class. [Overview](https://www.misp-project.org/taxonomies.html#_europol_incident)
+
+### event-assessment
+
+[event-assessment](https://github.com/MISP/misp-taxonomies/tree/main/event-assessment) :
+A series of assessment predicates describing the event assessment performed to make judgement(s) under a certain level of uncertainty. [Overview](https://www.misp-project.org/taxonomies.html#_event_assessment)
+
+### event-classification
+
+[event-classification](https://github.com/MISP/misp-taxonomies/tree/main/event-classification) :
+Classification of events as seen in tools such as RT/IR, MISP and other [Overview](https://www.misp-project.org/taxonomies.html#_event_classification)
+
+### exercise
+
+[exercise](https://github.com/MISP/misp-taxonomies/tree/main/exercise) :
+Exercise is a taxonomy to describe if the information is part of one or more cyber or crisis exercise. [Overview](https://www.misp-project.org/taxonomies.html#_exercise)
+
+### extended-event
+
+[extended-event](https://github.com/MISP/misp-taxonomies/tree/main/extended-event) :
+Reasons why an event has been extended.  [Overview](https://www.misp-project.org/taxonomies.html#_extended_event)
+
+### failure-mode-in-machine-learning
+
+[failure-mode-in-machine-learning](https://github.com/MISP/misp-taxonomies/tree/main/failure-mode-in-machine-learning) :
+The purpose of this taxonomy is to jointly tabulate both the of these failure modes in a single place. Intentional failures wherein the failure is caused by an active adversary attempting to subvert the system to attain her goals – either to misclassify the result, infer private training data, or to steal the underlying algorithm. Unintentional failures wherein the failure is because an ML system produces a formally correct but completely unsafe outcome. [Overview](https://www.misp-project.org/taxonomies.html#_failure_mode_in_machine_learning)
+
+### false-positive
+
+[false-positive](https://github.com/MISP/misp-taxonomies/tree/main/false-positive) :
+This taxonomy aims to ballpark the expected amount of false positives. [Overview](https://www.misp-project.org/taxonomies.html#_false_positive)
+
+### file-type
+
+[file-type](https://github.com/MISP/misp-taxonomies/tree/main/file-type) :
+List of known file types. [Overview](https://www.misp-project.org/taxonomies.html#_file_type)
+
+### flesch-reading-ease
+
+[flesch-reading-ease](https://github.com/MISP/misp-taxonomies/tree/main/flesch-reading-ease) :
+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). [Overview](https://www.misp-project.org/taxonomies.html#_flesch_reading_ease)
+
+### fpf
+
+[fpf](https://github.com/MISP/misp-taxonomies/tree/main/fpf) :
+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. [Overview](https://www.misp-project.org/taxonomies.html#_fpf)
+
+### fr-classif
+
+[fr-classif](https://github.com/MISP/misp-taxonomies/tree/main/fr-classif) :
+French gov information classification system [Overview](https://www.misp-project.org/taxonomies.html#_fr_classif)
+
+### gdpr
+
+[gdpr](https://github.com/MISP/misp-taxonomies/tree/main/gdpr) :
+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) [Overview](https://www.misp-project.org/taxonomies.html#_gdpr)
+
+### gea-nz-activities
+
+[gea-nz-activities](https://github.com/MISP/misp-taxonomies/tree/main/gea-nz-activities) :
+Information needed to track or monitor moments, periods or events that occur over time. This type of information is focused on occurrences that must be tracked for business reasons or represent a specific point in the evolution of ‘The Business’. [Overview](https://www.misp-project.org/taxonomies.html#_gea_nz_activities)
+
+### gea-nz-entities
+
+[gea-nz-entities](https://github.com/MISP/misp-taxonomies/tree/main/gea-nz-entities) :
+Information relating to instances of entities or things. [Overview](https://www.misp-project.org/taxonomies.html#_gea_nz_entities)
+
+### gea-nz-motivators
+
+[gea-nz-motivators](https://github.com/MISP/misp-taxonomies/tree/main/gea-nz-motivators) :
+Information relating to authority or governance. [Overview](https://www.misp-project.org/taxonomies.html#_gea_nz_motivators)
+
+### gsma-attack-category
+
+[gsma-attack-category](https://github.com/MISP/misp-taxonomies/tree/main/gsma-attack-category) :
+Taxonomy used by GSMA for their information sharing program with telco describing the attack categories [Overview](https://www.misp-project.org/taxonomies.html#_gsma_attack_category)
+
+### gsma-fraud
+
+[gsma-fraud](https://github.com/MISP/misp-taxonomies/tree/main/gsma-fraud) :
+Taxonomy used by GSMA for their information sharing program with telco describing the various aspects of fraud [Overview](https://www.misp-project.org/taxonomies.html#_gsma_fraud)
+
+### gsma-network-technology
+
+[gsma-network-technology](https://github.com/MISP/misp-taxonomies/tree/main/gsma-network-technology) :
+Taxonomy used by GSMA for their information sharing program with telco describing the types of infrastructure. WiP [Overview](https://www.misp-project.org/taxonomies.html#_gsma_network_technology)
+
+### honeypot-basic
+
+[honeypot-basic](https://github.com/MISP/misp-taxonomies/tree/main/honeypot-basic) :
+Updated (CIRCL, Seamus Dowling and EURECOM) from 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 [Overview](https://www.misp-project.org/taxonomies.html#_honeypot_basic)
+
+### ics
+
+[ics](https://github.com/MISP/misp-taxonomies/tree/main/ics) :
+FIRST.ORG CTI SIG - MISP Proposal for ICS/OT Threat Attribution (IOC) Project [Overview](https://www.misp-project.org/taxonomies.html#_ics)
+
+### iep
+
+[iep](https://github.com/MISP/misp-taxonomies/tree/main/iep) :
+Forum of Incident Response and Security Teams (FIRST) Information Exchange Policy (IEP) framework [Overview](https://www.misp-project.org/taxonomies.html#_iep)
+
+### iep2-policy
+
+[iep2-policy](https://github.com/MISP/misp-taxonomies/tree/main/iep2-policy) :
+Forum of Incident Response and Security Teams (FIRST) Information Exchange Policy (IEP) v2.0 Policy [Overview](https://www.misp-project.org/taxonomies.html#_iep2_policy)
+
+### iep2-reference
+
+[iep2-reference](https://github.com/MISP/misp-taxonomies/tree/main/iep2-reference) :
+Forum of Incident Response and Security Teams (FIRST) Information Exchange Policy (IEP) v2.0 Reference [Overview](https://www.misp-project.org/taxonomies.html#_iep2_reference)
+
+### ifx-vetting
+
+[ifx-vetting](https://github.com/MISP/misp-taxonomies/tree/main/ifx-vetting) :
+The IFX taxonomy is used to categorise information (MISP events and attributes) to aid in the intelligence vetting process [Overview](https://www.misp-project.org/taxonomies.html#_ifx_vetting)
+
+### incident-disposition
+
+[incident-disposition](https://github.com/MISP/misp-taxonomies/tree/main/incident-disposition) :
+How an incident is classified in its process to be resolved. The taxonomy is inspired from NASA Incident Response and Management Handbook. https://www.nasa.gov/pdf/589502main_ITS-HBK-2810.09-02%20%5bNASA%20Information%20Security%20Incident%20Management%5d.pdf#page=9 [Overview](https://www.misp-project.org/taxonomies.html#_incident_disposition)
+
+### infoleak
+
+[infoleak](https://github.com/MISP/misp-taxonomies/tree/main/infoleak) :
+A taxonomy describing information leaks and especially information classified as being potentially leaked. The taxonomy is based on the work by CIRCL on the AIL framework. The taxonomy aim is to be used at large to improve classification of leaked information. [Overview](https://www.misp-project.org/taxonomies.html#_infoleak)
+
+### information-security-data-source
+
+[information-security-data-source](https://github.com/MISP/misp-taxonomies/tree/main/information-security-data-source) :
+Taxonomy to classify the information security data sources. [Overview](https://www.misp-project.org/taxonomies.html#_information_security_data_source)
+
+### information-security-indicators
+
+[information-security-indicators](https://github.com/MISP/misp-taxonomies/tree/main/information-security-indicators) :
+A full set of operational indicators for organizations to use to benchmark their security posture. [Overview](https://www.misp-project.org/taxonomies.html#_information_security_indicators)
+
+### interception-method
+
+[interception-method](https://github.com/MISP/misp-taxonomies/tree/main/interception-method) :
+The interception method used to intercept traffic. [Overview](https://www.misp-project.org/taxonomies.html#_interception_method)
+
+### ioc
+
+[ioc](https://github.com/MISP/misp-taxonomies/tree/main/ioc) :
+An IOC classification to facilitate automation of malicious and non malicious artifacts [Overview](https://www.misp-project.org/taxonomies.html#_ioc)
+
+### iot
+
+[iot](https://github.com/MISP/misp-taxonomies/tree/main/iot) :
+Internet of Things taxonomy, based on IOT UK report https://iotuk.org.uk/wp-content/uploads/2017/01/IOT-Taxonomy-Report.pdf [Overview](https://www.misp-project.org/taxonomies.html#_iot)
+
+### kill-chain
+
+[kill-chain](https://github.com/MISP/misp-taxonomies/tree/main/kill-chain) :
+The Cyber Kill Chain, a phase-based model developed by Lockheed Martin, aims to help categorise and identify the stage of an attack. [Overview](https://www.misp-project.org/taxonomies.html#_kill_chain)
+
+### maec-delivery-vectors
+
+[maec-delivery-vectors](https://github.com/MISP/misp-taxonomies/tree/main/maec-delivery-vectors) :
+Vectors used to deliver malware based on MAEC 5.0 [Overview](https://www.misp-project.org/taxonomies.html#_maec_delivery_vectors)
+
+### maec-malware-behavior
+
+[maec-malware-behavior](https://github.com/MISP/misp-taxonomies/tree/main/maec-malware-behavior) :
+Malware behaviours based on MAEC 5.0 [Overview](https://www.misp-project.org/taxonomies.html#_maec_malware_behavior)
+
+### maec-malware-capabilities
+
+[maec-malware-capabilities](https://github.com/MISP/misp-taxonomies/tree/main/maec-malware-capabilities) :
+Malware Capabilities based on MAEC 5.0 [Overview](https://www.misp-project.org/taxonomies.html#_maec_malware_capabilities)
+
+### maec-malware-obfuscation-methods
+
+[maec-malware-obfuscation-methods](https://github.com/MISP/misp-taxonomies/tree/main/maec-malware-obfuscation-methods) :
+Obfuscation methods used by malware based on MAEC 5.0 [Overview](https://www.misp-project.org/taxonomies.html#_maec_malware_obfuscation_methods)
+
+### malware_classification
+
+[malware_classification](https://github.com/MISP/misp-taxonomies/tree/main/malware_classification) :
+Classification based on different categories. Based on https://www.sans.org/reading-room/whitepapers/incident/malware-101-viruses-32848 [Overview](https://www.misp-project.org/taxonomies.html#_malware_classification)
+
+### misinformation-website-label
+
+[misinformation-website-label](https://github.com/MISP/misp-taxonomies/tree/main/misinformation-website-label) :
+classification for the identification of type of misinformation among websites. Source:False, Misleading, Clickbait-y, and/or Satirical News Sources by Melissa Zimdars 2019 [Overview](https://www.misp-project.org/taxonomies.html#_misinformation_website_label)
+
+### misp
+
+[misp](https://github.com/MISP/misp-taxonomies/tree/main/misp) :
+MISP taxonomy to infer with MISP behavior or operation. [Overview](https://www.misp-project.org/taxonomies.html#_misp)
+
+### monarc-threat
+
+[monarc-threat](https://github.com/MISP/misp-taxonomies/tree/main/monarc-threat) :
+MONARC Threats Taxonomy [Overview](https://www.misp-project.org/taxonomies.html#_monarc_threat)
+
+### ms-caro-malware
+
+[ms-caro-malware](https://github.com/MISP/misp-taxonomies/tree/main/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. Based on https://www.microsoft.com/en-us/security/portal/mmpc/shared/malwarenaming.aspx, https://www.microsoft.com/security/portal/mmpc/shared/glossary.aspx, https://www.microsoft.com/security/portal/mmpc/shared/objectivecriteria.aspx, and http://www.caro.org/definitions/index.html. Malware families are extracted from Microsoft SIRs since 2008 based on https://www.microsoft.com/security/sir/archive/default.aspx and https://www.microsoft.com/en-us/security/portal/threat/threats.aspx. Note that SIRs do NOT include all Microsoft malware families. [Overview](https://www.misp-project.org/taxonomies.html#_ms_caro_malware)
+
+### ms-caro-malware-full
+
+[ms-caro-malware-full](https://github.com/MISP/misp-taxonomies/tree/main/ms-caro-malware-full) :
+Malware Type and Platform classification based on Microsoft's implementation of the Computer Antivirus Research Organization (CARO) Naming Scheme and Malware Terminology. Based on https://www.microsoft.com/en-us/security/portal/mmpc/shared/malwarenaming.aspx, https://www.microsoft.com/security/portal/mmpc/shared/glossary.aspx, https://www.microsoft.com/security/portal/mmpc/shared/objectivecriteria.aspx, and http://www.caro.org/definitions/index.html. Malware families are extracted from Microsoft SIRs since 2008 based on https://www.microsoft.com/security/sir/archive/default.aspx and https://www.microsoft.com/en-us/security/portal/threat/threats.aspx. Note that SIRs do NOT include all Microsoft malware families. [Overview](https://www.misp-project.org/taxonomies.html#_ms_caro_malware_full)
+
+### mwdb
+
+[mwdb](https://github.com/MISP/misp-taxonomies/tree/main/mwdb) :
+Malware Database (mwdb) Taxonomy - Tags used across the platform [Overview](https://www.misp-project.org/taxonomies.html#_mwdb)
+
+### nato
+
+[nato](https://github.com/MISP/misp-taxonomies/tree/main/nato) :
+NATO classification markings. [Overview](https://www.misp-project.org/taxonomies.html#_nato)
+
+### nis
+
+[nis](https://github.com/MISP/misp-taxonomies/tree/main/nis) :
+The taxonomy is meant for large scale cybersecurity incidents, as mentioned in the Commission Recommendation of 13 September 2017, also known as the blueprint. It has two core parts: The nature of the incident, i.e. the underlying cause, that triggered the incident, and the impact of the incident, i.e. the impact on services, in which sector(s) of economy and society. [Overview](https://www.misp-project.org/taxonomies.html#_nis)
+
+### open_threat
+
+[open_threat](https://github.com/MISP/misp-taxonomies/tree/main/open_threat) :
+Open Threat Taxonomy v1.1 base on James Tarala of SANS http://www.auditscripts.com/resources/open_threat_taxonomy_v1.1a.pdf, https://files.sans.org/summit/Threat_Hunting_Incident_Response_Summit_2016/PDFs/Using-Open-Tools-to-Convert-Threat-Intelligence-into-Practical-Defenses-James-Tarala-SANS-Institute.pdf, https://www.youtube.com/watch?v=5rdGOOFC_yE, and https://www.rsaconference.com/writable/presentations/file_upload/str-r04_using-an-open-source-threat-model-for-prioritized-defense-final.pdf [Overview](https://www.misp-project.org/taxonomies.html#_open_threat)
+
+### osint
+
+[osint](https://github.com/MISP/misp-taxonomies/tree/main/osint) :
+Open Source Intelligence - Classification (MISP taxonomies) [Overview](https://www.misp-project.org/taxonomies.html#_osint)
+
+### pandemic
+
+[pandemic](https://github.com/MISP/misp-taxonomies/tree/main/pandemic) :
+Pandemic [Overview](https://www.misp-project.org/taxonomies.html#_pandemic)
+
+### passivetotal
+
+[passivetotal](https://github.com/MISP/misp-taxonomies/tree/main/passivetotal) :
+Tags from RiskIQ's PassiveTotal service [Overview](https://www.misp-project.org/taxonomies.html#_passivetotal)
+
+### pentest
+
+[pentest](https://github.com/MISP/misp-taxonomies/tree/main/pentest) :
+Penetration test (pentest) classification. [Overview](https://www.misp-project.org/taxonomies.html#_pentest)
+
+### phishing
+
+[phishing](https://github.com/MISP/misp-taxonomies/tree/main/phishing) :
+Taxonomy to classify phishing attacks including techniques, collection mechanisms and analysis status. [Overview](https://www.misp-project.org/taxonomies.html#_phishing)
+
+### priority-level
+
+[priority-level](https://github.com/MISP/misp-taxonomies/tree/main/priority-level) :
+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. [Overview](https://www.misp-project.org/taxonomies.html#_priority_level)
+
+### ransomware
+
+[ransomware](https://github.com/MISP/misp-taxonomies/tree/main/ransomware) :
+Ransomware is used to define ransomware types and the elements that compose them. [Overview](https://www.misp-project.org/taxonomies.html#_ransomware)
+
+### retention
+
+[retention](https://github.com/MISP/misp-taxonomies/tree/main/retention) :
+Add a retenion time to events to automatically remove the IDS-flag on ip-dst or ip-src attributes. We calculate the time elapsed based on the date of the event. Supported time units are: d(ays), w(eeks), m(onths), y(ears). The numerical_value is just for sorting in the web-interface and is not used for calculations. [Overview](https://www.misp-project.org/taxonomies.html#_retention)
+
+### rsit
+
+[rsit](https://github.com/MISP/misp-taxonomies/tree/main/rsit) :
+Reference Security Incident Classification Taxonomy [Overview](https://www.misp-project.org/taxonomies.html#_rsit)
+
+### rt_event_status
+
+[rt_event_status](https://github.com/MISP/misp-taxonomies/tree/main/rt_event_status) :
+Status of events used in Request Tracker. [Overview](https://www.misp-project.org/taxonomies.html#_rt_event_status)
+
+### runtime-packer
+
+[runtime-packer](https://github.com/MISP/misp-taxonomies/tree/main/runtime-packer) :
+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. [Overview](https://www.misp-project.org/taxonomies.html#_runtime_packer)
+
+### scrippsco2-fgc
+
+[scrippsco2-fgc](https://github.com/MISP/misp-taxonomies/tree/main/scrippsco2-fgc) :
+Flags describing the sample [Overview](https://www.misp-project.org/taxonomies.html#_scrippsco2_fgc)
+
+### scrippsco2-fgi
+
+[scrippsco2-fgi](https://github.com/MISP/misp-taxonomies/tree/main/scrippsco2-fgi) :
+Flags describing the sample for isotopic data (C14, O18) [Overview](https://www.misp-project.org/taxonomies.html#_scrippsco2_fgi)
+
+### scrippsco2-sampling-stations
+
+[scrippsco2-sampling-stations](https://github.com/MISP/misp-taxonomies/tree/main/scrippsco2-sampling-stations) :
+Sampling stations of the Scripps CO2 Program [Overview](https://www.misp-project.org/taxonomies.html#_scrippsco2_sampling_stations)
+
+### smart-airports-threats
+
+[smart-airports-threats](https://github.com/MISP/misp-taxonomies/tree/main/smart-airports-threats) :
+Threat taxonomy in the scope of securing smart airports by ENISA. https://www.enisa.europa.eu/publications/securing-smart-airports [Overview](https://www.misp-project.org/taxonomies.html#_smart_airports_threats)
+
+### stealth_malware
+
+[stealth_malware](https://github.com/MISP/misp-taxonomies/tree/main/stealth_malware) :
+Classification based on malware stealth techniques. Described in https://vxheaven.org/lib/pdf/Introducing%20Stealth%20Malware%20Taxonomy.pdf [Overview](https://www.misp-project.org/taxonomies.html#_stealth_malware)
+
+### stix-ttp
+
+[stix-ttp](https://github.com/MISP/misp-taxonomies/tree/main/stix-ttp) :
+TTPs are representations of the behavior or modus operandi of cyber adversaries. [Overview](https://www.misp-project.org/taxonomies.html#_stix_ttp)
+
+### targeted-threat-index
+
+[targeted-threat-index](https://github.com/MISP/misp-taxonomies/tree/main/targeted-threat-index) :
+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. [Overview](https://www.misp-project.org/taxonomies.html#_targeted_threat_index)
+
+### thales_group
+
+[thales_group](https://github.com/MISP/misp-taxonomies/tree/main/thales_group) :
+Thales Group Taxonomy - was designed with the aim of enabling desired sharing and preventing unwanted sharing between Thales Group security communities. [Overview](https://www.misp-project.org/taxonomies.html#_thales_group)
+
+### threatmatch
+
+[threatmatch](https://github.com/MISP/misp-taxonomies/tree/main/threatmatch) :
+The ThreatMatch Sectors, Incident types, Malware types and Alert types are applicable for any ThreatMatch instances and should be used for all CIISI and TIBER Projects. [Overview](https://www.misp-project.org/taxonomies.html#_threatmatch)
+
+### threats-to-dns
+
+[threats-to-dns](https://github.com/MISP/misp-taxonomies/tree/main/threats-to-dns) :
+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 [Overview](https://www.misp-project.org/taxonomies.html#_threats_to_dns)
+
+### tlp
+
+[tlp](https://github.com/MISP/misp-taxonomies/tree/main/tlp) :
+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. [Overview](https://www.misp-project.org/taxonomies.html#_tlp)
+
+### tor
+
+[tor](https://github.com/MISP/misp-taxonomies/tree/main/tor) :
+Taxonomy to describe Tor network infrastructure [Overview](https://www.misp-project.org/taxonomies.html#_tor)
+
+### trust
+
+[trust](https://github.com/MISP/misp-taxonomies/tree/main/trust) :
+The Indicator of Trust provides insight about data on what can be trusted and known as a good actor. Similar to a whitelist but on steroids, reusing features one would use with Indicators of Compromise, but to filter out what is known to be good. [Overview](https://www.misp-project.org/taxonomies.html#_trust)
+
+### type
+
+[type](https://github.com/MISP/misp-taxonomies/tree/main/type) :
+Taxonomy to describe different types of intelligence gathering discipline which can be described the origin of intelligence. [Overview](https://www.misp-project.org/taxonomies.html#_type)
+
+### use-case-applicability
+
+[use-case-applicability](https://github.com/MISP/misp-taxonomies/tree/main/use-case-applicability) :
+The Use Case Applicability categories reflect standard resolution categories, to clearly display alerting rule configuration problems. [Overview](https://www.misp-project.org/taxonomies.html#_use_case_applicability)
+
+### veris
+
+[veris](https://github.com/MISP/misp-taxonomies/tree/main/veris) :
+Vocabulary for Event Recording and Incident Sharing (VERIS) [Overview](https://www.misp-project.org/taxonomies.html#_veris)
+
+### vmray
+
+[vmray](https://github.com/MISP/misp-taxonomies/tree/main/vmray) :
+VMRay taxonomies to map VMRay Thread Identifier scores and artifacts. [Overview](https://www.misp-project.org/taxonomies.html#_vmray)
+
+### vocabulaire-des-probabilites-estimatives
+
+[vocabulaire-des-probabilites-estimatives](https://github.com/MISP/misp-taxonomies/tree/main/vocabulaire-des-probabilites-estimatives) :
+Ce vocabulaire attribue des valeurs en pourcentage à certains énoncés de probabilité [Overview](https://www.misp-project.org/taxonomies.html#_vocabulaire_des_probabilites_estimatives)
+
+### workflow
+
+[workflow](https://github.com/MISP/misp-taxonomies/tree/main/workflow) :
+Workflow support language is a common language to support intelligence analysts to perform their analysis on data and information. [Overview](https://www.misp-project.org/taxonomies.html#_workflow)
 
 # Reserved Taxonomy
 
@@ -197,7 +635,7 @@ The following taxonomy namespaces are reserved and used internally to MISP.
 
 # Documentation
 
-A documentation of the taxonomies is [generated automatically](https://github.com/MISP/misp-taxonomies/blob/master/tools/machinetag.py) from the taxonomies description and available in [PDF](https://www.misp.software/taxonomies.pdf) and [HTML](https://www.misp.software/taxonomies.html).
+A documentation of the taxonomies is [generated automatically](https://github.com/MISP/misp-taxonomies/blob/main/tools/machinetag.py) from the taxonomies description and available in [PDF](https://www.misp.software/taxonomies.pdf) and [HTML](https://www.misp.software/taxonomies.html).
 
 # How to contribute your taxonomy?
 
@@ -255,11 +693,11 @@ The MISP taxonomies (JSON files) are dual-licensed under:
 or
 
 ~~~~
- Copyright (c) 2015-2019 Alexandre Dulaunoy - a@foo.be
- Copyright (c) 2015-2019 CIRCL - Computer Incident Response Center Luxembourg
- Copyright (c) 2015-2019 Andras Iklody
- Copyright (c) 2015-2019 Raphael Vinot
- Copyright (c) 2016-2019 Various contributors to MISP Project
+ Copyright (c) 2015-2021 Alexandre Dulaunoy - a@foo.be
+ Copyright (c) 2015-2021 CIRCL - Computer Incident Response Center Luxembourg
+ Copyright (c) 2015-2021 Andras Iklody
+ Copyright (c) 2015-2021 Raphael Vinot
+ Copyright (c) 2016-2021 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:

adversary/machinetag.json

@@ -1,7 +1,7 @@
 {
   "namespace": "adversary",
   "description": "An overview and description of the adversary infrastructure",
-  "version": 4,
+  "version": 6,
   "predicates": [
     {
       "value": "infrastructure-status",
@@ -56,6 +56,10 @@
         {
           "value": "pending-law-enforcement-request",
           "expanded": "Law enforcement requests are ongoing on the adversary infrastructure"
+        },
+        {
+          "value": "sinkholed",
+          "expanded": "Infrastructure of the adversary is sinkholed and information is collected"
         }
       ]
     },
@@ -106,6 +110,10 @@
         {
           "value": "tds",
           "expanded": "Traffic Distribution Systems including exploit delivery or/and web monetization channels"
+        },
+        {
+          "value": "c2",
+          "expanded": "C2 infrastructure without known specific type."
         }
       ]
     }

circl/machinetag.json

@@ -1,7 +1,7 @@
 {
   "namespace": "circl",
   "description": "CIRCL Taxonomy - Schemes of Classification in Incident Response and Detection",
-  "version": 4,
+  "version": 5,
   "predicates": [
     {
       "value": "incident-classification",
@@ -24,6 +24,14 @@
           "value": "system-compromise",
           "expanded": "System compromise"
         },
+        {
+          "value": "sabotage",
+          "expanded": "Sabotage"
+        },
+        {
+          "value": "privacy-violation",
+          "expanded": "Privacy violation"
+        },
         {
           "value": "scan",
           "expanded": "Scan"
@@ -40,6 +48,14 @@
           "value": "phishing",
           "expanded": "Phishing"
         },
+        {
+          "value": "whaling",
+          "expanded": "Whaling"
+        },
+        {
+          "value": "smishing",
+          "expanded": "SMS Phishing"
+        },
         {
           "value": "malware",
           "expanded": "Malware"
@@ -56,6 +72,10 @@
           "value": "fastflux",
           "expanded": "Fastflux"
         },
+        {
+          "value": "domain-fronting",
+          "expanded": "Domain Fronting"
+        },
         {
           "value": "sql-injection",
           "expanded": "SQL Injection"
@@ -84,10 +104,22 @@
           "value": "wiper",
           "expanded": "Wiper"
         },
+        {
+          "value": "ransomware",
+          "expanded": "ransomware"
+        },
         {
           "value": "sextortion",
           "expanded": "sextortion"
         },
+        {
+          "value": "social-engineering",
+          "expanded": "Social Engineering"
+        },
+        {
+          "value": "gdpr-violation",
+          "expanded": "GDPR Violation"
+        },
         {
           "value": "covid-19",
           "expanded": "covid-19"

course-of-action/machinetag.json

@@ -2,7 +2,7 @@
   "namespace": "course-of-action",
   "expanded": "Courses of Action",
   "description": "A Course Of Action analysis considers six potential courses of action for the development of a cyber security capability.",
-  "version": 1,
+  "version": 2,
   "predicates": [
     {
       "value": "passive",
@@ -43,7 +43,7 @@
           "expanded": "Degrading will not immediately fail an event, but it will slow down the further actions of the attacker. This tactic allows you to catch up during an incident response process, but you have to consider that the attackers may eventually succeed in achieving their objectives. Throttling bandwidth is one way to degrade an intrusion."
         },
         {
-          "value": "decieve",
+          "value": "deceive",
           "expanded": "Deception allows you to learn more about the intentions of the attacker by making them think the action was successful. One way to do this is to put a honeypot in place and redirect the traffic, based on an indicator, towards the honeypot."
         },
         {

cti/machinetag.json

@@ -0,0 +1,37 @@
+{
+  "namespace": "cti",
+  "description": "Cyber Threat Intelligence cycle to control workflow state of your process.",
+  "version": 1,
+  "predicates": [
+    {
+      "value": "planning",
+      "description": "CTI requirementes being generated.",
+      "expanded": "Phase"
+    },
+    {
+      "value": "collection",
+      "description": "Data collection initiated.",
+      "expanded": "Phase"
+    },
+    {
+      "value": "processing-and-analysis",
+      "description": "Data is being processed and analyzed",
+      "expanded": "Phase"
+    },
+    {
+      "value": "dissemination-done",
+      "description": "CTI product created and delivered to stakeholders.",
+      "expanded": "Phase"
+    },
+    {
+      "value": "feedback-received",
+      "description": "Feedback received by stakeholders.",
+      "expanded": "Phase"
+    },
+    {
+      "value": "feedback-pending",
+      "description": "Feedback pending by stakeholders.",
+      "expanded": "Phase"
+    }
+  ]
+}

cycat/machinetag.json

@@ -0,0 +1,119 @@
+{
+  "namespace": "cycat",
+  "expanded": " Universal Cybersecurity Resource Catalogue",
+  "description": "Taxonomy used by CyCAT, the Universal Cybersecurity Resource Catalogue, to categorize the namespaces it supports and uses.",
+  "version": 1,
+  "refs": [
+    "https://www.cycat.org/"
+  ],
+  "values": [
+    {
+      "predicate": "type",
+      "entry": [
+        {
+          "value": "tool",
+          "expanded": "Tool",
+          "description": "Open source or proprietary tool used in cybersecurity."
+        },
+        {
+          "value": "playbook",
+          "expanded": "Playbook",
+          "description": "Playbook, such as a defined set of rules with one or more actions triggered by different events to respond to, orchestrate or automate cybersecurity related actions."
+        },
+        {
+          "value": "taxonomy",
+          "expanded": "Taxonomy",
+          "description": "Cybersecurity taxonomy is a set of labels used to classify (in both terms - arrange in classes or/and design to national classification) cybersecurity related information."
+        },
+        {
+          "value": "rule",
+          "expanded": "Rule",
+          "description": "Detection rule or set of detection rules used in the cybersecurity field. Rulesets can be in different formats for (N/L)IDS/SIEM (such as Snort, Suricata, Zeek, SIGMA or YARA) or any other tool capable of parsing them."
+        },
+        {
+          "value": "notebook",
+          "expanded": "Notebook",
+          "description": "Interactive document to code, experiment, train or visualize cybersecurity-related information. A notebook can be transcribed in a format such as Jupyter Notebooks, Apache Zeppelin, Pluton or Google Colab."
+        },
+        {
+          "value": "vulnerability",
+          "expanded": "Vulnerability",
+          "description": "Public or non-public information about a security vulnerability in a specific software, hardware or service."
+        },
+        {
+          "value": "proof-of-concept",
+          "expanded": "Proof-of-concept",
+          "description": "Code to validate a known vulnerability."
+        },
+        {
+          "value": "fingerprint",
+          "expanded": "Fingerprint",
+          "description": "Code to uniquely identify specific cybersecurity-relevant patterns. Fingerprints can be expressed in different formats such as ja3, ja3s, hassh, jarm or favicon-mmh3."
+        },
+        {
+          "value": "mitigation",
+          "expanded": "Mitigation",
+          "description": "Mitigating control to prevent unwanted activity from happening, like a specific configuration of the operating system/tools or an implementation policy."
+        },
+        {
+          "value": "dataset",
+          "expanded": "Dataset",
+          "description": "Dataset for validation of detections and tool stacks,"
+        }
+      ]
+    },
+    {
+      "predicate": "scope",
+      "entry": [
+        {
+          "value": "identify",
+          "expanded": "Identify"
+        },
+        {
+          "value": "protect",
+          "expanded": "Protect"
+        },
+        {
+          "value": "detect",
+          "expanded": "Detect"
+        },
+        {
+          "value": "respond",
+          "expanded": "Respond"
+        },
+        {
+          "value": "recover",
+          "expanded": "Recover"
+        },
+        {
+          "value": "exploit",
+          "expanded": "Exploit"
+        },
+        {
+          "value": "investigate",
+          "expanded": "Investigate"
+        },
+        {
+          "value": "train",
+          "expanded": "Train"
+        },
+        {
+          "value": "test",
+          "expanded": "Test"
+        }
+      ]
+    }
+  ],
+  "predicates": [
+    {
+      "value": "type",
+      "expanded": "Type",
+      "description": "Type of entry in the catalogue."
+    },
+    {
+      "value": "scope",
+      "expanded": "Scope",
+      "description": "Scope of usage for the entry in the catalogue."
+    }
+  ]
+}

dark-web/machinetag.json

@@ -2,7 +2,7 @@
   "namespace": "dark-web",
   "expanded": "Dark Web",
   "description": "Criminal motivation on the dark web: A categorisation model for law enforcement. ref: Janis Dalins, Campbell Wilson, Mark Carman. Taxonomy updated by MISP Project",
-  "version": 3,
+  "version": 4,
   "predicates": [
     {
       "value": "topic",
@@ -198,6 +198,11 @@
           "value": "whistleblower",
           "expanded": "Whistleblower",
           "description": "Exposition and sharing of confidential information with protection of the witness in mind"
+        },
+        {
+          "value": "ransomware-group",
+          "expanded": "Ransomware Group",
+          "description": "Ransomware group PR or leak website"
         }
       ]
     },

domain-abuse/machinetag.json

@@ -1,8 +1,8 @@
 {
   "namespace": "domain-abuse",
   "expanded": "Domain Name Abuse",
-  "description": "Domain Name Abuse - taxonomy to tag domain names used for cybercrime. Use europol-incident to tag abuse-activity",
-  "version": 1,
+  "description": "Domain Name Abuse - taxonomy to tag domain names used for cybercrime.",
+  "version": 2,
   "predicates": [
     {
       "value": "domain-status",
@@ -73,6 +73,16 @@
           "value": "sinkhole",
           "expanded": "Sinkhole",
           "description": "Domain Name is sinkholed for research, detection, LE"
+        },
+        {
+          "value": "compromised-domain-name-registrar",
+          "expanded": "Compromised domain name registrar",
+          "description": "Domain name is compromised due to an incident at the registrar"
+        },
+        {
+          "value": "compromised-domain-name-registry",
+          "expanded": "Compromised domain name registry",
+          "description": "Domain name is compromised due to an incident at the registry"
         }
       ]
     }

interactive-cyber-training-audience/machinetag.json

@@ -0,0 +1,151 @@
+{
+  "namespace": "interactive-cyber-training-audience",
+  "description": "Describes the target of cyber training and education.",
+  "version": 1,
+  "refs": ["https://arxiv.org/abs/2101.05538"],
+  "expanded": "Interactive Cyber Training - Audience",
+  "predicates": [
+    {
+      "value": "sector",
+      "expanded": "Sector",
+      "description": "The sector from which the audience comes determines the nature of the training."
+    },
+    {
+      "value": "purpose",
+      "expanded": "Purpose",
+      "description": "Purpose answered the question for which reason trainings should be used."
+    },
+    {
+      "value": "proficiency-level",
+      "expanded": "Proficiency Level",
+      "description": "Proficiency describes the knowledge of users and what they are able to do."
+    },
+    {
+      "value": "target-audience",
+      "expanded": "Target Audience",
+      "description": "Target audience describes the audience, which is targeted by the training."
+    }
+      ],
+    "values": [
+      {
+        "predicate": "sector",
+        "entry": [
+          {
+            "value": "academic-school",
+            "expanded": "Academic - School",
+            "description": "The focus is on the principles underlying cybersecurity, ranging from theoretical to applied, at school level."
+          },
+          {
+            "value": "academic-university",
+            "expanded": "Academic - University",
+            "description": "The focus is on the principles underlying cybersecurity, ranging from theoretical to applied, at university level."
+          },
+          {
+            "value": "public-government",
+            "expanded": "Public - Government",
+            "description": "In public sector such as government, Cybersecurity is seen as tool to protect the public interest. Hence, it emphasizes on developing policies and systems to implement laws and regulations."
+          },
+          {
+            "value": "public-authorities",
+            "expanded": "Public - Authorities",
+            "description": "In public sector such as authorities, Cybersecurity is seen as tool to protect the public interest. Hence, it emphasizes on developing policies and systems to implement laws and regulations."
+          },
+          {
+            "value": "public-ngo",
+            "expanded": "Public - NGO",
+            "description": "In public sector such as NGO, Cybersecurity is seen as tool to protect the public interest. Hence, it emphasizes on developing policies and systems to implement laws and regulations."
+          },
+          {
+            "value": "public-military",
+            "expanded": "Public - Military",
+            "description": "In public sector such as military sector, Cybersecurity is seen as tool to protect the public interest. Hence, it emphasizes on developing policies and systems to implement laws and regulations."
+          },
+          {
+            "value": "private",
+            "expanded": "Private",
+            "description": "The private sector and industry focuses more on protecting its investments. The effectiveness of security mechanisms and people are more important than principles they embody."
+          }
+        ]
+      },
+      {
+        "predicate": "purpose",
+        "entry": [
+          {
+            "value": "awareness",
+            "expanded": "Awareness",
+            "description": "This training should be used to raise the awareness in multiple and different security threats."
+          },
+          {
+            "value": "skills",
+            "expanded": "Skills",
+            "description": "This training should be used to recognize the different skill levels of the participants so that can they be improved in a targeted manner."
+          },
+          {
+            "value": "collaboration",
+            "expanded": "Collaboration",
+            "description": "This training should be used to improve the cooperation within a team or beyond."
+          },
+          {
+            "value": "communication",
+            "expanded": "Communication",
+            "description": "This training should be used to increase the efficiency of internal and external communication in case of an incident."
+          },
+          {
+            "value": "leadership",
+            "expanded": "Leadership",
+            "description": "This training should be used to improve the management and coordination of the responsible entities."
+          }
+        ]
+      },
+      {
+        "predicate": "proficiency-level",
+        "entry": [
+          {
+            "value": "beginner",
+            "expanded": "Beginner",
+            "description": "The lowest level. Beginner are limited in abilities and knowledge. They have the possibility to use foundational conceptual and procedural knowledge in a controlled and limited environment. Beginners cannot solve critical tasks and need significant supervision. They are able to perform daily processing tasks. The focus is on learning."
+          },
+          {
+            "value": "professional",
+            "expanded": "Professional",
+            "description": "The mid level. Professionals have deeper knowledge and understanding in specific sectors. For these sectors they are able to complete tasks as requested. Sometimes supervision is needed but usually they perform independently. The focus is on enhancing and applying existing knowledge."
+          },
+          {
+            "value": "expert",
+            "expanded": "Expert",
+            "description": "The highest level. Experts have deeper knowledge and understanding in different sectors. They complete tasks self-dependent and have the possibilities to achieve goals in the most effective and efficient way. Experts have comprehensive understanding and abilities to lead and train others. The focus is on strategic action."
+          }
+        ]
+      },
+      {
+        "predicate": "target-audience",
+        "entry": [
+          {
+            "value": "student-trainee",
+            "expanded": "Student/Trainee",
+            "description": "Student and trainees have little to none practical knowledge. Training can be used for students and trainees, to enhance their knowledge and to practice theoretical courses."
+          },
+          {
+            "value": "it-user",
+            "expanded": "IT User",
+            "description": "IT users use the IT but have little to none knowledge about IT security. Users can get trained to understand principles of IT security and to grow awareness."
+          },
+          {
+            "value": "it-professional",
+            "expanded": "IT Professional",
+            "description": "Professionals have little to medium knowledge about IT security. Their professional focus is in specific sectors, therefore, they receive IT security knowledge for their sectors."
+          },
+          {
+            "value": "it-specialist",
+            "expanded": "IT Specialist",
+            "description": "Specialists already have a comprehensive knowledge in IT security. Therefore, the training is focussed on specific aspects."
+          },
+          {
+            "value": "management",
+            "expanded": "Management",
+            "description": "Management has little knowledge about IT security, but a broad overview. By the training, management can understand changed settings better."
+          }
+        ]
+      }
+  ]
+}

interactive-cyber-training-technical-setup/machinetag.json

@@ -0,0 +1,131 @@
+{
+  "namespace": "interactive-cyber-training-technical-setup",
+  "description": "The technical setup consists of environment structure, deployment, and orchestration.",
+  "version": 1,
+  "refs": ["https://arxiv.org/abs/2101.05538"],
+  "expanded": "Interactive Cyber Training - Technical Setup",
+  "predicates": [
+      {
+        "value": "environment-structure",
+        "expanded": "Environment Structure",
+        "description": "The environment structure refers to the basic characteristic of the event."
+      },
+      {
+        "value": "deployment",
+        "expanded": "Deployment",
+        "description": "The environment of cyber training can either be deployed on premise or on cloud infrastructures"
+      },
+      {
+        "value": "orchestration",
+        "expanded": "Orchestration",
+        "description": "The composition of parts and components of a pool of tasks. The goal is to setup a holistic scenario and integrate cyber training session. Furthermore, it includes a declarative description of the overall process in the form of a composite and harmonic collaboration."
+      }
+    ],
+    "values": [
+      {
+        "predicate": "environment-structure",
+        "entry": [
+          {
+            "value": "tabletop-style",
+            "expanded": "Tabletop Style",
+            "description": "A session that involves the movement of counters or other objects round a board or on a flat surface"
+          },
+          {
+            "value": "online-collaboration-platform",
+            "expanded": "Online Platform - Collaboration Platform",
+            "description": "The environment allows organizations to incorporate real-time communication capabilities and providing remote access to other systems. This includes the exchange of files and messages in text, audio, and video formats between different computers or users."
+          },
+          {
+            "value": "online-e-learning-platform",
+            "expanded": "Online Platform - E-Learning Platform",
+            "description": "A software application for the administration, documentation, tracking, reporting, and delivery of educational courses, training programs, or learning and development programs."
+          },
+          {
+            "value": "hosting",
+            "expanded": "Hosting",
+            "description": "A cyber training based on single hosts uses primarily a personal computer to providing tasks and challenges for a user. It allows a direct interaction with the systems."
+          },
+          {
+            "value": "simulated-network-infrastructure",
+            "expanded": "Network Infrastruture - Simulated",
+            "description": "Dependent of the realization type, a network-based environment consists of servers and clients, which are connected to each other in a local area network (LAN) or wide area network (WAN). A simulation copies the network components from the real world into a virtual environment. It provides an idea about how something works. It simulates the basic behavior but does not necessarily abide to all the rules of the real systems."
+          },
+          {
+            "value": "emulated-network-infrastructure",
+            "expanded": "Network Infrastruture - Emulated",
+            "description": "Dependent of the realization type, a network-based environment consists of servers and clients, which are connected to each other in a local area network (LAN) or wide area network (WAN). An emulator duplicates things exactly as they exist in real life. The emulation is effectively a complete imitation of the real thing. It operates in a virtual environment instead of the real world."
+          },
+          {
+            "value": "real-network-infrastructure",
+            "expanded": "Network Infrastruture - Real",
+            "description": "Dependent of the realization type, a network-based environment consists of servers and clients, which are connected to each other in a local area network (LAN) or wide area network (WAN). In a real network infrastructure, physical components are used to connect the systems and to setup a scenario."
+          }
+        ]
+      },
+      {
+        "predicate": "deployment",
+        "entry": [
+          {
+            "value": "physical-on-premise",
+            "expanded": "On Premise - Physical",
+            "description": "The environment for the training run on physical machines. The data is stored locally and not on cloud; nor is a third party involved. The advantages of on premise solutions are the physical accessibility, which makes it possible to use the complete range of cyber challenges."
+          },
+          {
+            "value": "virtual-on-premise",
+            "expanded": "On Premise - Virtual",
+            "description": "The environment for the training run virtual machines. The data is stored locally and not on cloud; nor is a third party involved. The benefit of virtual machines is the maximum of configurability. The advantages of on premise solutions are the physical accessibility, which makes it possible to use the complete range of cyber challenges."
+          },
+          {
+            "value": "cloud",
+            "expanded": "Cloud",
+            "description": "Training setup deployed in the cloud has on-demand availability of computer system resources, especially data storage and computing power, without direct active management by the user. In contrast to on premise setups, cloud solutions are rapid elastic on request. So the training can be adapted flexible on a large amount of users and is easily usable world wide."
+          }
+        ]
+      },
+      {
+        "predicate": "orchestration",
+        "entry": [
+          {
+            "value": "none-automation",
+            "expanded": "None Automation",
+            "description": "Specifies the automation of processes and the amount of human interaction with the system to maintain and administrate, especially for repetitive exercise; Here none automation is present."
+          },
+          {
+            "value": "partially-automation",
+            "expanded": "Partially Automation",
+            "description": "Specifies the automation of processes and the amount of human interaction with the system to maintain and administrate, especially for repetitive exercise; Here partially automated."
+          },
+          {
+            "value": "complete-automation",
+            "expanded": "Complete Automation",
+            "description": "Specifies the automation of processes and the amount of human interaction with the system to maintain and administrate, especially for repetitive exercise; Here full-automated."
+          },
+          {
+            "value": "portability-miscellaneous",
+            "expanded": "Portability - Miscellaneous",
+            "description": "Miscellaneous approaches are used to ensure the possibility to exchange data, challenges, or entire scenarios to other environments or locations."
+          },
+          {
+            "value": "portability-exchangenable-format",
+            "expanded": "Portability - Exchangenable Format",
+            "description": "Common data format (YALM, XML, JSON, ...) is used to ensure the possibility to exchange data, challenges, or entire scenarios to other environments or locations."
+          },
+          {
+            "value": "maintainability-modifiability",
+            "expanded": "Maintability - Modifiability",
+            "description": "Maintainability represents effectiveness and efficiency with which a session can be modified or adapted to changes."
+          },
+          {
+            "value": "maintainability-modularity",
+            "expanded": "Maintability - Modularity",
+            "description": "A modular concept has advantages in reusability and combinability."
+          },
+          {
+            "value": "compatibility",
+            "expanded": "Compatibility",
+            "description": "The Compatibility deals with the technical interaction possibilities via interfaces to other applications, data, and protocols."
+          }
+        ]
+      }
+  ]
+}

interactive-cyber-training-training-environment/machinetag.json

@@ -0,0 +1,192 @@
+{
+  "namespace": "interactive-cyber-training-training-environment",
+  "description": "The training environment details the environment around the training, consisting of training type and scenario.",
+  "version": 1,
+  "refs": ["https://arxiv.org/abs/2101.05538"],
+  "expanded": "Interactive Cyber Training - Training Environment",
+  "predicates": [
+    {
+      "value": "training-type",
+      "expanded": "Training Type",
+      "description": "Education in cybersecurity follows different approaches. The level of interaction and hands-on experience distinguishes different types of training."
+    },
+    {
+      "value": "scenario",
+      "expanded": "Scenario",
+      "description": "The scenario is a main component of cybersecurity training. Scenarios are needed to reach the goal of the training."
+    }x
+    ],
+    "values": [
+      {
+        "predicate": "training-type",
+        "entry": [
+          {
+            "value": "tabletop-game-speech",
+            "expanded": "Tabletop Game - Speech",
+            "description": "Table Top training -here based on speech-only- are a lightweight, but intellectually intense exercise. In this setting, the involved teams or participants focus on opposing missions. On a theoretical basis, the teams develop different strategies and countermeasures to explore the offensive cyber effects on operations."
+          },
+          {
+            "value": "tabletop-game-text",
+            "expanded": "Tabletop Game - text",
+            "description": "Table Top training -here based on text-only- are a lightweight, but intellectually intense exercise. In this setting, the involved teams or participants focus on opposing missions. On a theoretical basis, the teams develop different strategies and countermeasures to explore the offensive cyber effects on operations."
+          },
+          {
+            "value": "tabletop-game-multimedia",
+            "expanded": "Tabletop Game - Multimedia",
+            "description": "Table Top training -here based on multimedia- are a lightweight, but intellectually intense exercise. In this setting, the involved teams or participants focus on opposing missions. On a theoretical basis, the teams develop different strategies and countermeasures to explore the offensive cyber effects on operations."
+          },
+          {
+            "value": "capture-the-flag-quiz",
+            "expanded": "Capture the Flag - Quiz",
+            "description": "Capture the Flag (CTF) is a well-known cybersecurity contest in which participants compete in real-time, which can exists as a quiz."
+          },
+          {
+            "value": "capture-the-flag-jeopardy",
+            "expanded": "Capture the Flag - Jeopardy",
+            "description": "Capture the Flag (CTF) is a well-known cybersecurity contest in which participants compete in real-time, which can exists as jeopardy."
+          },
+          {
+            "value": "capture-the-flag-attack",
+            "expanded": "Capture the Flag - Attack",
+            "description": "Capture the Flag (CTF) is a well-known cybersecurity contest in which participants compete in real-time, which can exists as an attack-only scenario."
+          },
+          {
+            "value": "capture-the-flag-defence",
+            "expanded": "Capture the Flag - Defence",
+            "description": "Capture the Flag (CTF) is a well-known cybersecurity contest in which participants compete in real-time, which can exists as an defence-only scenario."
+          },
+          {
+            "value": "capture-the-flag-attack-defence",
+            "expanded": "Capture the Flag - Attack-Defence",
+            "description": "Capture the Flag (CTF) is a well-known cybersecurity contest in which participants compete in real-time, which can exists as an attack-defence scenario."
+          },
+          {
+            "value": "cyber-training-range-classroom-practice",
+            "expanded": "Cyber Training Range - Classroom Practice",
+            "description": "A cyber range provides an environment to practice network operation skills. It should represent real-world scenarios and offer isolation from other networks to contain malicious activity. In this training type, complex attacks take place in a simulated environment. The participants perform divers educational hands-on activities according to their role. In these trainings the roles that are not covered by participants are simulated or covered by the instructors. Trainings can be classroom practice."
+          },
+          {
+            "value": "cyber-training-range-single-team-training",
+            "expanded": "Cyber Training Range - Single Team Training",
+            "description": "A cyber range provides an environment to practice network operation skills. It should represent real-world scenarios and offer isolation from other networks to contain malicious activity. In this training type, complex attacks take place in a simulated environment. The participants perform divers educational hands-on activities according to their role. In these trainings the roles that are not covered by participants are simulated or covered by the instructors. Trainings can be single team trainings."
+          },
+          {
+            "value": "cyber-training-range-multiple-team-training",
+            "expanded": "Cyber Training Range - Multiple Team Training",
+            "description": "A cyber range provides an environment to practice network operation skills. It should represent real-world scenarios and offer isolation from other networks to contain malicious activity. In this training type, complex attacks take place in a simulated environment. The participants perform divers educational hands-on activities according to their role. In these trainings the roles that are not covered by participants are simulated or covered by the instructors. Trainings can be multiple team trainings."
+          },
+          {
+            "value": "project-approach",
+            "expanded": "Project Approach",
+            "description": "In this type of training, hands-on projects are to be completed during the training. Thereby, the participants learn and understand the basic concepts of security. During the projects, the teachers can intervene and control the learning process."
+          }
+        ]
+      },
+      {
+        "predicate": "scenario",
+        "entry": [
+          {
+            "value": "supervised",
+            "expanded": "Supervision: Supervised",
+            "description": "Describes if the training is supervised. For instance, cyber range trainings are typically supervised."
+          },
+          {
+            "value": "unsupervised",
+            "expanded": "Supervision: Unsupervised",
+            "description": "Describes if the training is unsupervised. For instance, jeopardy CTF are usually unsupervised."
+          },
+          {
+            "value": "free-multiple-choice",
+            "expanded": "Style: Free-/Multiple Choice",
+            "description": "Decribes the challenges within the training as Free-/Multi Choice. (can be the case with CTFs)"
+          },
+          {
+            "value": "problem-driven",
+            "expanded": "Style: Problem-Driven",
+            "description": "Describes the challenge within the training as Problem-driven.
+"
+          },
+          {
+            "value": "storyline-driven",
+            "expanded": "Style: Storyline-Driven",
+            "description": "Describes the challenge within the training as Storyline-driven."
+          },
+          {
+              "value": "challenges-target-network",
+              "expended": "Challenges: Network Target",
+              "description": "The target in this challenge is network."
+          },
+          {
+              "value": "challenges-target-host",
+              "expended": "Challenges: Host Target",
+              "description": "The target in this challenge is host."
+          },
+          {
+              "value": "challenges-target-application",
+              "expended": "Challenges: Application Target",
+              "description": "The target in this challenge is application."
+          },
+          {
+              "value": "challenges-target-protocol",
+              "expended": "Challenges: Protocol Target",
+              "description": "The target in this challenge is protocol."
+          },
+          {
+              "value": "challenges-target-data",
+              "expended": "Challenges: Data Target",
+              "description": "The target in this challenge is data."
+          },
+          {
+              "value": "challenges-target-person",
+              "expended": "Challenges: Person Target",
+              "description": "The target in this challenge is person."
+          },
+          {
+              "value": "challenges-target-physical",
+              "expended": "Challenges: Physical Target",
+              "description": "The target in this challenge is physical."
+          },
+          {
+            "value": "challenges-type-foot-printing",
+            "expended": "Challenges: Foot-printing Type",
+            "description": "Foot-printing is needed to solve this challenge."
+          },
+          {
+            "value": "challenges-type-scanning",
+            "expended": "Challenges: Scanning Type",
+            "description": "Scanning is needed to solve this challenge."
+          },
+          {
+            "value": "challenges-type-enumeration",
+            "expended": "Challenges: Enumeration Type",
+            "description": "Enumeration is needed to solve this challenge."
+          },
+          {
+            "value": "challenges-type-pivoting",
+            "expended": "Challenges: Pivoting Type",
+            "description": "Pivoting is needed to solve this challenge."
+          },
+          {
+            "value": "challenges-type-exploitation",
+            "expended": "Challenges: Exploitation Type",
+            "description": "Exploitation is needed to solve this challenge."
+          },
+          {
+            "value": "challenges-type-privilege-escalation",
+            "expended": "Challenges: Privilege escalation Type",
+            "description": "Privilege escalation is needed to solve this challenge."
+          },
+          {
+            "value": "challenges-type-covering-tracks",
+            "expended": "Challenges: Covering tracks Type",
+            "description": "Covering tracks is needed to solve this challenge."
+          },
+          {
+            "value": "challenges-type-maintaining",
+            "expended": "Challenges: maintaining Type",
+            "description": "Maintaining access is needed to solve this challenge."
+          }
+        ]
+      }
+  ]
+}

interactive-cyber-training-training-setup/machinetag.json

@@ -0,0 +1,157 @@
+{
+  "namespace": "interactive-cyber-training-training-setup",
+  "description": "The training setup further describes the training itself with the scoring, roles,
+the training mode as well as the customization level.",
+  "version": 1,
+  "refs": ["https://arxiv.org/abs/2101.05538"],
+  "expanded": "Interactive Cyber Training - Training Setup",
+  "predicates": [
+      {
+        "value": "scoring",
+        "expanded": "Scoring",
+        "description": "Scoring is not only used in competition-oriented training like CTF but also to motivate participants, give feedback, track the progress. The scoring can be based, but is not limited to monitoring systems, defined objectives, or over-the-shoulder evaluation mechanisms."
+      },
+      {
+        "value": "roles",
+        "expanded": "Roles",
+        "description": "Participants in a training are split in different teams, according to their skills, role and tasks."
+      },
+      {
+        "value": "training-mode",
+        "expanded": "Training Mode",
+        "description": "Defines whether the training opposes singles persons, teams or groups."
+      },
+      {
+        "value": "customization-level",
+        "expanded": "Customization Level",
+        "description": "Defines the level of customization of the training."
+      }
+    ],
+    "values": [
+      {
+        "predicate": "scoring",
+        "entry": [
+          {
+            "value": "no-scoring",
+            "expanded": "No Scoring",
+            "description": "The training have no type of scoring."
+          },
+          {
+            "value": "assessment-static",
+            "expanded": "Assessment: Static",
+            "description": "The scoring in this variant relies on the static setting of different scores for tasks and objectives, possibly incluing a degree of difficulty as well."
+          },
+          {
+            "value": "assessment-dynamic",
+            "expanded": "Assessment: Dynamic",
+            "description": "The scoring in this variant is set dynamically using mathematical functions or dynamic methods such as teh Elo Rating System."
+          },
+          {
+            "value": "awarding-manual",
+            "expanded": "Awarding: Manual",
+            "description": "Awards are given manually."
+          },
+          {
+            "value": "awarding-automatic",
+            "expanded": "Awarding: Automatic",
+            "description": "Awards are given automatically."
+          },
+          {
+            "value": "awarding-mixed",
+            "expanded": "Awarding: Mixed",
+            "description": "Awards are given manually and/or automatically."
+          }
+        ]
+      },
+      {
+        "predicate": "roles",
+        "entry": [
+          {
+            "value": "no-specific-role",
+            "expanded": "No specific Role",
+            "description": "Individuals who do not fit into the defined teams can be assigned to this role."
+          },
+          {
+            "value": "transparent-team-observer-watcher",
+            "expanded": "Transparent Team - Observer/Watcher",
+            "description": "Members of this team observe the training. Usually, these people have a defined purpose, but have no influence on the training itself. Possible purposes are learning about the training topic and roles, studying strategies of participants, or supervising employees."
+          },
+          {
+            "value": "white-team-trainer-instructor",
+            "expanded": "White Team - Trainer/Instructor",
+            "description": "This team consists of instructors, referees, organizers, and training managers. They design the training scenario including objectives, rules, background story, and tasks. During the training, this team controls the progress and assigns tasks to the teams. These so-called injects also include simulated media, operation coordination, or law enforcement agencies. Giving hints for the training teams could also be part of this team."
+          },
+          {
+            "value": "green-team-organizer-admin",
+            "expanded": "Green Team - Organizer/Admin",
+            "description": "The operators that are responsible for the exercise infrastructure build this team. Before a training, this team sets up and configures the environment and takes it down afterwards. During a training, it also monitors the environments health and handles problems that may arise."
+          },
+          {
+            "value": "red-team-attacker",
+            "expanded": "Red Team - Attacker",
+            "description": "This team consists of people authorized and organized to model security adversaries. They are responsible to identify and exploit potential vulnerabilities present in the training environment. Depending on the training environment, the tasks can follow a predefined attack path."
+          },
+          {
+            "value": "blue-team-defender",
+            "expanded": "Blue Team - Defender",
+            "description": "The group of individuals that is responsible for defending the training environment. They deal with the red team’s attacks and secure the compromised networks. Guidelines for that team are the training rules and local cyber law."
+          },
+          {
+            "value": "gray-team-bystander",
+            "expanded": "Gray Team - Bystander",
+            "description": "Bystanders of a training form this team. They do not necessarily have a specific intention or purpose, but an interest in the training event itself. It is also possible that this team interacts with participants and thereby unintentionally influences the training."
+          },
+          {
+            "value": "yellow-team-insider",
+            "expanded": "Yellow Team - Insider",
+            "description": "Members of this team perform not only tasks like generating legitimate network traffic and user behavior but also perform erroneous actions that lead to vulnerabilities and attacks. This team can also include the regular system builders, like programmers, developers, and software engineers and architects."
+          },
+          {
+            "value": "purple-team-bridge",
+            "expanded": "Purple Team - Bridge",
+            "description": "In a training, this team is a bridge between red and blue teams that helps to improve the performance of both. Through joint red-blue activities it improves the scope of the training participants. Goals are to maximize the Blue Teams capability and the effectiveness of Red Teams activities."
+          }
+        ]
+      },
+      {
+        "predicate": "training-mode",
+        "entry": [
+          {
+            "value": "single",
+            "expanded": "Single",
+            "description": "A single player plays against others. Others can be real persons, butalso scripted opponents."
+          },
+          {
+            "value": "team",
+            "expanded": "Team",
+            "description": "A team plays against others. In this alignments, each player can bring its expertise into the training, focussing on different aspects. Examples are Blue and Red Teams."
+          },
+          {
+            "value": "cross-group",
+            "expanded": "Cross-Group",
+            "description": "A group plays against others. In this setting, the group members might not know each other. Example are CTF competitions and training for the entire organization in a breach scenario."
+          }
+        ]
+      },
+      {
+        "predicate": "customization-level",
+        "entry": [
+          {
+            "value": "general",
+            "expanded": "General",
+            "description": "A general purpose training setup is not, or only little customized. This variant is suited for an entry level training or to learn about general processes without regard to the underlying setup."
+          },
+          {
+            "value": "specific",
+            "expanded": "Specific",
+            "description": "The training setup can be customized for a specific training goal or target audience. Examples for this variant are specific trainings within the High School education or for the health sector."
+          },
+          {
+            "value": "individual",
+            "expanded": "Individual",
+            "description": "The most tailored variant is an individual customization. Hereby, the training setup corresponds to a real environment in the best possible way. Exemplary uses of this variant are the training of teams in their environment or the training of new expert-level employees."
+          }
+        ]
+      }
+  ]
+}

ioc/machinetag.json

@@ -0,0 +1,26 @@
+{
+  "namespace": "ioc",
+  "description": "An IOC classification to facilitate automation of malicious and non malicious artifacts",
+  "version": 2,
+  "predicates": [
+    {
+      "value": "artifact-state",
+      "expanded": "Artifact State"
+    }
+  ],
+  "values": [
+    {
+      "predicate": "artifact-state",
+      "entry": [
+        {
+          "value": "malicious",
+          "expanded": "Malicious"
+        },
+        {
+          "value": "not-malicious",
+          "expanded": "Not Malicious"
+        }
+      ]
+    }
+  ]
+}

misp/machinetag.json

@@ -66,7 +66,7 @@
         },
         {
           "expanded": "Confidence cannot be evaluated",
-          "value": "confidence-cannot-be-evalued",
+          "value": "confidence-cannot-be-evaluated",
           "numerical_value": 50
         }
       ]
@@ -154,6 +154,35 @@
         }
       ]
     },
+    {
+      "predicate": "event-type",
+      "entry": [
+        {
+          "expanded": "observation",
+          "value": "observation"
+        },
+        {
+          "expanded": "incident",
+          "value": "incident"
+        },
+        {
+          "expanded": "report",
+          "value": "report"
+        },
+        {
+          "expanded": "collection",
+          "value": "collection"
+        },
+        {
+          "expanded": "analysis",
+          "value": "analysis"
+        },
+        {
+          "expanded": "automatic-analysis",
+          "value": "automatic-analysis"
+        }
+      ]
+    },
     {
       "predicate": "ids",
       "entry": [
@@ -223,12 +252,16 @@
       "value": "misp2yara",
       "exclusive": true
     },
+    {
+      "expanded": "Type of the event.",
+      "value": "event-type"
+    },
     {
       "expanded": "IDS related tag unfluencing the MISP behavior of the IDS flag.",
       "value": "ids"
     }
   ],
-  "version": 11,
+  "version": 12,
   "description": "MISP taxonomy to infer with MISP behavior or operation.",
   "expanded": "MISP",
   "namespace": "misp"

phishing/machinetag.json

@@ -1,7 +1,7 @@
 {
   "namespace": "phishing",
   "description": "Taxonomy to classify phishing attacks including techniques, collection mechanisms and analysis status.",
-  "version": 4,
+  "version": 5,
   "predicates": [
     {
       "value": "techniques",
@@ -79,6 +79,11 @@
           "value": "sms-phishing",
           "expanded": "SMS phishing",
           "description": "Adversary sends an SMS to a potential victims to gather sensitive information or use another phishing technique at a later stage."
+        },
+        {
+          "value": "business email compromise",
+          "expanded": "Business Email Compromise",
+          "description": "Adversary sends an email containing a malicious artefact from a legitimate business email address which has connections to you as an individual or your organisation."
         }
       ]
     },

ransomware/machinetag.json

@@ -2,11 +2,12 @@
   "namespace": "ransomware",
   "expanded": "ransomware types and elements",
   "description": "Ransomware is used to define ransomware types and the elements that compose them.",
-  "version": 5,
+  "version": 6,
   "refs": [
     "https://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-evolution-of-ransomware.pdf",
     "https://docs.apwg.org/ecrimeresearch/2018/5357083.pdf",
-    "https://bartblaze.blogspot.com/p/the-purpose-of-ransomware.html"
+    "https://bartblaze.blogspot.com/p/the-purpose-of-ransomware.html",
+    "https://arxiv.org/pdf/2102.06249.pdf"
   ],
   "predicates": [
     {

rsit/machinetag.json

@@ -3,18 +3,18 @@
     {
       "entry": [
         {
-          "description": "Or 'Unsolicited Bulk Email', this means that the recipient has not granted verifiable permission for the message to be sent and that the message is sent as part of a larger collection of messages, all having a functionally comparable content.",
+          "description": "Or 'Unsolicited Bulk Email', this means that the recipient has not granted verifiable permission for the message to be sent and that the message is sent as part of a larger collection of messages, all having a functionally comparable content. This IOC refers to resources which make up spam infrastructure, for example, harvesters like address verification, URLs in spam emails, etc.",
           "expanded": "Spam",
           "value": "spam"
         },
         {
-          "description": "Discreditation or discrimination of somebody, e.g. cyber stalking, racism or threats against one or more individuals.",
+          "description": "Bullying, harassment or discrimination of somebody, e.g., cyber stalking, racism or threats against one or more individuals.",
           "expanded": "Harmful Speech",
           "value": "harmful-speech"
         },
         {
-          "description": "Child pornography, glorification of violence, etc.",
-          "expanded": "Child Porn/Sexual/Violent Content",
+          "description": "Child Sexual Exploitation (CSE), sexual content, glorification of violence, etc.",
+          "expanded": "(Child) Sexual Exploitation/Sexual/Violent Content",
           "value": "violence"
         }
       ],
@@ -23,22 +23,22 @@
     {
       "entry": [
         {
-          "description": "System infected with malware, e.g. PC, smartphone or server infected with a rootkit.",
+          "description": "System infected with malware, e.g., a PC, smartphone or server infected with a rootkit. Most often this refers to a connection to a sinkholed command and control server.",
           "expanded": "Infected System",
           "value": "infected-system"
         },
         {
-          "description": "Command-and-control server contacted by malware on infected systems.",
+          "description": "Command and control server contacted by malware on infected systems.",
           "expanded": "C2 Server",
           "value": "c2-server"
         },
         {
-          "description": "URI used for malware distribution, e.g. a download URL included in fake invoice malware spam.",
+          "description": "URI used for malware distribution, e.g., a download URL included in fake invoice malware spam or exploit kits (on websites).",
           "expanded": "Malware Distribution",
           "value": "malware-distribution"
         },
         {
-          "description": "URI hosting a malware configuration file, e.g. webinjects for a banking trojan.",
+          "description": "URI hosting a malware configuration file, e.g., web injects for a banking trojan.",
           "expanded": "Malware Configuration",
           "value": "malware-configuration"
         }
@@ -48,17 +48,17 @@
     {
       "entry": [
         {
-          "description": "Attacks that send requests to a system to discover weaknesses. This also includes testing processes to gather information on hosts, services and accounts. Examples: fingerd, DNS querying, ICMP, SMTP (EXPN, RCPT, ...), port scanning.",
+          "description": "Attacks that send requests to a system to discover weaknesses. This also includes testing processes to gather information on hosts, services and accounts. This includes fingerd, DNS querying, ICMP, SMTP (EXPN, RCPT, etc) port scanning.",
           "expanded": "Scanning",
           "value": "scanner"
         },
         {
-          "description": "Observing and recording of network traffic (wiretapping).",
+          "description": "Observing and recording of network traffic (i.e. wiretapping).",
           "expanded": "Sniffing",
           "value": "sniffing"
         },
         {
-          "description": "Gathering information from a human being in a non-technical way (e.g. lies, tricks, bribes, or threats).",
+          "description": "Gathering information from a human being in a non-technical way (e.g., using lies, tricks, bribes, or threats).",
           "expanded": "Social Engineering",
           "value": "social-engineering"
         }
@@ -68,18 +68,18 @@
     {
       "entry": [
         {
-          "description": "An attempt to compromise a system or to disrupt any service by exploiting vulnerabilities with a standardised identifier such as CVE name (e.g. buffer overflow, backdoor, cross site scripting, etc.)",
-          "expanded": "Exploitation of known Vulnerabilities",
+          "description": "An attempt to compromise a system or to disrupt any service by exploiting vulnerabilities with a standardised identifier such as CVE name (e.g., using a buffer overflow, backdoor, cross site scripting)",
+          "expanded": "Exploitation of Known Vulnerabilities",
           "value": "ids-alert"
         },
         {
-          "description": "Multiple login attempts (Guessing / cracking of passwords, brute force).",
-          "expanded": "Login attempts",
+          "description": "Multiple brute-force login attempts (including guessing or cracking of passwords). This IOC refers to a resource, which has been observed to perform brute-force attacks over a given application protocol.",
+          "expanded": "Login Attempts",
           "value": "brute-force"
         },
         {
           "description": "An attack using an unknown exploit.",
-          "expanded": "New attack signature",
+          "expanded": "New Attack Signature",
           "value": "exploit"
         }
       ],
@@ -88,7 +88,7 @@
     {
       "entry": [
         {
-          "description": "Compromise of a system where the attacker gained administrative privileges.",
+          "description": "Compromise of a system where the attacker has gained administrative privileges.",
           "expanded": "Privileged Account Compromise",
           "value": "privileged-account-compromise"
         },
@@ -98,12 +98,17 @@
           "value": "unprivileged-account-compromise"
         },
         {
-          "description": "Compromise of an application by exploiting (un)known software vulnerabilities, e.g. SQL injection.",
+          "description": "Compromise of an application by exploiting (un)known software vulnerabilities, e.g., SQL injection.",
           "expanded": "Application Compromise",
           "value": "application-compromise"
         },
         {
-          "description": "Physical intrusion, e.g. into corporate building or data center.",
+          "description": "Compromise of a system, e.g., unauthorised logins or commands. This includes attempts to compromise honeypot systems.",
+          "expanded": "System Compromise",
+          "value": "system-compromise"
+        },
+        {
+          "description": "Physical intrusion, e.g., into a corporate building or data centre.",
           "expanded": "Burglary",
           "value": "burglary"
         }
@@ -113,27 +118,27 @@
     {
       "entry": [
         {
-          "description": "Denial of Service attack, e.g. sending specially crafted requests to a web application which causes the application to crash or slow down.",
+          "description": "Denial of Service attack, e.g., sending specially crafted requests to a web application which causes the application to crash or slow down.",
           "expanded": "Denial of Service",
           "value": "dos"
         },
         {
-          "description": "Distributed Denial of Service attack, e.g. SYN-Flood or UDP-based reflection/amplification attacks.",
+          "description": "Distributed Denial of Service attack, e.g., SYN flood or UDP-based reflection/amplification attacks.",
           "expanded": "Distributed Denial of Service",
           "value": "ddos"
         },
         {
-          "description": "Software misconfiguration resulting in service availability issues, e.g. DNS server with outdated DNSSEC Root Zone KSK.",
+          "description": "Software misconfiguration resulting in service availability issues, e.g., DNS server with outdated DNSSEC Root Zone KSK.",
           "expanded": "Misconfiguration",
           "value": "misconfiguration"
         },
         {
-          "description": "Physical sabotage, e.g cutting wires or malicious arson.",
+          "description": "Physical sabotage, e.g., cutting wires or malicious arson.",
           "expanded": "Sabotage",
           "value": "sabotage"
         },
         {
-          "description": "Outage caused e.g. by air condition failure or natural disaster.",
+          "description": "An outage caused, for example, by air conditioning failure or natural disaster.",
           "expanded": "Outage",
           "value": "outage"
         }
@@ -143,19 +148,24 @@
     {
       "entry": [
         {
-          "description": "Unauthorized access to information, e.g. by abusing stolen login credentials for a system or application, intercepting traffic or gaining access to physical documents.",
-          "expanded": "Unauthorised access to information",
+          "description": "Unauthorised access to information, e.g., by abusing stolen login credentials for a system or application, intercepting traffic or gaining access to physical documents.",
+          "expanded": "Unauthorised Access to Information",
           "value": "unauthorised-information-access"
         },
         {
-          "description": "Unauthorised modification of information, e.g. by an attacker abusing stolen login credentials for a system or application or a ransomware encrypting data.",
-          "expanded": "Unauthorised modification of information",
+          "description": "Unauthorised modification of information, e.g., by an attacker abusing stolen login credentials for a system or application, or ransomware encrypting data. Also includes defacements.",
+          "expanded": "Unauthorised Modification of Information",
           "value": "unauthorised-information-modification"
         },
         {
-          "description": "Loss of data, e.g. caused by harddisk failure or physical theft.",
+          "description": "Loss of data caused by, for example, hard disk failure or physical theft.",
           "expanded": "Data Loss",
           "value": "data-loss"
+        },
+        {
+          "description": "Leaked confidential information, e.g., credentials or personal data.",
+          "expanded": "Leak of Confidential Information",
+          "value": "data-leak"
         }
       ],
       "predicate": "information-content-security"
@@ -163,12 +173,12 @@
     {
       "entry": [
         {
-          "description": "Using resources for unauthorized purposes including profit-making ventures, e.g. the use of e-mail to participate in illegal profit chain letters or pyramid schemes.",
-          "expanded": "Unauthorized use of resources",
-          "value": "unauthorized-use-of-resources"
+          "description": "Using resources for unauthorised purposes including profit-making ventures, e.g., the use of email to participate in illegal profit chain letters or pyramid schemes.",
+          "expanded": "Unauthorised Use of Resources",
+          "value": "unauthorised-use-of-resources"
         },
         {
-          "description": "Offering or Installing copies of unlicensed commercial software or other copyright protected materials (Warez).",
+          "description": "Offering or installing copies of unlicensed commercial software or other copyright protected materials (also known as Warez).",
           "expanded": "Copyright",
           "value": "copyright"
         },
@@ -178,7 +188,7 @@
           "value": "masquerade"
         },
         {
-          "description": "Masquerading as another entity in order to persuade the user to reveal private credentials.",
+          "description": "Masquerading as another entity in order to persuade the user to reveal private credentials. This IOC most often refers to a URL, which is used to phish user credentials.",
           "expanded": "Phishing",
           "value": "phishing"
         }
@@ -188,28 +198,28 @@
     {
       "entry": [
         {
-          "description": "Publicly accessible services offering weak crypto, e.g. web servers susceptible to POODLE/FREAK attacks.",
-          "expanded": "Weak crypto",
+          "description": "Publicly accessible services offering weak cryptography, e.g., web servers susceptible to POODLE/FREAK attacks.",
+          "expanded": "Weak Cryptography",
           "value": "weak-crypto"
         },
         {
-          "description": "Publicly accessible services that can be abused for conducting DDoS reflection/amplification attacks, e.g. DNS open-resolvers or NTP servers with monlist enabled.",
-          "expanded": "DDoS amplifier",
+          "description": "Publicly accessible services that can be abused for conducting DDoS reflection/amplification attacks, e.g., DNS open-resolvers or NTP servers with monlist enabled.",
+          "expanded": "DDoS Amplifier",
           "value": "ddos-amplifier"
         },
         {
-          "description": "Potentially unwanted publicly accessible services, e.g. Telnet, RDP or VNC.",
-          "expanded": "Potentially unwanted accessible services",
+          "description": "Potentially unwanted publicly accessible services, e.g., Telnet, RDP or VNC.",
+          "expanded": "Potentially Unwanted Accessible Services",
           "value": "potentially-unwanted-accessible"
         },
         {
-          "description": "Publicly accessible services potentially disclosing sensitive information, e.g. SNMP or Redis.",
+          "description": "Publicly accessible services potentially disclosing sensitive information, e.g., SNMP or Redis.",
           "expanded": "Information disclosure",
           "value": "information-disclosure"
         },
         {
-          "description": "A system which is vulnerable to certain attacks. Example: misconfigured client proxy settings (example: WPAD), outdated operating system version, etc.",
-          "expanded": "Vulnerable system",
+          "description": "A system which is vulnerable to certain attacks, e.g., misconfigured client proxy settings (such as WPAD), outdated operating system version, or cross-site scripting vulnerabilities.",
+          "expanded": "Vulnerable System",
           "value": "vulnerable-system"
         }
       ],
@@ -218,9 +228,14 @@
     {
       "entry": [
         {
-          "description": "All incidents which don't fit in one of the given categories should be put into this class.",
-          "expanded": "Other",
+          "description": "All incidents which don't fit in one of the given categories should be put into this class or the incident is not categorised.",
+          "expanded": "Uncategorised",
           "value": "other"
+        },
+        {
+          "description": "The categorisation of the incident is unknown/undetermined.",
+          "expanded": "Undetermined",
+          "value": "undetermined"
         }
       ],
       "predicate": "other"
@@ -258,7 +273,7 @@
       "value": "intrusion-attempts"
     },
     {
-      "description": "A successful compromise of a system or application (service). This can have been caused remotely by a known or new vulnerability, but also by an unauthorized local access. Also includes being part of a botnet.",
+      "description": "A successful compromise of a system or application (service). This can have been caused remotely by a known or new vulnerability, but also by an unauthorised local access. Also includes being part of a botnet.",
       "expanded": "Intrusions",
       "value": "intrusions"
     },
@@ -278,12 +293,12 @@
       "value": "fraud"
     },
     {
-      "description": "Open resolvers, world readable printers, vulnerability apparent from Nessus etc scans, virus signatures not up-to-date, etc",
+      "description": "Open resolvers, world-readable printers, vulnerabilities apparent from scans, anti-virus signatures not up-to-date, etc.",
       "expanded": "Vulnerable",
       "value": "vulnerable"
     },
     {
-      "description": "All incidents which don't fit in one of the given categories should be put into this class. If the number of incidents in this category increases, it is an indicator that the classification scheme must be revised",
+      "description": "All incidents which don't fit in one of the given categories should be put into this class. If the number of incidents in this category increases, it is an indicator that the classification scheme must be revised.",
       "expanded": "Other",
       "value": "other"
     },
@@ -293,7 +308,7 @@
       "value": "test"
     }
   ],
-  "version": 3,
+  "version": 1003,
   "description": "Reference Security Incident Classification Taxonomy",
   "namespace": "rsit"
 }

summary.md

@@ -1,5 +1,5 @@
 # Taxonomies
-- Generation date: 2020-01-09
+- Generation date: 2021-04-13
 - license: CC-0
 - description: Manifest file of MISP taxonomies available.
 
@@ -21,6 +21,27 @@
     - conformity
     - other
     - test
+### DFRLab-dichotomies-of-disinformation
+- description: DFRLab Dichotomies of Disinformation.
+- version: 1
+- Predicates
+    - primary-target
+    - platforms-advertisement
+    - platforms-email
+    - primary-disinformant
+    - target-category
+    - target-concurrent-events
+    - platforms-open-web
+    - platforms-social-media
+    - platforms-messaging
+    - platforms
+    - content-language
+    - content-topic
+    - methods-tactics
+    - methods-narrative-techniques
+    - disinformant-category
+    - disinformant-concurrent-events
+    - disinformant-intent
 ### DML
 - description: 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.
 - version: 1
@@ -98,7 +119,7 @@
     - information-credibility
 ### adversary
 - description: An overview and description of the adversary infrastructure
-- version: 4
+- version: 6
 - Predicates
     - infrastructure-status
     - infrastructure-action
@@ -159,7 +180,7 @@
     - threat-vector
 ### circl
 - description: CIRCL Taxonomy - Schemes of Classification in Incident Response and Detection
-- version: 3
+- version: 5
 - Predicates
     - incident-classification
     - topic
@@ -259,6 +280,22 @@
     - report
     - origin
     - analyse
+### cti
+- description: Cyber Threat Intelligence cycle to control workflow state of your process.
+- version: 1
+- Predicates
+    - planning
+    - collection
+    - processing-and-analysis
+    - dissemination-done
+    - feedback-received
+    - feedback-pending
+### current-event
+- description: Current events - Schemes of Classification in Incident Response and Detection
+- version: 1
+- Predicates
+    - pandemic
+    - election
 ### cyber-threat-framework
 - description: 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
 - version: 2
@@ -267,6 +304,17 @@
     - Engagement
     - Presence
     - Effect/Consequence
+### cycat
+- description: Taxonomy used by CyCAT, the Universal Cybersecurity Resource Catalogue, to categorize the namespaces it supports and uses.
+- version: 1
+- Predicates
+    - type
+    - scope
+### cytomic-orion
+- description: Taxonomy to describe desired actions for Cytomic Orion
+- version: 1
+- Predicates
+    - action
 ### dark-web
 - description: Criminal motivation on the dark web: A categorisation model for law enforcement. ref: Janis Dalins, Campbell Wilson, Mark Carman. Taxonomy updated by MISP Project
 - version: 3
@@ -406,7 +454,7 @@
     - info-services
     - public-admin
 ### eu-nis-sector-and-subsectors
-- description: Sectors and sub sectors as identified by the NIS Directive
+- description: Sectors, subsectors, and digital services as identified by the NIS Directive
 - version: 1
 - Predicates
     - eu-nis-oes
@@ -501,7 +549,7 @@
     - event-class
 ### exercise
 - description: Exercise is a taxonomy to describe if the information is part of one or more cyber or crisis exercise.
-- version: 7
+- version: 8
 - Predicates
     - cyber-europe
     - cyber-storm
@@ -510,12 +558,22 @@
     - cyber-coalition
     - pace
     - cyber-sopex
+    - generic
+### extended-event
+- description: Reasons why an event has been extended. 
+- version: 1
+- Predicates
+    - competitive-analysis
+    - extended-analysis
+    - human-readable
+    - chunked-event
+    - update
 ### failure-mode-in-machine-learning
 - description: The purpose of this taxonomy is to jointly tabulate both the of these failure modes in a single place. Intentional failures wherein the failure is caused by an active adversary attempting to subvert the system to attain her goals – either to misclassify the result, infer private training data, or to steal the underlying algorithm. Unintentional failures wherein the failure is because an ML system produces a formally correct but completely unsafe outcome.
 - version: 1
 - Predicates
-    - unintended-failures-summary
     - intentionally-motivated-failures-summary
+    - unintended-failures-summary
 ### false-positive
 - description: This taxonomy aims to ballpark the expected amount of false positives.
 - version: 5
@@ -789,6 +847,11 @@
     - dns
     - host-file
     - other
+### ioc
+- description: An IOC classification to facilitate automation of malicious and non malicious artifacts
+- version: 2
+- Predicates
+    - artifact-state
 ### iot
 - description: Internet of Things taxonomy, based on IOT UK report https://iotuk.org.uk/wp-content/uploads/2017/01/IOT-Taxonomy-Report.pdf
 - version: 2
@@ -835,9 +898,26 @@
     - obfuscation-technique
     - payload-classification
     - memory-classification
+### misinformation-website-label
+- description: classification for the identification of type of misinformation among websites. Source:False, Misleading, Clickbait-y, and/or Satirical News Sources by Melissa Zimdars 2019
+- version: 1
+- Predicates
+    - fake-news
+    - satire
+    - extreme-bias
+    - conspiracy
+    - rumor
+    - state-news
+    - junk-sciences
+    - hate-news
+    - clickbait
+    - proceed-with-caution
+    - political
+    - credible
+    - unknown
 ### misp
 - description: MISP taxonomy to infer with MISP behavior or operation.
-- version: 11
+- version: 12
 - Predicates
     - ui
     - api
@@ -850,6 +930,7 @@
     - tool
     - misp2yara
     - ids
+    - event-type
 ### monarc-threat
 - description: MONARC Threats Taxonomy
 - version: 1
@@ -907,6 +988,11 @@
     - source-type
     - lifetime
     - certainty
+### pandemic
+- description: Pandemic
+- version: 4
+- Predicates
+    - covid-19
 ### passivetotal
 - description: Tags from RiskIQ's PassiveTotal service
 - version: 2
@@ -952,12 +1038,16 @@
     - baseline-negligible
 ### ransomware
 - description: Ransomware is used to define ransomware types and the elements that compose them.
-- version: 4
+- version: 6
 - Predicates
     - type
     - element
     - complexity-level
     - purpose
+    - target
+    - infection
+    - communication
+    - malicious-action
 ### retention
 - description: Add a retenion time to events to automatically remove the IDS-flag on ip-dst or ip-src attributes. We calculate the time elapsed based on the date of the event. Supported time units are: d(ays), w(eeks), m(onths), y(ears). The numerical_value is just for sorting in the web-interface and is not used for calculations.
 - version: 3
@@ -975,7 +1065,7 @@
     - 10y
 ### rsit
 - description: Reference Security Incident Classification Taxonomy
-- version: 3
+- version: 1002
 - Predicates
     - abusive-content
     - malicious-code
@@ -1069,6 +1159,14 @@
 - Predicates
     - targeting-sophistication-base-value
     - technical-sophistication-multiplier
+### ThreatMatch
+- description: The ThreatMatch Sectors, Incident types, Malware types and Alert types are applicable for any ThreatMatch instances and should be used for all CIISI and TIBER Projects.
+- version: 1
+- Predicates
+    - sector
+    - incident-type
+    - malware-type
+    - alert-type
 ### threats-to-dns
 - description: 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
 - version: 1
@@ -1090,6 +1188,13 @@
 - version: 1
 - Predicates
     - tor-relay-type
+### trust
+- description: The Indicator of Trust provides insight about data on what can be trusted and known as a good actor. Similar to a whitelist but on steroids, reusing features one would use with Indicators of Compromise, but to filter out what is known to be good.
+- version: 1
+- Predicates
+    - trust
+    - frequency
+    - valid
 ### type
 - description: Taxonomy to describe different types of intelligence gathering discipline which can be described the origin of intelligence.
 - version: 1
@@ -1180,6 +1285,13 @@
     - victim:revenue:iso_currency_code
     - attribute:availability:duration:unit
     - attribute:confidentiality:data:variety
+### vmray
+- description: VMRay taxonomies to map VMRay Thread Identifier scores and artifacts.
+- version: 1
+- Predicates
+    - artifact
+    - verdict
+    - vti_analysis_score
 ### vocabulaire-des-probabilites-estimatives
 - description: Ce vocabulaire attribue des valeurs en pourcentage à certains énoncés de probabilité
 - version: 3

thales_group/machinetag.json

@@ -0,0 +1,119 @@
+{
+  "predicates": [
+    {
+      "value": "distribution",
+      "exclusive": true
+    },
+    {
+      "colour": "#750806",
+      "description": "This TAG will insure you that these Event Attributes will be blocked on the Thales DIS Proxy (More to come). Distribution: All communities",
+      "expanded": "Use it when you want to block Event Attributes on the Thales DIS Proxy (More to come). Distribution: All communities",
+      "value": "to_block",
+      "numerical_value": 4
+    },
+    {
+      "colour": "#0A1EF7",
+      "description": "This TAG will insure you to share ONLY to the Thales Group MinArm alliance. Distribution: All communities",
+      "expanded": "Use it when you want to share to the Thales Group MinArm alliance ONLY. Distribution: All communities",
+      "value": "minarm",
+      "numerical_value": 5
+    },
+    {
+      "colour": "#A107E3",
+      "description": "This TAG will insure you to share ONLY to the Thales Group ACN alliance. Distribution: All communities",
+      "expanded": "Use it when you want to share to the Thales Group ACN alliance ONLY. Distribution: All communities",
+      "value": "acn",
+      "numerical_value": 6
+    },
+    {
+      "colour": "#FF6F00",
+      "description": "This TAG will insure you to share ONLY to the Thales Group Sigpart alliance. Distribution: All communities",
+      "expanded": "Use it when you want to share to the Thales Group Sigpart alliance ONLY. Distribution: All communities",
+      "value": "sigpart",
+      "numerical_value": 7
+    },
+    {
+      "colour": "#75646A",
+      "description": "Distribution: All communities",
+      "expanded": "Use it when you want to assign a trust category to an Attribute or Globally to an Event. Distribution: All communities",
+      "value": "ioc_confidence",
+      "exclusive": true
+    },
+    {
+      "colour": "#000000",
+      "description": "Distribution: Restricted Sharing Group",
+      "expanded": "(TLP:BLACK) Information cannot be effectively acted outside of strict and reduced circle of a trust. Distribution: Restricted Sharing Group",
+      "value": "tlp:black",
+      "numerical_value": 11
+    },
+    {
+      "colour": "#375a7f",
+      "description": "Distribution: All communities",
+      "expanded": "Use it when this came from Watcher Platform. Distribution: All communities",
+      "value": "Watcher",
+      "numerical_value": 12
+    }
+  ],
+  "values": [
+    {
+      "predicate": "distribution",
+      "entry": [
+        {
+          "colour": "#CC0033",
+          "description": "This TAG will insure you that this Event will be kept on your side. This Event will NOT be shared to the Thales Group community. Distribution: Your organisation only",
+          "expanded": "Use it when you want to keep the Event on your Organization ONLY. Distribution: Your organisation only",
+          "value": "team_eyes_only",
+          "numerical_value": 0
+        },
+        {
+          "colour": "#FFC000",
+          "description": "This TAG will insure you to share ONLY to the Thales Group Community. Distribution: All communities",
+          "expanded": "Use it when you want to share to the Thales Group Community ONLY. Distribution: All communities",
+          "value": "limited_distribution",
+          "numerical_value": 1
+        },
+        {
+          "colour": "#339900",
+          "description": "This TAG will insure you to share to the Thales Group External Alliances. Distribution: All communities",
+          "expanded": "Use it when you want to share to the Thales Group External Alliances (MinArm, ACN, InterCERT-FR). Distribution: All communities",
+          "value": "external_alliances",
+          "numerical_value": 2
+        },
+        {
+          "colour": "#ffffff",
+          "description": "This TAG will insure you to share to the Thales Group Customers. Distribution: All communities",
+          "expanded": "Use it when you want to share to the Thales Group Customers. Distribution: All communities",
+          "value": "customers",
+          "numerical_value": 3
+        }
+      ]
+    },
+    {
+      "predicate": "ioc_confidence",
+      "entry": [
+        {
+          "value": "high",
+          "expanded": "High",
+          "numerical_value": 8
+        },
+        {
+          "value": "medium",
+          "expanded": "Medium",
+          "numerical_value": 9
+        },
+        {
+          "value": "low",
+          "expanded": "Low",
+          "numerical_value": 10
+        }
+      ]
+    }
+  ],
+  "refs": [
+    "https://www.thalesgroup.com/en/cert"
+  ],
+  "version": 2,
+  "description": "Thales Group Taxonomy - was designed with the aim of enabling desired sharing and preventing unwanted sharing between Thales Group security communities.",
+  "expanded": "Thales Group Taxonomy",
+  "namespace": "thales_group"
+}

threatmatch/README.md

@@ -0,0 +1,2 @@
+## ThreatMatch 
+Incident types, Alert types, Malware types and Sectors should be used for all CIISI and TIBER projects.

threatmatch/machinetag.json

@@ -0,0 +1,514 @@
+{
+  "namespace": "threatmatch",
+  "expanded": "ThreatMatch categories for sharing into ThreatMatch and MISP",
+  "version": 3,
+  "description": "The ThreatMatch Sectors, Incident types, Malware types and Alert types are applicable for any ThreatMatch instances and should be used for all CIISI and TIBER Projects.",
+  "refs": [
+    "https://www.secalliance.com/platform/",
+    "https://www.ecb.europa.eu/press/pr/date/2020/html/ecb.pr200227_1~062992656b.en.html"
+  ],
+  "predicates": [
+    {
+      "value": "sector",
+      "expanded": "Extensive list of sector definition tags"
+    },
+    {
+      "value": "incident-type",
+      "expanded": "Incident tags are used by the ThreatMatch platform to categorise a relevant incident event."
+    },
+    {
+      "value": "malware-type",
+      "expanded": "Malware tags are used by the ThreatMatch platform to categorise malware types."
+    },
+    {
+      "value": "alert-type",
+      "expanded": "Alert tags are used by the ThreatMatch platform to categorise a relevant threat."
+    }
+  ],
+  "values": [
+    {
+      "predicate": "sector",
+      "entry": [
+        {
+          "value": "Banking & Capital Markets",
+          "expanded": "Banking & capital markets"
+        },
+        {
+          "value": "Financial Services",
+          "expanded": "Financial Services"
+        },
+        {
+          "value": "Insurance",
+          "expanded": "Insurance"
+        },
+        {
+          "value": "Pension",
+          "expanded": "Pension"
+        },
+        {
+          "value": "Government & Public Service",
+          "expanded": "Government & Public Service"
+        },
+        {
+          "value": "Diplomatic Services",
+          "expanded": "Diplomatic Services"
+        },
+        {
+          "value": "Energy, Utilities & Mining",
+          "expanded": "Energy, Utilities & Mining"
+        },
+        {
+          "value": "Telecommunications",
+          "expanded": "Telecommunications"
+        },
+        {
+          "value": "Technology",
+          "expanded": "Technology"
+        },
+        {
+          "value": "Academic/Research Institutes",
+          "expanded": "Academic/Research Institutes"
+        },
+        {
+          "value": "Aerospace, Defence & Security",
+          "expanded": "Aerospace, Defence & Security"
+        },
+        {
+          "value": "Agriculture",
+          "expanded": "Agriculture"
+        },
+        {
+          "value": "Asset & Wealth Management",
+          "expanded": "Asset & Wealth Management"
+        },
+        {
+          "value": "Automotive",
+          "expanded": "Automotive"
+        },
+        {
+          "value": "Business and Professional Services",
+          "expanded": "Business and Professional Services"
+        },
+        {
+          "value": "Capital Projects & Infrastructure",
+          "expanded": "Capital Projects & Infrastructure"
+        },
+        {
+          "value": "Charity/Not-for-Profit",
+          "expanded": "Charity/Not-for-Profit"
+        },
+        {
+          "value": "Chemicals",
+          "expanded": "Chemicals"
+        },
+        {
+          "value": "Commercial Aviation",
+          "expanded": "Commercial Aviation"
+        },
+        {
+          "value": "Commodities",
+          "expanded": "Commodities"
+        },
+        {
+          "value": "Education",
+          "expanded": "Education"
+        },
+        {
+          "value": "Engineering & Construction",
+          "expanded": "Engineering & Construction"
+        },
+        {
+          "value": "Entertainment & Media",
+          "expanded": "Entertainment & Media"
+        },
+        {
+          "value": "Forest, Paper & Packaging",
+          "expanded": "Forest, Paper & Packaging"
+        },
+        {
+          "value": "Healthcare",
+          "expanded": "Healthcare"
+        },
+        {
+          "value": "Hospitality & Leisure",
+          "expanded": "Hospitality & Leisure"
+        },
+        {
+          "value": "Industrial Manufacturing",
+          "expanded": "Industrial Manufacturing"
+        },
+        {
+          "value": "IT Industry",
+          "expanded": "IT Industry"
+        },
+        {
+          "value": "Legal",
+          "expanded": "Legal"
+        },
+        {
+          "value": "Metals",
+          "expanded": "Metals"
+        },
+        {
+          "value": "Pharmaceuticals & Life Sciences",
+          "expanded": "Pharmaceuticals & Life Sciences"
+        },
+        {
+          "value": "Private Equity",
+          "expanded": "Private Equity"
+        },
+        {
+          "value": "Retail & Consumer",
+          "expanded": "Retail & Consumer"
+        },
+        {
+          "value": "Semiconductors",
+          "expanded": "Semiconductors"
+        },
+        {
+          "value": "Sovereign Investment Funds",
+          "expanded": "Sovereign Investment Funds"
+        },
+        {
+          "value": "Transport & Logistics",
+          "expanded": "Transport & Logistics"
+        }
+      ]
+    },
+    {
+      "predicate": "incident-type",
+      "entry": [
+        {
+          "value": "ATM Attacks",
+          "expanded": "ATM Attacks"
+        },
+        {
+          "value": "ATM Breach",
+          "expanded": "ATM Breach"
+        },
+        {
+          "value": "Attempted Exploitation",
+          "expanded": "Attempted Exploitation"
+        },
+        {
+          "value": "Botnet Activity",
+          "expanded": "Botnet Activity"
+        },
+        {
+          "value": "Business Email Compromise",
+          "expanded": "Business Email Compromise"
+        },
+        {
+          "value": "Crypto Mining",
+          "expanded": "Crypto Mining"
+        },
+        {
+          "value": "Data Breach/Compromise",
+          "expanded": "Data Breach/Compromise"
+        },
+        {
+          "value": "Data Dump",
+          "expanded": "Data Dump"
+        },
+        {
+          "value": "Data Leakage",
+          "expanded": "Data Leakage"
+        },
+        {
+          "value": "DDoS",
+          "expanded": "DDoS"
+        },
+        {
+          "value": "Defacement Activity",
+          "expanded": "Defacement Activity"
+        },
+        {
+          "value": "Denial of Service (DoS)",
+          "expanded": "Denial of Service (DoS)"
+        },
+        {
+          "value": "Disruption Activity",
+          "expanded": "Disruption Activity"
+        },
+        {
+          "value": "Espionage",
+          "expanded": "Espionage"
+        },
+        {
+          "value": "Espionage Activity",
+          "expanded": "Espionage Activity"
+        },
+        {
+          "value": "Exec Targeting ",
+          "expanded": "Exec Targeting "
+        },
+        {
+          "value": "Exposure of Data",
+          "expanded": "Exposure of Data"
+        },
+        {
+          "value": "Extortion Activity",
+          "expanded": "Extortion Activity"
+        },
+        {
+          "value": "Fraud Activity",
+          "expanded": "Fraud Activity"
+        },
+        {
+          "value": "General Notification",
+          "expanded": "General Notification"
+        },
+        {
+          "value": "Hacktivism Activity",
+          "expanded": "Hacktivism Activity"
+        },
+        {
+          "value": "Malicious Insider",
+          "expanded": "Malicious Insider"
+        },
+        {
+          "value": "Malware Infection",
+          "expanded": "Malware Infection"
+        },
+        {
+          "value": "Man in the Middle Attacks",
+          "expanded": "Man in the Middle Attacks"
+        },
+        {
+          "value": "MFA Attack",
+          "expanded": "MFA Attack"
+        },
+        {
+          "value": "Mobile Malware",
+          "expanded": "Mobile Malware"
+        },
+        {
+          "value": "Phishing Activity",
+          "expanded": "Phishing Activity"
+        },
+        {
+          "value": "Ransomware Activity",
+          "expanded": "Ransomware Activity"
+        },
+        {
+          "value": "Social Engineering Activity",
+          "expanded": "Social Engineering Activity"
+        },
+        {
+          "value": "Social Media Compromise",
+          "expanded": "Social Media Compromise"
+        },
+        {
+          "value": "Spear-phishing Activity",
+          "expanded": "Spear-phishing Activity"
+        },
+        {
+          "value": "Spyware",
+          "expanded": "Spyware"
+        },
+        {
+          "value": "SQL Injection Activity",
+          "expanded": "SQL Injection Activity"
+        },
+        {
+          "value": "Supply Chain Compromise",
+          "expanded": "Supply Chain Compromise"
+        },
+        {
+          "value": "Trojanised Software",
+          "expanded": "Trojanised Software"
+        },
+        {
+          "value": "Vishing",
+          "expanded": "Vishing"
+        },
+        {
+          "value": "Website Attack (Other)",
+          "expanded": "Website Attack (Other)"
+        },
+        {
+          "value": "Unknown",
+          "expanded": "Unknown"
+        }
+      ]
+    },
+    {
+      "predicate": "malware-type",
+      "entry": [
+        {
+          "value": "Adware",
+          "expanded": "Adware"
+        },
+        {
+          "value": "Backdoor",
+          "expanded": "Backdoor"
+        },
+        {
+          "value": "Banking Trojan",
+          "expanded": "Banking Trojan"
+        },
+        {
+          "value": "Botnet",
+          "expanded": "Botnet"
+        },
+        {
+          "value": "Destructive",
+          "expanded": "Destructive"
+        },
+        {
+          "value": "Downloader",
+          "expanded": "Downloader"
+        },
+        {
+          "value": "Exploit Kit",
+          "expanded": "Exploit Kit"
+        },
+        {
+          "value": "Fileless Malware",
+          "expanded": "Fileless Malware"
+        },
+        {
+          "value": "Keylogger",
+          "expanded": "Keylogger"
+        },
+        {
+          "value": "Legitimate Tool",
+          "expanded": "Legitimate Tool"
+        },
+        {
+          "value": "Mobile Application",
+          "expanded": "Mobile Application"
+        },
+        {
+          "value": "Mobile Malware",
+          "expanded": "Mobile Malware"
+        },
+        {
+          "value": "Point-of-Sale (PoS)",
+          "expanded": "Point-of-Sale (PoS)"
+        },
+        {
+          "value": "Remote Access Trojan",
+          "expanded": "Remote Access Trojan"
+        },
+        {
+          "value": "Rootkit",
+          "expanded": "Rootkit"
+        },
+        {
+          "value": "Skimmer",
+          "expanded": "Skimmer"
+        },
+        {
+          "value": "Spyware",
+          "expanded": "Spyware"
+        },
+        {
+          "value": "Surveillance Tool",
+          "expanded": "Surveillance Tool"
+        },
+        {
+          "value": "Trojan",
+          "expanded": "Trojan"
+        },
+        {
+          "value": "Virus",
+          "expanded": "Virus "
+        },
+        {
+          "value": "Worm",
+          "expanded": "Worm"
+        },
+        {
+          "value": "Zero-day",
+          "expanded": "Zero-day"
+        },
+        {
+          "value": "Unknown",
+          "expanded": "Unknown"
+        }
+      ]
+    },
+    {
+      "predicate": "alert-type",
+      "entry": [
+        {
+          "value": "Actor Campaigns",
+          "expanded": "Actor Campaigns"
+        },
+        {
+          "value": "Credential Breaches",
+          "expanded": "Credential Breaches"
+        },
+        {
+          "value": "DDoS",
+          "expanded": "DDoS"
+        },
+        {
+          "value": "Exploit Alert",
+          "expanded": "Exploit Alert"
+        },
+        {
+          "value": "General Notification",
+          "expanded": "General Notification"
+        },
+        {
+          "value": "High Impact Vulnerabilities",
+          "expanded": "High Impact Vulnerabilities"
+        },
+        {
+          "value": "Information Leakages",
+          "expanded": "Information Leakages"
+        },
+        {
+          "value": "Malware Analysis",
+          "expanded": "Malware Analysis"
+        },
+        {
+          "value": "Nefarious Domains",
+          "expanded": "Nefarious Domains"
+        },
+        {
+          "value": "Nefarious Forum Mention",
+          "expanded": "Nefarious Forum Mention"
+        },
+        {
+          "value": "Pastebin Dumps",
+          "expanded": "Pastebin Dumps"
+        },
+        {
+          "value": "Phishing Attempts",
+          "expanded": "Phishing Attempts"
+        },
+        {
+          "value": "PII Exposure",
+          "expanded": "PII Exposure"
+        },
+        {
+          "value": "Sensitive Information Disclosures",
+          "expanded": "Sensitive Information Disclosures"
+        },
+        {
+          "value": "Social Media Alerts",
+          "expanded": "Social Media Alerts"
+        },
+        {
+          "value": "Supply Chain Event",
+          "expanded": "Supply Chain Event"
+        },
+        {
+          "value": "Technical Exposure",
+          "expanded": "Technical Exposure"
+        },
+        {
+          "value": "Threat Actor Updates",
+          "expanded": "Threat Actor Updates"
+        },
+        {
+          "value": "Trigger Events",
+          "expanded": "Trigger Events"
+        }
+      ]
+    }
+  ]
+}

tools/gen_manifest.py

@@ -23,7 +23,7 @@ def generateManifest(taxonomies):
     manifest = {}
     manifest['taxonomies'] = []
     manifest['path'] = 'machinetag.json'
-    manifest['url'] = 'https://raw.githubusercontent.com/MISP/misp-taxonomies/master/'
+    manifest['url'] = 'https://raw.githubusercontent.com/MISP/misp-taxonomies/main/'
     manifest['description'] = 'Manifest file of MISP taxonomies available.'
     manifest['license'] = 'CC-0'
     now = datetime.now()

tools/generator/misp-galaxy.py

@@ -2,7 +2,7 @@ import json
 import requests
 
 debug = False
-galaxy_url = 'https://raw.githubusercontent.com/MISP/misp-galaxy/master/clusters/'
+galaxy_url = 'https://raw.githubusercontent.com/MISP/misp-galaxy/main/clusters/'
 elements = ['tools.json', 'threat-actors.json']
 # elements = ['threat-actor-tools.json']
 

tools/machinetag.py

@@ -88,7 +88,7 @@ def asciidoc(content=False, adoc=doc, t='title', toplevel=False):
         content = '=== ' + content
     elif t == 'namespace':
         content = '== ' + content + '\n'
-        content = "{}\n{}{} {}{}{} {}".format(content, 'NOTE: ', namespace, 'namespace available in JSON format at https://github.com/MISP/misp-taxonomies/blob/master/',
+        content = "{}\n{}{} {}{}{} {}".format(content, 'NOTE: ', namespace, 'namespace available in JSON format at https://github.com/MISP/misp-taxonomies/blob/main/',
                                                 namespace, '/machinetag.json[*this location*]. The JSON format can be freely reused in your application',
                                                 'or automatically enabled in https://www.github.com/MISP/MISP[MISP] taxonomy.')
     elif t == 'description' and toplevel is True:

tools/website-genlist.py

@@ -1,9 +1,12 @@
 import json
 import os
 import re
+
 filename = os.path.join("../", "MANIFEST.json")
 with open(filename) as fp:
-	t = json.load(fp)
+    t = json.load(fp)
 
 for taxo in sorted(t['taxonomies'], key=lambda k: k['name']):
-    print ("[{}](https://github.com/MISP/misp-taxonomies/tree/master/{}):\n: {}[HTML](https://www.misp-project.org/taxonomies.html#_{})\n".format(taxo['name'], taxo['name'], taxo['description'], re.sub(r'-', '_',taxo['name'])))
+    print("### {}".format(taxo['name']))
+    print()
+    print("[{}](https://github.com/MISP/misp-taxonomies/tree/main/{}) :\n{} [Overview](https://www.misp-project.org/taxonomies.html#_{})\n".format(taxo['name'], taxo['name'], taxo['description'], re.sub(r'-', '_',taxo['name'])))

vmray/machinetag.json

@@ -0,0 +1,91 @@
+{
+  "description": "VMRay taxonomies to map VMRay Thread Identifier scores and artifacts.",
+  "namespace": "vmray",
+  "predicates": [
+    {
+      "expanded": "VMRay Verdict",
+      "value": "verdict"
+    },
+    {
+      "expanded": "VMRay Threat Identifier Analysis Score",
+      "value": "vti_analysis_score"
+    },
+    {
+      "expanded": "VMRay Artifact",
+      "value": "artifact"
+    }
+  ],
+  "values": [
+    {
+      "entry": [
+        {
+          "colour": "#B22F45",
+          "expanded": "Malicious",
+          "value": "malicious"
+        },
+        {
+          "colour": "#EDBB7E",
+          "expanded": "Suspicious",
+          "value": "suspicious"
+        },
+        {
+          "colour": "#3A9A81",
+          "expanded": "Clean",
+          "value": "clean"
+        },
+        {
+          "colour": "#969696",
+          "expanded": "N/A",
+          "value": "n/a"
+        }
+      ],
+      "predicate": "verdict"
+    },
+    {
+      "entry": [
+        {
+          "colour": "#3A9A81",
+          "expanded": "-1/5",
+          "value": "-1/5"
+        },
+        {
+          "colour": "#969696",
+          "expanded": "1/5",
+          "value": "1/5"
+        },
+        {
+          "colour": "#F9DA51",
+          "expanded": "2/5",
+          "value": "2/5"
+        },
+        {
+          "colour": "#EDBB7E",
+          "expanded": "3/5",
+          "value": "3/5"
+        },
+        {
+          "colour": "#E25959",
+          "expanded": "4/5",
+          "value": "4/5"
+        },
+        {
+          "colour": "#B22F45",
+          "expanded": "5/5",
+          "value": "5/5"
+        }
+      ],
+      "predicate": "vti_analysis_score"
+    },
+    {
+      "entry": [
+        {
+          "colour": "#1E516E",
+          "expanded": "is IOC",
+          "value": "ioc"
+        }
+      ],
+      "predicate": "artifact"
+    }
+  ],
+  "version": 1
+}