From 9704a7fced8d4c8ad0303d0856f079f0db984d4d Mon Sep 17 00:00:00 2001
From: Mezz <alexander.heidorn@dcso.de>
Date: Mon, 25 Mar 2019 13:22:56 +0100
Subject: [PATCH] DCSO Sharing Taxonomy added

---
 MANIFEST.json                |  5 +++++
 README.md                    |  1 +
 dcso-sharing/machinetag.json | 43 ++++++++++++++++++++++++++++++++++++
 3 files changed, 49 insertions(+)
 create mode 100644 dcso-sharing/machinetag.json

diff --git a/MANIFEST.json b/MANIFEST.json
index 2bc7b0a..0646d25 100644
--- a/MANIFEST.json
+++ b/MANIFEST.json
@@ -75,6 +75,11 @@
       "name": "cssa",
       "description": "The CSSA agreed sharing taxonomy."
     },
+    {
+      "version": 1,
+      "name": "DCSO-Sharing",
+      "description": "DCSO Sharing Taxonomy to classify certain types of MISP events using the DCSO Event Guide"
+    },
     {
       "version": 2,
       "name": "ddos",
diff --git a/README.md b/README.md
index 2ac1bba..996b5ce 100644
--- a/README.md
+++ b/README.md
@@ -27,6 +27,7 @@ The following taxonomies are described:
 - [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.
 - 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)
diff --git a/dcso-sharing/machinetag.json b/dcso-sharing/machinetag.json
new file mode 100644
index 0000000..c835d95
--- /dev/null
+++ b/dcso-sharing/machinetag.json
@@ -0,0 +1,43 @@
+{
+    "namespace": "DCSO-Sharing",
+    "description": "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.",
+    "version": 1,
+    "predicates": [
+      {
+        "value": "event-type"
+      }
+    ],
+    "values": [
+      {
+        "predicate": "event-type",
+        "entry": [
+          {
+            "value": "Observation",
+            "expanded": "This event describes traits and indicators closely related to a single entity, like an email campaign or sighting of a reference sample on VirusTotal. Events of this type are typically created by CSOC staff and may be verified by analysts. Observed and verified indicators would be consumed by automated filtering systems in order to support near-time threat prevention. In retrospect, observations could be correlated with reports and analysis events in order to help understand the motivation for an attack and to reassess the associated risk.",
+            "colour": "#00233e"
+          },
+          {
+            "value": "Incident",
+            "expanded": "This event describes traits and indicators related to a security incident. As such, the event may refer to multiple entities like organizations, bank account numbers, files, and URLs. Events of this type contain first-hand information, that is, the reporting organization took part in the analysis of the incident. Use event type \"Report\" for second-hand information. Events of this type are typically created and consumed by analysts.",
+            "colour": "#005d81"
+          },
+          {
+            "value": "Report",
+            "expanded": "Traceability of indicators can be essential to document compliance of processes with legal obligations or company regulations. This event preserves a report to document the origin and context of indicators. Events of this type need to be checked by a human to ensure correct reproduction of indicators and context. Intended consumers are automated processes. Events may also serve as a basis for analysis reports or to justify preventive measures. If your organization is or was directly involved in an incident and you want to provide a first-hand account, then please use event type \"Incident\" instead.",
+            "colour": "#3f97b8"
+          },
+          {
+            "value": "Analysis",
+            "expanded": "This event builds on \"observation\", \"incident\", and \"report\" events; adds enrichments; and provides context. Events of this type will be created by analysts with support by automated tools. Analysts are also the main consumers.",
+            "colour": "#5a8915"
+          },
+          {
+            "value": "Collection",
+            "expanded": "This event collects unrelated IoCs. For example, an event could combine all network IoCs that were learned of during a day or a week from events of other types.",
+            "colour": "#94a850"
+          }
+        ]
+      }
+    ]
+  }
+  
\ No newline at end of file