Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 623922" data-attributes="member: 32260">Thanks [USER=37647]@shmu26[/USER]. I wrote :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.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) .</blockquote>

[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]

Verification