MISP
/
misp-rfc
mirror of https://github.com/MISP/misp-rfc
2
0
Fork 0
Code Issues Releases Wiki Activity

chg: [threat-actor-naming] directory reference added 

TODO: one of the online directory
pull/50/head
Alexandre Dulaunoy 2024-12-21 11:39:28 +01:00
parent 2a9ea5fdf6
commit 4ee3a6ae9c
No known key found for this signature in database
GPG Key ID: 09E2CD4944E6CBCD
4 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
threat-actor-naming/raw.md
View File

@ -101,7 +101,7 @@ The name of the threat actor **MUST NOT** be based on the tools, techniques, or
## Directory
A reference registry of threat actors is **RECOMMENDED** to ensure consistency of names accross different parties.
A reference registry of threat actors is **RECOMMENDED** to ensure consistency of names accross different parties such as the threat actor MISP galaxy [@!MISP-G].
# Examples
@ -123,7 +123,7 @@ Naming a threat actor could include sensitive references to a case or an inciden
# Acknowledgements
The authors wish to thank all contributors who provided feedback via Twitter.
The authors wish to thank all contributors who provided feedback through the now-defunct Twitter and other new social networks.
# References

4
threat-actor-naming/threat-actor-naming.html
View File

@ -1452,7 +1452,7 @@ document are to be interpreted as described in RFC 2119 <span>[<a href="#RFC2119
<h3 id="name-directory">
<a href="#section-2.6" class="section-number selfRef">2.6. </a><a href="#name-directory" class="section-name selfRef">Directory</a>
</h3>
<p id="section-2.6-1">A reference registry of threat actors is <span class="bcp14">RECOMMENDED</span> to ensure consistency of names accross different parties.<a href="#section-2.6-1" class="pilcrow"></a></p>
<p id="section-2.6-1">A reference registry of threat actors is <span class="bcp14">RECOMMENDED</span> to ensure consistency of names accross different parties such as the threat actor MISP galaxy <span>[<a href="#MISP-G" class="cite xref">MISP-G</a>]</span>.<a href="#section-2.6-1" class="pilcrow"></a></p>
</section>
</div>
</section>
@ -1495,7 +1495,7 @@ document are to be interpreted as described in RFC 2119 <span>[<a href="#RFC2119
<h2 id="name-acknowledgements">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
</h2>
<p id="section-5-1">The authors wish to thank all contributors who provided feedback via Twitter.<a href="#section-5-1" class="pilcrow"></a></p>
<p id="section-5-1">The authors wish to thank all contributors who provided feedback through the now-defunct Twitter and other new social networks.<a href="#section-5-1" class="pilcrow"></a></p>
</section>
</div>
<div id="references">

8
threat-actor-naming/threat-actor-naming.txt
View File

@ -181,7 +181,8 @@ Internet-Draft Recommendations on Naming Threat Actors December 2024
2.6. Directory
A reference registry of threat actors is RECOMMENDED to ensure
consistency of names accross different parties.
consistency of names accross different parties such as the threat
actor MISP galaxy [MISP-G].
3. Examples
@ -208,8 +209,8 @@ Internet-Draft Recommendations on Naming Threat Actors December 2024
5. Acknowledgements
The authors wish to thank all contributors who provided feedback via
Twitter.
The authors wish to thank all contributors who provided feedback
through the now-defunct Twitter and other new social networks.
6. References
@ -220,7 +221,6 @@ Internet-Draft Recommendations on Naming Threat Actors December 2024
Dulaunoy & Bourmeau Expires 24 June 2025 [Page 4]
Internet-Draft Recommendations on Naming Threat Actors December 2024

4
threat-actor-naming/threat-actor-naming.xml
View File

@ -76,7 +76,7 @@ document are to be interpreted as described in RFC 2119 <xref target="RFC2119"><
</section>
<section anchor="directory"><name>Directory</name>
<t>A reference registry of threat actors is <bcp14>RECOMMENDED</bcp14> to ensure consistency of names accross different parties.</t>
<t>A reference registry of threat actors is <bcp14>RECOMMENDED</bcp14> to ensure consistency of names accross different parties such as the threat actor MISP galaxy <xref target="MISP-G"></xref>.</t>
</section>
</section>
@ -102,7 +102,7 @@ document are to be interpreted as described in RFC 2119 <xref target="RFC2119"><
</section>
<section anchor="acknowledgements"><name>Acknowledgements</name>
<t>The authors wish to thank all contributors who provided feedback via Twitter.</t>
<t>The authors wish to thank all contributors who provided feedback through the now-defunct Twitter and other new social networks.</t>
</section>
<section anchor="references"><name>References</name>