Respect signing of Powershell scripts
Derek Howard 1 year ago • updated by Rishikesh Gajul (Product Manager) 1 year ago • 2
We've begun signing our Powershell scripts, thus preventing the scripts from being run if any modifications have been made to the content of the script. However, when pasting the script into the Commands tab of Control, complete with the signature block, the command runs anyway, even when the hash doesn't match.
I would like to see Control refuse to run a script if the signature doesn't validate. If it is a problem with the script itself, then the agent could manually validate that the script contents actually do what they want it to do, and simply not paste in the signature block.
Available in Version:
Customer support service by UserEcho
Nevermind, looks like there was an issue with our Group Policy settings; now all Powershell scripts are being blocked in that tab.