What attackers do. Attackers use built-in command shells and scripting languages such as PowerShell, Windows Command Shell, Unix shells, Python or JavaScript to run their commands and tools. Because these interpreters are present and trusted on most systems, this is central to the Execution tactic.
How to defend. Restrict who can run interpreters and where, using application control, constrained language modes and removal of interpreters that are not needed. Enable detailed logging such as PowerShell script block logging, command line capture in process creation events and shell history collection. Endpoint detection rules should focus on suspicious parent and child relationships rather than the interpreter itself.
Signs to look for. Look for encoded or heavily obfuscated command lines, scripts launched by Office applications, browsers or web servers, and interpreters downloading content from the internet. A common gap is missing command line arguments in process logs, which hides what was actually run.