Search results

Feedback on Threat Actor Naming Standard

Status: Open.

#54 In MISP/misp-rfc;

· Johnnyd4251 opened on Jan 4, 2025

Feedback on the Threat Actor Naming Standard

Status: Open.

#53 In MISP/misp-rfc;

· colin-sophos opened on Jan 2, 2025

Add a description in the core format about hashes.csv for the manifest part

enhancement

Status: Open.

#38 In MISP/misp-rfc;

· adulau opened on Nov 17, 2020

update misp-core-format info and raw.md.txt to available draft 08

Status: Open.

#33 In MISP/misp-rfc;

· bernhardreiter opened on Dec 19, 2019

Add a section about current implementation (following BP from RFC 7942)

enhancement

Status: Open.

#26 In MISP/misp-rfc;

· adulau opened on Jun 23, 2019

<code>type</code> codes appear to be duplicated for Attribute and ShadowAttribute; should probably refer to a single appendix table

enhancement

Status: Open.

#25 In MISP/misp-rfc;

· acruise opened on May 16, 2019

Several of the attribute attributes refer to their context as "event", maybe C&amp;P error?

Status: Open.

#24 In MISP/misp-rfc;

· acruise opened on May 16, 2019

warning-list format Internet-Draft

Status: Open.

#7 In MISP/misp-rfc;

· adulau opened on Dec 7, 2017

Sample UUID and example orgs should be added

Status: Open.

#5 In MISP/misp-rfc;

· adulau opened on Apr 7, 2017

Timestamps should all be in the same format

valid

Status: Open.

#4 In MISP/misp-rfc;

· rhaist opened on Feb 13, 2017

Fields containing only numbers should be JSON integers

Status: Open.

#3 In MISP/misp-rfc;

· rhaist opened on Feb 13, 2017