I’ve simply been trying to follow this thread without having installed H_C. Until I do I am not going to be clear about specifics etc. that you discuss. But I am soaking up as much as I can in the meantime. I’d really like to compare it from experience to SysHardener, which I currently use.
There are some essential differences between SysHardener and Hard_Configurator (default-deny setup). SysHardener allows execution of programs (good and bad) downloaded by the user from the Internet or located on any other storage (pendrive, secondary disc, Memory Card, DVD disk, USB disk). On the contrary, Hard_Configurator (default-deny setup) blocks execution from all those places - to be more precise all locations outside Windows and Program Files folders. If the user wants to run the program installation from the forbidden location, then it is possible via 'Run As SmartScreen'. If the application was installed via 'Run As SmartScreen' to the forbidden location, then it is assumed as safe, so it can be whitelisted to run normally (without using 'Run As SmartScreen'). In any case, all installed applications were obligatory checked by SmartScreen reputation service, which is much safer than running them only under the protection of standard AV (the danger from 0-day malware).
There are more differences when something can be exploited, but the above is the essential difference. In the short words, the main difference follows from the below:
- SysHardener is default-allow for application installers and programs.
- Hard_Configurator is smart default-deny for them.
Edit.
If the user is cautious and knows the limitations of SmartScreen, then the above difference is less important and can be essential only when something will be exploited. Then default-deny protection is able to stop executable payload.