-
Notifications
You must be signed in to change notification settings - Fork 18
/
raw.md.txt
1456 lines (1173 loc) · 54.7 KB
/
raw.md.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Network Working Group A. Dulaunoy
Internet-Draft A. Iklody
Intended status: Informational CIRCL
Expires: 24 August 2024 21 February 2024
MISP taxonomy format
draft-08
Abstract
This document describes the MISP taxonomy format, a simple JSON
format used to represent machine tags (also known as triple tags)
vocabularies. A public directory, known as MISP taxonomies, is
available and utilizes the MISP taxonomy format. These taxonomies
are employed to classify cybersecurity events, threats, suspicious
events, or indicators.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 24 August 2024.
Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Dulaunoy & Iklody Expires 24 August 2024 [Page 1]
Internet-Draft MISP taxonomy format February 2024
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions and Terminology . . . . . . . . . . . . . . . 3
2. Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. predicates . . . . . . . . . . . . . . . . . . . . . . . 4
2.3. values . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4. optional fields . . . . . . . . . . . . . . . . . . . . . 4
2.4.1. colour . . . . . . . . . . . . . . . . . . . . . . . 4
2.4.2. description . . . . . . . . . . . . . . . . . . . . . 5
2.4.3. numerical_value . . . . . . . . . . . . . . . . . . . 5
3. Directory . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Sample Manifest . . . . . . . . . . . . . . . . . . . . . 7
4. Sample Taxonomy in MISP taxonomy format . . . . . . . . . . . 7
4.1. Admiralty Scale Taxonomy . . . . . . . . . . . . . . . . 7
4.2. Open Source Intelligence - Classification . . . . . . . . 9
4.3. Available taxonomies in the public directory . . . . . . 11
5. JSON Schema . . . . . . . . . . . . . . . . . . . . . . . . . 22
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
7. Normative References . . . . . . . . . . . . . . . . . . . . 25
8. Informative References . . . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
1. Introduction
Sharing threat information has become a fundamental requirement in
the Internet security and intelligence community at large. This
information can include indicators of compromise, malicious file
indicators, financial fraud indicators, or even detailed information
about a threat actor. Classification plays a crucial role while
sharing such indicators or information, ensuring adequate
distribution, understanding, validation, or action regarding the
shared information. The MISP taxonomies are a public repository of
known vocabularies that can be utilized in threat information
sharing.
Machine tags were introduced in 2007 [machine-tags] to allow users to
be more precise when tagging their pictures with geolocation. So a
machine tag is a tag which uses a special syntax to provide more
information to users and machines. Machine tags are also known as
triple tags due to their format.
In the MISP taxonomy context, machine tags help analysts to classify
their cybersecurity events, indicators or threats. MISP taxonomies
can be used for classification, filtering, triggering actions or
visualisation depending on their use in threat intelligence platforms
such as MISP [MISP-P].
Dulaunoy & Iklody Expires 24 August 2024 [Page 2]
Internet-Draft MISP taxonomy format February 2024
1.1. Conventions and Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. Format
A machine tag is composed of a namespace (MUST), a predicate (MUST)
and an optional value (OPTIONAL).
Machine tags are represented as a string. Below listed are a set of
sample machine tags for different namespaces such as tlp, admiralty-
scale and osint.
tlp:amber
admiralty-scale:information-credibility="1"
osint:source-type="blog-post"
The MISP taxonomy format describes how to define a machine tag
namespace in a parseable format. The objective is to provide a
simple format to describe machine tag (aka triple tag) vocabularies.
2.1. Overview
The MISP taxonomy format uses the JSON [RFC8259] format. Each
namespace is represented as a JSON object with meta information
including the following fields: namespace, description, version,
type.
namespace defines the overall namespace of the machine tag. The
namespace is represented as a string and MUST be present. The
description is represented as a string and MUST be present. A
version is represented as a unsigned integer MUST be present. A type
defines where a specific taxonomy is applicable and a type can be
applicable at event, user or org level. The type is represented as
an array containing one or more type and SHOULD be present. If a
type is not mentioned, by default, the taxonomy is applicable at
event level only. An exclusive boolean property MAY be present and
defines at namespace level if the predicates are mutually exclusive.
predicates defines all the predicates available in the namespace
defined. predicates is represented as an array of JSON objects.
predicates MUST be present and MUST at least content one element.
values defines all the values for each predicate in the namespace
defined. values SHOULD be present.
Dulaunoy & Iklody Expires 24 August 2024 [Page 3]
Internet-Draft MISP taxonomy format February 2024
2.2. predicates
The predicates array contains one or more JSON objects which lists
all the possible predicates. The JSON object contains two fields:
value and expanded. value MUST be present. expanded SHOULD be
present. value is represented as a string and describes the predicate
value. The predicate value MUST not contain spaces or colons.
expanded is represented as a string and describes the human-readable
version of the predicate value. An exclusive property MAY be present
and defines at namespace level if the values are mutually exclusive.
2.3. values
The values array contain one or more JSON objects which lists all the
possible values of a predicate. The JSON object contains two fields:
predicate and entry. predicate is represented as a string and
describes the predicate value. entry is an array with one or more
JSON objects. The JSON object contains two fields: value and
expanded. value MUST be present. expanded SHOULD be present. value is
represented as a string and describes the machine parsable value.
expanded is represented as a string and describes the human-readable
version of the value.
2.4. optional fields
2.4.1. colour
colour fields MAY be used at predicates or values level to set a
specify colour that MAY be used by the implementation. The colour
field is described as an RGB colour fill in hexadecimal
representation.
Example use of the colour field in the Traffic Light Protocol (TLP):
Dulaunoy & Iklody Expires 24 August 2024 [Page 4]
Internet-Draft MISP taxonomy format February 2024
"predicates": [
{
"colour": "#CC0033",
"expanded": "(TLP:RED) Information exclusively and directly
given to (a group of) individual recipients.
Sharing outside is not legitimate.",
"value": "red"
},
{
"colour": "#FFC000",
"expanded": "(TLP:AMBER) Information exclusively given
to an organization; sharing limited within
the organization to be effectively acted upon.",
"value": "amber"
}...]
2.4.2. description
description fields MAY be used at predicates or values level to add a
descriptive and human-readable information about the specific
predicate or value. The field is represented as a string.
Implementations MAY use the description field to improve more
contextual information. The description at the namespace level is a
MUST as described above.
2.4.3. numerical_value
numerical_value fields MAY be used at a predicate or value level to
add a machine-readable numeric value to a specific predicate or
value. The field is represented as a JSON number. Implementations
SHOULD use the decimal value provided to support scoring or
filtering.
The decimal range for numerical_value SHOULD use a range from 0 up to
100. The range is recommended to support common mathematical
properties among taxonomies.
Example use of the numerical_value in the MISP confidence level:
Dulaunoy & Iklody Expires 24 August 2024 [Page 5]
Internet-Draft MISP taxonomy format February 2024
{
"predicate": "confidence-level",
"entry": [
{
"expanded": "Completely confident",
"value": "completely-confident",
"numerical_value": 100
},
{
"expanded": "Usually confident",
"value": "usually-confident",
"numerical_value": 75
},
{
"expanded": "Fairly confident",
"value": "fairly-confident",
"numerical_value": 50
},
{
"expanded": "Rarely confident",
"value": "rarely-confident",
"numerical_value": 25
},
{
"expanded": "Unconfident",
"value": "unconfident",
"numerical_value": 0
},
{
"expanded": "Confidence cannot be evaluated",
"value": "confidence-cannot-be-evalued"
}
]
}
3. Directory
The MISP taxonomies directory is publicly available [MISP-T] in a git
repository. The repository contains a directory per namespace then a
file machinetag.json which contains the taxonomy as described in the
format above. In the root of the repository, a MANIFEST.json exists
containing a list of all the taxonomies.
The MANIFEST.json file is composed of an JSON object with metadata
like version, license, description, url and path. A taxonomies array
describes the taxonomy available with the description, name and
version field.
Dulaunoy & Iklody Expires 24 August 2024 [Page 6]
Internet-Draft MISP taxonomy format February 2024
3.1. Sample Manifest
{
"version": "20161009",
"license": "CC-0",
"description": "Manifest file of MISP taxonomies available.",
"url":
"https://raw.githubusercontent.com/MISP/misp-taxonomies/master/",
"path": "machinetag.json",
"taxonomies": [
{
"description": "The Admiralty Scale (also called the NATO System)
is used to rank the reliability of a source and
the credibility of an information.",
"name": "admiralty-scale",
"version": 1
},
{
"description": "Open Source Intelligence - Classification.",
"name": "osint",
"version": 2
}]
}
4. Sample Taxonomy in MISP taxonomy format
4.1. Admiralty Scale Taxonomy
"namespace": "admiralty-scale",
"description": "The Admiralty Scale (also called the NATO System)
is used to rank the reliability of a source and
the credibility of an information.",
"version": 1,
"predicates": [
{
"value": "source-reliability",
"expanded": "Source Reliability"
},
{
"value": "information-credibility",
"expanded": "Information Credibility"
}
],
"values": [
{
"predicate": "source-reliability",
"entry": [
{
Dulaunoy & Iklody Expires 24 August 2024 [Page 7]
Internet-Draft MISP taxonomy format February 2024
"value": "a",
"expanded": "Completely reliable"
},
{
"value": "b",
"expanded": "Usually reliable"
},
{
"value": "c",
"expanded": "Fairly reliable"
},
{
"value": "d",
"expanded": "Not usually reliable"
},
{
"value": "e",
"expanded": "Unreliable"
},
{
"value": "f",
"expanded": "Reliability cannot be judged"
}
]
},
{
"predicate": "information-credibility",
"entry": [
{
"value": "1",
"expanded": "Confirmed by other sources"
},
{
"value": "2",
"expanded": "Probably true"
},
{
"value": "3",
"expanded": "Possibly true"
},
{
"value": "4",
"expanded": "Doubtful"
},
{
"value": "5",
"expanded": "Improbable"
},
Dulaunoy & Iklody Expires 24 August 2024 [Page 8]
Internet-Draft MISP taxonomy format February 2024
{
"value": "6",
"expanded": "Truth cannot be judged"
}
]
}
]
}
4.2. Open Source Intelligence - Classification
{
"values": [
{
"entry": [
{
"expanded": "Blog post",
"value": "blog-post"
},
{
"expanded": "Technical or analysis report",
"value": "technical-report"
},
{
"expanded": "News report",
"value": "news-report"
},
{
"expanded": "Pastie-like website",
"value": "pastie-website"
},
{
"expanded": "Electronic forum",
"value": "electronic-forum"
},
{
"expanded": "Mailing-list",
"value": "mailing-list"
},
{
"expanded": "Block or Filter List",
"value": "block-or-filter-list"
},
{
"expanded": "Expansion",
"value": "expansion"
}
],
Dulaunoy & Iklody Expires 24 August 2024 [Page 9]
Internet-Draft MISP taxonomy format February 2024
"predicate": "source-type"
},
{
"predicate": "lifetime",
"entry": [
{
"value": "perpetual",
"expanded": "Perpetual",
"description": "Information available publicly on long-term"
},
{
"value": "ephemeral",
"expanded": "Ephemeral",
"description": "Information available publicly on short-term"
}
]
},
{
"predicate": "certainty",
"entry": [
{
"numerical_value": 100,
"value": "100",
"expanded": "100% Certainty",
"description": "100% Certainty"
},
{
"numerical_value": 93,
"value": "93",
"expanded": "93% Almost certain",
"description": "93% Almost certain"
},
{
"numerical_value": 75,
"value": "75",
"expanded": "75% Probable",
"description": "75% Probable"
},
{
"numerical_value": 50,
"value": "50",
"expanded": "50% Chances about even",
"description": "50% Chances about even"
},
{
"numerical_value": 30,
"value": "30",
"expanded": "30% Probably not",
Dulaunoy & Iklody Expires 24 August 2024 [Page 10]
Internet-Draft MISP taxonomy format February 2024
"description": "30% Probably not"
},
{
"numerical_value": 7,
"value": "7",
"expanded": "7% Almost certainly not",
"description": "7% Almost certainly not"
},
{
"numerical_value": 0,
"value": "0",
"expanded": "0% Impossibility",
"description": "0% Impossibility"
}
]
}
],
"namespace": "osint",
"description": "Open Source Intelligence - Classification",
"version": 3,
"predicates": [
{
"value": "source-type",
"expanded": "Source Type"
},
{
"value": "lifetime",
"expanded": "Lifetime of the information
as Open Source Intelligence"
},
{
"value": "certainty",
"expanded": "Certainty of the elements mentioned
in this Open Source Intelligence"
}
]
}
4.3. Available taxonomies in the public directory
The public directory of MISP taxonomies [MISP-T] contains a variety
of taxonomy in various fields such as:
CERT-XLM: CERT-XLM Security Incident Classification.
DFRLab-dichotomies-of-disinformation: DFRLab Dichotomies of
Disinformation.
DML: The Detection Maturity Level (DML) model is a capability
Dulaunoy & Iklody Expires 24 August 2024 [Page 11]
Internet-Draft MISP taxonomy format February 2024
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.
GrayZone: Gray Zone of Active defense includes all elements which
lay between reactive defense elements and offensive operations.
It does fill the gray spot between them. Taxo may be used for
active defense planning or modeling.
PAP: The Permissible Actions Protocol - or short: PAP - was designed
to indicate how the received information can be used.
access-method: The access method used to remotely access a system.
accessnow: Access Now classification to classify an issue (such as
security, human rights, youth rights).
action-taken: Action taken in the case of a security incident (CSIRT
perspective).
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.
adversary: An overview and description of the adversary
infrastructure
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)
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.
approved-category-of-action: A pre-approved category of action for
indicators being shared with partners (MIMIC).
artificial-satellites: This taxonomy was designed to describe
artificial satellites
aviation: A taxonomy describing security threats or incidents
against the aviation sector.
binary-class: Custom taxonomy for types of binary file.
cccs: Internal taxonomy for CCCS.
circl: CIRCL Taxonomy - Schemes of Classification in Incident
Response and Detection.
cnsd: La presente taxonomia es la primera versión disponible
para el Centro Nacional de Seguridad Digital del Perú.
coa: Course of action taken within organization to discover, detect,
deny, disrupt, degrade, deceive and/or destroy an attack.
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.
Dulaunoy & Iklody Expires 24 August 2024 [Page 12]
Internet-Draft MISP taxonomy format February 2024
common-taxonomy: Common Taxonomy for Law enforcement and CSIRTs
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.
course-of-action: A Course Of Action analysis considers six
potential courses of action for the development of a cyber
security capability.
crowdsec: Crowdsec IP address classifications and behaviors
taxonomy.
cryptocurrency-threat: Threats targetting cryptocurrency, based on
CipherTrace report.
csirt-americas: Taxonomía CSIRT Américas.
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.
cssa: The CSSA agreed sharing taxonomy.
cti: Cyber Threat Intelligence cycle to control workflow state of
your process.
current-event: Current events - Schemes of Classification in
Incident Response and Detection
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
(https://www.dni.gov/index.php/cyber-threat-framework)
cycat: Taxonomy used by CyCAT, the Universal Cybersecurity Resource
Catalogue, to categorize the namespaces it supports and uses.
cytomic-orion: Taxonomy to describe desired actions for Cytomic
Orion
dark-web: Criminal motivation and content detection the dark web: A
categorisation model for law enforcement. ref: Janis Dalins,
Campbell Wilson, Mark Carman. Taxonomy updated by MISP Project
and extended by the JRC (Joint Research Centre) of the European
Commission.
Dulaunoy & Iklody Expires 24 August 2024 [Page 13]
Internet-Draft MISP taxonomy format February 2024
data-classification: Data classification for data potentially at
risk of exfiltration based on table 2.1 of Solving Cyber Risk
book.
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.
ddos: Distributed Denial of Service - or short: DDoS - taxonomy
supports the description of Denial of Service attacks and
especially the types they belong too.
de-vs: German (DE) Government classification markings (VS).
death-possibilities: Taxonomy of Death Possibilities
deception: Deception is an important component of information
operations, valuable for both offense and defense.
dga: A taxonomy to describe domain-generation algorithms often
called DGA. Ref: A Comprehensive Measurement Study of Domain
Generating Malware Daniel Plohmann and others.
dhs-ciip-sectors: DHS critical sectors as in https://www.dhs.gov/
critical-infrastructure-sectors (https://www.dhs.gov/critical-
infrastructure-sectors)
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.
diamond-model-for-influence-operations: The diamond model for
influence operations analysis is a framework that leads analysts
and researchers toward a comprehensive understanding of a malign
influence campaign by addressing the socio-political, technical,
and psychological aspects of the campaign. The diamond model for
influence operations analysis consists of 5 components: 4 corners
and a core element. The 4 corners are divided into 2 axes:
influencer and audience on the socio-political axis, capabilities
and infrastructure on the technical axis. Narrative makes up the
core of the diamond.
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
domain-abuse: Domain Name Abuse - taxonomy to tag domain names used
for cybercrime.
doping-substances: This taxonomy aims to list doping substances
drugs: A taxonomy based on the superclass and class of drugs. Based
on https://www.drugbank.ca/releases/latest
(https://www.drugbank.ca/releases/latest)
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).
Dulaunoy & Iklody Expires 24 August 2024 [Page 14]
Internet-Draft MISP taxonomy format February 2024
ecsirt: Incident Classification by the ecsirt.net version mkVI of 31
March 2015 enriched with IntelMQ taxonomy-type mapping.
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.
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
eu-marketop-and-publicadmin: Market operators and public
administrations that must comply to some notifications
requirements under EU NIS directive
eu-nis-sector-and-subsectors: Sectors, subsectors, and digital
services as identified by the NIS Directive
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.
europol-event: This taxonomy was designed to describe the type of
events
europol-incident: This taxonomy was designed to describe the type of
incidents by class.
event-assessment: A series of assessment predicates describing the
event assessment performed to make judgement(s) under a certain
level of uncertainty.
event-classification: Classification of events as seen in tools such
as RT/IR, MISP and other
exercise: Exercise is a taxonomy to describe if the information is
part of one or more cyber or crisis exercise.
extended-event: Reasons why an event has been extended. This
taxonomy must be used on the extended event. The competitive
analysis aspect is from Psychology of Intelligence Analysis by
Richard J. Heuer, Jr. ref:http://www.foo.be/docs/intelligence/
PsychofIntelNew.pdf (http://www.foo.be/docs/intelligence/
PsychofIntelNew.pdf)
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.
false-positive: This taxonomy aims to ballpark the expected amount
of false positives.
Dulaunoy & Iklody Expires 24 August 2024 [Page 15]
Internet-Draft MISP taxonomy format February 2024
file-type: List of known file types.
financial: Financial taxonomy to describe financial services,
infrastructure and financial scope.
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).
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.
fr-classif: French gov information classification system
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)
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'.
gea-nz-entities: Information relating to instances of entities or
things.
gea-nz-motivators: Information relating to authority or governance.
gsma-attack-category: Taxonomy used by GSMA for their information
sharing program with telco describing the attack categories
gsma-fraud: Taxonomy used by GSMA for their information sharing
program with telco describing the various aspects of fraud
gsma-network-technology: Taxonomy used by GSMA for their information
sharing program with telco describing the types of infrastructure.
WiP
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
(http://www.mcs.vuw.ac.nz/comp/Publications/archive/CS-TR-06/CS-
TR-06-12.pdf)
ics: FIRST.ORG CTI SIG - MISP Proposal for ICS/OT Threat Attribution
(IOC) Project
iep: Forum of Incident Response and Security Teams (FIRST)
Information Exchange Policy (IEP) framework
iep2-policy: Forum of Incident Response and Security Teams (FIRST)
Dulaunoy & Iklody Expires 24 August 2024 [Page 16]
Internet-Draft MISP taxonomy format February 2024
Information Exchange Policy (IEP) v2.0 Policy
iep2-reference: Forum of Incident Response and Security Teams
(FIRST) Information Exchange Policy (IEP) v2.0 Reference
ifx-vetting: The IFX taxonomy is used to categorise information
(MISP events and attributes) to aid in the intelligence vetting
process
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%20Securi
ty%20Incident%20Management%5d.pdf#page=9 (https://www.nasa.gov/
pdf/589502main_ITS-HBK-2810.09-02%20%5bNASA%20Information%20Securi
ty%20Incident%20Management%5d.pdf#page=9)
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.
information-origin: Taxonomy for tagging information by its origin:
human-generated or AI-generated.
information-security-data-source: Taxonomy to classify the
information security data sources.
information-security-indicators: A full set of operational
indicators for organizations to use to benchmark their security
posture.
interactive-cyber-training-audience: Describes the target of cyber
training and education.
interactive-cyber-training-technical-setup: The technical setup
consists of environment structure, deployment, and orchestration.
interactive-cyber-training-training-environment: The training
environment details the environment around the training,
consisting of training type and scenario.
interactive-cyber-training-training-setup: The training setup
further describes the training itself with the scoring, roles, the
training mode as well as the customization level.
interception-method: The interception method used to intercept
traffic.
ioc: An IOC classification to facilitate automation of malicious and
non malicious artifacts
iot: Internet of Things taxonomy, based on IOT UK report
https://iotuk.org.uk/wp-content/uploads/2017/01/IOT-Taxonomy-
Report.pdf (https://iotuk.org.uk/wp-content/uploads/2017/01/IOT-
Taxonomy-Report.pdf)
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.
maec-delivery-vectors: Vectors used to deliver malware based on MAEC
5.0
Dulaunoy & Iklody Expires 24 August 2024 [Page 17]
Internet-Draft MISP taxonomy format February 2024
maec-malware-behavior: Malware behaviours based on MAEC 5.0
maec-malware-capabilities: Malware Capabilities based on MAEC 5.0
maec-malware-obfuscation-methods: Obfuscation methods used by
malware based on MAEC 5.0
malware_classification: Classification based on different
categories. Based on https://www.sans.org/reading-
room/whitepapers/incident/malware-101-viruses-32848
(https://www.sans.org/reading-room/whitepapers/incident/malware-
101-viruses-32848)
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
misp: MISP taxonomy to infer with MISP behavior or operation.
misp-workflow: MISP workflow taxonomy to support result of workflow
execution.
monarc-threat: MONARC Threats Taxonomy
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/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/
glossary.aspx),
https://www.microsoft.com/security/portal/mmpc/shared/
objectivecriteria.aspx
(https://www.microsoft.com/security/portal/mmpc/shared/
objectivecriteria.aspx), and http://www.caro.org/definitions/
index.html (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
(https://www.microsoft.com/security/sir/archive/default.aspx) and
https://www.microsoft.com/en-us/security/portal/threat/
threats.aspx (https://www.microsoft.com/en-
us/security/portal/threat/threats.aspx). Note that SIRs do NOT
include all Microsoft malware families.
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/en-