Skip to content

Commit 10fd227

Browse files
Merge pull request #293754 from yelevin/patch-2
Plain-text limitation
2 parents f677eed + 3f557ee commit 10fd227

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/sentinel/create-analytics-rules.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,8 +78,8 @@ In the Azure portal, stages are represented visually as tabs. In the Defender po
7878

7979
| Field | Description |
8080
| ----- | ----------- |
81-
| **Name** | A unique name for your rule. |
82-
| **Description** | A free-text description for your rule. |
81+
| **Name** | A unique name for your rule. This field supports plain text only. |
82+
| **Description** | A free-text description for your rule.<br>If Microsoft Sentinel is onboarded to the Defender portal, this field supports plain text only. |
8383
| **Severity** | Match the impact the activity triggering the rule might have on the target environment, should the rule be a true positive.<br><br>**Informational**: No impact on your system, but the information might be indicative of future steps planned by a threat actor.<br>**Low**: The immediate impact would be minimal. A threat actor would likely need to conduct multiple steps before achieving an impact on an environment.<br>**Medium**: The threat actor could have some impact on the environment with this activity, but it would be limited in scope or require additional activity.<br> **High**: The activity identified provides the threat actor with wide ranging access to conduct actions on the environment or is triggered by impact on the environment. |
8484
| **MITRE ATT&CK** | Choose those threat activities which apply to your rule. Select from among the **MITRE ATT&CK** tactics and techniques presented in the drop-down list. You can make multiple selections.<br><br>For more information on maximizing your coverage of the MITRE ATT&CK threat landscape, see [Understand security coverage by the MITRE ATT&CK® framework](mitre-coverage.md). |
8585
| **Status** | **Enabled**: The rule runs immediately upon creation, or at the [specific date and time you choose to schedule it (currently in PREVIEW)](#schedule-and-scope-the-query).<br>**Disabled**: The rule is created but doesn't run. Enable it later from your **Active rules** tab when you need it. |

articles/sentinel/customize-alert-details.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,8 +72,8 @@ Follow the procedure detailed below to use the alert details feature. These step
7272

7373
| Name | Description |
7474
| ---- | ----------- |
75-
| **AlertName** | String |
76-
| **Description** | String |
75+
| **AlertName** | String. Supports plain text only. |
76+
| **Description** | String. Supports plain text only, if Microsoft Sentinel is onboarded to Defender portal. |
7777
| **AlertSeverity** | One of the following values: <br>- **Informational**<br>- **Low**<br>- **Medium**<br>- **High** |
7878
| **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** |
7979
| **Techniques** (Preview) | A string that matches the following regular expression: `^T(?<Digits>\d{4})$`. <br>For example: **T1234** |

0 commit comments

Comments
 (0)