Threat Explorer
Command & Scripting Interpreter
T1059
Description
Adversaries abuse command and script interpreters (PowerShell, Bash, cmd) to execute commands.
Recommendations
- Application control
- Constrained language mode
- PowerShell logging
Security Reasoning
Composed from the intelligence model — every conclusion is traceable.
Command & Scripting Interpreter matters because it directly touches endpoints. The adversary's goal is to achieve an adversary objective against the organisation, which typically leads to materialisation of the underlying threat scenario. Left unchecked, it becomes a stepping stone in a broader operation rather than an isolated event.
Possible consequences
Affected assets
Interpreters and tooling execute on user endpoints and servers.
Security controls
Detection opportunities
- PowerShell / interpreter logging → alerts on this behaviour
- Behavioural EDR → alerts on this behaviour
- Existing rule · Suspicious PowerShell
Governance context
Few compensating controls apply — residual risk is close to inherent risk until additional controls land.
Reasoning chain
- Command & Scripting InterpreterAchieve an adversary objective against the organisationEvery technique exists to advance an adversary objective.
- Achieve an adversary objective against the organisationEndpointsInterpreters and tooling execute on user endpoints and servers.
- EndpointsMaterialisation of the underlying threat scenarioOnce the goal is achieved, materialisation of the underlying threat scenario typically follows.
- Materialisation of the underlying threat scenarioPowerShell / interpreter loggingDetect malicious script execution and capture command-line context.
- Materialisation of the underlying threat scenarioApplication control / allowlistingPrevent execution of unsigned or living-off-the-land binaries outside baseline.
- Materialisation of the underlying threat scenarioBehavioural EDRDetect injection, tampering and hands-on-keyboard behaviour.
- PowerShell / interpreter loggingPowerShell ScriptBlock (EID 4104) detection ruleDemonstrates that the control is designed and operating.
- PowerShell / interpreter loggingGPO enforcing Module & ScriptBlock loggingDemonstrates that the control is designed and operating.
- PowerShell / interpreter loggingEDR command-line telemetry sampleDemonstrates that the control is designed and operating.
- PowerShell / interpreter loggingISO 27001 · A.8.7 Protection against malware / A.8.19 Software installationISO 27001 fires here because the behaviour of "Command & Scripting Interpreter" is the exact scenario A.8.7 Protection against malware / A.8.19 Software installation exists to prevent — Application control and endpoint protection are the governance controls that restrict interpreter abuse.
- PowerShell / interpreter loggingNIST CSF · PR.PS — Platform SecurityNIST CSF fires here because the behaviour of "Command & Scripting Interpreter" is the exact scenario PR.PS — Platform Security exists to prevent — PS covers configuration and integrity of platforms where interpreters run.
- Compensating controlsResidual risk: highFew compensating controls apply — residual risk is close to inherent risk until additional controls land.
AI reasoning
Ask the AI to explain why, how, what changes, and what remains exposed — grounded in this reasoning chain.