Elastic Details Detection of Linux Persistence Across Boot, PAM, Packages, and Containers
Attack Tradecraft · 8 sources · Updated 2mo ago · First seen Feb 11, 2025

Elastic Security Labs published a series of Linux detection-engineering guides covering attacker persistence through scheduled tasks, systemd units, shell profiles, XDG autostart, permission and account changes, SSH keys, SysV/Upstart/rc.local startup paths, dynamic MOTD scripts, udev rules, package-manager hooks, Git hooks, process capabilities, and system-binary hijacking. The research maps techniques to MITRE ATT&CK and uses the PANIX simulation tool to demonstrate how adversaries can retain access or launch reverse shells, while recommending endpoint, file-integrity, process, network, service-state, and syslog telemetry alongside Elastic rules, ES|QL, and OSQuery hunts.
The latest guidance highlights high-impact persistence through malicious PAM changes, DPKG/RPM lifecycle scripts, and dangerous Docker deployments. Defenders should monitor PAM and package-management paths, suspicious child processes and outbound connections, lifecycle-script execution, and container settings such as privileged mode, host PID namespaces, and sensitive host mounts. Elastic cautions that boot-time persistence may execute before endpoint agents collect process events, making early file-change detection and proactive hunting essential; organizations should also tune detections for legitimate administration and remove obsolete Upstart systems from production.


