From 089fdef34ff5c447ac94180e2a0f9e3f309ea23c Mon Sep 17 00:00:00 2001
From: Jeroen Pinoy <jeroen.pinoy@fortitude.ninja>
Date: Thu, 11 Apr 2024 16:29:27 +0200
Subject: [PATCH] chg: [misp:event-type] Add description of the tags

---
 misp/machinetag.json | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/misp/machinetag.json b/misp/machinetag.json
index b067ad6..7dacd99 100644
--- a/misp/machinetag.json
+++ b/misp/machinetag.json
@@ -158,27 +158,27 @@
       "predicate": "event-type",
       "entry": [
         {
-          "expanded": "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 SOC 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.",
           "value": "observation"
         },
         {
-          "expanded": "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.",
           "value": "incident"
         },
         {
-          "expanded": "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.",
           "value": "report"
         },
         {
-          "expanded": "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.",
           "value": "collection"
         },
         {
-          "expanded": "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.",
           "value": "analysis"
         },
         {
-          "expanded": "automatic-analysis",
+          "expanded": "This event is the result of automated analysis.",
           "value": "automatic-analysis"
         }
       ]
@@ -261,7 +261,7 @@
       "value": "ids"
     }
   ],
-  "version": 12,
+  "version": 13,
   "description": "MISP taxonomy to infer with MISP behavior or operation.",
   "expanded": "MISP",
   "namespace": "misp"