Overview - Exposure insights

Exposure insights in Microsoft Security Exposure Management continuously aggregate security posture data and insights across workloads and resources, into a single pipeline.

Security Exposure Management is currently in public preview.

Exposure insights

Exposure insights provide rich context around the security posture state of your asset inventory.

Chief Information Security Officers (CISOs), decision makers, risk owners, and security teams can use security insights and context to understand and manage exposure risk across the entire organization, and to prioritize security efforts and investment.

Exposure insights provide visibility and granular context around security posture state. Insights enable you to:

• Break down organizational security posture into manageable security projects.
• Manage security projects as security initiatives in Security Exposure Management.
• Review, measure, and track risk exposure for each security initiative.
• Follow actionable recommendations and remediation steps to improve security posture and reduce risk.
• Monitor security posture state and improvements over time.

Security initiatives

Security initiatives provide a simple way to assess security readiness for a specific security area or workload, and to constantly track and measure exposure risk for that area or workload over time.

Security Exposure Management provides initiatives that currently include:

• Workload initiatives: Assess and manage the risk associated with specific workload domains, such as security for endpoints, identity resources, and cloud assets.

• Horizontal threat initiatives: Assess and manage risk for specific threat areas, such as ransomware protection, or financial fraud.

• Threat analytics initiatives: Assess threat risk with initiatives that are based on up-to-date research from Microsoft threat analytics. Microsoft threat analytics is a set of reports from expert Microsoft security researchers that provide information about real and relevant threats. These threat initiatives focus on:

  • Threat actors and threat vectors.
  • Threat reports that have three or more recommendations.

• Zero trust initiative: Assess the risk associated with zero trust compliance. This initiative aligns with guidance provided by the zero trust adoption framework.

Initiative elements

Working with initiatives

You can prioritize which initiatives you want to see on the Overview dashboard. Review the initiative score, and drill down into initiatives to see associated metrics and understand where gaps or risks reside.

Working with metrics

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:

• Review metrics properties, including:

  • 14-day trend: Shows the metric value changes over the last 14 days.
  • 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.
  • Total: Total number of assets under the metric scope.
  • Weight: The relative weight (importance) of the metric within the initiative, and its effect on the initiative score. From one (lowest) to ten (highest).
  • 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.
  • 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.
  • 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.
  • Recommendations: Security recommendations associated with the metric.
  • Last Updated shows the last date the metric was updated.

• Filter metrics for specific findings.

• Drill down into metrics to review and fix associated issues.

• Suggest new metrics to the product team.

• 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.

Unavailable metrics

In some cases, metrics display grayed out because the underlying data for the metric doesn't exist. For instance, if a required workload isn't onboarded, or if a secure score metric is set to completed or risk accepted in secure score and Security Exposure Management can't access the metric data.

Grayed out metrics aren't considered for score calculation.

Working with recommendations

Security Exposure Management ingests security recommendations from multiple sources, including Microsoft Defender for Cloud running the Defender for Cloud Security Posture Management (CSPM) plan, Microsoft Secure Score, Microsoft threat analytics, and other Microsoft workloads. Security Exposure Management integrates all of these recommendations into a single security catalog.

• You can view recommendations from the Recommendations tab, or review and remediate recommendations within a specific security initiative or metric.
• Each recommendation provides remediation steps to fix detected compliance issues.
• Every action taken on a security recommendation helps to reduce exposure and risk, improve security posture, and directly influence its related security initiatives and metrics.

Security Exposure Management categorizes recommendations by compliance status, as follows:

• Compliant: Indicates that the recommendation was implemented successfully.
• Not complaint: Indicates that the recommendation hasn't been fixed.
• Mitigated by organization: Displays when steps to mitigate recommendations were taken elsewhere, and Security Exposure Management can't know whether recommendations are compliant. For example, by changing a status in Secure score.
• Not available: Means there isn't enough information to determine the compliance status.

Secure score

Microsoft Secure Score helps organizations to plan and improve overall security posture using the secure score as a tracking metric.

Security Exposure Management uses secure score as one of its sources for initiative scores.

• Secure Score has recommended actions for a number of products.
• When you select a recommendation to review, Security Exposure Management allows you to remediate the problem in the specific product, including recommendations that are derived from Secure Score.
• For recommendations where Secure Score is relevant, the recommendation doesn't display if Secure Score isn't active.

Monitoring and improving scores

The exposure state for a security initiative is reflected in the initiative score.

• Initiatives with metrics: For initiatives with metrics, the score is calculated based on the value and weight of metrics within the initiative.
• Initiatives without metrics: For threat initiatives that don't have metrics, the initiative score is calculated in the same way that Secure Score is calculated.

For initiatives with metrics:

• As metrics improve the initiative score rises to reflect an improved posture for the security initiative.
• Metrics largely improve by applying the recommendations associated with the initiative.
• Changes in metrics, including deprecation/removal, value, and metric properties can affect the initiative score.

Reviewing initiative history

On the History tab of an initiative, you can:

• Track the history of changes greater than 2.5% that affect initiative score.
• Filter for specific time points.
• Drill down to specific changes.

When you drill down into a specific change, you can see the percentage effects of metrics in the initiative score, along with the change reason. Reasons include:

• Property change - A change in the weight of the metric in the score.
• Value change - A change in the value of the metric in the initiative score.
• Metric removed - The metric is no longer relevant for that specific initiative. For instance, if a better suggestion is introduced or it becomes irrelevant.
• Metric depreciated - The metric is removed globally.

Selecting the metric that changed provides more details about the change. For instance, it might display the new weight of a property change, or the number of affected assets before or after the change.

You can't control the metric or score changes in advance.

Reviewing events

Events measure the score drop or worsening in the metric status. Events include:

• Metric score drop events: These events are issued with there's a decrease of at least 2% in metric score (exposure grew by 2%) since yesterday.
• Initiative score drop events: These events are issued when there's a decrease of at least 2% in initiative score since yesterday.

On the Events page for an initiative, you can view and filter events.

Next steps

• Review security initiatives
• Investigate security metrics
• Review security recommendations
• Explore security events