Separate metric progress from weight in the Identity Security Initiative

Use this document to resolve one bounded operational decision: Separate metric progress from weight in the Identity Security Initiative. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Identity Security Initiative from Microsoft supports the following bounded statements:

• Metric progress represents exposure improvement on a scale from 0 for high exposure to 100 for no exposure. The research record locates this support at Review security metrics > metric property table > Progress.
• Metric weight represents relative importance and effect on the initiative score; the interface shows High, Medium, Low, or Risk accepted. The research record locates this support at Review security metrics > metric property table > Weight.
• The initiative score combines each recommendation’s weight with the percentage of noncompliant recommendations. The research record locates this support at Review security metrics > paragraph before the metric property table.

Keep the evidence boundary at these traced claims. They support a review of directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking; they do not support conclusions outside the source’s stated conditions.

What the source does not establish

This feature is Preview, requires Defender for Identity and Security Exposure Management prerequisites, and does not fully support the Affected assets experience during Preview. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners and the environment’s recorded constraints.

Applicability questions

• For source statement 1 at Review security metrics > metric property table > Progress, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Review security metrics > metric property table > Weight, which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Review security metrics > paragraph before the metric property table, which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking are in and out of scope?
• Which condition in Active Directory data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of directory identities, posture assessments, exposed relationships, recommendations, ownership, remediation, and exception tracking, observed and expected states, owner, and reason for deviation.

An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory data quality, Windows DNS, sensor coverage, time, synchronization, cloud processing, and accountable identity owners before and after the test, and store only sanitized operational evidence.

Verification and evidence

A reviewer should be able to retrace the decision from Review security metrics > metric property table > Progress; Review security metrics > metric property table > Weight; Review security metrics > paragraph before the metric property table through affected-entity lists, directory attributes, relationship paths, assessment timestamps, remediation tests, and accepted exceptions. Record what was collected, where, when, by whom, and which system or role it represents.

Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.

Official references

• Identity Security Initiative — Microsoft