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
Security
Guides - Privacy & Security Tips
Software restriction Policies to Windows Home
Message
<blockquote data-quote="Andy Ful" data-source="post: 544791" data-attributes="member: 32260"><p>Windows_Security</p><p></p><p>[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Safer\CodeIdentifiers]</p><p>"DefaultLevel"=dword:00020000</p><p>"DefaultLevel"=dword:00000000</p><p></p><p>Both values are for default deny SRP. The only difference I noticed is when You remove BAT, CMD, JS, JSE, VBS, VBE, WSH extensions from SRP protected extensions list in :</p><p>HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Safer\CodeIdentifiers\ExecutableTypes</p><p></p><p>If "DefaultLevel"=dword:00000000 then removed extensions are still protected by SRP, but at the later stage (when script interpreters try to find and run files).</p><p>If "DefaultLevel"=dword:00020000, scripts are not protected after extensions removal. They are protected only if the script extensions are on the list.</p><p>I found out this by accident while testing "Run As Smartscreen", because I use SRP with "DefaultLevel"=dword:00000000 and had to remove script extensions to make it working.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>I confirmed that now, in Windows 10 Pro, choosing Basic User gives "DefaultLevel"=dword:00020000 .</p><p>I was confused because in Lucy's post and some technet articles "DefaultLevel"=dword:00000000 had been used.</p><p></p><p><a href="http://www.wilderssecurity.com/threads/maximising-windows-7-security-with-srp-under-lua-whatever-the-win7-version.262686/" target="_blank">http://www.wilderssecurity.com/threads/maximising-windows-7-security-with-srp-under-lua-whatever-the-win7-version.262686/</a></p><p><a href="https://technet.microsoft.com/en-us/library/bb457006.aspx" target="_blank">Using Software Restriction Policies to Protect Against Unauthorized Software</a></p></blockquote><p></p>
[QUOTE="Andy Ful, post: 544791, member: 32260"] Windows_Security [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Safer\CodeIdentifiers] "DefaultLevel"=dword:00020000 "DefaultLevel"=dword:00000000 Both values are for default deny SRP. The only difference I noticed is when You remove BAT, CMD, JS, JSE, VBS, VBE, WSH extensions from SRP protected extensions list in : HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Safer\CodeIdentifiers\ExecutableTypes If "DefaultLevel"=dword:00000000 then removed extensions are still protected by SRP, but at the later stage (when script interpreters try to find and run files). If "DefaultLevel"=dword:00020000, scripts are not protected after extensions removal. They are protected only if the script extensions are on the list. I found out this by accident while testing "Run As Smartscreen", because I use SRP with "DefaultLevel"=dword:00000000 and had to remove script extensions to make it working.:) I confirmed that now, in Windows 10 Pro, choosing Basic User gives "DefaultLevel"=dword:00020000 . I was confused because in Lucy's post and some technet articles "DefaultLevel"=dword:00000000 had been used. [URL]http://www.wilderssecurity.com/threads/maximising-windows-7-security-with-srp-under-lua-whatever-the-win7-version.262686/[/URL] [URL="https://technet.microsoft.com/en-us/library/bb457006.aspx"]Using Software Restriction Policies to Protect Against Unauthorized Software[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Top