Linux File System Monitoring & Actions, (Tue, Dec 20th)

This post was originally published on this site

There can be multiple reasons to keep an eye on a critical/suspicious file or directory. For example, you could track an attacker and wait for some access to the captured credentials in a phishing kit installed on a compromised server. You could deploy an EDR solution or an OSSEC agent that implements an FIM (‘File Integrity Monitoring”)[1]. Upon a file change, an action can be triggered. Nice, but what if you would like a quick solution but agentless? (In the scope of an incident, for example)

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.