Windows PowerShell is, by default, quite secure. However, by changing the Execution Policy, you can make Windows PowerShell much more vulnerable to malicious code. In fact, the lowest level Execution Policy is Unrestricted, which permits all scripts to run without restriction or question.
In the January issue of TechNet Magazine, Don Jones discusses how malicious code can potentially use Windows PowerShell, he looks at the importance of protecting your profile, and gives advice on choosing the right Execution Policy to keep Windows PowerShell more secure.
And don’t miss his latest Cmdlet of the Month, where he introduces you to Get-AuthenticodeSignature.