-
Notifications
You must be signed in to change notification settings - Fork 18
/
raw.md.txt
executable file
·3696 lines (2571 loc) · 113 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: 30 December 2024 28 June 2024
MISP core format
draft-17
Abstract
This document describes the MISP core format used to exchange
indicators and threat information between MISP (Open Source Threat
Intelligence Sharing Platform formerly known as Malware Information
Sharing Platform) instances. The JSON format includes the overall
structure along with the semantic associated for each respective key.
The format is described to support other implementations which reuse
the format and ensuring an interoperability with existing MISP
[MISP-P] software and other Threat Intelligence Platforms.
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 30 December 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 30 December 2024 [Page 1]
Internet-Draft MISP core format June 2024
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions and Terminology . . . . . . . . . . . . . . . 3
2. Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Event . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2.1. Event Attributes . . . . . . . . . . . . . . . . . . 4
2.2.2. Event Objects . . . . . . . . . . . . . . . . . . . . 7
2.3. Attribute . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3.1. Sample Attribute Object . . . . . . . . . . . . . . . 8
2.3.2. Attribute Attributes . . . . . . . . . . . . . . . . 9
2.4. ShadowAttribute . . . . . . . . . . . . . . . . . . . . . 15
2.4.1. Sample Attribute Object . . . . . . . . . . . . . . . 16
2.4.2. ShadowAttribute Attributes . . . . . . . . . . . . . 16
2.4.3. ShadowAttribute Objects . . . . . . . . . . . . . . . 22
2.5. Object . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.5.1. Sample Object . . . . . . . . . . . . . . . . . . . . 23
2.5.2. Object Attributes . . . . . . . . . . . . . . . . . . 24
2.6. Object References . . . . . . . . . . . . . . . . . . . . 28
2.6.1. Sample ObjectReference object . . . . . . . . . . . . 28
2.6.2. ObjectReference Attributes . . . . . . . . . . . . . 28
2.7. EventReport . . . . . . . . . . . . . . . . . . . . . . . 30
2.7.1. id . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.7.2. UUID . . . . . . . . . . . . . . . . . . . . . . . . 31
2.7.3. event_id . . . . . . . . . . . . . . . . . . . . . . 31
2.7.4. name . . . . . . . . . . . . . . . . . . . . . . . . 31
2.7.5. content . . . . . . . . . . . . . . . . . . . . . . . 31
2.7.6. distribution . . . . . . . . . . . . . . . . . . . . 31
2.7.7. sharing_group_id . . . . . . . . . . . . . . . . . . 32
2.7.8. timestamp . . . . . . . . . . . . . . . . . . . . . . 32
2.7.9. deleted . . . . . . . . . . . . . . . . . . . . . . . 32
2.8. Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.8.1. Sample Tag . . . . . . . . . . . . . . . . . . . . . 33
2.9. Sighting . . . . . . . . . . . . . . . . . . . . . . . . 33
2.9.1. Sample Sighting . . . . . . . . . . . . . . . . . . . 34
2.10. Galaxy . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.10.1. Sample Galaxy . . . . . . . . . . . . . . . . . . . 35
2.11. Analyst Data . . . . . . . . . . . . . . . . . . . . . . 37
2.11.1. Opinion . . . . . . . . . . . . . . . . . . . . . . 37
2.11.2. Note . . . . . . . . . . . . . . . . . . . . . . . . 40
2.11.3. Relationship . . . . . . . . . . . . . . . . . . . . 44
3. JSON Schema . . . . . . . . . . . . . . . . . . . . . . . . . 48
4. Manifest . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.1.1. Sample Manifest . . . . . . . . . . . . . . . . . . . 63
5. Implementation . . . . . . . . . . . . . . . . . . . . . . . 64
6. Security Considerations . . . . . . . . . . . . . . . . . . . 64
Dulaunoy & Iklody Expires 30 December 2024 [Page 2]
Internet-Draft MISP core format June 2024
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 65
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 65
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.1. Normative References . . . . . . . . . . . . . . . . . . 65
9.2. Informative References . . . . . . . . . . . . . . . . . 65
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 66
1. Introduction
Sharing threat information became a fundamental requirements in the
Internet, security and intelligence community at large. Threat
information can include indicators of compromise, malicious file
indicators, financial fraud indicators or even detailed information
about a threat actor. MISP [MISP-P] started as an open source
project in late 2011 and the MISP format started to be widely used as
an exchange format within the community in the past years. The aim
of this document is to describe the specification and the MISP core
format.
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
2.1. Overview
The MISP core format is in the JSON [RFC8259] format. In MISP, an
event is composed of a single JSON object.
A capitalized key (like Event, Org) represent a data model and a non-
capitalised key is just an attribute. This nomenclature can support
an implementation to represent the MISP format in another data
structure.
2.2. Event
An event is a simple meta structure scheme where attributes and meta-
data are embedded to compose a coherent set of indicators. An event
can be composed from an incident, a security analysis report or a
specific threat actor analysis. The meaning of an event only depends
of the information embedded in the event.
Dulaunoy & Iklody Expires 30 December 2024 [Page 3]
Internet-Draft MISP core format June 2024
2.2.1. Event Attributes
2.2.1.1. uuid
uuid represents the Universally Unique IDentifier (UUID) [RFC4122] of
the event. The uuid MUST be preserved for any updates or transfer of
the same event. UUID version 4 is RECOMMENDED when assigning it to a
new event.
uuid is represented as a JSON string. uuid MUST be present.
2.2.1.2. id
id represents the human-readable identifier associated to the event
for a specific MISP instance. A human-readable identifier MUST be
represented as an unsigned integer.
id is represented as a JSON string. id SHALL be present.
2.2.1.3. published
published represents the event publication state. If the event was
published, the published value MUST be true. In any other
publication state, the published value MUST be false.
published is represented as a JSON boolean. published MUST be
present.
2.2.1.4. info
info represents the information field of the event. info is a free-
text value to provide a human-readable summary of the event. info
SHOULD NOT be bigger than 256 characters and SHOULD NOT include new-
lines.
info is represented as a JSON string. info MUST be present.
2.2.1.5. threat_level_id
threat_level_id represents the threat level.
4: Undefined
3: Low
2: Medium
1: High
If a higher granularity is required, a MISP taxonomy applied as a Tag
SHOULD be preferred.
Dulaunoy & Iklody Expires 30 December 2024 [Page 4]
Internet-Draft MISP core format June 2024
threat_level_id is represented as a JSON string. threat_level_id
SHALL be present.
2.2.1.6. analysis
analysis represents the analysis level.
0: Initial
1: Ongoing
2: Complete
If a higher granularity is required, a MISP taxonomy applied as a Tag
SHOULD be preferred.
analysis is represented as a JSON string. analysis SHALL be present.
2.2.1.7. date
date represents a reference date to the event in ISO 8601 format
(date only: YYYY-MM-DD). This date corresponds to the date the event
occurred, which may be in the past.
date is represented as a JSON string. date MUST be present.
2.2.1.8. timestamp
timestamp represents a reference time when the event, or one of the
attributes within the event was created, or last updated/edited on
the instance. timestamp is expressed in seconds (decimal) since 1st
of January 1970 (Unix timestamp). The time zone MUST be UTC.
timestamp is represented as a JSON string. timestamp MUST be present.
2.2.1.9. publish_timestamp
publish_timestamp represents a reference time when the event was
published on the instance. published_timestamp is expressed in
seconds (decimal) since 1st of January 1970 (Unix timestamp). At
each publication of an event, publish_timestamp MUST be updated. The
time zone MUST be UTC. If the published_timestamp is present and the
published flag is set to false, the publish_timestamp represents the
previous publication timestamp. If the event was never published,
the published_timestamp MUST be set to 0.
publish_timestamp is represented as a JSON string. publish_timestamp
MUST be present.
Dulaunoy & Iklody Expires 30 December 2024 [Page 5]
Internet-Draft MISP core format June 2024
2.2.1.10. org_id
org_id represents a human-readable identifier referencing an Org
object of the organisation which generated the event. A human-
readable identifier MUST be represented as an unsigned integer.
The org_id MUST be updated when the event is generated by a new
instance.
org_id is represented as a JSON string. org_id MUST be present.
2.2.1.11. orgc_id
orgc_id represents a human-readable identifier referencing an Orgc
object of the organisation which created the event.
The orgc_id and Org object MUST be preserved for any updates or
transfer of the same event.
orgc_id is represented as a JSON string. orgc_id MUST be present.
2.2.1.12. attribute_count
attribute_count represents the number of attributes in the event.
attribute_count is expressed in decimal.
attribute_count is represented as a JSON string. attribute_count
SHALL be present.
2.2.1.13. distribution
distribution represents the basic distribution rules of the event.
The system must adhere to the distribution setting for access control
and for dissemination of the event.
distribution is represented by a JSON string. distribution MUST be
present and be one of the following options:
0 Your Organisation Only
1 This Community Only
2 Connected Communities
3 All Communities
4 Sharing Group
Dulaunoy & Iklody Expires 30 December 2024 [Page 6]
Internet-Draft MISP core format June 2024
2.2.1.14. sharing_group_id
sharing_group_id represents a human-readable identifier referencing a
Sharing Group object that defines the distribution of the event, if
distribution level "4" is set. A human-readable identifier MUST be
represented as an unsigned integer.
sharing_group_id is represented by a JSON string and SHOULD be
present. If a distribution level other than "4" is chosen the
sharing_group_id MUST be set to "0".
2.2.1.15. extends_uuid
extends_uuid represents which event is extended by this event. The
extends_uuid is described as a Universally Unique IDentifier (UUID)
[RFC4122] with the UUID of the extended event.
extends_uuid is represented as a JSON string. extends_uuid SHOULD be
present.
2.2.2. Event Objects
2.2.2.1. Org
An Org object is composed of an uuid, name and id.
The uuid represents the Universally Unique IDentifier (UUID)
[RFC4122] of the organisation. The organisation UUID is globally
assigned to an organisation and SHALL be kept overtime.
The name is a readable description of the organisation and SHOULD be
present. The id is a human-readable identifier generated by the
instance and used as reference in the event. A human-readable
identifier MUST be represented as an unsigned integer.
uuid, name and id are represented as a JSON string. uuid, name and id
MUST be present.
2.2.2.1.1. Sample Org Object
"Org": {
"id": "2",
"name": "CIRCL",
"uuid": "55f6ea5e-2c60-40e5-964f-47a8950d210f"
}
Dulaunoy & Iklody Expires 30 December 2024 [Page 7]
Internet-Draft MISP core format June 2024
2.2.2.2. Orgc
An Orgc object is composed of an uuid, name and id.
The uuid MUST be preserved for any updates or transfer of the same
event. UUID version 4 is RECOMMENDED when assigning it to a new
event. The organisation UUID is globally assigned to an organisation
and SHALL be kept overtime.
The name is a readable description of the organisation and SHOULD be
present. The id is a human-readable identifier generated by the
instance and used as reference in the event. A human-readable
identifier MUST be represented as an unsigned integer.
uuid, name and id are represented as a JSON string. uuid, name and id
MUST be present.
2.3. Attribute
Attributes are used to describe the indicators and contextual data of
an event. The main information contained in an attribute is made up
of a category-type-value triplet, where the category and type give
meaning and context to the value. Through the various category-type
combinations a wide range of information can be conveyed.
A MISP document MUST at least includes category-type-value triplet
described in section "Attribute Attributes".
2.3.1. Sample Attribute Object
Dulaunoy & Iklody Expires 30 December 2024 [Page 8]
Internet-Draft MISP core format June 2024
"Attribute": {
"id": "346056",
"type": "comment",
"category": "Other",
"to_ids": false,
"uuid": "57f4f6d9-cd20-458b-84fd-109ec0a83869",
"event_id": "3357",
"distribution": "5",
"timestamp": "1475679332",
"comment": "",
"sharing_group_id": "0",
"deleted": false,
"value": "Hello world",
"SharingGroup": [],
"ShadowAttribute": [],
"RelatedAttribute": [],
"first_seen": "2019-06-02T22:14:28.711954+00:00",
"last_seen": null
}
2.3.2. Attribute Attributes
2.3.2.1. uuid
uuid represents the Universally Unique IDentifier (UUID) [RFC4122] of
the event. The uuid MUST be preserved for any updates or transfer of
the same event. UUID version 4 is RECOMMENDED when assigning it to a
new event.
uuid is represented as a JSON string. uuid MUST be present.
2.3.2.2. id
id represents the human-readable identifier associated to the event
for a specific MISP instance. A human-readable identifier MUST be
represented as an unsigned integer.
id is represented as a JSON string. id SHALL be present.
2.3.2.3. type
type represents the means through which an attribute tries to
describe the intent of the attribute creator, using a list of pre-
defined attribute types.
type is represented as a JSON string. type MUST be present and it
MUST be a valid selection for the chosen category. The list of valid
category-type combinations is as follows:
Dulaunoy & Iklody Expires 30 December 2024 [Page 9]
Internet-Draft MISP core format June 2024
Antivirus detection link, comment, text, hex, attachment, other,
anonymised
Artifacts dropped md5, sha1, sha224, sha256, sha384, sha512,
sha512/224, sha512/256, sha3-224, sha3-256, sha3-384, sha3-512,
ssdeep, imphash, telfhash, impfuzzy, authentihash, vhash, cdhash,
filename, filename|md5, filename|sha1, filename|sha224,
filename|sha256, filename|sha384, filename|sha512,
filename|sha512/224, filename|sha512/256, filename|sha3-224,
filename|sha3-256, filename|sha3-384, filename|sha3-512,
filename|authentihash, filename|vhash, filename|ssdeep,
filename|tlsh, filename|imphash, filename|impfuzzy,
filename|pehash, regkey, regkey|value, pattern-in-file, pattern-
in-memory, filename-pattern, pdb, stix2-pattern, yara, sigma,
attachment, malware-sample, named pipe, mutex, process-state,
windows-scheduled-task, windows-service-name, windows-service-
displayname, comment, text, hex, x509-fingerprint-sha1, x509-
fingerprint-md5, x509-fingerprint-sha256, other, cookie, gene,
kusto-query, mime-type, anonymised, pgp-public-key, pgp-private-
key
Attribution threat-actor, campaign-name, campaign-id, whois-
registrant-phone, whois-registrant-email, whois-registrant-name,
whois-registrant-org, whois-registrar, whois-creation-date,
comment, text, x509-fingerprint-sha1, x509-fingerprint-md5, x509-
fingerprint-sha256, other, dns-soa-email, anonymised, email
External analysis md5, sha1, sha256, sha3-224, sha3-256, sha3-384,
sha3-512, filename, filename|md5, filename|sha1, filename|sha256,
filename|sha3-224, filename|sha3-256, filename|sha3-384,
filename|sha3-512, ip-src, ip-dst, ip-dst|port, ip-src|port, mac-
address, mac-eui-64, hostname, domain, domain|ip, url, user-agent,
regkey, regkey|value, AS, snort, bro, zeek, pattern-in-file,
pattern-in-traffic, pattern-in-memory, filename-pattern,
vulnerability, cpe, weakness, attachment, malware-sample, link,
comment, text, x509-fingerprint-sha1, x509-fingerprint-md5, x509-
fingerprint-sha256, ja3-fingerprint-md5, jarm-fingerprint, hassh-
md5, hasshserver-md5, github-repository, other, cortex,
anonymised, community-id
Financial fraud btc, dash, xmr, iban, bic, bank-account-nr, aba-rtn,
bin, cc-number, prtn, phone-number, comment, text, other, hex,
anonymised
Internal reference text, link, comment, other, hex, anonymised, git-
commit-id
Network activity ip-src, ip-dst, ip-dst|port, ip-src|port, port,
Dulaunoy & Iklody Expires 30 December 2024 [Page 10]
Internet-Draft MISP core format June 2024
hostname, domain, domain|ip, mac-address, mac-eui-64, email,
email-dst, email-src, eppn, url, uri, user-agent, http-method, AS,
snort, pattern-in-file, filename-pattern, stix2-pattern, pattern-
in-traffic, attachment, comment, text, x509-fingerprint-md5, x509-
fingerprint-sha1, x509-fingerprint-sha256, ja3-fingerprint-md5,
jarm-fingerprint, hassh-md5, hasshserver-md5, other, hex, cookie,
hostname|port, bro, zeek, anonymised, community-id, email-subject,
favicon-mmh3, dkim, dkim-signature, ssh-fingerprint
Other comment, text, other, size-in-bytes, counter, datetime, cpe,
port, float, hex, phone-number, boolean, anonymised, pgp-public-
key, pgp-private-key
Payload delivery md5, sha1, sha224, sha256, sha384, sha512,
sha512/224, sha512/256, sha3-224, sha3-256, sha3-384, sha3-512,
ssdeep, imphash, telfhash, impfuzzy, authentihash, vhash, pehash,
tlsh, cdhash, filename, filename|md5, filename|sha1,
filename|sha224, filename|sha256, filename|sha384,
filename|sha512, filename|sha512/224, filename|sha512/256,
filename|sha3-224, filename|sha3-256, filename|sha3-384,
filename|sha3-512, filename|authentihash, filename|vhash,
filename|ssdeep, filename|tlsh, filename|imphash,
filename|impfuzzy, filename|pehash, mac-address, mac-eui-64, ip-
src, ip-dst, ip-dst|port, ip-src|port, hostname, domain, email,
email-src, email-dst, email-subject, email-attachment, email-body,
url, user-agent, AS, pattern-in-file, pattern-in-traffic,
filename-pattern, stix2-pattern, yara, sigma, mime-type,
attachment, malware-sample, link, malware-type, comment, text,
hex, vulnerability, cpe, weakness, x509-fingerprint-sha1, x509-
fingerprint-md5, x509-fingerprint-sha256, ja3-fingerprint-md5,
jarm-fingerprint, hassh-md5, hasshserver-md5, other,
hostname|port, email-dst-display-name, email-src-display-name,
email-header, email-reply-to, email-x-mailer, email-mime-boundary,
email-thread-index, email-message-id, azure-application-id,
mobile-application-id, chrome-extension-id, whois-registrant-
email, anonymised
Payload installation md5, sha1, sha224, sha256, sha384, sha512,
Dulaunoy & Iklody Expires 30 December 2024 [Page 11]
Internet-Draft MISP core format June 2024
sha512/224, sha512/256, sha3-224, sha3-256, sha3-384, sha3-512,
ssdeep, imphash, telfhash, impfuzzy, authentihash, vhash, pehash,
tlsh, cdhash, filename, filename|md5, filename|sha1,
filename|sha224, filename|sha256, filename|sha384,
filename|sha512, filename|sha512/224, filename|sha512/256,
filename|sha3-224, filename|sha3-256, filename|sha3-384,
filename|sha3-512, filename|authentihash, filename|vhash,
filename|ssdeep, filename|tlsh, filename|imphash,
filename|impfuzzy, filename|pehash, pattern-in-file, pattern-in-
traffic, pattern-in-memory, filename-pattern, stix2-pattern, yara,
sigma, vulnerability, cpe, weakness, attachment, malware-sample,
malware-type, comment, text, hex, x509-fingerprint-sha1, x509-
fingerprint-md5, x509-fingerprint-sha256, azure-application-id,
azure-application-id, mobile-application-id, chrome-extension-id,
other, mime-type, anonymised
Payload type comment, text, other, anonymised
Persistence mechanism filename, regkey, regkey|value, comment, text,
other, hex, anonymised
Person first-name, middle-name, last-name, full-name, date-of-birth,
place-of-birth, gender, passport-number, passport-country,
passport-expiration, redress-number, nationality, visa-number,
issue-date-of-the-visa, primary-residence, country-of-residence,
special-service-request, frequent-flyer-number, travel-details,
payment-details, place-port-of-original-embarkation, place-port-
of-clearance, place-port-of-onward-foreign-destination, passenger-
name-record-locator-number, comment, text, other, phone-number,
identity-card-number, anonymised, email, pgp-public-key, pgp-
private-key
Social network github-username, github-repository, github-
organisation, jabber-id, twitter-id, email, email-src, email-dst,
eppn, comment, text, other, whois-registrant-email, anonymised,
pgp-public-key, pgp-private-key
Support Tool link, text, attachment, comment, other, hex, anonymised
Targeting data target-user, target-email, target-machine, target-
org, target-location, target-external, comment, anonymised
Attributes are based on the usage within their different communities.
Attributes can be extended on a regular basis and this reference
document is updated accordingly.
2.3.2.4. category
category represents the intent of what the attribute is describing as
selected by the attribute creator, using a list of pre-defined
attribute categories.
Dulaunoy & Iklody Expires 30 December 2024 [Page 12]
Internet-Draft MISP core format June 2024
category is represented as a JSON string. category MUST be present
and it MUST be a valid selection for the chosen type. The list of
valid category-type combinations is mentioned above.
2.3.2.5. to_ids
to_ids represents whether the attribute is meant to be actionable.
Actionable defined attributes that can be used in automated processes
as a pattern for detection in Local or Network Intrusion Detection
System, log analysis tools or even filtering mechanisms.
to_ids is represented as a JSON boolean. to_ids MUST be present.
2.3.2.6. event_id
event_id represents a human-readable identifier referencing the Event
object that the attribute belongs to. A human-readable identifier
MUST be represented as an unsigned integer.
The event_id SHOULD be updated when the event is imported to reflect
the newly created event's id on the instance.
event_id is represented as a JSON string. event_id MUST be present.
2.3.2.7. distribution
distribution represents the basic distribution rules of the
attribute. The system must adhere to the distribution setting for
access control and for dissemination of the attribute.
distribution is represented by a JSON string. distribution MUST be
present and be one of the following options:
0 Your Organisation Only
1 This Community Only
2 Connected Communities
3 All Communities
4 Sharing Group
5 Inherit Event
2.3.2.8. timestamp
timestamp represents a reference time when the attribute was created
or last modified. timestamp is expressed in seconds (decimal) since
1st of January 1970 (Unix timestamp). The time zone MUST be UTC.
timestamp is represented as a JSON string. timestamp MUST be present.
Dulaunoy & Iklody Expires 30 December 2024 [Page 13]
Internet-Draft MISP core format June 2024
2.3.2.9. comment
comment is a contextual comment field.
comment is represented by a JSON string. comment MAY be present.
2.3.2.10. sharing_group_id
sharing_group_id represents a human-readable identifier referencing a
Sharing Group object that defines the distribution of the attribute,
if distribution level "4" is set. A human-readable identifier MUST
be represented as an unsigned integer.
sharing_group_id is represented by a JSON string and SHOULD be
present. If a distribution level other than "4" is chosen the
sharing_group_id MUST be set to "0".
2.3.2.11. deleted
deleted represents a setting that allows attributes to be revoked.
Revoked attributes are not actionable and exist merely to inform
other instances of a revocation.
deleted is represented by a JSON boolean. deleted MUST be present.
2.3.2.12. data
data contains the base64 encoded contents of an attachment or a
malware sample. For malware samples, the sample MUST be encrypted
using a password protected zip archive, with the password being
"infected".
data is represented by a JSON string in base64 encoding. data MUST be
set for attributes of type malware-sample and attachment.
2.3.2.13. RelatedAttribute
RelatedAttribute is an array of attributes correlating with the
current attribute. Each element in the array represents an JSON
object which contains an Attribute dictionnary with the external
attributes who correlate. Each Attribute MUST include the id,
org_id, info and a value. Only the correlations found on the local
instance are shown in RelatedAttribute.
RelatedAttribute MAY be present.
Dulaunoy & Iklody Expires 30 December 2024 [Page 14]
Internet-Draft MISP core format June 2024
2.3.2.14. ShadowAttribute
ShadowAttribute is an array of shadow attributes that serve as
proposals by third parties to alter the containing attribute. The
structure of a ShadowAttribute is similar to that of an Attribute,
which can be accepted or discarded by the event creator. If
accepted, the original attribute containing the shadow attribute is
removed and the shadow attribute is converted into an attribute.
Each shadow attribute that references an attribute MUST contain the
containing attribute's ID in the old_id field and the event's ID in
the event_id field.
2.3.2.15. value
value represents the payload of an attribute. The format of the
value is dependent on the type of the attribute.
value is represented by a JSON string. value MUST be present.
2.3.2.16. first_seen
first_seen represents a reference time when the attribute was first
seen. first_seen is expressed as an ISO 8601 datetime up to the
micro-second with time zone support.
first_seen is represented as a JSON string. first_seen MAY be
present.
2.3.2.17. last_seen
last_seen represents a reference time when the attribute was last
seen. last_seen is expressed as an ISO 8601 datetime up to the micro-
second with time zone support.
last_seen is represented as a JSON string. last_seen MAY be present.
2.4. ShadowAttribute
ShadowAttributes are 3rd party created attributes that either propose
to add new information to an event or modify existing information.
They are not meant to be actionable until the event creator accepts
them - at which point they will be converted into attributes or
modify an existing attribute.
They are similar in structure to Attributes but additionally carry a
reference to the creator of the ShadowAttribute as well as a
revocation flag.
Dulaunoy & Iklody Expires 30 December 2024 [Page 15]
Internet-Draft MISP core format June 2024
2.4.1. Sample Attribute Object
"ShadowAttribute": {
"id": "8",
"type": "ip-src",
"category": "Network activity",
"to_ids": false,
"uuid": "57d475f1-da78-4569-89de-1458c0a83869",
"event_uuid": "57d475e6-41c4-41ca-b450-145ec0a83869",
"event_id": "9",
"old_id": "319",
"comment": "",
"org_id": "1",
"proposal_to_delete": false,
"value": "5.5.5.5",
"deleted": false,
"Org": {
"id": "1",
"name": "MISP",
"uuid": "568cce5a-0c80-412b-8fdf-1ffac0a83869"
},
"first_seen": "2019-06-02T22:14:28.711954+00:00",
"last_seen": null
}
2.4.2. ShadowAttribute Attributes
2.4.2.1. uuid
uuid represents the Universally Unique IDentifier (UUID) [RFC4122] of
the event. The uuid MUST be preserved for any updates or transfer of
the same event. UUID version 4 is RECOMMENDED when assigning it to a
new event.
uuid is represented as a JSON string. uuid MUST be present.
2.4.2.2. id
id represents the human-readable identifier associated to the event
for a specific MISP instance. human-readable identifier MUST be
represented as an unsigned integer. id is represented as a JSON
string. id SHALL be present.
2.4.2.3. type
type represents the means through which an attribute tries to
describe the intent of the attribute creator, using a list of pre-
defined attribute types.
Dulaunoy & Iklody Expires 30 December 2024 [Page 16]
Internet-Draft MISP core format June 2024
type is represented as a JSON string. type MUST be present and it
MUST be a valid selection for the chosen category. The list of valid
category-type combinations is as follows:
Antivirus detection link, comment, text, hex, attachment, other,
anonymised
Artifacts dropped md5, sha1, sha224, sha256, sha384, sha512,
sha512/224, sha512/256, sha3-224, sha3-256, sha3-384, sha3-512,
ssdeep, imphash, telfhash, impfuzzy, authentihash, vhash, cdhash,
filename, filename|md5, filename|sha1, filename|sha224,
filename|sha256, filename|sha384, filename|sha512,
filename|sha512/224, filename|sha512/256, filename|sha3-224,
filename|sha3-256, filename|sha3-384, filename|sha3-512,
filename|authentihash, filename|vhash, filename|ssdeep,
filename|tlsh, filename|imphash, filename|impfuzzy,
filename|pehash, regkey, regkey|value, pattern-in-file, pattern-
in-memory, filename-pattern, pdb, stix2-pattern, yara, sigma,
attachment, malware-sample, named pipe, mutex, process-state,
windows-scheduled-task, windows-service-name, windows-service-
displayname, comment, text, hex, x509-fingerprint-sha1, x509-
fingerprint-md5, x509-fingerprint-sha256, other, cookie, gene,
kusto-query, mime-type, anonymised, pgp-public-key, pgp-private-
key
Attribution threat-actor, campaign-name, campaign-id, whois-
registrant-phone, whois-registrant-email, whois-registrant-name,
whois-registrant-org, whois-registrar, whois-creation-date,
comment, text, x509-fingerprint-sha1, x509-fingerprint-md5, x509-
fingerprint-sha256, other, dns-soa-email, anonymised, email
External analysis md5, sha1, sha256, sha3-224, sha3-256, sha3-384,
sha3-512, filename, filename|md5, filename|sha1, filename|sha256,
filename|sha3-224, filename|sha3-256, filename|sha3-384,
filename|sha3-512, ip-src, ip-dst, ip-dst|port, ip-src|port, mac-
address, mac-eui-64, hostname, domain, domain|ip, url, user-agent,
regkey, regkey|value, AS, snort, bro, zeek, pattern-in-file,
pattern-in-traffic, pattern-in-memory, filename-pattern,
vulnerability, cpe, weakness, attachment, malware-sample, link,
comment, text, x509-fingerprint-sha1, x509-fingerprint-md5, x509-
fingerprint-sha256, ja3-fingerprint-md5, jarm-fingerprint, hassh-
md5, hasshserver-md5, github-repository, other, cortex,
anonymised, community-id
Financial fraud btc, dash, xmr, iban, bic, bank-account-nr, aba-rtn,
bin, cc-number, prtn, phone-number, comment, text, other, hex,
anonymised
Internal reference text, link, comment, other, hex, anonymised, git-
commit-id
Network activity ip-src, ip-dst, ip-dst|port, ip-src|port, port,
Dulaunoy & Iklody Expires 30 December 2024 [Page 17]
Internet-Draft MISP core format June 2024
hostname, domain, domain|ip, mac-address, mac-eui-64, email,
email-dst, email-src, eppn, url, uri, user-agent, http-method, AS,
snort, pattern-in-file, filename-pattern, stix2-pattern, pattern-
in-traffic, attachment, comment, text, x509-fingerprint-md5, x509-
fingerprint-sha1, x509-fingerprint-sha256, ja3-fingerprint-md5,
jarm-fingerprint, hassh-md5, hasshserver-md5, other, hex, cookie,
hostname|port, bro, zeek, anonymised, community-id, email-subject,
favicon-mmh3, dkim, dkim-signature, ssh-fingerprint
Other comment, text, other, size-in-bytes, counter, datetime, cpe,
port, float, hex, phone-number, boolean, anonymised, pgp-public-
key, pgp-private-key
Payload delivery md5, sha1, sha224, sha256, sha384, sha512,
sha512/224, sha512/256, sha3-224, sha3-256, sha3-384, sha3-512,
ssdeep, imphash, telfhash, impfuzzy, authentihash, vhash, pehash,
tlsh, cdhash, filename, filename|md5, filename|sha1,
filename|sha224, filename|sha256, filename|sha384,
filename|sha512, filename|sha512/224, filename|sha512/256,
filename|sha3-224, filename|sha3-256, filename|sha3-384,
filename|sha3-512, filename|authentihash, filename|vhash,
filename|ssdeep, filename|tlsh, filename|imphash,
filename|impfuzzy, filename|pehash, mac-address, mac-eui-64, ip-
src, ip-dst, ip-dst|port, ip-src|port, hostname, domain, email,
email-src, email-dst, email-subject, email-attachment, email-body,
url, user-agent, AS, pattern-in-file, pattern-in-traffic,
filename-pattern, stix2-pattern, yara, sigma, mime-type,
attachment, malware-sample, link, malware-type, comment, text,
hex, vulnerability, cpe, weakness, x509-fingerprint-sha1, x509-
fingerprint-md5, x509-fingerprint-sha256, ja3-fingerprint-md5,
jarm-fingerprint, hassh-md5, hasshserver-md5, other,
hostname|port, email-dst-display-name, email-src-display-name,
email-header, email-reply-to, email-x-mailer, email-mime-boundary,
email-thread-index, email-message-id, azure-application-id,
mobile-application-id, chrome-extension-id, whois-registrant-
email, anonymised
Payload installation md5, sha1, sha224, sha256, sha384, sha512,