@ -55,17 +55,23 @@ The key words "**MUST**", "**MUST NOT**", "**REQUIRED**", "**SHALL**", "**SHALL
"**SHOULD**", "**SHOULD NOT**", "**RECOMMENDED**", "**MAY**", and "**OPTIONAL**" in this
document are to be interpreted as described in RFC 2119 [@!RFC2119].
# Reusing threat actor naming
# Recommendations
## Reusing threat actor naming
Before creating a new threat actor name, you **MUST** consider a review of existing threat actor names from databases such as the threat actor
MISP galaxy [@!MISP-G]. Proliferation of threat actor names is a significant challenge for the day-to-day analyst work. If your threat actor defined an existing threat actor, you **MUST**
reuse an existing threat actor name. If there is no specific threat actor name, you **SHALL** create a new threat actor following the best
<pid="rfc.section.1.1.p.1">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 <ahref="#RFC2119"class="xref">[RFC2119]</a>.</p>
<h1id="rfc.section.2">
<ahref="#rfc.section.2">2.</a><ahref="#reusing-threat-actor-naming"id="reusing-threat-actor-naming">Reusing threat actor naming</a>
<ahref="#rfc.section.2.1">2.1.</a><ahref="#reusing-threat-actor-naming"id="reusing-threat-actor-naming">Reusing threat actor naming</a>
</h1>
<pid="rfc.section.2.1.p.1">Before creating a new threat actor name, you MUST consider a review of existing threat actor names from databases such as the threat actor MISP galaxy <ahref="#MISP-G"class="xref">[MISP-G]</a>. Proliferation of threat actor names is a significant challenge for the day-to-day analyst work. If your threat actor defined an existing threat actor, you MUST reuse an existing threat actor name. If there is no specific threat actor name, you SHALL create a new threat actor following the best practices defined in this document.</p>
<h1id="rfc.section.2.2">
<ahref="#rfc.section.2.2">2.2.</a><ahref="#don-t-confuse-actor-naming-with-malware-naming"id="don-t-confuse-actor-naming-with-malware-naming">Don't confuse actor naming with malware naming</a>
<pid="rfc.section.2.p.1">Before creating a new threat actor name, you MUST consider a review of existing threat actor names from databases such as the threat actor MISP galaxy <ahref="#MISP-G"class="xref">[MISP-G]</a>. Proliferation of threat actor names is a significant challenge for the day-to-day analyst work. If your threat actor defined an existing threat actor, you MUST reuse an existing threat actor name. If there is no specific threat actor name, you SHALL create a new threat actor following the best practices defined in this document.</p>
<pid="rfc.section.4.p.1">Naming a threat actor could include specific sensitive reference to a case or an incident. Before releasing the naming, the creator MUST review the name to ensure no sensitive information is included in the threat actor name.</p>
<pid="rfc.section.6.p.1">Naming a threat actor could include specific sensitive reference to a case or an incident. Before releasing the naming, the creator MUST review the name to ensure no sensitive information is included in the threat actor name.</p>
<sectionanchor="reusing-threat-actor-naming"title="Reusing threat actor naming">
<t>Before creating a new threat actor name, you MUST consider a review of existing threat actor names from databases such as the threat actor
MISP galaxy <xreftarget="MISP-G"></xref>. Proliferation of threat actor names is a significant challenge for the day-to-day analyst work. If your threat actor defined an existing threat actor, you MUST
@ -45,12 +47,19 @@ reuse an existing threat actor name. If there is no specific threat actor name,
practices defined in this document.</t>
</section>
<sectionanchor="don-t-confuse-actor-naming-with-malware-naming"title="Don't confuse actor naming with malware naming">
