Skip to content

Commit 2bb608e

Browse files
authored
Merge pull request #2229 from MicrosoftDocs/main
Published main to live, Thursday 10:30 AM PST, 12/19
2 parents 24232c8 + e56824d commit 2bb608e

File tree

3 files changed

+8
-7
lines changed

3 files changed

+8
-7
lines changed

CloudAppSecurityDocs/caac-known-issues.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,7 @@ In the following applications, we encountered scenarios where browsing to a link
7272
- Workplace from Meta
7373
- ServiceNow
7474
- Workday
75+
- Box
7576

7677
### File upload limitations
7778

defender-xdr/microsoft-threat-actor-naming.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -17,12 +17,12 @@ ms.custom:
1717
- cx-ti
1818
ms.topic: conceptual
1919
search.appverid: met150
20-
ms.date: 12/17/2024
20+
ms.date: 12/19/2024
2121
---
2222

2323
# How Microsoft names threat actors
2424

25-
Microsoft shifted to a new naming taxonomy for threat actors aligned with the theme of weather. We intend to bring better clarity to customers and other security researchers with the new taxonomy. We offer a more organized, articulate, and easy way to reference threat actors so that organizations can better prioritize and protect themselves. We also aim to aid security researchers, who are already confronted with an overwhelming amount of threat intelligence data.
25+
Microsoft uses a naming taxonomy for threat actors aligned with the theme of weather. We intend to bring better clarity to customers and other security researchers with this taxonomy. We offer a more organized, articulate, and easy way to reference threat actors so that organizations can better prioritize and protect themselves. We also aim to aid security researchers, who are already confronted with an overwhelming amount of threat intelligence data.
2626

2727
:::image type="content" source="/defender/media/threat-actor-naming/threat-actor-categories.png" alt-text="Nation-state actors based on Microsoft naming" lightbox="/defender/media/threat-actor-naming/threat-actor-categories-lg.png":::
2828

@@ -38,11 +38,11 @@ Microsoft categorizes threat actors into five key groups:
3838

3939
**Groups in development:** a temporary designation given to an unknown, emerging, or developing threat activity. This designation allows Microsoft to track a group as a discrete set of information until we can reach high confidence about the origin or identity of the actor behind the operation. Once criteria are met, a group in development is converted to a named actor or merged into existing names.
4040

41-
In our new taxonomy, a weather event or *family name* represents one of the above categories. For nation-state actors, we assigned a family name to a country/region of origin tied to attribution. For example, Typhoon indicates origin or attribution to China. For other actors, the family name represents a motivation. For example, Tempest indicates financially motivated actors.
41+
In this taxonomy, a weather event or *family name* represents one of the above categories. For nation-state actors, we assigned a family name to a country/region of origin tied to attribution. For example, Typhoon indicates origin or attribution to China. For other actors, the family name represents a motivation. For example, Tempest indicates financially motivated actors.
4242

4343
Threat actors within the same weather family are given an adjective to distinguish actor groups with distinct tactics, techniques, and procedures (TTPs), infrastructure, objectives, or other identified patterns. For groups in development, we use a temporary designation of Storm and a four-digit number where there's a newly discovered, unknown, emerging, or developing cluster of threat activity.
4444

45-
The table that follows shows how the family names map to the threat actors that we track.
45+
The following table shows how the family names map to the threat actors that we track.
4646

4747
|Threat actor category|Type|Family name|
4848
|:---|:---|:---|
@@ -52,7 +52,7 @@ The table that follows shows how the family names map to the threat actors that
5252
|Influence operations|Influence operations|Flood|
5353
|Groups in development|Groups in development|Storm|
5454

55-
The table that follows lists publicly disclosed threat actor names with their origin or threat actor category, previous names, and corresponding names used by other security vendors where available. This page will be updated as more info on other vendors’ names become available.
55+
The following table lists publicly disclosed threat actor names with their origin or threat actor category, previous names, and corresponding names used by other security vendors where available. This page will be updated as more info on other vendors’ names become available.
5656

5757
|Threat actor name|Origin/Threat actor category|Other names|
5858
|:-----|:-----|:---|
@@ -181,7 +181,7 @@ The table that follows lists publicly disclosed threat actor names with their or
181181
|Wisteria Tsunami|India, Private sector offensive actor|DEV-0605|
182182
|Zigzag Hail|Korea|DUBNIUM, Nemim, TEMPLAR, TieOnJoe, Fallout Team, Purple Pygmy, Dark Hotel, Egobot, Tapaoux, PALADIN, Darkhotel|
183183

184-
Read our announcement about the new taxonomy for more information: [https://aka.ms/threatactorsblog](https://aka.ms/threatactorsblog)
184+
Read our announcement about this taxonomy for more information: [https://aka.ms/threatactorsblog](https://aka.ms/threatactorsblog)
185185

186186
## Putting intelligence into the hands of security professionals
187187

unified-secops-platform/overview-deploy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ After you [connect Microsoft Sentinel to Microsoft Defender](/defender-xdr/micro
135135

136136
For more information, see [Microsoft incident creation ](/azure/sentinel/microsoft-365-defender-sentinel-integration?tabs=azure-portal).
137137

138-
### Conduct a MITRE Att&ck crosswalk
138+
### Conduct a MITRE ATT&CK crosswalk
139139

140140
With fusion, anomaly, and threat intelligence analytic rules enabled, conduct a MITRE Att&ck crosswalk to help you decide which remaining analytic rules to enable and to finish implementing a mature XDR (extended detection and response) process. This empowers you to detect and respond throughout the lifecycle of an attack.
141141

0 commit comments

Comments
 (0)