(L1) Ensure devices without a compliance policy are marked 'not compliant'
Part of CIS · Intune · Device compliance · All checks
Invoke-Maester -TestId CIS.M365.4.1Overview
Section titled “Overview”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.
Rationale
Section titled “Rationale”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.
Impact
Section titled “Impact”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.
Remediation action
Section titled “Remediation action”- Navigate to Microsoft Intune admin center.
- Click on Devices and then under Managed devices on Compliance.
- Click Compliance settings.
- Ensure Mark devices with no compliance policy assigned as set to Not compliant
PowerShell
Section titled “PowerShell”- Connect to Microsoft Graph using
Connect-MgGraph -Scopes "DeviceManagementConfiguration.ReadWrite.All" - Run the following commands:
$Uri = 'https://graph.microsoft.com/v1.0/deviceManagement'$Body = @{ settings = @{ secureByDefault = $true }} | ConvertTo-JsonInvoke-MgGraphRequest -Uri $Uri -Method PATCH -Body $BodyRelated links
Section titled “Related links”- Microsoft Intune admin center
- Use compliance policies to set rules for devices you manage with Intune
- CIS Microsoft 365 Foundations Benchmark v7.0.0 - Page 184
Details
Section titled “Details”Every attribute of this check
| Field | Value |
|---|---|
| Test ID | CIS.M365.4.1 |
| Severity | Medium |
| Suite | CIS |
| Product | Intune |
| Feature | Device compliance |
| Area | Devices and endpoints |
| Resource type | Tenant |
| User impact | Medium |
| Implementation cost | Medium |
| MITRE ATT&CK | T1078.004 Cloud Accounts |
| Supports benchmark | CIS Microsoft 365 Foundations Benchmark (version 7.0.0), requirement 4.1 |
| Benchmark level | L1 |
| Benchmark profiles | E3 Level 1, E5 Level 1 |
| Supports controls | cis-m365:4.1, nist-800-53-r5:AC-19, nist-800-53-r5:CM-6 |
| PowerShell test | Test-MtCisDevicesWithoutCompliancePolicyMarked |
| Services | Graph |
| Compatible licenses | INTUNE_A |
Source
Section titled “Source”- Test:
tests/cis/Test.CIS.M365.4.1.ps1 - Documentation:
tests/cis/Test.CIS.M365.4.1.md
About this check
- Severity
- Medium
- Effort to fix
- Medium
- Impact on users
- Medium
- Product
- Intune
- Feature
- Device compliance
- Area
- Devices and endpoints
- Suite
- CIS