Reply to thread

Message

<blockquote data-quote="Lenny_Fox" data-source="post: 848646" data-attributes="member: 82776">Hi,I nearly finished a Bachelor in webdesign &amp; digital marketing&nbsp; (just finishing my final thesis while working). Part of this study also included User Experience and Usability. I am not commenting on the interface and color scheme you choose ([USER=32260]@Andy Ful[/USER] ), just suggesting a new program which is basically a combination of your existing programs.I suggest a zero config version with just two settings Default and Hardened mode (like an ON=hardened and OFF=default switch). The aim is to maximize security while minimizing the functional impact. This is the reason why I suggest to allow executables to run in user space when they are whitelsted by Windows Defender, but dangerous file formats and lolbins should be restricted. DEFAULT modeSoftware Restriction Policies OFF and Windows Defender on Default and Windows FW block rules disabledHARDENED modeConfigure defender on MAXFirewall hardening enable LOLbins block rules.Software Restriction policies on DISALLOWED, but allow EXE, TMP, MSI and MSU,Enforcement Skip DLLs,, Designated File types default + Windows Script Hist + Powershell,Block sponsors Script Interpreters + DotNet compilers, Protect Windowss Folders ON, Protect shortcuts ON,Documents Anti-Exploit ON, Block remote access ON, Disable 16 bits ON, Disable SMB ON, Disable Cached Logons ONNow your software is signed this would extend the usability for a larger audience.Regards Lenny</blockquote>

[QUOTE="Lenny_Fox, post: 848646, member: 82776"] Hi, I nearly finished a Bachelor in webdesign & digital marketing (just finishing my final thesis while working). Part of this study also included User Experience and Usability. I am not commenting on the interface and color scheme you choose ([USER=32260]@Andy Ful[/USER] ), just suggesting a new program which is basically a combination of your existing programs. I suggest a zero config version with just two settings Default and Hardened mode (like an ON=hardened and OFF=default switch). The aim is to maximize security while minimizing the functional impact. This is the reason why I suggest to allow executables to run in user space when they are whitelsted by Windows Defender, but dangerous file formats and lolbins should be restricted. DEFAULT mode Software Restriction Policies OFF and Windows Defender on Default and Windows FW block rules disabled HARDENED mode Configure defender on MAX Firewall hardening enable LOLbins block rules. Software Restriction policies on DISALLOWED, but allow EXE, TMP, MSI and MSU, Enforcement Skip DLLs,, Designated File types default + Windows Script Hist + Powershell, Block sponsors Script Interpreters + DotNet compilers, Protect Windowss Folders ON, Protect shortcuts ON, Documents Anti-Exploit ON, Block remote access ON, Disable 16 bits ON, Disable SMB ON, Disable Cached Logons ON Now your software is signed this would extend the usability for a larger audience. Regards Lenny [/QUOTE]

Verification