What attackers do. Attackers abuse PowerShell to run commands, download tools, move through the network and execute code in memory. As it is built into Windows and powerful, it is a favourite for the Execution tactic.
How to defend. Enable PowerShell script block, module and transcription logging and forward the events centrally. Use constrained language mode with application control for most users, remove PowerShell version 2, and restrict remoting to administrators. Antimalware scan interface integration lets security tools see scripts after they are decoded.
Signs to look for. Look for encoded commands, hidden windows, download cradles, PowerShell launched by Office, browsers or web servers, and connections out to the internet from PowerShell. A common gap is collecting process start events but not the script content itself.