Skip to content
Sponsor
3.0 preview2.3.0 stable

These docs describe the preview. Pick the version you run and every page marks what it doesn't have yet. Get the preview →
Maester 2.x docs (archived) →

(L1) Ensure devices without a compliance policy are marked 'not compliant'

CIS.M365.4.1MediumIntuneDevice compliance

Part of CIS · Intune · Device compliance · All checks

Run this check
Invoke-Maester -TestId CIS.M365.4.1

4.1 (L1) Ensure devices without a compliance policy are marked ‘not compliant’

Compliance policies are sets of rules and conditions that are used to evaluate the configuration of managed devices. These policies can help secure organizational data and resources from devices that don’t meet those configuration requirements. Managed devices must satisfy the conditions you set in your policies to be considered compliant by Intune. When combined with Conditional Access, this allows more control over how non-compliant devices are treated.

The recommended state is Mark devices with no compliance policy assigned as Not compliant

This test runs the same check as MT.1054. The benchmark’s audit reads the Intune device management settings and verifies that secureByDefault is true, which is what MT.1054 checks. The default, Compliant (secureByDefault is false), fails.

Implementing this setting is a first step in adopting compliance policies for devices. When used in together with Conditional Access policies the attack surface can be reduced by forcing an action to be taken for non-compliant devices.

Note: This section does not focus on which compliance policies to use, only that an organization should adopt and enforce them to their needs.

Any devices without a compliance policy will be marked not compliant. Care should be taken to first deploy any new compliance policies with a Conditional Access (CA) policy that is in the Report-only state. After the environment’s device compliance is better understood it is then appropriate to finally align with Mark devices with no compliance policy assigned as and enable any CA policies that enforce actions based on device compliance.

If a mature environment already has an existing device compliance CA policy and a large number of devices without an assigned compliance policy, this could cause disruption as those devices would then be suddenly considered not compliant.

  1. Navigate to Microsoft Intune admin center.
  2. Click on Devices and then under Managed devices on Compliance.
  3. Click Compliance settings.
  4. Ensure Mark devices with no compliance policy assigned as set to Not compliant
  1. Connect to Microsoft Graph using Connect-MgGraph -Scopes "DeviceManagementConfiguration.ReadWrite.All"
  2. Run the following commands:
$Uri = 'https://graph.microsoft.com/v1.0/deviceManagement'
$Body = @{
settings = @{
secureByDefault = $true
}
} | ConvertTo-Json
Invoke-MgGraphRequest -Uri $Uri -Method PATCH -Body $Body
Every attribute of this check
FieldValue
Test IDCIS.M365.4.1
SeverityMedium
SuiteCIS
ProductIntune
FeatureDevice compliance
AreaDevices and endpoints
Resource typeTenant
User impactMedium
Implementation costMedium
MITRE ATT&CKT1078.004 Cloud Accounts
Supports benchmarkCIS Microsoft 365 Foundations Benchmark (version 7.0.0), requirement 4.1
Benchmark levelL1
Benchmark profilesE3 Level 1, E5 Level 1
Supports controlscis-m365:4.1, nist-800-53-r5:AC-19, nist-800-53-r5:CM-6
PowerShell testTest-MtCisDevicesWithoutCompliancePolicyMarked
ServicesGraph
Compatible licensesINTUNE_A