Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 940118" data-attributes="member: 32260">SRP protects scripts and scriptlets in 2 ways:<ol>
<li data-xf-list-type="ol">By file extension (VBS, JS, ..., BAT, CMD, PS1, MSI, CHM, JAR, HTA, etc.)</li>
<li data-xf-list-type="ol">By monitoring scripting engines (VBScript, JScript, Windows Command Shell, MSI Installer)</li>
</ol>The first is related to file associations and can block also other file types (included in the list of Protected SRP extensions). It is similar to SysHardener, but SWH allows whitelisting (not possible in SysHardener).The second is independent of file associations and is triggered when the scripting engine is executed (wscript.exe, cscript.exe, cmd.exe). It will block scripting in SWH when the &lt;Software Restriction Policies&gt;. So even the script embedded in a TXT file will be blocked, for example:wscript.exe /e:vbscript D:\helloworld.txt”.If you want to run scripts managed by VBScript, JScript, Windows Command Shell, or MSI Installer engines you have to whitelist them (scripts in the Windows and Program Files .... folders are whitelisted by default).</blockquote>

[QUOTE="Andy Ful, post: 940118, member: 32260"] SRP protects scripts and scriptlets in 2 ways: [LIST=1] [*]By file extension (VBS, JS, ..., BAT, CMD, PS1, MSI, CHM, JAR, HTA, etc.) [*]By monitoring scripting engines (VBScript, JScript, Windows Command Shell, MSI Installer) [/LIST] The first is related to file associations and can block also other file types (included in the list of Protected SRP extensions). It is similar to SysHardener, but SWH allows whitelisting (not possible in SysHardener). The second is independent of file associations and is triggered when the scripting engine is executed (wscript.exe, cscript.exe, cmd.exe). It will block scripting in SWH when the <Software Restriction Policies>. So even the script embedded in a TXT file will be blocked, for example: wscript.exe /e:vbscript D:\helloworld.txt”. If you want to run scripts managed by VBScript, JScript, Windows Command Shell, or MSI Installer engines you have to whitelist them (scripts in the Windows and Program Files .... folders are whitelisted by default). [/QUOTE]

Verification