Process Killing Detected via Defend for Containers
This rule detects the killing of processes inside a container. An adversary may attempt to find and kill competing processes to gain control of the container.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
Known benign triggers
- There is a potential for false positives if the processes are killed for legitimate purposes, such as debugging or troubleshooting. It is important to investigate any alerts generated by this rule to determine if they are indicative of malicious activity or part of legitimate container activity.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| flare.io/learn/resources/blog/teampcp-cloud-native-ransomware | 13 |
From the source
- At source
- Open at source
- Upstream identifier
- 85d9c573-ad77-461b-8315-9a02a280b20b
- Tagged by the source as
- Data Source: Elastic Defend for ContainersDomain: ContainersNoise: UnknownOS: LinuxPerformance: FastPlatform: LinuxResources: Investigation GuideRule Type: Event Correlation (EQL)Tactic: ImpactUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3