You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Import-module dbops is being blocked by security software. #160
I was at SQLbits last week where they mentioned this as a good solution to what I need.
I plan on running this in a Dev-ops Pipeline. But I want to test on my machine.
However, My companies security software is blocking is as malware.
I have reached out to our security team and they have confirmed it.
Obviously, this is false. However, what within the function could be causing this? So that I can justify an exception in the system.
Additionally if you could provide a way around it.
It was carbon black that was blocking it.
I recived this as the best error for now...
"The application pwsh.exe ran a script ....\Documents\PowerShell\Modules\PSFramework\1.7.270\PSFramework.psm1 that contains suspicious obfuscation techniques. This script contains highly suspicious obfuscated PowerShell code. A Deny policy action was applied."
Thanks for providing the details! Carbon Black seems to have an issue with the dependency module PSFramework. Here's a relevant issue to track: PowershellFrameworkCollective/psframework#517
Activity
nvarscar commentedon Mar 27, 2023
Possibly related to dataplat/dbatools#8241
Which AV software is causing this? What is the error that you see?
AEaston99 commentedon Mar 28, 2023
It was carbon black that was blocking it.
I recived this as the best error for now...
"The application pwsh.exe ran a script ....\Documents\PowerShell\Modules\PSFramework\1.7.270\PSFramework.psm1 that contains suspicious obfuscation techniques. This script contains highly suspicious obfuscated PowerShell code. A Deny policy action was applied."
nvarscar commentedon Mar 28, 2023
Thanks for providing the details! Carbon Black seems to have an issue with the dependency module
PSFramework. Here's a relevant issue to track: PowershellFrameworkCollective/psframework#517