Skip to content

Commit 686fc58

Browse files
authored
Merge pull request #2351 from DebLanger/US360352_Metrics
update metrics enhancements
2 parents 99056d5 + a64f5cc commit 686fc58

File tree

4 files changed

+21
-10
lines changed

4 files changed

+21
-10
lines changed

exposure-management/exposure-insights-overview.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -63,20 +63,20 @@ You can prioritize which initiatives you want to see on the **Overview** dashboa
6363
On the **Metrics** tab of an initiative, or in the **Metrics** section of **Exposure Insights**, you can see the metric state, its effect and relative importance in an initiative, and recommendations to improve the metric. For each metric you can:
6464

6565
- Review metrics properties, including:
66-
- **14-day trend**: Shows the metric value changes over the last 14 days.
67-
- **Affected items**: The number of items within the metric. In most cases, these items would be assets that are exposed or that create a risk factor. In other cases, affected items would be the number of missing Microsoft secure score points to effectively implement recommended controls.
68-
- **Total**: Total number of assets under the metric scope.
69-
- **Weight**: The relative weight (importance) of the metric within the initiative, and its effect on the initiative score. From one (lowest) to ten (highest).
70-
- **Score impact**: The impact that completing the metric (getting it to 0%) has on the security initiative. Meaning if a given metric is completed, the score impact is the addition seen to the initiative score.
66+
- **Metric name**: The name of the metric.
67+
- **Progress**: Shows the improvement of the exposure level for the metric from 0 (high exposure) to 100 (no exposure).
7168
- **State**: Shows whether the metric needs attention, the risk was mitigated outside Security Exposure Management and shouldn't affect the initiative score, or was mitigated and the initiative score should be adjusted accordingly.
72-
- **Current value**: Current percentage of exposed assets within the total assets covered by the metric, with the state for each metric. Zero percent is best since there's no exposure, while 100% is worst.
69+
- **Affected assets**: The number of assets within the metric. In most cases, these would be assets that are exposed or that create a risk factor. In other cases, affected assets would be the number of missing Microsoft secure score points to effectively implement recommended controls.
70+
- **Total assets**: Total number of assets under the metric scope.
7371
- **Recommendations**: Security recommendations associated with the metric.
74-
- **Last Updated** shows the last date the metric was updated.
72+
- **Weight**: The relative weight (importance) of the metric within the initiative, and its effect on the initiative score. Shown as **High**, **Medium**, and **Low**. It can also be defined as **Risk accepted**.
73+
- **14-day trend**: Shows the metric value changes over the last 14 days.
74+
- **Last updated** shows the last date the metric was updated.
7575

7676
- Filter metrics for specific findings.
7777
- Drill down into metrics to review and fix associated issues.
7878
- Suggest new metrics to the product team.
79-
- Customize the weight of a metric so that it has greater or lesser effect in the initiative, based on your business priorities. Editing a metric affects all the initiatives in which the metric is included.
79+
- Customize the weight of a metric so that it has greater or lesser effect in the initiative, based on your business priorities. Editing a metric affects all the initiatives in which the metric is included. Once edited, it might take up to 2 hours for changes to be reflected in the metric value and its related initiatives.
8080

8181
### Unavailable metrics
8282

-486 KB
Loading

exposure-management/security-metrics.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,16 +37,17 @@ Security initiative metrics in [Microsoft Security Exposure Management](microsof
3737

3838
- **Description**: Metric description.
3939
- **State**: Current state of metric.
40+
- **Progress**: Shows the improvement of the exposure level for the metric from 0 (high exposure) to 100 (no exposure).
4041
- **Last state update**: The last time metric state was updated.
41-
- **Current value**: Current exposure score from significant to no/low exposure.
4242
- **Affected assets**. The number of affected assets out of the total assets.
4343
- **Weight**: Metric weight which affects the metric impact on initiative score.
44-
- **Score impact**: Possible score gain.
4544
- **Security recommendations**: Recommendations associated with the metric.
4645

4746
## Edit the metric weight
4847

4948
You can customize metric weight according to your business needs.
49+
> [!NOTE]
50+
> You must have **Exposure managment (manage)** permissions and access to all assets on the tenant level to edit the weight. For more information, see, [Permissions](prerequisites.md#permissions)
5051
5152
1. To edit the metric weight, select a specific metric.
5253
1. In the metric properties side panel, select Edit metric, then change the metric weight and apply.

exposure-management/whats-new.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,16 @@ Learn more about MSEM by reading the blogs, [here](https://techcommunity.microso
2424
>
2525
> `https://aka.ms/msem/rss`
2626
27+
## January 2025
28+
29+
### Metrics enhancements
30+
31+
The metrics have been enhanced to show the improvement of the exposure levels with a progress bar, progressing from left to right and from 0% (indicating high exposure) to 100% (indicating no exposure).
32+
33+
In addition, the metrics weight is now displayed as high, medium, or low, based on the metric's importance to the initiative. The weight can also be defined as risk accepted.
34+
35+
For more information, see, [Working with metrics](exposure-insights-overview.md#working-with-metrics)
36+
2737
## December 2024
2838

2939
### New predefined classifications

0 commit comments

Comments
 (0)