I examined your settings. There is one option I cannot fully understand: 0-tolerance cloud blocking level. I thought that it had to block all unknown executables, but that is not the case, when looking at your tests.
Here is the link to docs.microsoft.com article:It seems that the Attack Surface Reduction introduced in Windows 10 Fall Creators Update works also in Windows Home version. It can be configured when using PowerShell.
The bad news is that the rule 'Block Office applications from creating child processes' does not work with Microsoft Office 2007 and Open Office. It works well with Microsoft Office 2016.
So it is possible, that the below ASR features:
will work only with the office software still supported by Microsoft (MS Office 2010, 2013, 2016).
- Block Office applications from creating child processes
- Block Office applications from creating executable content
- Block Office applications from injecting into other processes
- Block Win32 imports from Macro code in Office
Unfortunately, I cannot test it for MS Office 2010 and MS Office 2013. I someone can then please let me know.
Set-MpPreference -AttackSurfaceReductionRules_Ids BE9BA2D9-53EA-4CDC-84E5-9B1EEEE46550,D4F940AB-401B-4EFC-AADC-AD5F3C50688A,3B576869-A4EC-4529-8536-B80A7769E899,75668C1F-73B5-4CF0-BB93-3ECF5CB7CC84,D3E037E1-3EB8-44C8-A917-57927947596D,5BEB7EFE-FD9A-4556-801D-275E5FFC04CC,92E97FA1-2EDF-4476-BDD6-9DD0B4DDDC7B -AttackSurfaceReductionRules_Actions Enabled,Enabled,Enabled,Enabled,Enabled,Enabled,Enabled
Set WshShell = CreateObject("WScript.Shell")
WshShell.Run("c:\z\eso.exe")
WScript.Quit
I check it from here:new versions
Thanks.
In fact the ASR rule 'Impede JavaScript and VBScript to launch executables' has also another more appropriate description: 'Block JavaScript or VBScript from launching downloaded executable content'.Here is the link to docs.microsoft.com article:
Use Attack surface reduction rules to prevent malware infection
It follows from it, that ASR applies to:
The bad thing is that also the ASR rule 'Impede JavaScript and VBScript to launch executables' seems not working outside Microsoft Office.
- Windows 10, version 1709 (and later)
- Microsoft Office 365
- Microsoft Office 2016
- Microsoft Office 2013
- Microsoft Office 2010
After setting the ASR rules:
I can still run successfully eso.exe via the simple RunEso.vbs script:Code:Set-MpPreference -AttackSurfaceReductionRules_Ids BE9BA2D9-53EA-4CDC-84E5-9B1EEEE46550,D4F940AB-401B-4EFC-AADC-AD5F3C50688A,3B576869-A4EC-4529-8536-B80A7769E899,75668C1F-73B5-4CF0-BB93-3ECF5CB7CC84,D3E037E1-3EB8-44C8-A917-57927947596D,5BEB7EFE-FD9A-4556-801D-275E5FFC04CC,92E97FA1-2EDF-4476-BDD6-9DD0B4DDDC7B -AttackSurfaceReductionRules_Actions Enabled,Enabled,Enabled,Enabled,Enabled,Enabled,Enabled
Code:Set WshShell = CreateObject("WScript.Shell") WshShell.Run("c:\z\eso.exe") WScript.Quit
Set WshShell = CreateObject("WScript.Shell")
WshShell.Run("c:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noprofile -command (New-Object System.Net.WebClient).DownloadFile('https://kcsoftwares.com/files/sumo_lite.exe','C:\Users\Public\Downloads\sumo_lite.exe')")
WScript.Sleep(10000)
WshShell.Run("C:\Users\Public\Downloads\sumo_lite.exe")
WScript.Quit
The problem is that Hard_Configurator do not look outside from the computer (no external connections). I was thinking about adding a <Check for updates button>. That option could check for the program new versions.How can the average user of Hard Config keep notified about new versions?
I am on v. 3.1.0.0
Here is the link:Any plans to release the source code on GitHub? I mean for people worried about downloading unsigned applications xD
You are welcome. Post here any questions. I am ready to answer, if the help files are not sufficient.Hi, I installed Hard_Configurator. And I'm happy. It's a great tool.
I like this
View attachment 175695
The SRP part of Hard_Configurator will work, but you have reset SRP:I've been following your work on Hard_Configurator for some time and have been using SRP on Pro versions of Windows since Vista Days. My "mentor" with SRP was mechBgon, an early detailer of how to set up SRP. Never had any known malware since. While your work seems to be towards using H_C on Home versions, I was wondering if it is applicable for Pro versions as well? I was toying with trying it on a Pro version in place of my custom mechBgon installs. Would it work? Your thoughts.