TA0002 · EXECUTION
Inter-Process Communication
Adversaries may abuse inter-process communication (IPC) mechanisms for local code or command execution. IPC is typically used by processes to share data, communicate with each other, or synchronize execution.
Detect it with
Monitor for strings in files/commands, loaded DLLs/libraries, or spawned processes that are associated with abuse of IPC mechanisms.
Why it matters on shift
Inter-Process Communication is one of the concrete ways adversaries achieve execution. Recognising it in telemetry lets you name the technique in your ticket and pivot to what came before and after.
What to look for next
After execution, the next tactic is usually Persistence. Search your telemetry for the transition before closing the ticket.
3 sub-techniques
How it shows up in practice
- T1559.001
Component Object Model
Adversaries may use the Windows Component Object Model (COM) for local code execution.
- T1559.002
Dynamic Data Exchange
Adversaries may use Windows Dynamic Data Exchange (DDE) to execute arbitrary commands. DDE is a client-server protocol for one-time and/or continuous inter-process communication (IPC) between applications.
- T1559.003
XPC Services
Adversaries can provide malicious content to an XPC service daemon for local code execution.
Kill-chain context