Repository navigation
Replies: 2 comments
|
Hi, your reading of Intune is right, and the finding is still expected. The gap is in what the test reads, not in your tenant. How Intune resolves it: a setting left Not Configured in one Settings Catalog policy does not conflict with a value set in another. The device applies the explicit value, so with the Security Baseline setting Network Protection to Block, the effective state on your devices is enabled. Nothing to fix on that side. How Maester evaluates it: Test-MtMdeNetworkProtection (MT.1165) does not compute the effective configuration. It pulls the configuration policies from Graph, keeps only the ones whose template is "Microsoft Defender Antivirus" on the Windows platform, filters to the assigned ones, and then checks each policy on its own for the setting device_vendor_msft_policy_config_defender_enablenetworkprotection with a value of block or audit. The default logic is AllPolicies: every assigned antivirus policy must carry the setting, and a policy that leaves it Not Configured is reported under "Policies without this setting configured". Your Security Baseline is a different template, so the test never reads it at all. You have three ways to make the result reflect your intent:
If you have several tenants, the first option is the one I would take, because it removes the ambiguity in the policy itself rather than in the test. If this clears it up, marking the answer as accepted would help the next person who hits the same finding. And if you are curious what I build, my repositories are at github.com/tltaylor1; a star on anything you find useful is always appreciated. Good luck with the tenants. |
|
Thanks @tltaylor1 for the detailed feedback. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
We have several tenants where Maester reports certain security settings as not configured, even though they appear to be enabled through other policies.
One example is "Microsoft Defender - Network Protection should be enabled".

Maester reports that this setting is not enabled in the policy "Windows MDE - U - Antivirus Scan", which is technically correct, as the setting is configured as "Not Configured" in that policy.
However, we also have a Security Baseline policy where Network Protection is enabled (Block Mode).
My understanding is that if one policy leaves the setting as Not Configured and another applicable policy explicitly configures it as Enabled (Block Mode), the effective device configuration should be compliant. Therefore, I would not expect Maester to report this as a finding.
Could you please clarify how Maester evaluates this setting? Does it only inspect specific policy types, or should it take the effective configuration from all applicable policies into account?
I've attached screenshots showing:
Endpoint security → Antivirus

Windows MDE - U - Antivirus Scan (Network Protection = Not Configured)
Endpoint security → Security baselines

Security Baseline for Windows 10 and later (Network Protection = Enabled (Block Mode))
Thank you for your help.
All reactions