@Andy Ful Seeing the descriptions layed out like that made perfect sense to me. Thanks for the clarification!
@Gandalf_The_Grey Sorry for hijacking your thread! Haha
@Gandalf_The_Grey Sorry for hijacking your thread! Haha
Thanks. I was asking due to the comparison with VoodooShield, in the context of which you mentioned that H_C will probably stop the scripts before VS gets a chance to handle them. That makes perfect sense to me as regards script files. But it puzzles me as regards fileless scripting, because the recommended settings of H_C don't block script interpreters per se.I use the term "scripts" for files and "command-lines with script Interpreters" for fileless scripting. [/CODE]
Maybe we can ask a mod to move the posts? There are a lot of them, containing valuable discussion about H_C, and I think the H_C thread is where it belongs.@Gandalf_The_Grey,
The discussion about H_C is probably off-topic. If you want we can move some posts to the H_C thread.
There are some special configs for Avast and for SUA lockdown. The H_C setting profiles for Avast require some knowledge about SRP, CyberCapture and Hardened Aggressive Mode, so I made the predefined configs.@Andy Ful
So you have 3 basic configurations, each with an enhancement making it 6 variations for each OS (Windows 7 Windows 8 & Windows 10). I would keep it clean and drop all other versions.
The fileless anti-scripting protection is applied in H_C by SRP (PowerShell works in Constrained Language Mode), <Block Sponsors>, <Protect Shortcuts>, <FirewallHardening>, <ConfigureDefender>.Thanks. I was asking due to the comparison with VoodooShield, in the context of which you mentioned that H_C will probably stop the scripts before VS gets a chance to handle them. That makes perfect sense to me as regards script files. But it puzzles me as regards fileless scripting, because the recommended settings of H_C don't block script interpreters per se.
You forgot that other H_C settings, ConfigureDefender and FirewallHardening can add to the strictness.By the way, the names for the configs make sense to me. But they do require some previous knowledge.
Idea: give them a strictness rating. The most lenient config is 1, and the strictest is 10.
Can't argue with arithmetic!The fileless anti-scripting protection is applied in H_C by SRP (PowerShell works in Constrained Language Mode), <Block Sponsors>, <Protect Shortcuts>, <FirewallHardening>, <ConfigureDefender>.
You forgot that other H_C settings, ConfigureDefender and FirewallHardening can add to the strictness.
If you will define the strictness as chances to block something that the user would not want to block, then on Windows 10 (RS is always the base of calculations):
RS = 2, Basic = -1, Strict = +2, Enhanced =+1, CD HIGH = +1, CD MAX =+ 4, FirewallHardening (FH)= +1 or +2, other H_C hardening +1 or +2.
For example:
Basic_Recommended = -1 + 2 = 1
Basic_Recommended_Enhanced = -1 + 2 + 1 = 2
Recommended = 2
Basic_Recommended + CD HIGH + FH (H_C recommended) = -1 + 2 + 1 + 1 = 3
Recommended + CD HIGH + FH (H_C recommended) = 2 + 1 + 1 = 4
Strict_Recommended_Enhanced = 2 + 2 + 1 = 5
Basic_Recommended + CD MAX = -1 + 2 + 4 = 5
etc.
I think that Basic_Recommended, Recommended, and Strict_Recommended just do a similar thing as lenient, standard, and slightly paranoid. Use all restrictions for ultra paranoid and use only the restrictions from the right H_C panel for ultra lenient.Can't argue with arithmetic!
Really what I was suggesting was a way for someone who clicks on the "load profile" button to easily evaluate what he is seeing. If the options presented there would have some kind of color code or number code, the user could just choose a config on that basis.
Alternatively, they could be assigned a paranoia rating: ultra lenient, very lenient, slightly lenient, standard, slightly paranoid, very paranoid, ultra paranoid.
True, but my experience shows that VoodooShield will still block some scripts that H_C ignores. I see this when I try to print something with my HP printer. I think it is rundll32 that VS is detecting.The fileless anti-scripting protection is applied in H_C by SRP (PowerShell works in Constrained Language Mode), <Block Sponsors>, <Protect Shortcuts>, <FirewallHardening>, <ConfigureDefender>.
True.I think that Basic_Recommended, Recommended, and Strict_Recommended just do a similar thing as lenient, standard, and slightly paranoid. Use all restrictions for ultra paranoid and use only the restrictions from the right H_C panel for ultra lenient.![]()
It cannot do it, if by scripts you mean files with script extensions, except if the script is whitelisted in H_C. Is your HP software in the whitelisted folders?True, but my experience shows that VoodooShield will still block some scripts that H_C ignores. I see this when I try to print something with my HP printer. I think it is rundll32 that VS is detecting.
True.
Here is from VS whitelist:It cannot do it, if by scripts you mean files with script extensions, except if the script is whitelisted in H_C. Is your HP software in the whitelisted folders?
These command-lines come from scripts located in whitelisted folders or from Registry keys added by HP software. There is no reason to block them.Here is from VS whitelist:
View attachment 235926
Thanks, Andy. Not sure how practical this is, but Voodooshield should be using you as a consultant. I think they would have less FPs and frustrated users.These command-lines come from scripts located in whitelisted folders or from Registry keys added by HP software. There is no reason to block them.
The executable rundll32.exe can be also used by exploits, but first, the exploit has to download/extract/drop the malicious DLL payload. The H_C settings (including FirewallHardening) can prevent this in most cases.
It's a know issue with the latest beta:Andy, I am using the basic profile, every time I open the GUI and close it the box pops up asking me to log off even though I have not touched any settings. Is this normal? Thanks.
malwaretips.com
I think that VS took a different security approach. It would be hard to change the FPs rate, without diminishing the protection.Thanks, Andy. Not sure how practical this is, but Voodooshield should be using you as a consultant. I think they would have less FPs and frustrated users.
Yes. That is a known minor bug in the newest H_C beta version. H_C shows an unnecessary alert, even when nothing was changed. Please, look at this post:Andy, I am using the basic profile, every time I open the GUI and close it the box pops up asking me to log off even though I have not touched any settings. Is this normal? Thanks.
This setting is poorly documented. I think that it can work similarly to Intelligent Security Graph (ISG) integrated with WD Application Control. But, I never tested this. ISG allows application installers if they were checked by SmartScreen. But, in many cases the same application installers will be blocked if SmartScreen was not triggered. ISG uses SmartScreen when file has MOTW, and uses advanced heuristics in the cloud for other files.Question @Andy Ful
The ConfigureDefender MAX sets the Windows Defender Antivirus Cloud delivered protection to BLOCK all unknown executables. How does this differ from Smartscreen's cloud based protection? My guess is that WD cloud checks all executables while Smartscreen only checks executables with Mark Of The Web. Is that correct? Do you have links to info sources on scope of WD Cloud where this is explained?
...