mirror of https://github.com/MISP/misp-rfc
				
				
				
			
						commit
						32169a363b
					
				| 
						 | 
				
			
			@ -96,7 +96,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 such as the threat actor MISP galaxy [@!MISP-G]. 
 | 
			
		||||
A reference registry of threat actors is **RECOMMENDED** to ensure consistency of names across different parties such as the threat actor MISP galaxy [@!MISP-G].
 | 
			
		||||
 | 
			
		||||
# Examples
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
| 
						 | 
				
			
			@ -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 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>
 | 
			
		||||
<p id="section-2.6-1">A reference registry of threat actors is <span class="bcp14">RECOMMENDED</span> to ensure consistency of names across 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>
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
| 
						 | 
				
			
			@ -181,7 +181,7 @@ 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 such as the threat
 | 
			
		||||
   consistency of names across different parties such as the threat
 | 
			
		||||
   actor MISP galaxy [MISP-G].
 | 
			
		||||
 | 
			
		||||
3.  Examples
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
| 
						 | 
				
			
			@ -73,7 +73,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 such as the threat actor MISP galaxy <xref target="MISP-G"></xref>.</t>
 | 
			
		||||
<t>A reference registry of threat actors is <bcp14>RECOMMENDED</bcp14> to ensure consistency of names across different parties such as the threat actor MISP galaxy <xref target="MISP-G"></xref>.</t>
 | 
			
		||||
</section>
 | 
			
		||||
</section>
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
		Reference in New Issue