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
Inactive Support Threads
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
Security Apps
Hard_Configurator Tools
Hard_Configurator - Windows Hardening Configurator
Message
<blockquote data-quote="Andy Ful" data-source="post: 885606" data-attributes="member: 32260"><p>Why did you do it via registry tweak and GPO? You could do it via H_C. It is not good to mix the H_C rules with the same GPO rules.</p><p>[ATTACH=full]241403[/ATTACH]</p><p>The <Block PowerShell Scripts> option is set to ON in the Recommended Settings. The <Block Windows Script Host> option blocks wscript and cscript also for administrators.</p><p>The H_C Recommended Settings already block wscript and cscript by SRP restrictions for processes running with standard privileges and this <strong>allows whitelisting</strong>. You can additionally block wscript and cscript by the policy <Block Windows Script Host>, but then you <strong>cannot whitelist any script</strong>.</p><p></p><p></p><p>All these extensions (and many more) are already blocked by H_C. Did you use the option <Designated File Types> ?</p><p></p><p>[ATTACH=full]241404[/ATTACH]</p><p></p><p>The advantage of using H_C (SRP) for that is that you can whitelist a particular script or file with a blocked extension, if something requires it to work (some devices use scripts, .hta, etc.). <strong>When you unassociate the file extension, the whitelisting is not possible.</strong></p></blockquote><p></p>
[QUOTE="Andy Ful, post: 885606, member: 32260"] Why did you do it via registry tweak and GPO? You could do it via H_C. It is not good to mix the H_C rules with the same GPO rules. [ATTACH type="full" alt="P_WSH.png"]241403[/ATTACH] The <Block PowerShell Scripts> option is set to ON in the Recommended Settings. The <Block Windows Script Host> option blocks wscript and cscript also for administrators. The H_C Recommended Settings already block wscript and cscript by SRP restrictions for processes running with standard privileges and this [B]allows whitelisting[/B]. You can additionally block wscript and cscript by the policy <Block Windows Script Host>, but then you [B]cannot whitelist any script[/B]. All these extensions (and many more) are already blocked by H_C. Did you use the option <Designated File Types> ? [ATTACH type="full" alt="DFT.png"]241404[/ATTACH] The advantage of using H_C (SRP) for that is that you can whitelist a particular script or file with a blocked extension, if something requires it to work (some devices use scripts, .hta, etc.). [B]When you unassociate the file extension, the whitelisting is not possible.[/B] [/QUOTE]
Insert quotes…
Verification
Post reply
Top