Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 926248" data-attributes="member: 32260">I think that Microsoft should introduce an option similar to Tamper Protection which could lock the Defender&#039;s settings against Administrative changes. With such an option enabled, any configuration change would have to be done only manually via Microsoft Security Center.In Enterprises, the administrators have Intune (or similar paid software) which can alert about Defender&#039;s configuration changes. But, Microsoft Defender free does not have anything like that. The user normally is not alerted about most changes and cannot see most of the Defender settings (including file extension exclusions). Of course, they can be seen by using PowerShell, WMI, or when looking into Windows Registry.For example PowerShell commands:(get-mppreference).ExclusionExtension(get-mppreference).ExclusionPath(get-mppreference).ExclusionIpAddress(get-mppreference).ExclusionProcess</blockquote>

[QUOTE="Andy Ful, post: 926248, member: 32260"] I think that Microsoft should introduce an option similar to Tamper Protection which could lock the Defender's settings against Administrative changes. With such an option enabled, any configuration change would have to be done only manually via Microsoft Security Center. In Enterprises, the administrators have Intune (or similar paid software) which can alert about Defender's configuration changes. But, Microsoft Defender free does not have anything like that. The user normally is not alerted about most changes and cannot see most of the Defender settings (including file extension exclusions). Of course, they can be seen by using PowerShell, WMI, or when looking into Windows Registry. For example PowerShell commands: [B](get-mppreference).ExclusionExtension (get-mppreference).ExclusionPath [B](get-mppreference).[/B]ExclusionIpAddress [B](get-mppreference).[/B]ExclusionProcess[/B] [/QUOTE]

Verification