Maester Packs
LowScript packFree

CIS Windows 11 Intune L1

Checks that Intune policies configure the Level 1 recommendations of the CIS Microsoft Intune for Windows 11 Benchmark v5.0.0. One test per setting.

Version
0.1.3
Tests
307
Connectors
0
Published
7 Nov 2026

Pacers31Colts18 · pacers31colts18.cis-win11-intune-l1 · 0 stars · Open source · MIT

PowerShell 
Install-MtPack Pacers31Colts18/maester-packs-joeloveless/cis-win11-intune-l1

Install only packs from sources you trust. This pack is made by Pacers31Colts18, not by Maester. The site only indexes and scans it: Install-MtPack downloads it straight from github.com/Pacers31Colts18/maester-packs-joeloveless.

maester-packs.lock.json entry 
{  "Id": "pacers31colts18.cis-win11-intune-l1",  "Source": "Pacers31Colts18/maester-packs-joeloveless/cis-win11-intune-l1",  "Version": "0.1.3",  "Commit": "e9f51edda94c14f105b9079db5525af8814a7118",  "Digest": "sha256:8909734d7b8696c201179d841992ba808901b7a5cdf66352588c678adc4454a9"}

← All tests

MP.JL.CISW11INT.L1.015 MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning: WarningLevel is set to Enabled: 90% or less

Severity: MediumGraph

Description

CIS Microsoft Intune for Windows 11 Benchmark, recommendation 4.5.12 (Level 1).

The test passes when an assigned settings catalog policy for Windows sets Administrative Templates > MSS (Legacy) > MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning to Enabled, with WarningLevel set to 90% or less in the same policy, and no other assigned policy sets it to something else.

Remediation action

  1. In the Microsoft Intune admin center, go to Devices > Configuration and open (or create) a settings catalog policy for Windows 10 and later.
  2. Add Administrative Templates > MSS (Legacy) > MSS: (WarningLevel) Percentage threshold for the security event log at which the system will generate a warning and set it to Enabled, then set WarningLevel to 90% or less.
  3. Assign the policy to your Windows devices, and remove any other assigned policy that sets it to something else.

Related links

%TestResult%