Execution Policy

Definitions

1. A PowerShell setting that controls whether scripts may run and whether they must be signed. The main policies are Restricted, which allows interactive commands but no scripts and is the default on Windows client systems; RemoteSigned, the default on Windows Server, which runs local scripts but requires a trusted signature on scripts downloaded from the internet, identified by the Mark of the Web; AllSigned, which requires signatures on every script; and Unrestricted and Bypass, which apply few or no checks. Policies can be set at several scopes, including Group Policy for the machine or user, the local machine, the current user, and the current process, with Group Policy taking precedence. Microsoft is explicit that the execution policy is not a security boundary: it exists to prevent accidental execution, and a user can bypass it by starting PowerShell with -ExecutionPolicy Bypass or by running script contents directly. Real control over script execution comes from tools such as AppLocker, WDAC, and constrained language mode.

   In plain English: A Windows setting that controls whether PowerShell scripts can run — more of a seatbelt than a lock, since advanced users can bypass it easily.

   Example: "Set-ExecutionPolicy RemoteSigned lets you run local scripts but requires downloaded ones to be signed."

Related Terms

• Responsible Disclosure
• Cmdlet
• Script Block
• Active Directory
• Bitlocker
• CASB
• Cloud Access Security Broker
• Data Loss Prevention
• DLP
• DMARC
• Email Authentication
• Firewall Rules
• Group Policy
• Ingress Filtering
• Living off the Land
• NTLM
• Pass the Hash
• Policy as Code
• Policy Engine
• PowerShell Module
• Shadow Copy
• Control Flow Guard
• Credential Dumping
• Disclosure Policy
• DLL Hijacking
• DLL Injection
• Domain Controller
• PowerShell Attack
• PS Exec
• RDP