-
Potential Persistence via File Modification
Sep 19, 2026 · Domain: Endpoint OS: Linux Use Case: Threat Detection Tactic: Persistence Tactic: Credential Access Tactic: Privilege Escalation Tactic: Defense Evasion Data Source: File Integrity Monitoring Resources: Investigation Guide Noise: Medium Performance: Normal Rule Type: Event Correlation (EQL) Platform: Linux ·This rule leverages the File Integrity Monitoring (FIM) integration to detect file modifications of files that are commonly used for persistence on Linux systems. The rule detects modifications to files that are commonly used for cron jobs, systemd services, message-of-the-day (MOTD), SSH configurations, shell configurations, runtime control, init daemon, passwd/sudoers/shadow files, Systemd udevd, and XDG/KDE autostart entries. To leverage this rule, the paths specified in the query need to be added to the FIM policy in the Elastic Security app.
Read More