

Device/Vendor/MSFT/Policy/Config/Defender/AllowRealtimeMonitoring they didn't found by the way that I found :) With MS Support we tested by adding OMA-URI with Integer 1. Also working with MS Support, already 4 months working on this issue. And tested "Microsoft Defender for Endpoint baseline" to add/remove users to see if can somehow trigger the "re-enable". We have dedicated ASR policies under Endpoint security -> Attack surface reduction. Security Baseline by the way created if follow the Onboarding process in Microsoft 365 E3 from Endpoint wizard. The question will be the usual one, why and how to fix Jindal

HKLM\Software\Policies\Microsoft\Windows Defender\Real-Time ProtectionĬriteria: If the value "DisableBehaviorMonitoring" is REG_DWORD = 0, this is not a finding. Procedure: Use the Windows Registry Editor to navigate to the following key: Verify the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Defender Antivirus -> Real-time Protection -> "Turn on behavior monitoring" is set to "Enabled" or "Not Configured". Set the policy value for Computer Configuration -> Administrative Templates -> Windows Components -> Windows Defender Antivirus -> Real-time Protection -> "Turn on behavior monitoring" to "Enabled " or "Not Configured".

CCI-001170 - The information system prevents the automatic execution of mobile code in organization-defined software applications.STIGQter: STIG Summary: Microsoft Windows Defender Antivirus Security Technical Implementation Guide Version: 2 Release: 2 Benchmark Date: : Windows Defender AV must be configured to enable behavior monitoring.
