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
Security
Guides - Privacy & Security Tips
How do you secure PowerShell?
Message
<blockquote data-quote="Andy Ful" data-source="post: 623922" data-attributes="member: 32260"><p>Thanks [USER=37647]@shmu26[/USER]. I wrote :</p><p><em>Process Lasso, Sandboxie, NVT ExeRadar Pro, etc. can monitor executables: powershell.exe and powershell_ise.exe. (...) But mostly, they cannot stop custom made executable with an unknown name.</em></p><p></p><p>That was unfair to NVT ERP (that I like very much). In fact, any anti-exe can stop custom made executable with an unknown name (if not whitelisted), but NVT ERP additionally can stop vulnerable system executables.</p><p>Sandboxie can force powershell.exe and powershell_ise.exe to run sandboxed (paid version). Generally, it cannot stop custom made powershell host, but if the parent process is sandboxed, then the child fake powershell executable is also sandboxed. So, the strength of Sandboxie protection depends, if one runs potentially vulnerable applications in the sandbox or not.</p><p></p><p>Edited!</p><p>The real problem for anti-exe solutions, arise with memory exploits, when they can run PowerShell from System.Management.Automation.dll (System.Management.Automation.ni.dll) .</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 623922, member: 32260"] Thanks [USER=37647]@shmu26[/USER]. I wrote : [I]Process Lasso, Sandboxie, NVT ExeRadar Pro, etc. can monitor executables: powershell.exe and powershell_ise.exe. (...) But mostly, they cannot stop custom made executable with an unknown name.[/I] That was unfair to NVT ERP (that I like very much). In fact, any anti-exe can stop custom made executable with an unknown name (if not whitelisted), but NVT ERP additionally can stop vulnerable system executables. Sandboxie can force powershell.exe and powershell_ise.exe to run sandboxed (paid version). Generally, it cannot stop custom made powershell host, but if the parent process is sandboxed, then the child fake powershell executable is also sandboxed. So, the strength of Sandboxie protection depends, if one runs potentially vulnerable applications in the sandbox or not. Edited! The real problem for anti-exe solutions, arise with memory exploits, when they can run PowerShell from System.Management.Automation.dll (System.Management.Automation.ni.dll) . [/QUOTE]
Insert quotes…
Verification
Post reply
Top