Skip to content

Device Hardening Gaps (Secure Configuration Assessment)

The question it answers: Which device hardening settings fail on the most devices, ranked by impact?

Credential Guard, LSA protection, SMBv1, Office macro settings, BitLocker and hundreds more: which hardening settings fail on the most devices, ranked by impact. The configuration counterpart of Exploitable Vulnerabilities.

Where in the appTenant › Defender & Security Operations › Device Hardening Gaps
WorkloadSecurity
KindFindings list · dashboard tile
DataRead from Microsoft 365 when someone first opens it, then kept for the report cache lifetime (Settings > Data & cache, 1 hour unless changed).
LicenceDefender for Endpoint P2 or Defender Vulnerability Management.
Report id (API and MCP)tenant.secops.hardening-gaps
ColumnKeyType
SeveritySeverityStatus
CategoryCategoryText
ConfigurationSubjectLink
CheckSettingText
Impact / devicesValueText
RiskFindingText
Remediation / devicesDetailText
DateWhenDate
Devices failingNumberNumber

A findings list hides columns that no row fills. Severity is Critical, Serious, Warning, OK or Info; rows rated Critical, Serious or Warning need attention (Working with findings).

Licence: Defender for Endpoint P2 or Defender Vulnerability Management.

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
ThreatHunting.Read.AllMicrosoft GraphRun hunting queries and read shared saved hunting queries
Data sources it reads
  • POST /v1.0/security/runHuntingQuery (DeviceTvmSecureConfigurationAssessment, ...KB)
GET /ir-api/v1/reports/tenant.secops.hardening-gaps?size=100

An AI assistant reads it with the MCP tool get_report and the id tenant.secops.hardening-gaps. The client needs the Read grant for Security. See Using the API.