Securing Powershell

[ITGuyNW]

I'm reviewing our AD/GPO permissions during summer and one thing I want to look at is Powershell.

 

How should Powershell be appropriately secured for normal domain users these days? There seems to be a lot of argument online about hiding it because if its secure, then you don't need to hide it. However, how do I know its secure?

[mavhc]

Define secured, it can't do anything the user doesn't have permissions for, so you can't secure powershell, you can only secure the network/system as a whole

[psydii]

Make sure  you've got logging enabled, require (at least) remote signed, and have an av solution that supports AMSI