PowerShell utilizes execution policies to regulate how it loads configuration files and runs scripts. Implementation of these policies only happens on Windows platforms. The PowerShell execution policies are mentioned below:

• AllSigned:
  • The scripts can run.
  • Needs that all scripts and configuration files be signed by a reliable publisher, which includes scripts that you compose on the local computer.
  • Encourages you before EXECUTING scripts from publishers that are still not categorized as untrusted or trusted.
  • Risks running signed, but VICIOUS, scripts.
• Bypass:
  • Nothing is stopped and there are no alerts or prompts generated.
  • The Bypass execution policy is created for configurations in which a PowerShell script is constructed into a larger application or for configurations in which PowerShell is the basis for a program that possesses its security model.
• Default:
  • Restricted for Windows CLIENTS.
  • RemoteSigned for Windows servers.
• RemoteSigned:
  • The default execution policy for the Windows system.
  • Scripts can run.
  • A digital SIGNATURE from an AUTHORIZED publisher is required on internet downloaded scripts and configuration files. It contains email and instant messaging programs.
  • It doesn't need digital signatures on scripts that are not downloaded from the internet and composed on the local computer.
  • It executes internet downloaded scripts that are not signed if the scripts are unblocked, like utilizing the Unblock-File cmdlet.
  • Risks executing unsigned scripts from sources except for the internet and signed scripts that could be malicious in nature.
• Restricted:
  • The default implementation policy for Windows client computers.
  • Allows individual commands, but does not permit scripts.
  • Stops operating all script files, including configuration files (.ps1xml), PowerShell profiles (.ps1), and module script files (.psm1) formatting
• Undefined:
  • There is no implementation policy specified in the current scope.
  • The execution policy is Restricted for Windows clients and RemoteSigned for Windows Server if the implementation policy in all scopes is Undefined.
• Unrestricted:
  • The default execution policy for non-Windows systems and cannot be modified.
  • Unsigned scripts can operate. There is a chance of running malicious scripts.
  • Alerts the customer before running scripts and configuration files that do not belong from the Local intranet zone.