chg: [MANIFEST] update

MANIFEST.json

@@ -4,7 +4,7 @@
   "path": "machinetag.json",
   "taxonomies": [
     {
-      "description": "The Targeted Threat Index is a metric for assigning an overall threat ranking score to email messages that deliver malware to a victim\u2019s computer. The TTI metric was first introduced at SecTor 2013 by Seth Hardy as part of the talk \u201cRATastrophe: Monitoring a Malware Menagerie\u201d along with Katie Kleemola and Greg Wiseman.",
+      "description": "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.",
       "name": "targeted-threat-index",
       "version": 3
     },
@@ -94,7 +94,7 @@
       "version": 2
     },
     {
-      "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\u20131. doi:10.1109/comst.2018.2849614",
+      "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",
       "version": 1
     },
@@ -124,7 +124,7 @@
       "version": 0
     },
     {
-      "description": "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 \u2018The Business\u2019.",
+      "description": "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’.",
       "name": "gea-nz-activities",
       "version": 1
     },
@@ -234,7 +234,7 @@
       "version": 2
     },
     {
-      "description": "Taxonom\u00eda CSIRT Am\u00e9ricas.",
+      "description": "Taxonomía CSIRT Américas.",
       "name": "csirt-americas",
       "version": 1
     },
@@ -334,7 +334,7 @@
       "version": 3
     },
     {
-      "description": "Ce vocabulaire attribue des valeurs en pourcentage \u00e0 certains \u00e9nonc\u00e9s de probabilit\u00e9",
+      "description": "Ce vocabulaire attribue des valeurs en pourcentage à certains énoncés de probabilité",
       "name": "vocabulaire-des-probabilites-estimatives",
       "version": 3
     },
@@ -464,7 +464,7 @@
       "version": 1
     },
     {
-      "description": "Updated (CIRCL, Seamus Dowling and EURECOM) from Christian Seifert, Ian Welch, Peter Komisarczuk, \u2018Taxonomy of Honeypots\u2019, 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",
+      "description": "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",
       "name": "honeypot-basic",
       "version": 4
     },
@@ -529,11 +529,11 @@
       "version": 5
     },
     {
-      "description": "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\u2019s with proper case handling procedures and will form the basis of SLA\u2019s between the CSIRT and other Company departments.",
+      "description": "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.",
       "name": "csirt_case_classification",
       "version": 1
     }
   ],
   "url": "https://raw.githubusercontent.com/MISP/misp-taxonomies/master/",
   "version": "20191105"
-}
+}