Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Operating Systems
Windows 10
OS Archive
Use Windows 10 build-in (anti)execution options
Message
<blockquote data-quote="Windows_Security" data-source="post: 754778" data-attributes="member: 50782"><p>Andy,</p><p></p><p>only install. also' regular' programs which use the HKLM run keys (elevated). Because ransomware likes to misuses the HKCU keys to survive re-boot, I don't set a deny, but remove the rights of standard user, so in order to change them you need to be admin or higher. Same trick with windows startfolders for users, don't set a deny, but remove the create/write rights for current user. this still allow updates invoked by Windows itself (as admin, system or trusted installer).</p><p></p><p>I use basic user as default level with run MSI as admin reg tweak, So right click run as admin allows to install everything. I know this is not as secure as Default deny (<strong><span style="color: rgb(65, 168, 95)">not anymore when adding these folder holes to protected folders feature of WD</span></strong>), I like to have the option to right click run as admin to install stuff.<s>I accept the down side that basic user has holes compared to default deny</s></p><p></p><p>It is my experience that you don't need a watertight block, just adding several hurdles and tripwires from different angles, makes it very dificult for exploits to succeed (e.g. add a WD exploit rule for powershell to disable launching child processes, I don't need NVT OS armor for that).</p><p></p><p>I</p><p></p><p>Regards</p><p></p><p>Kees</p></blockquote><p></p>
[QUOTE="Windows_Security, post: 754778, member: 50782"] Andy, only install. also' regular' programs which use the HKLM run keys (elevated). Because ransomware likes to misuses the HKCU keys to survive re-boot, I don't set a deny, but remove the rights of standard user, so in order to change them you need to be admin or higher. Same trick with windows startfolders for users, don't set a deny, but remove the create/write rights for current user. this still allow updates invoked by Windows itself (as admin, system or trusted installer). I use basic user as default level with run MSI as admin reg tweak, So right click run as admin allows to install everything. I know this is not as secure as Default deny ([B][COLOR=rgb(65, 168, 95)]not anymore when adding these folder holes to protected folders feature of WD[/COLOR][/B]), I like to have the option to right click run as admin to install stuff.[S]I accept the down side that basic user has holes compared to default deny[/S] It is my experience that you don't need a watertight block, just adding several hurdles and tripwires from different angles, makes it very dificult for exploits to succeed (e.g. add a WD exploit rule for powershell to disable launching child processes, I don't need NVT OS armor for that). I Regards Kees [/QUOTE]
Insert quotes…
Verification
Post reply
Top