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
Other security for Windows, Mac, Linux
Deep Instinct | Deep Learning AI Cybersecurity Platform
Message
<blockquote data-quote="simmerskool" data-source="post: 1040313" data-attributes="member: 61091"><p>That's what I was "afraid" of <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite117" alt=":eek:" title="Eek! :eek:" loading="lazy" data-shortname=":eek:" /> Let me reopen that screen, timeout...</p><p>I see two settings: | Script Protection | Deep Script Analysis at the top of this page</p><p>Malicious PowerShell Command Execution is set to Prevent</p><p>Di info comment (Defines the action that is performed on Powershell commands with malicious content)</p><p>____________________________________________________________</p><p>bottom half of same screen</p><p>Script Control</p><p>PowerShell execution is now set to Detect (was set to Prevent) CyF said Prevent will block good powershell commands that windows needs...</p><p></p><p>I am no expert (did anyone suspect anything different?) But not every powershell command is malicious, right? How do you tell? I'm expecting Di to figure that one out <img class="smilie smilie--emoji" loading="lazy" alt="😅" title="Grinning face with sweat :sweat_smile:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f605.png" data-shortname=":sweat_smile:" /> unrealistic?? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite119" alt=":rolleyes:" title="Roll eyes :rolleyes:" loading="lazy" data-shortname=":rolleyes:" /> Or the 2 scripts blocked overnight perhaps should have not been blocked? And if user has to write a specific rule for each action in windows, that seems unrealistic. Don't get me wrong, I am not saying you are wrong, but should Di be blocking good scripts at 3:55 AM while I'm usually sleeping. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite132" alt=":unsure:" title="Unsure :unsure:" loading="lazy" data-shortname=":unsure:" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite132" alt=":unsure:" title="Unsure :unsure:" loading="lazy" data-shortname=":unsure:" /> </p><p></p><p>And now seeing the full breakdown of the powershell script block: process chain wininit.exe -> services.exe -> svchost.exe -> CompatTelRunner.exe -> CompatTelRunner.exe -> powershell.exe | </p><p>User Name | NT Authority\System</p><p></p><p>Seeing all the info is Di_nice! Sounds like MS phoning home?? (can't share screenshot as I'm in VM, Di on Host)</p><p>So you're saying (I think) better on Prevent, but then when you see an event like this, Di should let user specifically allow that script from that source change the next time. And that's the better procedure every time something like this happens.</p></blockquote><p></p>
[QUOTE="simmerskool, post: 1040313, member: 61091"] That's what I was "afraid" of :eek: Let me reopen that screen, timeout... I see two settings: | Script Protection | Deep Script Analysis at the top of this page Malicious PowerShell Command Execution is set to Prevent Di info comment (Defines the action that is performed on Powershell commands with malicious content) ____________________________________________________________ bottom half of same screen Script Control PowerShell execution is now set to Detect (was set to Prevent) CyF said Prevent will block good powershell commands that windows needs... I am no expert (did anyone suspect anything different?) But not every powershell command is malicious, right? How do you tell? I'm expecting Di to figure that one out 😅 unrealistic?? :rolleyes: Or the 2 scripts blocked overnight perhaps should have not been blocked? And if user has to write a specific rule for each action in windows, that seems unrealistic. Don't get me wrong, I am not saying you are wrong, but should Di be blocking good scripts at 3:55 AM while I'm usually sleeping. :unsure::unsure: And now seeing the full breakdown of the powershell script block: process chain wininit.exe -> services.exe -> svchost.exe -> CompatTelRunner.exe -> CompatTelRunner.exe -> powershell.exe | User Name | NT Authority\System Seeing all the info is Di_nice! Sounds like MS phoning home?? (can't share screenshot as I'm in VM, Di on Host) So you're saying (I think) better on Prevent, but then when you see an event like this, Di should let user specifically allow that script from that source change the next time. And that's the better procedure every time something like this happens. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
