Team: Huntress Managed Identity Security Posture Management (ISPM)
Product: Microsoft 365, Microsoft Secure Score
Summary: This article explains the Managed ISPM page in the Security Insights Report, including Compliance Rating, Microsoft Secure Score, and the posture work Huntress did during the period.
In this Article
Overview
Account-Level and Organization-Level Versions
Compliance Rating
Microsoft Secure Score
Posture Activity This Period
Deployment Method Breakdown
How This Page Differs from the Identity Posture Assessment
Related Articles
Overview
The Managed ISPM page shows the security posture of your Microsoft 365 environment. It covers how many recommended protections are in place, how your Microsoft Secure Score compares, and what Huntress did to improve your posture during the period.
The page appears only for accounts and organizations with Huntress Managed Identity Security Posture Management (ISPM). The Managed EDR, ITDR, and SIEM pages report detection and response activity. This page reports the current state of your posture and how it changed.
Account-Level and Organization-Level Versions
An account-level report summarizes every organization with Managed ISPM. An organization-level report shows one organization's own results. This table shows which sections appear on each:
| Section | Account-level report | Organization-level report |
|---|---|---|
| Total identities | Shown | Shown |
| Organizations with and without Managed ISPM, and Top Organizations | Shown | Not shown |
| Compliance Rating | Average across organizations with Managed ISPM | The organization's rating |
| Microsoft Secure Score | Organization Secure Score Breakdown by risk band | The organization's score and risk band |
| Posture Activity this Period | Shown, with hours saved | Shown, without hours saved |
| Deployment Method Breakdown | Shown | Not shown |
The account-level page also lists the three organizations with the highest Compliance Rating. Organizations are ranked by the percentage of their controls that are compliant, so an organization at 30/30 ranks above one at 40/50.
Compliance Rating
Your Compliance Rating shows how many recommended security protections are in place and working as expected. A higher rating means stronger protection and fewer security gaps.
A chart shows the rating for the 6 months ending with the reporting period. Months without a rating have no data point. When your rating is already high, holding steady from month to month is a good result.
Microsoft Secure Score
Microsoft Secure Score shows the percentage of Microsoft's recommended security protections that are in place. The report groups scores into risk bands:
| Risk band | Score | What it means |
|---|---|---|
| High risk | Below 60% | Important recommended protections still need attention. |
| Medium risk | 60% to 80% | Many recommended protections are in place, with some important improvements still to make. |
| Low risk | 80% or higher | Most recommended protections are in place. Huntress continues to monitor and address new recommendations. |
On account-level reports, the Organization Secure Score Breakdown shows how many organizations fall into each band. If a score hasn't been synced from Microsoft yet, the section says A Microsoft Secure Score has not been synced yet.
Posture Activity This Period
This section shows the posture work Huntress did during the period. It doesn't appear when there was no posture work.
On organization-level reports, it counts:
- Controls made compliant: Security settings Huntress updated to meet recommended standards, including protections that had drifted out of compliance and were corrected.
- Conditional access policies (CAPs) that completed Learning Mode: Policies that finished the impact analysis Huntress runs before enforcement, so issues are addressed before users are affected.
On account-level reports, the section leads with Hours Saved from this work. Huntress credits about 15 minutes for each control brought back into compliance with Continuous Enforcement and for each CAP that completes Learning Mode. These hours are already included in the hours saved on the Executive Summary, so don't add the two together. For the full calculation, see How Are Metrics and Hours Saved Calculated?
Deployment Method Breakdown
On account-level reports, this section shows how many organizations use each deployment method:
| Method | Meaning |
|---|---|
| Managed | Huntress keeps the controls up to date automatically. |
| Modified | The controls have been customized. |
| Off | Managed ISPM controls aren't deployed. |
Managed controls need the least maintenance because they stay up to date automatically. We recommend moving organizations set to Modified or Off to Managed for more consistent protection.
How This Page Differs from the Identity Posture Assessment
The Managed ISPM page and the Identity Posture Assessment answer different questions. This table compares them:
| Managed ISPM page | Identity Posture Assessment | |
|---|---|---|
| When | Every monthly and quarterly report | On demand |
| Purpose | Posture trend and Huntress activity over the period | A detailed point-in-time view of security gaps |
| Where | Security Insights Report | Managed ISPM in Huntress |
The Managed ISPM page isn't a compliance or audit report. For a detailed view, generate an Identity Posture Assessment.
Related Articles
These articles cover Managed ISPM in more detail: