T1559 Inter-Process Communication
EnterpriseAdversaries 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. IPC is also commonly used to avoid situations such as deadlocks, which occurs when processes are stuck in a cyclic waiting pattern. Adversaries may abuse IPC to execute arbitrary code or commands. IPC mechanisms may differ depending on OS, but typically exists in a form accessible through programming languages/libraries or native interfaces such as Windows Dynamic Data Exchange or Component Object Model. Linux environments support several different IPC mechanisms, two of which being sockets and pipes. Higher level execution mediums, such as those of Command and Scripting Interpreters, may also leverage underlying IPC mechanisms. Adversaries may also use Remote Services such as Distributed Component Object Model to facilitate remote IPC execution.
platforms
Platforms this applies to.
tactics
ATT&CK tactics this technique serves.
sub-techniques (3)
More specific entries beneath this one.
mitigations
ATT&CK mitigations that reduce this.
detected by (5)
Data components that detect this.
NIST CSF 2.0 — areas of relevance (Protect / Detect)
NIST CSF 2.0 areas this most relates to (evidence-ranked).
- PR.PSPlatform Securitymoderate · backed by 7 of 19 mapped controls
- DE.CMContinuous Monitoringmoderate · backed by 6 of 19 mapped controls
- PR.DSData Securitymoderate · backed by 6 of 19 mapped controls
Derived from MITRE CTID (Apache-2.0) and the NIST 800-53 ↔ CSF crosswalk (public domain). Indicative relevance along the Protect/Detect axis — not a compliance assessment or coverage claim.
mitigating controls (19)
Security controls that mitigate this.
software (17)
Malware and tools associated with this.
campaigns (2)
Campaigns that use this.
Detected by (Sigma) (1)
Sigma detection rules related to this.
source
Where this definition is published.