Skip to content

Commit 378aaa3

Browse files
authored
Merge pull request #268085 from batamig/alert-details-override
Sentinel alert property details
2 parents b40b493 + 0fe6f2c commit 378aaa3

File tree

1 file changed

+18
-17
lines changed

1 file changed

+18
-17
lines changed

articles/sentinel/customize-alert-details.md

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Customize alert details in Microsoft Sentinel | Microsoft Docs
33
description: Customize how alerts are named and described, along with their severity and assigned tactics, based on the alerts' content.
44
author: yelevin
55
ms.topic: how-to
6-
ms.date: 11/23/2022
6+
ms.date: 03/05/2024
77
ms.author: yelevin
88
---
99

@@ -50,22 +50,23 @@ Follow the procedure detailed below to use the alert details feature. These step
5050
5151
1. To override other default properties, select an alert property from the **Alert property** drop-down list. Then select the field from the query results, whose contents you want to populate the alert property, from the **Value** drop-down list.
5252

53-
1. To override more default properties, select **+ Add new** and repeat the previous step.
54-
55-
The following alert properties can be overridden:
56-
- AlertName
57-
- Description
58-
- AlertSeverity
59-
- Tactics
60-
- Techniques (Preview)
61-
- AlertLink (Preview)
62-
- ConfidenceLevel (Preview)
63-
- ConfidenceScore (Preview)
64-
- ExtendedLinks (Preview)
65-
- ProductComponentName (Preview)
66-
- ProductName (Preview)
67-
- ProviderName (Preview)
68-
- RemediationSteps (Preview)
53+
1. To override more default properties, select **+ Add new** and repeat the previous step. The following properties can be overridden:
54+
55+
|Name |Description |
56+
|---------|---------|
57+
|**AlertName** | String |
58+
|**Description** | String |
59+
|**AlertSeverity** | One of the following values: <br>- **Informational**<br>- **Low**<br>- **Medium**<br>- **High** |
60+
|**Tactics** | One of the following values: <br>- **Reconnaissance**<br>- **ResourceDevelopment**<br>- **InitialAccess**<br>- **Execution**<br> - **Persistence**<br>- **PrivilegeEscalation**<br>- **DefenseEvasion**<br>- **CredentialAccess** <br>- **Discovery**<br> - **LateralMovement**<br>- **Collection**<br>- **Exfiltration**<br>- **CommandAndControl**<br>- **Impact**<br> - **PreAttack**<br>- **ImpairProcessControl**<br>- **InhibitResponseFunction** |
61+
|**Techniques** (Preview) | A string that matches the following regular expression: `^T(?<Digits>\d{4})$`. <br>For example: **T1234** |
62+
|**AlertLink** (Preview) | String |
63+
|**ConfidenceLevel** (Preview) | One of the following values: <br>- **Low**<br>- **High**<br>- **Unknown** |
64+
|**ConfidenceScore** (Preview) | Integer, between **0**-**1** (inclusive) |
65+
|**ExtendedLinks** (Preview) | String |
66+
|**ProductComponentName** (Preview) | String |
67+
|**ProductName** (Preview) | String |
68+
|**ProviderName** (Preview) | String |
69+
|**RemediationSteps** (Preview) | String |
6970

7071
If you change your mind, or if you made a mistake, you can remove an alert detail by clicking the trash can icon next to the **Alert property/Value** pair, or delete the free text from the **Alert Name/Description Format** fields.
7172

0 commit comments

Comments
 (0)