Reply to thread

Message

<blockquote data-quote="simmerskool" data-source="post: 1040262" data-attributes="member: 61091">+1~ day running Di on win10. Overnight it blocked 2 powershell scripts, I have Di popup on desktop. two (2) | script blocked | powershell...was blocked according to your company policy&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; security engine= script control&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; security module= powershellIf I hover over the popup it displays the full script. I then logged into Di dashboard and I am NOT seeing these 2 script block events, and the main dashbd is unchanged since the initial deep static scan. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite132" alt=":unsure:" title="Unsure&nbsp; &nbsp; :unsure:" loading="lazy" data-shortname=":unsure:" /> Company policy, I assume, are the initial setting used at deployment, I followed [USER=59691]@Kongo[/USER]&#039;s settings. Nothing seems &quot;broken&quot; <img class="smilie smilie--emoji" loading="lazy" alt="😅" title="Grinning face with sweat&nbsp; &nbsp; :sweat_smile:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f605.png" data-shortname=":sweat_smile:" /> Performance feel at the keyboard is normal, little or no impact running Di with MS Defender (w/exclusions for Di). Occasionally if I open something Di has not seen system will balk for a second or 2, but overall minimal impact felt. I did send CyF support a question about script blocks not seen in dashbd. Will update if I learn anything useful.</blockquote>

[QUOTE="simmerskool, post: 1040262, member: 61091"] +1~ day running Di on win10. Overnight it blocked 2 powershell scripts, I have Di popup on desktop. two (2) | script blocked | powershell...was blocked according to your company policy security engine= script control security module= powershell If I hover over the popup it displays the full script. I then logged into Di dashboard and I am [U]NOT[/U] seeing these 2 script block events, and the main dashbd is unchanged since the initial deep static scan. :unsure: Company policy, I assume, are the initial setting used at deployment, I followed [USER=59691]@Kongo[/USER]'s settings. Nothing seems "broken" 😅 Performance feel at the keyboard is normal, little or no impact running Di with MS Defender (w/exclusions for Di). Occasionally if I open something Di has not seen system will balk for a second or 2, but overall minimal impact felt. I did send CyF support a question about script blocks not seen in dashbd. Will update if I learn anything useful. [/QUOTE]

Verification