- Jul 3, 2015
- 8,153
The Lsass rule sometimes does not start working immediately, right? Did you notice that with any other rules?
No, I did not notice such behavior with other rules.The Lsass rule sometimes does not start working immediately, right? Did you notice that with any other rules?
There were problems with this feature, but now it works well.Is it recommended to enable "Network Protection"? Seems to be a instable protection feature ...
The new ConfigureDefender ver. 1.0.1.0 is available for testing:
Added ASR mitigations introduced in Windows ver. 1803 (they should work also on updated ver. 1709).
- for Windows 64-bit: AndyFul/ConfigureDefender
- for Windows 32-bit: AndyFul/ConfigureDefender
In the "Child Protection", all ASR mitigations are enabled, with some folder exclusions:
Windows, Program Files ..., ProgramData\Microsoft\Windows Defender.
.
I noticed that mitigation: "Block executable files from running unless they meet a prevalence, age, or trusted list criteria" is more restrictive than Defender 'Cloud Protection Level' set to Block. Furthermore, most executables blocked by this mitigation (but not all) can be run after one day.
.
The mitigation "Block credential stealing from the Windows local security authority subsystem (lsass.exe)" can block some schtaks.exe processes and also processes started by Windows Defender in the folder: ProgramData\Microsoft\Windows Defender.
Post edited.
The Lsass rule, does not support exclusions.
Please, wait a few weeks. This version is OK, but there is a little information about how some ASR mitigations work. So, the predefined configs may change after testing.Do you advise downloading this to replace current version - IF NOT testing?
That was an official release.Patiently waiting for the official release!
That was an official release.
Thanks for the update and this great piece of softwareThe new ConfigureDefender ver. 1.0.1.1 is available:
for Windows 64-bit: AndyFul/ConfigureDefender
for Windows 32-bit: AndyFul/ConfigureDefender
.
1. Corrected a minor bug related to unnecessary folder exclusion for the ASR mitigation that does not support exclusions.
2. In <Defender high settings> the ASR mitigation 'Use advanced protection against ransomware' is set to ON, and 'Controlled Folder Access' is set to Audit.
.
<Defender high settings> can be adopted by most users.
<Child Protection> is very restrictive due to Controlled Folder Access, hiding the Defender Security Center, and two new mitigations:
The new version was sent to Microsoft and is whitelisted by Defender. It is not whitelisted by SmartScreen, yet. This will take some time.
- Block executable files from running unless they meet a prevalence, age, or trusted list criteria
- Block credential stealing from the Windows local security authority subsystem (lsass.exe)
Be safe.
'Audit' means that the file will not be blocked (no visible alert), but the info about the possible block (if the setting was Enabled) is written to the Windows Event Log. It helps to find out how safe will be enabling the setting and what the user can expect after enabling it.Thanks for the update and this great piece of software
What does "Audit" mean?
Do you get a popup?
Okay, thanks for the explanation and the link. I will have a look at it.'Audit' means that the file will not be blocked (no visible alert), but the info about the possible block (if the setting was Enabled) is written to the Windows Event Log. It helps to find out how safe will be enabling the setting and what the user can expect after enabling it.
Import custom views to see Windows Defender Exploit Guard events
I edited my previous post to attach the config file for NirSoft FullEventLogView.Okay, thanks for the explanation and the link. I will have a look at it.
Cool, I could find one audited event this way on my laptopI edited my previous post to attach the config file for NirSoft FullEventLogView.